What actually changed
Less changed than most organizations expect, and the parts that did change are the ones that matter for planning. Microsoft's Viva service description calls Viva Engage a new app, integrated in Teams, that surfaces existing and new community experiences powered by Microsoft 365 services; it is available to all Microsoft 365 or Office 365 enterprise and frontline plan users, and it is the evolution of Yammer (Microsoft Learn, Microsoft Viva service description, accessed 2026-10-20). Networks, communities and conversations continued. What changed is where people meet the product (inside Teams and Outlook as well as on its own site), how features are licensed (a Core tier and a premium tier), and how far the network depends on Microsoft 365 groups, SharePoint and Purview. EPC Group's Microsoft 365 consulting practice treats a Yammer-era network as a governance project first and an adoption project second, because the compliance posture of the network is decided by its configuration, not by its name.
Licensing: Core, premium and Answers
Microsoft documents three service plans. Viva Engage Core, also listed as Yammer Enterprise, comes with Microsoft 365 and enables the core experiences, for example communities and storyline. Viva Employee Communities and Communications enables the premium experiences: leadership corner, AMAs, storyline announcements, delegation, analytics and campaigns; it comes with Microsoft Viva Suite and with Microsoft Viva Employee Communications and Communities. Viva Engage Knowledge enables the premium Answers experience and ships in the same two products (Microsoft Learn, Viva Engage setup requirements, accessed 2026-10-20).
Two details shape rollout plans. First, if an organization does not enforce Viva Engage licensing, users can still reach the Core experience; if it does, each user needs a Microsoft 365 license and the Core service plan (same source). Per-user Core licenses exist so that Engage can be rolled out to part of a company, and only users with a Core license see the Viva Engage tile and the Viva Engage app in Teams (Microsoft Learn, Manage Viva Engage Core user licenses in Microsoft 365, accessed 2026-10-20). Second, administrators do not need any Engage license: Engage administrators, still called Yammer administrators in Microsoft Entra ID, can configure Core and premium features without a premium assignment (Microsoft Learn, Viva Engage setup requirements, accessed 2026-10-20). EPC Group therefore licenses premium only for the leaders, communicators and community managers who use those features, and leaves the rest of the company on Core.
Networks, native mode and connected communities
The compliance-relevant change is the connection to Microsoft 365 Groups. To use connected communities, a network must enforce Microsoft 365 identity, which runs a seven-day trial before its status changes to Committed, and must be in a one-to-one configuration with its tenant. About 24 hours after commitment, new eligible communities are connected automatically, and after about a week existing eligible communities convert. A community is eligible if it is public or private internal, has an owner and members, and its owner has Microsoft 365 Group creation rights; unlisted private and external groups cannot connect (Microsoft Learn, Viva Engage and Microsoft 365 Groups, accessed 2026-10-20).
A connected community gets a SharePoint site and document library, a OneNote notebook and a Planner plan, follows the tenant's Microsoft 365 Groups naming policy, and is deleted along with its group if the group expiration policy removes it. Restricting who can create Microsoft 365 Groups also determines which new communities connect (same source). Attachments to community posts are stored in the community's SharePoint library under Apps/Viva Engage, or under a Yammer folder for communities created before the rename, and storyline attachments sit in a hidden library in the owner's OneDrive (Microsoft Learn, Viva Engage file storage overview, accessed 2026-10-20). Microsoft defines native mode as the state in which all users are in Microsoft Entra ID, all groups are Microsoft 365 Groups and all files are in SharePoint Online (Microsoft Learn, Get started with Communication Compliance, accessed 2026-10-20). EPC Group's first deliverable on a Yammer-era network is a readiness check against those conditions: multiple networks, unlisted groups, ownerless communities and users without Entra accounts.
Communities, Teams channels and leadership communications
The question EPC Group is asked most is where a conversation should live. The working rule: a Viva Engage community serves a broad or self-selecting audience that reads, asks and reacts, such as a practice network, an employee resource group or a company-wide announcements space; a Teams channel serves a defined team that produces work together. Because a connected community is itself a Microsoft 365 group, and a group created from Outlook or elsewhere does not include Viva Engage (Microsoft Learn, Viva Engage and Microsoft 365 Groups, accessed 2026-10-20), the choice is made at creation and is hard to reverse, which is why EPC Group puts it on the provisioning form. Storylines bridge the two: storyline posts from Teams or Engage are visible on both surfaces, and premium users can send storyline announcements and view analytics (Microsoft Learn, Manage Viva Engage experiences in Microsoft Teams, accessed 2026-10-20).
Leadership features need their own governance. Identified leaders with the Communities and Communications service plan get storyline announcements, leadership corner, campaigns and AMAs; leaders without it get storyline only. Leader identification and audience management are prerequisites for those features, a leader can have up to 40 audiences, and only an Engage, verified or network admin or a corporate communications manager can enable an org-wide audience (Microsoft Learn, The role of leaders, accessed 2026-10-20). EPC Group's Viva employee experience practice writes these decisions into a one-page communications policy before premium licenses are assigned.
Retention and eDiscovery
Microsoft Purview treats Viva Engage as two retention locations: Viva Engage community messages and Viva Engage user messages. Copies of messages are stored in hidden folders, in group mailboxes for community messages and in each participant's mailbox for user messages, and compliance administrators search them with eDiscovery rather than relying on what the app shows. User messages include private messages, storyline posts and copies of community messages that mention or notify the user. Expired items move to the SubstrateHolds folder within up to seven days and are then permanently deleted unless another policy, Litigation Hold, delay hold or eDiscovery hold applies. Files are excluded and follow SharePoint and OneDrive retention, and a departing user's messages under retention are kept in an inactive mailbox (Microsoft Learn, Learn about retention for Viva Engage, accessed 2026-10-20). Microsoft adds that a full Viva Engage design also needs a policy on the Microsoft 365 Group mailboxes & sites location, and that Viva Engage retention policies do not support admin units (Microsoft Learn, Create and configure retention policies, accessed 2026-10-20).
Documented work
ANON-CASES: EPC Group engagement data for Viva Engage covers large enterprises consolidating Yammer-era networks, moving them to enforced Microsoft 365 identity and connected communities, splitting Core and premium licensing, and adding Purview retention for community and user messages, delivered by the firm's Microsoft 365 consulting practice. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.
Primary sources
- Microsoft Viva service description — Microsoft Learn, accessed 2026-10-20
- Viva Engage setup requirements — Microsoft Learn, accessed 2026-10-20
- Manage Viva Engage Core user licenses in Microsoft 365 — Microsoft Learn, accessed 2026-10-20
- Viva Engage and Microsoft 365 Groups — Microsoft Learn, accessed 2026-10-20
- Viva Engage file storage overview — Microsoft Learn, accessed 2026-10-20
- Manage Viva Engage experiences in Microsoft Teams — Microsoft Learn, accessed 2026-10-20
- The role of leaders — Microsoft Learn, accessed 2026-10-20
- Learn about retention for Viva Engage — Microsoft Learn, accessed 2026-10-20
- Create and configure retention policies — Microsoft Learn, accessed 2026-10-20
- Get started with Communication Compliance — Microsoft Learn, accessed 2026-10-20
Frequently Asked Questions
Is Viva Engage included in Microsoft 365, or does it need a Viva license?
The core experience is included. Microsoft lists the Viva Engage Core (or Yammer Enterprise) service plan as coming with Microsoft 365 and enabling communities and storyline; if licensing is enforced, each user needs a Microsoft 365 license and that Core service plan. Premium experiences, including leadership corner, AMAs, storyline announcements, delegation, analytics and campaigns, come from the Viva Employee Communications and Communities service plan in Microsoft Viva Suite or Microsoft Viva Employee Communications and Communities, and the full Answers experience needs the Viva Engage Knowledge plan (Microsoft Learn, Viva Engage setup requirements, accessed 2026-10-20). Engage administrators need no Engage license to administer either tier.
What happened to Yammer networks and communities?
Microsoft describes Viva Engage as the evolution of Yammer, available to all Microsoft 365 or Office 365 enterprise and frontline plan users and integrated in Teams (Microsoft Learn, Microsoft Viva service description, accessed 2026-10-20). Existing networks and communities carried over; the Entra role is still listed as Yammer Administrator, and attachment folders in older communities are still labeled Yammer (Microsoft Learn, Viva Engage file storage overview, accessed 2026-10-20). Networks that enforce Microsoft 365 identity and run one network per tenant have eligible communities connected to Microsoft 365 Groups, each with a SharePoint site, OneNote notebook and Planner plan (Microsoft Learn, Viva Engage and Microsoft 365 Groups, accessed 2026-10-20).
When should a community be a Viva Engage community rather than a Teams channel?
EPC Group uses a Viva Engage community when the audience is broad, membership is open or dynamic, and the purpose is announcements, questions and discussion across departments; it uses a Teams channel when a defined team needs to work together on files, meetings and tasks. Both sit on Microsoft 365 Groups: a connected community creates a group with its own SharePoint site, and a group created in Outlook does not include Viva Engage (Microsoft Learn, Viva Engage and Microsoft 365 Groups, accessed 2026-10-20). Storylines also appear in Teams chats, so leaders can post once and reach both surfaces (Microsoft Learn, Manage Viva Engage experiences in Microsoft Teams, accessed 2026-10-20).
How are leadership communications, such as Leadership Corner and storylines, governed?
Any Engage-licensed user can be identified as a leader, but only leaders with the Viva Engage Communities and Communications service plan get storyline announcements, leadership corner, campaigns and AMAs; others get storyline only. Verified admins, network admins, Engage admins and licensed corporate communications managers identify leaders, and leaders or their delegates configure up to 40 audiences in Manage audiences, with org-wide audiences enabled by an admin (Microsoft Learn, The role of leaders, accessed 2026-10-20). Engage admins can turn leadership corner off in feature management. EPC Group writes a short communications policy naming who is a leader, who can delegate, and who approves org-wide audiences.
How are Viva Engage retention and eDiscovery handled?
Microsoft Purview retention policies have two Viva Engage locations, Viva Engage community messages and Viva Engage user messages. Copies of messages are stored in hidden folders in group and user mailboxes, which eDiscovery searches; messages visible in the app are not the compliance copies (Microsoft Learn, Learn about retention for Viva Engage, accessed 2026-10-20). Files are not covered by those locations, so Microsoft advises a second policy on the Microsoft 365 Group mailboxes & sites location (Microsoft Learn, Create and configure retention policies, accessed 2026-10-20). Communication Compliance needs the network in native mode (Microsoft Learn, Get started with Communication Compliance, accessed 2026-10-20).
Talk to a senior architect
If your organization still runs a Yammer-era network with unclear licensing, unconnected communities or no Viva Engage retention policy, a 30-minute discovery call with a senior EPC Group architect will map what you have against native mode and set out the plan. See the Microsoft 365 consulting service hub for engagement structures.
Email contact@epcgroup.net or call 888-381-9725.
a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.