OneDrive and SharePoint: Why the Confusion Corrupts Your Intranet Numbers

By Nicolas Saliba · 8 min read

Here is a conversation that happens in a quarterly review at least once in the life of every internal communication team. The team reports that SharePoint activity is up 22 per cent on the quarter. Someone from IT, being helpful, points out that the finance function migrated a shared drive in February and that most of the increase is people opening spreadsheets. The number was accurate. It was also about document storage, not about anybody reading anything the communication team published. Once that has happened in front of a CFO, the intranet number carries an asterisk for a year.

Why the two get confused in the first place

The confusion is not carelessness. It is architectural. OneDrive for Business is not a separate product sitting next to SharePoint. It is a personal SharePoint site collection, provisioned per user, hosted on a separate domain in your tenant that ends in -my.sharepoint.com^[1]. Same storage engine, same permission model, same sync client, different purpose. When a colleague says “it is in SharePoint”, they may mean the intranet, a team’s document library, or a file in their own OneDrive, and all three statements are technically true.

Microsoft is clearer about this than most organisations are. The admin centre carries a SharePoint site usage report and a separate OneDrive usage report, and they do not double-count each other^[2]. The trouble starts one level up, in how the numbers get talked about and how custom reporting gets built.

“SharePoint” is three different things and only one is the intranet

For an internal communication team, the useful distinction is not OneDrive against SharePoint. It is between three surfaces that all run on SharePoint and are measured as though they were one.

Communication sites, hub sites and news posts. This is the intranet. Content is published by a small number of people and read by many. It is the only one of the three where readership means what an internal communicator wants it to mean.

Team site document libraries. Every Microsoft Team provisions a SharePoint site behind it. A file opened in a Teams channel is SharePoint file activity. In most tenants this is by far the largest source of SharePoint numbers, and none of it is communication.

OneDrive for Business. Personal storage. Reported separately by Microsoft, but frequently reabsorbed into “SharePoint” in a custom dashboard, in a slide title, or in a sentence spoken aloud in a meeting.

An intranet engagement figure that has not been explicitly scoped to the first of these three is not wrong so much as meaningless. It moves when a department migrates a file share, when a large project spins up, or when a team turns on sync. None of those events tell you anything about whether your CEO message landed.

	OneDrive for Business	SharePoint team site library	SharePoint communication site
What it is for	One person’s working files	A team’s shared documents	Publishing to an audience
Who owns it	The individual	The team or group owner	Internal communication
Typical action	Save, sync, share a link	Co-author, version, comment	Read a news post or page
Host	tenant-my.sharepoint.com	tenant.sharepoint.com	tenant.sharepoint.com
Site template	SPSPERS	GROUP#0 or STS#0	SITEPAGEPUBLISHING#0
Belongs in the IC number	No	No	Yes
Native report	OneDrive usage	SharePoint site usage	SharePoint site usage and page analytics

Where the blending actually enters your reporting

Four specific places, in rough order of how often we see them.

The Power BI build that pulls site collections without filtering. A custom report against the Microsoft Graph reporting API returns site-level rows, and personal sites are available through the same family of endpoints. A build that enumerates site collections and sums activity will include personal sites unless somebody deliberately excludes the -my host^[3]. This is the most common single cause of an intranet figure nobody can defend.

Counting file activity as engagement. File views and edits are the most abundant SharePoint signal, which makes them tempting. They are also almost entirely produced by collaboration rather than communication. If your intranet KPI moves with file activity, you are reporting on how busy the organisation is, not on how well it is informed.

Counting users rather than readers. A tenant “SharePoint active user” is anyone who touched any file anywhere. That population is close to your entire headcount and it never moves much, which is why it looks reassuringly stable and tells you nothing.

Site sprawl in the denominator. Large tenants accumulate thousands of sites. If your reporting scope is “all sites”, the intranet is a rounding error inside it, and any genuine improvement in intranet readership disappears into the noise. Our note on which intranet metrics matter to communications works through what to keep in scope.

Scoping the number so it survives a follow-up question

The fix is not a tool. It is a definition, agreed once with IT and then held.

Exclude the personal host. Everything on -my.sharepoint.com is out of the internal communication scope, permanently. It is a legitimate IT metric and an irrelevant communication one.
Scope to the publishing surface by site template. Communication sites, your hub, and any team sites you genuinely use for news. Everything else is out. Write the list down and review it twice a year, because sites get created constantly.
Measure news posts, not pages. A news post is a published communication with a date and an author. A page can be a landing page nobody chose to read. Reporting news post reach separately from general site traffic changes the conversation with executives more than any other single adjustment.
Define a reader, not a user. A unique person who opened a published news item, once, in the period. Not sessions, not views, not file touches.
Segment by organisational attribute. Reach means nothing as a tenant total. It means something as “64 per cent of the commercial function and 11 per cent of manufacturing”, which is a sentence that produces a decision. Our guide to audience segmentation for internal communications covers how to structure the attributes before you start.

If you have just been through an intranet rebuild, do this before you report anything, because a redesign changes site structure and any comparison across it is invalid unless the scope definition is stable. The piece on measuring after a SharePoint redesign covers the sequencing.

What native reporting does and does not give you

SharePoint site analytics is free, already switched on, and genuinely sufficient for a site owner who wants to know whether traffic to their site went up. If that is your question, use it and buy nothing. The admin centre reports are similarly adequate for tenant-level health monitoring, which is what they were built for.

The constraints are structural. Native reporting is scoped per site, so a campaign that ran across the hub, three country sites and a newsletter cannot be counted once. It holds no organisational attributes, so the segmentation above is not available without joining to Entra ID or an HR file yourself. And it retains a finite window, which makes year-on-year comparison awkward exactly when you need it. Those limits are set out in more detail in our piece on the limits of SharePoint analytics.

Teams frequently try to close the gap with Power BI on the Graph reporting API. That can work and some organisations run it well. Three things are worth knowing first: 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 therefore needs a robust ingestion process with retry, a scheduled reconciliation against the native figures, and a named owner for both. Budget for the pipeline rather than the dashboard. Our longer treatment of SharePoint analytics in Power BI goes through the failure modes.

Tryane sits above this. It reads SharePoint alongside Viva Engage, Teams and your newsletter platform, applies the scope definition once so personal storage and project file churn stay out of the communication figure, joins the result to organisational structure through Entra ID or an HR file, and keeps unlimited history. 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.

Frequently asked questions

Is OneDrive for Business part of SharePoint?

Technically yes. It is a personal site collection running on the same platform, hosted on the -my.sharepoint.com domain in your tenant. Commercially and in everyday conversation it is treated as a separate product, which is precisely why reporting gets muddled.

Does the Microsoft 365 admin centre already separate them?

Yes. The SharePoint site usage report and the OneDrive usage report are distinct and do not double-count. The blending happens in custom builds that enumerate site collections without excluding personal sites, and in the way figures get described once they leave the admin centre.

Should Teams file activity count towards intranet engagement?

No. Every Team is backed by a SharePoint site, so Teams file activity appears as SharePoint activity, but it is collaboration rather than communication. Measure Teams as a communication channel through channel posts and announcements you actually published, not through the document library behind it.

What should we report instead of SharePoint page views?

Reach on published news items, expressed as a percentage of a defined population, alongside a small number of quality measures such as read completion and return rate. A single reach percentage with a named denominator survives executive questioning far better than a large view count with no denominator at all.

Can Tryane exclude OneDrive automatically?

Yes. The communication scope is defined at setup, personal sites are excluded, and you choose which sites count as publishing surfaces. That definition then applies consistently across periods, which is what makes a trend comparable when the site estate changes underneath it.