The question that starts this is usually short. The CCO wants to know whether the intranet is working, or whether the investment in Viva has produced anything, and the Head of Internal Communication opens the Microsoft 365 admin centre to find out. What comes back is a set of usage reports: active users per product, files stored, mail sent, a Viva Engage activity table[1]. Every figure is accurate. None of them answers the question that was asked. That gap opened with the Office 365 Adoption content pack, survived the rebrand to Microsoft 365, and survived the arrival of Viva. This is about what an analytics layer over Microsoft 365 has to do before an internal communication team can use it.
The adoption reporting was built for someone else
The Office 365 Adoption content pack, and the usage reports that succeeded it, were built for a real customer with a real problem. That customer was the IT director who had signed a large licence agreement and needed to show the organisation was using it. Adoption reporting does that job well. It tells you how many people opened Teams last month, how many had SharePoint file activity, and how the curve moved after the rollout campaign.
Internal communication inherited those reports because they were the only ones in the building. They were never designed for the internal communication question, which is not “are people using the product” but “did this message reach the population it was written for, and did anything change as a result”. Those two questions look similar on a slide. They diverge completely the moment someone senior asks a follow-up.
The real difference is the unit of analysis. Adoption reporting counts product events at tenant level. Internal communication measures a specific message against a specific audience, and that audience is not a property the product holds. Microsoft 365 knows a user opened a page. It does not know the user is a shift supervisor in a plant in Valenciennes, which is the only fact that makes the number interesting.
What actually changed when Office 365 became Microsoft 365
The rename in 2020 was cosmetic. What followed it was not. The number of distinct surfaces on which an internal communication team publishes went from roughly two to roughly six, and each new surface arrived with its own reporting panel, its own definitions and its own retention window.
A team that in 2018 published to a SharePoint intranet and a Yammer network now publishes to SharePoint communication sites, news posts surfaced through Viva Connections on mobile[2], Viva Engage communities, Teams channels and announcements, a newsletter platform, and increasingly video hosted in Stream and embedded across all of the above. That is six or seven places a message can land.
The reporting fragmented faster than the publishing did
Every one of those surfaces reports on itself. SharePoint site analytics reports on the site. Viva Engage community insights report on the community. The Teams usage report counts Teams activity. There is no native place where a message published in three of them appears as one number, and no native way to ask what proportion of a given population saw it in any of them.
This is the practical reason so many internal communication teams still run a monthly spreadsheet. It is not that they lack tooling. They have seven tools, each correct about a slice, and no arithmetic that combines the slices honestly. Adding SharePoint page views to Viva Engage reactions produces a number with no meaning, and experienced practitioners know it, which is why the spreadsheet ends up reporting each channel separately and never answering the reach question at all. Our note on measuring cross-channel internal communications works through why the naive addition fails.
Five things the analytics layer has to do
Strip away the vendor categories and the requirement comes down to five capabilities. A tool that does three of them is a partial answer. A tool that does none of them is an adoption report with a nicer chart.
1. Read the surfaces together. SharePoint, Viva Engage, Teams and the newsletter platform have to arrive in one model with one definition of a reader, so a message published across several of them can be counted once. This is the capability that turns “12,000 page views and 340 reactions” into “reached 61 per cent of the population it targeted”.
2. Join activity to organisational structure. Function, country, site, language, grade, contract type, manager line. Without this join every figure is a tenant aggregate, and the aggregate flatters you, because head office reads everything and head office is loud in the data. The join is normally made through Entra ID or a periodic HR file, and getting the attribute model right matters more than the tool choice. Our guide to audience segmentation for internal communications covers how to structure it.
3. Resolve to the message, not the surface. An internal communication team plans campaigns, not sites. The unit that has to be measurable is “the safety briefing published on 14 March”, across wherever it appeared, not “the EHS communication site in March”.
4. Hold history across product transitions. Microsoft renames and replaces things on a roughly three-year cycle. Yammer became Viva Engage. Delve went. Stream moved. Each transition resets or truncates native reporting, and a team wanting a five-year trend needs that history held somewhere that is not the product. This is the most under-appreciated requirement, and it becomes visible at the worst possible moment, which is a budget review. The article on what Viva Engage changed about Yammer measurement covers what that break cost teams.
5. Be delegable without admin rights. Most native usage reporting requires a tenant administrator role or a Power BI Pro licence to see anything useful. An internal communication team of four, sitting outside IT, needs its own access, and needs to be able to give a country communication manager a filtered view without raising a ticket.
The honest position on Microsoft native
Native Microsoft 365 reporting is free, already switched on, and genuinely sufficient in a common case: one team, one surface, one question. If you own a single communication site and want to know whether traffic rose after the redesign, SharePoint site analytics answers that and you should not buy anything. The same applies to a community manager watching one Viva Engage community. Reaching for a third-party tool there adds cost and a login for no gain.
The limits are structural rather than a matter of quality. Native reporting is per-surface by design, holds no organisational attributes, and retains a finite window. Internal communication teams hit those three constraints in that order, usually within the first year of trying to report properly.
| What you want to know | Microsoft 365 usage reports | SharePoint site analytics | Viva Engage insights | A dedicated IC analytics layer |
|---|---|---|---|---|
| Is the product being used? | Yes, tenant level | Per site | Per community | Yes, and by population |
| Did this campaign reach the frontline? | No | No | No | Yes, if attributes are joined |
| One number across SharePoint, Engage and newsletter | No | No | No | Yes |
| Trend spanning the Yammer to Viva Engage move | No | No | No | Yes, history held independently |
| Access for a non-admin communicator | Admin role usually needed | Site owner | Community admin | Delegated by segment |
| Cost | Included | Included | Included | Licensed |
The Power BI route and what it really costs
The obvious internal answer is to pull the Microsoft Graph reporting API into Power BI and build the cross-surface model yourself[3]. Several organisations run this well. It is worth understanding what makes it hard before committing a data engineer to it.
The Graph reporting API is not consistently reliable. It produces days with missing data, and a dashboard built on a naive daily pull will quietly show troughs that are collection failures rather than behaviour. Separately, customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, which is a difficult conversation to have in front of an executive audience. A dependable build needs a robust ingestion process with retry and backfill, plus scheduled reconciliation against the native figures and a named owner for both. Budget for the pipeline rather than the dashboard. Our longer piece on SharePoint analytics in Power BI sets out the failure modes.
Where the specialist tools sit
There is a small, serious market here and it is worth knowing it honestly. Swoop Analytics has deep expertise in enterprise social network analysis and is strong on network structure in Viva Engage. Intlock’s CardioLog Analytics is thorough on SharePoint and lands well where IT owns the deployment. tygraph, now part of AvePoint, suits large enterprises buying governance and analytics together. Any of the three can be the right answer depending on which surface dominates your estate.
Tryane sits in the cross-channel layer specifically. It reads SharePoint, Viva Engage, Teams and newsletter platforms together, joins that activity to organisational structure through Entra ID or an HR file, and keeps unlimited history so a trend survives the next product transition. On the procurement questions: SOC 2 Type 2 certified, GDPR compliant by design, EU hosting by default with US data residency on request, single sign-on through Azure AD or Entra ID, no agent to install, deployment in a couple of hours. For the direct comparison, see Tryane against SharePoint native analytics, and if you are choosing measures rather than tools, start with the internal communication KPIs that survive executive scrutiny.
Frequently asked questions
Does the Office 365 Adoption content pack still exist?
Not under that name. Its function moved into the usage reports in the Microsoft 365 admin centre and the Microsoft 365 usage analytics template for Power BI. The reporting is better than it was in 2018, but its audience has not changed: it answers the IT adoption question, not the internal communication reach question.
Can I get reach by department from Microsoft 365 natively?
Not without building it. Native reporting holds no organisational attributes such as function, site or contract type. To segment by department you export the activity data and join it to a workforce dataset yourself, or use an analytics layer that performs the join as part of its normal operation.
Is Viva Connections reporting enough to measure the intranet on mobile?
It reports dashboard and feed usage, which is useful and was not available before. It does not tell you which populations were reached, and it does not combine with your SharePoint news figures into one reach number for a campaign. Treat it as one more surface to include rather than as the answer.
How long does an analytics layer take to deploy on an existing tenant?
For Tryane, a couple of hours, using single sign-on through Azure AD or Entra ID, with no agent installed and no change to your SharePoint or Viva Engage configuration. The work that takes real time is not technical. It is agreeing the organisational attribute model, deciding which sites count as communication surfaces, and settling what the team will report each month.
Does this replace our Microsoft 365 investment?
No, and any vendor suggesting it does should be treated carefully. Microsoft 365 remains the publishing estate and continues to record what it records. An analytics layer sits above it, reading those surfaces together and joining them to organisational structure, so you can answer the cross-channel and segmented questions that no single native panel is built to answer.
Sources
• Microsoft Learn, activity reports in the Microsoft 365 admin centre
• Microsoft Learn, Viva Connections overview
• Microsoft Learn, Microsoft Graph reporting API
• Gallagher, State of the Sector
Further reading
• Measuring cross-channel internal communications
• SharePoint analytics in Power BI, and where it breaks
• OneDrive and SharePoint, and what the confusion does to your numbers
• Audience segmentation for internal communications
• Tryane compared with Viva Engage native analytics
Tryane runs a 15-minute working session with Heads of Internal Communication, mapping which Microsoft 365 surfaces you publish to and showing what a single cross-channel reach figure looks like on your own tenant. Book a slot with Jérémy to schedule yours.