An internal communication team moves the weekly leadership update out of the newsletter and into a Teams channel, on the reasonable grounds that this is where people already are. Engagement looks lively. Six months later the CCO asks a plain question about last Thursday’s post: how many people saw it? The team opens Teams, then the Teams admin centre, then the Microsoft 365 usage reports, and discovers there is no answer. Not a disappointing answer. No answer.
This is the trade Teams makes, and it is worth understanding before you move a flagship channel into it. Teams is the best surface in Microsoft 365 for communication that needs a response from a bounded group. It is the weakest for communication you will later have to prove landed.
What Teams is genuinely good at in internal communication
Teams earns its place for one specific job: communication to a group small enough to have a conversation, where the point is the conversation. A site director posting shift changes into a team of 80 operations staff who then ask three clarifying questions is Teams working exactly as designed. The message arrives in the tool people already have open, the questions are visible to everyone, and the answer only has to be given once.
It is also the natural home for the manager cascade. When the corporate message needs local translation, a people-manager posting into their own team channel adds context that no central publication can. That local layer is the part most internal communication functions are weakest at, and Teams gives it somewhere to live[1].
Third, it reaches people who never open the intranet. In distributed operations, frontline populations often have Teams on a shared device and nothing else. Our piece on measuring frontline worker communications covers that population in detail.
The metric Teams does not have
Here is the gap, stated precisely. A SharePoint news page has unique viewers. A newsletter has opens and clicks. A Viva Engage post has views and reactions inside a community with a known membership. A Teams channel post has none of that in any exportable form.
What exists is real but sits at the wrong level. Per-team analytics in the Teams client shows active users, posts and replies over a period, which describes the health of the team rather than the reach of a message[2]. The Teams usage reports in the Microsoft 365 admin centre aggregate activity across the tenant, again by user and by team, not by post[3]. Neither answers the CCO’s question.
The seen-by indicator that appears on some channel posts is not a substitute. It is only present in smaller teams, it is a live client-side display rather than a reported figure, and there is no export path to a monthly report. Reactions are worse: they measure the enthusiasm of a handful of people, and in a channel of 400 they are consistent with almost any level of readership.
| Channel | Reach evidence available | Segmentable natively | Reportable historically |
|---|---|---|---|
| SharePoint news page | Unique viewers, views over time | No | Within the retention window |
| Newsletter | Delivery, opens, clicks | By list, not by attribute | Yes, in the sending platform |
| Viva Engage post | Views and reactions inside a known community | No | Within the retention window |
| Teams channel post | None at post level | No | No |
The consequence is not academic. Gallagher’s State of the Sector research keeps finding channel proliferation and measurement at the top of the profession’s concerns, and the two are connected: every channel added without a reach measure makes the aggregate picture less complete rather than more[4]. Teams is the channel most often added without anyone first checking what it reports.
Four ways to measure Teams as a communication channel anyway
Instrument the destination, not the post
The most reliable technique is to stop trying to measure the post. Put the substance on a SharePoint page and use the Teams post as the distribution mechanism, with a tracked link. You then measure the page, which does have viewer data, and you inherit whatever segmentation your analytics layer provides. Our walkthrough of SharePoint native analytics covers what that page-level data does and does not include.
Measure the cascade, not the broadcast
For manager cascades, the meaningful measure is not readership but whether the cascade happened at all. Track the share of team channels in which a manager posted the local version within the agreed window. In a 12,000-person group with 900 people-managers, knowing that 61 per cent posted and that the gap is concentrated in two regions is a directly actionable finding, and it is a measure of your operating model rather than of a piece of content.
Use team-level activity as a liveness signal
Per-team activity data answers a narrower question well: is this channel alive or has it been abandoned? A communication channel with no posts for six weeks and three active users is not a channel, and a channel map that quietly lists forty of these is a finding worth presenting.
Deduplicate people across channels
A person reached by the intranet, the newsletter and a Teams post counts three times in per-channel reporting, and a person reached by none of them does not appear at all. Cross-channel deduplication against a workforce population is the only way to answer the question executives actually ask, which is what share of the organisation we reached. That method is set out in our piece on cross-channel measurement, and the four questions a number can answer are in our guide to internal communication analytics.
The honest position on native Teams reporting
Teams reporting is free, already switched on, and correct for what it was built to do. Microsoft built it for adoption and administration, not for editorial measurement, and it does the adoption job well. If your question is whether Teams is being used across the organisation, the native reports answer it without help.
The limits appear at the editorial question. There is no post-level reach, no join to organisational attributes such as function, country, site or contract type, and no continuity when a team is renamed, archived or reorganised. That last point catches people out, because a channel reorganisation can remove the history you were using as a baseline.
Teams sometimes try to close this with a Power BI build against the Microsoft Graph reporting API. That can work, and it is more demanding than it looks. 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. A dependable build needs a robust ingestion process and scheduled reconciliation against native figures, so budget for the pipeline rather than the dashboard.
Tryane sits above all of this. It reads Teams alongside SharePoint, Viva Engage and your newsletter platform, joins that activity to your organisational structure through Entra ID or an HR file, and keeps history across renames and migrations. Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, and deploys in a couple of hours over single sign-on with Entra ID, with no agent to install. For a like-for-like view of the two conversational surfaces, see Teams compared with Viva Engage.
A channel policy that keeps Teams in its lane
The practical conclusion is a rule, not a tool. Use Teams for communication to a bounded group where a response is wanted and where you will never need to defend reach: shift information, local manager cascade, project updates, questions after a town hall. Keep anything you will be asked to prove on a surface that records readership, and use Teams to drive traffic to it. Detailed instrumentation options are in our note on measuring internal communications in Microsoft Teams.
Frequently asked questions
Can I see how many people read a Teams channel post?
Not as a reportable figure. Some channel posts display a seen-by indicator in smaller teams, but it is a client-side display rather than a metric, it does not exist across all team sizes, and there is no export to a monthly report. If readership of a specific message matters, publish the substance on a SharePoint page and use the Teams post to point at it.
Should we move our main internal communication channel to Teams?
Only if you accept that you will not be able to evidence reach on it. Teams is a strong choice for conversation and cascade, and a weak one for flagship communications that appear in a board report. Most organisations that measure well end up with the substance on SharePoint, distribution through Teams and the newsletter, and community discussion in Viva Engage.
What is the difference between Teams and Viva Engage for internal communication?
Teams is for bounded groups who work together, Viva Engage is for open communities across the organisation. The measurement difference matters as much as the cultural one: a Viva Engage post has views and reactions inside a community with known membership, and a Teams channel post has no equivalent record.
Does Microsoft Copilot change what we can measure in Teams?
Not at the reach level. Copilot summarises and drafts inside the conversation, which changes how people work with content rather than what the platform records about who saw it. The measurement gap described here is a reporting design decision, not a capability that an assistant fills in.
Does Tryane replace the Teams admin reports?
No. Teams keeps recording what it records, and the admin reports remain the right source for adoption and administration questions. Tryane reads Teams together with your other channels and joins the result to your organisational structure, so you can answer reach and segmentation questions that no single native report covers.
Sources
• Microsoft Learn, overview of teams and channels
• Microsoft Learn, view analytics for teams and channels
• Microsoft Learn, Microsoft Teams usage activity report
• Gallagher, State of the Sector
Further reading
• Measuring internal communications in Microsoft Teams
• Teams compared with Viva Engage
• Measuring cross-channel internal communications
• Measuring frontline worker communications
• A guide to internal communication analytics
Tryane runs a 15-minute working session with Heads of Internal Communication: bring your channel map and we will show which of your Teams channels can be evidenced today and which cannot, on your own tenant. Book a slot with Jérémy.