Microsoft plans to split Teams event attendance and engagement reporting from the policy that currently governs the same reports for ordinary meetings. The change, listed as Microsoft 365 Roadmap item 567466, is in development for worldwide standard multi-tenant tenants and is targeted for general availability in August 2026.
Today, the
The new policy is intended to remove that all-or-nothing choice. Per Microsoft’s roadmap entry, admins will be able to allow organizers to view attendance and engagement reports for Teams events while restricting those reports for Teams meetings.
Attendance reports can contain more than a headcount. Depending on the configuration, Teams records attendee identity, join and leave times, duration, and engagement activity. Microsoft’s Teams documentation says engagement data can include aggregate actions such as reactions and interactions during an event or meeting.
That data is often useful to communications, training, HR, and marketing teams running webinars or town halls. It can be less appropriate for routine internal meetings, where organizations may have stricter privacy expectations or a simple policy against attendance tracking.
The coming separation should let admins keep a tighter default for meetings while retaining reporting for managed event programs. It also better reflects the difference between a small team call and a scheduled, organizer-led event designed to measure audience participation.
Microsoft’s current documentation says the existing attendance and engagement setting can be configured to disable reports, enforce them, allow organizers to switch them off, or limit reports to attendee identity only. That behavior currently covers meetings and events together.
Admins should also check internal retention, privacy, and disclosure practices before enabling broader event reporting. Microsoft’s roadmap dates are estimates and the company notes that roadmap features can be changed, delayed, or removed before release.
Once the rollout arrives, organizations will need to update their event-policy design separately from their existing meeting-report configuration.
Today, the
CsTeamsMeetingPolicy setting for attendance and engagement reports applies across meetings and events. That means an organization that wants webinar or town hall organizers to access post-event attendance data must also permit comparable reporting for the users’ regular Teams meetings.The new policy is intended to remove that all-or-nothing choice. Per Microsoft’s roadmap entry, admins will be able to allow organizers to view attendance and engagement reports for Teams events while restricting those reports for Teams meetings.
Why the split matters
Attendance reports can contain more than a headcount. Depending on the configuration, Teams records attendee identity, join and leave times, duration, and engagement activity. Microsoft’s Teams documentation says engagement data can include aggregate actions such as reactions and interactions during an event or meeting.That data is often useful to communications, training, HR, and marketing teams running webinars or town halls. It can be less appropriate for routine internal meetings, where organizations may have stricter privacy expectations or a simple policy against attendance tracking.
The coming separation should let admins keep a tighter default for meetings while retaining reporting for managed event programs. It also better reflects the difference between a small team call and a scheduled, organizer-led event designed to measure audience participation.
What admins should do
No immediate configuration action is available while the feature remains in development. Teams administrators should instead review existingCsTeamsMeetingPolicy assignments and identify groups that need event reporting but should not receive meeting-report access.Microsoft’s current documentation says the existing attendance and engagement setting can be configured to disable reports, enforce them, allow organizers to switch them off, or limit reports to attendee identity only. That behavior currently covers meetings and events together.
Admins should also check internal retention, privacy, and disclosure practices before enabling broader event reporting. Microsoft’s roadmap dates are estimates and the company notes that roadmap features can be changed, delayed, or removed before release.
Once the rollout arrives, organizations will need to update their event-policy design separately from their existing meeting-report configuration.
References
- Primary source: Microsoft 365 Roadmap
Published: 2026-07-14T22:41:38.6349466Z
Microsoft 365 Roadmap | Microsoft 365
The Microsoft 365 Roadmap lists updates that are currently planned for applicable subscribers. Check here for more information on the status of new features and updates.www.microsoft.com
- Official source: learn.microsoft.com
Get-CsTeamsMeetingPolicy (MicrosoftTeams) | Microsoft Learn
The CsTeamsMeetingPolicy cmdlets enable administrators to control the type of meetings that users can create or the features that they can access while in a meeting. It also helps determine how meetings deal with anonymous or external users Teams Meeting policies can be configured at the global...learn.microsoft.com
