Someone senior asks how the intranet is performing. Before you can answer, you have to decide what you mean by the intranet, and that decision is not neutral. If you mean the SharePoint communication sites your team publishes to, you will report one number. If you mean every place an employee meets official internal information inside Microsoft 365, including the Viva Connections feed, the Teams tab a manager pinned and the weekly newsletter that links back, you will report a different one. Both are defensible. Only one of them matches what the person asking has in mind, and the distance between the two is where most intranet reporting quietly loses credibility.
So this is a definition with a practical purpose: what an intranet is, what it has become inside Microsoft 365, and how the boundary you draw around it determines what you are entitled to claim on the monthly slide.
The working definition
An intranet is a private network of resources, authenticated and scoped to a single organisation, that exists to do three jobs: publish, find and transact. Everything else is implementation detail.
Publish covers news, leadership messages, campaign pages and the editorial calendar. Find covers policies, procedures, forms, org charts and the document estate. Transact covers the things an employee comes to do rather than read: request equipment, book leave, submit an expense claim, complete a mandatory training module.
That split matters more than the usual feature list, because only the first job belongs to internal communication. The second is shared with HR, legal and IT. The third belongs to whichever function owns the process. Most intranet reporting mixes all three into one traffic figure, which is why intranet numbers so often look healthy while the communication team cannot prove a single message landed. A payroll portal generating 40,000 sessions in January tells you people were paid, not that anyone read the CEO update.
Two adjacent terms are worth separating once. An extranet extends selected resources to people outside the organisation under a different trust model, a boundary we cover in our note on intranet versus extranet. A digital workplace is the broader category that includes the intranet plus collaboration, meetings and business applications. The intranet is a component of the digital workplace, not a synonym for it.
The modern intranet is not one website
In a Microsoft 365 organisation, the intranet in 2026 is a set of connected surfaces rather than a destination. Microsoft’s own architecture guidance describes a home site, a set of hub sites and communication sites beneath them, with news flowing across the structure rather than living in one place[1]. Organisation news sites give designated sites the authority to publish news that surfaces across the tenant[2].
On top of that sits Viva Connections, which delivers the same content inside Microsoft Teams on desktop and mobile through a feed and a dashboard[3]. Then there is enterprise search, which is how a large share of employees actually reach intranet content, and the internal newsletter, which for many populations is the only surface they ever see.
The consequence is easy to picture. A production supervisor in Valenciennes may go a full quarter without opening a browser tab on a SharePoint page. She reads the safety brief in the Viva Connections feed on a shared tablet, gets the restructuring note forwarded by her manager, and sees the CEO video because someone played it on the line. Every one of those is the intranet doing its job, and none of them shows up as a page view on the site your team owns. If your definition stops at SharePoint site analytics, she is invisible to you, and she is exactly the person the board wants reassurance about.
Why the boundary decides what you can claim
Once you accept that the intranet is a set of surfaces, the reporting problem becomes a denominator problem. Almost every intranet claim takes the form of a percentage, and a percentage is only as honest as the population underneath it.
| Denominator you choose | What it contains | What a percentage then means | Where it breaks |
|---|---|---|---|
| Total headcount | Everyone on the payroll, including people with no account | True organisational reach | Guarantees a low number and invites an argument about fairness |
| Entra ID accounts | Everyone with an identity, including service and shared accounts | Reach of the addressable population | A shared shop-floor account is many people or none |
| Licensed Microsoft 365 users | People who could technically open the page | Reach of the licensed population | Excludes deskless staff by design, which flatters the figure |
| Users active in Microsoft 365 in the period | People who did something in the tenant | Reach among people already present | Circular: the least reachable are removed before you measure |
| Members of the targeted audience group | The population the message was written for | Reach of the intended audience | Only works if audience groups are maintained, an HR data question |
None of these is right in the abstract. The failure is not choosing one, or choosing a different one each quarter. A team that reports “78 per cent of the intranet audience saw the announcement” without saying which of those five populations it means has produced a number that cannot be checked and therefore cannot be defended. Gallagher’s State of the Sector research keeps finding measurement at the top of the capability gaps internal communicators name[4], and much of that gap is definitional rather than technical.
What SharePoint native reports about the intranet
SharePoint site usage reporting is per site. It gives you views, unique viewers, average time spent and popular content for a site collection, over a retained window[5]. That is genuinely useful, it is free, it is already switched on, and for a single site owner asking whether their pages are being read it is sufficient. Do not build anything if that is the question you have.
The limits are structural rather than a matter of Microsoft doing a poor job. Reporting is attached to sites and pages, not to people and segments, so there is no native way to say what proportion of the finance function in Germany saw a given post. Hub sites do not roll usage up across the estate the way the information architecture might suggest. The retained window is finite. And intranet numbers sit apart from Viva Engage and newsletter numbers, so cross-channel reach is out of reach by construction. Our guide to SharePoint native analytics sets out what each report contains.
Teams often try to close the gap with a Power BI build on the Microsoft Graph reporting API[6]. It can work, but be clear about what you are taking on. The reporting API is not consistently reliable and produces days with missing data. Customers have shown us Power BI dashboards returning KPI values 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, so budget for the pipeline rather than the dashboard.
A definition you can put on the first slide
The fix is unglamorous. Write the definition down, agree it once, repeat it every time you report. Three scopes are enough.
- Channel scope. Which surfaces count as the intranet here: named SharePoint hubs, the Viva Connections feed and dashboard, the internal newsletter, and whether Viva Engage is in or out.
- Population scope. Which of the five denominators above is the base, in plain words, with the number written next to it.
- Time scope. The window, and how you handle the reset that happens when a site is redesigned and URLs change.
Worked example: “Intranet reach here means unique readers of organisation news across the four corporate hubs and the Viva Connections feed, as a proportion of the 31,400 people with an Entra ID account, over a rolling 28 days.” That sentence is boring, and it is the reason the rest of the deck holds. Once it is fixed, the interesting questions become answerable, and our note on which intranet metrics actually matter takes the next step.
Where a measurement layer fits
This is the layer Tryane occupies. It reads SharePoint alongside Viva Engage, Teams and your newsletter platform, joins that activity to your organisational structure through Entra ID or an HR file so segment questions become answerable, and keeps history across product transitions and site redesigns so the trend line does not restart every time the intranet does. The definitional work above is still yours. What the platform removes is the manual export and join that makes most teams abandon the segmented version of the question. If you are setting those attributes up for the first time, our piece on audience segmentation for internal communications covers how to structure them, and the note on cross-channel measurement deals with the double-counting problem you hit as soon as more than one surface is in scope.
On the procurement points that usually come up: Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, deploys in a couple of hours using single sign-on through Azure AD or Entra ID, keeps unlimited history, and installs no agent on any device.
Frequently asked questions
What is the difference between an intranet and a digital workplace?
The intranet is the private space for publishing, finding and transacting on organisational information. The digital workplace is the wider environment that includes the intranet plus collaboration, meetings, business applications and devices. In Microsoft 365 terms, the intranet is largely SharePoint and Viva Connections, while the digital workplace also takes in Teams, Outlook, Viva Engage and line of business tools.
Is SharePoint an intranet?
SharePoint is the platform most organisations build an intranet on, not the intranet itself. The intranet is the arrangement of home site, hubs, communication sites, news and navigation you design on top of it, plus the surfaces such as Viva Connections that deliver it. If you say “the intranet” and mean one site collection, your reporting will understate what employees actually received.
Does Viva Connections count as part of the intranet?
Yes, and leaving it out is a common reporting error. Viva Connections surfaces intranet content inside Microsoft Teams on desktop and mobile, which for frontline and deskless populations is often the only place they meet it. If your definition of the intranet is browser-based, you have excluded the audience you are most often asked about.
What is the difference between an intranet and an extranet?
Access and trust model. An intranet is scoped to people inside the organisation and authenticated against your own directory. An extranet extends a controlled subset of resources to external parties such as suppliers or distributors, usually through guest access or a separate portal. Combining the two in one reporting view produces reach percentages that are hard to interpret, because the population is not one workforce.
How do I choose the right denominator for intranet reach?
Choose the population the message was written for rather than the one that flatters the number, and state it next to the percentage. For an all-staff announcement, headcount or Entra ID accounts is the honest base. For a targeted campaign, the audience group is. What to avoid is switching between them without saying so, because that turns a reporting discussion into an argument about the data.
Sources
• Microsoft Learn, plan an intranet with SharePoint in Microsoft 365
• Microsoft Learn, Viva Connections overview
• Microsoft Learn, portal health and site usage
• Gallagher, State of the Sector
Further reading
• Which intranet metrics matter to communications
• A guide to SharePoint native analytics
• Viva Connections analytics and intranet adoption
• Measuring cross-channel internal communications
• What SharePoint is, a complete guide for internal communication
Tryane runs a 15-minute working session with Heads of Internal Communication that starts with the definition question: which surfaces count as your intranet, which population is your denominator, and what your current numbers look like once both are fixed. Book a slot with Jérémy.