Forum Discussion
Teams recordings failing or going into Stream
halbp Hello, this is how it's supposed to work Use OneDrive for Business and SharePoint for meeting recordings - Microsoft Teams | Microsoft Docs
All Teams meeting recordings are now being stored in OneDrive/SharePoint, Stream is not an option for storage anymore according to the official documentation. If the storage process fails for some reason, the recordings are instead being stored in Azure for 21 days before deletion and during this time accessible from the chat or conversation. You'll need the proper license for the services included.
I general I would start by looking at the assigned policies. That is, what Teams meeting policies are your users assigned and is the parameter -RecordingStorageMode set to "OneDriveForBusiness". If they really end up in Stream (not only temporary in Teams, i.e. Azure Media Services) even though this shouldn't be possible, regardless of the above parameter, you better open up a support ticket with Microsoft.
If the parameter used is set to Stream and still uses Stream for storage I would also reach out to the official support as that's not the expected behavior going forward according to the official documentation.
Troubleshooting assistance for admins
Self-help diagnostics for Teams administrators - Microsoft Teams | Microsoft Docs
Edit* Product team is now aware of the bug and will look into it asap (why auto-record puts the recording in Stream regardless if all policies are set to OD). They also suggested to provide this info using the Feedback feature in the Teams client (Help, bottom left corner).
halbp Hello, this is how it's supposed to work Use OneDrive for Business and SharePoint for meeting recordings - Microsoft Teams | Microsoft Docs
All Teams meeting recordings are now being stored in OneDrive/SharePoint, Stream is not an option for storage anymore according to the official documentation. If the storage process fails for some reason, the recordings are instead being stored in Azure for 21 days before deletion and during this time accessible from the chat or conversation. You'll need the proper license for the services included.
I general I would start by looking at the assigned policies. That is, what Teams meeting policies are your users assigned and is the parameter -RecordingStorageMode set to "OneDriveForBusiness". If they really end up in Stream (not only temporary in Teams, i.e. Azure Media Services) even though this shouldn't be possible, regardless of the above parameter, you better open up a support ticket with Microsoft.
If the parameter used is set to Stream and still uses Stream for storage I would also reach out to the official support as that's not the expected behavior going forward according to the official documentation.
Troubleshooting assistance for admins
Self-help diagnostics for Teams administrators - Microsoft Teams | Microsoft Docs
Edit* Product team is now aware of the bug and will look into it asap (why auto-record puts the recording in Stream regardless if all policies are set to OD). They also suggested to provide this info using the Feedback feature in the Teams client (Help, bottom left corner).
- Hi, I would start by looking at the assigned policies. That is, what Teams meeting policies are your users assigned and is the parameter -RecordingStorageMode set to "OneDriveForBusiness". If they really end up in Stream (not only temporary in Teams, i.e. Azure Media Services) even though it shouldn't be possible regardless of the above parameter you better open up a support ticket with Microsoft.
- Yes that is set to Stream, but as you say it shouldn't end up Stream anyway as that option is supposed to have no effect now.
I did some more investigation, and if the user sets the meeting options to record automatically, then the recording is saved in Stream, I can see it there and I get an email from Stream with the location. If they start recording manually, it goes into OneDrive.
And yes, I have verified myself that the recording does indeed end up in Stream. So this seems to be an error, I am going to log a call.Have you tried setting the policy to ODB anyway? I'm wondering if that's what's causing it, regardless of what the documentation states. If you have and it's still happening, could you please post an update here when you find out why this is happening?
Update: Our global policy has RecordingStorageMode set to "Stream" and we are seeing this behavior with auto recording as well. I switched to a policy that is set to "OneDriveForBusiness" and the account now correctly records to ODB. I'm guessing that if you're currently configured this way and change that your policy setting to OneDriveForBusiness, it will fix your problem. The documentation states this setting is now irrelevant, but apparently not.
