Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 21:28 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Microsoft Teams: Teams Events Attendance and Engagement Report Policy

Rollout

Ends
11 Jan 2027
Roadmap
567466
Platforms
Desktop

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

Updated September 11, 2026: We have updated the timeline. Thank you for your patience.

What and Why

We are introducing a new policy that separates Teams Events attendance and engagement report controls from Teams Meetings attendance and engagement report controls. With this change, administrators can independently manage organizer access to attendance and engagement reports for Teams Events through CsTeamsEventsPolicy, without affecting attendance and engagement report settings for Teams Meetings managed through CsTeamsMeetingPolicy.

This update provides greater administrative flexibility by allowing separate configuration of attendance and engagement reporting for Teams Events and Teams Meetings.

Rollout schedule

  • General Availability (Worldwide, GCC): Rollout will begin in early November 2026 (previously mid-October) and is expected to complete by early December 2026 (previously end of October)

Impact on your organization

  • Teams Events attendance and engagement report controls will be managed separately from Teams Meetings.
  • A new attendance and engagement report setting will be available in CsTeamsEventsPolicy.
  • Administrators can configure one of the following policy values:
  • On
  • Off
  • On, organizers can turn it off (default)
  • Off, organizers can turn it on
  • Organizers can view and download attendance and engagement reports for all events. Organizers cannot disable attendance and engagement reporting.
  • Organizers cannot view or download attendance and engagement reports for any events.
  • Organizers can view and download attendance and engagement reports for events and can disable attendance and engagement reporting in event options.
  • Attendance and engagement reporting is disabled by default. Organizers can enable attendance and engagement reporting in event options for individual events.

Action Required / Recommendations

  • Review your current attendance and engagement reporting requirements for Teams Events.
  • Configure the appropriate setting in the new Teams Events attendance and engagement report policy based on your organizational needs.
  • Do not assume Teams Events will continue to inherit attendance and engagement report settings from CsTeamsMeetingPolicy.
  • Update internal administrative documentation and guidance if you currently manage attendance reporting through Teams meeting policies.

No immediate action is required before rollout. However, we recommend reviewing and validating policy settings after the feature becomes available to ensure Teams Events reporting behavior aligns with your organization's requirements.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 21:28 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current