Skip to main content
🦉
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderPortfolio
🦉
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderPortfolio

Connect

© 2026 M365 Message Center. Created with ❤️ by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center • Not affiliated with Microsoft

  1. Home
  2. /
  3. MC1085569

Microsoft Teams: Upgrade to Meeting Recording Organizer Policy by 30 June 2025

Plan for Change
Major Change

Message ID

MC1085569
View in Admin Center

Services

Microsoft Teams

Summary

Microsoft Teams will retire the recording initiator policy by June 30, 2025. Recordings will default to the meeting organizer's OneDrive. The fallback sequence will be Organizer -> Co-organizer(s) -> Initiator -> Async Media Storage. No action is required, but proactive adjustments are recommended. More information is available in the provided links.

Details

We are writing to inform you about an upcoming change regarding the MeetingInitiator value in the MeetingRecordingOwnership from PowerShell. Starting June 30, 2025, recording initiator policy will be retired. By default, recordings will be saved to the meeting organizer's OneDrive without needing MeetingRecordingOwnership setting.

  • MeetingInitiator value will be retired.
  • MeetingRecordingOwnership setting will be retired.

When this will happen:

June 30, 2025

How this affects your organization:

We understand the importance of governance and predictability in managing recordings, which is why we have introduced the Recordings saved to Organizers OdB in GCC, GCCH, and DOD by default, enabling recordings to be saved to the organizer's OneDrive, even if the organizer did not attend the meeting or event. Co-organizers have the same editing permissions as organizers for recording files.

When the organizer does not have a OneDrive account such as meetings scheduled using a shared mailbox, a fallback logic will be in place to determine the recording owner, following the sequence: Organizer -> Co-organizer(s) -> Initiator -> Async Media Storage (AMS).

Furthermore, we have introduced new features that provide more compliant control, available exclusively on the Organizer's ODB. Here is a quick comparison between the Initial's Policy and the Organizer's Policy:

AspectInitial's PolicyOrganizer's Policy
Default value

MeetingRecordingOwnership is set to MeetingInitiator

MeetingRecordingOwnership is set to MeetingOrganizer

Fallback pathInitiator -> Async Media Storage (AMS).Organizer -> Co-organizer (s) -> Initiator -> Async Media Storage (AMS). 

Who can access recording/transcription meeting option

*see more for Teams meeting option

No

Yes


No action is required on your part as the Meeting Organizer will be the default value for Recording Ownership.

What you can do to prepare:

Before June 30 2025, we encourage you to proactively set the MeetingRecordingOwnership as MeetingOrganizer to benefit earlier from better fallback coverage under the Organizer’s ODB policy. When the organizer doesn’t have a OneDrive account such as meetings scheduled using a shared mailbox, fallback logic is automatically enable Organizer -> Co-organizer (s) -> Initiator -> Async Media Storage (AMS) to determine the recording owner. We also support Who keeps recording feature to display recording owner in the chat to help you identify the recording owner in any situation. 

You can find more information by visiting related documentation to understand convenience recording in Teams meeting experience:

  • Introduction to recording Microsoft Teams calls and meetings - Microsoft Teams | Microsoft Learn
  • Teams meeting recording and transcript storage and permissions in OneDrive and SharePoint - Microsoft Teams | Microsoft Learn

Timeline

📅
Published
May 30, 2025
Message published to Message Center
✏️
Updated
May 30, 2025
Message content updated
⚠️
Action Required By
Jun 30, 2025
Action deadline
🏁
End Date
Sep 30, 2025
Message timeline ends

Tags

#Admin impact#Retirement

Category

📋Plan for Change

Related Messages

Similar updates

MC1087565●

Microsoft Teams: LEAP will transition to Microsoft Unified

Jun 3, 2025
MC1059667●

Action required: Classic Microsoft Teams end of availability starts July 1, 2025

Apr 21, 2025
MC1055554●

Microsoft Teams: The "Code snippets" feature for chats and channels will retire

Apr 15, 2025
MC1129730●

Remove toggle for Calendar in Teams

Aug 5, 2025
MC1127233●

Feature retirement: deploy Shifts to your frontline teams at scale in Teams Admin Center

Aug 1, 2025