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 |
|
|
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
Source: Microsoft
Latest Posts
- Microsoft Copilot Studio – Reassign an agent’s owner with PowerShell [MC1085991]
- Power Platform admin center – Deploy and manage unified sandbox environments [MC1086001]
- Power Automate – Share desktop flow connections with service principal users [MC1086003]
- Microsoft Power Automate – Use machine to credential mapping in desktop flow connections [MC1086000]