Viva Engage and Yammer: What the Rename Actually Changed for Governance

By Nicolas Saliba · Published April 2023, Updated August 2026 · 8 min read

Quick answer: Viva Engage is the new name for Yammer. Microsoft completed the rename in 2023 and retired the Yammer brand, but the underlying network, communities and data did not change. What did change: Storyline and Answers were added, premium features moved under Viva Suite licensing, and community creation, ownership, retention and external access are now governed through Microsoft 365 admin rather than Yammer settings.

The question most internal communication teams still type into a search box is some version of “what is the difference between Yammer and Viva Engage”. The honest answer is that the difference nobody explained properly at the time was not the interface. It was who is allowed to create a community, who owns it, what happens when that owner leaves, how long the content survives, and whether anyone outside the company can take part.

All of those moved. Yammer was a network with its own administration console and its own network-level policy. Viva Engage is a surface on top of Microsoft 365 Groups, which means community governance now sits inside the same machinery that governs Teams, SharePoint and mailboxes^[1]. For an internal communication function, that is a bigger change than any feature on the release notes.

The rename was cosmetic. The plumbing was not.

Most published comparisons of Yammer and Viva Engage list features: Storyline, Stories, Leadership Corner, Answers, better Teams integration. Those are real, but a feature list is not a change management brief. What changed structurally is that a Viva Engage community is a Microsoft 365 Group. Create one and you also create a group mailbox, a SharePoint site, a Planner plan and a set of permissions that your IT and compliance colleagues already have policies for.

That single architectural fact produces every practical consequence below. It is also why the internal communication team that used to run its own network now finds itself raising tickets.

Dimension	Yammer, as most organisations ran it	Viva Engage today
Administration surface	Standalone Yammer admin centre, network-level settings	Microsoft 365 admin centre, Entra ID, Microsoft Purview
Community object	Yammer group, largely self-contained	Microsoft 365 Group with mailbox, SharePoint site and Planner
Who can create one	Usually anyone in the network	Whoever the tenant group-creation policy allows
Lifecycle	Groups persisted until manually archived	Group expiration and ownerless-group policies apply
External participation	External networks and external groups	Entra External ID guest access, governed centrally
Files	Yammer file store	SharePoint document library on the group site
Retention and eDiscovery	Separate Yammer data governance	Microsoft Purview retention policies and eDiscovery

The table leaves out two questions that usually come next. The first is licensing: community and conversation features are included in Microsoft 365 and Office 365 enterprise plans, while premium experiences such as Leadership Corner need Viva Suite or Viva Employee Communications and Communities^[5]. Our comparison of Viva Engage and Viva Engage Premium sets out where that line falls. The second is where Viva Engage stops and Teams starts, which we cover in Viva Engage vs Teams.

The four changes internal communication teams actually feel

You may no longer be able to create a community

In a well-governed Microsoft 365 tenant, group creation is restricted to a named security group, usually to stop Teams sprawl. Viva Engage communities inherit that restriction, because they are groups. Plenty of internal communication teams discovered this the first time they tried to stand up a community for a transformation programme and got an error message instead.

This is not Microsoft being obstructive. It is a reasonable IT policy that was written before anyone thought about the internal communication use case. The fix is administrative, not technical: get the internal communication function added to the allow-list, or agree a service level with the group that holds it. Either works. Discovering the problem on the morning of a launch does not.

Your communities can expire, and ownerless ones are a real risk

Microsoft 365 group expiration policy lets an organisation set groups to expire after a defined period unless an owner renews them, and there is a separate policy for groups that have lost all their owners^[2]. Both are sensible controls. Both are hazardous for internal communication, because IC-created communities are frequently owned by one enthusiastic person who has since moved to a different role.

The concrete failure looks like this. A safety community created in 2022 by a site HSE manager who left in 2024. Nobody renewed it. The renewal notification went to an inactive mailbox. Two years of incident discussion and a thousand members are now sitting on a countdown that nobody in the communication team can see. Run an ownership audit before that becomes a conversation with legal rather than with IT.

External communities work completely differently now

Yammer external networks were a distinct construct that a lot of organisations used for partner, dealer, franchise and customer advisory communities. That pattern is gone. External participation in Viva Engage runs through Entra External ID guest access, governed by tenant-wide policy rather than by a network you controlled.

For an internal communication team in a partner-heavy business, this is the single most disruptive item on the list, and it has a measurement tail as well as an access tail. Guest accounts carry no organisational attributes, which is why we wrote separately about how intranet and extranet audiences break your segmentation at the boundary. If you ran an external Yammer network, that population needs a deliberate plan, not a migration ticket.

Compliance can now see everything, and should

Viva Engage content falls under Microsoft Purview retention policies and is discoverable through the normal eDiscovery process^[3]. This is an improvement in governance terms and a change in practice terms. Community guidance written for the Yammer era, when the data governance story was separate and less visible, may not say the right things about what belongs in a public community and what belongs in a private channel.

Rewrite the community charter with your compliance colleague rather than for them. It takes an afternoon and it prevents the conversation where a moderator learns about retention policy from a legal hold notice.

Storyline changed the unit of organisation, quietly

One change deserves separate treatment because it is not a governance setting at all. Storyline is person-centred: a leader posts to their own storyline and it reaches followers, not community members. That is a genuinely useful affordance for leadership communication, and it also means a significant share of your most visible content now sits outside any community, with no moderator, no charter and no community owner.

Decide your position on this and write it down. Some organisations route all executive communication through Leadership Corner and treat storyline as informal. Others do the opposite. Both are defensible. Having no position is what produces the situation where the CEO’s most-read post of the year cannot be found in any reporting structure. Our complete guide to Viva Engage works through how the surfaces fit together.

The honest position on native analytics, and where measurement fits

Viva Engage community insights are free, already switched on, and genuinely sufficient for a community manager running one community. If you own a single community and want to know whether your posts land inside it, use the native panel and move on.

The governance changes above create a second-order measurement problem that native reporting does not address. Communities that expired are gone from the numbers. Communities that changed owner may have changed name. External participants who used to sit in a Yammer external network are now guests with no attributes. The trend line you present to the executive committee spans all of that, and the native retention window does not. We covered the measurement continuity question in depth in the piece on what Yammer changed in your organisation and what Viva Engage did to the measurement, and the specific gaps in the limits of native Viva Engage analytics.

Teams sometimes try to rebuild the missing history in Power BI against the Microsoft Graph reporting API. It can be done, but be clear-eyed. The reporting API is not consistently reliable and produces days with missing data, customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, and a dependable build needs a proper ingestion process with scheduled reconciliation and a named owner. Budget for the pipeline, not the dashboard.

Tryane sits above all of this. It reads Viva Engage alongside SharePoint, Teams and your newsletter platform, joins that activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions so the Yammer years and the Viva Engage years read as one trend. It is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, and deploys in a couple of hours with no agent to install. Gallagher’s State of the Sector research keeps finding measurement to be the capability internal communicators name as their biggest gap, and product transitions like this one are a large part of the reason^[4].

A short governance checklist

Confirm whether your internal communication team is on the group-creation allow-list, and fix it now rather than at launch.
Export the list of Viva Engage communities with their owners, and flag every one with fewer than two active owners.
Check whether group expiration policy applies to communities, and who receives the renewal notification.
Rewrite the community charter alongside compliance, covering retention and what belongs in a public community.
Write down your position on storyline versus communities for executive content.
Re-plan any population that used to sit in a Yammer external network, including how you will measure it.

Frequently asked questions

Is Yammer completely gone?

Yes. Microsoft completed the transition and retired the Yammer brand and the standalone experience. Communities, posts and membership carried across into Viva Engage. The administration model, the external network construct and the data governance story did not carry across unchanged, which is where most of the operational surprises came from.

Is Yammer still available?

Not under that name. Microsoft’s FAQ answers the question directly: Yammer is now Viva Engage, and although the name changed, the product is largely the same^[6]. When Microsoft announced the move in February 2023, it said all of Yammer would become Viva Engage, retiring the Yammer brand, with no changes to features or capabilities for Microsoft 365 customers beyond the branding^[7]. The old name survives in a few admin places: Engage administrators are still called Yammer administrators in Microsoft Entra ID, and the core service plan appears as Viva Engage Core or Yammer Enterprise^[8].

Is Viva Engage free?

Not as a standalone product, but it costs nothing extra for most Microsoft 365 customers. Microsoft’s FAQ says you need a Viva Engage or Yammer licence, and that Viva Engage is available to most Microsoft 365 customers at no additional cost^[6]. Community and conversation features come with Microsoft 365 and Office 365 enterprise plans; premium features need Viva Suite or Viva Employee Communications and Communities^[5]. As of September 2026, Microsoft’s US pricing page lists Employee Communications and Communities from $2.00 per user per month and Viva Suite from $12.00 per user per month, both paid yearly^[9].

Why can I no longer create a community?

Almost certainly because your tenant restricts Microsoft 365 group creation to a named security group, and Viva Engage communities are groups. This is a common control against Teams sprawl. Ask your Microsoft 365 administrator to add the internal communication function to the allow-list or to agree a turnaround time for requests.

Can a Viva Engage community be deleted automatically?

If your organisation applies the Microsoft 365 group expiration policy, a community can expire and be deleted when no owner renews it. Groups that have lost all their owners are a related risk. Both are worth auditing, particularly for older communities created by people who have since changed role.

What replaced Yammer external networks?

External participation now runs through guest access governed by Entra External ID at tenant level. There is no direct equivalent of a separate external network under your own control. Organisations that ran partner or customer communities on the old model generally need to redesign the approach rather than migrate it, and should plan for the fact that guest accounts carry no organisational attributes for reporting.

What are the alternatives to Yammer or Viva Engage?

Inside Microsoft 365, the usual options each cover part of what Viva Engage does. Teams channels suit project or team-based collaboration rather than open, organisation-wide communities^[10]. SharePoint communication sites are built for broad communication, with the goal of informing readers rather than having them create content^[11]. Viva Connections gives employees a personalised gateway to news and company resources from an app in Teams, and is available to Microsoft 365 and Office 365 enterprise plan users^[12]. Viva Amplify manages campaigns published to Outlook, Teams and SharePoint, and needs a Viva Suite or Viva Employee Communications and Communities licence^[13]. Outside Microsoft, the alternatives are other enterprise social networks, intranet platforms and employee communication apps. Tryane is not a replacement for any of them: it is the analytics layer that measures Viva Engage, SharePoint, Teams and newsletters together, whichever mix you keep.

Does Tryane replace Viva Engage analytics?

No. Viva Engage keeps recording what it records. Tryane sits above it, reading Viva Engage alongside SharePoint, Teams and newsletters, joining all of it to your organisational structure so you can answer cross-channel and segmented questions no single native panel can. You keep the Microsoft 365 investment and add the layer for what native does not do.