The CIO says the digital workplace programme will deliver connected insight in the next release. The Head of Internal Communication, who has heard this before, asks a more useful question: connected how, exactly? Because “connected” is doing an enormous amount of work in that sentence, and the answer determines whether the internal communication team gets a reporting capability or another dashboard that nobody can reconcile.
Connecting a Microsoft 365 digital workplace to a measurement layer is not a switch. It is three separate joins, done in a specific order, each of which fails in a specific way. Most programmes complete the first, skip the second, and discover the third only when someone asks for a three-year trend. Here is what each one involves and what it buys you.
Join one: the same person across four surfaces
Your intranet lives in SharePoint. Your enterprise social network lives in Viva Engage. Your team-level conversation lives in Teams. Your newsletter lives in a mail platform. Each of these records activity, and each records it against its own notion of a user.
The first join resolves those into one person. It sounds trivial in a tenant where everyone has a single Entra ID identity, and in a clean tenant it very nearly is[1]. In a real one, it is where the first surprises appear. Shared accounts on shop-floor terminals, contractors in a separate tenant, people who kept two accounts after an acquisition, service accounts posting on behalf of leaders, and the population that reads the newsletter on a personal device with no corporate identity at all.
What this join buys you is deduplication. Without it, a person who saw a message on the intranet, in a community and in the newsletter is counted three times, and your reach number is a sum of overlapping audiences that nobody can interpret. Cross-channel measurement is impossible until this is done, which is why our note on cross-channel measurement starts here rather than with the reporting.
Join two: activity to organisational structure
This is the one that matters most and the one most often deferred. Knowing that 4,100 people read something is not useful. Knowing which 4,100, expressed in the language your executive committee already uses, is the whole point.
Practically, it means attaching organisational attributes to each identity: function, business unit, country, site, language, grade, contract type, manager chain. Some of these live in Entra ID and are reliable. Others live only in the HR system and arrive as a file on a schedule. The quality question is unavoidable, and it is worth being blunt about it, because it is the single largest cause of a measurement programme stalling after the technical work is finished.
What actually goes wrong with attributes
Cost centres that have not been updated since a reorganisation. Country fields populated with the legal entity rather than the place of work, so a Belgian plant reports as French. Job families with 340 distinct values, of which 200 have fewer than five people. Group membership that decays over time, which Microsoft’s own guidance on group lifecycle treats as a governance problem rather than an edge case[2].
None of these are fatal, and none of them are the analytics vendor’s fault or the IT team’s fault. They are what happens to an organisational data model over ten years. The realistic approach is to pick five or six attributes you will actually report on, agree who owns their quality, and refuse to segment on the rest until they are fixed. The piece on audience segmentation covers how to choose them.
Join three: time
The third join is the one nobody asks about at the start and everybody asks about eventually. Can this thing show me a trend that spans the Yammer to Viva Engage transition, the intranet redesign, the tenant merger after the acquisition, and the year we changed newsletter platforms?
Native tooling does not promise this and should not be criticised for it. Retention windows are finite by design, product transitions reset counters, and a tenant migration is a discontinuity in every native report you own. If your measurement layer holds its own history independently, the trend survives. If it queries the native APIs live each time, the trend is only as long as the shortest retention window in the chain.
| The join | What breaks without it | The question it unlocks |
|---|---|---|
| Identity across surfaces | Reach is a sum of overlapping audiences | How many distinct people did this campaign reach? |
| Activity to organisational structure | Numbers are true and unusable | Did it land in manufacturing, or only at head office? |
| History across product change | Every migration restarts the trend at zero | Is the three-year programme working? |
The honest case for staying native
SharePoint site analytics, Viva Engage community insights, Teams reporting and Viva Connections adoption reporting are free, already switched on, and genuinely sufficient for a single team or a single community[3]. A community manager who wants to know whether last week’s post did better than the one before does not need an integration project. If that is the whole question in your organisation, stop here.
The native tooling stops at exactly the three joins above. It does not resolve identity across products for reporting purposes, it does not join to HR attributes, and it does not hold history across transitions. Those are architectural boundaries rather than gaps someone forgot to fill, and pretending otherwise leads to disappointment. Our comparison of digital workplace analytics approaches sets out where each option sits.
The common third path is a Power BI build over the Microsoft Graph reporting API. It can work. It is also where most of these programmes lose a year. 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, which is a difficult conversation to have in front of an executive committee. A dependable build needs a robust ingestion process, scheduled reconciliation against native figures, and a named owner who is still there in eighteen months. Budget for the pipeline rather than the dashboard. The detail is in our note on SharePoint analytics in Power BI.
What the integration actually costs in effort
The technical connection is not the expensive part. Tryane deploys in a couple of hours using single sign-on through Azure AD or Entra ID, installs no agent, and changes nothing in your SharePoint or Viva Engage configuration. It is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency available on request.
The effort goes into join two, and it is organisational rather than technical: agreeing which attributes you will report on, who owns their accuracy, and how often the HR file refreshes. Teams that treat this as a data-quality workstream with a named owner finish it in weeks. Teams that treat it as a configuration step discover it in month four, in front of an audience. Gallagher’s State of the Sector research consistently identifies measurement as the capability internal communicators name first as missing[4], and a good share of that gap is this specific piece of unglamorous work. If you are building the wider plan, our measurement strategy guide puts the joins in sequence with everything else.
Frequently asked questions
What does a connected digital workplace mean in practice?
It means activity from your intranet, enterprise social network, team conversations and newsletter can be read as one dataset, attributed to one person, described in your own organisational language, and compared over time. If a proposal does not do all four, ask which of the four it does, because the missing one determines which questions you will not be able to answer.
Do we need an HR file, or is Entra ID enough?
Entra ID is enough for identity and often enough for country and department. It is rarely enough for the attributes internal communication actually wants to segment on, such as contract type, shift pattern, site or job family. Most organisations use Entra ID as the identity spine and a scheduled HR extract for the richer attributes.
How long does the integration take?
The technical connection takes hours. Agreeing the attribute model, its owner and its refresh cadence takes weeks in most organisations, and that is the realistic timeline to communicate upward. Programmes that quote the technical number to their sponsor create an expectation gap that is uncomfortable to close later.
Will this survive a tenant migration or an acquisition?
Only if the measurement layer holds its own history rather than querying native APIs live. A migration resets native reporting, and the trend you spent three years building disappears with it. This is the single most common reason organisations regret deferring join three.
Does this replace our Microsoft 365 analytics?
No. SharePoint, Viva Engage and Teams continue to record what they record, and their native panels remain the right tool for single-surface questions. Tryane sits above them, performing the three joins so cross-channel, segmented and longitudinal questions become answerable. You keep the Microsoft 365 investment and add the layer for what native does not do.
Sources
• Microsoft Learn, what is Microsoft Entra ID
• Microsoft Learn, group lifecycle management
• Microsoft Learn, Viva Connections overview
• Gallagher, State of the Sector
Further reading
• Digital workplace analytics, compared
• Measuring cross-channel internal communications
• Audience segmentation for internal communications
• Building an internal communications measurement strategy
• Viva Connections analytics and intranet adoption
Tryane runs a 15-minute working session with Heads of Internal Communication, going through which of the three joins your current setup has completed and which questions that leaves open. Book a slot with Jérémy to schedule yours.