Published Apr 8, 2024
Microsoft Teams meeting recordings will now be saved to the organizer's OneDrive by default, with rollout dates varying from early June to late August 2024, depending on the service availability. Admins can use PowerShell policy 'TeamsRecordingRollOutPolicy' for special cases. No significant user impact is expected, but admins may need to update documentation.
Updated May 1, 2024: We have updated the rollout timeline below. Thank you for your patience.
We are rolling out a change to Microsoft Teams meetings recordings, which will be saved by default to the meeting organizer's Microsoft OneDrive account. (Now, meeting recordings are saved to the OneDrive account for the person who initiates the recording.)
This message is associated with Microsoft 365 Roadmap ID 116251.
When this will happen:
General Availability (Worldwide): We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May).
General Availability (GCC): We will begin rolling out mid-June 2024 and expect to complete by late June 2024.
General Availability (GCC High): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.
General Availability (DoD): We will begin rolling out mid-August 2024 and expect to complete by late August 2024.
How this will affect your organization:
This rollout will ensure recordings are governed by the organizer's meeting setup and policies, like other meeting artifacts (meeting invitation, transcript, and so on). If the organizer does not have OneDrive provisioned, the OneDrive account is out of capacity, or the recording fails to upload successfully, the recording will be accessible from the recording link in the meeting chat (current behavior for these cases).
This rollout will also be supported by the PowerShell user-level policy TeamsRecordingRollOutPolicy that admins can use for special situations to continue to save recordings in the recoding initiator's OneDrive account. For example, when existing workflows need to be migrated or when Teams accounts have delegate permissions, and so on.
This rollout will not have any significant end user impact. From an IT admin perspective, the rollout will drive better compliance and may need some oversight because the change is desirable.
What you need to do to prepare:
To temporarily override this rollout, use the PowerShell policy TeamsRecordingRollOutPolicy. Three months after the rollout, we will stop honoring the override policy, to ensure consistent storage.
This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.
We will update this comm before rollout with revised documentation.