Users will be informed about pending expirations via a notification in the Teams chat window when the video pops into the chat at the end of the recording session (see picture below).
#Cotse autoexpire address update
How will I know when this feature is fully rolled out to my tenant? We will provide another update to the message center post when we are actively deploying to production tenants.How come I can set and see the expiration policy but do not see the expiration set on the files? We rolled out the ability for the tenant admin to define the default expiration days to allow them to preemptively define the default behavior before we roll out the actual expiration stamping and execution.We have therefore decided to delay the production rollout of the portion of this feature that stamps expiration dates on the file and deletes the file based on that expiration date. Why are you delaying this rollout? As part of this change, we are deleting files, and we want to ensure we spend adequate time in our testing and early adopter environments.We are making this update based on new statistics that show on average across all tenants, less than 1% of recordings are watching after 120 vs 5% after 60 days.Īs a reminder if you want to override the default setting you can do so in the Teams Admin center or by setting NewMeetingRecordingExpirationDays in PowerShell. The final stage is the part of the feature that actually stamps the expiration date on the file and physically deletes the file based on that stamped expiration date.įor any tenant that does not have a custom policy in place already, we are updating the default expiration days from 60 to 120 days. To ensure the best experience we have postponed the start of final stage of this change until late March. If you want to override the default and have not yet set this new attribute, please do so. Note: The policy attribute to control the expiration is NewMeetingRecordingExpirationDays. We will not turn on the auto-expiration actions until January 2022 at the earliest, to give you time to override the policy if you’d like. Compliance policies will override the expiration setting.ĭo not want recordings in your tenant to auto-expire? No problem, instructions to disable the feature in the Teams admin console or in PowerShell are shown below. Meeting owners will be notified about expired recordings and may extend the expiration date in OneDrive/SharePoint. Newly created meeting recordings in OneDrive & SharePoint will be automatically deleted after this point unless the meeting owner extends the expiration. Teams Admins will be able to modify the default meeting recording expiration time via a setting in the Teams Admin Portal or by modifying policy attributes using Powershell scripts. Newly created Teams meeting recordings in OneDrive and SharePoint will be automatically deleted by the service based on a default Teams policy setting. This message is associated with Microsoft 365 Roadmap ID 84580. Admins can disable this feature if desired. Additionally, they have updated this post to correct the setting modification capability limitations and will provide an additional update when those limitations are corrected.Īs part of the evolution of the new Stream ( built on SharePoint), we are introducing the meeting recording auto-expiration feature, which will automatically delete Teams recording files stored in OneDrive or SharePoint after a preset period of time. Updated August 31, 2021: Microsoft has updated the rollout timeline below. New action is required if you do not want your meeting recordings to auto-expire in January 2022.
We are not turning on the auto-expiration feature yet.
#Cotse autoexpire address how to
Updated November 09, 2021: We have updated this post with guidance on how to take preemptive action. Updated April 01, 2022: We have begun rolling this out and will be monitoring customer reported issues to ensure a smooth deployment. Updated April 06, 2022: We have begun rolling this out and will be monitoring customer reported issues to ensure a smooth deployment. Updated April 29, 2022: We have begun rolling this out and will be monitoring customer reported issues to ensure a smooth deployment. Updated May 24, 2022: We have updated the rollout timeline below.
0 kommentar(er)
