Admins unable to update Meeting Recording Expiration Days

Nichlas Babb 1 Reputation point
2021-08-04T16:27:22.933+00:00

None of the Global admins in my company are able to use the PS Script: Set-CsTeamsMeetingPolicy -Identity Global -MeetingRecordingExpirationDays 50.
Trying to set the policy to the max days (99999) but we are all getting the following error: You are not permitted to invoke Set-CsTeamsMeetingPolicy with the following parameters:
MeetingRecordingExpirationDays
+ CategoryInfo : NotSpecified: (:) [Set-CsTeamsMeetingPolicy], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Microsoft.Rtc.Management.Internal.SetTeamsMeetingPolicyCmdlet
+ PSComputerName : api.interfaces.records.teams.microsoft.com

According to this article we should currently be able to do this: https://learn.microsoft.com/en-us/microsoftteams/cloud-recording

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,250 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. JimmyYang-MSFT 49,441 Reputation points Microsoft Vendor
    2021-08-05T07:21:45.517+00:00

    Hi @Nichlas Babb

    The feature is still in development and may be released in September. you could see the roadmap to know more details about it.

    120725-21.png


    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. AOEH 1 Reputation point
    2021-08-06T12:35:53.583+00:00

    Message Summary
    As 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.

    Key points

    Microsoft 365 Roadmap ID: 84580.
    Timing: late September through mid-November
    Roll-out: tenant level
    Control type: user control and admin control
    FAQs: https://learn.microsoft.com/microsoftteams/cloud-recording#auto-expiration
    Action: review, assess and decide what you want the default expiration period to be for your organization
    How this will affect your organization:

    New recordings will automatically expire 60 days after they are recorded if no action is taken. The 60-day default was chosen as, on average across all tenants, most >meeting recordings are never watched again after 60 days. However this setting can be modified if a different expiration timeline is desired.

    To change the default expiration days at the tenant level, there will be two methods available.

    You can use PowerShell to modify “MeetingRecordingExpirationDays.” This can be done at any time, as the setting is present in PowerShell today even though the >feature is not yet enabled. An example command is: "Set-CsTeamsMeetingPolicy -Identity Global -MeetingRecordingExpirationDays 50”
    As this feature is rolled out, a new setting will be available in the Teams admin center.
    Users (except for users with A1 licenses) can also modify the expiration date for any recordings on which they have edit/delete permissions, using the files details pane >in OneDrive or SharePoint. A1 users will receive a 30-day expiration default that can be reduced but not increased. To retain recordings for longer than 30 days A1 >users will need to download the file to a non-synced folder.

    At either the tenant or user level (excluding A1 users as noted above), the expiration timeline can range from one day to several years, or even set to never auto-expire.

    Additional clarifications:

    The expiration setting is not a retention setting. For example, setting a 30-day expiration on a file will trigger an auto-deletion 30 days after the file was created, but it >will not prevent a different system or user from deleting that file ahead of that schedule.
    When a recording is deleted due to the expiration setting, the end user will be notified via email. The SharePoint tenant or site admin, or the end user with edit/delete >permissions will be able to retrieve the file from the recycle bin for up to 90 days.
    Any retention/deletion/legal hold policies you have designated in the Compliance center will override this feature. In other words, if there is a conflict between your >designated Compliance policy setting and the expiration setting, the compliance policy timeline always wins.
    The admin does not have the ability to override end-user modification capabilities.
    This will not impact any existing meeting recordings created before the feature is deployed. Also, any changes to the default date in the admin console will only apply >to newly created meeting recordings after the change is made.
    The expiration days setting in Teams is controlled only via MeetingRecordingExpirationDays. CallRecordingExpirationDays is currently being ignored.
    The min number of days that can be set on MeetingRecordingExpirationDays is 1 and the maximum is 99,999 (e.g. 273 years).
    This feature does not impact meeting recordings stored in Microsoft Stream (classic Stream) but will affect recordings stored in the new Stream (built on OneDrive and >SharePoint).
    This feature is only available for Teams meeting recordings created by the Teams service in OneDrive and SharePoint. It is not available for other file types in OneDrive >and SharePoint.
    What you need to do to prepare:

    If you want the default expiration to be different than 60 days, please modify it via PowerShell or (once available) in the admin center.

    If you are going to specify a tenant level expiration standard, inform your user base about the change before we deploy it so that they are aware they will need to take >action to retain their new recording files past the specified time period once the feature is enabled.

    Learn more about the feature in these FAQs.

    @JimmyYang-MSFT , this was announced in the message center, including the command to increase the default period. Due to that, I assumed (like @Nichlas Babb ) that we can change that value now. I would say, it is a bug: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/7630

    Cheers, Alex