What Is SharePoint? The Three Things It Means, and What Each One Lets You Claim

By Nicolas Saliba · Published June 2025, Updated August 2026 · 7 min read

Someone hands you a slide that says “SharePoint: 41,000 monthly active users” and asks whether it can go in the board pack. Your organisation has 38,000 people. The number is larger than the headcount, it came out of a genuine Microsoft report, and nobody in the room can explain the gap. That is the moment most internal communication leaders discover that SharePoint is not one thing, and that the definition is not a technicality. It decides which sentences you are allowed to say out loud.

So this is a definition piece, but not a beginner’s one. It is written for the person who has to defend a number. Microsoft describes SharePoint as a platform for sites, content management and collaboration across Microsoft 365^[1], which is accurate and does almost nothing to help you scope a report.

Three surfaces, one platform

Communication sites, which is what you mean by the intranet

A communication site is built for a small number of authors publishing to a large readership: news posts, pages, a home site, hub navigation. Audience targeting is available, which means a page or a news post can be shown to some populations and not others. When an IC team says “the intranet”, this is nearly always what it means, and it is the only surface where a reach claim survives without heavy qualification. Designating an organisation news site is what gives corporate news its authority in search and in the Viva Connections feed^[2].

Team sites, which are collaboration and not communication

A team site is provisioned behind every Microsoft 365 group and every team in Microsoft Teams. Someone creates a team, a SharePoint site appears. In a 38,000-person group there will be tens of thousands of them, most with a handful of members, and together they generate an enormous volume of activity that has nothing to do with internal communication. That is where the 41,000 came from.

OneDrive, which is personal storage on the same plumbing

OneDrive for Business is per-person storage running on SharePoint technology. Nobody publishes to it, it has no audience, and it should never appear in a communication figure. Microsoft’s planning guidance treats SharePoint and OneDrive as one platform serving two purposes^[3], which is technically true and is precisely why the numbers blend so easily. The specific ways that blending corrupts an intranet figure are worked through in OneDrive and SharePoint. This piece takes the next step: what you are entitled to claim once the surfaces have been separated.

The claim ledger

The useful discipline is to write down, surface by surface, the sentence the data supports and the sentence it does not. Anything on the right-hand side is a hypothesis, and hypotheses do not belong in a board pack.

Surface	What the number is	What you may claim	What you may not claim
Communication site, organisation news	Unique viewers of a page or news post.	That this many distinct people opened this item in this period.	That they read it, understood it, or that those who did not open it were unreached.
Hub of department sites	Per-site usage, owned by each site owner.	Activity within each site, separately.	A group total. Visitors overlap between sites and adding them double counts.
Team sites	Collaboration activity across thousands of groups.	Platform adoption, which is useful to IT.	Anything about internal communication performance.
OneDrive	Personal file activity.	Storage and sync behaviour.	Any communication claim. It should not be in the report at all.
Tenant total^[4]	All of the above added together.	Licence and platform usage.	Intranet reach. This is the number that exceeds headcount.

The row that causes most trouble in practice is the second. A hub with 14 department sites produces 14 usage reports, and the instinct is to sum them into an intranet total. The same person visiting three of those sites appears three times. There is no native way to deduplicate across sites, so the honest version of a cross-site number is that you do not have one. The same problem one level up is why cross-channel totals cannot be added either, which is the subject of why your cross-channel totals do not add up.

One more nuance that cuts the other way. A colleague reading a news post inside the Viva Connections feed on a phone has genuinely consumed your communication site content, even though no browser visit to the intranet took place. Reporting that quietly assumes a desktop visit undercounts exactly the mobile and frontline populations you are most often asked about, and Viva Connections reports separately, as covered in Viva Connections analytics and intranet adoption.

The decisions made before you arrived

Most of what you can measure was fixed by provisioning and architecture choices, usually taken by IT, often years earlier, and almost never with a reporting question in mind. Four matter more than the rest.

Whether corporate news lives on a designated organisation news site. If it does, corporate content is distinguishable from every other page in the tenant and can be reported as a set. If it is scattered across department sites, there is no clean population of corporate content and every reach figure needs manual assembly.

Whether audience targeting is switched on and populated. Targeting is what lets a page be aimed at a population. Without it, everything is published to everyone, and “reach against the intended audience” has no intended audience to measure against.

Whether the hub architecture matches how the organisation works. Hubs that mirror the legal entity structure rather than how people actually work produce navigation nobody follows and analytics nobody can interpret.

Whether anyone owns retention of the data. Native reporting keeps a finite window. If nobody exports on a schedule, the history is simply absent the first time someone asks for a three-year view.

If you are new in post, those four questions are worth asking in your first fortnight, and the answers usually explain why the existing reporting is thin. Gallagher’s State of the Sector research repeatedly finds measurement to be the capability internal communicators name first as their gap^[5]. A meaningful share of that gap was created by decisions taken before the IC team was in the room.

The honest position on native reporting

SharePoint site analytics is free, already switched on, and genuinely sufficient for a site owner who wants to know whether their own pages are being read. If you run one communication site for one audience, use it and spend nothing. Using SharePoint native analytics explains how to read it without fooling yourself, and the limits of SharePoint native analytics covers where it stops.

The structural gaps are three. There is no join to organisational attributes, so no segmentation by function, site, country or contract type without exporting and joining the data yourself. There is no deduplication across sites or channels, so no unique reach. And the retention window is short.

The common answer is a Power BI build on the Microsoft Graph reporting API. It works for some organisations and is more demanding than it looks. The reporting API is not consistently reliable and produces days with missing data^[6]. 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 the native figures and a named owner, so budget for the pipeline rather than the dashboard.

Tryane sits above all of this. It reads SharePoint alongside Viva Engage, Teams and your newsletter platform, joins the activity to your organisational structure through Entra ID or an HR file, resolves the same person across sites and channels, and keeps unlimited history. SOC 2 Type 2 certified, GDPR compliant by design, EU hosting by default with US data residency on request, deploys in a couple of hours over single sign-on, no agent to install.

Frequently asked questions

Is SharePoint an intranet?

SharePoint is the platform an intranet is usually built on, which is not the same thing. Your intranet is the set of communication sites, the home site and the organisation news site. The rest of the estate is collaboration. The distinction is developed in what an intranet actually is.

Why is our SharePoint user count higher than our headcount?

Almost always because the figure is a tenant total that includes team sites and OneDrive, because it counts across a period rather than distinct people at a point in time, or because it includes external guests and service accounts. It is a valid platform metric. It is not an intranet reach figure.

What is the difference between a communication site and a team site?

Intent and audience. A communication site is a small number of authors publishing to a large readership, with audience targeting available. A team site is a working space for a group, provisioned automatically behind every Microsoft 365 group and every team. Only the first belongs in communication reporting.

Does SharePoint Premium change what we can measure?

It adds content processing and management capability rather than a new communication analytics surface. Useful for content operations, not a substitute for reach measurement. What it does and does not change is covered in SharePoint Premium for internal communications.

Can I report a single intranet reach figure across all our sites?

Not from native reporting, because there is no deduplication across sites. You can report per site, or you can compute a genuine unique reach with a layer that resolves the same person across sites and channels. Adding site totals together produces a number that is confidently wrong.