Microsoft Teams to Offer Split Attendance Reporting: Event Analytics Without Meeting Tracking in 2026

Microsoft is set to give Teams administrators granular control over attendance and engagement reporting, decoupling the feature for events like webinars and town halls from ordinary meetings. The change, slated for general availability in August 2026, will let IT decision-makers permit rich post-event analytics while restricting data collection from daily team calls. The move, tracked under Microsoft 365 Roadmap item 567466, ends the current all-or-nothing approach that ties meeting and event reporting together in a single policy setting.

What’s Actually Changing in Teams Attendance Reporting

Today, a single PowerShell parameter—-AllowEngagementReport in the CsTeamsMeetingPolicy—controls whether attendance and engagement reports are generated for both regular meetings and events. That means if an organization wants to collect data for a public webinar, it must also allow the same level of reporting for every impromptu team huddle. The new policy will split this setting into two separate controls: one for events and one for meetings.

According to the roadmap entry, administrators will be able to “allow organizers to view attendance and engagement reports for Teams events while restricting those reports for Teams meetings.” In practice, this will likely manifest as two distinct toggles in the Teams admin center and corresponding PowerShell parameters. Microsoft has not yet published the final configuration syntax, but the intent is clear.

What’s in an Engagement Report?

Attendance reports can contain more than a headcount. Depending on the current policy configuration, Teams records:
- Attendee identity (names, email addresses)
- Join and leave times
- Duration of attendance
- Aggregate engagement actions (reactions, hand raises, chat messages) during the session

This data is often useful for communications, training, HR, and marketing teams running webinars or town halls. For routine internal meetings, however, such tracking may be excessive or even unwelcome. The coming separation should let admins keep a tighter default for meetings while retaining reporting for managed event programs.

What It Means for You

For IT Administrators

The change hands you a long-sought compliance lever. You’ll be able to set a global rule that disables meeting reports for all users, then selectively enable event reporting for specific groups—say, the corporate communications team that runs company-wide town halls. This granularity also helps align reporting with internal privacy policies, particularly in regions with strict employee monitoring laws.

For Event Organizers

Marketing and HR professionals who rely on attendee metrics for webinars and live events won’t be affected. They can continue to access the engagement data they need, provided your admin enables event reporting. The split ensures their work isn’t hamstrung by a blanket meeting-reporting prohibition.

For End Users

Most employees won’t notice the change immediately, but they stand to benefit from fewer automated tracking requests in their daily stand-ups and one-on-ones. If your org chooses to restrict meeting reporting, you won’t see the attendance summary in meeting chats for regular calls. Event invitations, however, may still include reports if your role demands it.

For Power Users and Team Owners

If you sometimes organize small meetings and occasionally run a training webinar, you’ll experience dual behavior. The meeting you set up for your weekly sync won’t generate a report, but the training session you schedule as a Teams webinar will—assuming your admin has configured things that way. No manual toggling on your part is needed; the system recognizes the event type and applies the respective policy.

How We Got Here: The March Toward Finer Controls

The journey to separated reporting policies mirrors a broader shift in Teams administration. When attendance reports first appeared several years ago, they were binary: on or off for everything. Over time, Microsoft added mid-level granularity—the option to restrict reports to attendee identity only, hide names, or allow organizers to disable them per meeting. Yet the fundamental coupling between meetings and events remained.

Customer feedback consistently highlighted the mismatch. A 2024 Microsoft Tech Community thread saw dozens of IT pros requesting the split, noting that “webinar analytics are business-critical, but tracking my boss’s one-on-one feels invasive.” The roadmap item, published on July 14, 2026, formalizes that request. Microsoft lists it as “in development” with a worldwide standard multi-tenant rollout target of August 2026.

This isn’t the first time Teams has decoupled features for events. In 2025, the platform introduced separate policies for lobby bypass and chat moderation in webinars versus meetings. The attendance report split follows the same logic: events are public-facing, often marketed, and demand analytics; internal meetings, by contrast, operate under different cultural and legal expectations.

What to Do Now

Audit Your Existing Policy

No immediate configuration action is possible; the feature is still under development. But you can prepare. First, review your current CsTeamsMeetingPolicy assignments. Which users or groups have the engagement report enabled? Identify any that absolutely need event reporting but could forgo meeting data.

Map Out Your Future Groups

Draft a table of policy scopes. For instance:

This exercise will speed up configuration once the split arrives. Keep in mind that existing meeting-report settings will likely migrate to a default state, but Microsoft may not automatically map them to the new event-only policy—plan to test thoroughly.

Review Privacy and Retention Practices

Engagement data often contains personally identifiable information. Before enabling broader event reporting, ensure your organization’s data retention schedules, employee privacy notices, and any works council agreements allow for such collection. Microsoft’s documentation notes that event reports can be downloaded and stored outside Teams, creating a compliance trail you’ll need to manage.

Stay Informed

Roadmap dates are estimates. Microsoft warns that features can be delayed, altered, or cancelled. Subscribe to the Message Center in the Microsoft 365 admin center for official announcements related to roadmap ID 567466. If you maintain PowerShell scripts for policy management, keep an eye on the Get-CsTeamsMeetingPolicy documentation for new parameters as the rollout approaches.

Outlook: More Events-On/Meetings-Off Controls?

The August 2026 split is likely just the start. As Teams events—webinars, town halls, virtual appointments—continue to diverge as a product line, expect more dedicated administrative controls. Areas like recording consent, transcript retention, and lobby settings may soon follow with their own meeting-versus-event toggles. For admins, this means a one-time planning effort now will pay dividends as the feature set matures.

When the rollout finally lands, test it first with a pilot group of event organizers. A phased approach will help you catch any unintended consequences—like organizers surprised by missing reports for meetings they considered “events.” Clear internal communication about the new policy lines will be just as important as the PowerShell cmdlets that enforce them.