Skip to content

Commit

Permalink
Merge pull request #15360 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
publish main to live 10:30 AM 8/8/24
  • Loading branch information
American-Dipper committed Aug 8, 2024
2 parents 72d0f19 + 95691e6 commit 74a3976
Show file tree
Hide file tree
Showing 6 changed files with 51 additions and 13 deletions.
6 changes: 6 additions & 0 deletions Teams/devices/teams-ip-phones.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,8 @@ The following are the latest firmware versions released via Microsoft Teams Admi
#### <b> Yealink </b>
| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date|
|:----------------|:-------------------|:----------------------------|:----------------------------------------------------------------------------------------------|:--------------------------------------------|
|MP54/MP56/MP58| `122.15.0.157`| `N/A` | Teams client: `1449/1.0.94.2024071104` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| August 7, 2024|
|CP965| `143.15.0.65`| `N/A` | Teams client: `1449/1.0.94.2024071104` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| August 7, 2024|
|MP52 E2/MP54 E2/MP56 E2/MP58 E2| `176.15.0.19`| `N/A` | Teams client: `1449/1.0.94.2024071104` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: ` 1.0.0.202402202353.product`| July 31, 2023|
|MP52| `145.15.0.94`| N/A | Teams client: `1449/1.0.94.2024060310` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| July 2, 2024|
|VP59| `91.15.0.147`| N/A | Teams client: `1449/1.0.94.2024060310` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| July 2, 2024|
Expand All @@ -194,6 +196,8 @@ The following are the latest firmware versions released via Microsoft Teams Admi
#### <b> HP | Poly </b>
| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date| Cloud|
|:----------------|:-------------------|:----------------------------|:------------------------------------------------------------------|:-------------------------|:----------------------------------|
| CCX350/CCX400/CCX500/CCX505/CCX600 | `8.1.6.1006` | `N/A`| Teams client: `1449/1.0.94.2024011003` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| August 2, 2024| GCCH|
|Trio C60 | `8.1.6.1005` | `N/A` | Teams client: `1449/1.0.94.2024011003` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| August 2, 2024 | GCCH|
|CCX350/CCX400/CCX505/CCX600 | `8.1.2.1122` | N/A | Teams client: `1449/1.0.94.2023041203` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202301162118.product`| January 22, 2024| DoD |
|CCX350/CCX400/CCX500/CCX505/CCX600 | `8.1.5.1732` | `8.1.3.1301`| Teams client: `1449/1.0.94.2023072509` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202306202019.product`| January 19, 2024| GCCH|
|Trio C60 | `8.1.5.1737` | `8.1.3.1300` | Teams client: `1449/1.0.94.2023072509` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202306202019.product`| January 19, 2024 | GCCH|
Expand Down Expand Up @@ -232,6 +236,7 @@ The following are the latest firmware versions released via Microsoft Teams Admi
#### <b> Neat </b>
| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date|
|:----------------|:-------------------|:----------------------------|:-----------------------------------------------------------|:--------------------------|
| Neat Frame | `NFF1.20240516.0007` | N/A | Teams client: `1449/1.0.95.2023101102` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| August 7, 2024|
| Neat Frame | `NFF1.20240312.0005` | N/A | Teams client: `1449/1.0.95.2023101102` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| April 12, 2024|
| Neat Frame | `NFF1.20240120.0009` | N/A | Teams client: `1449/1.0.95.2023101102` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| February 29, 2024|
| Neat Frame | `NFF1.20230928.0015` | N/A | Teams client: `1449/1.0.95.2023061601` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202306202019.product`| December 7, 2023|
Expand Down Expand Up @@ -273,6 +278,7 @@ The following are the latest firmware versions released via Microsoft Teams Admi
#### <b> EPOS </b>
| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date|
|:----------------|:-------------------|:----------------------------|:--------------------------------------------------------------------|:-------------------------------|
| Expand Control 3P | `v2.1.24185.04` | N/A| Teams client: `1449/1.0.97.2024061108` <br> Company Portal: `5.0.6152.0` <br> Admin Agent: `1.0.0.202402202353.product`| August 8, 2024|
| Expand Control 3P | `v1.9.24025.01` | N/A| Teams client: `1449/1.0.97.2023111003` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202310260109.product`| February 19, 2024|
| Expand Control 3P | `v1.8.23258.01` | N/A| Teams client: `1449/1.0.97.2023080401` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202306202019.product`| October 17, 2023|
| Expand Control 3P | `v1.7.23195.06` | N/A| Teams client: `1449/1.0.97.2023060102` <br> Company Portal: `5.0.5484.0` <br> Admin Agent: `1.0.0.202305022347.product`| July 31, 2023|
Expand Down
12 changes: 10 additions & 2 deletions Teams/meeting-recording.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ When a meeting is recorded:
- People invited to the meeting have permissions to view the recording (guests and external attendees can view the recording only if the recording is explicitly shared with them).
- Microsoft Purview compliance, OneDrive file storage, and access permissions apply to the meeting recording files the same as with other files.
- It's linked in the chat for the meeting.
- It's displayed in the Recordings and Transcripts tab for the meeting in Teams calendar.
- It's displayed in the **Recordings and Transcripts** tab for the meeting in Teams calendar.
- It's added to various file lists across Microsoft 365: Shared with me, office.com, Recommended, Recent, etc.
- Microsoft 365 Search indexes it

Expand Down Expand Up @@ -218,10 +218,18 @@ You shouldn't rely on meeting expiration settings for legal protection since end

#### Recording expiration settings and Microsoft 365 retention policies in Microsoft Purview

File retention takes precedence over file deletion. A Teams meeting recording expiration policy can't delete a Teams meeting recording with a Purview retention policy until after the retention period is completed. For example, if you have a Purview retention policy that says a file will be kept for five years and a Teams meeting recording expiration policy set for 60 days, the Teams meeting recording expiration policy permanently deletes the recording after five years.
#### File retention vs expiration policies

File retention takes precedence over file deletion. A Teams meeting recording expiration policy can't delete a Teams meeting recording with a Purview retention policy until after the retention period is completed. For example, if you have a Purview retention policy that says a file will be kept for five years and a Teams meeting recording expiration policy set for 60 days, the Teams meeting recording expiration policy permanently deletes the recording after five years.

Once the recording reaches the expiration date, it gets deleted from the user’s OneDrive, and is copied to the tenant's Preservation Hold library. Your users can't see the recording in OneDrive anymore, but as an admin, only you can find the recording in the Preservation Hold library. To learn more about the Preservation Hold library, see [Learn about retention for SharePoint and OneDrive](/purview/retention-policies-sharepoint#how-retention-works-for-sharepoint-and-onedrive).

#### Expiration vs deletion policies

If you have a Teams meeting recording expiration policy and Purview deletion policy with different deletion dates, the file is deleted at the earliest of the two dates. For example, if you have a Purview deletion policy that says a file will be deleted after one year and a Teams meeting recording expiration set for 120 days, the Teams meeting recording expiration policy will delete the file after 120 days.

#### Deleting recordings before the expiration date

Users can manually delete their recordings before the expiration date unless there's a Purview retention policy that prevents it. If a user manually deletes a recording that's still in the retention period, the recording is held in the Preservation Hold library. However, the recording shows as deleted to the end user. To find out more, see [Learn about retention for SharePoint and OneDrive](/microsoft-365/compliance/retention-policies-sharepoint).

### Deletion of recordings
Expand Down
14 changes: 14 additions & 0 deletions Teams/rooms/android-app-firmware.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,9 @@ The following are the latest firmware versions released via Microsoft Teams Admi

| Device model | Latest Firmware version | Minimum Firmware version required| Teams client | Company Portal | Admin Agent | Release date |
|:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|
| EPOS EXPAND Vision 5T |`v2.1.24193.02`| N/A | `1449/1.0.96.2024061103`| `5.0.6152.0` | `1.0.0.202402202353.product`| August 6, 2024|
| EPOS EXPAND Control 3C |`v2.0.24185.02`| N/A | `1449/1.0.96.2024061103`| `5.0.6152.0` | `1.0.0.202402202353.product`| August 6, 2024|
| EPOS EXPAND Vision 3T |`v2.1.24193.02`| N/A | `1449/1.0.96.2024032804`| `5.0.6152.0` | `1.0.0.202402202353.product`| August 6, 2024|
| EPOS EXPAND Vision 5T |`v2.0.24113.02`| N/A | `1449/1.0.96.2024032804`| `5.0.5484.0` | `1.0.0.202402202353.product`| February 20, 2024|
| EPOS EXPAND Control 3C |`v2.0.24113.03`| N/A | `1449/1.0.96.2024032804`| `5.0.5484.0` | `1.0.0.202402202353.product`| February 8, 2024|
| EPOS EXPAND Vision 5T |`v1.9.23365.01`| N/A | `1449/1.0.96.2023062301`| `5.0.5484.0` | `1.0.0.202310260109.product`| February 20, 2024|
Expand Down Expand Up @@ -350,6 +353,17 @@ The following are the latest firmware versions released via Microsoft Teams Admi

| Device model | Latest Firmware version | Minimum Firmware version required| Teams client | Company Portal | Admin Agent | Release date | Cloud |
|:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:----------------------------------|
| Cisco Board Pro 55 | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Board Pro 75 | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Room Bar | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Room Kit Pro | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product`| August 6, 2024| GCCH|
| Cisco Desk Pro | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Room Bar Pro | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Room Kit EQ | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Navigator | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Room Kit EQX | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Board Pro G2 55 | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Board Pro G2 75 | `11.17.1.11` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 6, 2024| GCCH|
| Cisco Board Pro 55 | `11.16.1.10` | N/A | `1449/1.0.96.2024042606` | `5.0.6061.0` | `1.0.0.202402202353.product` | June 26, 2024| GCCH|
| Cisco Board Pro 75 | `11.16.1.10` | N/A | `1449/1.0.96.2024042606` | `5.0.6061.0` | `1.0.0.202402202353.product` | June 26, 2024| GCCH|
| Cisco Room Bar | `11.16.1.10` | N/A | `1449/1.0.96.2024042606` | `5.0.6061.0` | `1.0.0.202402202353.product` | June 26, 2024| GCCH|
Expand Down
18 changes: 12 additions & 6 deletions Teams/rooms/rooms-licensing.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ ms.author: tonysmit
author: mstonysmith
manager: pamgreen
ms.reviewer: kspiess
ms.date: 08/1/2023
ms.date: 08/08/2024
ms.topic: article
audience: Admin
ms.service: msteams
Expand Down Expand Up @@ -47,7 +47,10 @@ A Teams Room system can be one of the following:

The remote administration tasks you perform on a Teams Rooms system or device in the Teams admin center depend on the license that's assigned the system or device. For more information, see [Microsoft Teams Rooms license overview in Teams admin center](admin-center-license-overview.md).

[!INCLUDE [mtr-user-licensing](../includes/mtr-user-licensing.md)]
> [!IMPORTANT]
> - Microsoft Teams Rooms devices need specific licenses like "Microsoft Teams Rooms Pro" or "Microsoft Teams Rooms Basic" to work. Other user licenses won't function with meeting devices. Meeting devices without a Teams Rooms license will be unable to sign in until they obtain one.
> - Microsoft Teams Shared Devices licenses are not supported with Teams Rooms devices. Only assign Teams Rooms Basic or Teams Rooms Pro licenses to these devices (Teams Rooms legacy licenses are also acceptable).

## Teams Rooms license service plan comparison

Expand Down Expand Up @@ -208,11 +211,14 @@ If you encounter devices showing an incorrect “unlicensed” status even thoug
- For MTR-A devices, kindly open an incident with the TAC team to ensure that the correct account information is sent to the service.


### Assigning additional licenses:
## Assigning additional licenses:

Teams Rooms licenses include all necessary services for Teams Rooms functionality, and additional licenses are neither needed nor supported for these devices, with the exception of telephony. Customers requiring outbound calling features should purchase an appropriate calling plan for the device or configure direct routing for the room account.

Teams Rooms devices managed by central IT should not be assigned any licenses beyond Microsoft Teams Rooms Pro, Microsoft Teams Rooms Basic and those required for calling. However, if a device is used by an executive to conduct meetings and access their personal calendar, it is permissible to set up the executive's user account on the device, provided the device also has a valid Microsoft Teams Rooms Pro license. The executive's account needs to satisfy the device's authentication requirements. Signing in with a user account doesn’t provide personal device experience on the device. An IT administrator should independently evaluate this scenario to determine if it aligns with company policies and permits such exceptions.

Teams rooms licenses contain all services needed for Teams rooms functions and additional licenses are not needed or supported with Teams Rooms devices. This excludes telephony, and customers with calling needs should purchase a calling plan to assign to the device, or set up direct routing for the room account. A Teams rooms device managed by central IT should not assign any other licenses than needed for calling. However, in some instances, where a device is used by an executive to conduct meetings using a Teams rooms device and access to their personal calendar is desired, the executive's user account can be set up on the device as long as device also has a valid Microsoft Teams Rooms Pro license. Using a user account on a Teams rooms device would require the account to meet authentication requirements as needed by the device and will still provide room specific experience on the device. An IT administrator should perform an independent evaluation of this scenario and decide if their company policies allow for this exception.

> [!IMPORTANT]
> - Microsoft Teams rooms are not personal devices and should not be considered or used as such.
> - Don't assign Microsoft OneDrive for Business licenses to a Teams rooms account when the resource account for the Teams rooms device is managed by your IT department. Doing so has the potential of saving user owned content on the room's OneDrive for Business (such as recordings, transcripts and Whiteboards in cases where room starts the meeting or session and invites end users to the session) and provides challenges for content management.
> - Microsoft Teams rooms are communal devices and should not be regarded or utilized as personal ones.
> - Avoid assigning Microsoft OneDrive for Business licenses to a Teams rooms account if the resource account is IT-managed. This can prevent user content, like recordings or transcripts, from being saved on the room's OneDrive, ensuring better content management.
2 changes: 1 addition & 1 deletion Teams/rooms/teams-devices-feature-comparison.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ To help guide you as to what features are available on different platforms, you
| | Partner Delegation | Not available | Not available |
| | Autopilot + Autologin | Not available | Not available |
| | One Time Passcode | Available | Not available |
| | ServiceNow Integration | Not available | Available |
| | ServiceNow Integration | Not available | Not available |
| | Device grouping & Role-based access control | Available | Available |
| | Device Settings Management | Available | Not available |
| | Update Management | Available | Not available |
Expand Down
12 changes: 8 additions & 4 deletions Teams/tmr-meeting-recording-change.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,11 @@ For **shared accounts** and **Microsoft Teams Rooms meetings**, if the organizer

To understand what happens if an organizer doesn't have a OneDrive account, see the **Recording storage for organizers without OneDrive accounts** section in this article.

To learn more about Microsoft Teams Rooms meetings, see [Microsoft Teams Rooms (Windows)](https://support.microsoft.com/office/microsoft-teams-rooms-windows-e667f40e-5aab-40c1-bd68-611fe0002ba2). For details on shared accounts, see [About shared mailboxes - Microsoft 365 admin](/microsoft-365/admin/email/about-shared-mailboxes).
To learn more about Microsoft Teams Rooms meetings, see [Microsoft Teams Rooms (Windows)](https://support.microsoft.com/office/microsoft-teams-rooms-windows-e667f40e-5aab-40c1-bd68-611fe0002ba2). For details on shared accounts, see [About shared mailboxes - Microsoft 365 admin](/microsoft-365/admin/email/about-shared-mailboxes).

### Automatically recorded meetings

For meetings that are automatically recorded, the recording is temporarily saved to async media storage.

### Videos

Expand All @@ -66,9 +70,9 @@ To learn how to apply retention labels to Teams meeting recordings, see [How to

If the organizer doesn’t have a OneDrive account, here's what happens, in order, to the meeting recording:

1. The recording is saved to the co-organizers' OneDrive. If there are multiple co-organizers, the recording is saved to the co-organizers' OneDrive, according to the first letter of each co-organizer's user ID. To see the user IDs for users in your org, see [Get-TeamUser](/powershell/module/teams/get-teamuser).
2. If none of the co-organizers have OneDrive accounts, the recording is saved to the OneDrive account of the user who initiated the recording. However, for meetings that are automatically recorded, the recording is temporarily saved to async media storage.
3. If the user who initiated the recording doesn’t have a OneDrive, the recording gets temporarily stored to async media storage.
1. The recording is saved to the co-organizer's OneDrive. When there are multiple co-organizers, the recording saves to the co-organizers' OneDrive, ordered by the first number in each co-organizer's Entra object ID. The meeting or event organizer has permissions to edit and share the recording. To find the object IDs for users in your org, see [Locate important IDs for a user](/partner-center/account-settings/find-ids-and-domain-names#find-the-user-object-id).
2. If none of the co-organizers have OneDrive accounts, the recording is saved to the OneDrive account of the user who initiated the recording.
3. If the user who initiated the recording doesn’t have a OneDrive, the recording gets temporarily stored to async media storage.

### Async media storage

Expand Down

0 comments on commit 74a3976

Please sign in to comment.