diff --git a/Teams/app-powered-tasks-in-planner.md b/Teams/app-powered-tasks-in-planner.md index bcc362fa6e..6a0a8ca50e 100644 --- a/Teams/app-powered-tasks-in-planner.md +++ b/Teams/app-powered-tasks-in-planner.md @@ -6,7 +6,7 @@ manager: jtremper ms.topic: conceptual ms.service: msteams ms.reviewer: andfried -ms.date: 12/10/2024 +ms.date: 12/17/2024 search.appverid: MET150 searchScope: - Microsoft Teams @@ -33,22 +33,22 @@ ms.collection: The app-powered tasks feature offers your organization more control over what users see when they open their tasks in the Planner app within Microsoft Teams. Instead of showing only the standard set of task fields, you can provide users with an experience tailored to the task at hand. That experience might be a workflow-specific set of fields or step-by-step guidance to walk the user through a workflow from beginning to end. To achieve this, you integrate a Teams app with the task and create these tasks programmatically. -Say, for example, users in your organization use a Teams app to track and complete inspections. You choose to integrate this inspections app with tasks so that a Planner task is created for each inspection tracked in the system. +Say, for example, users in your organization use a Teams app to track and complete inspections. You can integrate this inspections app with tasks so that a Planner task is created for each inspection tracked in the system. - When a user opens one of these tasks from the Planner app in Teams, they see a simplified screen with a button to jump directly to the inspection experience powered by your inspections app. -- When they complete the task and exit the inspections experience, they're right back in Planner where they started. +- When they complete the task and close the inspections experience, they're right back in Planner where they started. Users get the tailored experience that a Teams app provides right from within their assigned tasks. They don't have to navigate to a different app to get work done or lose context of where they were when working with their tasks. -In addition to these benefits when users complete tasks, the app-powered tasks feature allows organizations to reflect required line-of-business (LOB) processes and workflows as tasks, so employees can see all tasks assigned to them from a single place. +In addition to these benefits when users complete tasks, the app-powered tasks feature allows organizations to reflect required line-of-business processes and workflows as tasks, so employees can see all the work they're accountable for from a single place. -This experience is supported in the Planner app on Teams web, desktop, and mobile. You can update any Teams app to create app-powered tasks and provide tailored task experiences for your users. +This experience is supported in the Planner app on Teams web, desktop, and mobile. You can provide tailored task experiences for your users with any Teams app that meets the following requirements. ## Requirements App-powered tasks is an extensibility feature that relies on programmatic creation and management of tasks. The requirements to use this feature are as follows. -- Each app-powered task must have a reference URL that points to an experience in a destination Teams app. We recommend that you point this reference URL to the specific item or screen the user should be working on. This reference URL must be added to the task in a specific way. To learn more, see the [Configure the reference URL](#configure-the-reference-url) section of this article. +- Each app-powered task points to an experience in a destination Teams app, which requires you to provide a reference URL to that experience. We recommend that you point this reference URL to the specific item or screen the user should be working on. This reference URL must be added to the task in a specific way. To learn more, see the [Step 1: Configure the reference URL](#step-1-configure-the-reference-url) section of this article. - Tasks must be created and updated using the [business scenarios](/graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta) API in Microsoft Graph. - Users who need to work with the task must have access to the destination app in Teams, as governed by the app policies you set in the Teams admin center. To learn more, see [Overview of app management and governance in Teams admin center](manage-apps.md). - The destination Teams app is responsible for managing the task lifecycle, which includes the following actions: @@ -59,19 +59,13 @@ App-powered tasks is an extensibility feature that relies on programmatic creati - Mark the task as Completed when all steps are done. See [Update businessScenarioTask](/graph/api/businessscenariotask-update?view=graph-rest-beta). - Delete the task. See [Delete businessScenarioTask](/graph/api/businessscenarioplanner-delete-tasks?view=graph-rest-beta). - This feature allows your destination Teams app to govern the lifecycle of the task because some workflows might not have deterministic flows. As a result, the Planner app doesn't know whether all required steps are completed. For example, a finding during an inspection might result in the inclusion of several more steps in the inspection. Similarly, users are prevented from updating task fields or marking the task as Completed. These actions might result in users making changes that conflict with what's reflected in your destination Teams app. +This feature allows your destination Teams app to govern the task lifecycle because some workflows might not have deterministic flows. As a result, the Planner app doesn't know whether all required steps are completed. For example, a finding during an inspection might result in the inclusion of several more steps in the inspection. Similarly, users are prevented from updating task fields or marking the task as Completed. These actions might result in users making changes that conflict with what's reflected in your destination Teams app. ## Create an app-powered task This section covers how to use the [Create businessScenarioTask](/graph/api/businessscenarioplanner-post-tasks) API to create an app-powered task. -Use the following HTTP POST request, where `{your-business-scenario-ID}` is your business scenario ID. - -```http -POST https://graph.microsoft.com/beta/solutions/businessScenarios/{your-business-scenario-ID}/planner/tasks -``` - -The following shows a request, with placeholders for the properties that you specify in the request body. +Use the following HTTP POST request. Here's what the request looks like, with placeholders for the properties that you specify. **Request** @@ -83,7 +77,7 @@ POST https://graph.microsoft.com/beta/solutions/businessScenarios/{your-business "target": { "@odata.type": "#microsoft.graph.businessScenarioGroupTarget", "taskTargetKind": "group", - "groupId": "{group ID of team}" + "groupId": "{group ID of the team where you want to create the task}" }, "businessScenarioProperties": { "externalObjectId": "{any unique ID, for example, the ID of the object in your destination app}", @@ -108,46 +102,32 @@ POST https://graph.microsoft.com/beta/solutions/businessScenarios/{your-business } ``` -### Define the attachment +The following sections walk through how to form the request in more detail. + +### How to define the properties in the request -What differentiates an app-powered task from a standard task is the presence of a specific attachment. The attachment contains a link (reference URL) to the destination experience in the Teams app, which enables Planner to recognize a task as an app-powered task. +A specific type of attachment differentiates an app-powered task from a standard task. The attachment must be of type `TeamsHostedApp` and must contain a specially formatted link (reference URL) to the destination experience in the Teams app. This signifies to Planner that the task is an app-powered task. Keep in mind that the API refers to these attachments as [references](/graph/api/resources/plannerexternalreferences?view=graph-rest-beta). -To define the attachment, specify the following properties in `"references"` in the request body. +First, you configure the reference URL to point to the destination experience. Then, specify the reference URL along with other required properties for the attachment in the request body. -```http - "references": { - "{reference-URL}": { - "@odata.type": "microsoft.graph.plannerExternalReference", - "alias": "{destination app name}", - "previewPriority": " !", - "type": "TeamsHostedApp" - } - } -``` - -|Property |Description| -|---------|---------| -|`reference-URL`| The URL to the destination experience, in Stageview Modal link syntax. For details on how to format and encode the URL, see the [Configure the reference URL](#configure-the-reference-url) section of this article.| -|`alias`|The name of your Teams app. When a user opens the task, they see a message that says, “Complete this task in \, and a **Start task** button to jump to the destination experience.| -|`previewPriority`|Leave as `!`.| -|`type`| Set to `TeamsHostedApp`.| +#### Step 1: Configure the reference URL -#### Configure the reference URL +The reference URL uses a specific format. Follow these steps to construct and then encode the URL. -##### Format the URL +##### Step 1a: Construct the URL The reference URL to the destination experience must use [Stageview Modal link syntax](/microsoftteams/platform/tabs/open-content-in-stageview) in the following format: `https://teams.microsoft.com/l/stage/{Teams-app-Id}/0?context={"contentUrl":"URL-to-destination-experience"},"name":"{page-title}","openMode":"modal"}` -Specify the following parameters in the reference URL. +To construct the reference URL, specify the following parameters. |Parameter |Description | |---------|---------| |`Teams-app-Id`|The app ID of the Teams app you're integrating with the task.| -|`URL-to-destination-experience`|The URL that points to the specific experience in your destination Teams app that you want users to see when they open the task. The domain of the URL must be a valid domain for the app ID. | +|`URL-to-destination-experience`|The URL that points to the target experience in your destination Teams app that you want users to see when they open the task. For security reasons, the URL must point to a valid domain associated with the Teams app, which is represented by the app ID you provide.| |`page-title`| The title that should appear at the top of the screen when the user is shown the URL to the destination experience.| Here's an example of a reference URL before encoding: @@ -162,7 +142,7 @@ In this example: If the YouTube app in Teams is available to you, you can send this URL to yourself and confirm it opens. -##### Encode the reference URL +##### Step 1b: Encode the URL You need to encode the reference URL before you can use it in the attachment. Percent encoding ensures the link is in a compatible format for programmatic use. @@ -184,9 +164,31 @@ Follow these steps to encode the reference URL. We use the example reference URL > [!NOTE] > If your URL points to a Power App, make sure it includes the `&source=teamstab` parameter to make single sign-on (SSO) work for Power Apps and the `&skipMobileRedirect=1` parameter to skip the screen that prompts users to open the standalone Power App player. +#### Step 2: Define the attachment + +To define the attachment, specify the following properties in `"references"` in the request body. + +```http + "references": { + "{reference-URL}": { + "@odata.type": "microsoft.graph.plannerExternalReference", + "alias": "{destination app name}", + "previewPriority": " !", + "type": "TeamsHostedApp" + } + } +``` + +|Property |Description| +|---------|---------| +|`reference-URL`| The URL to the destination experience, in Stageview Modal link syntax. For details on how to construct and encode the URL, see the [Step 1: Configure the reference URL](#step-1-configure-the-reference-url) section of this article.| +|`alias`|The name of your Teams app. When a user opens the task, they see a message that says, “Complete this task in \, and a **Start task** button to jump to the destination experience.| +|`previewPriority`|Leave as `!`.| +|`type`| Set to `TeamsHostedApp`. This is what signifies to Planner that the task is an app-powered task.| + ## Example -This example shows how to create an app-powered task named "Review security practices presentation" and assign it to a user named Adele Vance (user ID 44ee44ee-ff55-aa66-bb77-88cc88cc88cc). This request uses the reference URL example. +This example shows how to create an app-powered task named "Review security practices presentation" and assign it to a user named Adele Vance (user ID 44ee44ee-ff55-aa66-bb77-88cc88cc88cc). This request uses the example reference URL from the [Step 1: Configure the reference URL](#step-1-configure-the-reference-url) section of this article. **Request** @@ -223,9 +225,12 @@ POST https://graph.microsoft.com/beta/solutions/businessScenarios/ccd5aa8aebd048 } ``` +> [!NOTE] +> This example reference URL was chosen as an easy way to test the app-powered tasks experience using an app that's available in many organizations' environments. Keep in mind that with this example reference URL, users won't be able to complete the task. This is because the YouTube app isn't integrated with app-powered tasks and doesn't make an API call to mark the task complete after the video is played. + ### What this looks like in the Planner app -Here's what the user sees when they open the task in the Planner app in Teams. Selecting the **Start task** button takes the user to the destination experience in the Teams app. In this example, the experience is a security practices video in the YouTube app in Teams. +Here's what the user sees when they open the task in the Planner app in Teams. Selecting the **Start task** button takes the user to the destination experience in the Teams app. In this example, the destination experience is a security practices video in the YouTube app in Teams. :::image type="content" source="media/app-powered-tasks-in-planner.png" alt-text="Screenshot of an example of an app-powered task in My Tasks in the Planner app in Teams." lightbox="media/app-powered-tasks-in-planner.png"::: diff --git a/Teams/devices/certified-hardware-android.md b/Teams/devices/certified-hardware-android.md index 488914cea5..c796e5a252 100644 --- a/Teams/devices/certified-hardware-android.md +++ b/Teams/devices/certified-hardware-android.md @@ -152,6 +152,17 @@ For information about the latest Teams app releases, see [What's new in Microsof | Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Cisco Board Pro 55 | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Board Pro 75 | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Room Bar | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Room Kit Pro | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product`| December 16, 2024| +| Cisco Desk Pro | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Room Bar Pro | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Room Kit EQ | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Navigator | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Room Kit EQX | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Board Pro G2 55 | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| +| Cisco Board Pro G2 75 | `ce11.22.1.12` | N/A | `1449/1.0.96.2024101004` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 16, 2024| | Cisco Board Pro 55 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | November 4, 2024| | Cisco Board Pro 75 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | November 4, 2024| | Cisco Room Bar | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | November 4, 2024| @@ -540,6 +551,17 @@ For information about the latest Teams app releases, see [What's new in Microsof | Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | Cloud | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:----------------------------------| +| Cisco Board Pro 55 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Board Pro 75 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Room Bar | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Room Kit Pro | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product`| December 13, 2024| GCCH| +| Cisco Desk Pro | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Room Bar Pro | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Room Kit EQ | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Navigator | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Room Kit EQX | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Board Pro G2 55 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| +| Cisco Board Pro G2 75 | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | December 13, 2024| GCCH| | Cisco Board Pro 55 | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | September 27, 2024| GCCH| | Cisco Board Pro 75 | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | September 27, 2024| GCCH| | Cisco Room Bar | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | September 27, 2024| GCCH| @@ -625,6 +647,15 @@ For information about the latest Teams app releases, see [What's new in Microsof | Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | Cloud | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:---------------------------------| +| Poly Studio X30 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio X50 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio X52 | `4.3.2.422023` |`N/A` |`1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio X70 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio X72 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio G7500 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly Studio G62 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly TC8 | `6.3.2.211744` | N/A | `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | +| Poly TC10 | `6.3.2.211744` | N/A | `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| December 13, 2024|GCCH | | Poly Studio X30 | `4.2.0-396113` | `4.1.0_00.180034`| `1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| May 7, 2024| GCCH | | Poly Studio X50 | `4.2.0-396113` | `4.1.0_00.180034`| `1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| May 7, 2024| GCCH | | Poly Studio X52 | `4.2.0-396113` |`4.1.0.382189` |`1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| May 7, 2024| GCCH | diff --git a/Teams/devices/teams-panels-certified-hardware.md b/Teams/devices/teams-panels-certified-hardware.md index ff6321d675..ffcc01d5a5 100644 --- a/Teams/devices/teams-panels-certified-hardware.md +++ b/Teams/devices/teams-panels-certified-hardware.md @@ -132,6 +132,7 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Poly | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:---------------------------------------------------------------------------------|:---------------------------------------------| +| TC10 | `6.4.0-7000547` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| December 16, 2024| | TC10 | `6.3.2.211744` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| October 10, 2024| | TC10 | `6.3.0-211719` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| August 1, 2024| | TC10 | `5.0.1.211321` | N/A| Teams client: `1449/1.0.97.2023080401`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202306202019.product`| December 12, 2023| @@ -173,7 +174,8 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Poly | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:---------------------------------------------------------------------------------|:---------------------------------------------| -| TC10 | `6.3.0-211719` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| August 29, 2024| +| TC10 | `6.3.2.211744` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| December 13, 2024| GCCH| +| TC10 | `6.3.0-211719` | N/A| Teams client: `1449/1.0.97.2024042504`
Company Portal: `5.0.6061.0`
Admin Agent: `1.0.0.202402202353.product`| August 29, 2024| GCCH | ## [End of certification](#tab/eol) diff --git a/Teams/devices/teams-phones-certified-hardware.md b/Teams/devices/teams-phones-certified-hardware.md index e80c0a612b..2379a4a720 100644 --- a/Teams/devices/teams-phones-certified-hardware.md +++ b/Teams/devices/teams-phones-certified-hardware.md @@ -110,6 +110,7 @@ See [Microsoft Teams phones feature set](phones-for-teams.md) for information on #### HP | Poly | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications** | Release date | |:----------------|:-------------------|:----------------------------|:----------------------------------------------------------------------------------|:--------------------------------------------| +| CCX350/CCX400/CCX500/CCX505/CCX600/Trio C60 | `9.0.1.6562` | `N/A`| Teams client: `1449/1.0.94.2024080808`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| December 16, 2024| | CCX350/CCX400/CCX500/CCX505/CCX600/Trio C60 | `9.0.0.10460` | `N/A`| Teams client: `1449/1.0.94.2024080808`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| Recalled| | CCX350/CCX400/CCX500/CCX505/CCX600 | `8.1.6.1006` | `8.1.3.1301`| Teams client: `1449/1.0.94.2024011003`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| April 12, 2024| |Trio C60 | `8.1.6.1005` | `8.1.3.1300` | Teams client: `1449/1.0.94.2024011003`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| April 12, 2024 | diff --git a/Teams/languages-for-voicemail-greetings-and-messages.md b/Teams/languages-for-voicemail-greetings-and-messages.md index e50a6f1faf..d6d561012c 100644 --- a/Teams/languages-for-voicemail-greetings-and-messages.md +++ b/Teams/languages-for-voicemail-greetings-and-messages.md @@ -45,7 +45,7 @@ Teams supports the following languages for voicemail greetings. |Czech |Czech Republic |cs-CZ |Yes |Yes |No | |Danish |Denmark |da-DK |Yes |Yes |No | |Dutch |Belgium |nl-BE |Yes, but Dutch (Netherlands) is used. |Yes |No | -|Dutch |Netherlands |nl-NL |Yes |Yes |No | +|Dutch |Netherlands |nl-NL |Yes |Yes |Yes | |English |Australia |en-AU |Yes, but English (United States) is used. |Yes |Yes, but English (United States) is used. | |English |Canada |en-CA |Yes, but English (United States) is used. |Yes |Yes, but English (United States) is used. | |English |India |en-IN |Yes, but English (United States) is used. |Yes |Yes, but English (United States) is used. | @@ -66,6 +66,8 @@ Teams supports the following languages for voicemail greetings. |Greek |Greece |el-GR |Yes |Yes |No | |Hebrew |Israel |he-IL |Yes |No |No | |Hindi |India |hi-IN |Yes |No |No | +|Tamil |India |ta-IN |Yes |No |No | +|Telugu |India |te-IN |Yes |No |No | |Hungarian |Hungary |hu-HU |Yes |No |No | |Indonesian |Indonesia |id-ID |Yes |Yes |No | |Italian |Italy |it-IT |Yes |Yes |Yes | @@ -73,6 +75,8 @@ Teams supports the following languages for voicemail greetings. |Korean |Korean |ko-KR |Yes |Yes |No | |Latvian |Latvia |lv-LV |Yes |Yes |No | |Lithuanian |Lithuania |lt-LT |Yes |Yes |No | +|Malay |Malaysia |ms-MY |Yes |No |No | +|Maltese |Malta |mt-MT |Yes |No |No | |Norwegian (Bokmal) |Norway |nb-NO |Yes |Yes |No | |Polish |Poland |pl-PL |Yes |Yes |No | |Portuguese |Brazil |pt-BR |Yes, but Portuguese (Portugal) is used. |Yes |Yes | @@ -86,6 +90,7 @@ Teams supports the following languages for voicemail greetings. |Swedish |Sweden |sv-SE |Yes |Yes |No | |Thai |Thailand |th-TH |Yes |Yes |No | |Turkish |Türkiye |tr-TR |Yes |Yes |No | +|Urdu |Pakistan |ur-PK |Yes |No |No | |Vietnamese |Vietnam |vi-VN |Yes |Yes |No | |Welsh |Wales |cy-GB |Yes |Yes |No | diff --git a/Teams/meeting-webinar-town-hall-feature-comparison.md b/Teams/meeting-webinar-town-hall-feature-comparison.md index c916fa900b..64e909cc1a 100644 --- a/Teams/meeting-webinar-town-hall-feature-comparison.md +++ b/Teams/meeting-webinar-town-hall-feature-comparison.md @@ -47,6 +47,8 @@ The following table shows which features are available in meetings, webinars, an |[Convenience recording](meeting-recording.md)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |[Custom backgrounds](custom-meeting-backgrounds.md)|Premium|Premium|Premium| |[Decorate my background](https://adoption.microsoft.com/microsoft-teams-premium/decorate-your-background/)|Premium|Premium|Premium| +|[Download town hall transcripts](https://support.microsoft.com/office/manage-town-hall-recordings-in-microsoft-teams-88ac3af7-db67-4556-a202-b73a1d6c2e46)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|[Download webinar transcripts](https://support.microsoft.com/office/manage-webinar-recordings-in-microsoft-teams-8cf1ba61-c9d8-4628-8b5d-0dcdb8503144)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| |[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|For view-only meetings only.|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |[eCDN analytics](/ecdn/technical-documentation/analytics)|For view-only meetings only.|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |[Email communication for events](manage-email-communications.md)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| diff --git a/Teams/plan-town-halls.md b/Teams/plan-town-halls.md index 35097679c9..7e9f67ac16 100644 --- a/Teams/plan-town-halls.md +++ b/Teams/plan-town-halls.md @@ -171,6 +171,7 @@ Teams admins and organizers have different policies and settings to control the |[Audio and video](meeting-policies-audio-and-video.md)|Can manage the availability and use of audio and video for presenters and organizers.| Only presenters and organizers can use their audio and video. Attendees can't share their audio or video, but interact through Q&A.| |[Chat](manage-meeting-chat.md)|Can manage whether organizers, presenters, and co-organizers can read and write messages to each other during town halls.|Can chat with presenters and co-organizers. Attendees don't use this chat during town halls. To learn how attendees can use chat during town halls, see [Manage event chat for Microsoft Teams town halls](town-hall-chat.md).| |[Content sharing](meeting-policies-content-sharing.md)|Can control sharing mode, who can request control, and can set a default for who can present.|Can control who can present among presenters, organizers, and co-organizers. Attendees can't share content in town halls.| +|[Download transcripts](https://support.microsoft.com/office/manage-town-hall-recordings-in-microsoft-teams-88ac3af7-db67-4556-a202-b73a1d6c2e46)|No control.|Can download transcripts from their town halls.| |[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|Can manage and configure the availability of eCDN for organizers. Admins can also turn off the Microsoft eCDN for town hall organizers with a Premium license and switch to a partner eCDN provider.| No control.| |[Email communications (Teams Premium)](manage-email-communications.md)|Can control if event organizers and co-organizers can edit email templates for their town halls.|Can edit email templates before they're sent out.| |[External presenters](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c)|No control.|Can invite presenters from outside of your organization. External presenters have a unique join link to join the town hall without waiting in the lobby.| diff --git a/Teams/plan-webinars.md b/Teams/plan-webinars.md index 05d2c5ae44..38f39db7ed 100644 --- a/Teams/plan-webinars.md +++ b/Teams/plan-webinars.md @@ -89,6 +89,7 @@ A Teams Premium subscription includes the following features for webinars: |Turn on Q&A for webinars|![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |View attendance reports|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |External presenters|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Download transcripts|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |Create a webinar wait list | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | |Limit the day and time when people can register | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | |Manage attendees’ view | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | @@ -111,6 +112,7 @@ Teams admins and organizers have different policies and settings to control the |[Chat](manage-meeting-chat.md)|Can manage whether organizers, presenters, and co-organizers, and attendees can read and write chat messages.|Can manage whether chat is available for their webinars.| |[Collaboration features](meeting-policies-content-sharing.md)|Can control the availability of PowerPoint Live, whiteboard, and shared notes.|No control.| |[Content sharing](meeting-who-present-request-control.md)|Can control sharing mode and who can request control and can set a default for who can present.|Can control who can present.| +|[Download transcripts](https://support.microsoft.com/office/manage-webinar-recordings-in-microsoft-teams-8cf1ba61-c9d8-4628-8b5d-0dcdb8503144)|No control.|Can download transcripts from their webinars.| |[Email communications (Teams Premium)](manage-email-communications.md)|Can control if event organizers and co-organizers can edit email templates for their webinars.|Can edit email templates before they're sent out.| |[External presenters](https://support.microsoft.com/office/schedule-a-webinar-in-microsoft-teams-0719a9bd-07a0-47fd-8415-6c576860f36a)|No control.|Can invite presenters from outside of your organization. External presenters have a unique join link to join the webinar without waiting in the lobby.| |[Green room](https://support.microsoft.com/office/green-room-for-teams-meetings-5b744652-789f-42da-ad56-78a68e8460d5)|No control.|Can choose if green room is used for a webinar.| diff --git a/Teams/teams-recording-compliance.md b/Teams/teams-recording-compliance.md index 6bbafe3103..42e8116fcd 100644 --- a/Teams/teams-recording-compliance.md +++ b/Teams/teams-recording-compliance.md @@ -108,8 +108,8 @@ Compliance recording isn't supported for: **Large Meetings** -The Compliance Recording platform supports meeting sizes up to 250 users in paired bot mode. -Larger meeting sizes might have performance implications and will be addressed with a future update. +The Compliance Recording platform is optimized for meetings, however performance may be impacted during meetings with over 250 users in paired bot mode. We're actively working on improvements in a future update to enhance the experience. +Please contact your recording partner for more information. **Call queues** @@ -167,7 +167,8 @@ The following list includes partners certified to deliver a compliance recording |Red Box |[https://www.redboxvoice.com/compliance-recording-for-microsoft-teams](https://www.redboxvoice.com/red-box-partners/microsoft-integration/compliance-recording-for-microsoft-teams) | |Theta Lake |[https://thetalake.com/integrations/microsoft/](https://thetalake.com/integrations/microsoft/) | |Touch Call Recording (GuardRec Compliance 2022.10.3) |[https://touchcallrecording.com/teams-policy-based-recording-for-callings-and-meetings](https://touchcallrecording.com/teams-policy-based-recording-for-callings-and-meetings) | -|Verint |[https://www.verba.com/solutions/microsoft-teams-recording](https://www.verba.com/solutions/microsoft-teams-recording) | +|Verint Verba |[https://www.verba.com/solutions/microsoft-teams-recording](https://www.verba.com/solutions/microsoft-teams-recording) | +|Verint EDM |[https://www.verint.com/enterprise-recording-engagement-data-management/](https://www.verint.com/enterprise-recording-engagement-data-management/) | The following partners are in the process of certifying their solution for Microsoft Teams: diff --git a/Teams/vdi-2.md b/Teams/vdi-2.md index 13634dd3ad..e8da1d1865 100644 --- a/Teams/vdi-2.md +++ b/Teams/vdi-2.md @@ -386,6 +386,7 @@ By default, the MsTeamsPlugin automatically downloads and installs the right Sli - If someone turns their camera **on** only, there's no issue because the video element is created, not destroyed. - If the presenter maximizes the call monitor (which destroys the self preview of what the presenter is sharing). - Stopping and resharing the window should resolve the issue. + - This issue has been resolved in new Teams 24335.206.X.X or higher versions. #### Citrix virtual channel allow list