The Teams meeting recap feature highlights some of the important resources which can be generated for meetings. The recording, transcript, and attendance report are displayed under the Details tab for meetings accessed through the Teams calendar app.
Storage for videos stored in the new Stream will be charged against SharePoint Online and OneDrive for Business accounts. This shouldn’t make much difference for Teams recordings, as there’s plenty of storage available for OneDrive accounts. You can increase the default amount to 5 TB in enterprise tenants, and that should be enough for even the most copious of Teams meeting recorders.
On December 18, Microsoft will switch control over Teams 1:1 meeting recording from meeting to calling policies. By default, this stops users recording 1:1 meetings, meaning that tenant admins will have to update the default calling policy and any custom calling policy to allow recordings to continue. Of course, you might think it a bad idea to allow people to record 1:1 calls, in which case you don’t need to do anything.
It’s very convenient to be able to record a Teams meeting and have the recording processed and stored in Stream. But what happens when the recording fails to be processed? Usually it’s because the account that starts the recording (the owner) doesn’t have a Stream license. Fortunately, the situation is easily rescued.
In a surprise development, Microsoft announced that recording of Teams 1:1 calls is now available. Some limitations are present and the feature seems rushed, but perhaps this is because people working at home on confidential transactions need the feature, In any case, record away!
In mid-February, Microsoft will roll out a change to allow Office 365 tenants in regions where the Teams and Stream services are not co-located to record Teams meetings for the first time. This might be good news for you, but it might also pose a data sovereignty issue because once you start using Stream in another region, that’s where the recordings will stay.