Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 13:41 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Action date

30 Jun 2025 483d ago Act by , as Microsoft's metadata states

What the notice says

Microsoft’s text, with source markup removed
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: Aspect Initial's Policy Organizer's Policy Default value MeetingRecordingOwnership is set to MeetingInitiator MeetingRecordingOwnership is set to MeetingOrganizer Fallback path Initiator -> 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

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
  • 1 linked page has not been read yet.
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 26 Oct 13:41 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current