Skip to content

Commit

Permalink
Merge branch 'main' into docs-editor/certified-hardware-android-17308…
Browse files Browse the repository at this point in the history
…89999
  • Loading branch information
rjagiewich authored Nov 6, 2024
2 parents 05fef58 + 1f1161c commit e69f3f8
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Teams/manage-meeting-recording-options.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ author: wlibebe
manager: pamgreen
ms.topic: article
ms.service: msteams
ms.reviewer:
ms.reviewer: lisma
ms.date: 12/11/2023
audience: admin
ms.localizationpriority: medium
Expand Down Expand Up @@ -70,7 +70,7 @@ By default, meeting recordings are deleted after 120 days. This is configured by
- **Recordings automatically expire** determines if meeting recordings are automatically deleted after a specified time.
- **Default expiration time** specifies the number of days after which recordings are deleted. The default is 120.

When a meeting participant records a meeting, the recording is stored in their OneDrive. Channel meetings are stored in the SharePoint site associated with the channel. Because meeting recordings are .mp4 files, they can be moved or deleted like any other file. If a meeting recording is moved from its original location, the expiration setting will no longer affect it.
When a meeting participant records a meeting, the recording is stored in the organizer's OneDrive. Channel meetings are stored in the SharePoint site associated with the channel. Because meeting recordings are .mp4 files, they can be moved or deleted like any other file. If a meeting recording is moved from its original location, the expiration setting will no longer affect it. For details, see [Teams meeting recording storage and permissions in OneDrive and SharePoint](tmr-meeting-recording-change.md).

The expiration feature is meant for removing old recordings to save storage space. It's not meant for enforcing compliance requirements. If you have compliance requirements around how long meeting recordings are retained or when they're deleted, consider storing them in a SharePoint library where you can apply [Microsoft Purview retention policies](/microsoft-365/compliance/retention).

Expand Down
1 change: 1 addition & 0 deletions Teams/plan-town-halls.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,7 @@ If you've been using live events for your organization, you might want to unders
|AI generated captions|![Image of a checkmark for yes](media/circle-check.png)|![Image of a checkmark for yes](media/circle-check.png)|![Image of a checkmark for yes](media/circle-check.png)|
|Attendee reporting|![Image of a checkmark for yes](media/circle-check.png)| ![Image of a checkmark for yes](media/circle-check.png)|![Image of a checkmark for yes](media/circle-check.png)|
|Broadcast capacity|10k|10k|- 20k</br> *- 100k In development*|
|Chat for attendees|![Image of a x for no](media/x-for-no.png)|![Image of a x for no](media/x-for-no.png)|![Image of a checkmark for yes](media/circle-check.png)|
|Concurrent events|15|15|50|
|Control when event invites are sent|![Image of a checkmark for yes](media/circle-check.png)|*In development*|*In development*|
|Co-organizer capacity|N/A|10|10|
Expand Down

0 comments on commit e69f3f8

Please sign in to comment.