Microsoft’s recent change to Teams meeting recordings has been more disruptive than expected! Originally, the update was supposed to shift the ownership of recordings from the person who pressed “record” to the meeting organizer’s OneDrive, starting in June 2024. But now that it’s here, it’s causing some real workflow headaches.

Previously, I could record a meeting, edit it in Stream, trim unnecessary parts, update transcriptions, add chapters, adjust the expiry date, and then organise and share the recording as needed. Now, that flexibility is gone. The recording ends up in the organiser’s OneDrive, which might be inaccessible, especially if they didn’t attend the meeting or if it’s tied to a service account. This has turned into a game of tracking down who owns the recording just to make simple edits or share it.

While Microsoft did introduce a temporary PowerShell policy to revert ownership back to the recording initiator, this fix only lasts for three months before it defaults back to the organiser. That’s not exactly a long-term solution.

I can understand why Microsoft made this change—there have been issues with access when the recording initiator leaves the team or when confusion arises over ownership. But forcing this on users without a choice has thrown a wrench into many people’s workflows, mine included.

There’s been a lot of pushback on this decision, with discussions in local tech communities I am part of, Microsoft Community Answers Forums, and Reddit echoing similar frustrations. Hopefully, the team responsibility for Teams development takes a page from @Marc Mroz and the guys over at Microsoft Stream’s playbook, listens to the community, and brings back some much-needed flexibility. This kind of change should be a choice, not a hard-coded rule.

For now, there is a temporary fix for this if you use PowerShell to connect to MS Teams and run the following command:

Set-CsTeamsRecordingRollOutPolicy -Identity Global -MeetingRecordingOwnership RecordingInitiator

If you run this it will put things back to how they were with the Recording Initiator being the owner of the file, however it looks like this will only hold in place for 3 months and then the change will be forced.

This gives you some time to re-educate and let people know this change is coming, or perhaps time for enough people to push back to Microsoft and allow this to be a choice.

This is a modified version of the script available here https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamsrecordingrolloutpolicy?view=teams-ps which allows you to make a new policy, but does not tell you how to apply said policy. By running against “Global” it makes this change for everyone.

You can also check what policy you have by running:

Get-CsTeamsRecordingRollOutPolicy

Hope this helps

#BeExcellentToEachOther

​Microsoft’s recent change to Teams meeting recordings has been more disruptive than expected! Originally, the update was supposed to shift the ownership of recordings from the person who pressed “record” to the meeting organizer’s OneDrive, starting in June 2024. But now that it’s here, it’s causing some real workflow headaches. Previously, I could record a meeting, edit it in Stream, trim unnecessary parts, update transcriptions, add chapters, adjust the expiry date, and then organise and share the recording as needed. Now, that flexibility is gone. The recording ends up in the organiser’s OneDrive, which might be inaccessible, especially if they didn’t attend the meeting or if it’s tied to a service account. This has turned into a game of tracking down who owns the recording just to make simple edits or share it. While Microsoft did introduce a temporary PowerShell policy to revert ownership back to the recording initiator, this fix only lasts for three months before it defaults back to the organiser. That’s not exactly a long-term solution. I can understand why Microsoft made this change—there have been issues with access when the recording initiator leaves the team or when confusion arises over ownership. But forcing this on users without a choice has thrown a wrench into many people’s workflows, mine included. There’s been a lot of pushback on this decision, with discussions in local tech communities I am part of, Microsoft Community Answers Forums, and Reddit echoing similar frustrations. Hopefully, the team responsibility for Teams development takes a page from @Marc Mroz and the guys over at Microsoft Stream’s playbook, listens to the community, and brings back some much-needed flexibility. This kind of change should be a choice, not a hard-coded rule. For now, there is a temporary fix for this if you use PowerShell to connect to MS Teams and run the following command: Set-CsTeamsRecordingRollOutPolicy -Identity Global -MeetingRecordingOwnership RecordingInitiator  If you run this it will put things back to how they were with the Recording Initiator being the owner of the file, however it looks like this will only hold in place for 3 months and then the change will be forced. This gives you some time to re-educate and let people know this change is coming, or perhaps time for enough people to push back to Microsoft and allow this to be a choice. This is a modified version of the script available here https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamsrecordingrolloutpolicy?view=teams-ps which allows you to make a new policy, but does not tell you how to apply said policy. By running against “Global” it makes this change for everyone. You can also check what policy you have by running: Get-CsTeamsRecordingRollOutPolicy  Hope this helps #BeExcellentToEachOther  Read More

​