Microsoft Teams: Meeting Participant Detail audit records will be available in all participating (non-organizer) tenants

Starting late August 2026, Microsoft Teams will share Meeting Participant Detail audit records with all participating tenants for their own users in cross-tenant meetings, enhancing audit visibility while maintaining data boundaries. No action is required, but admins may review audit processes accordingly.

[What and why]

Microsoft Teams audit logging is being enhanced to improve visibility for cross-tenant meetings.

Meeting Participant Detail audit records will now be shared with all participating tenants, not just the organizer tenant. This change enables administrators to access participant-level audit information for meetings attended by users in their tenant, even when the meeting is hosted by another organization.

This enhancement helps administrators better monitor and investigate Teams meeting activity involving users in their organization while maintaining tenant-level data boundaries.

[Rollout schedule]

• General Availability (Worldwide): Beginning in late August 2026 and expected to complete by early September 2026

[Impact on your organization]

Who is affected

• Microsoft 365 administrators who use Teams audit logs
• Organizations whose users participate in Teams meetings hosted by external tenants

Platforms and services

• Microsoft Teams
• Microsoft Purview Audit

What will happen

After this rollout:

• Participating tenants will receive Meeting Participant Detail audit records for their own users who attended a Teams meeting organized by another tenant.
• The Meeting Participant Detail audit record includes organizer information, allowing administrators to identify whether a meeting was organized by their tenant or by an external organization.
• This change does not result in all Meeting Participant Detail audit records being shared with participating tenants.
• Participating tenants will receive only audit records associated with users from their own tenant.
• Participating tenants will not receive Meeting Participant Detail audit records for users belonging to other organizations that attended the same meeting.

[Action required and recommendations]

No action is required.

Administrators may want to review any existing audit log collection, retention, or monitoring processes that consume Meeting Participant Detail audit records and assess whether the additional audit records affect those processes.

Learn more 

• (update expected) Audit log activities | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Question	Answer
Does this change alter how existing customer data is processed, stored, or accessed?	Yes. After rollout, Meeting Participant Detail audit records will be shared with participating tenants for their own users who attend meetings organized by another tenant. This changes how existing audit data is accessed by participating organizations.
Does this change modify Purview-related capabilities, including audit logging?	Yes. The change expands the availability of Meeting Participant Detail audit records, enhancing audit logging visibility for participating tenants in cross-tenant Teams meetings.
Does this change alter how admins monitor, report on, or demonstrate compliance activities?	Yes. Administrators in participating tenants will gain access to additional Meeting Participant Detail audit records for their own users, increasing visibility into meeting participation and supporting monitoring and compliance investigations.
Does this change include an admin control?	Yes. The feature supports role-based access control (RBAC), and customer administrators can control access using licensing, Admin UI, PowerShell cmdlets, and user or group-level controls supported by the parent service.
Can users enable or disable this feature themselves?	Yes. User opt-in or opt-out controls are supported through the parent service where applicable.
Does this change store customer data and have data residency implications?	Yes. The feature stores data in the same location as the parent service and follows the parent service's data residency and processing commitments.