Meeting policies and meeting expiration in Microsoft Teams
Meeting policies in Microsoft Teams are used to control whether users in your organization can start and schedule meetings and the features that are available to meeting participants for meetings that are scheduled by users. You can use the global (Org-wide default) policy or create and assign custom policies. You manage meeting policies in the Microsoft Teams admin center or by using Get, New, Set, Remove, Grant -CsTeamsMeetingPolicy PowerShell cmdlets.
The meeting policy settings that control whether users can start and schedule meetings and also control expiration of meetings scheduled by users. When a meeting join link and conference ID for a meeting expires, no one can join the meeting. The following meeting policy settings determine whether users can start and schedule meetings in Teams. We discuss the meeting settings in this article.
- Meet now in channels: Controls whether a user can start an impromptu meeting in a channel.
- Channel meeting scheduling: Controls whether a user can schedule a meeting in a channel.
- Private meeting scheduling: Controls whether a user can schedule a private meeting in Teams. A meeting is private when it's not published to a channel in a team.
- Outlook add in: Controls whether a user can schedule a private meeting from Outlook. A meeting is private when it's not published to a channel in a team.
- Meet now in private meetings: Controls whether a user can start an impromptu private meeting.
By default, these settings are on. When any of these settings are turned off, any user who is assigned the policy can't start or schedule new meetings of that type. At the same time, the meeting join links and conference IDs of all existing meetings of that type that the user previously started or scheduled expire.
For example, if a user is assigned a meeting policy in which these meeting policy settings are set to On, and then you turn off the Allow Meet now in channels setting, that user can no longer start impromptu meetings in channels, and the channel Meet now join links that the user previously created are expired. The user can still start and schedule other meeting types and join meetings organized by other people.
What happens when the meeting join link and conference ID expire?
When the meeting join link and conference ID for a meeting expires, no one can join the meeting. When a user tries to join the meeting through the link or by phone, they'll get a message that says the meeting is no longer available. Conversations, files, whiteboards, recordings, transcripts, and other content related to the meeting are retained and users can still access them.
What happens when you turn on and turn off a meeting policy setting?
Switch a meeting policy setting from on to off
When a meeting policy setting is set to On, users who are assigned the policy can start or schedule meetings of that type and everyone can join. When you switch the meeting policy setting to Off, users who are assigned the policy can't start or schedule new meetings of that type, and the meeting join links and conference IDs of existing meetings that the user previously scheduled are expired.
Keep in mind that the user can still join meetings organized by other people.
Switch a meeting policy setting from off to on
When you switch a meeting policy setting from Off to On, users who are assigned the policy can start or schedule meetings of that type. If a meeting policy setting is turned off and then turned on again for a user, all previously scheduled (and expired) meetings organized by the user become active and people can join them using the meeting join link or by phone.
Meeting expiration scenarios
Here's a summary of how meeting expiration works for each of the meeting policy settings discussed in this article.
|If you want to...||Do this||Meeting join behavior|
|Expire private Meet now meetings started by a user||Turn off Meet now in private meetings.||No one can join private Meet now meetings started by the user.|
|Expire private meetings scheduled by a user||Turn off Private meeting scheduling and turn off Outlook add-in.||No one can join private meetings scheduled by the user. This prevents people from joining the following meetings:
Both Private meeting scheduling and Outlook add-in must be off to expire private meetings scheduled by a user. If one setting is off and the other is on, meeting join links and conference IDs of existing meetings remain active and won't be expired.
|Expire channel Meet now meetings started by a user||Turn off Meet now in channels and turn off Channel meeting scheduling.||No one can join channel Meet now meetings started by the user.|
|Expire channel meetings scheduled by a user||Turn off Channel meeting scheduling.||No one can join channel meetings scheduled by the user. This prevents people from joining the following meetings:
If you want people to access meetings that were previously scheduled or started by a particular user, you can:
- Turn on the meeting policy setting for that user.
- Turn off the meeting policy setting for that user and have another user who has the policy setting enabled create a new meeting to replace the expired meeting.
If the meeting was sent by a delegate, who was given permissions to send meeting invitations on behalf of another person, such as a manager, the meeting policy setting is applied to the person who granted permission (the manager).
Changes to meeting expiration
All newly created Teams meeting recordings (TMRs) will have a default expiration of 60 days. This is on by default for all tenants. This means that by default, all TMRs created after this feature was turned on will be deleted 60 days after their creation date. Admins can also set meetings to never auto-expire. The OneDrive and SharePoint system will monitor the expiration date set on all TMRs and will automatically move TMRs to the recycle bin on their expiration date.
Automatic meeting expiration is a lightweight housekeeping mechanism to reduce storage clutter created by older TMRs. On average, across all customers, 99% of TMRs aren't watched after 60 days. We believe nearly all customers will benefit from the reduced storage load on their tenant by removing recordings that likely won't be watched again after 60 days. It's our goal to provide as clean an experience as possible for all customers by default.
Use meeting expiration to limit the OneDrive or SharePoint for cloud storage consumption driven by Teams meeting records. A typical meeting recording consumes around 400 MB per hour of recording.
The maximum default expiration date for A1 users is 30 days.
- The expiration date is calculated as the day it's created plus the default number of days set in the Teams policy by the admin.
- Playback doesn't impact the expiration date.
Change the default expiration date
Admins can edit the default expiration setting in PowerShell or the Teams admin center. Any changes will only effect newly created TMRs from that point forward. It won't impact any recordings created before that date. Admins can't change the expiration date on existing TMRs. This is done to protect the decision of the user that owns the TMR. Both meetings and calls can be controlled by this setting.
The expiration date value can be set as follows:
- Minimum value: 1 day
- Maximum value: 99,999 days
- You can also set the expiration date to -1 so the recordings never expire.
Example PowerShell command:
Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays 50
You can set the expiration date in the Teams admin center under Meeting policies. After you turn on Meetings automatically expire, you'll get the option to set a recording expiration.
Security and compliance
Should I rely on this feature for strict security and compliance adherence?
No, you shouldn't rely on this for legal protection since end users can modify the expiration date of any recordings they control.
Will a retention and/or deletion policy I've set in the Security & Compliance center override the Teams meeting recording expiration setting?
Yes, any policies you have set in the compliance center will take full precedence.
- If you have a policy that says all files in a site must be retained for 100 days, and the expiration setting for a Teams meeting recording is 30 days, then the recording will be retained for the full 100 days.
- If you have a deletion policy that says all Teams meeting recordings will be deleted after five days and you have an expiration setting for a Teams meeting recording of 30 days, then the recording will be deleted after five days.
Will this feature enforce file retention?
No, files won't be retained due to this feature or its settings. If a user with delete permissions attempts to delete a TMR that has an expiration setting, that user’s delete action will be executed.
What SKUs are required for this feature?
- All SKUs will have this feature by default.
- A1 users will be defaulted to a maximum 30-day expiration period, but they can change the expiration date as needed.
What if I want the admin to have full control over the lifecycle of meeting recordings and don't want to give end users the ability to override the expiration date?
We recommend using the Security and Compliance retain and/or delete policies. That offering is targeted to solve complex policy and SLA-driven administrative legal concerns.
The auto-expiration feature is solely meant as a lightweight housekeeping mechanism to reduce storage clutter created from old Teams meeting recordings.
Will future TMRs migrated from Classic Stream after this feature is released have auto-expiration applied to them too?
No, migrated TMRs will not come with an expiration set on them. Instead, we encourage admins to only migrate TMRs that they want to retain. More details will be provided in the migration documentation.
How is this feature different from the expiration message I see when a TMR upload to OneDrive and SharePoint fails?
When a recording fails to upload to OneDrive or SharePoint, the Teams application displays a message in the chat that users have up to 21 days to download the TMR before it’s permanently deleted from the Teams server. This existing expiration experience due to failed TMR uploads is not related to the OneDrive and SharePoint auto-expiration feature being discussed in the help document.