Merge pull request #16692 from MicrosoftDocs/main

Publish main to live, 02/24/25, 10:30 AM PT

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

@@ -3,7 +3,7 @@ title: Adobe Acrobat as a default PDF viewer in Teams
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.service: msteams
 audience: admin
 ms.subservice: teams-apps

Teams/app-centric-management.md

@@ -3,7 +3,7 @@ title: App centric management to manage user access to Teams apps
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 audience: admin
 ms.service: msteams
 ms.subservice: teams-apps

Teams/app-permissions.md

@@ -3,7 +3,7 @@ title: Microsoft Teams apps permissions and consent
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: conceptual
+ms.topic: how-to
 audience: admin
 ms.service: msteams
 ms.subservice: teams-apps

Teams/apps-update-experience.md

@@ -3,7 +3,7 @@ title: Microsoft Teams apps update experience and admin role
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: upgrade-and-migration-article
 ms.tgt.pltfrm: cloud
 ms.service: msteams
 ms.subservice: teams-apps

Teams/audit-app-management-activities.md

@@ -3,7 +3,7 @@ title: Search the audit logs of app management events
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.service: msteams
 ms.subservice: teams-apps
 audience: admin

Teams/customize-apps.md

@@ -3,7 +3,7 @@ title: Use app customization to brand the apps for your organization's needs
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.tgt.pltfrm: cloud
 ms.service: msteams
 ms.subservice: teams-apps

Teams/install-teams-apps.md

@@ -3,7 +3,7 @@ title: Preinstall Teams apps for your org users
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: conceptual
+ms.topic: how-to
 ms.service: msteams
 ms.subservice: teams-apps
 ms.custom: intro-get-started

Teams/m365-custom-connectors.md

@@ -3,7 +3,7 @@ title: Manage Microsoft 365 connectors and custom connectors
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.service: msteams
 ms.subservice: teams-apps
 audience: admin

Teams/manage-apps.md

@@ -3,7 +3,7 @@ title: Manage your apps in the Microsoft Teams admin center
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: conceptual
+ms.topic: how-to
 ms.service: msteams
 ms.subservice: teams-apps
 ms.custom: intro-get-started

Teams/purchase-third-party-apps.md

@@ -3,7 +3,7 @@ title: Purchase third-party apps and manage subscriptions and licenses
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.service: msteams
 ms.subservice: teams-apps
 audience: admin

Teams/submit-approve-custom-apps.md

@@ -3,7 +3,7 @@ title: Use the Teams App Submission API to submit and approve your custom apps
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.tgt.pltfrm: cloud
 ms.service: msteams
 ms.subservice: teams-apps

Teams/teams-app-permission-policies.md

@@ -3,7 +3,7 @@ title: Manage app permission policies in Microsoft Teams
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.tgt.pltfrm: cloud
 ms.service: msteams
 ms.subservice: teams-apps

Teams/teams-app-setup-policies.md

@@ -3,7 +3,7 @@ title: Manage app setup policies in Microsoft Teams
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.tgt.pltfrm: cloud
 ms.subservice: teams-apps
 ms.service: msteams

Teams/teams-client-health-update-monitoring.md

@@ -0,0 +1,102 @@
+---
+title:  Update monitoring in the Teams admin center
+ms.author: heidip
+author: MicrosoftHeidi
+manager: jtremper
+ms.topic: article
+ms.date: 02/24/2025
+ms.service: msteams
+audience: admin
+ms.collection: 
+- M365-collaboration
+- m365initiative-deployteams
+ms.reviewer: shals
+search.appverid: MET150
+f1.keywords:
+- NOCSH
+description: Monitoring for updates for the Teams client using the Teams admin center.
+appliesto: 
+- Microsoft Teams
+ms.localizationpriority: medium
+---
+
+# Microsoft Teams update monitoring
+
+[!INCLUDE [new-feature-teams-admin-center](includes/new-feature-teams-admin-center.md)]
+
+As an admin, it’s important that your users have the latest and the most secure version of the Teams client. Teams update monitoring in the Teams admin center allows you to proactively monitor Teams client updates and versions. It also helps identify users who aren't on latest version of Teams, so you can support them.
+
+This dashboard highlights the client update status for the devices in your tenant and gives Microsoft recommended insights for moving users to the latest version of Teams client.
+
+## Access the Teams update dashboard
+
+To access the update monitoring and insights dashboard:
+
+1. Go to the Teams admin center and login with your Admin credentials.
+1. Select **Teams client health** from the navigation pane on the left-hand side of the window.
+
+:::image type="content" source="media/teams-client-health-main-page-alt.png" alt-text="A screenshot of the Teams client health page with callouts marked. The first callout is over the page title. The second callout is on the upper middle of a table showing details. The number three is to the upper right of this table next to search, settings, and export options.":::
+
+- Callout 1: The Client update widget displays the overall version status distribution for all devices in your tenant. The update status widget provides statuses by three categories:
+  - Latest Build: A device is running a Teams client build newer than the last 100% released build.
+  - One or more builds behind: A device is running a Teams client build less than 30 days old and older than the last stable build.
+  - Outdated: A device is running a Teams client build less than 90 days old and more than 30 days old.
+- Callout 2: The table under the **Health tab** shows a more detailed breakdown of this information, such as:
+  - Client versions: The exact client version number.
+  - Release Date: The date this specific client version was fully released to the general ring.
+  - Version status: The Teams client version status.
+  - Platform: The platform for the client version.
+  - Devices on this version: The total devices in the tenant currently running this client version.
+  - Users on this version: The total number of users in the tenant currently running this client version.
+  - Percentage of total users: The percentage of total users in the tenant currently running the client version.
+  - Device Crashes: The total number of devices that experienced a client crash in the last 28 days.
+  - Device launch failures: The total number of devices that experienced a client launch failure in the last 28 days.
+- Callout 3: You can use these buttons to:
+  - Export the table to a CSV file.
+  - Filter and search by versions.
+  - Manage settings for columns in the table.
+
+### Client version details
+
+You can see your organization's client version distribution and adoption of each client version and the health of each client version in your organization. To view a detailed dashboard with insights, select any version from the health table from a row in this table.
+
+You can identify users and devices running outdated version of Teams, and review troubleshooting insights on issues preventing users from updating to a newer version of Teams.
+
+:::image type="content" source="media/teams-client-version-details-page.png" alt-text="A screenshot of the version details page, with callouts. The first callout, on the top left-hand side, is the client version. The second callout, underneath the first, is the date of release. The third callout, to the immediate right of the second, is the Teams client version. The fourth callout, in the middle underneath the third, has charts showing trends. The fifth, center of the screenshot, shows a table with details. The sixth, to the middle right, shows search, settings, and export options.":::
+
+- Callout 1: Client versions - The exact client version number.
+- Callout 2: Release Date - The date this specific client version was fully released to the general ring.
+- Callout 3: Version status - The Teams client version status.
+- Callout 4:
+  - Devices on this version trend: The trend of devices adopting this client version the last 28 days.
+  - Device crashes trend: The trend of devices experiencing client crashes on this version in the last 28 days.
+  - Device launch failure trend: The trend of devices experiencing client launch failures on this version in the last 28 days.
+- Callout 5: The table provides the following data:
+  - User: The username.
+   - Ring: The ring that the user is currently using.
+   - Device: The device name
+   - Platform: The platform the user is running Teams client on.
+   - Platform details: Operating system details.
+   - Insight: If the user experienced an update failure and is running an outdated version of Teams.
+   - Last Activity: The timestamp of the last active update.
+- Callout 6: You can search or filter for any client versions. You can also sort and export the dashboard's table in a CSV file.
+
+## Client health per user
+
+You can also monitor Client health per user from the user’s page.
+
+1. Go to **Teams** > **Users** > **Manage users** page.
+1. Select any user account.
+1. Select the **Client health** tab.
+
+:::image type="content" source="media/teams-client-per-user-view.png" alt-text="A screenshot of the per-user view, with numbered callouts. The first callout is slightly to the right of the middle of the screenshot, over the Client health tab. The second callout is directly underneath the first, above a table. The third is on the middle right of the screenshot, above the search, settings, and export options.":::
+
+- Callout 1: The Client health tab, which provides key health and update information for all clients used by the user.
+- Callout 2: The table shows the following information:
+  - Client versions: The exact client version number.
+  - Release Date: The date on which this specific client version was fully released to the general ring.
+  - Version status: The client version status of the Teams client.
+  - Devices: The device name that the user is currently running this Teams client on.
+  - Device Crashes: The number of total crashes experienced by this client version on the user’s specific device in the last seven days.
+  - Device launch failures: Total launch failures experienced by this client version on the user's specific device in the last seven days.
+- Callout 3: You can search or filter for any client versions. You can also sort and export the dashboard's table in a CSV file.

Teams/teams-client-health.md

@@ -0,0 +1,89 @@
+---
+title: The Teams client health dashboard in the Teams admin center
+ms.author: heidip
+author: MicrosoftHeidi
+manager: jtremper
+ms.topic: article
+ms.date: 02/24/2025
+ms.service: msteams
+audience: admin
+ms.collection: 
+- M365-collaboration
+- m365initiative-deployteams
+ms.reviewer: shals
+search.appverid: MET150
+f1.keywords:
+- NOCSH
+description: How to configure and use the health page in the Teams admin center to manage clients using monitoring and informational advice specific to situations.
+appliesto: 
+- Microsoft Teams
+ms.localizationpriority: medium
+---
+
+# Teams client health dashboard in the Teams admin center
+
+[!INCLUDE [new-feature-teams-admin-center](includes/new-feature-teams-admin-center.md)]
+
+This article provides an overview of the new Teams client health dashboards and tools for managing Teams clients in the Microsoft Teams admin center.
+
+Teams client health is an all-new page with a set of data, insights, and tools to help administrators troubleshoot and resolve issues. When a Teams application experiences an issue, end-users typically reach out to their admins. As an admin, you may have many requests from end-users. These requests can leave you in a reactive position with limited information to diagnose and resolve problems effectively.
+
+You may need to proactively monitor for issues. You may also need to perform remediation actions to manage and fix issues before they impact your end user productivity or cause further escalations.
+
+## Access the Teams client health dashboard
+
+To access the Teams client health dashboard, follow these steps:
+
+1. Go to the Teams admin center.
+1. Select **Teams client health** from the navigation pane.
+
+The Teams client health page displays an overview of Teams client health along with more information when you go into the details.
+
+:::image type="content" source="media/teams-client-health-main-page.png" alt-text="A screenshot of the client health page with four callout boxes marked. Box 1 is at the top of the page next to Client health. Box 2 is on the top right next to Top issues. Box 3 is on the lower middle above the issues list. Box 4 is on the lower right next to the search, settings, and export options.":::
+
+The **Client health** widget displays key health metrics like device crashes and launch failure trends for the last 28 days for all devices in your tenant.
+
+> [!NOTE]
+> This widget only surfaces health markers that are end-user impacting and actionable by administrators.
+ 
+Here are more details on each metric:
+
+- Callout 1: This widget shows Client health trends across the health metric:
+    - **Crashes**: The number of devices experiencing Teams app crashes per day within the last 28 days. Supported for Windows (non-VDI) and Mac Applications.
+    - **Launch failures**: The number of devices experiencing Teams app launch failures per day within the last 28 days.
+    > [!NOTE]
+    > Supported for Windows (non-VDI) and Mac applications.
+- Callout 2: This widget shows the top issues experienced by users in the organization:
+    - Device reported crashes: The number of devices that experienced crashes in the last seven days. The number of devices that experienced crashes in last 28 days.
+    - Device reported launch failures: The number of devices that experienced launch failures in the last seven days. The number of devices that experienced launch failures in the last 28 days.
+    - Device reported update failures: The number of devices that experienced update failures in last seven days. The number of devices that experienced update failures in last 28 days.
+- Callout 3: This table provides the following data:
+    - Issue: Problems impacting devices and users in the tenant.
+    - Insights: Insights on potential reasons behind these problems.
+    - Impacted Devices in the last seven days (%): The number of devices that experienced the issue in the last seven days and the percentage of the device base impacted in the organization.
+    - Affected users in the last seven days (%): The number of users who experienced the issue in the last seven days and the percentage of the user base impacted in the organization.
+    - Impacted Devices in the last 28 days (%): The number of devices that experienced the issue in the last 28 days and the percentage of the device base impacted in the organization.
+    - Affected users in the last 28 days (%): The number of users who experienced the issue in the last 28 days and the percentage of the user base impacted in the organization.
+    - Suggested Actions: Recommended mitigation guidance to troubleshoot and fix the issue. 
+- Callout 4: You can use these buttons to:
+    - Export the table to a CSV file.
+    - Filter by issue or insight.
+    - Access settings for the columns in the table.
+
+:::image type="content" source="media/teams-client-issue-details-page.png" alt-text="A screenshot of a details page, with callouts marked. The first callout is next to the title for the page, and says Crash. The second callout is below the title and indicates what's behind this issue. The third callout is next to a link to help fix the issue. The fourth callout is at the top of the list of users experiencing the issue with details about them. The fifth callout is on the upper right-hand side of the page, with the filter, settings, and export options.":::
+
+- Callout 1: Issue type - The category of issue impacting users and devices.
+- Callout 2: Insight - The insight or reason leading users and devices to experience the issue.
+- Callout 3: Mitigation link - This link points to Microsoft recommended mitigation and guidance to resolving the issue.
+- Callout 4: The table provides the following data:
+    - Client version - The Teams client version the user is currently on.
+    - Version status - The client version status of the Teams client the user is running on.
+    - Ring - The ring the user is a part of.
+    - Device - Details about the device the user is currently using.
+    - Device crashes - The number of devices that experienced crashes in last seven days.
+    - Device launch failures - The number of devices that experienced launch failures in the last seven days.
+    - Updated on (UTC) - The time stamp when this information was last refreshed.
+- Callout 5: You can use these buttons to:
+    - Export the table to a CSV file.
+    - Filter and search by versions.
+    - Manage settings for columns in the table.

Teams/teams-custom-app-policies-and-settings.md

@@ -3,7 +3,7 @@ title: Manage custom app policies and settings
 author: surbhigupta12
 ms.author: surbhigupta
 manager: prkosh
-ms.topic: article
+ms.topic: how-to
 ms.tgt.pltfrm: cloud
 ms.subservice: teams-apps
 ms.service: msteams

Teams/toc.yml

@@ -523,6 +523,12 @@ items:
               href: alerts/alerts-in-progress-meeting-video.md
             - name: Alerts for screen sharing issues
               href: alerts/alerts-in-progress-meeting-screen-sharing.md
+    - name: Teams client supportability tools
+      items:
+        - name: Teams client health
+          href: teams-client-health.md
+        - name: Update monitoring
+          href: teams-client-health-update-monitoring.md
 
     - name: Teams alerting and monitoring
       href: alerts/teams-admin-alerts.md