Tryane Analytics and Microsoft 365: What the Layer Reads, and What It Does Not Do

By Nicolas Saliba · 8 min read

The question usually comes from IT rather than from communications. The organisation already pays for Microsoft 365 E5. SharePoint reports on itself, Viva Engage reports on itself, Teams reports on itself, and the newsletter platform sends a delivery report every Tuesday. So what exactly is the analytics layer for, and what is it going to touch inside the tenant?

It is a fair question and it deserves a specific answer rather than a positioning statement. This article sets out what an analytics layer over Microsoft 365 reads, what it joins that activity to, what it deliberately does not do, and the situations where you should not buy one at all.

Start with what Microsoft native already gives you

Microsoft native reporting is free, already switched on, and genuinely sufficient for a single team measuring a single surface. Any honest comparison has to start there, because most of the time the native panel is the right answer and nothing needs to change.

Surface	Native reporting	What it answers well	Where it stops
SharePoint	Site usage and page analytics^[1]	Views, unique viewers and time on page for a site or news post	No join to function or site, no view across other channels
Viva Engage	Community and network insights^[2]	Posts, replies, reactions and active members per community	Participation rate against a workforce population
Microsoft Teams	Usage reports in the admin centre^[3]	Tenant-level activity and adoption	Whether a specific announcement reached a specific population
Newsletter platform	Vendor delivery and open reporting	Delivery, opens and clicks for one send	Whether openers also read the intranet version

Each panel is accurate about its own surface. The difficulty is that an internal communication function does not have surface-shaped questions. It has population-shaped questions: did the safety announcement reach plant operators in the three sites affected, on any channel, and how does that compare with the last one.

What the layer reads

Tryane reads communication activity, not work. Specifically, across a Microsoft 365 tenant it consumes:

SharePoint: news posts, pages and communication sites, including the reading depth signals the native panel exposes only per site.
Viva Engage: community posts and replies, storyline posts, and leadership corner activity where it is in use.
Microsoft Teams: posts in the channels you designate as communication channels, typically an all-company channel or a set of business-unit channels. Not private chats.
Newsletters: sends from PoliteMail, ContactMonkey or Microsoft 365 native email, matched to the same audience model as the other channels. The measures worth carrying across are covered in our note on internal newsletter metrics.

Reading these together is the point. A single person who opens the newsletter, skims the SharePoint article and never touches Viva Engage appears in three native panels as three unrelated fragments. Joined, they are one reader with a channel preference, which changes what you publish where. The mechanics of that join are set out in measuring cross-channel internal communications.

What it joins that activity to

Activity on its own produces counts. Counts become findings when they acquire a denominator, and the denominator is your workforce structure: function, business unit, country, site, language, contract type, manager population. In a Microsoft 365 organisation those attributes usually live in Entra ID^[4], or in a scheduled HR extract when the directory is thin.

This is the step that determines whether the whole programme is useful, and it is worth spending real time on before any dashboard is built. An attribute model that distinguishes “Operations” from “Manufacturing France” from “Site 042” will answer questions for years. One that only holds department names copied from an old directory will not. Our guide to audience segmentation for internal communications covers how to structure it.

Reporting is then set to a minimum group size so that no individual is identifiable inside a segment. That threshold is a governance decision, not a technical one, and it is worth agreeing with your works council or data protection officer before the first report circulates.

What the layer deliberately does not do

This section matters more than the feature list, because most of the resistance an IC team meets internally comes from people who assume the answer is yes to all of the following.

It is not employee monitoring. There is no individual productivity score, no presence tracking, no keystroke or application telemetry. Private chats, private channels and one-to-one messages are out of scope. The unit of analysis is a communication and an audience segment, not a person.

It is not an intranet or a publishing tool. Nothing is authored in it, nothing is sent from it, and it does not sit in the path of a publication. If the layer is switched off tomorrow, every message still goes out exactly as before.

It does not replace the engagement survey. Communication data evidences behaviour. Belief, sentiment and felt experience come from asking people, and the two instruments answer different questions.

It does not invent data Microsoft did not record. Where the underlying API is incomplete, the honest response is reconciliation and a visible gap, not an interpolated line. Any vendor whose chart is always smooth is smoothing something.

It does not claim business attribution. A layer can show that the safety message reached 82 per cent of operators, and it cannot tell you that this caused the incident rate to fall. Presenting reach as if it were outcome is the fastest way to lose an executive audience.

The Power BI question

Most teams consider building this themselves against the Microsoft Graph reporting API before they buy anything, and some organisations run that build well. Go in with the real cost in view. The Graph reporting API is not consistently reliable and produces days with missing data^[5]. Customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, which is an uncomfortable conversation to have in front of an executive committee. A dependable build needs a robust ingestion process and scheduled reconciliation against native figures, so budget for the pipeline rather than the dashboard. The specific failure modes are set out in SharePoint analytics in Power BI.

Tryane exposes its data through an API precisely so that a Power BI or Tableau layer remains an option. The argument is not that you should avoid Power BI. It is that the hard part is ingestion and reconciliation rather than visualisation, and that is what you are actually buying.

Deployment and the security review

The practical facts your IT counterpart will ask for: Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency available on request, authenticates through single sign-on with Azure AD or Entra ID, and deploys in a couple of hours. There is no agent to install on any device and no change to how SharePoint, Viva Engage or Teams are configured. Unlimited history is retained, which is the part that matters when a product transition resets a native reporting window. The questions a security review will raise are covered in security and compliance for internal communications analytics.

When not to buy this

Three situations where the honest answer is that you do not need a layer yet. If you run a single community or a single intranet site, the native panel is sufficient and better integrated than anything you would bolt on^[6]. If you have no usable source of organisational attributes and no prospect of one, the segmentation that justifies the layer will not be available, so fix the directory first. And if nobody owns the reporting, a new data source will produce a dashboard that is looked at twice.

Gallagher’s State of the Sector research consistently finds measurement to be the capability internal communicators name as their biggest gap^[7], and tooling only closes part of that. If you are still deciding, the evaluation criteria are set out in how to choose an internal communications analytics tool.

Frequently asked questions

Does Tryane replace SharePoint or Viva Engage analytics?

No. Both continue to record exactly what they record today. The layer sits above them, reading each surface and joining the activity to your organisational structure so that cross-channel and segmented questions can be answered. You keep the Microsoft 365 investment and add what the native panels are not designed to do. The specific differences are covered in our comparisons with SharePoint native analytics and Viva Engage native analytics.

Can it see private Teams chats?

No. One-to-one chats, group chats and private channels are out of scope. What is read is activity in the channels you explicitly designate as communication channels, which in most organisations means an all-company channel and a handful of business-unit channels. The broader picture on Teams measurement is in measuring internal communications on Microsoft Teams.

What does it need from our HR system?

Organisational attributes rather than personal records: function, business unit, country, site, language, contract type and manager population. Many organisations start with Entra ID alone and add a scheduled HR extract later when they need attributes the directory does not carry, such as shift pattern or collective agreement.

How long does deployment take, and what does IT have to do?

A couple of hours in most tenants. IT grants the read permissions, configures single sign-on, and confirms which Teams channels and SharePoint sites are in scope. There is no agent, no code deployed into SharePoint, and no change to publishing workflows.

What happens to our history if Microsoft changes a product again?

That is one of the main reasons the layer exists. Native reporting windows are finite and product transitions reset them, which is what happened to teams reporting on Yammer through the move to Viva Engage. History held in the layer is retained independently, so a multi-year trend survives a change of surface.