Merge pull request #15602 from MicrosoftDocs/main

Publish main to live 09/16/2024, 3:30 PM

.openpublishing.redirection.json

@@ -5164,6 +5164,16 @@
   "source_path": "Teams/education-insights-sis-data-sync.md",
   "redirect_url": "/microsoftteams/expand-teams-across-your-org/teams-for-education-landing-page",
   "redirect_document_id": false
+},
+{  
+  "source_path": "Teams/rooms/updates.md",
+  "redirect_url": "/microsoftteams/rooms/update-management",
+  "redirect_document_id": false
+},
+{  
+  "source_path": "Teams/devices/check-in-and-room-release.md",
+  "redirect_url": "/microsoftteams/devices/check-in-and-auto-release",
+  "redirect_document_id": false
 }
-] 
+]
 }

Teams/aa-cq-cqd-historical-reports.md

@@ -75,39 +75,39 @@ When completed, you're able to [configure a scheduled refresh](/power-bi/connect
 
 Use one of the following methods to control access to the historical reports:
 
-1. Voice applications policy
+- Voice applications policy
 
-To control which Auto attendants, Call queues and Agents users can report on without providing them access to Teams admin center, create a voice applications policy that grants them access to historical reporting and assign them as an Authorized user to the appropriate Auto attendants and Call queues.
+  To control which Auto attendants, Call queues and Agents users can report on without providing them access to Teams admin center, create a voice applications policy that grants them access to historical reporting and assign them as an Authorized user to the appropriate Auto attendants and Call queues.
 
-For more information, see [Plan for Auto attendant and Call queue authorized users](./aa-cq-authorized-users-plan.md).
+  For more information, see [Plan for Auto attendant and Call queue authorized users](./aa-cq-authorized-users-plan.md).
 
-> [!TIP]
-> Using the voice applications policy to control access is the recommended approach.  With the voice applications policy and Authorized users it is possible to control which Auto attendants, Call queues, and Agents a user can report on. If necessary, the policy still allows a user to report on all Auto attendants, Call queues, and Agents without providing access to Teams admin Center.
+  > [!TIP]
+  > Using the voice applications policy to control access is the recommended approach.  With the voice applications policy and Authorized users it is possible to control which Auto attendants, Call queues, and Agents a user can report on. If necessary, the policy still allows a user to report on all Auto attendants, Call queues, and Agents without providing access to Teams admin Center.
 
-Create, or modify, a voice applications policy that enables the historical reporting permissions. Assign the policy to the appropriate users. Assign the users as authorized users to the appropriate auto attendants and call queues. For more information, see [Manage voice applications policies in Microsoft Teams](./manage-voice-applications-policies.md)
+  Create, or modify, a voice applications policy that enables the historical reporting permissions. Assign the policy to the appropriate users. Assign the users as authorized users to the appropriate auto attendants and call queues. For more information, see [Manage voice applications policies in Microsoft Teams](./manage-voice-applications-policies.md)
 
-The historical reporting permissions can only be set through PowerShell and will be available in Teams admin center later this year. 
+  The historical reporting permissions can only be set through PowerShell and will be available in Teams admin center later this year. 
 
-For more information, see:
+  For more information, see:
 
-|New voice applications policy           |Existing voice applications policy |
-|:---------------------------------------|:----------------------------------|
-| [New-CsTeamsVoiceApplicationsPolicy/-HistoricalAutoAttendantMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#-HistoricalAutoAttendantMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalAutoAttendantMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#-HistoricalAutoAttendantMetricsPermission) |
-| [New-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission) |
-| [New-CsTeamsVoiceApplicationsPolicy/--HistoricalAgentMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission) |
+  |New voice applications policy           |Existing voice applications policy |
+  |:---------------------------------------|:----------------------------------|
+  | [New-CsTeamsVoiceApplicationsPolicy/-HistoricalAutoAttendantMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#-HistoricalAutoAttendantMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalAutoAttendantMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#-HistoricalAutoAttendantMetricsPermission) |
+  | [New-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#-HistoricalCallQueueMetricsPermission) |
+  | [New-CsTeamsVoiceApplicationsPolicy/--HistoricalAgentMetricsPermission](/powershell/module/teams/new-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission)  | [Set-CsTeamsVoiceApplicationsPolicy/-HistoricalCallQueueMetricsPermission](/powershell/module/teams/set-csteamsvoiceapplicationspolicy#--HistoricalAgentMetricsPermission) |
 
-#### Known issues
+  #### Known issues
 
-If the voice applications policy assigned to a user only enables the historical reporting permissions, and optionally the real-time reporting permissions, then the user can't access the historical reports. Support is working to resolve this problem. In the interim, enable at least one Auto attendant and Call queue change permission in the policy. Enabling the Auto attendant **Business hours greeting** and Call queue **Welcome greeting** is suggested, but enabling any of the change permissions will work around this issue.
+  If the voice applications policy assigned to a user only enables the historical reporting permissions, and optionally the real-time reporting permissions, then the user can't access the historical reports. Support is working to resolve this problem. In the interim, enable at least one Auto attendant and Call queue change permission in the policy. Enabling the Auto attendant **Business hours greeting** and Call queue **Welcome greeting** is suggested, but enabling any of the change permissions will work around this issue.
 
-2. Call Quality Dashboard (CQD) pipeline [legacy]
+- Call Quality Dashboard (CQD) pipeline [legacy]
 
-If you want the user to report on **all** the Auto attendants, Call queues, and Agents in the tenant and you want to grant the user access to Teams admin center to run other Usage reports, assign the user a CQD access role with both **View Reports** and **View EUII fields** set to **Yes**.
+  If you want the user to report on **all** the Auto attendants, Call queues, and Agents in the tenant and you want to grant the user access to Teams admin center to run other Usage reports, assign the user a CQD access role with both **View Reports** and **View EUII fields** set to **Yes**.
 
-For more information, see [CQD access role](./turning-on-and-using-call-quality-dashboard.md#assign-admin-roles-for-access-to-cqd).
+  For more information, see [CQD access role](./turning-on-and-using-call-quality-dashboard.md#assign-admin-roles-for-access-to-cqd).
 
-> [!NOTE]
-> If a user is assigned a CQD access role and a voice applications policy, the CQD role will take precendence and the user will see all the Auto attendants, Call queues and Agents in the tenant.
+  > [!NOTE]
+  > If a user is assigned a CQD access role and a voice applications policy, the CQD role will take precendence and the user will see all the Auto attendants, Call queues and Agents in the tenant.
 
 ## V3.x.x desktop installation
 
@@ -125,25 +125,25 @@ Perform the following steps:
 
    :::image type="content" source="media/aa-cq-historical-report-01-v318.png" alt-text="Screenshot showing the DataSource, Report Level, and UTC Offset selections.":::
 
-    - **DataSource**: Select the `api.interfaces.records.teams.microsoft.com` entry.
-    - **Report Level**:
-        - Select `Per Call` (default) to retrieve all the individual call records.
-        - Select `Per Day` to retrieve an aggregated total for each day. 
-    - **UTC Offset**: Select the UTC offset that represents the time zone the reports are presented in. Only valid when the **Report Level** is set to `Per Call`
+   - **DataSource**: Select the `api.interfaces.records.teams.microsoft.com` entry.
+   - **Report Level**:
+     - Select `Per Call` (default) to retrieve all the individual call records.
+     - Select `Per Day` to retrieve an aggregated total for each day. 
+   - **UTC Offset**: Select the UTC offset that represents the time zone the reports are presented in. Only valid when the **Report Level** is set to `Per Call`
 
-    #### Per Day vs Per Call 
+   #### Per Day vs Per Call 
 
    - Per Call reporting retrieves the individual call records for each Auto attendant, Call queue, and Agent, the user is authorized for and makes them available in the Power BI client. Per Call reporting also allows call records to be displayed in the local time zone selected by the user. For some customers, especially those using the CQD access role to control access, this may result in hitting the 90,000 default or 200,000 per query record limit. In this case, the Per Day reporting option should be selected.
 
-    - Per Day reporting retrieves one daily summary record for each Auto attendant, Call queue, and Agent. This results in fewer records being returned to the client, reducing the possibility of hitting the 90,000 default or 200,000 per query record limit. Per Day reporting is based on a UTC-00:00 day (00:00:00-23:59:59 UTC) only and any UTC offset supplied by the user is ignored.
+   - Per Day reporting retrieves one daily summary record for each Auto attendant, Call queue, and Agent. This results in fewer records being returned to the client, reducing the possibility of hitting the 90,000 default or 200,000 per query record limit. Per Day reporting is based on a UTC-00:00 day (00:00:00-23:59:59 UTC) only and any UTC offset supplied by the user is ignored.
 
 5. Sign in with your Teams account.
    - Select **File**, then **Options and settings**, and then **Data source settings**.
    - Select **Edit Permissions**, and then **Edit**.
    - Select **Organizational account**, and then **Sign in**.
    - Select **Save**, then **OK**, and then **Close**.
 
-     :::image type="content" source="media/aa-cq-historical-report-03-v301.png" alt-text="Screenshot showing sign-in for V3.x.x.":::
+   :::image type="content" source="media/aa-cq-historical-report-03-v301.png" alt-text="Screenshot showing sign-in for V3.x.x.":::
 
 6. Select **Refresh**, in the ribbon bar and the data refreshes.
 

Teams/administrative-unit.md

@@ -2,20 +2,22 @@
 title: Manage devices with administrative units
 author: mstonysmith
 ms.author: tonysmit
-ms.reviewer: 
-ms.date: 07/14/2021
 manager: pamgreen
+ms.reviewer: ayerragangu
+ms.date: 09/16/2024
 ms.topic: article
 audience: admin
 ms.service: msteams
+ms.subservice: itpro-devices
+ms.collection: 
+  - teams-rooms-devices
+  - Teams_ITAdmin_Devices
+  - Tier1
 search.appverid: MET150
 description: Learn how to use administrative units in Microsoft Teams
 ms.localizationpriority: medium
 f1.keywords: 
   - NOCSH
-ms.collection: 
-  - M365-collaboration
-  - Teams_ITAdmin_Devices
 appliesto: 
   - Microsoft Teams
 ---

Teams/adobe-acrobat-pdf-viewer-teams.md

@@ -7,7 +7,7 @@ ms.topic: article
 ms.service: msteams
 audience: admin
 ms.subservice: teams-apps
-ms.date: 09/09/2024
+ms.date: 09/17/2024
 ms.collection: 
 - Teams_ITAdmin_Help
 - M365-collaboration
@@ -27,14 +27,14 @@ ms.localizationpriority: medium
 
 As an admin, you can set Adobe Acrobat as the default app to view and edit PDF files in Microsoft Teams. Your users can view and search the PDF files. The users can also comment on and annotate the PDF files for free after they sign in.
 
-To configure Adobe Acrobat app as the default handler for PDF files in your tenant, complete the following steps as prerequisites:
+To configure Adobe Acrobat app as the default handler for PDF files in your org, complete the following steps as prerequisites:
 
 * [Allow Adobe Acrobat app](#allow-adobe-acrobat-app-in-your-tenant).
 * [Install Adobe Acrobat app](#install-adobe-acrobat-app-for-all-users).
 
 ## Allow Adobe Acrobat app in your tenant
 
-To set up the app as a default PDF viewer, [allow third-party apps in your tenant](manage-apps.md#manage-org-wide-app-settings) and then follow these steps:
+To set up the app as a default PDF viewer, [allow third-party apps in your org](manage-apps.md#manage-org-wide-app-settings) and then follow these steps:
 
 1. Sign in to Teams admin center and access **Teams app** > **[Manage apps](https://admin.teams.microsoft.com/policies/manage-apps)**.
 
@@ -54,7 +54,7 @@ To assign and make the Adobe Acrobat app available for all users, follow these s
 
 1. Under **Manage policies** tab, select **Global (Org-wide default)**, and then select **Edit**.
 
-   :::image type="content" source="media/setup-policies.png" alt-text="Screenshot of setup policies for Adobe Acrobat app in Teams admin center.":::
+   :::image type="content" source="media/setup-policies.png" alt-text="Screenshot of setup policies for Adobe Acrobat app in Teams admin center." lightbox="media/setup-policies.png":::
 
 1. Under Installed apps, select **Add apps**.
 
@@ -64,7 +64,7 @@ To assign and make the Adobe Acrobat app available for all users, follow these s
 
 1. Select **Save**.
 
-1. Optionally, you can allow Single Sign-On (SSO) with Microsoft Entra identity if you own a license of Adobe Acrobat. We recommend configuring SSO using the instructions available at [Set up identity and single sign-on](https://helpx.adobe.com/enterprise/using/set-up-identity.html).
+1. Optionally, you can allow single sign-on (SSO) with Microsoft Entra identity if you own a license of Adobe Acrobat. We recommend configuring SSO using the instructions available at [Set up identity and single sign-on](https://helpx.adobe.com/enterprise/using/set-up-identity.html).
 
 After you complete the configuration, Teams uses Adobe Acrobat app as the default file handler for PDF files.
 
@@ -75,12 +75,12 @@ To selectively allow the Adobe Acrobat app for a few individuals or for a group,
 Know the following information about this functionality:
 
 * Typically, it [takes a few hours](teams-app-setup-policies.md#considerations-and-limitations) for the app to be available to users after you apply the app setup policy to users.
-* The PDF files that are pinned as tabs in channels and the PDF files available in the Assignments app continue to open in the native viewer of Teams and not in the Adobe Acrobat app.
+* Comment or annotate on the PDF without signing in. For a complete list of functionality and the prerequisites, see [Manage PDF files in Teams with Acrobat app](https://www.adobe.com/content/dam/dx-dc/pdf/ue/acrobat-msft-teams-feature-comp-ue.pdf).
+* The PDF files that are pinned as tabs in channels and the PDF files available in the `Assignments` app continue to open in the native viewer of Teams and not in the Adobe Acrobat app.
 * Adobe Acrobat as a default PDF viewer in Teams works only on desktop and web clients. It isn't supported on the mobile client.
 * Users need an Adobe Acrobat plan to use the premium tools such as Export PDF, Organize Pages, Combine Files, Compress PDF, and Protect PDF.
 * To uninstall the app, users can remove the app from their Teams client. Admin can remove the Adobe Acrobat app using setup policy.
 * If you block Adobe Acrobat app, then remove the app from the setup policy. It ensures that the user experience reverts to using the native PDF file viewer.
 * If you face any issues to sign in to the Adobe Acrobat app in the Teams desktop client, then use [Teams in browser](https://teams.microsoft.com/) to sign in.
-* Sign-in to a free [Adobe account](https://acrobat.adobe.com/us/en/) to comment or annotate on the PDF files. The app in Teams can offer functionality such as annotating, organizing, compressing, and protecting PDF files. For a complete list of functionality and the prerequisites, see [Manage PDF files in Teams with Acrobat app](https://www.adobe.com/content/dam/dx-dc/pdf/ue/acrobat-msft-teams-feature-comp-ue.pdf).
-* When you collaborate on a PDF document, it's stored for a short duration (for up to 24 hours) on the Adobe servers in the region in which you're located. This temporary storage is to facilitate transient processing. Your documents are encrypted end-to-end when being transferred from your local filesystem to the server and remain encrypted on the server as well. See [security for Acrobat](https://aka.ms/Adobe_Acrobat_Security).
+* For details on how your documents are secured, see [security for Acrobat](https://aka.ms/Adobe_Acrobat_Security).
 * Once Adobe Acrobat is made the default PDF file handler, then a PDF file clicked in Teams opens in Teams. Users can't open PDF files in their desktop app using any setting in Teams. Users can download PDF files locally and open those in other apps.

Teams/alerts/device-health-status.md

@@ -3,7 +3,7 @@ title: Microsoft Teams Devices Monitoring and Alerting
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: kimmatlock
+ms.reviewer: altsou
 ms.date: 08/21/2024
 ms.topic: article
 audience: Admin

Teams/custom-meeting-templates-overview.md

@@ -41,7 +41,7 @@ The following meeting options can be controlled by using a meeting template:
 |Allow mic and camera for attendees|Specifies if attendees can unmute and use their camera.|
 |*Recording & transcription*||
 |Recording|Specifies who can record and if the meeting is recorded automatically.|
-|Copilot|Specifies if Copilot is on or on with transcript|
+|Copilot|Specifies how transcripts are used for Microsoft 365 Copilot in Teams meetings and events.|
 |*Roles*||
 |Announce when people dialing in join or leave|Specifies if a sound plays when people calling in by phone join or leave the meeting.|
 |*Meeting engagement*||

Teams/devices/authentication-best-practices-for-android-devices.md

@@ -3,7 +3,7 @@ title: Authentication best practices for Microsoft Teams shared device managemen
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: tjaved
+ms.reviewer: dimehta
 ms.date: 05/07/2024
 ms.topic: article
 ms.service: msteams

Teams/devices/check-in-and-room-release.md → Teams/devices/check-in-and-auto-release.md

@@ -3,7 +3,7 @@ title: Check-in and auto release on Teams Panels
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: eveigrimshaw
+ms.reviewer: eviegrimshaw
 ms.date: 06/25/2024
 ms.topic: article
 audience: Admin

Teams/devices/common-area-mobile-phones.md

@@ -1,7 +1,7 @@
 ---
 title: Set up an Android mobile phone as a common area phone
-ms.author: tonysmit
 author: mstonysmith
+ms.author: tonysmit
 manager: pamgreen
 ms.reviewer: prashibadkur
 ms.date: 08/25/2024

Teams/devices/device-management.md

@@ -3,7 +3,7 @@ title: Manage devices in Microsoft Teams
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: kimmatlock
+ms.reviewer: srpall
 ms.date: 07/08/2024
 ms.topic: article
 ms.service: msteams

Teams/devices/device-store.md

@@ -1,7 +1,7 @@
 ---
 title: Teams device store
-ms.author: tonysmit
 author: mstonysmith
+ms.author: tonysmit
 manager: pamgreen
 ms.reviewer: pauljuricic
 ms.date: 08/08/2024

Teams/devices/hot-desking-teams-displays.md

@@ -3,7 +3,7 @@ title: Hot desking Teams displays
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: prashibadkur
+ms.reviewer: eviegrimshaw
 ms.date: 05/15/2024
 ms.topic: article
 ms.service: msteams

Teams/devices/manage-device-tags.md

@@ -3,7 +3,7 @@ title: Manage and filter Microsoft Teams device tags
 author: mstonysmith
 ms.author: tonysmit
 manager: pamgreen
-ms.reviewer: snchatur
+ms.reviewer: ayerragangu
 ms.date: 05/01/2024
 ms.topic: article
 ms.service: msteams