How Yammer Influenced Your Organisation, and What Viva Engage Changed

By Nicolas Saliba · 8 min read

Every organisation that ran Yammer for more than a couple of years has the same artefact sitting inside Viva Engage today: a social graph built by people who have since changed roles, changed countries, or left. The communities are still there. The membership counts still look respectable. And when the CCO asks whether the enterprise social network is doing anything for the organisation, the honest answer from most internal communication teams is that they cannot tell.

That gap is not a failure of effort. It is a measurement problem created by a product transition. Yammer became Viva Engage in 2023, and Microsoft carried the network across but reset a great deal of the analytical continuity that IC teams had built around it^[1]. This article is about what survived that move, what did not, and how to answer the connection question with evidence rather than membership counts.

What Yammer actually changed inside organisations

It is worth being precise about Yammer’s contribution, because the vendor language around enterprise social networks has always been vague. Yammer did three specific things well in large organisations.

First, it created lateral communication paths that the org chart did not provide. A quality engineer in a plant in Lyon could ask a question that a quality engineer in a plant in Ohio answered, without either of them routing through their respective management chains. In a 12,000-person manufacturer with 40 sites, that is not a small thing. It is the difference between solving a problem once and solving it forty times.

Second, it gave leadership a channel that was visibly not a broadcast. A CEO post that accepted replies read differently from a CEO email that did not. Whether leaders used that well varied enormously, but the affordance existed.

Third, and least discussed, it produced a public record of who knew what. Over several years, a well-used Yammer network became a searchable archive of institutional problem-solving. That archive is the asset most organisations underestimated and most failed to carry forward deliberately.

The part that did not carry over

Viva Engage inherited the communities, the posts, and much of the membership. What it did not inherit was the measurement layer that IC teams had assembled around Yammer, often over years of spreadsheet work. Community insights in Viva Engage report on the community. They do not report on the organisation.

That distinction matters more than it sounds. A community insights panel will tell you that a community has 1,400 members and that 90 posted last month. It will not tell you whether those 90 people are concentrated in one function, whether the frontline is represented at all, or whether engagement in your German sites collapsed after a reorganisation. Those are organisational questions, and they require organisational attributes that the native analytics does not hold.

Why membership counts are the wrong measure

The most common reporting pattern we see is a monthly slide with community counts, member counts, and a post volume trend. It is easy to produce and it survives scrutiny only until someone senior asks a follow-up question.

The follow-up question is usually some version of: are the people we most need to reach actually in this network? For most organisations, the answer is uncomfortable. Gallup’s long-running workplace research has consistently found that the majority of the global workforce is not engaged at work, and that the gap is widest in frontline and deskless populations^[2]. An enterprise social network that is thriving among head-office knowledge workers and absent on the shop floor is not connecting the organisation. It is connecting a segment of it, and reporting on the aggregate hides exactly that.

Gallagher’s State of the Sector research has repeatedly identified measurement as the capability gap internal communicators name first^[3]. The reason is structural rather than personal. The native tooling reports what it can see, and what it can see is activity inside a product, not participation across a workforce.

Question	What native Viva Engage insights answer	What it cannot answer
Is the network active?	Yes. Post, reply and reaction volume over time.	Whether activity is broad or concentrated in a handful of teams.
Who is participating?	Named individuals and counts per community.	Participation rate by function, country, language or site.
Did the leadership post land?	Views and reactions on that post.	Whether it reached the populations it was written for.
Is this improving?	Trend over the retained reporting window.	Multi-year trend spanning the Yammer to Viva Engage transition.

The honest position on Microsoft native analytics

Viva Engage community insights are free, already switched on, and sufficient for a community manager running a single community. If you own one community and you want to know whether your posts are landing inside it, the native panel does that job and you do not need anything else.

The limits appear when the question becomes organisational. Native insights do not join to HR attributes, so you cannot segment by function, grade, site or contract type without exporting and joining the data yourself. The retained reporting window is finite, which makes multi-year narrative difficult precisely when you are trying to show progress across the Yammer transition. And the data lives in a different place from your SharePoint intranet numbers and your newsletter numbers, so cross-channel reach stays out of reach.

Teams often try to close this with a custom Power BI build against the Microsoft Graph reporting API. That route can work, but it is more demanding than it first appears. The reporting API is not consistently reliable: it produces days with missing data, and we have seen customers whose Power BI dashboards return KPI values that do not match the native SharePoint reports for the same period. Building on it properly requires a robust ingestion process, scheduled reconciliation against the native figures, and someone who owns that pipeline. Several organisations have made it work. Many more have quietly abandoned the build after the first reconciliation argument in front of an executive audience. If you go this route, budget for the pipeline, not just the dashboard. Our note on SharePoint analytics in Power BI covers the specific failure modes in more detail.

What connection looks like when you can measure it

A useful way to reframe the question is to stop asking whether the network is active and start asking whether it is representative. Three measures make that concrete.

Participation rate by population, not headcount. Not “1,400 members” but “38 per cent of the commercial function, 4 per cent of manufacturing”. The second version tells you where to act.
Reach of the specific message, by the segment it was written for. A safety update aimed at plant operators should be measured against plant operators, not against the whole tenant.
Cross-channel reach. Some of your audience will never come to Viva Engage. They will get the message from the SharePoint intranet, a manager cascade or a printed board. Counting only the social channel systematically undercounts the people hardest to reach.

This is the layer Tryane sits in. 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 rather than two disconnected reports. If you are working through what to put on the monthly slide, our guide to internal communication KPIs sets out the measures that survive executive scrutiny, and the piece on audience segmentation covers how to structure the attributes before you start.

On the practical side: Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency available on request, and deploys in a couple of hours using single sign-on through Azure AD or Entra ID. There is no agent to install and no change to your existing Viva Engage configuration. For teams evaluating options, the comparison of Tryane against Viva Engage native analytics lays out where each approach fits.

Frequently asked questions

Is Yammer still available?

No. Microsoft completed the transition of Yammer to Viva Engage, and the Yammer branding and standalone experience have been retired. Existing communities, posts and membership moved across. What did not move across cleanly, for most organisations, was the reporting continuity that teams had built around the old product.

Did we lose our Yammer history when we moved to Viva Engage?

The content generally carried over. The analytical history is a different matter. Native reporting retains a finite window, which means multi-year comparisons spanning the transition are usually not available from the native tooling. If you need to show a trend that starts before the migration, you need a measurement layer that held that history independently.

Can Viva Engage insights tell me whether frontline staff are participating?

Not directly. Community insights report activity within a community, and do not join to workforce attributes such as function, site or contract type. To answer a frontline participation question you need to combine Viva Engage activity with your organisational structure, which means either exporting and joining the data yourself or using a dedicated analytics layer that does the join for you.

Should we build this in Power BI instead?

You can, and some organisations run it well. Be aware that the Microsoft Graph reporting API produces days with missing data and that customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period. A dependable build needs a robust ingestion process, scheduled reconciliation against native figures and a named owner. Budget for the pipeline rather than the dashboard.

Does Tryane replace Viva Engage analytics?

No. Viva Engage continues to record 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 that no single native panel can. You keep your Microsoft 365 investment and add the measurement layer for what native cannot do.

Sources

• Microsoft Learn, Viva Engage overview

• Gallup, State of the Global Workplace

• Gallagher, State of the Sector