Oct 01 2021 07:55 AM
Teams meeting recordings (OneDrive) for scheduled meetings are not being shared to all invited. Instead, the file is only being shared to people who attended the meeting. I've tested this a few times and gone through the lists to verify that the people that did not attend the meeting do not have access. If this is by design, this is a significant oversight by Microsoft. Previously in Stream, the recording was shared to everyone in the invite. Now with the move to OneDrive, this means going through the attendee list and comparing to who was invited, then manually going to the OneDrive recording, modifying the sharing, and adding each of the people that did not attend the meeting. Most meeting recordings in our organization are needed for the people who missed the meeting, and by default they cannot access. What a pain for any meeting larger than a few people!
Microsoft's documentation does not match the behavior:
"People invited to the meeting, except external users, will automatically be granted permission to the recording file with view access without ability to download."
https://docs.microsoft.com/en-us/microsoftteams/cloud-recording
Please tell me there's a powershell setting for this somewhere...
Sep 07 2022 02:05 AM
Sep 07 2022 10:59 AM
@manshu1905 Great idea! I remember when I use to believe MS support could fix problems, lol. I appreciate any info you find out. If they suggest that other users should open tickets to help show the issue is systemic, let me know and I'll open a ticket as well.
Aug 30 2023 12:24 PM
@Eric_H or @manshu1905 - did you ever find a resolution for this? I have some end users reporting the same symptom this week. Just started digging in, but haven't uncovered anything too helpful yet.
Thanks,
Brian
Sep 21 2023 02:29 PM - edited Sep 21 2023 02:30 PM
@GullettBrianand @Eric_Hepinstall - Hello, I'm getting reports as of yesterday from our employees when they are invited to Teams meetings but don't attend...they can't access the chat or recording from the meeting.
Did anyone find a resolution to this issue?
Dec 18 2023 09:38 AM