diff --git a/.github/workflows/BuildValidation.yml b/.github/workflows/BuildValidation.yml new file mode 100644 index 0000000000..3828c1facf --- /dev/null +++ b/.github/workflows/BuildValidation.yml @@ -0,0 +1,21 @@ +name: Build validation + +permissions: + pull-requests: write + statuses: write + +on: + issue_comment: + types: [created] + +jobs: + + build-status: + uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-BuildValidation.yml@workflows-test + with: + PayloadJson: ${{ toJSON(github) }} + secrets: + AccessToken: ${{ secrets.GITHUB_TOKEN }} + + + diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 9ade48af34..67f8a960b3 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -5286,8 +5286,8 @@ "redirect_document_id": false }, { - "source_path": "Skype/SfbPartnerCertification/certification/devices-usb-devices.md", - "redirect_url": "/microsoftteams/devices/usb-devices", + "source_path": "Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md", + "redirect_url": "/SkypeForBusiness/certification/devices-usb-devices", "redirect_document_id": false }, { @@ -5324,16 +5324,81 @@ "source_path": "Skype/SfbPartnerCertification/lync-cert/pcs-optimized-for-lync.md", "redirect_url": "/microsoftteams/devices/certification-overview", "redirect_document_id": false + }, + { + "source_path": "Teams/devices/phones-for-teams.md", + "redirect_url": "/microsoftteams/phones/phones-for-teams", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/plan-device-deployment.md", + "redirect_url": "/microsoftteams/phones/plan-device-deployment", + "redirect_document_id": false }, - { - "source_path": "Teams/devices/teams-ip-phones.md", - "redirect_url": "/microsoftteams/devices/certified-devices-overview", - "redirect_document_id": false + { + "source_path": "Teams/devices/teams-ip-phones.md", + "redirect_url": "/microsoftteams/devices/certified-devices-overview", + "redirect_document_id": false }, { "source_path": "Teams/rooms/android-app-firmware.md", "redirect_url": "/microsoftteams/devices/certified-hardware-android", "redirect_document_id": false + }, + { + "source_path": "Teams/devices/phones-panels-deploy.md", + "redirect_url": "/microsoftteams/devices/mtra-panels-deploy", + "redirect_document_id": false + }, + { + "source_path": "Teams/set-up-common-area-phones.md", + "redirect_url": "/microsoftteams/phones/set-up-common-area-phones", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/common-area-mobile-phones.md", + "redirect_url": "/microsoftteams/phones/common-area-mobile-phones", + "redirect_document_id": false + }, + { + "source_path": "Teams/sip-gateway-configure.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-configure", + "redirect_document_id": false + }, + { + "source_path": "Teams/sip-gateway-plan.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-plan", + "redirect_document_id": false + }, + { + "source_path": "Teams/sip-gateway-dynamic-filters.md", + "redirect_url": "/microsoftteams/devices/sip-gateway-dynamic-filters", + "redirect_document_id": false + }, + { + "source_path": "Teams/flw-realwear.md", + "redirect_url": "/microsoftteams/devices/usb-devices", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/collab-bar-deploy.md", + "redirect_url": "/microsoftteams/rooms/rooms-deploy", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/teams-android-devices-user-interface.md", + "redirect_url": "/microsoftteams/phones/teams-android-devices-user-interface", + "redirect_document_id": false + }, + { + "source_path": "Teams/rooms/admin-center-license-overview.md", + "redirect_url": "/microsoftteams/rooms/rooms-licensing", + "redirect_document_id": false + }, + { + "source_path": "Teams/devices/smartvision-admin.md", + "redirect_url": "/microsoftteams/devices/multistream-intelliframe", + "redirect_document_id": false } ] -} +} \ No newline at end of file diff --git a/Skype/SfBServer2019/virtualization-guidance.md b/Skype/SfBServer2019/virtualization-guidance.md index 6190757857..f6948f11ba 100644 --- a/Skype/SfBServer2019/virtualization-guidance.md +++ b/Skype/SfBServer2019/virtualization-guidance.md @@ -33,10 +33,7 @@ While virtualization is supported, there are some key points to remember: SfB Server 2019 is supported on Windows Server 2016 and Windows Server 2019. -For third-party hypervisors, you need a hypervisor that has passed the Server Virtualization Validation Program (SVVP) testing for the relevant OS. - -- See the [Windows Server 2016 versions](https://www.windowsservercatalog.com/results.aspx?&bCatID=1521&cpID=0&avc=86&ava=88&avt=0&avq=0&OR=1&PGS=25) in the SVVP list. -- See the [Windows Server 2019 versions](https://www.windowsservercatalog.com/results.aspx?&bCatID=1521&cpID=0&avc=86&ava=130&avt=0&avq=0&OR=1&PGS=25) in the SVVP list. +For third-party hypervisors, you need a hypervisor that has passed the Server Virtualization Validation Program (SVVP) testing for the relevant OS. For more information, see [Support partners for non-Microsoft hardware virtualization software](/troubleshoot/windows-server/virtualization/non-microsoft-hardware-virtualization-software). ## Stress and performance tool diff --git a/Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md b/Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md index 85096eeb37..9161b54b70 100644 --- a/Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md +++ b/Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md @@ -82,8 +82,6 @@ To see a list of those countries/regions that have phone numbers automatically a - You can set up to four languages for each audio conferencing phone number - one primary and three secondary. And you can also set languages on a dedicated audio conferencing phone number. - To set the dial-in phone number for a user, see [Set the phone numbers included on invites](set-the-phone-numbers-included-on-invites.md). - -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] ## Related topics diff --git a/Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md b/Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md index 738264d57c..e64ecbdc2c 100644 --- a/Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md +++ b/Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md @@ -143,8 +143,6 @@ After you enable external communication for your entire business, you can turn i > [!NOTE] > You may have to wait for up to 24 hours for your changes to take effect. - -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] ## Related topics diff --git a/Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md b/Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md index 942834f902..b178682e4a 100644 --- a/Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md +++ b/Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md @@ -105,10 +105,6 @@ To configure these settings in bulk, use PowerShell. See [Set up your computer f To configure these settings in bulk, use PowerShell. See [Set the phone numbers included on invites](../audio-conferencing-in-office-365/set-the-phone-numbers-included-on-invites.md) [Set up your computer for Windows PowerShell](../set-up-your-computer-for-windows-powershell/set-up-your-computer-for-windows-powershell.md). - -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] - - ## Related topics [Set up Skype for Business Online](set-up-skype-for-business-online.md) diff --git a/Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md b/Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md index 1253412e85..3e08427b98 100644 --- a/Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md +++ b/Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md @@ -97,14 +97,9 @@ Skype contacts who signed in with their Microsoft account (formerly Windows Live |:-----|:-----| | Video conversations
Person-to-person instant messaging
Presence
| Multi-party IM conversations
Audio and video conversations with three or more people
Desktop and program sharing
| -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] - ## Related topics [Allow users to contact external Skype for Business users](allow-users-to-contact-external-skype-for-business-users.md) [Set up Skype for Business Online](set-up-skype-for-business-online.md) - - - diff --git a/Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md b/Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md index c76ce9aa5c..cb316c6516 100644 --- a/Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md +++ b/Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md @@ -167,8 +167,6 @@ The quality of audio, video, and application sharing in Skype for Business is gr [Make and receive a video call using Skype for Business](https://support.office.com/article/abf62493-670f-4b0d-b2cf-fe03b49caf42) -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] - ## Related topics diff --git a/Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md b/Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md index b8cec810bb..762384ef4e 100644 --- a/Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md +++ b/Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md @@ -92,8 +92,6 @@ If you want to use your existing Calling Plan, buy the **Phone System** add-on a If you are using on-premises PSTN connectivity for hybrid users, you *only* assign **Phone System** licenses to your users. **DO NOT** also assign a Calling Plan. -[!INCLUDE [LinkedIn Learning Info](../../common/office/linkedin-learning-info.md)] - ## Related topics - [Set up Skype for Business Online](../set-up-skype-for-business-online/set-up-skype-for-business-online.md) diff --git a/Skype/SfbPartnerCertification/certification/archived/test-spec.md b/Skype/SfbPartnerCertification/certification/archived/test-spec.md index c969111110..197da12264 100644 --- a/Skype/SfbPartnerCertification/certification/archived/test-spec.md +++ b/Skype/SfbPartnerCertification/certification/archived/test-spec.md @@ -69,8 +69,6 @@ Use the following table to find the tools for testing USB peripherals, PCs, and [Phones and devices home](devices-ip-phones.md) -[USB Audio and Video devices](devices-usb-devices.md) - If you are a vendor seeking to join the certification program, see [How to Join](how-to-join.md) for requirements and available programs. View the [Microsoft Teams devices store](https://products.office.com/microsoft-teams/across-devices/devices) to see products certified for Microsoft Teams and Skype for Business. diff --git a/Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md b/Skype/SfbPartnerCertification/certification/devices-usb-devices.md similarity index 100% rename from Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md rename to Skype/SfbPartnerCertification/certification/devices-usb-devices.md diff --git a/Teams/CQD-PSTN-report.md b/Teams/CQD-PSTN-report.md index dc99efe1a6..01d369e0a4 100644 --- a/Teams/CQD-PSTN-report.md +++ b/Teams/CQD-PSTN-report.md @@ -1,7 +1,7 @@ --- title: "Using the CQD PSTN Direct Routing report" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: siunies ms.date: 03/06/2020 diff --git a/Teams/CQD-Power-BI-connector.md b/Teams/CQD-Power-BI-connector.md index 4618525ec0..65e176c0fe 100644 --- a/Teams/CQD-Power-BI-connector.md +++ b/Teams/CQD-Power-BI-connector.md @@ -3,8 +3,8 @@ title: "Install Power BI Connector to use CQD query templates" author: mkbond007 ms.author: mabond manager: pamgreen -ms.reviewer: siunies -ms.date: 03/06/2020 +ms.reviewer: jamp +ms.date: 10/07/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -23,14 +23,14 @@ description: "Install Power BI Connector to use Call Quality Dashboard (CQD) que # Install Microsoft Call Quality connector for Power BI to use Call Quality Dashboard query templates -Before you can use the Power BI query templates (PBIX files) for Microsoft Teams Call Quality Dashboard (CQD), you'll need to install the Microsoft Call Quality connector for Power BI, using the *MicrosoftCallQuality.pqx* file included in the [download](https://www.microsoft.com/download/details.aspx?id=102291). +Before you can use the Power BI query templates (PBIX files) for Microsoft Teams Call Quality Dashboard (CQD), you need to install the Microsoft Call Quality connector for Power BI, using the *MicrosoftCallQuality.pqx* file included in the [download](https://www.microsoft.com/download/details.aspx?id=102291). Read [Use Power BI to analyze CQD data for Teams](CQD-Power-BI-query-templates.md) to learn about these templates. Make sure you have the right [CQD access role](./turning-on-and-using-call-quality-dashboard.md#assign-admin-roles-for-access-to-cqd) to access the Power BI reports. > [!NOTE] -> The Microsoft Call Quality connector only supports DirectQuery in Power BI; Import mode is not supported. +> The Microsoft Call Quality connector only supports DirectQuery in Power BI; Import mode isn't supported. ## Installation @@ -40,60 +40,60 @@ The process for installing a custom connector and adjusting security to enable u 2. Download the connector file (either a *\*.mez* or *\*.pqx* file) and place it in the *Custom Connectors* directory. -3. **If the connector file is a *\*.mez* file,** you'll also need to adjust your security settings as described in the [custom connector setup documentation](/power-bi/desktop-connector-extensibility#data-extension-security). +3. **If the connector file is a *\*.mez* file,** you also need to adjust your security settings as described in the [custom connector setup documentation](/power-bi/desktop-connector-extensibility#data-extension-security). If a new version of the Microsoft Call Quality connector is released, replace the old connector file in the *Custom Connectors* directory with the new file. -Customers in Government cloud environments (GCC, GCC-H, DoD) will need to [install the connector](/power-bi/connect-data/service-gateway-custom-connectors) with an [on-premises data gateway](/power-bi/connect-data/service-gateway-onprem) for compatibility with Power BI Service. Without an on-premises gateway, Government cloud customers will only be able to use the Microsoft Call Quality connector in Power BI Desktop. +Customers in Government cloud environments (GCC, GCC-H, DoD) need to [install the connector](/power-bi/connect-data/service-gateway-custom-connectors) with an [on-premises data gateway](/power-bi/connect-data/service-gateway-onprem) for compatibility with Power BI Service. Without an on-premises gateway, Government cloud customers can only use Microsoft Call Quality connector in Power BI Desktop. ## Setup -To build a report and run queries, you'll first need to connect to the CQD data source. Follow the steps below in order to connect: +To build a report and run queries, you first need to connect to the CQD data source. In order to connect, perform the following steps: -1. In the Home tab of Power BI Desktop, select on *Get Data*. +1. In the Home tab of Power BI Desktop, select **Get Data**. ![Get Data in the Power BI Connector.](media/CQD-power-bi-connector1-resize.png) -2. The *Get Data* window should appear at this point. Navigate to *Online Services*, then select *Microsoft Call Quality (Beta)* and hit *Connect*. +2. The *Get Data* window should appear at this point. Navigate to **Online Services**, then select **Microsoft Call Quality (Beta)** and select **Connect**. ![Microsoft Call Quality in the Power BI Connector.](media/CQD-power-bi-connector2-resize.png) -3. You'll be prompted to sign in next. Use the same credentials that you use for Call Quality Dashboard.2 +3. In the sign-in prompt, use the same credentials that you use for Call Quality Dashboard.2 -4. The next prompt will give you the option between two *Data Connectivity modes*. Select *DirectQuery* and hit *OK*. +4. The next prompt gives you the option between two **Data Connectivity modes**. Select **DirectQuery**, then select **OK**. -5. Finally, you'll see a final prompt showing you the entire data model for Call Quality Dashboard. No data will be visible at this point, only the data model for CQD. Select *Load* to complete the setup process. +5. The final prompt shows you the entire data model for Call Quality Dashboard. No data is visible at this point, only the data model for CQD. Select **Load** to complete the setup process. -6. At this point, Power BI will load the data model onto the right side of the window. The page will remain otherwise blank, and no queries will be loaded by default. Proceed to **Building Queries** below in order to build a query and return data. +6. At this point, Power BI loads the data model onto the right side of the window. The page remains otherwise blank, and no queries are loaded by default. In order to build a query and return data, see [Building Queries](#building-queries). -If any of the steps during this setup process weren't clear, you can find a more detailed explanation of the process in [Quickstart: Connect to data in Power BI Desktop](/power-bi/desktop-quickstart-connect-to-data). +If any of the steps during this setup process aren't clear, you can find a more detailed explanation of the process in [Quickstart: Connect to data in Power BI Desktop](/power-bi/desktop-quickstart-connect-to-data). ## Building Queries Once setup is complete, you should see the names of several hundred dimensions and measures load in the *Fields* pane. Constructing actual queries from here's simple, just select the dimensions and measures you want for your query, then drag and drop them onto the page. Here's a more detailed explanation, with a simple example: -1. Select the visualization you want to use from the *Visualizations* pane. A blank version of that visualization should appear on the page. For the purposes of this example, we'll be using the *Table* visualization. +1. Select the visualization you want to use from the *Visualizations* pane. A blank version of that visualization should appear on the page. For the purposes of this example, we're using the *Table* visualization. ![Visualizations pane in the Power BI Connector.](media/CQD-power-bi-connector3-resize.png) -2. Determine which dimensions and measures (denoted by an aggregation symbol by their name) you wish to use for your query, then manually select them and drag them onto the black visualization. Alternately, drag them onto the *Values* field beneath the visualization options. +2. Determine which dimensions and measures (denoted by an aggregation symbol by their name) you wish to use for your query. Then, manually select these dimensions and measures and drag them onto the black visualization. Alternately, drag them onto the *Values* field beneath the visualization options. ![Visualizations query in the Power BI Connector.](media/CQD-power-bi-connector4-resize2.png) > [!IMPORTANT] > Call Quality Dashboard requires a measure for any query to run. Failure to add a measure to a query will cause that query to fail. -3. Next, select any dimensions you want to filter on and drag them to the *Filters on this visual* field in the *Filters* pane. The Microsoft Call Quality connector currently supports *Basic filtering* (select values from a list of possible dimension values), *Advanced filtering* (manually specify values and operands to filter on, similar to Call Quality Dashboard), and *Relative date filtering* (only available for the *End Time* and *Start Time* dimensions). Filtering according to *Top N* isn't supported by Call Quality Dashboard. +3. Next, select any dimensions you want to filter on and drag them to the **Filters on this visual** field in the *Filters* pane. The Microsoft Call Quality connector currently supports *Basic filtering* (select values from a list of possible dimension values), *Advanced filtering* (manually specify values and operands to filter on, similar to Call Quality Dashboard), and *Relative date filtering* (only available for the *End Time* and *Start Time* dimensions). Call Quality Dashboard doesn't support filtering according to *Top N*. ![Visualizations filters in the Power BI Connector.](media/CQD-power-bi-connector5-resize.png) > [!IMPORTANT] - > Filters are only supported when applied to Dimensions. Filtering on the values of Measurements is not supported in Call Quality Dashboard. + > Filters are only supported when applied to Dimensions. Filtering on the values of Measurements isn't supported in Call Quality Dashboard. -4. Finally, select the *Format* tab within the *Visualizations* pane to style and format your query. +4. Finally, select the **Format** tab within the *Visualizations* pane to style and format your query. > [!NOTE] - > Call Quality Dashboard queries require at least one measure in order to run. If your query does not load, double check that you have included a measure in the query. + > Call Quality Dashboard queries require at least one measure in order to run. If your query does not load, double check that you included a measure in the query. ## Creating a Drillthrough Report @@ -101,7 +101,7 @@ Once setup is complete, you should see the names of several hundred dimensions a 1. Create another page for the focused report, and then add your queries to that page. -2. Select the dimension you want to use as a drillthrough filter and drag them onto the *Drillthrough* field under on the *Visualizations* pane. +2. Select the dimension you want to use as a drillthrough filter and drag them onto the **Drillthrough** field under on the *Visualizations* pane. ![Drillthrough in the Power BI Connector.](media/CQD-power-bi-connector6-resize.png) @@ -117,21 +117,21 @@ You should design Microsoft Call Quality connector queries with drillthrough fun ## Limitations -Not all Power BI functionality is support by the Microsoft Call Quality connector, either as a result of limitations on Call Quality Dashboard's data model or on DirectQuery connectors in general. The list below notes some of the Connector's more noteworthy limitations, but this list is not exhaustive: +Not all Power BI functionality is support by the Microsoft Call Quality connector, either as a result of limitations on Call Quality Dashboard's data model or on DirectQuery connectors in general. The list below notes some of the Connector's more noteworthy limitations, but this list isn't exhaustive: 1. **Calculated Columns –** DirectQuery connectors in general have limited support for calculated columns in Power BI. Some calculated columns might work with the Connector, that those columns are exceptions. As a general rule, calculated columns don't function. -2. **Aggregations –** The Call Quality Dashboard data model is built on a cube model, meaning that aggregations are already supported in the form of measures. Attempting to manually add aggregations to different dimensions or changing the aggregation type of a measure won't work with the Connector, and it will generally result in an error. +2. **Aggregations –** The Call Quality Dashboard data model is built on a cube model, meaning that aggregations are already supported in the form of measures. Attempting to manually add aggregations to different dimensions or changing the aggregation type of a measure doesn't work with the Connector, and it will generally result in an error. 3. **Custom Visuals –** While the Microsoft Call Quality connector does work with a range of custom visuals, we're unable to guarantee compatibility with all custom visuals. Many custom visuals rely on the use of calculated columns or imported data, neither of which is supported by DirectQuery connectors. -4. **Referencing Cached Data –** Power BI currently doesn't support referencing cached data from a DirectQuery connector in any way. Any attempt to reference the results of a query will result in a new query. +4. **Referencing Cached Data –** Power BI currently doesn't support referencing cached data from a DirectQuery connector in any way. Any attempt to reference the results of a query will create a new query. -5. **Relative Data Filtering –** Is supported in the Microsoft Call Quality connector, but only with the *Start Time* and *End Time* dimensions. Although the *Date* dimension may be the obvious choice for relative date filtering, *Date* isn't stored as a date time object and thus doesn't support relative date filtering in Power BI. +5. **Relative Data Filtering –** Is supported in the Microsoft Call Quality connector, but only with the *Start Time* and *End Time* dimensions. Although the *Date* dimension might be the obvious choice for relative date filtering, *Date* isn't stored as a date time object and thus doesn't support relative date filtering in Power BI. 6. **Dimension Only or Measurement Only Queries -** Aren't supported at this time in the Microsoft Call Quality connector. If you create a visualization with three or more measurements and no dimensions, or three or more dimensions and no measurements, the column data will be transposed. Always include at least one dimension (for example, Month Year) and one measurement (for example, Total Call Count) in your visualizations. -7. **Government Community Cloud (GCC, GCC-High, and DoD) Support –** For customers in Government cloud environments, the Microsoft Call Quality connector can be used with an [on-premises data gateway](/power-bi/connect-data/service-gateway-onprem) for compatibility with Power BI service. Simply follow the guide for [installing custom connectors with an on-premises data gateway](/power-bi/connect-data/service-gateway-custom-connectors) using the latest version of the Microsoft Call Quality connector to enable access. Additionally, an appropriate Power BI US Government license is required for government cloud. For more information on licensing, please see the latest guidance for [Power BI for US government customers](/power-bi/enterprise/service-govus-overview#buy-a-power-bi-pro-subscription-for-government-customers). +7. **Government Community Cloud (GCC, GCC-High, and DoD) Support –** For customers in Government cloud environments, the Microsoft Call Quality connector can be used with an [on-premises data gateway](/power-bi/connect-data/service-gateway-onprem) for compatibility with Power BI service. Simply follow the guide for [installing custom connectors with an on-premises data gateway](/power-bi/connect-data/service-gateway-custom-connectors) using the latest version of the Microsoft Call Quality connector to enable access. Additionally, an appropriate Power BI US Government license is required for government cloud. For more information on licensing, see the latest guidance for [Power BI for US government customers](/power-bi/enterprise/service-govus-overview#buy-a-power-bi-pro-subscription-for-government-customers). Most of these issues are either restrictions to DirectQuery connector design in Power BI or fundamental to the design of the CQD data model. @@ -148,20 +148,20 @@ Alternatively, if the dates you want to view are recent, apply a relative date f ### When I add certain dimensions to my reports, the visual immediately returns **"Couldn't load the data for this visual"**. Removing the dimension fixes the visual--what is happening? -This is a known issue in the Microsoft Call Quality connector; any dimension that is exposed as a whole number will appear in Power BI as an 'aggregate' column, where Power BI will attempt a default summarize action (typically 'Sum'). In some cases, this behavior will succeed at summing up the values even though the result isn't useful, since the 'sum' of a dimension like Second WiFi Channel is meaningless. In other cases, this summarize action will fail and cause errors in the visual. +This is a known issue in the Microsoft Call Quality connector. Any dimension that's exposed as a whole number appears in Power BI as an "aggregate" column, where Power BI attempts a default summarize action (typically 'Sum'). In some cases, this behavior succeeds at summing up the values even though the result isn't useful, since the "sum" of a dimension like Second WiFi Channel is meaningless. In other cases, this summarize action fails and causes errors in the visual. -To work around this issue, start by removing the dimension from the visual. Select the dimension from the 'Fields' list, browse to the 'Column tools' tab in the ribbon, select the 'Summarization' drop-down menu and select **Don't summarize**. You can now add the dimension to the visual again. +To work around this issue, start by removing the dimension from the visual. Select the dimension from the **Fields** list, browse to the *Column tools* tab in the ribbon, select the **Summarization** drop-down menu, and select **Don't summarize**. You can now add the dimension to the visual again. ## Error Codes -Because the Microsoft Call Quality connector for Power BI is less restricted than the browser app in terms of kinds of queries you can construct, you may occasionally encounter errors while building your queries. If you receive an error message of the type "CQDError. RunQuery – Query Execution Error", reference the list below with the ErrorType number provided in order to troubleshoot the possible issue with the query. The following are the most common Error Type codes you may encounter with the CQD Power BI Connector: +Because the Microsoft Call Quality connector for Power BI is less restricted than the browser app in terms of kinds of queries you can construct, you might occasionally encounter errors while building your queries. If you receive an error message of the type "CQDError. RunQuery – Query Execution Error," reference the list below with the ErrorType number provided in order to troubleshoot the possible issue with the query. The following are the most common Error Type codes you might encounter with the CQD Power BI Connector: - **ErrorType 1 - Query Structure Error:** A query structure error is typically caused by the Connector failing to build a properly formatted query. This happens most often when using unsupported functionality, as specified in the Limitations above. Double check that you aren't using any calculated columns or custom visuals for that query. - **ErrorType 2 - Query Building Error:** A query building error is caused by the Microsoft Call Quality connector being unable to properly parse the query you're attempting to build. This error happens most often when using unsupported functionality, as specified in the Limitations above. Double check that you aren't using any calculated columns or custom visuals for that query. - - **ErrorType 5 - Execution Timeout:** The query has reached the maximum possible runtime before timing out. Try adding more filters to the query in order to limit its scope. Narrowing the data range is often the most effective way to achieve this. + - **ErrorType 5 - Execution Timeout:** The query reached the maximum possible runtime before timing out. Try adding more filters to the query in order to limit its scope. Narrowing the data range is often the most effective way to achieve this. - **ErrorType 7 - No Measurements Error:** Call Quality Dashboard queries require a measure in order to function. Double check that your query includes measure. Measures in the Microsoft Call Quality connector are denoted by the aggregation (sum) symbol before their name. @@ -169,7 +169,7 @@ If you encounter any another errors outside of this scope, notify the Call Quali ## Footnotes -**1** Certain processes and apps (for example, OneDrive) may cause your Documents root folder to change; make sure that the *Power BI Desktop\\Custom Connectors* directory is placed inside of the current root folder Documents folder. +**1** Certain processes and apps (for example, OneDrive) might cause your Documents root folder to change; make sure that the *Power BI Desktop\\Custom Connectors* directory is placed inside of the current root folder Documents folder. **2** The sign in credentials you use for Call Quality Dashboard *don't* need to be the same credentials you use for logging into the Power BI Desktop app itself. @@ -177,11 +177,11 @@ If you encounter any another errors outside of this scope, notify the Call Quali ### When will the Power BI Connector be updated from "Beta" status? -The Microsoft Call Quality (Beta) connector for Power BI is the first 'release' version of the connector and has been officially security signed by the Power BI team to reflect this. At the time of the connector's initial release, the Power BI team was unable to provide support and broader certification, but was still prepared to attest to the security, authenticity, and general functionality of the Microsoft Call Quality connector. We're planning to invest in the Microsoft Call Quality connector for Power BI soon. +Despite the "beta" label in the Microsoft Call Quality connector, the connector is in release status; it's *not* a beta. At the time of the connector's initial release, the Power BI team was unable to provide support and broader certification (and thus, the "beta" tag), but they were still prepared to attest to the security, authenticity, and general functionality of the Microsoft Call Quality connector. Since then, the CQD team independently continues to invest further development into the connector to improve and revise its functionality. The "beta" label shouldn't dissuade customers from using the connector. The labeling is just a side effect of our independent approach to connector development. ### Why does the connector seem slower compared to Call Quality Dashboard in the browser? What can I do to improve performance? -Query performance for the various templates is actually the same in both the browser and in the connector. Just like any other standalone app, Power BI adds its authentication and rendering time to our performance. In addition, the difference comes in the number of concurrent queries being run. Because the in-browser version of Call Quality Dashboard had less well-developed and information-dense visualization options, most of our reports were limited to loading 2-3 queries at a time. On the other hand, the connector templates often display 20+ concurrent queries. If you wish to build reports that are as responsive as the older ones you were used to, try creating reports with no more than 2-3 queries per tab. +Query performance for the various templates is actually the same in both the browser and in the connector. Just like any other standalone app, Power BI adds its authentication and rendering time to our performance. In addition, the difference comes in the number of concurrent queries being run. Because the in-browser version of Call Quality Dashboard had less well-developed and information-dense visualization options, most of our reports were limited to loading 2-3 queries at a time. On the other hand, the connector templates often display 20+ concurrent queries. If you wish to build reports that are as responsive as the older ones you were used to, try creating reports with no more than 2-3 queries per tab. For more information, see the following articles: @@ -192,10 +192,10 @@ For more information, see the following articles: The 10,000-row limit is specified on the API end, and it's designed to help significantly improve performance and reduce the risk of query execution errors resulting from low memory conditions. -Instead of attempting to increase the result row count, it's best to restructure your reports according to connector best practices. The templates we have included are designed to demonstrate these best practices. Where possible, start by looking at your KPIs using broader, lower-cardinality dimensions, such as Month, Year, Date, Region, Country, etc. From there, you can drill down into increasingly higher-cardinality dimensions. The Helpdesk and Location-Enhanced Reports both provide good examples of this drill down workflow. +Instead of attempting to increase the result row count, it's best to restructure your reports according to connector best practices. The templates we include are designed to demonstrate these best practices. Where possible, start by looking at your KPIs using broader, lower-cardinality dimensions, such as Month, Year, Date, Region, Country, etc. From there, you can drill down into increasingly higher-cardinality dimensions. The Helpdesk and Location-Enhanced Reports both provide good examples of this drill down workflow. -## Related topics +## Related articles [Use Power BI to analyze CQD data for Teams](CQD-Power-BI-query-templates.md) diff --git a/Teams/ITAdmin-readiness.md b/Teams/ITAdmin-readiness.md index bb862555c6..fe1f0f3ed4 100644 --- a/Teams/ITAdmin-readiness.md +++ b/Teams/ITAdmin-readiness.md @@ -61,7 +61,8 @@ Use the training resources to educate yourself about Teams, teach others or run | Teams Phone Deployment playbook | | [Deck](https://aka.ms/teams-phone-deployment-playbook) | | Teams Phone for Frontline Workers Deployment playbook | | [Deck](https://aka.ms/teams-phone-FLW-deployment-playbook) | | Teams Phone Service Reliability and Survivability playbook | | [Deck](https://aka.ms/teams-phone-service-reliability-playbook) | -| Teams VDI 2.0 playbook | | [Deck](https://aka.ms/teams-vdi-2.0-playbook) | +| Teams Phone shared calling playbook | | [Deck](https://aka.ms/teams-phone-shared-calling-playbook) | +| Teams new VDI solution playbook | | [Deck](https://aka.ms/teams-vdi-2.0-playbook) | | Upgrade from Skype for Business to Teams | [Video 1: Introduction to Upgrade](https://aka.ms/teams-upgrade-intro)
[Video 2: Plan your upgrade](https://aka.ms/teams-upgrade-plan)
[Video 3: Coexistence and Interoperability](https://aka.ms/teams-upgrade-coexistence-interop)
[Video 4: Administrator experience](https://aka.ms/teams-upgrade-admin) | [Deck](https://aka.ms/teams-upgrade-deck)| | Windows desktop client | [Video](https://aka.ms/teams-clients) | [Deck](https://aka.ms/teams-clients-deck) | | Windows Defender Application Control for new Teams | | [Deck](https://aka.ms/new-teams-WDAC) | diff --git a/Teams/QoS-in-Teams-clients.md b/Teams/QoS-in-Teams-clients.md index 92bd709fea..111de49fbe 100644 --- a/Teams/QoS-in-Teams-clients.md +++ b/Teams/QoS-in-Teams-clients.md @@ -1,12 +1,12 @@ --- title: Implement Quality of Service (QoS) in Microsoft Teams desktop clients on Windows -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: siunies -ms.date: 09/27/2023 +ms.date: 11/12/2024 audience: admin description: Learn how to use Quality of Service (QoS) to optimize network traffic for the Microsoft Teams desktop client. ms.localizationpriority: medium @@ -65,7 +65,9 @@ To create the device configuration policy for QoS for Teams clients on Windows: |Teams Screenshare: Application|New Teams executable name.|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsScreenshare/AppPathNameMatchCondition|String|ms-teams.exe| |Teams Screenshare: Ports|Screen sharing ports used by the Teams client.|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsScreenshare/SourcePortMatchCondition|String|50040-50059| |Teams Screenshare: DSCP Marking|Marking applied for screen sharing (AF21)|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsScreenshare/DSCPAction|Integer|18| - + |Teams Calling-Meeting Signaling: Application|New Teams executable name.|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsCMSignaling/AppPathNameMatchCondition|String|ms-teams.exe| + |Teams Calling-Meeting Signaling: Ports|Calling and Meeting Signaling source ports used by the Teams client.|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsCMSignaling/SourcePortMatchCondition|String|50070-50089| + |Teams Calling-Meeting Signaling: DSCP Marking|Marking applied for calling and meeting signaling (CS5)|./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsCMSignaling/DSCPAction|Integer|40| **For the classic Teams client, using the following table.** @@ -82,6 +84,9 @@ To create the device configuration policy for QoS for Teams clients on Windows: |Classic Teams Screenshare: Application|Classic Teams executable name.|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsScreenshare/AppPathNameMatchCondition|String|teams.exe| |Classic Teams Screenshare: Ports|Screen sharing ports used by the Teams client.|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsScreenshare/SourcePortMatchCondition|String|50040-50059| |Classic Teams Screenshare: DSCP Marking|Marking applied for screen sharing (AF21)|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsScreenshare/DSCPAction|Integer|18| + |Classic Teams Calling-Meeting Signaling: Application|New Teams executable name.|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsCMSignaling/AppPathNameMatchCondition|String|teams.exe| + |Classic Teams Calling-Meeting Signaling: Ports|Calling and Meeting Signaling source ports used by the Teams client.|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsCMSignaling/SourcePortMatchCondition|String|50070-50089| + |Classic Teams Calling-Meeting Signaling: DSCP Marking|Marking applied for calling and meeting signaling (CS5)|./Device/Vendor/MSFT/NetworkQoSPolicy/ClassicTeamsCMSignaling/DSCPAction|Integer|40| 9. Select **Next** 10. In **Assignments**, select the group or groups that you want to target with this policy. The group membership must include Windows devices (and not user accounts) as this is a device policy. @@ -93,7 +98,7 @@ To create the device configuration policy for QoS for Teams clients on Windows: ## Configuring DSCP markings using PowerShell commands -Endpoint DSCP markings can be set in PowerShell using the [New-NetQosPolicy](/powershell/module/netqos/new-netqospolicy) command. In the examples below, there are two commands each for audio, video, and application sharing. The following commands show creating policies for both the new Teams client (ms-teams.exe) and classic Teams client (Teams.exe). You can combine these commands into a PowerShell script and distrbute to your desired endpoints. +Endpoint DSCP markings can be set in PowerShell using the [New-NetQosPolicy](/powershell/module/netqos/new-netqospolicy) command. In the examples below, there are two commands each for audio, video, and application sharing. The following commands show creating policies for both the new Teams client (ms-teams.exe) and classic Teams client (Teams.exe). You can combine these commands into a PowerShell script and distribute to your desired endpoints. **Set QoS for audio** @@ -115,6 +120,13 @@ new-NetQosPolicy -Name "Classic Teams Video" -AppPathNameMatchCondition "Teams.e ```powershell new-NetQosPolicy -Name "Teams Sharing" -AppPathNameMatchCondition "ms-teams.exe" -IPProtocolMatchCondition Both -IPSrcPortStartMatchCondition 50040 -IPSrcPortEndMatchCondition 50059 -DSCPAction 18 -NetworkProfile All new-NetQosPolicy -Name "Classic Teams Sharing" -AppPathNameMatchCondition "Teams.exe" -IPProtocolMatchCondition Both -IPSrcPortStartMatchCondition 50040 -IPSrcPortEndMatchCondition 50059 -DSCPAction 18 -NetworkProfile All +``` + +**Set QoS for calling and meeting signaling** + +```powershell +new-NetQosPolicy -Name "Teams Calling-Meeting Signaling" -AppPathNameMatchCondition "ms-teams.exe" -IPProtocolMatchCondition UDP -IPSrcPortStartMatchCondition 50070 -IPSrcPortEndMatchCondition 50089 -DSCPAction 40 -NetworkProfile All +new-NetQosPolicy -Name "Classic Teams Calling-Meeting Signaling" -AppPathNameMatchCondition "Teams.exe" -IPProtocolMatchCondition UDP -IPSrcPortStartMatchCondition 50070 -IPSrcPortEndMatchCondition 50089 -DSCPAction 40 -NetworkProfile All ``` @@ -139,7 +151,7 @@ To create a QoS audio policy for domain-joined Windows computers, first log on t 9. On the third page, make sure that both **Any source IP address** and **Any destination IP address** are selected, and then select **Next**. These two settings ensure that packets will be managed regardless of which computer (IP address) sent the packets and which computer (IP address) will receive the packets. 10. On page four, select **TCP and UDP** from the **Select the protocol this QoS policy applies to** drop-down list. TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) are the two networking protocols most commonly used. 11. Under the heading **Specify the source port number**, select **From this source port or range**. In the accompanying text box, type the port range reserved for audio transmissions. For example, if you reserved ports 50000 through ports 50019 for audio traffic, enter the port range using this format: **50000:50019**. Select **Finish**. -12. Repeat steps 5-10 to create policies for Video and Application/Desktop Sharing, substituting the appropriate values in steps 6 and 10. +12. Repeat steps 5-10 to create policies for Video, Application/Desktop Sharing and Calling and Meeting Signaling, substituting the appropriate values in steps 6 and 10. The new policies you've created won't take effect until Group Policy has been refreshed on your client computers. Although Group Policy periodically refreshes on its own, you can force an immediate refresh by following these steps: diff --git a/Teams/QoS-in-Teams.md b/Teams/QoS-in-Teams.md index 39fbe365d4..8272e1c829 100644 --- a/Teams/QoS-in-Teams.md +++ b/Teams/QoS-in-Teams.md @@ -1,7 +1,7 @@ --- title: Implement Quality of Service in Microsoft Teams -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.topic: article ms.service: msteams @@ -148,11 +148,13 @@ The DSCP value tells a correspondingly configured network what priority to give _Recommended initial port ranges_ |Media traffic type| Client source port range |Protocol|DSCP value|DSCP class| -|:--- |:--- |:--- |:--- |:--- | +|:--- |:---: |:---: |:---: |:--- | |Audio| 50,000–50,019|TCP/UDP|46|Expedited Forwarding (EF)| |Video| 50,020–50,039|TCP/UDP|34|Assured Forwarding (AF41)| |Application/Screen Sharing| 50,040–50,059|TCP/UDP|18|Assured Forwarding (AF21)| -||||| +|Calling and Meetings Signaling| 50,070–50,089*|UDP|40|Class Selector 5 (CS5)| + +\* These ports are not currently configurable. Be aware of the following when you use these settings: @@ -162,6 +164,8 @@ Be aware of the following when you use these settings: - If you later need to adjust the port ranges to improve user experience, the port ranges can't overlap and should be adjacent to each other. +- The port ranges used for Calling and Meetings signaling cannot be customized currently. + ## Step 4. Implement QoS settings Implement QoS settings for clients and network devices, and determine how you want to handle media traffic for meetings. diff --git a/Teams/Teams-overview.md b/Teams/Teams-overview.md index b012127b2b..9f1012f33b 100644 --- a/Teams/Teams-overview.md +++ b/Teams/Teams-overview.md @@ -28,10 +28,6 @@ appliesto: If you're the admin for Microsoft Teams in your organization, you're in the right place. When you're ready to get going with Teams, start with [How to roll out Teams](./deploy-overview.md) and [Set up secure collaboration with Microsoft 365 and Microsoft Teams](/microsoft-365/solutions/setup-secure-collaboration-with-teams). -Don't miss our Welcome to Teams for the Teams admin video (just over 3 minutes): - -> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE47cdp] - If you're looking for end user Teams Help, click **Help** on the left side of the app, or go to the [Microsoft Teams help center](https://support.office.com/teams). For training, go to [Microsoft Teams Training](training-microsoft-teams-landing-page.md). > [!IMPORTANT] @@ -43,11 +39,11 @@ Teams is built on Microsoft 365 groups, Microsoft Graph, and the same enterprise When you create a team, here's what gets created: -- A new [Microsoft 365 group](office-365-groups.md) -- A [SharePoint](sharepoint-onedrive-interact.md) site and document library to store team files -- An [Exchange Online](exchange-teams-interact.md) shared mailbox and calendar -- A OneNote notebook -- Ties into other Microsoft 365 apps such as Planner and Power BI +- A new [Microsoft 365 group](office-365-groups.md). +- A [SharePoint](sharepoint-onedrive-interact.md) site and document library to store team files. +- An [Exchange Online](exchange-teams-interact.md) shared mailbox and calendar. +- A OneNote notebook. +- Ties into other Microsoft 365 apps such as Planner and Power BI. When you create a team from an existing group, that group's membership, site, mailbox, and notebook are surfaced in Teams. @@ -58,11 +54,9 @@ To customize and extend Teams, add third-party apps using [app management tasks] ## Managing Teams -As the admin, you'll manage Teams through the Teams admin center. For a quick orientation, watch the Manage Teams using the Teams admin center video (3:03 min): +As the admin, you'll manage Teams through the Teams admin center. -> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE476Yi] - -To learn more: +To learn how to manage Teams in the Teams admin center, see: - [Use Teams admin roles to manage Teams](using-admin-roles.md) - [Manage Teams in the Teams admin center](manage-teams-in-modern-portal.md) @@ -82,12 +76,11 @@ Every team is different; there's no one-size-fits-all approach to collaboration. - **OneDrive** for storing files and sharing them with people that a user invites. Content that a user saves to OneDrive is private until the user shares it with others, making it the best option for storing personal and draft documents that are not intended to be shared or not ready to be shared. -- **Viva Engage** to connect people across the organization. Drive company-wide initiatives, share best practices, and build communities around common topics of interest or areas of practice. Crowdsource ideas to foster open discussions with people across the company. +- **Viva Engage** to connect people across the organization. Drive company-wide initiatives, share best practices, and build communities around common topics of interest or areas of practice. Crowd source ideas to foster open discussions with people across the company. - **Office apps** are all the familiar tools that people know and use regularly, including Word, Excel, PowerPoint, and OneNote. -## Related topics - -[Teams Troubleshooting](/MicrosoftTeams/troubleshoot/teams) +## Related articles -[What's new in Teams](https://support.office.com/article/d7092a6d-c896-424c-b362-a472d5f105de) +- [Teams Troubleshooting](/MicrosoftTeams/troubleshoot/teams) +- [What's new in Teams](https://support.office.com/article/d7092a6d-c896-424c-b362-a472d5f105de) diff --git a/Teams/aa-cq-authorized-users-plan.md b/Teams/aa-cq-authorized-users-plan.md index d327c43713..1fc26b497b 100644 --- a/Teams/aa-cq-authorized-users-plan.md +++ b/Teams/aa-cq-authorized-users-plan.md @@ -8,7 +8,7 @@ ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams audience: admin -ms.date: 03/25/2024 +ms.date: 10/22/2024 ms.collection: - M365-voice - m365initiative-voice @@ -25,9 +25,6 @@ description: Learn the requirements needed to set up authorized users for Auto a # Plan for Auto attendant and Call queue authorized users -> [!NOTE] -> Some of these features are in limited public preview. For more information, contact your Microsoft customer success manager. Information in this article is subject to change. - This article is for IT Pros and administrators who want to delegate certain Auto attendant or Call queue configuration capabilities to the users in their organization. This article describes benefits and licensing requirements. After reading this article, see [Set up authorized users](aa-cq-authorized-users.md) and [Manage voice applications policies](manage-voice-applications-policies.md) for more information. ## Benefits diff --git a/Teams/aa-cq-authorized-users.md b/Teams/aa-cq-authorized-users.md index 5768f78e17..27c573a520 100644 --- a/Teams/aa-cq-authorized-users.md +++ b/Teams/aa-cq-authorized-users.md @@ -8,7 +8,7 @@ ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams audience: admin -ms.date: 03/25/2024 +ms.date: 10/22/2024 ms.collection: - M365-voice - m365initiative-voice @@ -25,9 +25,6 @@ description: Learn how to set up authorized users and what they can manage for A # Set up Auto attendant and Call queue authorized users -> [!NOTE] -> Some of these features are in limited public preview. For more information, contact your Microsoft customer success manager. Information in this article is subject to change. - This article is for IT Pros and administrators who want to delegate Auto attendant and Call queue change capabilities to users in their organization. This article describes the necessary steps to create an Authorized user. Before reading this article, be sure you've read [Plan for authorized users](aa-cq-authorized-users-plan.md), which describes licensing requirements and prerequisites for Auto attendant and Call queue authorized users. diff --git a/Teams/aa-cq-cqd-historical-reports-v164.md b/Teams/aa-cq-cqd-historical-reports-v164.md index 06109413bc..1bb6d47a8c 100644 --- a/Teams/aa-cq-cqd-historical-reports-v164.md +++ b/Teams/aa-cq-cqd-historical-reports-v164.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 08/22/2023 +ms.date: 10/31/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -25,7 +25,7 @@ ms.custom: - ms.teamsadmincenter.directrouting.cqd - ms.lync.lac.ToolsCallQualityDashboard ROBOTS: NOINDEX, NOFOLLOW -description: Learn about how to use the Teams Auto Attendant & Call Queue Historical Report Power BI report to view Auto Attendant and Call Queue historical data for GCC High and DoD customers. +description: Learn about how to use the Teams Auto Attendant & Call Queue Historical Report Power BI report to view Auto attendant and Call queue historical data for GCC High and DoD customers. --- # Auto attendant and call queue historical reports for GCC High and DoD @@ -67,15 +67,15 @@ Perform the following steps: 1. Open the zip file. -1. Navigate to the AACQ sub-folder +1. Navigate to the AACQ subfolder. 1. Open the `CQD Teams Auto Attendant & Call Queue Historical Report V1.64.pbit` template file. Power BI Desktop should launch. -1. You'll be prompted to select the CQD data pipeline region. Select the region where your tenant is located. +1. Once prompted to select the CQD data pipeline region, choose the region where your tenant is located. :::image type="content" source="media/aa-cq-historical-report-01-v164.png" alt-text="Screenshot selecting the CQD data pipeline region."::: - Public Cloud Customers (Not supported but will work): + Public Cloud Customers (not supported but works): 1. The region where your tenant is located can be obtained by using the [Get-CsTenant](/powershell/module/teams/get-cstenant) cmdlet. @@ -85,7 +85,7 @@ Perform the following steps: microsoftcommunicationsonline/noam-4a-s7 ``` - The region will be displayed after the **/** as in the above example where the region is `noam`. + The region is displayed after the **/** as in the above example where the region is `noam`. GCC High and DoD Customers: @@ -94,23 +94,23 @@ Perform the following steps: - GCCH: `cqd.gov.teams.microsoft.us/data` - DoD: `cqd.dod.teams.microsoft.us/data` -1. The report will launch with sample data. +1. The report launches with sample data. 1. To see your own data, select **Refresh** on the **Home** tab under **Queries** in Power BI Desktop. :::image type="content" source="media/aa-cq-historical-report-02-v164.png" alt-text="Screenshot selecting the refresh option."::: -1. You'll be prompted to sign in. Select **Organizational account**, and then select **Sign in**. +1. When prompted to sign in, select **Organizational account**, and then select **Sign in**. :::image type="content" source="media/aa-cq-historical-report-03-v164.png" alt-text="Screenshot showing login for V1.63."::: -1. Select **Connect**, and the data will refresh. +1. After you select **Connect**, the data refreshes. ## Data latency for AA and CQ analytics -Data is typically available within 30 minutes of the call completing; however, there are occasions where it may take several hours for data to appear. +Data is typically available within 30 minutes of the call completing; however, there are occasions where it might take several hours for data to appear. -You'll have to refresh the data to see any new data. +You have to refresh the data to see any new data. ## Customization @@ -171,27 +171,27 @@ Perform the following steps: |Name |Data Type |Description | |:---------------------------------------|:------------------------|:--------------------------------------| -|AA Name |Text |Name of resource account attached to Auto Attendant

If the full Resource Account name is **aa_test@microsoft.com**, then this value will be: **aa_test** | +|AA Name |Text |Name of resource account attached to Auto Attendant

If the full Resource Account name is **aa_test@microsoft.com**, then this value is: **aa_test** | |AACallerActionCount |Whole number |Summarize: Sum
Count of actions selected by caller in Auto Attendant during the call | -|AACallerActionCount (Measure) |Whole number |Same as above except will be 0 if no calls instead of blank | -|AACallFlow |Text |Encapsulates the different states of Auto Attendant Call--possible values:

§ abs_search
§ announcement
§ automatic_menu
§ call_termination
§ call_transfer
§ first_level_menu
§ main_menu
§ speech_input_confirmation
§ user_selection | -|AACallResult |Text |Final call result--possible values:

§ failed_to_establish_media (the media portion of the call couldn't be established)
§ failover_to_operator (call transferred to operator typically due to a system error)
§ oaa_chain_too_long (too many legs in the AA)
§ oaa_session_too_long (AA session has lasted too long)
§ service_declined (AA didn't accept the call)
§ service_terminated (AA configuration disconnects the call or call hung up)
§ terminated_automatic_selection (AA configuration disconnects the calls)
§ terminated_no_operator (call terminated due to error no operator defined)
§ terminated_transfer_failed (call terminated as transfer failed - typically to external number)
§ transfer_in_progress (AA->AA transfer)
§ transferred_to_operator (call was transferred to operator - typically due to user error)
§ transferred_to_receptionist (same as transferred_to_operator)
§ transferred_to_self (call was returned to the start of the AA - typically from a menu announcement option)
§ transferred_to_shared_voicemail (call was transferred to shared voicemail)
§ transferred_to_user (call was transferred to a user - includes call queues)
§ unknown (an unknown condition has occurred)
§ user_terminated (caller hung up) | +|AACallerActionCount (Measure) |Whole number |Same as above except this displays as 0 instead of being blank if there are no calls | +|AACallFlow |Text |Encapsulates the different states of Auto Attendant Call--possible values:

- abs_search
- announcement
- automatic_menu
- call_termination
- call_transfer
- first_level_menu
- main_menu
- speech_input_confirmation
- user_selection | +|AACallResult |Text |Final call result--possible values:

- failed_to_establish_media (the media portion of the call couldn't be established)
- failover_to_operator (call transferred to operator typically due to a system error)
- oaa_chain_too_long (too many legs in the AA)
- oaa_session_too_long (AA session lasted too long)
- service_declined (AA didn't accept the call)
- service_terminated (AA configuration disconnects the call or call hung up)
- terminated_automatic_selection (AA configuration disconnects the calls)
- terminated_no_operator (call terminated due to error no operator defined)
- terminated_transfer_failed (call terminated as transfer failed - typically to external number)
- transfer_in_progress (AA->AA transfer)
- transferred_to_operator (call was transferred to operator - typically due to user error)
- transferred_to_receptionist (same as transferred_to_operator)
- transferred_to_self (call was returned to the start of the AA - typically from a menu announcement option)
- transferred_to_shared_voicemail (call was transferred to shared voicemail)
- transferred_to_user (call was transferred to a user - includes call queues)
- unknown (an unknown condition occurred)
- user_terminated (caller hung up) | |AA Call Legend |Text |Sets up legend items based on AACallResult | |AAChainDuration |Decimal number |Summarize: Sum
Duration of call in Auto Attendant | -|AAChainDuration (Measure) |Decimal number |Same as above except will be 0 if no calls instead of blank | +|AAChainDuration (Measure) |Decimal number |Same as above except displays as 0 instead of blank if there are no calls | |AAChainIndex |Text | | -|AAConnectivityType |Text |Type of call--possible values:

§ ExternalCall
§ InternalCall | +|AAConnectivityType |Text |Type of call--possible values:

- ExternalCall
- InternalCall | |AACount |Text |Number of Auto Attendants involved in call | -|AADirectorySearchMethod |Text |Last address book search method--possible values:

§ abs_search_dtmf
§ abs_search_extension_x
§ abs_search_name | +|AADirectorySearchMethod |Text |Last address book search method--possible values:

- abs_search_dtmf
- abs_search_extension_x
- abs_search_name | |AAStartHour |Decimal number |Auto Attendant call start hour | |AAStartTime |Date/time |Auto Attendant call start time | -|AATransferAction |Text |Call transfer target type--possible values:

§ application - voice application entity
§ external_pstn
§ hunt_group - Call Queue entity
§ orgaa - Auto Attendant entity
§ shared_voicemail
§ unknown
§ user | -|Call Type1 |Text |Type of call--possible values:

§ External
§ Internal | +|AATransferAction |Text |Call transfer target type--possible values:

- application - voice application entity
- external_pstn
- hunt_group - Call Queue entity
- orgaa - Auto Attendant entity
- shared_voicemail
- unknown
- user | +|Call Type1 |Text |Type of call--possible values:

- External
- Internal | |IsAAInvolved |Text |Always 1 | |MM-DD |Text |Auto Attendant call month-day | |PSTNMinutes |Whole number |Summarize: Sum
Total minute usage | |TotalCallCount |Whole number |Summarize: Sum
Always 1 - used to provide sum of all calls | -|Sum of TotalCallCount (Measure) |Whole number |Same as above except will be 0 if no calls instead of blank | +|Sum of TotalCallCount (Measure) |Whole number |Same as above except displays as 0 instead of blank if there are no calls | ### Cloud Call Queue Analytics report @@ -233,37 +233,36 @@ Perform the following steps: |Call Count |Whole number |Summarize: Sum
Number of calls | |Call Queue Agent Count |Whole number |Summarize: Sum
Number of agents configured in the call queue | |Call Queue Agent Opt In Count |Whole number |Summarize: Sum
Number of agents opted-in to the call queue | -|Call Queue Call Result |Text |Call queue call final state--possible values:

§ agent_joined_conference (answered conference mode calls)
§ declined
§ disconnected
§ error
§ failed
§ invalid
§ overflown (overflow condition met)
§ timed_out (timeout condition met)
§ transferred_to_agent (answered transfer mode calls {default}) | +|Call Queue Call Result |Text |Call queue call final state--possible values:

- agent_joined_conference (answered conference mode calls)
- declined
- disconnected
- error
- failed
- invalid
- overflown (overflow condition met)
- timed_out (timeout condition met)
- transferred_to_agent (answered transfer mode calls {default}) | |Call Queue Call Result Legend |Text |Sets up legend items based on Call Queue Result | -|Call Queue Target Type |Text |***Call redirection target type--possible values:***

§ ApplicationEndpoint
§ Mailbox
§ Other
§ User | +|Call Queue Target Type |Text |***Call redirection target type--possible values:***

- ApplicationEndpoint
- Mailbox
- Other
- User | |Call Queue Target Type Legend |Text |Sets up legend items based on Call Queue Target Type | -|Call Type1 |Text |Type of call--possible values:

§ External
§ Internal | -|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value will be: **cq_test** | +|Call Type1 |Text |Type of call--possible values:

- External
- Internal | +|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value is: **cq_test** | |CQ Hour |Whole Number |Call queue call start hour | -|Date |Date/time |Call queue call start date and time (hour) | +|Date |Date/time |Call queue call start date and time (hour) | |DateTimeCQName |Text |Unique key for filtering on fCallQueueFinalStateAction | -|PSTN Connectivity Type |Text |Type of call--possible values:

§ ExternalCall
§ InternalCall | +|PSTN Connectivity Type |Text |Type of call--possible values:

- ExternalCall
- InternalCall | |PSTN Total Minutes |Whole number |Summarize: Sum
Total minutes usage for PSTN calls | -|Sum of Call Count (Measure) |Whole number |Same as Call Count however will be 0 when no call | +|Sum of Call Count (Measure) |Whole number |Same as Call Count except displays as 0 if there are no calls | |TotalCallCount (Measure) |Whole Number |Summarize: Sum
Call Count | - #### fCallQueueFinalStateAction CQD fields description |Name |Data Type |Description | |:---------------------------------------|:------------------------|:--------------------------------------------------| |Average Call Duration (Seconds) |Decimal number |Summarize: Sum
Average call duration in seconds for abandoned calls | |Average Call Queue Duration (Sec) |Decimal number |Summarize: Sum
Average waiting in seconds for answered calls | -|Avg of Average Call Duration (Measure) |Whole number |Same as Average Call Duration (Seconds) however will be 0 when no calls | -|Avg of Average CQ Duration (Measure) |Whole number |Same as Average Call Queue Duration (Sec) however will be 0 when no calls | +|Avg of Average Call Duration (Measure) |Whole number |Same as Average Call Duration (Seconds) however displays as 0 if there are no calls | +|Avg of Average CQ Duration (Measure) |Whole number |Same as Average Call Queue Duration (Sec) however displays as 0 if there are no calls | |Call Count |Whole number |Summarize: Sum
Number of calls | -|Call Queue Call Result |Text |Call queue call final state--possible values:

§ agent_joined_conference (answered conference mode calls)
§ declined
§ disconnected
§ error
§ failed
§ invalid
§ overflown (overflow condition met)
§ timed_out (timeout condition met)
§ transferred_to_agent (answered transfer mode calls {default} | +|Call Queue Call Result |Text |Call queue call final state--possible values:

- agent_joined_conference (answered conference mode calls)
- declined
- disconnected
- error
- failed
- invalid
- overflown (overflow condition met)
- timed_out (timeout condition met)
- transferred_to_agent (answered transfer mode calls {default}) | |Call Queue Call Result Legend |Text |Sets up legend items based on Call Queue Call Result | -|Call Queue Final State Action |Text |Call queue final action--possible values:

§ disconnect (timed_out calls)
§ disconnect_with_busy (overflown calls)
§ failed_to_accept_call
§ forward
§ shared_voicemail
§ other
§ voicemail | -|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value will be: **cq_test** | +|Call Queue Final State Action |Text |Call queue final action--possible values:

- disconnect (timed_out calls)
- disconnect_with_busy (overflown calls)
- failed_to_accept_call
- forward
- shared_voicemail
- other
- voicemail | +|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value is **cq_test** | |Date |Date/time |Call Queue call start date and time (hour) | |DateTimeCQName |Text |Unique key for filtering on fCallQueueFinalStateAction | -|IsAbandoned |True/false |True if call isn't answered by an agent | +|IsAbandoned |True/false |True if agent doesn't answer a call | ### Cloud Call Queue Agent Timeline report @@ -296,37 +295,33 @@ Perform the following steps: |Name |Data Type |Description | |:---------------------------------------|:------------------------|:---------------------------------------------------| -|Agent Name |Text |User UPN
If the full username is **user@microsoft.com**, then this value will be: **user** | +|Agent Name |Text |User UPN
If the full username is **user@microsoft.com**, then this value is **user** | |Average Call Duration (Seconds) |Decimal number |Summarize: Sum
The average duration of answered call queue calls in seconds | |Call Count |Whole number |Summarize: Sum
Number of calls answered by the agent | |Call Duration (Minutes) |Whole number |Summarize: Sum
Total call duration of answered call queue calls in minutes (rounded down to nearest minute) | -|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value will be: **cq_test** | +|CQ Name |Text |Name of resource account attached to Call Queue

If the full Resource Account name is **cq_test@microsoft.com**, then this value is **cq_test** | |Date |Date |Date of call | |DateTime |DateTime |Date of call | |Hour |Whole number |Hour of call | |MM-DD |Text |Month and day of call | > [!NOTE] -> When a call arrives at the first call queue, if the number of calls already waiting in that queue has reached the **Call overflow handling** limit and if the redirect option sends new calls to a second call queue, then the agents in the second call queue will be shown as being in the first call queue on this report. +> When a call arrives at the first call queue, if the number of calls already waiting in that queue has reached the **Call overflow handling** limit and if the redirect option sends new calls to a second call queue, then the agents in the second call queue show as being in the first call queue on this report. ## Known issues - Auto attendant resource account IDs are being masked which prevents reporting by individual auto attendants. Support is investigating. - -- Call queue and auto attendants are shown by the resource account's ID instead of call queue/auto attendant names. To show all the traffic for an auto attendant or call queue, you must select all the resource accounts assigned to the auto attendant or call queue. - +- Call queue and auto attendants are shown by the resource account's ID instead of call queue/auto attendant names. To show all the traffic for an auto attendant or call queue, you must select all the resource accounts assigned to the auto attendant or call queue. - Only 28 days of history are available in the dashboard as call queue/auto attendant data is considered personal data and is subject to data privacy retention policies. - -- In some scenarios, the agent answered call count on the **Cloud Call Queue Agent Timeline** report may be different than the number of calls shown in the Teams client call history. The Teams client call history is correct. Support is investigating, but there's no estimated time to repair available at this time. - -- 1 **Incoming call source** in the auto attendant and call queue graphs show the final call leg source rather than the initial call leg source. For example, if an auto attendant receives an external call and transfers the call to another auto attendant or call queue, the **Incoming call source** will be reported as Internal. +- In some scenarios, the agent answered call count on the **Cloud Call Queue Agent Timeline** report might be different than the number of calls shown in the Teams client call history. The Teams client call history is correct. Support is investigating, but there's no estimated time to repair available at this time. +- 1 **Incoming call source** in the auto attendant and call queue graphs show the final call leg source rather than the initial call leg source. For example, if an auto attendant receives an external call and transfers the call to another auto attendant or call queue, the **Incoming call source** is reported as Internal. ## Version 1.xx history -Refer to: CQD Teams Auto Attendant & Call Queue Historical Reports - Change Log.docx in the downloaded zip file for a detailed list of changes +Refer to **CQD Teams Auto Attendant & Call Queue Historical Reports - Change Log.docx** in the downloaded zip file for a detailed list of changes |Version |Date Published |Filename |Description | -|:--------|:------------------|:------------------------------------------------------------------|:--------------------------------------------------- +|:--------|:------------------|:------------------------------------------------------------------|:---------------------------------------------------| |1.64 |July 14, 2023 |CQD Teams Auto Attendant & Call Queue Historical Report V1.64.pbit |Support for GCC High and DoD clouds | |1.63 |August 24, 2022 |CQD Teams Auto Attendant & Call Queue Historical Report V1.63.pbit | | |1.60 |July 22, 2022 |CQD Teams Auto Attendant & Call Queue Historical Report V1.60.pbit | | diff --git a/Teams/aa-cq-cqd-historical-reports.md b/Teams/aa-cq-cqd-historical-reports.md index 877f934241..8c3525222f 100644 --- a/Teams/aa-cq-cqd-historical-reports.md +++ b/Teams/aa-cq-cqd-historical-reports.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 09/27/2024 +ms.date: 11/22/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -54,7 +54,7 @@ These reports use data from the Voice Applications Analytics Collector (VAAC) se You need to have Power BI Desktop installed. You can install and use the free version from the [Microsoft Windows Store](https://aka.ms/pbidesktopstore). > [!IMPORTANT] -> Power BI Desktop is updated and released on a monthly basis, incorporating customer feedback and new features. Only the most recent version of Power BI Desktop is supported; customers who contact support for Power BI Desktop will be asked to upgrade to the most recent version. You can get the most recent version of Power BI Desktop from the [Windows Store](https://aka.ms/pbidesktopstore), or as a single executable containing all supported languages that you [download](https://www.microsoft.com/download/details.aspx?id=58494) and install on your computer. +> Power BI Desktop is updated and released on a monthly basis, incorporating customer feedback and new features. Only the most recent version of Power BI Desktop is supported. Customers who contact support for Power BI Desktop are asked to upgrade to the most recent version. You can get the most recent version of Power BI Desktop from the [Windows Store](https://aka.ms/pbidesktopstore), or as a single executable containing all supported languages that you [download](https://www.microsoft.com/download/details.aspx?id=58494) and install on your computer. ### Power BI Service @@ -91,7 +91,7 @@ Use one of the following methods to control access to the historical reports: 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. + > If a user is assigned a CQD access role and a voice applications policy, the CQD role takes precendence and the user can see all the Auto attendants, Call queues, and Agents in the tenant. ## V3.x.x desktop installation @@ -605,6 +605,9 @@ A valid query consists of several attributes in a JSON object: - **LimitResultRowsCount**: the max count of rows returned by VAAC +>[!NOTE] +> When you submit a query that searches by `Date`, and the search criteria includes both date and time (ISO 8601 format), the time portion is ignored. + ## Accessing VAAC outside of Power BI Any application that can access RESTful web services can use the VAAC API to retrieve historical data. In the following example, [Postman](https://www.postman.com/) is used. diff --git a/Teams/add-change-remove-emergency-location-organization.md b/Teams/add-change-remove-emergency-location-organization.md index e84a7e7bc4..8003a289ff 100644 --- a/Teams/add-change-remove-emergency-location-organization.md +++ b/Teams/add-change-remove-emergency-location-organization.md @@ -1,7 +1,7 @@ --- title: Manage emergency locations -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: serdars ms.reviewer: jastark, roykuntz ms.date: 09/24/2024 diff --git a/Teams/add-change-remove-emergency-place-organization.md b/Teams/add-change-remove-emergency-place-organization.md index 488b23c2a7..59f762907c 100644 --- a/Teams/add-change-remove-emergency-place-organization.md +++ b/Teams/add-change-remove-emergency-place-organization.md @@ -1,7 +1,7 @@ --- title: Add places to emergency locations -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jastark, roykuntz ms.date: 06/26/2023 diff --git a/Teams/advanced-collaboration-analytics.md b/Teams/advanced-collaboration-analytics.md index 58de45ddee..deaeb05fd2 100644 --- a/Teams/advanced-collaboration-analytics.md +++ b/Teams/advanced-collaboration-analytics.md @@ -54,6 +54,8 @@ You can also archive the team directly from the report. However, archiving a tea To archive an inactive team, under the **Action** column, select the **bin** icon. In the *Archive team?* dialog box, select **Archive**. +A value for **Last activity date (UTC)** is displayed only if teams activity has taken place after October 2023. + > [!NOTE] > SharePoint Administrators with a [Microsoft Syntex - SharePoint Advanced Management](/sharepoint/advanced-management) license can use [site lifecycle policies](/sharepoint/site-lifecycle-management) in the SharePoint admin center to detect inactive sites, including team-connected sites. @@ -65,7 +67,7 @@ This card is only available if you've configured an allowlist in [external acces :::image type="content" source="media/inactive-external-domains.png" alt-text="Screenshot that shows the total number of allowed domains."::: -Select **View details** to see which domains are inactive, including the last activity date. A value for **Last activity date (UTC)** is displayed only if domain activity has taken place after the purchase of Teams Premium. +Select **View details** to see which domains are inactive, including the last activity date. A value for **Last activity date (UTC)** is displayed only if domain activity has taken place after October 2023. You can change the time frame by choosing a date range from the **Date range** dropdown and selecting **Run report**. diff --git a/Teams/alerts/teams-admin-alerts.md b/Teams/alerts/teams-admin-alerts.md index 45aa677558..df2b8d7ab8 100644 --- a/Teams/alerts/teams-admin-alerts.md +++ b/Teams/alerts/teams-admin-alerts.md @@ -1,13 +1,13 @@ --- title: Microsoft Teams Monitoring and Alerting -ms.author: jtremper -author: jacktremper -manager: pamgreen +ms.author: heidip +author: MicrosoftHeidi +manager: jtremper audience: Admin ms.topic: conceptual ms.service: msteams ms.reviewer: vapati -ms.date: 07/30/2023 +ms.date: 10/30/2024 f1.keywords: ms.localizationpriority: medium search.appverid: diff --git a/Teams/anonymous-users-in-meetings.md b/Teams/anonymous-users-in-meetings.md index 708f401121..4c0334e74e 100644 --- a/Teams/anonymous-users-in-meetings.md +++ b/Teams/anonymous-users-in-meetings.md @@ -22,7 +22,7 @@ description: For IT Pros - Learn how anonymous meeting participation works in Mi # Manage anonymous participant access to Teams meetings, webinars, and town halls (IT admins) -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls Anonymous participants in meetings, webinars, and town halls hosted by your organization are those participants who can't be verified. This could include: diff --git a/Teams/answer-auto-attendant-and-call-queue-calls.md b/Teams/answer-auto-attendant-and-call-queue-calls.md index 6a76e466bd..bbe8b8f0d4 100644 --- a/Teams/answer-auto-attendant-and-call-queue-calls.md +++ b/Teams/answer-auto-attendant-and-call-queue-calls.md @@ -5,10 +5,10 @@ author: mkbond007 ms.author: mabond manager: pamgreen audience: ITPro -ms.date: 08/01/2023 +ms.date: 10/31/2024 ms.topic: conceptual ms.service: msteams -description: Describes Cloud Auto attendants and Call queues, and explains how you can answer these calls in Teams. +description: Describes Cloud Auto attendants and Call queues, and explains how you can answer these calls in Microsoft Teams. f1.keywords: - NOCSH ms.localizationpriority: medium @@ -35,41 +35,41 @@ Cloud Call queues include greetings that are used when someone calls in to a pho ## Handling an Auto attendant or Call queue call -Users will be able to differentiate incoming calls from an Auto attendant or Call queue before they answer the call. Along with the name and/or number of the caller, each call will include the display name of the resource account assigned to the Auto attendant or the Call queue that the caller was trying to reach, giving users a better context for addressing the caller. +Users can differentiate incoming calls from an Auto attendant or Call queue before they answer the call. Along with the name and/or number of the caller, each call includes the display name of the resource account assigned to the Auto attendant or the Call queue that the caller was trying to reach, giving users better context for addressing the caller. -The following illustration shows how an incoming call from an Auto attendant or Call queue will appear to a user. +The following illustration shows how an incoming call from an Auto attendant or Call queue appears to a user. ![Screenshot of an incoming call notification.](media/answer-auto-attendant-and-call-queue-calls-image1.png) -Once an Auto attendant or Call queue call is answered, the user can process the call like any other call — they can add or conference in another user or transfer the call to another party. Also, Auto attendant calls will be forwarded based on the user's configuration. +Once an Auto attendant or Call queue call is answered, the user can process the call like any other call — they can add or conference in another user or transfer the call to another party. Also, Auto attendant calls are forwarded based on the user's configuration. -> [!NOTE] -> Call queue calls are not forwarded based on the user's call answering rules configuration. This is to ensure callers remain in the queue until an agent can answer the call and the caller isn't forwarded unexpectedly. +> [!NOTE] +> Call queue calls aren't forwarded based on the user's call answering rules configuration. This ensures that callers remain in the queue until an agent can answer the call and that the caller isn't forwarded unexpectedly. > -> Users receiving calls from Call queues will only be presented with the name of the caller if it's provided from the PSTN or if the caller's number matches the target user's local Team's client contacts. +> Users receiving calls from Call queues are only presented with the name of the caller if it's provided from the Public Switched Telephone Network (PSTN) or if the caller's number matches the target user's local Teams client contacts. > -> Agents are not notified of any missed calls or voicemails for Call queue calls. +> Agents aren't notified of any missed calls or voicemails for Call queue calls. ## Supported clients Support for Auto attendant and Call queue calls is available in the following clients: -- Microsoft Teams Windows client (32 and 64-bit versions) +- Microsoft Teams Windows client (32-bit and 64-bit versions) - Microsoft Teams Mac client - Microsoft Teams iPhone app - Microsoft Teams Android app -The Teams client is only supported with a [co-existence mode of Teams Only](/microsoftteams/setting-your-coexistence-and-upgrade-settings). +The Teams client is only supported with a [coexistence mode of Teams Only](/microsoftteams/setting-your-coexistence-and-upgrade-settings). ## Configure Auto attendant and Call queue support for Microsoft Teams -To receive Auto attendant and Call queue calls on Microsoft Teams, you need to configure your interoperability policy and upgrade policy. Please review [Migration and interoperability for organizations using Teams together with Skype for Business](migration-interop-guidance-for-teams-with-skype.md). If you do not have Auto attendant and/or Call queue configured and would like to do so, see [Set up a Cloud Auto attendant](create-a-phone-system-auto-attendant.md) and [Create a Cloud Call queue](create-a-phone-system-call-queue.md). +To receive Auto attendant and Call queue calls on Microsoft Teams, you need to configure your interoperability policy and upgrade policy. For more information, review [Migration and interoperability for organizations using Teams together with Skype for Business](migration-interop-guidance-for-teams-with-skype.md). If you don't have Auto attendants and/or Call queues configured and would like to do so, see [Set up a Cloud Auto attendant](create-a-phone-system-auto-attendant.md) and [Create a Cloud Call queue](create-a-phone-system-call-queue.md). ## Known Issues -When a Call queue agent receives a call on their mobile device, the call may go on hold if the device is locked. Users must unlock the device first and then answer the call. +When a Call queue agent receives a call on their mobile device, the call might go on hold if the device is locked. Users must unlock the device first and then answer the call. -## Related topics +## Related articles [Create a Cloud Call queue](create-a-phone-system-call-queue.md) diff --git a/Teams/app-centric-management.md b/Teams/app-centric-management.md index de517f043c..21b8be15ac 100644 --- a/Teams/app-centric-management.md +++ b/Teams/app-centric-management.md @@ -13,7 +13,7 @@ ms.collection: - M365-collaboration - Tier1 search.appverid: MET150 -ms.date: 08/27/2024 +ms.date: 11/14/2024 ms.reviewer: mhayrapetyan description: Manage access to Teams apps using app centric management. f1.keywords: @@ -27,16 +27,22 @@ ms.custom: seo-marvel-apr2020 # Use app centric management to manage access to apps > [!IMPORTANT] -> All organizations don't have app centric management feature available. If you were not using custom permission policies and you weren't an enterprise customer, we migrated your organization to use this feature. If you are using custom permission policies or you are an enterprise customer, then you will soon be able to migrate to the app centric management feature on your own. For timelines, see [Message Center post MC688930](https://admin.microsoft.com/Adminportal/Home#/MessageCenter/:/messages/MC688930) or [Microsoft 365 roadmap item 151829](https://www.microsoft.com/en-US/microsoft-365/roadmap?filters=&searchterms=151829). -> -> If you see policies on the [permission policies page](https://admin.teams.microsoft.com/policies/app-permission), continue to [use app permission policies](teams-app-permission-policies.md) or migrate to this feature on your own. -> If your org is now using the app centric management feature, you see the following message on the permission policy page. +> All organizations don't have app centric management feature available. If you were not using custom permission policies and you weren't an enterprise customer, we automatically migrated your organization to use this feature. You see the following message on the permission policy page: > > :::image type="content" source="media/acm-policy-page.png" alt-text="Screenshot showing the permissions policy change for organization that are using app centric management."::: +> +> If you're using custom permission policies or you're an enterprise customer, then you must manually migrate to the app centric management feature. For timelines, see [Message Center post MC688930](https://admin.microsoft.com/Adminportal/Home#/MessageCenter/:/messages/MC688930) or [Microsoft 365 roadmap item 151829](https://www.microsoft.com/en-US/microsoft-365/roadmap?filters=&searchterms=151829). +> +> If you see policies on the [permission policies page](https://admin.teams.microsoft.com/policies/app-permission), continue to [use app permission policies](teams-app-permission-policies.md) or migrate to this feature on your own. + +With the introduction of app centric management functionality, admins have two methods to control the access and availability of apps and Copilot agents. + +* Continue to [use permission policies](teams-app-permission-policies.md). +* Use the feature if already auto-migrated or [manually migrate to app centric management](#migrate-to-app-centric-management). It replaces app permission policies. -App centric management functionality introduces a new way to control access to Teams apps for users and groups. It replaces app permission policies. This functionality lets you specify which users and groups can use each app and you can control it on a per-app basis. +This functionality lets you specify which users and groups can use each app or a Copilot agent and you can control it on a per-app basis. -You can manage access to apps for individual users, supported groups, or everyone in the organization. You have complete control over who can or can't add apps in your organization. You can also control the access to new apps that we publish to Teams app store. +Whatever method your use, you can manage access to apps for individual users, supported groups, or everyone in the organization. You have complete control over who can or can't add apps in your organization. You can also control the access to new apps that we publish to Teams app store. ## How is app centric management different than permission policy @@ -67,7 +73,7 @@ Previously, we automatically migrated organizations that weren't using any custo | Assisted | Administrator | Org uses one or more custom policies | Guided UI in admin center | | Automatic | Microsoft | Org uses only the default global policy | Automatic, without admin intervention | -We strongly recommend that you prepare for the migration and follow these steps to prepare: +To migrate your organization, follow these steps: 1. Log into Teams admin center and access Teams apps > [Permission policies](https://admin.teams.microsoft.com/policies/app-permission) page. Take inventory of the apps in the permission policies and identify the users and groups that the apps are allowed or blocked for. During the migration, you may have to manually edit the availability for some apps for the existing users and groups. For details, see step 5. @@ -85,31 +91,31 @@ We strongly recommend that you prepare for the migration and follow these steps * Available to specific users and groups: List of apps that are selectively allowed for at least one org user or a supported group. * Available to no one: List of apps that nobody in the org can use. -1. In each tab, you can modify the app availability to one of the [three app availability types](#how-is-app-centric-management-different-than-permission-policy), as necessary. Edit availability option appears in **Available to specific users and groups** tab if the app availability isn't clear and admin input is needed to proceed. It is because the apps aren't present in the policies that you selected to migrate or have conflicting availability. You must assign such apps to before you can proceed. +1. In each tab, you can modify the app availability to one of the [three app availability types](#how-is-app-centric-management-different-than-permission-policy), as necessary. Edit availability option appears in **Available to specific users and groups** tab if the app availability isn't clear and admin input is needed to proceed. Either the apps aren't present in the policies that you selected to migrate or selected policies contain conflicting availability. You must assign such apps to one of the availability types before you can proceed. - :::image type="content" source="media/acm-migration-availability.png" alt-text="Screenshot showing three tabs during migration that help you review and modify the app availability."::: + :::image type="content" source="media/acm-migration-availability.png" alt-text="Screenshot showing three tabs during migration that help you review and modify the app availability." lightbox="media/acm-migration-availability.png"::: > [!TIP] - > If you see many apps in this tab, you likely have policies that have conflicting apps availability. For example, a policy that allows many apps and another policy that blocks the same apps. In such a scenario, we recommend that you uncheck the policy that leads to a conflict or you edit the availability in this tab. + > If you see many apps in this tab, you likely have policies that have conflicting apps availability. For example, a policy that allows an app and another policy that blocks the same app. In such a scenario, we recommend that you uncheck the policy that leads to a conflict or you edit the availability in this tab. 1. You can validate the changes on a per-app or a per-user basis. Select a tab and type the name of the app or the user. :::image type="content" source="media/acm-verify-per-app.png" alt-text="Screenshot showing the option to verify available of for each user and users who receive a particular app." lightbox="media/acm-verify-per-app-large.png"::: -1. On the final review UI, you can see the apps, their availability, and the Org-wide app settings that apply after the migration. You can download this information as a CSV file to evaluate further. For example, you can use the inventory mapping from Step 1 to ensure that the app availability is as intended. Once assured, select **Start migration** and follow the prompts. +1. On the final review UI, you can see the apps, their availability, and the Org-wide app settings that apply after the migration. You can download this information as a CSV file to evaluate further. For example, you can use the inventory mapping from Step 1 to ensure that the app availability is as intended. Once assured, select **Start migration** and follow the prompts. Migration may take up to 24 hours to complete. - :::image type="content" source="media/acm-migration-review.png" alt-text="Screenshot showing the last UI to review all settings."::: + :::image type="content" source="media/acm-migration-review.png" alt-text="Screenshot showing the last UI to review all settings." lightbox="media/acm-migration-review-large.png"::: -During migration, you can save a draft of the migration progress using the **Finish later** option. Also, you can cancel and delete the saved draft using the **Reset all changes** option. +During migration, you can save a draft of the migration progress using the **Finish later** option. You can cancel the migration and delete the saved draft using the **Reset all changes** option. > [!NOTE] -> The existing Manage apps UI gets disabled when you start the migration. If you aren't ready to proceed or want to make change to the exiting permission policies, open the wizard and select the Reset all changes option. You can restart the migration again. +> While migrating, you can't make changes to app assignments. The existing UI gets disabled when you start the migration. If you aren't ready to proceed or want to make change to the exiting permission policies, open the migration wizard and select the Reset all changes option. You'll lose the progress and can restart the migration later. -After migration, your blocked apps continue to remain unavailable to users. The statuses of such apps show as `unblocked` now, but the apps are assigned to `No one` in the `Available to` column on the Manage apps page. It means that org user can't use the app, just as you intended before. +After migration, your blocked apps continue to remain unavailable to users. The statuses of such apps show as `unblocked` now, but the apps are assigned to `No one` in the `Available to` column on the Manage apps page. It means that org user can't use the app, just as you intended before. Users can view the apps in store and [request access to apps](user-requests-approve-apps.md). ## Add or modify app availability for users -To let users add and use an app, you must assign users or groups to an app. It takes up to 24-72 hours for the changes to take effect. In rare cases, it may take up to 6 days for the availability changes to reflect in the client. +To let users add and use an app or a copilot agent, you must assign users or groups to an app. To make any apps or copilot agents available in your organization, ensure that the settings to allow these are the same in Teams admin center and in [Microsoft 365 admin center](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps) in the Integrated Apps page. It takes up to 24 hours for the changes to take effect. In rare cases, it may take up to 6 days for the availability changes to reflect in the client. 1. In Teams admin center, go to the [Manage apps](https://admin.teams.microsoft.com/policies/manage-apps) page, search for the required app, and select the app name to open its app details page. You can't assign apps in bulk. @@ -119,7 +125,7 @@ To let users add and use an app, you must assign users or groups to an app. It t 1. Select the required option from **Manage who can install this app** menu. When assigning users or groups, search for the user or the group from the **Search for users or groups** menu. Select **Apply**. - :::image type="content" source="media/acm-add-modify-access.png" alt-text="Screenshot showing how to define the app availability from the app details page."::: + :::image type="content" source="media/acm-add-modify-access.png" alt-text="Screenshot showing how to define the app availability from the app details page." lightbox="media/acm-add-modify-access.png"::: 1. To remove one or more users or groups from an app, select the rows and select **Remove**. diff --git a/Teams/app-ownership-developer-portal.md b/Teams/app-ownership-developer-portal.md new file mode 100644 index 0000000000..ec9e235eef --- /dev/null +++ b/Teams/app-ownership-developer-portal.md @@ -0,0 +1,78 @@ +--- +title: Ownership of apps in Developer Portal +author: ashishguptaiitb +ms.author: guptaashish +manager: prkosh +ms.topic: article +ms.service: msteams +audience: admin +ms.subservice: teams-apps +ms.date: 10/21/2024 +ms.collection: +- Teams_ITAdmin_Help +- M365-collaboration +search.appverid: +f1keywords: +description: +appliesto: +- Microsoft Teams +ms.localizationpriority: medium +--- + +# Manage Microsoft Teams app ownership in Developer Portal + +App developers use [Developer Portal](/microsoftteams/platform/concepts/build-and-test/teams-developer-portal) to configure, distribute, and manage their Teams apps. Developers who create or import an app in Developer Portal becomes the owner of the app. An app owner can add other org users as owners as well. + +An owner may leave the organization or can delete the app from the portal after the app is published. In such cases, a Global Administrator can help in the following ways: + +* Take over the ownership of an app and add other developers as owners. +* Import the app if it was created outside of Developer Portal or was deleted from the portal. + +The above tasks help admins to let another developer work on the app and manage it, hence maintaining business continuity. + +## Admin takes ownership of a custom app + +Your organization can use a custom app that is available just within your org and not on the Teams store. It's created for and managed within your org. +Admins can take ownership of a custom app in the following scenarios: + +* Custom app that is available in the portal. +* Custom app that wasn't created in or is removed from the portal. + +### Take ownership of custom app available in the portal + +If a custom app exists in the portal, then taking ownership isn't possible for a user. Admins can either import the zip archive or take ownership in the following ways. + +| Role | Available option | Outcome on app ownership | +|------|------------------|--------------------------| +| Admin | Import > Replace | Recommended approach if you have the app zip archive. Retains app ID of previous app so the app remains the same. The portal overwrites ownership making you the sole owner. You can add new org users as owners. | +| Admin | Take ownership | Recommended approach if you know the app ID. The portal adds you as yet another app owner. You can add other users as developers. | +| Admin | Import > Replace | Creates a new app ID and makes the admin as owner. No relation to the previous app. | +| User | Import | Creates a new app ID so no relation to the previous app. Uploader is the owner and can add other developers. | + +> [!TIP] +> To know the app ID, use the app details page in the Teams admin center. If the app is deleted from admin center, then import the zip archive of the app. + +### Take ownership of custom app not available in the portal + +It is possible to create a custom app without using the Developer Portal or to delete it after creation. In this case, your org doesn't have the app available in the portal. You can import or take ownership in the following ways. + +| Role | Available option | Outcome on app ownership | +|------|------------------|--------------------------| +| Admin | Import | Provide app ID in the import dialog. The portal makes you the sole owner and you can add other users as owners. There's no impact on the app as it doesn't exist in the portal. | +| Admin | Take ownership | If app was created in the portal, admin can provide app ID and take ownership as the sole owner. It doesn't work if app was created outside the portal. | +| User | - | Not possible for a user to either import or to take ownership. | + +## Admin takes ownership of a Store app + +An org can publish its app to [Microsoft AppStore](https://appsource.microsoft.com) using Partner Center UI. + +In the above cases, you as an admin can reclaim the ownership of the app in Developer Portal by contacting Microsoft Support. To ascertain the ownership, provide the following details to Microsoft Support: + +* Proof of ownership of the app: Provide a screenshot of the email approval from Microsoft app validation team. When an org submits a Teams app in Partner Center, Microsoft validates the app and contacts from `teamsubm@microsoft.com` email ID. Microsoft app validation team lets your org know that the app is approved for publishing to the AppStore. +* Your tenant ID. +* Your app's ID. + +## Related articles + +* [Know about Developer Portal](/microsoftteams/platform/concepts/build-and-test/teams-developer-portal). +* [Developer Portal Teams app](https://teams.microsoft.com/l/app/14072831-8a2a-4f76-9294-057bf0b42a68). diff --git a/Teams/app-powered-tasks-in-planner.md b/Teams/app-powered-tasks-in-planner.md new file mode 100644 index 0000000000..19e5841c5d --- /dev/null +++ b/Teams/app-powered-tasks-in-planner.md @@ -0,0 +1,235 @@ +--- +title: Manage app-powered tasks in Planner for tailored task experiences +author: lana-chin +ms.author: v-chinlana +manager: jtremper +ms.topic: conceptual +ms.service: msteams +ms.reviewer: andfried +ms.date: 11/14/2024 +search.appverid: MET150 +searchScope: + - Microsoft Teams +audience: admin +description: Learn how to create and manage app-powered tasks in the Planner app in Teams to provide tailored task experiences. +ms.localizationpriority: medium +appliesto: + - Microsoft Teams +ms.collection: +- M365-collaboration +- m365-frontline +- teams-1p-app-admin +- highpri +--- + +# Manage app-powered tasks in Planner for tailored task experiences + +> [!NOTE] +> This feature is currently in public preview. + +## Overview + +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. + +- 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. + +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. + +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. + +## 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. +- 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: + + - Create the task. See [Create businessScenarioTask](/graph/api/businessscenarioplanner-post-tasks?view=graph-rest-beta). + - Assign the task. See [Update businessScenarioTask](/graph/api/businessscenariotask-update?view=graph-rest-beta). + - Update the task, if properties change. See [Update businessScenarioTask](/graph/api/businessscenariotask-update?view=graph-rest-beta). + - 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. + +## 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. + +**Request** + +```http +POST https://graph.microsoft.com/beta/solutions/businessScenarios/{your-business-scenario-ID}/planner/tasks + +{ +"title": "{Task title}", + "target": { + "@odata.type": "#microsoft.graph.businessScenarioGroupTarget", + "taskTargetKind": "group", + "groupId": "{group ID of team}" + }, + "businessScenarioProperties": { + "externalObjectId": "{any unique ID, for example, the ID of the object in your destination app}", + "externalBucketId": "{any bucket ID from planConfiguration of your business scenario}" + }, + "assignments": { + "{user ID of user you want to assign the task to}": { + "@odata.type": "#microsoft.graph.plannerAssignment", + "orderHint": " !" + } + }, + "details": { + "references": { + "{reference URL}": { + "@odata.type": "microsoft.graph.plannerExternalReference", + "alias": "{destination app name}", + "previewPriority": " !", + "type": "TeamsHostedApp" + } + } + } +} +``` + +### Define the attachment + +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. + +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. + +```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`.| + +#### Configure the reference URL + +##### Format 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. + +|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. | +|`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: + +`https://teams.microsoft.com/l/stage/com.microsoft.teamspace.tab.youtube/0?context={"contentUrl":"https://tabs.teams.microsoft.com/youtubeContentStage?videoId=HBGmSy1iVmY","name":"Security%20talk","openMode":"modal"}` + +In this example: + +- `Teams-app-Id` is the app ID of the YouTube app in Teams (`com.microsoft.teamspace.tab.youtube`). Keep in mind that most Teams app IDs are alphanumeric and might look different. +- `URL-to-destination-experience` points to the experience within the destination Teams app (`https://tabs.teams.microsoft.com/youtubeContentStage?videoId=HBGmSy1iVmY`). +- `page-title` is the name of the screen title (`Security talk`) when loading the URL. + +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 + +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. + +Follow these steps to encode the reference URL. We use the example reference URL described earlier to demonstrate how to encode the URL. + +1. Percent encode the part of the URL that comes after `0?context=`. Don't encode `https://` or `=` (the equal symbol), or any of the characters in between. + + `https://teams.microsoft.com/l/stage/com.microsoft.teamspace.tab.youtube/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Ftabs.teams.microsoft.com%2FyoutubeContentStage%3FvideoId%3DHBGmSy1iVmY%22%2C%22name%22%3A%22Security%2520talk%22%2C%22openMode%22%3A%22modal%22%7D` + + > [!TIP] + > This is the last step where the link can be easily validated in Teams chat. After you complete this step, you can test the URL by sending it to yourself in a Teams chat. The link should open on Teams desktop, web, or mobile for any user who has access to the destination app in Teams. + +1. Replace *all* `.` characters in the reference URL with `%2E`. You must do this across all characters in the reference URL, from beginning to end. If you skip this step, the reference URL might not work. + + The following URL is ready for programmatic use. + + `https://teams%2Emicrosoft%2Ecom/l/stage/com%2Emicrosoft%2Eteamspace%2Etab%2Eyoutube/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Ftabs%2Eteams%2Emicrosoft%2Ecom%2FyoutubeContentStage%3FvideoId%3DHBGmSy1iVmY%22%2C%22name%22%3A%22Security%2520talk%22%2C%22openMode%22%3A%22modal%22%7D` + + > [!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. + +## 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. + +**Request** + +```http +POST https://graph.microsoft.com/beta/solutions/businessScenarios/ccd5aa8aebd048bd839a4fa5b7420631/planner/tasks + +{ +"title": "Review security practices presentation", + "target": { + "@odata.type": "#microsoft.graph.businessScenarioGroupTarget", + "taskTargetKind": "group", + "groupId": "769bbf41-70b7-4ea6-a044-a7037358883e" + }, + "businessScenarioProperties": { + "externalObjectId": "SP-202418", + "externalBucketId": "Security practices" + }, + "assignments": { + "44ee44ee-ff55-aa66-bb77-88cc88cc88cc": { + "@odata.type": "#microsoft.graph.plannerAssignment", + "orderHint": " !" + } + }, + "details": { + "references": { + "https://teams%2Emicrosoft%2Ecom/l/stage/com%2Emicrosoft%2Eteamspace%2Etab%2Eyoutube/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Ftabs%2Eteams%2Emicrosoft%2Ecom%2FyoutubeContentStage%3FvideoId%3DHBGmSy1iVmY%22%2C%22name%22%3A%22Security%2520talk%22%2C%22openMode%22%3A%22modal%22%7D": { + "@odata.type": "microsoft.graph.plannerExternalReference", + "alias": "Security practices presentation", + "previewPriority": " !", + "type": "TeamsHostedApp" + } + } + } +} +``` + +### 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. + +:::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"::: + +To learn more about the user experience, see [Work with app-powered tasks in the Planner app in Teams](https://support.microsoft.com/topic/16d2f882-aad5-4346-a459-4dfd9fc9a457). + +## Related articles + +- [Use the business scenarios API in Microsoft Graph to integrate with Planner](/graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta) +- [Manage the Planner app for your organization in Microsoft Teams](manage-planner-app.md) diff --git a/Teams/apps-in-teams.md b/Teams/apps-in-teams.md index fc515f0733..441cbfe6f5 100644 --- a/Teams/apps-in-teams.md +++ b/Teams/apps-in-teams.md @@ -178,6 +178,7 @@ The following apps are provided by Microsoft and are generally available: * Praise * Project * PTZ Camera Controls +* Queues App * Roadmap – Microsoft Project * Selfhost - Avatars * SharePoint diff --git a/Teams/assign-change-or-remove-a-phone-number-for-a-user.md b/Teams/assign-change-or-remove-a-phone-number-for-a-user.md index e942b4e5af..b1115a4c90 100644 --- a/Teams/assign-change-or-remove-a-phone-number-for-a-user.md +++ b/Teams/assign-change-or-remove-a-phone-number-for-a-user.md @@ -1,7 +1,7 @@ --- title: "Manage phone numbers for users" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: julienp, roykuntz, jastark ms.date: 02/14/2024 diff --git a/Teams/audio-conferencing-dial-out-usage-report.md b/Teams/audio-conferencing-dial-out-usage-report.md index 0afe93a763..aaa05daad9 100644 --- a/Teams/audio-conferencing-dial-out-usage-report.md +++ b/Teams/audio-conferencing-dial-out-usage-report.md @@ -1,10 +1,10 @@ --- title: Audio Conferencing dial-out usage report -ms.author: jtremper -author: jacktremper +ms.author: jenz +author: jenzamora manager: pamgreen -ms.reviewer: -ms.date: 11/16/2023 +ms.reviewer: oscarr +ms.date: 10/24/2024 ms.topic: conceptual ms.tgt.pltfrm: cloud ms.service: msteams @@ -28,15 +28,15 @@ description: "Learn which countries/regions have dial-in conferencing numbers, a # Audio Conferencing dial-out usage report -The Audio Conferencing dial-out usage report in the Teams admin center gives you an overview of usage and dollars spent for the audio conferencing dial-out service. This report allows admins to consume user-level data in terms of communication credits spent and dial-out minutes used. It will help admins determine the future communication credits needed going forward from any point in time. +The Audio Conferencing dial-out usage report in the Teams admin center provides an overview of usage and expenses for the audio conferencing dial-out service. As an admin, this report allows you to analyze user-level data, including communication credits spent and dial-out minutes used. This insight helps you accurately estimate future communication credit requirements. ## View the Audio Conferencing dial-out usage report -In the left navigation of the Microsoft Teams admin center, select **Analytics & reports** \> **Usage reports**. On the **View reports** tab, under **Report**, select the **Audio Conferencing dial-out usage report**. +1. In the Microsoft Teams admin center, expand **Analytics & reports** > **Usage reports**. In the **View reports** tab, for the **Report** dropdown, select the **Audio Conferencing dial-out usage report**. -Under **Date range**, you can select a predefined range of 7 or 28 days, or set a custom range. +2. In the **Date range** dropdown, you can select a predefined range of 7 or 28 days, or set a custom range. -Under **Country Previsioned**, select a preferred country/region, or select all, and then select **Run report**. +3. In the **Country or region provisioned** dropdown, select a preferred country/region, or select all, and then select **Run report**. ## Report details @@ -83,3 +83,8 @@ The bottom of the page has a table, which shows user level breakdowns with the f If you need to search for usage for a specific user, there's a search bar on the right above the report. The meeting organizer names are all selectable hyperlinks that take you to a more detailed usage report for the user. This user view has the same three tabs as the main report, however the chart at the top of the page shows details for that specific user. You can export any report shown in this table to a CSV file for offline analysis. Select **Export to Excel**, and then on the **Downloads** tab, select **Download** to download the report when it's ready. + +## Related topics + +- [Plan Audio Conferencing for Microsoft Teams meetings](/microsoftteams/audio-conferencing-in-office-365) +- [Audio Conferencing complimentary dial-out](/microsoftteams/complimentary-dial-out-period) diff --git a/Teams/block-external-content-share.md b/Teams/block-external-content-share.md index e0f578b987..799e1846ec 100644 --- a/Teams/block-external-content-share.md +++ b/Teams/block-external-content-share.md @@ -21,7 +21,7 @@ appliesto: [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls ## Overview diff --git a/Teams/block-inbound-calls.md b/Teams/block-inbound-calls.md index 6e7c325c12..bf1626fb1a 100644 --- a/Teams/block-inbound-calls.md +++ b/Teams/block-inbound-calls.md @@ -11,8 +11,8 @@ ms.collection: - m365initiative-voice - Tier1 audience: Admin -ms.reviewer: jenstr, roykuntz -ms.date: 09/27/2023 +ms.reviewer: jastark, roykuntz +ms.date: 10/29/2024 appliesto: - Microsoft Teams ms.localizationpriority: medium @@ -27,27 +27,27 @@ Microsoft Calling Plans, Direct Routing, and Operator Connect all support blocki This inbound call blocking feature only works on inbound calls that originate from the PSTN and only works on a tenant global level. Individual Teams users can't manipulate this list. The Teams client does allow individual users to block PSTN calls. For information about how your end users can implement call blocking, see [Manage call settings in Teams](https://support.microsoft.com/office/456cb611-3477-496f-b31a-6ab752a7595f). > [!NOTE] -> Blocked callers may experience slightly different behaviors when they've been blocked. The behavior is based on how the blocked caller's carrier handles the notification that the call isn't allowed to be successfully completed. Examples may include a carrier message stating the call can't be completed as dialed, or simply dropping the call. +> Blocked callers might experience slightly different behaviors when they've been blocked. The behavior is based on how the blocked caller's carrier handles the notification that the call isn't allowed to be successfully completed. Examples might include a carrier message stating the call can't be completed as dialed, or simply dropping the call. -Note that it's currently not possible to manage call blocking by using Teams admin center. +It's currently not possible to manage call blocking by using Teams admin center. ## Manage call blocking by using PowerShell To manage call blocking, you need to define one or more number patterns to block calls from, define exceptions to the number patterns, and enable the call blocking feature. -Number block patterns are defined as regular expression patterns. The order of the expressions is unimportant--the first pattern matched in the list results in the call being blocked. A new number or pattern that's added or removed in the blocked callers list may take up to 24 hours for the pattern to become active. +Number block patterns are defined as regular expression patterns. The order of the expressions is unimportant--the first pattern matched in the list results in the call being blocked. A new number or pattern that's added or removed in the blocked callers list can take up to 24 hours for the pattern to become active. ### Activate the call blocking feature To view and activate the call blocking feature, use the **Get-** and **Set-CsTenantBlockingCallingNumbers** Teams PowerShell Module cmdlets. -- [Get-CsTenantBlockedCallingNumbers](/powershell/module/teams/get-cstenantblockedcallingnumbers) returns the inbound block number patterns and the inbound exempt number patterns parameters for the global blocked number list. This cmdlet also returns whether blocking has been Enabled (True or False). +- [Get-CsTenantBlockedCallingNumbers](/powershell/module/teams/get-cstenantblockedcallingnumbers) returns the inbound block number patterns and the inbound exempt number patterns parameters for the global blocked number list. This cmdlet also returns whether or not blocking is Enabled (True or False). - [Set-CsTenantBlockedCallingNumbers](/powershell/module/teams/set-cstenantblockedcallingnumbers) allows you to specify whether the global tenant blocked calls are turned on or off at the tenant level. ### Manage block number patterns -You manage number patterns by using the **New-**, **Get-**, **Set-**, **Test-**, and **Remove-CsInboundBlockedNumberPattern** Teams PowerShell Module cmdlets. +You manage number patterns by using the **New-**, **Get-**, **Set-**, **Test-**, and **Remove-CsInboundBlockedNumberPattern** Teams PowerShell Module cmdlets. - [Get-CsInboundBlockedNumberPattern](/powershell/module/teams/get-csinboundblockednumberpattern) returns a list of all blocked number patterns added to the tenant list including Name, Description, Enabled (True/False), and Pattern. @@ -68,7 +68,7 @@ tests whether calls from a given phone number will be blocked. #### Block a number -In the following example, the tenant administrator wants to block all calls coming from the number range 1 (312) 555-0000 to 1 (312) 555-9999. The number pattern is created so that both numbers in range with + prefixed and numbers in the range without + prefixed are matched. You don't need to include the symbols – and () in the phone numbers because the system strips these symbols before matching. To turn on the number pattern, set the **Enabled** parameter to True. To disable this specific number pattern, set the parameter to False. +In the following example, the tenant administrator wants to block all calls coming from the number range 1 (312) 555-0000 to 1 (312) 555-9999. The number pattern is created so that both numbers in range with + prefixed and numbers in the range without + prefixed are matched. You don't need to include the symbols – and () in the phone numbers because the system strips these symbols before matching. To turn on the number pattern, set the **Enabled** parameter to True. To disable this specific number pattern, set the parameter to False. ```PowerShell New-CsInboundBlockedNumberPattern -Name "BlockRange1" -Enabled $True -Description "Block Contoso" -Pattern "^\+?1312555\d{4}$" @@ -184,7 +184,7 @@ Set-CsInboundExemptNumberPattern -Identity "AllowContoso1" -Enabled $False #### Remove a number exception -The **Remove-CsInboundExemptNumberPattern** cmdlet will remove the given number pattern from the tenant list. In this example, the **Identity** parameter is required. +The **Remove-CsInboundExemptNumberPattern** cmdlet removes the given number pattern from the tenant list. In this example, the **Identity** parameter is required. If the identity isn't known, use the **Get-CsInboundExemptNumberPattern** cmdlet to first locate the proper pattern and note the identity. Then, run the **Remove-CsInboundExemptNumberPattern** cmdlet and pass the appropriate identity value. Allow time for replication before you test and validate. @@ -200,10 +200,10 @@ Remove-CsInboundExemptNumberPattern -Identity "AllowContoso1" The pattern matching for blocking callers is done by using Regex. Multiple tools are available online to help validate a Regex pattern match. If you aren't familiar with Regex patterns, we recommend that you take some time to familiarize yourself with the basics. To make sure you get expected results, use a tool for validating pattern matches before you add new blocked number matches to your tenant. -## Related topics +## Related articles [Set-CsTenantBlockedCallingNumbers](/powershell/module/teams/set-cstenantblockedcallingnumbers) [Set-CsInboundBlockedNumberPattern](/powershell/module/teams/set-csinboundblockednumberpattern) -[Manage call settings in Teams](https://support.microsoft.com/office/manage-your-call-settings-in-teams-456cb611-3477-496f-b31a-6ab752a7595f) +[Manage call settings in Teams](https://support.microsoft.com/office/456cb611-3477-496f-b31a-6ab752a7595f) diff --git a/Teams/call-park-and-retrieve.md b/Teams/call-park-and-retrieve.md index 0b36b1a4c6..8f22a30ef5 100644 --- a/Teams/call-park-and-retrieve.md +++ b/Teams/call-park-and-retrieve.md @@ -1,7 +1,7 @@ --- title: "Call park and retrieve in Microsoft Teams" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 12/14/2023 diff --git a/Teams/call-sharing-and-group-call-pickup.md b/Teams/call-sharing-and-group-call-pickup.md index cbabcfa1ce..e5dc8f8321 100644 --- a/Teams/call-sharing-and-group-call-pickup.md +++ b/Teams/call-sharing-and-group-call-pickup.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.date: 12/12/2023 -ms.reviewer: jenstr +ms.reviewer: jastark ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -42,9 +42,12 @@ Users must be assigned a Microsoft Teams Phone license to set up and use call sh ## Limitations -A user can only be the owner of one call group. Each configured call group can have a maximum of 25 users or 32,768 characters. A user can be a member of maximum 25 call groups. +- A user can only own one call group. +- Each call group can have up to 25 users. +- A user can be a member of up to 25 call groups. +- If you add more than five members to a call group, the ring order automatically switches to "Everyone at once." -Note that mobile devices will only get notified if they're set for banner and ringtone. +Mobile devices are only notified if they're set for banner and ringtone. ## Enable the use of group call pickup @@ -69,7 +72,7 @@ To configure immediate call forward settings: 1. Select **Manage call group** and select **Add people** to add the appropriate users to the call group. -1. For each user in the call group, select the type of notification that the user will see when they get an incoming call. **Ring** is the default notification type. +1. For each user in the call group, select the type of notification that you want the user to see when they get an incoming call. **Ring** is the default notification type. 1. From the dropdown, select the appropriate call group order. diff --git a/Teams/caller-id-policies.md b/Teams/caller-id-policies.md index eb11bacfb7..c0965ff36d 100644 --- a/Teams/caller-id-policies.md +++ b/Teams/caller-id-policies.md @@ -1,7 +1,7 @@ --- title: Manage caller ID for users -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: roykuntz ms.date: 03/26/2024 @@ -136,7 +136,7 @@ For more information on each policy, see [configure caller ID policies](#configu - **Resource account:** Set a resource account associated with an Auto Attendant or Call Queue. - If you choose **Resource account**, you're prompted to specify a resource account for the next field, called **Replace the caller ID with this resource account**. Only resource accounts with an assigned phone number will be displayed. If you just assigned a phone number to the resource account, it might take a few minutes before the resource account is available for selection. + If you choose **Resource account**, you're prompted to specify a resource account for the next field, called **Replace the caller ID with this resource account**. Only resource accounts with an assigned phone number will be displayed. If you just assigned a phone number to the resource account, it might take a few minutes before the resource account is available for selection. 7. Select **Save**. diff --git a/Teams/calling-plan-overview.md b/Teams/calling-plan-overview.md index 930e6ed32b..b907ad8db2 100644 --- a/Teams/calling-plan-overview.md +++ b/Teams/calling-plan-overview.md @@ -1,7 +1,7 @@ --- title: "Country/region availability - Audio Conferencing, Calling Plans" -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: mikedav, jastark, oscarr ms.date: 11/29/2017 diff --git a/Teams/calling-plans-for-office-365.md b/Teams/calling-plans-for-office-365.md index 5805fcdab2..071c65a641 100644 --- a/Teams/calling-plans-for-office-365.md +++ b/Teams/calling-plans-for-office-365.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams Calling Plans -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 08/05/2024 diff --git a/Teams/change-the-default-language-for-greetings-and-emails.md b/Teams/change-the-default-language-for-greetings-and-emails.md index dbd01faa32..bcc0013229 100644 --- a/Teams/change-the-default-language-for-greetings-and-emails.md +++ b/Teams/change-the-default-language-for-greetings-and-emails.md @@ -1,7 +1,7 @@ --- title: "Change the default language for greetings and emails" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 11/28/2017 diff --git a/Teams/change-the-settings-for-an-audio-conferencing-bridge.md b/Teams/change-the-settings-for-an-audio-conferencing-bridge.md index e2735b10d4..1b9ce01b4f 100644 --- a/Teams/change-the-settings-for-an-audio-conferencing-bridge.md +++ b/Teams/change-the-settings-for-an-audio-conferencing-bridge.md @@ -4,7 +4,7 @@ ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/13/2023 +ms.date: 11/1/2024 ms.topic: article ms.assetid: 783fad3f-b77c-422b-b91f-7c8b0af324fb ms.tgt.pltfrm: cloud @@ -36,7 +36,7 @@ When you set up Audio Conferencing in Microsoft 365 or Office 365, you get phone When a user dials in to a meeting using a phone, the conferencing bridge answers the call with voice prompts from the meeting auto attendant. Depending on your settings, the conferencing bridge can also play notifications, ask callers to record their name, and control the PIN settings. A PIN is assigned to meeting organizers to allow them to start their meetings if they can't use the Microsoft Teams app. > [!IMPORTANT] - > A PIN is only required for the meeting organizer when a Teams app user hasn't already started the meeting. If everyone is dialing in to the meeting, the PIN is required for the meeting organizer to start the meeting. + > The meeting organizer only needs a PIN when a Teams app user hasn't already started the meeting. If everyone is dialing in to the meeting, the PIN is required for the meeting organizer to start the meeting. > [!NOTE] > [!INCLUDE [updating-admin-interfaces](includes/updating-admin-interfaces.md)] @@ -50,7 +50,7 @@ When a user dials in to a meeting using a phone, the conferencing bridge answers 3. In the **Bridge settings** pane, select: - **Meeting entry and exit notifications**- If you turn off this setting, users in the meeting aren't notified when someone enters or leaves the meeting. - When you turn on **Meeting entry and exit notifications**, you can select one of these options: + - When you turn on **Meeting entry and exit notifications**, you can select one of these options: - **Names or phone numbers**- When users join a meeting by dialing in, their phone number is played. - Toggle **Ask callers to record their name before joining the meeting** **On** or **Off**. If you turn this off, callers aren't asked to record their name before they join a meeting. @@ -59,7 +59,7 @@ When a user dials in to a meeting using a phone, the conferencing bridge answers 4. To set the PIN length for meetings, select the number of digits you want for the PIN in the **PIN length** list. -5. To control whether to send email to your users when their settings are changed, toggle **Automatically send emails to users if their audio conferencing configuration changes** **On** or **Off**. +5. To control whether to send an email to your users when their settings are changed, toggle **Automatically send emails to users if their audio conferencing configuration changes** **On** or **Off**. For more information, see [Emails automatically sent to users when their Audio Conferencing settings change in Microsoft Teams](emails-sent-to-users-when-their-settings-change-in-teams.md). 6. Select **Save**. @@ -69,16 +69,20 @@ When a user dials in to a meeting using a phone, the conferencing bridge answers ## Manage audio conferencing bridges with PowerShell -To manage audio conferencing bridges with PowerShell, use the **`-CsOnlineDialInConferencingBridge`** cmdlet. +To manage audio conferencing bridges with PowerShell, use the following parameters, within the PowerShell [Set-CsOnlineDialInConferencingTenantSettings](/powershell/module/teams/set-csonlinedialinconferencingtenantsettings) cmdlet: -For **`-CsOnlineDialInConferencingBridge`** script examples, see [Set-CsOnlineDialInConferencingBridge](/powershell/module/teams/Set-CsOnlineDialInConferencingBridge). - -To manage entry and exit announcements through PowerShell, see [Set-CsOnlineDialInConferencingBridge](/powershell/module/teams/Set-csonlinedialinconferencingtenantsettings). +- **`-EnableNameRecording`** +- **`-EntryExitAnnouncementsType`** +- **`-EnableNameRecording`** +- **`-PinLength`** ## Related articles - [Set up Audio Conferencing for Microsoft Teams](set-up-audio-conferencing-in-teams.md) +- [Allow users to record their name when they join a meeting in Microsoft Teams](enable-users-to-record-their-name-when-they-join-a-meeting-in-teams.md) +- [Turn on or off entry and exit announcements for meetings in Teams](turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md) - [Why you need to use Office 365 PowerShell](/microsoft-365/enterprise/why-you-need-to-use-microsoft-365-powershell) - [Best ways to manage Microsoft 365 or Office 365 with Windows PowerShell](/previous-versions//dn568025(v=technet.10)) - [Microsoft Teams PowerShell Overview](teams-powershell-overview.md) - [Install Microsoft Teams PowerShell Module](teams-powershell-install.md) + diff --git a/Teams/client-firewall-script.md b/Teams/client-firewall-script.md index e87dd85997..1905872db5 100644 --- a/Teams/client-firewall-script.md +++ b/Teams/client-firewall-script.md @@ -21,6 +21,9 @@ appliesto: # Sample script - classic Microsoft Teams firewall PowerShell script +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + This sample script, which needs to run on client computers in the context of an elevated administrator account, will create a new inbound firewall rule for each user folder found in c:\users. When Teams finds this rule, it will prevent the Teams application from prompting users to create firewall rules when the users make their first call from Teams. ```powershell diff --git a/Teams/cloud-voice-landing-page.md b/Teams/cloud-voice-landing-page.md index 886eafda97..86416fbbfb 100644 --- a/Teams/cloud-voice-landing-page.md +++ b/Teams/cloud-voice-landing-page.md @@ -1,7 +1,7 @@ --- title: Plan your voice solution in Microsoft Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 08/03/2023 ms.topic: article @@ -15,7 +15,7 @@ ms.collection: - m365solution-scenario - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis f1.keywords: - CSH ms.custom: @@ -98,7 +98,7 @@ This article introduces the following Teams Phone key features and functionality - [Cloud Voicemail](#cloud-voicemail) - [Calling identity](#calling-identity) -![Diagram 3 shows Teams Phone contains Auto attendants and call queries, Cloud voicemail, and Calling identity.](media/phone-system-contains.png) + ![Diagram 3 shows Teams Phone contains Auto attendants and call queries, Cloud voicemail, and Calling identity.](media/phone-system-contains.png) For information about all Teams Phone features, and how to set up Teams Phone, see the following articles: diff --git a/Teams/cloud-voice-network-settings.md b/Teams/cloud-voice-network-settings.md index 8edbf68310..7433587fca 100644 --- a/Teams/cloud-voice-network-settings.md +++ b/Teams/cloud-voice-network-settings.md @@ -1,11 +1,11 @@ --- title: Network settings for cloud voice features -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.reviewer: roykuntz -ms.date: 12/08/2023 +ms.date: 10/10/2024 ms.service: msteams audience: admin search.appverid: MET150 @@ -25,9 +25,11 @@ ms.custom: seo-marvel-mar2020 # Network settings for cloud voice features in Microsoft Teams -Learn about network regions, network sites, network subnets, and trusted IP addresses. These terms and concepts are used throughout our cloud voice documentation for [Location-Based Routing for Direct Routing](location-based-routing-plan.md) and [dynamic emergency calling](configure-dynamic-emergency-calling.md). If you're deploying these cloud features in your organization, you must configure network settings for use with these features in Microsoft Teams. +Learn about network regions, network sites, network subnets, and trusted IP addresses. -This article gives you an overview of the network settings that are common to Location-Based Routing and dynamic emergency calling. Depending on the cloud voice feature and capability that you're deploying, you configure some or all these settings. For steps on how to configure these settings, see [Manage your network topology for cloud features in Teams](manage-your-network-topology.md). +These terms and concepts are used throughout our cloud voice documentation for [Location-Based Routing for Direct Routing](location-based-routing-plan.md) and [dynamic emergency calling](configure-dynamic-emergency-calling.md). If you're deploying these cloud voice features in your organization, you must configure network settings for use with these features in Microsoft Teams. + +This article gives you an overview of the network settings that are common to Location-Based Routing and dynamic emergency calling. Depending on the cloud voice feature and capability that you're deploying, you configure some or all of these settings. For steps on how to configure these settings, see [Manage your network topology for cloud features in Teams](manage-your-network-topology.md). Note that it can take some time (up to four hours) for some changes to network settings (such as a new address, network identifier, and so on) to propagate and be available to Teams clients. @@ -44,7 +46,6 @@ The same network regions are shared by Location-Based Routing for Direct Routing A network site represents a location where your organization has a physical venue, such as an office, a set of buildings, or a campus. Network sites are defined as a collection of IP subnets. Each network site must be associated with a network region. -You can also use network sites to enable and configure emergency calling. ## Network subnet @@ -52,13 +53,14 @@ Each subnet must be associated with a specific network site. A client's location Subnet information is used to determine the network site on which an endpoint is located when a new session is initiated. When the location of each party in a session is known, the cloud voice feature can apply that information to determine how to handle call setup or routing. -For each network site, work with your network admin to determine which IP subnets are assigned to each network site. For example, the New York site in the North America region can be assigned the following IP subnets: 172.29.80.0/23, 157.57.216.0/25, 172.29.91.0/23, 172.29.81.0/24. If Bob, who usually works in Detroit, travels to the New York office for training, turns on his computer and connects to the network, his computer gets an IP address in one of the four ranges that are allocated for New York, for example, 172.29.80.103. +For each network site, you should work with your network administrator to determine which IP subnets are assigned to which network site. For example, assume the New York site in the North America region is assigned the following IP subnets: 172.29.80.0/23, 157.57.216.0/25, 172.29.91.0/23, 172.29.81.0/24. Assume Bob, who usually works in Detroit, travels to the New York office for training. When he turns on his computer and connects to the network, his computer gets an IP address in one of the four ranges that are allocated for New York; for example, 172.29.80.103. ## Trusted IP address Trusted IP addresses are the internet external IP addresses of the enterprise network. They determine whether the user's endpoint is inside the corporate network before checking for a specific site match. -If the user's external IP address matches an IP address that's in the trusted IP address list, the cloud voice feature checks to determine the internal subnet where the user's endpoint is located. A match can be made against either IPv4 or IPv6 IP addresses and is dependent upon the format of the IP packet sent to the network settings. (If a public IP address has both IPv4 and IPv6, you must add both as trusted IP addresses.) +If the user's external IP address matches an IP address that's in the trusted IP address list, the cloud voice feature checks to determine the internal subnet where the user's endpoint is located. A match can be made against either IPv4 or IPv6 IP addresses and is dependent upon the format of the IP packet sent to the network settings. (If the enterprise network +has both IPv4 and IPv6 internet accessible external IP addresses, you must add both as trusted IP addresses.) If the user's external IP address doesn't match an IP address that's in the trusted IP address list, the endpoint is classified as being at an unknown location. diff --git a/Teams/configure-dynamic-emergency-calling.md b/Teams/configure-dynamic-emergency-calling.md index 766fbf7c76..005a5e7df5 100644 --- a/Teams/configure-dynamic-emergency-calling.md +++ b/Teams/configure-dynamic-emergency-calling.md @@ -1,7 +1,7 @@ --- title: Configure dynamic emergency calling -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: article ms.service: msteams diff --git a/Teams/configure-lobby-sensitive-meetings.md b/Teams/configure-lobby-sensitive-meetings.md index 70e0353ffd..af4d00922b 100644 --- a/Teams/configure-lobby-sensitive-meetings.md +++ b/Teams/configure-lobby-sensitive-meetings.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 12/11/2023 +ms.reviewer: vivek.mohan +ms.date: 11/12/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,47 +25,61 @@ description: Learn how to configure the Teams meeting lobby to enhance security [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The meeting lobby is a tool that you can use to help ensure that inappropriate people aren't admitted to meetings. By holding different types of participants in the lobby, meeting organizers can vet them and make sure it's appropriate for them to attend the meeting. +The meeting lobby is a tool that you can use to help ensure that inappropriate people aren't admitted to meetings. Holding different types of participants in the lobby allows meeting organizers to make sure it's appropriate for them to attend the meeting. -By default, people in your organization and [guests](guest-access.md) are admitted to meetings directly and participants from [trusted organizations](/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#specify-trusted-microsoft-365-organizations) and [anonymous participants](anonymous-users-in-meetings.md) must wait in the lobby to be admitted by a meeting organizer. Meeting organizers can change this default setting for each meeting they create. +By default, people in your organization and [guests](guest-access.md) are admitted to meetings directly. Participants from [trusted organizations](/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#specify-trusted-microsoft-365-organizations) and [anonymous participants](anonymous-users-in-meetings.md) must wait in the lobby until a meeting organizer admits them. Meeting organizers can change this default setting for each meeting they create. -The lobby and other related settings can be controlled by the Teams Administrator by using meeting policies, meeting templates, and sensitivity labels to customize the experience for different users and different types of meetings. + Meeting policies in the Teams admin center, meeting templates, and sensitivity labels to customize the lobby experience for different users and different types of meetings. The following table lists features that you can use to help manage the lobby experience for your organization and where to configure them. |Setting|Admin policy|Sensitivity label|Template|Meeting organizer| |:------|:----------:|:---------------:|:------:|:---------------:| -|Announce when dial-in callers join or leave|No|No|Yes|Yes| -|Anonymous users and dial-in callers can start a meeting|Yes|No|No|No| -|Anonymous users can join a meeting|Yes|No|No|No| -|People dialing in can bypass the lobby|Yes|Yes|Yes|Yes| -|Who can bypass the lobby|Yes|Yes|Yes|Yes| +|[Announce when dial-in callers join or leave](custom-meeting-templates-overview.md)|No|No|Yes|Yes| +|[Anonymous users and dial-in callers can start a meeting](who-can-bypass-meeting-lobby.md)|Yes|No|No|No| +|[Anonymous users can join a meeting](who-can-bypass-meeting-lobby.md)|Yes|No|No|No| +|[People dialing in can bypass the lobby](who-can-bypass-meeting-lobby.md)|Yes|Yes|Yes|Yes| +|[Who can admit from lobby](who-can-bypass-meeting-lobby.md)|Yes|No|No|Yes| +|[Who can bypass the lobby](who-can-bypass-meeting-lobby.md)|Yes|Yes|Yes|Yes| For information about how to use templates and sensitivity labels to configure meeting settings, see [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) and [Use sensitivity labels to protect calendar items, Teams meetings, and chat](/microsoft-365/compliance/sensitivity-labels-meetings). -> [!Note] +> [!NOTE] > Meeting settings in sensitivity labels and custom meeting templates require Teams Premium. ## Lobby settings for different types of meetings +### Who can admit from lobby + +The following settings are available for **Who can admit from lobby**: + +- Organizers, co-organizers, and presenters +- Organizers and co-organizers + +To manage who can bring participants from the lobby into the meeting or webinar, you should consider using this per-organizer policy for sensitive meetings. When set to the default value of **Organizers, co-organizers, and presenters**, only organizers, co-organizers, and presenters can admit participants into the meeting from the lobby. This policy sets a default that your organizers can change through their **Meeting options**. + +### Who can bypass the lobby + The following settings are available for **Who can bypass the lobby**: - Everyone -- People in my org, trusted orgs, and guests - People in my org and guests +- People in my org, trusted orgs, and guests - People in my org -- People who were invited - Only organizers and co-organizers +- People who were invited -An additional setting, **People dialing in can bypass the lobby**, controls if people calling in by phone can bypass the lobby. +This per-organizer policy controls who can bypass the lobby into the meeting or webinar. When set to the default value of **People in my org and guests**, only people in my org and guests can bypass lobby. This policy sets a default that your organizers can change through their **Meeting options**. + +Another setting, **People dialing in can bypass the lobby**, controls if people calling in by phone can bypass the lobby. While the meeting organizer normally chooses which setting to use for each meeting, you can enforce a particular setting using either a meeting template or a sensitivity label. -If your organization requires that certain types of meetings not be attended by people outside the organization, consider a meeting template that only allows people in your organization to bypass the lobby. This ensures that people outside the organization who were accidentally invited or sent a meeting link can't join the meeting directly. +If your organization needs to restrict certain meetings to internal participants only, you could use a meeting template that allows only people in your organization to bypass the lobby. This option ensures that people outside the organization who were accidentally invited or sent a meeting link can't join the meeting directly. -If your organization has meetings where highly sensitive information is shared and you need to be sure that only certain people attend, consider using a meeting template or sensitivity label that only allows meeting organizers to bypass the lobby. This ensures that organizers can vet each incoming participant to make sure they should be in the meeting. This also prevents the meeting from starting until an organizer joins. +For meetings with highly sensitive information, you could use a meeting template or sensitivity label that allows only meeting organizers to bypass the lobby. This option allows organizers to vet participants and ensures the meeting doesn't start until an organizer joins. -For sensitive meetings in general, consider using the **People who were invited** option. This ensures that people who don't have either a direct or forwarded meeting invite go through the lobby. (The meeting organizer can also prevent forwarding when they create the meeting.) +For sensitive meetings in general, consider using the **People who were invited** option. This option ensures that people who don't have either a direct or forwarded meeting invite go through the lobby. (The meeting organizer can also prevent forwarding when they create the meeting.) For more information about the meeting lobby, see [Control who can bypass the meeting lobby in Microsoft Teams](who-can-bypass-meeting-lobby.md). @@ -75,7 +89,7 @@ For information about using meeting templates and sensitivity labels together, s By default, attendees who are dialing in by phone go through the lobby. Administrators can change this default with the **People dialing in can bypass the lobby** admin meeting policy. If you want to enforce this setting to be on or off, you must use a meeting template or sensitivity label. -If there are circumstances where you want to allow callers to bypass the lobby, meeting organizers can control this setting, or you can enforce it through a meeting template or sensitivity label. +If you want to allow callers to bypass the lobby, meeting organizers can control this setting, or you can enforce it through a meeting template or sensitivity label. #### Join and leave notifications @@ -85,10 +99,10 @@ Meeting organizers have the option of having attendees calling in by phone annou Unless you allow everyone to bypass the lobby, anonymous participants must go through the lobby to attend the meeting. Meeting organizers can then decide if these participants should be admitted. -If your organization doesn't allow anonymous participants to join meetings at all, you can turn off the **Anonymous users can join a meeting** policy in the Teams admin center. If you have certain groups in your organization - such as marketing - who need to organize meetings with anonymous participants and others - such as research - who shouldn't, you can use Teams meeting policies to configure anonymous meeting join for different groups. For more information, see [Manage anonymous participant access to Teams meetings, webinars, and town halls](anonymous-users-in-meetings.md). +If your organization doesn't allow anonymous participants in meetings, turn off the **Anonymous users can join a meeting** policy in the Teams admin center. For groups like marketing that need anonymous participants to join meetings, and others like research that don't, use Teams meeting policies to configure anonymous meeting join for different groups. For more information, see [Manage anonymous participant access to Teams meetings, webinars, and town halls](anonymous-users-in-meetings.md). ## Related topics -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - -[Manage external meetings and chat in Microsoft Teams](/microsoftteams/manage-external-access) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Manage external meetings and chat in Microsoft Teams](/microsoftteams/manage-external-access) +- [Who can admit from lobby](https://support.microsoft.com/office/using-the-lobby-in-microsoft-teams-meetings-eaf70322-d771-4043-b595-b40794bac057) diff --git a/Teams/configure-meetings-baseline-protection.md b/Teams/configure-meetings-baseline-protection.md index 53f7db211c..bcf473d489 100644 --- a/Teams/configure-meetings-baseline-protection.md +++ b/Teams/configure-meetings-baseline-protection.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 12/11/2023 +ms.reviewer: vivek.mohan +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,9 +25,9 @@ description: Learn how to configure Teams meetings for a baseline level of prote [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -For the *baseline* level of protection, we restrict who can bypass the lobby by using a sensitivity label and set a default value for who can present with a Teams admin policy. You can restrict additional actions as well if your organization requires it. +For the *baseline* level of protection, we restrict **Who can bypass the lobby** by using a sensitivity label and set a default value for **Who can present** with a Teams admin policy. You can restrict other actions as well if your organization requires it. -> [!Note] +> [!NOTE] > Meeting options in sensitivity labels and custom meeting templates require Teams Premium. The following table describes which actions we restrict for baseline meetings and where those options are configured. @@ -44,11 +44,12 @@ The following table describes which actions we restrict for baseline meetings an |People dialing in can bypass the lobby|**Off**|Template|Yes| |Prevent copying chat content to clipboard|**Off**|Label|Yes| |Record automatically|**Off**|Template|No| +|Require a verification check from|**Not required**|Label or Template|Yes| |Who can bypass the lobby?|**People in my org, trusted orgs, and guests**|Template|No| |Who can present|**People in my org and guests**|Teams admin center|No| |Who can record|**Organizers, co-organizers, and presenters**|Template|No| -Options that are listed as enforced are enforced by the sensitivity label or meeting template. Options that aren't enforced can be changed by the meeting organizer. +The sensitivity label or meeting template enforces options that are listed as enforced. The meeting organizer can change Options that aren't enforced. ## Default values for **Who can present** @@ -56,48 +57,39 @@ The default value for **Who can present** is **Everyone**. For the baseline prot We can set this value with a sensitivity label, but the value would be enforced for any meetings with that label. This option isn't available in meeting templates, so we set it in the Teams admin center. -To configure who can present +To configure who can present: + 1. In the Teams admin center, expand **Meetings** and select **Meeting policies**. 1. Select the policy that you want to update. 1. Under **Content sharing**, set **Who can present** to **People in my org and guests**. 1. Select **Save**. -## Watermarks and end-to-end encryption +## Default values for **Who can admit from lobby** -In the *baseline* level of protection, we disable watermarks and end-to-end encryption by using a sensitivity label. This will prevent meeting organizers from using these features. Watermarks and end-to-end encryption are more applicable to sensitive meetings. +You can choose to keep the default for **Who can admit from lobby** as **Organizers and presenters** or change it to **Organizers and co-organizers**. This per-organizer policy sets a default that your organizers can change through their **Meeting options**. You must manage this setting through the Teams admin center. Meeting templates and sensitivity labels don't support this policy. -End-to-end encryption and watermarks disable some other features such as PowerPoint Live. Turning them off for the *baseline* level of protection can avert instances where meeting organizers use these features without realizing the limits they impose. +To configure who can admit from lobby: -If you work in a highly regulated industry, you may want to keep these features available even in the *baseline* level of protection. +1. In the Teams admin center, expand **Meetings** and select **Meeting policies**. +2. Select the policy that you want to update. +3. Under **Meeting join & lobby**, for **Who can admit from lobby**, choose either **Organizers and presenters**(default value) or **Organizers and co-organizers**. +4. Select **Save** -## Sensitivity labels +## Watermarks and end-to-end encryption -For the *baseline* level of protection, we use a sensitivity label that you can use directly in a meeting or as part of a meeting template. Depending on the configuration you choose, this label can also be used to classify teams and individual files. +In the *baseline* level of protection, we turn off watermarks and end-to-end encryption by using a sensitivity label. This setting prevents meeting organizers from using these features. Watermarks and end-to-end encryption are more applicable to sensitive meetings. -If you already have sensitivity labels deployed in your organization, consider how this label fits with your overall label strategy. You can change the name or settings shown below if needed to meet the needs of your organization. If you already have a label that you use for baseline or general protection, you can edit the label and add Teams meetings to it. +End-to-end encryption and watermarks turn off some other features such as PowerPoint Live. Turning them off for the *baseline* level of protection can avert instances where meeting organizers use these features without realizing the limits they impose. -To create a sensitivity label -1. Open the [Microsoft Purview compliance portal](https://compliance.microsoft.com). -1. Under **Solutions**, expand **Information protection** and then select **Labels**. -1. Select **Create a label**. -1. Give the label a name. We suggest **Sensitive**, but you can choose a different name if that one is already in use. -1. Add a display name and description, and then select **Next**. -1. On the **Define the scope for this label** page, make sure **Items**, **Files**, **Emails**, and **Meetings** are selected. (Note that you can select other options if you want to use this label for other purposes.) -1. Select **Next**. -1. On the **Choose protection settings for labeled items** page, select **Protect Teams meetings and chats** and then select **Next** -1. On the **Settings for Teams meetings and chats** page, choose the following values: - 1. Select **Control end-to-end encryption for meeting video and audio** and set **Apply end-to-end encryption** to **Don't apply end-to-end encryption**. - 1. Select **Control watermarks** and select **Don't apply watermark to shared content** and **Don't apply watermark to everyone's video feed**. - 1. Configure any other settings that you need for your organization. +If you work in a highly regulated industry, you might want to keep these features available even in the *baseline* level of protection. - :::image type="content" alt-text="Screenshot of meeting sensitivity label settings showing configuration in this procedure." source="media/teams-meeting-sensitivity-label-baseline-small.png"::: +## Sensitivity labels -1. Select **Next**. -1. Complete the wizard with any additional settings you want to use, select **Create label**, and then select **Done**. +For the *baseline* level of protection, we use a sensitivity label that you can use directly in a meeting or as part of a meeting template. Depending on the configuration you choose, this label can also be used to classify teams and individual files. -Once you've created the label, you need to publish it to the users who will use it. For baseline protection, we make the label available to all users. You publish the label in the Microsoft Purview compliance portal, on the **Label policies** page under **Information protection**. If you have an existing policy that applies to all users, add this label to that policy. If you need to create a new policy, see [Publish sensitivity labels by creating a label policy](/purview/create-sensitivity-labels#publish-sensitivity-labels-by-creating-a-label-policy). +If you already have sensitivity labels deployed in your organization, consider how this label fits with your overall label strategy. You can change the name or settings if needed to meet the needs of your organization. If you already have a label that you use for baseline or general protection, you can edit the label and add Teams meetings to it. -For additional information about using sensitivity labels with meetings, see [Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings). +To learn how to create and manage a sensitivity label, see [Use sensitivity labels to protect calendar items, Teams meetings and chat](/purview/sensitivity-labels-meetings#how-to-configure-a-sensitivity-label-to-protect-calendar-items-teams-meetings-and-chats). ## Meeting templates @@ -105,27 +97,25 @@ In the *baseline* level of protection, we use the template to set a default valu We also prevent people dialing in by phone from bypassing the lobby. You can omit this setting if your organization frequently holds meetings where dial-in participants should be able to join directly. If there are certain types of meetings where this is true, consider using a separate template for those meetings. -If you've chosen to disable watermarks and end-to-end encryption in the sensitivity label, you can also use the template to hide those options from the meeting organizer. +If you turned off watermarks and end-to-end encryption in the sensitivity label, you can also use the template to hide those options from the meeting organizer. To create a custom meeting template 1. In the Teams admin center, expand **Meetings** and select **Meeting templates**. 1. Select **Add** 1. Type a name and description for the template. -1. In the **Apply sensitivity label** section, choose the label you created above. +1. In the **Apply sensitivity label** section, choose the label you created. 1. Select **Apply sensitivity label**, and then select **Lock**. 1. In the **Lobby** dropdown, select **People in my org, trusted orgs, and guests**. 1. Make sure **People dialing in can bypass the lobby** is set to **Off**, then select it and select **Lock**. -1. If you've disabled watermarks and end-to-end encryption with the sensitivity label, consider selecting those options here and selecting **Hide** so meeting organizers won't see them. -1. Change any additional options if desired. +1. If you turned off watermarks and end-to-end encryption with the sensitivity label, consider selecting those options here and selecting **Hide** so meeting organizers doesn't see them. +1. Change any other options if desired. 1. To prevent the meeting organizer from changing an option, select the option and then select **lock**. 1. To prevent the meeting organizer from seeing an option, select the option and then select **Hide**. 1. Select **Save**. ## Related topics -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) diff --git a/Teams/configure-meetings-highly-sensitive-protection.md b/Teams/configure-meetings-highly-sensitive-protection.md index 49994c7614..f9225222e0 100644 --- a/Teams/configure-meetings-highly-sensitive-protection.md +++ b/Teams/configure-meetings-highly-sensitive-protection.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 12/11/2023 +ms.reviewer: vivek.mohan +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,16 +25,17 @@ description: Learn how to configure Teams meetings for protection for highly sen [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -For the *highly sensitive* level of protection, we'll look at two different scenarios: -- Highly sensitive meetings where attendees participate and interact with the presenters -- Highly sensitive presentations where attendees don't interact and are just viewing the presentation +For the *highly sensitive* level of protection, let's look at two different scenarios: -> [!Note] +- Highly sensitive meetings where attendees participate and interact with the presenters. +- Highly sensitive presentations where attendees don't interact and are just viewing the presentation. + +> [!NOTE] > Meeting options in sensitivity labels and custom meeting templates require Teams Premium. -#### Highly sensitive meetings +## Highly sensitive meetings -For highly sensitive meetings, we'll restrict who can bypass the lobby, who can present, when participants can chat, and we'll block copying from the meeting chat. We'll also enable end-to-end encryption and watermarking for shared video and content. +For highly sensitive meetings, we restrict **Who can bypass the lobby,** **Who can present**, when participants can chat, and we'll block copying from the meeting chat. We'll also enable end-to-end encryption and watermarking for shared video and content. The following table describes which actions we'll restrict for highly sensitive meetings and where those options are configured. @@ -56,7 +57,7 @@ The following table describes which actions we'll restrict for highly sensitive Options that are listed as enforced are enforced by the sensitivity label or meeting template. Options that are not enforced can be changed by the meeting organizer. -#### Highly sensitive presentations +## Highly sensitive presentations For highly sensitive presentations - where we don't expect interaction with the meeting attendees - we'll turn off attendees' mics and cameras, and turn off the meeting chat. @@ -76,6 +77,7 @@ The following table describes which actions we'll restrict for highly sensitive |People dialing in can bypass the lobby|**Off**|Label|Yes| |Prevent copying chat content to clipboard|**On**|Label|Yes| |Record meetings automatically|**Off**|Template|Yes| +|Require a verification check from|**Anonymous users and people from untrusted organizations**|Label or Template|Yes| |Who can bypass the lobby?|**Only organizers and co-organizers**|Label|Yes| |Who can present|**Only organizers and co-organizers**|Label|Yes| |Who can record|**Only organizers and co-organizers**|Template|No| @@ -101,6 +103,17 @@ By setting **Who can present** to **Only organizers and co-organizers** in the s We use the sensitivity label to prevent anyone other than meeting organizers from bypassing the lobby. This allows organizers to vet each attendee and ensure that they should be admitted. +## Who can admit from lobby + +You can choose to keep the default for **Who can admit from lobby** as **Organizers and presenters** or change it to **Organizers and co-organizers**. This per-organizer policy sets a default that your organizers can change through their **Meeting options**. You must manage this setting through the Teams admin center. Meeting templates and sensitivity labels don't support this policy. + +To configure who can admit from lobby: + +1. In the Teams admin center, expand **Meetings** and select **Meeting policies**. +2. Select the policy that you want to update. +3. Under **Meeting join & lobby**, for **Who can admit from lobby**, choose either **Organizers and presenters**(default value) or **Organizers and co-organizers**. +4. Select **Save** + ## Participation options for highly sensitive meetings While chat can be controlled with the sensitivity label, we use templates in this case so that the meeting and presentation templates can share the same label. We restrict chat to in-meeting only for meetings and turn it off completely for presentations. (Organizers can use the Q&A feature in presentations to allow audience comments or questions.) @@ -118,7 +131,8 @@ If you already have sensitivity labels deployed in your organization, consider h > [!IMPORTANT] > If a sensitivity label that restricts copying from the chat is specified as the default channel label in a container label, then teams with that container label will restrict copying from the chat for all channels in the team, both in and out of channel meetings. -To create a sensitivity label +To create a sensitivity label: + 1. Open the [Microsoft Purview compliance portal](https://compliance.microsoft.com). 1. Under **Solutions**, expand **Information protection**, and then select **Labels**. 1. Select **Create a label**. @@ -156,7 +170,7 @@ In the *highly sensitive* level of protection, we're configuring the following o Since these options differ between meetings and presentations, we'll create one template for meetings and another for presentations. Both templates can use the sensitivity label that we create above. -#### Highly sensitive meetings template +### Highly sensitive meetings template To create a meeting template for highly sensitive meetings @@ -174,7 +188,7 @@ To create a meeting template for highly sensitive meetings 1. To prevent the meeting organizer from seeing an option, select the option and then select **Hide**. 1. Select **Save**. -#### Highly sensitive presentations template +### Highly sensitive presentations template To create a meeting template for highly sensitive presentations @@ -196,10 +210,7 @@ To create a meeting template for highly sensitive presentations ## Related topics -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) - -[Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) +- [Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) diff --git a/Teams/configure-meetings-sensitive-protection.md b/Teams/configure-meetings-sensitive-protection.md index c8ad7d784f..5f28b6f394 100644 --- a/Teams/configure-meetings-sensitive-protection.md +++ b/Teams/configure-meetings-sensitive-protection.md @@ -41,6 +41,7 @@ The following table describes which actions we'll restrict for sensitive meeting |People dialing in can bypass the lobby|**Off**|Label|Yes| |Prevent copying chat content to clipboard|**Off**|Label|No| |Record automatically|**Off**|Template|No| +|Require a verification check from|**Anonymous users**|Label or Template|Yes| |Who can bypass the lobby?|**People who were invited**|Label|Yes| |Who can present|**People in my org and guests**|Label|Yes| |Who can record|**Organizer and co-organizers**|Label|Yes| diff --git a/Teams/configure-meetings-three-tiers-protection.md b/Teams/configure-meetings-three-tiers-protection.md index f38bc20cfe..a038dd4497 100644 --- a/Teams/configure-meetings-three-tiers-protection.md +++ b/Teams/configure-meetings-three-tiers-protection.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: solution-overview ms.service: msteams ms.reviewer: -ms.date: 12/11/2023 +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -26,14 +26,14 @@ description: Learn how to configure Teams meetings for better security using thr [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The articles in this series provide options for using the compliance features available in Teams and Microsoft 365 to create a meeting environment that meets your compliance requirements. We'll look at the options available with sensitivity labels and templates and how you can use them together with other Teams admin settings. +The articles in this series offer various options for you, as an admin, to utilize the compliance features in Teams and Microsoft 365. These options allow ensure that your organization's meeting environment aligns with your compliance requirements. These articles explore the available options with sensitivity labels and templates, and how you can use them together with other Teams admin settings. -> [!Note] -> Meeting sensitivity labels and custom meeting templates require Teams Premium. +> [!NOTE] +> Meeting sensitivity labels and custom meeting templates require a Teams Premium license. -This article defines four different configurations, starting with a baseline configuration for meetings that don't have specific compliance requirements. Each additional configuration represents a meaningful step up in protection as meeting options become more restricted. The configurations in this article provide examples of how to configure protection for meetings with different levels of sensitivity. Use these examples to understand what's possible and modify the specific settings as needed for your organization. +This article defines four different configurations, starting with a baseline configuration for meetings that don't have specific compliance requirements. Each extra configuration represents up a meaningful step in protection as meeting options become more restricted. The configurations in this article provide examples of how to configure protection for meetings with different levels of sensitivity. Use these examples to understand what's possible and modify the specific settings as needed for your organization. -We'll discuss these three configurations: +There are three configurations: - Baseline protection @@ -41,11 +41,11 @@ We'll discuss these three configurations: - Highly sensitive protection -Additionally, we'll discuss a variation of the highly sensitive configuration that is designed for presentations that have minimal interaction from attendees. +This series also provides a variation of the highly sensitive configuration that is designed for presentations that have minimal interaction from attendees. ## Three tiers at a glance -The following table summarizes the configurations for each tier. Use these configurations as starting point recommendations and adjust the configurations to meet the needs of your organization. Depending on your compliance needs, you may not need every tier. +The following table summarizes the configurations for each tier. Use these configurations as starting point recommendations and adjust the configurations to meet the needs of your organization. Depending on your compliance needs, you might not need every tier. | |Baseline|Sensitive|Highly sensitive|Highly sensitive presentation| |:-----|:-----|:-----|:-----|:-----| @@ -59,6 +59,7 @@ The following table summarizes the configurations for each tier. Use these confi |People dialing in can bypass the lobby|**Off**|**Off**|**Off**|**Off**| |Prevent copying chat content to clipboard|**Off**|**Off**|**On**|**On**| |Record meetings automatically|**Off**|**Off**|**Off**|**Off**| +|Require a verification check from|**Not required**|**Anonymous users**|**Anonymous users and people from untrusted organizations**|**Anonymous users and people from untrusted organizations**| |Who can bypass the lobby?|**People in my org, trusted orgs, and guests**|**People who were invited**|**Only organizers and co-organizers**|**Only organizers and co-organizers**| |Who can present|**People in my org and guests**|**People in my org and guests**|**Only organizers and co-organizers**|**Only organizers and co-organizers**| |Who can record|**Organizers, co-organizers, and presenters**|**Organizers and co-organizers**|Disabled due to watermarking|Disabled due to watermarking| @@ -73,7 +74,7 @@ Details on how to configure each tier are covered in: Both meeting templates and sensitivity labels have the ability to enforce certain meeting options. Most options can be enforced as either on or off or can be left unconfigured so the meeting organizer can set them. -> [!Important] +> [!IMPORTANT] > Some features are [controlled by admin policies](meeting-templates-sensitivity-labels-policies.md#policies-labels-templates-and-meetings-settings) and must be enabled there before they can be controlled by meeting templates and sensitivity labels. Some options are only available in sensitivity labels and some are only available in templates. The following are available in both: @@ -84,33 +85,37 @@ Some options are only available in sensitivity labels and some are only availabl - Meeting recording - Prevent copying chat content to clipboard - Watermarking +- Require a verification check from Sensitivity labels and templates can be used together to help you meet your compliance needs. For more information, see [Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md). ## Meeting chat -Meeting chat can be an important part of collaboration during a meeting. However, you may want to restrict meeting chat in certain types of meetings to avoid sensitive information being shared there. +Meeting chat can be an important part of collaboration during a meeting. However, you might want to restrict meeting chat in certain types of meetings to avoid sensitive information being shared there. As an admin, you can control meeting chat in the following ways: -- **Teams admin meeting policy** (per user or group) can be used to allow chat, allow chat for everyone except anonymous participants, or turn chat off. Can also be used to prevent copying chat content to the clipboard. -- **Sensitivity label meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard These options can be left unconfigured to be controlled by a template or the meeting organizer. -- **Meeting template meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured to be controlled by the meeting organizer. +- **Teams admin meeting policy** (per user or group) can be used to allow chat, allow chat for everyone except anonymous participants, or turn off chat. Can also be used to prevent copying chat content to the clipboard. +- **Sensitivity label meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured for a meeting organizer or template to control. +- **Meeting template meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured for a meeting organizer or template to control. For the three tiers of protection, we allow chat for baseline and sensitive meetings and restrict it in highly sensitive meetings to in-meeting only. We also prevent copying chat content to the clipboard in sensitive and highly sensitive meetings. For more information, see [Manage chat for sensitive Teams meetings](manage-chat-sensitive-meetings.md). -## Meeting recordings +## Meeting recordings and transcripts -As an admin, you can control meeting recordings in the following ways: +As an admin, you can control meeting recordings and transcripts in the following ways: - The **Meeting recording** admin meeting policy (per user or group) +- The **Transcription** admin meeting policy (per user or group) - The **Recordings automatically expire** (recording deletion) admin meeting policy (per user or group) - The **Who can record** option in sensitivity labels and meeting templates (per meeting) - The **Record automatically** option in sensitivity labels and meeting templates (per meeting) -If your organization or certain people or groups within it should never be able to record meetings, you can turn off the feature by using the **Meeting recording** admin meeting policy. +If your organization or certain people or groups within it should never be able to record meetings, you can turn off the feature by using the [**Meeting recording**](meeting-recording.md#allow-or-prevent-users-from-recording-meetings) admin meeting policy. + +If your organization or certain people or groups within it should never be able to transcribe meetings, you can turn off the feature by using the [**Transcription**](meeting-transcription-captions.md#transcription) admin meeting policy. If there are certain types of meetings that must always be recorded, you can enforce the **Record automatically** option using either a meeting template or a sensitivity label. @@ -130,35 +135,37 @@ There are three kinds of external participants who can join meetings: Participants from trusted organizations join meetings via the [external access](manage-external-access.md) feature. You can control what domains, if any, your organization wants to trust. (This setting also affects 1:1 and group chat with people in those domains.) -If [Teams guest access](guest-access.md) is enabled for your organization, then guests will be able to join meetings. Guest access settings can also be used to control guests' screen sharing mode, including disabling screen sharing. (Guest access is also used for inviting guests to teams.) +If [Teams guest access](guest-access.md) is enabled for your organization, then guests can join meetings. Guest access settings can also be used to control guests' screen sharing mode, including disabling screen sharing. (Guest access is also used for inviting guests to teams.) -If the [**Anonymous users can join a meeting** Teams admin setting](anonymous-users-in-meetings.md) is turned on, anonymous participants will be able to join meetings. +If the [**Anonymous users can join a meeting** Teams admin setting](anonymous-users-in-meetings.md) is turned on, anonymous participants can able to join meetings. While you can turn anonymous join off completely without affecting features other than meetings, both guest access and trusted organizations are used in scenarios other than meetings. If you want to restrict meeting access for these participants but need to leave the features turned on for other reasons, you must use the lobby to prevent these participants from joining a meeting. ## Lobby options -The meeting lobby allows meeting organizers to vet attendees before allowing them into the meeting. Depending on the type of meeting and your compliance requirements, you may want to allow all attendees to bypass the lobby and join the meeting directly, or hold certain types of attendees in the lobby until they're admitted by a meeting organizer. If you wish to prevent certain types of people - such as guests - from attending meetings, you can have them go through the lobby and then the meeting organizer can deny them admittance. +The meeting lobby allows meeting organizers to vet attendees before allowing them into the meeting. Depending on the meeting type and compliance requirements, you can allow all attendees to bypass the lobby or hold certain attendees in the lobby until the organizer admits them. If you wish to prevent certain types of people - such as guests - from attending meetings, you can have them go through the lobby and then the meeting organizer can deny them admittance. For the baseline tier, we allow everyone except anonymous attendees to bypass the lobby. For sensitive meetings, we allow only people with a meeting invitation to bypass the lobby. For highly sensitive meetings, we require organizers to admit each attendee. As an admin, you can control the lobby in the following ways: - The **Who can bypass the lobby?** admin meeting policy (per user or group) +- The **Who can admit from lobby** admin meeting policy (per organizer or group) - The **People dialing in can bypass the lobby** admin meeting policy (per user or group) - The **Who can bypass the lobby?** option in sensitivity labels and meeting templates (per meeting) - The **People dialing in can bypass the lobby** admin meeting policy (per user or group) or in sensitivity labels and meeting templates (per meeting) -These options are also available to the meeting organizer unless they've been locked by a sensitivity label or template. +These options are also available to the meeting organizer unless a sensitivity label or template locks them. -If you're in a highly regulated industry and you need to manually admit each attendee to all meetings in your organization, you can configure the lobby by using admin meeting policies in the Teams admin center. If your organization has different types of meetings that have different lobby requirements, then we recommend using meeting templates or sensitivity labels to configure these options. +If you're in a highly regulated industry and need to manually admit attendees to all meetings, you can configure the lobby using admin meeting policies in the Teams admin center. If your organization has different types of meetings that have different lobby requirements, then we recommend using meeting templates or sensitivity labels to configure these options. While the admin policy sets a default, you need a template or label to enforce a lobby option. +You can choose to keep the default for **Who can admit from lobby** as **Organizers and presenters** or change it to **Organizers and co-organizers**. This per-organizer policy sets a default that your organizers can change through their **Meeting options**. You must manage this setting through the Teams admin center. Meeting templates and sensitivity labels don't support this policy. + For more information, see [Configure the Microsoft Teams meeting lobby for sensitive meetings](configure-lobby-sensitive-meetings.md). ## Related topics -[Microsoft cloud for enterprise architects illustrations](/microsoft-365/solutions/cloud-architecture-models) - -[Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) +- [Microsoft cloud for enterprise architects illustrations](/microsoft-365/solutions/cloud-architecture-models) +- [Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) diff --git a/Teams/considerations-calling-plan.md b/Teams/considerations-calling-plan.md index 99070c4671..c23af46314 100644 --- a/Teams/considerations-calling-plan.md +++ b/Teams/considerations-calling-plan.md @@ -1,7 +1,7 @@ --- title: Considerations for Calling Plans -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 05/08/2024 @@ -28,13 +28,13 @@ description: "Learn about emergency calling considerations for Microsoft Calling This article describes emergency calling considerations for Microsoft Calling Plan users. Before reading this article, see emergency calling concepts and definitions in [Plan and manage emergency calling](what-are-emergency-locations-addresses-and-call-routing.md). -To find out if Microsoft Calling Plans are the right solution for your business, see [PSTN connectivity options](pstn-connectivity.md) and [Microsoft Calling Plans for Teams](calling-plans-for-office-365.md). +To find out if Microsoft Calling Plans are the right solution for your business, see [Public Switched Telephone Network (PSTN) connectivity options](pstn-connectivity.md) and [Microsoft Calling Plans for Teams](calling-plans-for-office-365.md). ## Emergency call enablement for Calling Plans Each Calling Plan user is automatically enabled for emergency calling and is required to have a registered emergency address associated with their assigned telephone number. -When the location is associated to the telephone number depends on the country/region: +The point in time when the location is associated to the telephone number depends on the country/region: - In the United States and Canada, an emergency location is required when a number is assigned to a user. @@ -48,7 +48,7 @@ Dynamic location for routing emergency calls is supported in the United States a - If a Teams client for a United States Calling Plan user dynamically acquires an emergency address within the United States, that address is used for emergency routing instead of the registered address. The call is automatically routed to the PSAP in the serving area of the address. -- If a Teams client for a United States Calling Plan user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. +- If a Teams client for a United States Calling Plan user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones and Microsoft Teams Rooms route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. Dynamic location for routing emergency calls is supported in Canada the same as in the United States with the following exception: all emergency calls are screened nationally before being transferred to the PSAP. @@ -70,7 +70,7 @@ For example: - If a Teams client is located at a tenant-defined dynamic emergency location, emergency calls from that client are automatically routed to the PSAP serving that geographic location. -- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location. +- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone or Microsoft Teams Room, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location. - If an emergency caller is unable to update their emergency location to the screening center, the call is transferred to the PSAP serving the caller's registered address. diff --git a/Teams/considerations-direct-routing.md b/Teams/considerations-direct-routing.md index 69b2d57b46..f5963f4987 100644 --- a/Teams/considerations-direct-routing.md +++ b/Teams/considerations-direct-routing.md @@ -1,7 +1,7 @@ --- title: Considerations for Direct Routing -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 05/08/2024 @@ -26,9 +26,9 @@ description: "Learn about emergency calling considerations for Teams Phone Direc # Considerations for Direct Routing -This article describes considerations for emergency calling for Direct Routing users. Before reading this article, make sure you've read emergency calling concepts and definitions in [Plan and manage emergency calling](what-are-emergency-locations-addresses-and-call-routing.md). +This article describes considerations for emergency calling for Direct Routing users. Before reading this article, make sure you read emergency calling concepts and definitions in [Plan and manage emergency calling](what-are-emergency-locations-addresses-and-call-routing.md). -To find out if Direct Routing is the right solution for your business, see [PSTN connectivity options](pstn-connectivity.md) and [Plan Direct Routing](direct-routing-plan.md). +To find out if Direct Routing is the right solution for your business, see [Public Switched Telephone Network (PSTN) connectivity options](pstn-connectivity.md) and [Plan Direct Routing](direct-routing-plan.md). ## Emergency call enablement for Direct Routing @@ -38,7 +38,7 @@ You can assign an emergency call routing policy to a Direct Routing user account - If an emergency call routing policy is associated with the site, then the site policy is used to configure emergency calling. -- If there is no emergency call routing policy associated with the site, if the client is connected at an undefined site, or if the dialed number does not match any of the emergency numbers defined in the emergency call routing policy associated with the site, then the emergency call routing policy associated with the user account is used to configure emergency calling. +- If there's no emergency call routing policy associated with the site, if the client is connected at an undefined site, or if the dialed number doesn't match any of the emergency numbers defined in the emergency call routing policy associated with the site, then the emergency call routing policy associated with the user account is used to configure emergency calling. - If the Teams client is unable to obtain an emergency call routing policy, then the user isn't enabled for emergency calling. @@ -50,7 +50,7 @@ For Direct Routing users, dynamic location for routing emergency calls is suppor - If a Teams client for a United States Direct Routing user dynamically acquires an emergency address within the United States, that address is used for emergency routing instead of the registered address, and the call is automatically routed to the PSAP in the serving area of the address. -- If a Teams client for a United States Direct Routing user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. +- If a Teams client for a United States Direct Routing user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones and Microsoft Teams Rooms route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. Dynamic location for routing emergency calls is supported in Canada the same as in the United States with the following exception: all emergency calls are screened nationally before being transferred to the PSAP. @@ -58,7 +58,7 @@ For more information, see [Configure dynamic emergency calling](configure-dynami ## Emergency call routing for Direct Routing -The emergency call routing policy for Direct Routing references an online PSTN usage, which must have the appropriate Direct Routing configuration to properly route the emergency calls to the appropriate PSTN gateway(s). In particular, you must ensure that there is an OnlineVoiceRoute for the emergency dial string. For more information, see [Configure Direct Routing](direct-routing-configure.md). +The emergency call routing policy for Direct Routing references an online PSTN usage, which must have the appropriate Direct Routing configuration to properly route the emergency calls to the appropriate PSTN gateway(s). In particular, you must ensure that there's an OnlineVoiceRoute for the emergency dial string. For more information, see [Configure Direct Routing](direct-routing-configure.md). > [!NOTE] > Teams clients no longer prepend the "+" sign to emergency numbers; that is, +911. Consequently, Teams emergency calls no longer send a "+" preceding the 911 number. Be sure your voice route patterns reflect this change. @@ -89,7 +89,7 @@ When an emergency call with a dynamically acquired location is routed to the app - Substitutes the emergency caller's number with the ELIN phone number. - Routes the call to the PSAP serving that location, and then the dispatchers obtain the location from the uploaded ELIN record. -Upon a call back to the emergency number, the ELIN application will do the reverse called number substitution to that of the original emergency caller. +Upon a call-back to the emergency number, the ELIN application does the reverse called number substitution to that of the original emergency caller. For more information, see [Session Border Controllers certified for Direct Routing](direct-routing-border-controllers.md). diff --git a/Teams/considerations-operator-connect.md b/Teams/considerations-operator-connect.md index 093e0c6824..f7757d389e 100644 --- a/Teams/considerations-operator-connect.md +++ b/Teams/considerations-operator-connect.md @@ -1,7 +1,7 @@ --- title: Considerations for Operator Connect -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 05/08/2024 @@ -45,7 +45,7 @@ Dynamic location for routing emergency calls is supported in the United States a - If a Teams client for a United States user dynamically acquires an emergency address within the United States, that address is used for emergency routing instead of the registered address, and the call is automatically routed to the PSAP in the serving area of the address. -- If a Teams client for a United States user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. +- If a Teams client for a United States user doesn't dynamically acquire an emergency address within the United States, then the registered emergency address is used to help screen and route the call. Calls from Common Area Phones and Microsoft Teams Rooms route directly to the PSAP. Otherwise, the call is screened to determine if an updated address is required before connecting the caller to the appropriate PSAP. Dynamic location for routing emergency calls is supported in Canada the same as in the United States with the following exceptions: all emergency calls are screened nationally before being transferred to the PSAP. @@ -68,7 +68,7 @@ When a Teams Operator Connect user dials an emergency number, how the call is ro - In the United States, emergency calls from that client are automatically routed to the PSAP serving that geographic location. - In Canada, all emergency calls are screened by a national call center before transferring the call to the PSAP serving that geographic location. -- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location. +- If a Teams client isn't located at a tenant-defined dynamic emergency location and the client isn't a Common Area Phone or Microsoft Teams Room, emergency calls from that client are screened by a national call center to determine the location of the caller before transferring the call to the PSAP serving that geographic location. - If an emergency caller is unable to update their emergency location to the screening center, the call is transferred to the PSAP serving the caller's registered address. diff --git a/Teams/considerations-teams-phone-mobile.md b/Teams/considerations-teams-phone-mobile.md index 99ab763284..3677ba25cb 100644 --- a/Teams/considerations-teams-phone-mobile.md +++ b/Teams/considerations-teams-phone-mobile.md @@ -1,7 +1,7 @@ --- title: Considerations for Teams Phone Mobile -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 05/08/2024 diff --git a/Teams/copilot-teams-transcription.md b/Teams/copilot-teams-transcription.md index d485146a60..ceea947495 100644 --- a/Teams/copilot-teams-transcription.md +++ b/Teams/copilot-teams-transcription.md @@ -28,19 +28,22 @@ description: Learn how to manage Microsoft 365 Copilot in Teams meetings and eve # Manage Microsoft 365 Copilot in Teams meetings and events -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls Microsoft 365 Copilot in Teams meetings and events is an artificial intelligence (AI) tool that captures important conversation points. Each meeting and webinar participant with a Microsoft 365 Copilot license can ask prompts that are only visible to them. Participants and organizers can learn things like who said what and where people agree or disagree. Microsoft 365 Copilot in Teams can also recommend follow-up tasks, all in real time during a meeting. Organizers, co-organizers, and presenters can use Copilot during town hall events. As an admin, you can manage how users in your org use Copilot for Teams meetings and events. There are two ways for users in your organization to use Copilot in meetings and events: -**1. During and after the meeting**
+> [!IMPORTANT] +> When organizers turn off Copilot for their meeting or event, recording and transcription are also turned off. + +**1. During and after the meeting** When organizers create a meeting or event, they can set Copilot's value to **During and after the meeting** from the dropdown in their meeting options. Once someone starts transcription, licensed users can select the Copilot button for use during, and after the meeting or event. To learn more about how organizers can use Copilot during and after the meeting, see [Get started with Microsoft 365 Copilot in Teams in Microsoft Teams meetings](https://support.microsoft.com/office/get-started-with-copilot-in-microsoft-teams-meetings-0bf9dd3c-96f7-44e2-8bb8-790bedf066b1). -**2. Only during the meeting**
+**2. Only during the meeting** When organizers create a meeting or event, they can set Copilot's value to **Only during the meeting** from the dropdown in their meeting options. Once someone with a Microsoft 365 Copilot license selects the Copilot button during the meeting or event, Copilot runs for all licensed users. This option relies on speech-to-text audio processing data that isn't saved after the meeting or event ends. Users can't access Copilot in Teams and its history after the meeting or event. @@ -100,7 +103,7 @@ You can apply your Copilot meeting policies to groups or individual users. You c To manage how users in your org use Copilot in Teams meetings and events, use the **`-Copilot`** parameter within the PowerShell [**CsTeamsMeetingPolicy**](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet. -To allow users to use Copilot **Only during the meeting** in meetings and events created by organizers with this policy,: +To allow users to use Copilot **Only during the meeting** in meetings and events created by organizers with this policy: ```PowerShell Set-CsTeamsMeetingPolicy -Identity -Copilot Enabled diff --git a/Teams/cqd-intelligent-media-quality-classifiers.md b/Teams/cqd-intelligent-media-quality-classifiers.md index 0002a88736..2177b58d05 100644 --- a/Teams/cqd-intelligent-media-quality-classifiers.md +++ b/Teams/cqd-intelligent-media-quality-classifiers.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: jamp, oloper, hakanbe, mamcgrath -ms.date: 10/03/2024 +ms.date: 10/07/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -29,9 +29,9 @@ The Call Quality Dashboard (CQD) for Microsoft Teams and Skype for Business allo In CQD, Good and Poor stream classification is performed by a series of conditional statements. For audio, network metrics are used to determine if the performance of the underlying network would have resulted in degraded audio quality, while video and video-based screen sharing (VBSS) use video metrics to perform a similar quality assessment. The intelligent media quality classifiers take a broader and deeper view of the call telemetry, weighing several factors (including network) to determine perceived user experience of the call and to identify possible root cause when there's suspected quality degradation. Because of this difference, it's expected that the Good and Poor values resulting from the [stream classification](stream-classification-in-call-quality-dashboard.md) logic won't necessarily match up with the intelligent media quality classifier findings. -## Overview of intelligent media classifiers in CQD +## Overview of intelligent media quality classifiers in CQD -Intelligent media quality classifiers in CQD use Machine Learning (ML) algorithms that help pinpoint specific problem areas in stream quality. Compared to [Steam classification in CQD](stream-classification-in-call-quality-dashboard.md), intelligent media quality classification in CQD provides IT admins with a more advanced analysis into causality, media degradation, and root cause. These classifiers enable you to take proactive measures for addressing and preventing call quality issues. +Intelligent media quality classifiers in CQD use Machine Learning (ML) algorithms that help pinpoint specific problem areas in stream quality. Compared to [Stream classification in CQD](stream-classification-in-call-quality-dashboard.md), intelligent media quality classification in CQD provides IT admins with a more advanced analysis into causality, media degradation, and root cause. These classifiers enable you to take proactive measures for addressing and preventing call quality issues. To deliver the most comprehensive insights, intelligent media quality classifiers individually address three main real-time media modalities: Audio, Video, and VBSS. These classifiers focus on call quality on a stream level (such as Audio, Video, and VBSS) and then they go further with in-depth analyses in areas such as network, compute device, and input device, allowing for pinpointing specific problem areas. @@ -195,15 +195,15 @@ Network classifiers include three types of dimensions: location-related, network - Network-related dimensions: - Second Network - Second Network Name - - Second Wi-fi Band + - Second Wifi Band - Second Wifi Channel - Second Wifi Radio Type - - SecondWifiSignalStrengthValue + - Second Wifi Signal Strength - Second Network Connection Detail - - SecondSubnet - - SecondBSSID + - Second Subnet + - Second BSSID - Device-related dimensions: - - Second Wi-Fi Microsoft Driver + - Second Wifi Microsoft Driver - Second Wifi Vendor Driver - Second Compute Device Name @@ -304,7 +304,7 @@ The following CQD dimensions that can indicate possible audio issues are: - Audio Capture Device In Use - Audio Render Device In Use -The recommended range for signal level is (-24,-14), the optimal for noise is <-60. +The recommended range for signal level is (-24, -14), the optimal for noise is <-60. #### Input device root cause examples @@ -313,7 +313,7 @@ The recommended range for signal level is (-24,-14), the optimal for noise is <- ## Maintenance of classification models -The classifier models are monitored on the general population of Microsoft Teams users. If an anomaly is detected, then it is investigated and there's a high chance that the model is re-trained. This can cause temporal fluctuation of respective problem detection rates. Where these fluctuations would cause a significant change in detection rates, we will post a message to inform Teams admins through the M365 Message Center. +The classifier models are monitored on the general population of Microsoft Teams users. If an anomaly is detected, then it's investigated and there's a high chance that the model is re-trained. This can cause temporal fluctuation of respective problem detection rates. Where these fluctuations would cause a significant change in detection rates, we'll post a message to inform Teams admins through the M365 Message Center. ## Related topics diff --git a/Teams/create-a-phone-system-auto-attendant-languages.md b/Teams/create-a-phone-system-auto-attendant-languages.md index ed2f918511..bc3e3275a6 100644 --- a/Teams/create-a-phone-system-auto-attendant-languages.md +++ b/Teams/create-a-phone-system-auto-attendant-languages.md @@ -1,10 +1,10 @@ --- title: "Microsoft Teams auto attendant supported languages" -author: DaniEASmith -ms.author: danismith +author: mkbond007 +ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 02/05/2021 +ms.date: 10/31/2024 ms.topic: article ms.assetid: ms.tgt.pltfrm: cloud @@ -15,9 +15,9 @@ ms.collection: - m365initiative-voice - tier1 audience: Admin -appliesto: +appliesto: + - Microsoft Teams - Skype for Business - - Microsoft Teams ms.localizationpriority: medium f1.keywords: - CSH @@ -87,7 +87,7 @@ The auto attendant supports the following languages for Text to Speech (TTS) and |Welsh (United Kingdom) |Y |N | > [!NOTE] -> Choosing a language that does not support Speech Recognition will disable the voice inputs option within the menu and dial by name will be restricted to using keypad (DTMF) entry only. Please refer to [Dial by Name - Keypad (DTMF) entry](dial-voice-reference.md#dial-by-name---keypad-dtmf-entry) for more information. +> Choosing a language that doesn't support Speech Recognition will disable the voice inputs option within the menu and dial by name will be restricted to using keypad (DTMF) entry only. For more information, see [Dial by Name - Keypad (DTMF) entry](dial-voice-reference.md#dial-by-name---keypad-dtmf-entry). > [!NOTE] -> When using Text to Speech, the text must be entered in the selected language as the system does not perform translation. +> When using Text to Speech, the text must be entered in the selected language as the system doesn't perform translation. diff --git a/Teams/create-a-phone-system-auto-attendant-via-cmdlets.md b/Teams/create-a-phone-system-auto-attendant-via-cmdlets.md index 72cc9b83f0..db5ad4e01a 100644 --- a/Teams/create-a-phone-system-auto-attendant-via-cmdlets.md +++ b/Teams/create-a-phone-system-auto-attendant-via-cmdlets.md @@ -1,10 +1,10 @@ --- -title: Create an auto attendant via cmdlets -author: DaniEASmith -ms.author: danismith +title: Create an Auto attendant via cmdlets +author: mkbond007 +ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 01/20/2022 +ms.date: 10/29/2024 ms.topic: article ms.assetid: 6fc2687c-0abf-43b8-aa54-7c3b2a84b67c ms.tgt.pltfrm: cloud @@ -16,8 +16,8 @@ ms.collection: - tier1 audience: Admin appliesto: - - Skype for Business - Microsoft Teams + - Skype for Business ms.localizationpriority: medium f1.keywords: - CSH @@ -28,11 +28,11 @@ ms.custom: description: Learn how to configure auto attendants via cmdlets --- -# Create an auto attendant via cmdlets +# Create an Auto attendant via cmdlets -## Assumptions +## Prerequisites -1. PowerShell is installed on your computer +1. Install PowerShell on your computer. - Set up your computer for [Windows PowerShell](/SkypeForBusiness/set-up-your-computer-for-windows-powershell/set-up-your-computer-for-windows-powershell) - MSTeams Module Installed @@ -47,12 +47,12 @@ description: Learn how to configure auto attendants via cmdlets Install-Module -Name Microsoft.Graph -Force -AllowClobber ``` -2. You have tenant administration rights -3. You purchased Microsoft Teams Phone -4. The following call queues were set up using the [Creating Call Queues with PowerShell cmdlets](create-a-phone-system-call-queue-via-cmdlets.md) guide. +2. Ensure you have tenant administration rights. +3. Purchase Microsoft Teams Phone. +4. The call queues mentioned in this article were set up using the [Creating Call Queues with PowerShell cmdlets](create-a-phone-system-call-queue-via-cmdlets.md) guide. > [!NOTE] -> Some of the following cmdlets may be part of the Public Preview version of Teams PowerShell Module. For more information, see [Install Teams PowerShell public preview](teams-powershell-install.md) and also see [Microsoft Teams PowerShell Release Notes](teams-powershell-release-notes.md). +> Some of the cmdlets mentioned in this article may be part of the Public Preview version of Teams PowerShell Module. For more information, see [Install Teams PowerShell public preview](teams-powershell-install.md) and also see [Microsoft Teams PowerShell Release Notes](teams-powershell-release-notes.md). Users who already have the MicrosoftTeams module installed should `Update-Module MicrosoftTeams` to ensure the most up-to-date version is installed. @@ -85,7 +85,7 @@ Useful configuration information: ## Login -You will be prompted to enter your Teams administrator credentials. +When prompted, enter your Teams administrator credentials. ```PowerShell $credential = Get-Credential @@ -103,7 +103,7 @@ $operatorEntity = New-CsAutoAttendantCallableEntity -Identity $operatorID -Type ## Dial By Name Auto Attendant - Resource Account Creation -**Note**: Creating resource account here so it can be referenced on the main auto attendant. The actual Dial By Name auto attendant is created later. +Create a resource account here so it can be referenced on the main auto attendant. You can create the actual Dial By Name auto attendant later. ### Get license types @@ -113,7 +113,7 @@ Get-MgSubscribedSku ### Create and assign Resource Account -**Note**: Phone number not required here as call queue is front ended by an Auto Attendant +A phone number isn't required here as the call queue is nested behind an auto attendant. - ApplicationID - Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 @@ -298,7 +298,7 @@ Get-CsPhoneNumberAssignment -PstnAssignmentStatus Unassigned -CapabilitiesContai #### Assign available phone number -**Note:** Usage location assigned to the phone number must match the usage location assigned to the Resource Account. +The usage location assigned to the phone number must match the usage location assigned to the Resource Account. ```PowerShell Set-CsPhoneNumberAssignment -Identity ContosoMainAA-RA@contoso.com -PhoneNumber +{spare number from output of above command} -PhoneNumberType CallingPlan @@ -341,3 +341,11 @@ $dialByNameAutoAttendant = New-CsAutoAttendant -Name "Contoso Dial By Name" -Def ```PowerShell New-CsOnlineApplicationInstanceAssociation -Identities @($dialByNameApplicationInstanceID) -ConfigurationID $dialByNameAutoAttendant.Id -ConfigurationType AutoAttendant ``` + +## Related articles + +[Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) + +[Here's what you get with Microsoft Teams Phone](here-s-what-you-get-with-phone-system.md) + +[Create a Call queue via cmdlets](create-a-phone-system-call-queue-via-cmdlets.md) diff --git a/Teams/create-a-phone-system-auto-attendant.md b/Teams/create-a-phone-system-auto-attendant.md index 3b55fbb6e9..93ccedfed8 100644 --- a/Teams/create-a-phone-system-auto-attendant.md +++ b/Teams/create-a-phone-system-auto-attendant.md @@ -27,9 +27,9 @@ description: Learn how to set up and manage Auto attendants in Microsoft Teams. # Set up a Microsoft Teams Auto attendant -Auto attendants let people call your organization and navigate a menu system to speak to the right department, Call queue, person, or an operator. You can create Auto attendants for your organization with the Microsoft Teams admin center or with PowerShell. +Auto attendants let people call your organization and navigate a menu system to speak to the right department, Call queue, person, or operator. You can create Auto attendants for your organization with the Microsoft Teams admin center or with PowerShell. -Be sure you've read [Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) and followed the [getting started steps](plan-auto-attendant-call-queue.md#getting-started) before you follow the procedures in this article. +Before you follow the procedures in this article, be sure you've read [Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) and followed the [getting started steps](plan-auto-attendant-call-queue.md#getting-started). Auto attendants can redirect calls, based on callers' input, to one of the following destinations: @@ -40,7 +40,7 @@ Auto attendants can redirect calls, based on callers' input, to one of the follo - In Microsoft 365 admin center, enable **Let people outside the organization email this team** for the Microsoft 365 group that you specify. - **External phone number** - any phone number. See [external transfer technical details](create-a-phone-system-auto-attendant.md?tabs=general-info#external-phone-number-transfers---technical-details). - **Announcement (Audio file)** - Play an audio file. The system plays the announcement, and then returns to the Auto attendant menu. See [Supported audio file formats](plan-auto-attendant-call-queue.md#supported-audio-file-formats). -- **Announcement (Typed)** - Type in a message. Text you want the system to read. You can enter up to 1000 characters. The system plays the announcement, and then returns to the Auto attendant menu. +- **Announcement (Typed)** - Type in a message. Text you want the system to read. You can enter up to 1,000 characters. The system plays the announcement, and then returns to the Auto attendant menu. > [!NOTE] > When redirecting calls to a **Person in the organization**, that person must be voice enabled. For details on enabling voice, see [Assign Teams add-on licenses to users](teams-add-on-licensing/assign-teams-add-on-licenses.md). @@ -54,7 +54,11 @@ Auto attendants can redirect calls, based on callers' input, to one of the follo ## What's new for Auto attendants in the past six months -- No new features in the past six months. +- November 21 + - [Dial by name improvements](#dial-by-name-improvements) for when a search returns multiple people with the same name. + +- November 5 + - [Nested Auto attendants and Call queues](#nested-auto-attendants-and-call-queues) no longer require a resource account and associated licensing. ## Steps to create an Auto attendant @@ -66,7 +70,7 @@ The steps to add an Auto attendant are: 1. Set up resource accounts. 1. Set up authorized users. -The steps outlined in the article create Auto attendants using the Teams admin center. For instructions to **create Auto attendants using PowerShell**, see [Creating Auto attendants with PowerShell cmdlets](create-a-phone-system-auto-attendant-via-cmdlets.md). +The steps outlined in the article create Auto attendants using the Teams admin center. For instructions on creating Auto attendants using PowerShell, see [Creating Auto attendants with PowerShell cmdlets](create-a-phone-system-auto-attendant-via-cmdlets.md). ## Follow these steps to set up your Auto attendant @@ -85,9 +89,7 @@ To set up an Auto attendant, in the [Teams admin center](https://admin.teams.mic 1. Specify a [supported language](create-a-phone-system-auto-attendant-languages.md) for this Auto attendant. This language is used for system-generated voice prompts. > [!IMPORTANT] - > When using *Text to Speech*, the text must be entered in the selected language as the system doesn't perform translation. - > - > All words are pronounced in the selected language. + > When using *Text to Speech*, the text must be entered in the selected language as the system doesn't perform translation. All words are pronounced in the selected language. 1. Choose if you want to enable voice inputs. When enabled, the name of every menu option becomes a speech-recognition keyword. For example, callers can say "One" to select the menu option mapped to key 1, or they can say "Sales" to select the menu option named "Sales." If you choose a language in Step 4 that doesn't support voice inputs, this option isn't available. @@ -103,7 +105,7 @@ Once you've set your Auto attendant's general info, select **Next**. - If you select **Play an audio file** you can use the **Upload file** button to upload a recorded greeting message saved as audio in .WAV, .MP3, or .WMA format. The recording can be no larger than 5 MB. -- If you select **Type a greeting message**, the system reads the text that you enter (up to 1000 characters) when the Auto attendant answers a call. +- If you select **Type a greeting message**, the system reads the text that you enter (up to 1,000 characters) when the Auto attendant answers a call. ### Route the call @@ -133,9 +135,8 @@ If you assign dial keys to destinations, we recommend that you choose **None** f If you didn't assign dial keys, then choose an option for **Directory search**. -**Dial by name** - If you enable this option, callers can say the user's name or type it on the telephone keypad. Any online user or any user hosted on-premises using Skype for Business Server, is an eligible user and can be found with Dial by name. - -**Dial by extension** - If you enable this option, callers can connect with users in your organization by dialing their phone extension. Any online user or any user hosted on-premises using Skype for Business Server, is an eligible user and can be found with **Dial by extension**. (You can set who is and isn't included in the directory on the [Dial scope](?tabs=dial-scope) page.) +- **Dial by name** - If you enable this option, callers can say the user's name or type it on the telephone keypad. Any online user or any user hosted on-premises using Skype for Business Server, is an eligible user and can be found with Dial by name. +- **Dial by extension** - If you enable this option, callers can connect with users in your organization by dialing their phone extension. Any online user or any user hosted on-premises using Skype for Business Server, is an eligible user and can be found with **Dial by extension**. (You can set who is and isn't included in the directory on the [Dial scope](?tabs=dial-scope) page.) > [!NOTE] > If you want to use both the **Dial by name** and **Dial by extension** features, you can assign a dial key on your main Auto attendant to reach an Auto attendant enabled for **Dial by name**. Within that Auto attendant, you can assign the 1 key (which has no letters associated with it) to reach the **Dial by extension** Auto attendant. @@ -174,10 +175,10 @@ Your Auto attendant can have a call flow for each [Holiday you've set up](set-up 1. Choose the type of greeting that you want to use. -1. Choose if you want to **Disconnect**, **Redirect** or **Play menu options** the call. +1. Choose if you want to **Disconnect**, **Redirect**, or **Play menu options** the call. - 1. If you chose to redirect, choose the call routing destination for the call. - 1. If you choose to play menu options, configure the **Play menu options**. + - If you chose to redirect, choose the call routing destination for the call. + - If you choose to play menu options, configure the **Play menu options**. 1. Select **Save**. @@ -210,7 +211,9 @@ Before you can create and manage resource accounts, you must do the following: - [Obtain phone numbers](manage-resource-accounts.md#obtain-phone-numbers) - [Assign permissions for managing a resource account](manage-resource-accounts.md#assign-permissions-for-managing-a-resource-account) -All Auto attendants must have an associated resource account. All resource accounts must be assigned a [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md). If you wish, you can assign several resource accounts to an Auto attendant. +All Auto attendants that directly answer calls must have an associated resource account. All resource accounts must be assigned a [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md). If you wish, you can assign several resource accounts to an Auto attendant. + +Nested Auto attendants and Call queues that receive calls from an auto attendant or call queue that has already answered the call don't require a resource account. For details on how to create resource accounts and ready them for use with auto attendants, see [Manage Teams resource accounts](manage-resource-accounts.md). @@ -220,7 +223,7 @@ Once you've added resource accounts, select **Next**. ## Step 5: Authorized users -**Authorized users** specifies the users who are authorized to make changes to this Auto attendant. The capabilities that the users have are determined based on the [Teams voice applications policy](./manage-voice-applications-policies.md) that is assigned to the user. +**Authorized users** specifies the users who are authorized to make changes to this Auto attendant. The capabilities that the users have are determined based on the [Teams voice applications policy](./manage-voice-applications-policies.md) that is assigned to the user. To **add a user** to the authorized users: @@ -241,15 +244,45 @@ For more information, see [Set up authorized users](./aa-cq-authorized-users.md) --- +## Extra functionality available through PowerShell cmdlets + +> [!CAUTION] +> These configuration options are currently only available through PowerShell cmdlets and they don't appear in Teams admin center. If these options are configured through PowerShell, any changes to the Auto attendant through Teams admin center will erase these settings. + +### Nested Auto attendants and call queues + +Nested Auto attendants and Call queues (auto attendants and call queues that don't directly answer phone calls) no longer require a Resource Account and associated licensing. + +Existing configurations that use Resource Accounts continue to function and remain fully supported. A combination of both methods can be used at the same time. + +For more information, see [New-CsAutoAttendantCallableEntity -Type ConfigurationEndPoint](/powershell/module/teams/new-csautoattendantcallableentity#-Type). + +#### PowerShell example + +To create a new callable entity to another Auto attendant or Call queue, use the New-CsAutoAttendantCallableEntity cmdlet, as shown in the following example: + +```PowerShell +New-CsAutoAttendantCallableEntity -Identity -Type ConfigurationEndPoint +``` + +### Dial by name improvements + +When a dial by name search returns multiple people with the same name, the results can now be enhanced by appending additional information after the name. This makes it easier for callers to reach the correct person. + +The default is to only say the name. However, the office or department information can now be added as part of the results. + +For more information, see [New-CsAutoAttendant -UserNameExtension](/powershell/module/teams/new-csautoattendant#-UserNameExtension). + ## Resources for complex scenarios ### External phone number transfers - technical details -Refer to the [Prerequisites](plan-auto-attendant-call-queue.md#prerequisites) in order to allow Auto attendants to transfer calls externally. In addition, +Refer to the [Prerequisites](plan-auto-attendant-call-queue.md#prerequisites) in order to allow Auto attendants to transfer calls externally. -- For a resource account with a [Calling Plan license](calling-plans-for-office-365.md) or [Operator Connect](operator-connect-plan.md) number, the external transfer phone number must be entered in E.164 format (+[country code][area code][phone number]). +In addition, for a resource account with a: -- For a resource account with a Microsoft Teams Phone License and Direct Routing online voice routing policy, the external transfer phone number format is dependant on the [Session Border Controller (SBC)](direct-routing-connect-the-sbc.md) settings. +- [Calling Plan license](calling-plans-for-office-365.md) or [Operator Connect](operator-connect-plan.md) number, the external transfer phone number must be entered in E.164 format (+[country code][area code][phone number]). +- [Microsoft Teams Phone license](setting-up-your-phone-system.md) and [Direct Routing online voice routing policy](direct-routing-voice-routing.md), the external transfer phone number format is dependant on the [Session Border Controller (SBC)](direct-routing-connect-the-sbc.md) settings. The outbound phone number that's displayed is determined as follows: @@ -262,7 +295,7 @@ In a Skype for Business hybrid environment, to transfer an Auto attendant call t ### Auto Attendant Diagnostic Tool -If you're an administrator, you can use the following diagnostic tool to validate that an Auto attendant is able to receive calls: +As an administrator, you can use the following diagnostic tool to validate that an Auto attendant is able to receive calls: 1. Select **Run Tests**, which populates the diagnostic in the Microsoft 365 Admin Center. @@ -271,7 +304,7 @@ If you're an administrator, you can use the following diagnostic tool to validat 1. In the Run diagnostic pane, enter the Resource Account in the **Username or Email** field, and then select **Run Tests**. -1. The tests identify tenant, policy, or resource account configurations that are preventing the Auto attendant from receiving calls and also provide steps to fix any problems identified. +The tests identify tenant, policy, or resource account configurations that are preventing the Auto attendant from receiving calls and also provide steps to fix any problems identified. ## Related articles diff --git a/Teams/create-a-phone-system-call-queue-languages.md b/Teams/create-a-phone-system-call-queue-languages.md index ac23f1cf6c..c2f58c853b 100644 --- a/Teams/create-a-phone-system-call-queue-languages.md +++ b/Teams/create-a-phone-system-call-queue-languages.md @@ -1,10 +1,10 @@ --- title: "Microsoft Teams call queue supported languages" -author: DaniEASmith -ms.author: danismith +author: mkbond007 +ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 02/05/2021 +ms.date: 10/31/2024 ms.topic: article ms.assetid: ms.tgt.pltfrm: cloud diff --git a/Teams/create-a-phone-system-call-queue-via-cmdlets.md b/Teams/create-a-phone-system-call-queue-via-cmdlets.md index 668dfb342e..659db0efe8 100644 --- a/Teams/create-a-phone-system-call-queue-via-cmdlets.md +++ b/Teams/create-a-phone-system-call-queue-via-cmdlets.md @@ -1,10 +1,10 @@ --- -title: Create a call queue via cmdlets -author: DaniEASmith -ms.author: danismith +title: Create a Call queue via cmdlets +author: mkbond007 +ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 01/17/2022 +ms.date: 10/29/2024 ms.topic: article ms.assetid: 67ccda94-1210-43fb-a25b-7b9785f8a061 ms.tgt.pltfrm: cloud @@ -15,9 +15,9 @@ ms.collection: - m365initiative-voice - tier1 audience: Admin -appliesto: +appliesto: + - Microsoft Teams - Skype for Business - - Microsoft Teams ms.localizationpriority: medium f1.keywords: - CSH @@ -29,11 +29,11 @@ ms.custom: - azure-ad-ref-level-one-done description: Learn how to configure call queues via cmdlets --- -# Create a call queue via cmdlets +# Create a Call queue via cmdlets -## Assumptions +## Prerequisites -1. PowerShell is installed on your computer +1. Install PowerShell on your computer. - Set up your computer for [Windows PowerShell](/SkypeForBusiness/set-up-your-computer-for-windows-powershell/set-up-your-computer-for-windows-powershell) - MSTeams Module Installed @@ -47,21 +47,26 @@ description: Learn how to configure call queues via cmdlets Install-Module -Name Microsoft.Graph -Force -AllowClobber ``` -2. You have tenant administration rights -3. You have purchased Microsoft Teams Phone -4. The agents, distribution lists, and Teams channels referred to below have already been created +2. Ensure you have tenant administration rights. +3. Purchase Microsoft Teams Phone. +4. The agents, distribution lists, and Teams channels mentioned in this article have already been created. -Note: The Teams Channel cmdlet used below is part of the Public Preview version of Teams PowerShell Module. For more information, see [Install Teams PowerShell public preview](teams-powershell-install.md) and also see [Microsoft Teams PowerShell Release Notes](teams-powershell-release-notes.md). +> [!NOTE] +> The Teams Channel cmdlet used in this scenario is part of the Public Preview version of Teams PowerShell Module. For more information, see [Install Teams PowerShell public preview](teams-powershell-install.md) and also see [Microsoft Teams PowerShell Release Notes](teams-powershell-release-notes.md). Users who already have the MicrosoftTeams module installed should `Update-Module MicrosoftTeams` to ensure the most up-to-date version is installed. ## Scenario -The following three call queues will be created: +In this scenario, you create the following three call queues: + +- Sales Call Queue +- Support Call Queue +- Facilities Collaborative Calling Queue Sales Call Queue information: -- Fronted by Auto Attendant: Yes +- Nested behind Auto Attendant: Yes - Direct calling from PSTN: No - Language: English US - Greeting: None @@ -82,7 +87,7 @@ Sales Call Queue information: Support Call Queue information: -- Fronted by Auto Attendant: Yes +- Nested behind Auto Attendant: Yes - Direct calling from PSTN: No - Language: English UK - Greeting: Play an audio file @@ -107,7 +112,7 @@ Support Call Queue information: Facilities Collaborative Calling Queue information: -- Fronted by Auto Attendant: No +- Nested behind Auto Attendant: No - Direct calling from PSTN: No (internal calling only) - Language: French FR - Greeting: None @@ -127,7 +132,7 @@ Facilities Collaborative Calling Queue information: ## Login -You will be prompted to enter your Teams administrator credentials. +When prompted, enter your Teams administrator credentials. ```powershell $credential = Get-Credential @@ -139,7 +144,7 @@ Connect-MgGraph -Credential $credential ### Create Audio Files -Replace "d:\\" with the path to where the wav files are stored on your computer. +Replace `d:\\` with the path to where the wav files are stored on your computer. ```powershell $content = [System.IO.File]::ReadAllBytes('d:\sales-hold-in-queue-music.wav') @@ -160,7 +165,7 @@ $userSalesMaryID = (Get-CsOnlineUser -Identity "sip:mary@contoso.com").Identity Get-CsAutoAttendantSupportedLanguage ``` -### Create Call Queue +### Create Call queue ```powershell New-CsCallQueue -Name "Sales" -AgentAlertTime 15 -AllowOptOut $true -MusicOnHoldAudioFileID $audioFileSalesHoldInQueueMusicID -OverflowAction Forward -OverflowActionTarget $userAdeleID -OverflowThreshold 200 -TimeoutAction Forward -TimeoutActionTarget $userAdeleID -TimeoutThreshold 120 -RoutingMethod Attendant -ConferenceMode $true -User @($userSalesBillID, $userSalesMaryID) -LanguageID "en-US" @@ -172,15 +177,15 @@ New-CsCallQueue -Name "Sales" -AgentAlertTime 15 -AllowOptOut $true -MusicOnHold Get-MgSubscribedSku ``` -### Create and Assign Resource Account +### Create and assign resource account -Note: Phone number not required here as call queue is front ended by an Auto Attendant +A phone number isn't required here as the call queue is nested behind an auto attendant. - ApplicationID - Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 - Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 -Note: The license type shown below (PHONESYSTEM_VIRTUALUSER) must be one that is listed by the `Get-MgSubscribedSku` cmdlet above. +The license type shown after `(PHONESYSTEM_VIRTUALUSER)` must be one that's listed by the `Get-MgSubscribedSku` cmdlet. ```powershell New-CsOnlineApplicationInstance -UserPrincipalName Sales-RA@contoso.com -DisplayName "Sales" -ApplicationID "11cd3e2e-fccb-42ad-ad00-878b93575e07" @@ -199,7 +204,7 @@ New-CsOnlineApplicationInstanceAssociation -Identities @($applicationInstanceID) ### Create audio files -Replace "d:\\" with the path to where the wav files are stored on your computer. +Replace `d:\\` with the path to where the wav files are stored on your computer. ```powershell $content1 = [System.IO.File]::ReadAllBytes('d:\support-greeting.wav') @@ -224,7 +229,7 @@ $teamSupportID = (Get-Team -DisplayName "Support").GroupID Get-CsAutoAttendantSupportedLanguage ``` -### Create Call Queue +### Create Call queue ```powershell New-CsCallQueue -Name "Support" -AgentAlertTime 15 -AllowOptOut $false -DistributionLists $teamSupportID -WelcomeMusicAudioFileID $audioFileSupportGreetingID -MusicOnHoldAudioFileID $audioFileSupportHoldInQueueMusicID -OverflowAction SharedVoicemail -OverflowActionTarget $teamSupportID -OverflowThreshold 200 -OverflowSharedVoicemailAudioFilePrompt $audioFileSupportSharedVoicemailGreetingID -EnableOverflowSharedVoicemailTranscription $true -TimeoutAction SharedVoicemail -TimeoutActionTarget $teamSupportID -TimeoutThreshold 2700 -TimeoutSharedVoicemailTextToSpeechPrompt "We're sorry to have kept you waiting and are now transferring your call to voicemail." -EnableTimeoutSharedVoicemailTranscription $true -RoutingMethod LongestIdle -ConferenceMode $true -LanguageID "en-US" @@ -238,13 +243,13 @@ Get-MgSubscribedSku ### Create and Assign Resource Account -Note: Phone number not required here as call queue is front-ended by an Auto Attendant +A phone number isn't required here as the call queue is nested behind an auto attendant. - ApplicationID - Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 - Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 -Note: The license type shown below (PHONESYSTEM_VIRTUALUSER) must be one that is listed by the `Get-MgSubscribedSku` cmdlet above. +The license type shown after `(PHONESYSTEM_VIRTUALUSER)` must be one that's listed by the `Get-MgSubscribedSku` cmdlet. ```powershell New-CsOnlineApplicationInstance -UserPrincipalName Support-RA@contoso.com -DisplayName "Support" -ApplicationID "11cd3e2e-fccb-42ad-ad00-878b93575e07" @@ -280,7 +285,7 @@ $teamFacilitiesHelpDeskChannelID = "{assign ID from output of above command}" $teamFacilitiesHelpDeskChannelUserID = (Get-TeamChannelUser -GroupId $teamFacilitiesGroupID -DisplayName "Help Desk" -Role Owner).UserId ``` -### Get On Behalf Of Calling Resource Account ID +### Get on behalf of Calling Resource Account ID ```powershell $oboResourceAccountID = (Get-CsOnlineUser -Identity "MainAA-RA@contoso.com").Identity @@ -292,7 +297,7 @@ $oboResourceAccountID = (Get-CsOnlineUser -Identity "MainAA-RA@contoso.com").Ide Get-CsAutoAttendantSupportedLanguage ``` -### Create Call Queue +### Create Call queue ```powershell New-CsCallQueue -Name "Facilities" -AgentAlertTime 15 -AllowOptOut $false -ChannelId $teamFacilitiesHelpDeskChannelID -ChannelUserObjectId $teamFacilitiesHelpDeskChannelUserID -ConferenceMode $true -DistributionList $teamFacilitiesGroupID -LanguageID "fr-FR" -OboResourceAccountIds $oboResourceAccountID -OverflowAction DisconnectWithBusy -OverflowThreshold 200 -RoutingMethod RoundRobin -TimeoutAction Disconnect -TimeoutThreshold 2700 -UseDefaultMusicOnHold $true @@ -304,15 +309,15 @@ New-CsCallQueue -Name "Facilities" -AgentAlertTime 15 -AllowOptOut $false -Chann Get-MgSubscribedSku ``` -### Create and Assign Resource Account +### Create and assign Resource Account -**Note**: Phone number not required here as call queue is front-ended by an Auto Attendant +A phone number isn't required here as the call queue is nested behind an auto attendant. - ApplicationID - Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07 - Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07 -Note: The license type shown below (PHONESYSTEM_VIRTUALUSER) must be one that is listed by the `Get-MgSubscribedSku` cmdlet above. +The license type shown after `(PHONESYSTEM_VIRTUALUSER)` must be one that's listed by the `Get-MgSubscribedSku` cmdlet. ```powershell New-CsOnlineApplicationInstance -UserPrincipalName Facilities-RA@contoso.com -DisplayName "Facilities" -ApplicationID "11cd3e2e-fccb-42ad-ad00-878b93575e07" @@ -326,3 +331,11 @@ $callQueueID = (Get-CsCallQueue -NameFilter "Facilities").Identity New-CsOnlineApplicationInstanceAssociation -Identities @($applicationInstanceID) -ConfigurationID $callQueueID -ConfigurationType CallQueue ``` + +## Related articles + +[Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) + +[Here's what you get with Microsoft Teams Phone](here-s-what-you-get-with-phone-system.md) + +[Create an Auto attendant via cmdlets](create-a-phone-system-auto-attendant-via-cmdlets.md) diff --git a/Teams/create-a-phone-system-call-queue.md b/Teams/create-a-phone-system-call-queue.md index 2cb2facdfe..5ad9480561 100644 --- a/Teams/create-a-phone-system-call-queue.md +++ b/Teams/create-a-phone-system-call-queue.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 09/27/2024 +ms.date: 11/22/2024 ms.topic: article ms.assetid: 67ccda94-1210-43fb-a25b-7b9785f8a061 ms.tgt.pltfrm: cloud @@ -23,7 +23,7 @@ ms.localizationpriority: medium f1.keywords: - CSH ms.custom: - - ms.teamsadmincenter.callqueues.overview" + - ms.teamsadmincenter.callqueues.overview - Phone System description: Learn how to set up Call queues in Microsoft Teams. Call queues provide a greeting message, hold music, call redirecting, and other features. --- @@ -39,14 +39,19 @@ Call queues provide: - Call routing - in *First In, First Out* (FIFO) order - to agents. - Handling options for queue overflow and timeout. -Before you follow the procedures in this article, be sure you have read [Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) and followed the [getting started steps](plan-auto-attendant-call-queue.md#getting-started). +Before you follow the procedures in this article, be sure you've read [Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) and followed the [getting started steps](plan-auto-attendant-call-queue.md#getting-started). ## What's new for Call queues in the past six months +- November 22 + - [Callback](#step-5-callback-1) functionality is now available through Teams admin center. + +- November 5 + - [Nested Auto attendants and Call queues](#nested-auto-attendants-and-call-queues) no longer require a resource account and associated licensing. + - September 16 - - [Callback](#callback) functionality available through PowerShell cmdlets - - Conference mode is now supported for Skype for Business clients and calls that are routed to the queue from Skype for Business Server -- April 8 - Additional messaging options for call queue Overflow, Timeout, and No Agents exception routing in Teams admin center and [PowerShell cmdlets](#additional-messaging) + - [Callback](#callback-via-powershell) functionality is available through PowerShell cmdlets. + - Conference mode is now supported for Skype for Business clients and calls that are routed to the queue from Skype for Business Server. ## Steps to create a Call queue @@ -56,6 +61,7 @@ The steps to set up a Call queue includes: 1. Set the greeting and music 1. Set up call answering 1. Choose and assign agents +1. Set up callback 1. Set up call exception handling 1. Set up authorized users @@ -79,15 +85,15 @@ Before you can create and manage resource accounts, you must do the following ac - [Obtain phone numbers](manage-resource-accounts.md#obtain-phone-numbers) - [Assign permissions for managing a resource account](manage-resource-accounts.md#assign-permissions-for-managing-a-resource-account) -All Call queues must have an associated resource account. All resource accounts must be assigned a [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md). If you wish, you can assign several resource accounts to a Call queue. +All Call queues that directly answer calls must have an associated resource account. All resource accounts must be assigned a [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md). If you wish, you can assign several resource accounts to a Call queue. -For details on how to create resource accounts and ready them for use with auto attendants, see [Manage Teams resource accounts](manage-resource-accounts.md). +Nested Auto attendants and Call queues that receive calls from an auto attendant or call queue that has already answered the call don't require a resource account. -Agents see the resource account name when they receive an incoming call. +For details on how to create resource accounts and ready them for use with auto attendants or call queues, see [Manage Teams resource accounts](manage-resource-accounts.md). -### Assign a calling ID (optional) +Agents see the resource account name or call queue name when they receive an incoming call. -**Available for Teams channel/collaborative calling desktop users and Teams mobile client users with standard Call queues.** +### Assign a calling ID (optional) Assign outbound caller ID numbers for the agents by specifying one or more resource accounts with a phone number. Agents can select which outbound caller ID number to use with each outbound call they make. Within the Calls App, agents can use their Call Queue (CQ) / Auto Attendant (AA) number or their own personal Direct InWard Dial (DID). @@ -113,7 +119,7 @@ After you create this new resource account for calling ID, you still need to: ### Set the Service level threshold -_This feature is in public preview._ +_This feature is in private preview._ Service level measures the efficiency and responsiveness to incoming customer requests within a specific Service level threshold. @@ -144,7 +150,7 @@ Specify if you want to play a *greeting* to callers when they arrive in the queu >[!NOTE] > When using *Text to Speech*, the text must be entered in the selected language as the system doesn't perform translation. > -> All words will be pronounced in the selected language. +> All words are pronounced in the selected language. Teams provides default music to callers while they're *on hold in a queue*. @@ -180,7 +186,7 @@ The following clients are supported when using a Teams channel for Call queues: > [!NOTE] > If you use this option, it can take up to 24 hours for the Call queue to be fully operational. > -> If there are more than 200 members in the team, only the first 200 members, in alphabetical order, will be added as agents to the Call queue. +> If there are more than 200 members in the team, only the first 200 members, in alphabetical order, are added as agents to the Call queue. ### Users and groups @@ -197,23 +203,17 @@ To **add a user** to the queue: To **add a group** to the queue: 1. Select **Add groups**, search for the group, select **Add**, and then select **Add**. - 1. You can use distribution lists, security groups, and Microsoft 365 groups or Microsoft Teams teams. + - You can use distribution lists, security groups, and Microsoft 365 groups or Microsoft Teams teams. > [!NOTE] > New users added to a group can take up to eight hours for their first call to arrive. > -> If there are more than 200 members in the group, only the first 200 members, in alphabetical order, will be added as agents to the Call queue. +> If there are more than 200 members in the group, only the first 200 members, in alphabetical order, are added as agents to the Call queue. > [!IMPORTANT] > Known issue: Assigning private channels to Call queues > -> When using a private channel calls will be distributed to all members of the team even if the private channel only has a subset of team members. -> -> You may experience this problem when trying to assign a private channel to a Call queue. This problem may occur even if the Call queue previously had a private channel assigned or if the private channel was previously assigned to a Call queue. -> -> If you already have private channels assigned to Call queue they will continue to work. This problem only affects new assignments. -> -> Support continues to work on identifying the root cause of this problem. +> When using a private channel, calls are be distributed to all members of the team even if the private channel only has a subset of team members. You may experience this problem when trying to assign a private channel to a Call queue. This problem may occur even if the Call queue previously had a private channel assigned or if the private channel was previously assigned to a Call queue. If you already have private channels assigned to Call queues, they will continue to work. This problem only affects new assignments. Support continues to work on identifying the root cause of this problem. ### Conference mode @@ -226,12 +226,11 @@ Agents' Teams accounts must be set to TeamsOnly mode. Agents who don't meet the Once you select your call answering options, select the **Next** button at the bottom of the **Add a Call queue** page. -> [!NOTE] -> Conference mode isn't supported for calls that are routed to the queue from a Direct Routing gateway that's enabled for Location Based Routing. -> -> Conference mode is required if Teams users need to consult/transfer calls with Call queues. -> -> Agents may hear the configured music on hold in queue for up to 2 seconds when first joining the call. +Keep the following in mind: + +- Conference mode isn't supported for calls that are routed to the queue from a Direct Routing gateway that's enabled for Location Based Routing. +- Conference mode is required if Teams users need to consult/transfer calls with Call queues. +- Agents may hear the configured music on hold in queue for up to 2 seconds when first joining the call. > [!IMPORTANT] > Transfer mode (when conference mode is disabled) is now in legacy mode. Support for transfer mode is scheduled to be removed by the end of June 2025. @@ -241,11 +240,11 @@ Once you select your call answering options, select the **Next** button at the b ## Step 4: Select your agent routing options > [!NOTE] -> When using **Longest idle** and when there are less calls in queue than available agents, only the first two longest idle agents will be presented with calls from the queue. +> When using **Longest idle** and when there are fewer calls in the queue than available agents, only the first two longest idle agents are presented with calls from the queue. > > When using **Longest idle**, there may be times when an agent receives a call from the queue shortly after becoming unavailable, or a short delay in receiving a call from the queue after becoming available. > -> Call Queue call presentation to agents may conflict with Location Based Routing restrictions. In this case, the agent will receive a call toast but can't answer the call. This condition will continue until another agent is available to answer the call, the caller hangs up, or the Call queue timeout condition occurs. +> Call Queue call presentation to agents may conflict with Location Based Routing restrictions. In this case, the agent receives a call toast but can't answer the call. This condition continues until another agent is available to answer the call, the caller hangs up, or the Call queue timeout condition occurs. **Routing method** determines the order in which agents receive calls from the queue. @@ -253,7 +252,7 @@ Choose from these options: - **Attendant routing** rings all agents in the queue at the same time. The first call agent to pick up the call gets the call. -- **Serial routing** rings all call agents one by one in the order specified in the **Call agents** list. If an agent dismisses or doesn't pick up a call, the call will ring the next agent. This cycle repeats until the call is answered, times out, or the caller hangs up. +- **Serial routing** rings all call agents one by one in the order specified in the **Call agents** list. If an agent dismisses or doesn't pick up a call, the call rings the next agent. This cycle repeats until the call is answered, times out, or the caller hangs up. - **Round robin** balances the routing of incoming calls so that each call agent gets the same number of calls from the queue. @@ -276,9 +275,9 @@ If an agent opts out of getting calls, they can't receive calls regardless of th > Setting the **Presence-based routing** to **on** is the recommended setting. > [!NOTE] -> When **Longest idle** is selected as the routing method, presence-based routing is required and automatically enabled even though the Presence-based routing toggle will be **Off** and grayed out. +> When **Longest idle** is selected as the routing method, presence-based routing is required and automatically enabled even though the Presence-based routing toggle is **Off** and grayed out. > -> If presence-based routing isn't enabled and there are multiple calls in the queue, the system will present these calls simultaneously to the agents regardless of their presence status. This action will result in multiple call notifications to agents, particularly if some agents don’t answer the initial call presented to them. +> If presence-based routing isn't enabled and there are multiple calls in the queue, the system presents these calls simultaneously to the agents regardless of their presence status. This action results in multiple call notifications to agents, particularly if some agents don’t answer the initial call presented to them. > > When using **Presence-based routing**, there may be times when an agent receives a call from the queue shortly after becoming unavailable or a short delay in receiving a call from the queue after becoming available. > @@ -292,16 +291,138 @@ We recommend turning on **Call agents can opt out of taking calls**. ### Agent alert time -**Agent alert time** specifies how long an agent's phone will ring before the queue redirects the call to the next agent. +**Agent alert time** specifies how long an agent's phone rings before the queue redirects the call to the next agent. > [!TIP] > Setting the **Agent alert time** to a minimum **20 seconds** is the recommended setting. Once you select your agent call routing options, select the **Next** button at the bottom of the **Add a Call queue** page. -## [Step 5: Exception Handling](#tab/call-exception-handling) -## Step 5: Exception handling +## [Step 5: Callback](#tab/callback) + +## Step 5: Callback + +**Callback** allows *eligible* callers waiting in a call queue to receive a callback to the number they're calling from when an agent becomes available. + +A caller becomes eligible for callback based on any one of the following configured conditions coming true: + +- **Wait time in queue** - Once a caller in queue exceeds this configured wait time they become eligible for callback. This option applies to callers at the front of the queue. + +- **Number of calls in queue** - Once the number of callers in queue reaches this level, new callers arriving in the queue become eligible for callback. This option applies to callers arriving in the queue. Callers that arrived in the queue before this limit was reached aren't eligible for callback. + +- **Calls to agent ratio** - Once the number of callers waiting in queue exceeds the ratio, new callers arriving in the queue become eligible for callback. This option applies to callers arriving in the queue. + +Additionally, for a call to become eligble for callback, it must have a valid inbound phone number in E.164 format and it must not be presenting to an agent. + +After the music on hold finishes playing, eligible callers receive an option to request callback. + +As an admin, you can also set the messaging a caller hears, the key they need to press, and an email address to be notified at if the callback fails. + +#### Callback and Call queue timeouts + +In order for an *eligible* call to be offered callback, the [Call timeout](#call-timeout-set-how-to-handle-call-timeouts) value must be set high enough to allow the call to become eligible for callback and for the music to finish playing after the call becomes eligible. + +Consider the following call queue configuration: + +- Call back wait time in queue: 60 seconds +- Call Queue Timeout: 120 seconds +- Call Queue Music: Default + +After waiting in the queue for 60 seconds, the caller becomes eligible for callback. However, as the default music is two minutes long, the call queue timeout will occur first and the caller won't be offered callback. + +Once a caller has successfully requested a callback, the callback request is also subject to the call queue timout configuration. If a callback request times out, the information about the caller is sent to the configured email notification address. + +In order for a callback to be successful, the call queue timeout value must be high enough to allow for the call to become eligible, for the music to stop playing, for a caller to successfully request a callback, and for the callback to be queued until an agent becomes available and answers the call. + +> [!NOTE] +> For callers within the North American Numbering Plan, in addition to the eligibility requirements already listed and in order to become eligible for callback, the inbound phone number must not start with any of the following digits: +> +> |Starting Digits | +> |:-------------------------------------------------| +> | 1-242, 246, 264, 268, 284 | +> | 1-340, 345 | +> | 1-441 , 473 | +> | 1-500 | +> | 1-600, 649, 658, 664, 670, 671, 684 | +> | 1-700, 721, 758, 767, 784, 787 | +> | 1-800, 811, 822, 833, 844, 855, 866, 877, 888 | +> | 1-809, 829, 849, 868, 869, 876 | +> | 1-900, 939 | +> | 1-nnn-555-1212 | +> | 1-nnn-555,0100-0199 | + +Once you select your callback options, select the **Next** button at the bottom of the **Add a Call queue** page. + +### Callback via PowerShell + +|New-CsCallQueue (For new call queues) |Set-CsCallQueue (For existing call queues) | +|:---------------------------------------|:------------------------------------------| +| [-IsCallbackEnabled](/powershell/module/teams/new-cscallqueue#-IsCallbackEnabled) | [-IsCallbackEnabled](/powershell/module/teams/set-cscallqueue#-IsCallbackEnabled) | +| [-CallbackRequestDtmf](/powershell/module/teams/new-cscallqueue#-CallbackRequestDtmf) | [-CallbackRequestDtmf](/powershell/module/teams/set-cscallqueue#-CallbackRequestDtmf) | +| [-WaitTimeBeforeOfferingCallbackInSecond](/powershell/module/teams/new-cscallqueue#-WaitTimeBeforeOfferingCallbackInSecond) | [-WaitTimeBeforeOfferingCallbackInSecond](/powershell/module/teams/set-cscallqueue#-WaitTimeBeforeOfferingCallbackInSecond) | +| [-NumberOfCallsInQueueBeforeOfferingCallback](/powershell/module/teams/new-cscallqueue#-NumberOfCallsInQueueBeforeOfferingCallback) | [-NumberOfCallsInQueueBeforeOfferingCallback](/powershell/module/teams/set-cscallqueue#-NumberOfCallsInQueueBeforeOfferingCallback) | +| [-CallToAgentRatioThresholdBeforeOfferingCallback](/powershell/module/teams/new-cscallqueue#-CallToAgentRatioThresholdBeforeOfferingCallback) | [-CallToAgentRatioThresholdBeforeOfferingCallback](/powershell/module/teams/set-cscallqueue#-CallToAgentRatioThresholdBeforeOfferingCallback) | +| [-CallbackOfferAudioFilePromptResourceId](/powershell/module/teams/new-cscallqueue#-CallbackOfferAudioFilePromptResourceId) | [-CallbackOfferAudioFilePromptResourceId](/powershell/module/teams/set-cscallqueue#-CallbackOfferAudioFilePromptResourceId) | +| [-CallbackOfferTextToSpeechPrompt](/powershell/module/teams/new-cscallqueue#-CallbackOfferTextToSpeechPrompt) | [-CallbackOfferTextToSpeechPrompt](/powershell/module/teams/set-cscallqueue#-CallbackOfferTextToSpeechPrompt) | +| [-CallbackEmailNotificationTarget](/powershell/module/teams/new-cscallqueue#-CallbackEmailNotificationTarget) | [-CallbackEmailNotificationTarget](/powershell/module/teams/set-cscallqueue#-CallbackEmailNotificationTarget) | + +#### PowerShell Examples + +##### Calls become eligible after waiting 60 seconds + +To create a new call queue, use the New-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +New-CsCallQueue -Name "Callback Eligible After 60 seconds" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +To modify an existing call queue, use the Set-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +##### Calls become eligible for callback when there are more than 50 calls in queue + +To create a new call queue, use the New-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +New-CsCallQueue -Name "Callback Eligible After 50 calls" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +To modify an existing call queue, use the Set-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf + "Tone1" -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +##### Calls become eligible for callback when there are 2 times more calls than agents + +To create a new call queue, use the New-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +New-CsCallQueue -Name "Callback Eligible After 2x calls to agents" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -CallToAgentRatioThresholdBeforeOfferingCallback 2 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +To modify an existing call queue, use the Set-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf + "Tone1" -CallToAgentRatioThresholdBeforeOfferingCallback 2 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +##### Calls become eligible for callback after waiting 60 seconds or when there are more than 50 calls in queue + +To create a new call queue, use the New-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +New-CsCallQueue -Name "Callback Eligible After 60s or 50 calls" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + +To modify an existing call queue, use the Set-CsCallQueue cmdlet, as shown in the following example: +````PowerShell +Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +```` + + +## [Step 6: Exception Handling](#tab/call-exception-handling) + +## Step 6: Exception handling **Exception handling** determines how calls are handled when certain exceptions occur. @@ -311,9 +432,9 @@ For example, when **Overflow** occurs, you might send calls to a backup Call que > [!NOTE] > For external transfers, see [Prerequisites](./plan-auto-attendant-call-queue.md#prerequisites) and the [external phone number transfers - technical details](./create-a-phone-system-auto-attendant.md?tabs=general-info#external-phone-number-transfers---technical-details) for number formatting. -> +> > Don't include any special characters in the greeting message when redirecting to **Voicemail (shared)**. -> +> > The Overflow, Call timeout and No Agents exception redirect options for **Person in organization** and **Voicemail personal** support additional prompting. For more information, see [Additional messaging](#additional-messaging) ### Overflow: Set how to handle call overflow @@ -350,13 +471,13 @@ This call exception handling option handles calls when no agents are opted into > - Presence based routing off: No agents are opted into the queue. > - Presence based routing on: No agents logged in, or all agents are in *Appear Offline*. > -> If agents are logged in or opted in, then calls will be queued. +> If agents are logged in or opted in, then calls are queued. Once you select your call overflow, call timeout, and no agents handling options, select the **Next** button at the bottom of the **Add a Call queue** page. -## [Step 6: Authorized users](#tab/authorized-users) +## [Step 7: Authorized users](#tab/authorized-users) -## Step 6: Authorized users +## Step 7: Authorized users **Authorized users** specifies the users who are authorized to make changes to this Call queue. You can determine the capabilities that the users have through [Teams voice applications policies](./manage-voice-applications-policies.md) assigned to your users. @@ -394,11 +515,11 @@ The following settings are recommended: ## Extra functionality available through PowerShell cmdlets > [!CAUTION] -> These configuration options are currently only available through PowerShell cmdlets and they don't appear in Teams admin center. If these options are configured through PowerShell, any changes to the Call queue through Teams admin center will erase these settings. +> These configuration options are currently only available through PowerShell cmdlets and they don't appear in Teams admin center. If these options are configured through PowerShell, any changes to the Call queue through Teams admin center erases these settings. ### Additional messaging -The Overflow, Call timeout and No Agents exception redirect options for **Person in organization** and **Voicemail personal** support additional prompting just like the other redirect options. +The Overflow, Call timeout, and No Agents exception redirect options for **Person in organization** and **Voicemail personal** support additional prompting just like the other redirect options. For more information, see: @@ -417,170 +538,87 @@ For more information, see: | [-NoAgentRedirectVoicemailTextToSpeechPrompt](/powershell/module/teams/new-cscallqueue#-NoAgentRedirectVoicemailTextToSpeechPrompt) | [-NoAgentRedirectVoicemailTextToSpeechPrompt](/powershell/module/teams/set-cscallqueue#-NoAgentRedirectVoicemailTextToSpeechPrompt) | | [-NoAgentRedirectVoicemailAudioFilePrompt](/powershell/module/teams/new-cscallqueue#-NoAgentRedirectVoicemailAudioFilePrompt) | [-NoAgentRedirectVoicemailAudioFilePrompt](/powershell/module/teams/set-cscallqueue#-NoAgentRedirectVoicemailAudioFilePrompt) | -### Callback - -Callback allows eligible callers waiting in queue to receive a callback to the number they're calling from when an agent becomes available. - -A caller becomes *eligible* for callback based on any one of the following configured conditions coming true: - -- Wait time in queue - Once a caller in queue exceeds this configured wait time they become *eligible* for callback. This option applies to callers at the front of the queue. - -- Number of calls in queue - Once the number of callers in queue reaches this level, new callers arriving in the queue become *eligible* for callback. This option applies to callers arriving in the queue. Callers that arrived in the queue before this limit was reached aren't eligible for callback. - -- Calls to agent ratio - Once the number of callers waiting in queue exceeds the ratio, new callers arriving in the queue become *eligible* for callback. This option applies to callers arriving in the queue. - -Additionally, for a call to become *eligible* for callback, it must have a valid inbound phone number in E.164 format and it must not be presenting to an agent. - -*Eligible* callers will receive an option to request callback *after* the music on hold finishes playing. - -You can also set the messaging a caller hears, the key they need to press, and an email address to be notified if the callback fails. - -#### Callback and Call Queue Timeout - -In order for an *eligible* call to be offered callback, the [Call timeout](#call-timeout-set-how-to-handle-call-timeouts) value must be set high enough to allow the call to become eligible for callback and for the music to finish playing after the call becomes eligible. - -Consider the following call queue configuration: - -- Callback wait time in queue: 60 seconds -- Call Queue Timeout: 120 seconds -- Call Queue Music: Default - -In this configuration, a caller becomes eligible for callback after waiting in the queue for 60 seconds. However, as the default music is two minutes long, call queue timeout will occur and the caller won't be offered a callback. - -Once a caller successfully requests a callback, the callback is also subject to the call queue timeout configuration. If a callback times out, the information about the caller is sent to the configured email notification address. +### Hiding authorized users -In order for a callback to be successful, the call queue timeout value must be high enough to allow for the call to become eligible, for the music to stop playing, for a caller to successfully request a callback, and for the callback to be queued until an agent becomes available and answers the call. +Hidden authorized users are authorized users who shouldn't appear on the list of supervisors for the agents who are members of a particular call queue. -> [!NOTE] -> Conference mode must be enabled on the call queue in order to configure callback. -> -> In addition to the eligibility requirements already listed, for callers within the North American Numbering Plan, the inbound phone number must not start with any of the following digits in order to become eligible for callback: -> -> |Starting Digits | -> |:-------------------------------------------------| -> | 1-242, 246, 264, 268, 284 | -> | 1-340, 345 | -> | 1-441 , 473 | -> | 1-500 | -> | 1-600, 649, 658, 664, 670, 671, 684 | -> | 1-700, 721, 758, 767, 784, 787 | -> | 1-800, 811, 822, 833, 844, 855, 866, 877, 888 | -> | 1-809, 829, 849, 868, 869, 876 | -> | 1-900, 939 | -> | 1-nnn-555-1212 | -> | 1-nnn-555,0100-0199 | +Hidden authorized users aren't visible to Queues app users. For more information, see: |New-CsCallQueue (For new call queues) |Set-CsCallQueue (For existing call queues) | |:---------------------------------------|:------------------------------------------| -| [-IsCallbackEnabled](/powershell/module/teams/new-cscallqueue#-IsCallbackEnabled) | [-IsCallbackEnabled](/powershell/module/teams/set-cscallqueue#-IsCallbackEnabled) | -| [-CallbackRequestDtmf](/powershell/module/teams/new-cscallqueue#-CallbackRequestDtmf) | [-CallbackRequestDtmf](/powershell/module/teams/set-cscallqueue#-CallbackRequestDtmf) | -| [-WaitTimeBeforeOfferingCallbackInSecond](/powershell/module/teams/new-cscallqueue#-WaitTimeBeforeOfferingCallbackInSecond) | [-WaitTimeBeforeOfferingCallbackInSecond](/powershell/module/teams/set-cscallqueue#-WaitTimeBeforeOfferingCallbackInSecond) | -| [-NumberOfCallsInQueueBeforeOfferingCallback](/powershell/module/teams/new-cscallqueue#-NumberOfCallsInQueueBeforeOfferingCallback) | [-NumberOfCallsInQueueBeforeOfferingCallback](/powershell/module/teams/set-cscallqueue#-NumberOfCallsInQueueBeforeOfferingCallback) | -| [-CallToAgentRatioThresholdBeforeOfferingCallback](/powershell/module/teams/new-cscallqueue#-CallToAgentRatioThresholdBeforeOfferingCallback) | [-CallToAgentRatioThresholdBeforeOfferingCallback](/powershell/module/teams/set-cscallqueue#-CallToAgentRatioThresholdBeforeOfferingCallback) | -| [-CallbackOfferAudioFilePromptResourceId](/powershell/module/teams/new-cscallqueue#-CallbackOfferAudioFilePromptResourceId) | [-CallbackOfferAudioFilePromptResourceId](/powershell/module/teams/set-cscallqueue#-CallbackOfferAudioFilePromptResourceId) | -| [-CallbackOfferTextToSpeechPrompt](/powershell/module/teams/new-cscallqueue#-CallbackOfferTextToSpeechPrompt) | [-CallbackOfferTextToSpeechPrompt](/powershell/module/teams/set-cscallqueue#-CallbackOfferTextToSpeechPrompt) | -| [-CallbackEmailNotificationTarget](/powershell/module/teams/new-cscallqueue#-CallbackEmailNotificationTarget) | [-CallbackEmailNotificationTarget](/powershell/module/teams/set-cscallqueue#-CallbackEmailNotificationTarget) | +| [-HideAuthorizedUsers](/powershell/module/teams/new-cscallqueue#-hideauthorizedusers) | [-HideAuthorizedUsers](/powershell/module/teams/set-cscallqueue#-hideauthorizedusers) | -#### PowerShell Examples +### Nested Auto attendants and Call queues -##### Calls become eligible after waiting 60 seconds +**Nested Auto attendants and Call queues**, or auto attendants and call queues that don't directly answer phone calls, no longer require a Resource Account and associated licensing. -Create a new call queue: -````PowerShell -New-CsCallQueue -Name "Callback Eligible After 60 seconds" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget -```` +Existing configurations that use Resource Accounts will continue to function and remain fully supported. A combination of both methods can be used at the same time. -Modify an existing call queue: -````PowerShell -Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget -```` +When call queue [Exception handling](#step-6-exception-handling-1) occurs, the `Voice app` destination for Overflow, Timeout, and No Agents can refer to an auto attendant or call queue directly instead of the Resource Account for that auto attendant or call queue. -##### Calls become eligible for callback when there are more than 50 calls in queue +For more information, see the following documentation: -Create a new call queue: -````PowerShell -New-CsCallQueue -Name "Callback Eligible After 50 calls" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget -```` +|New-CsCallQueue (For new call queues) |Set-CsCallQueue (For existing call queues) | +|:---------------------------------------|:------------------------------------------| +| [-OverflowActionTarget](/powershell/module/teams/new-cscallqueue#-overflowactiontarget) | [-OverflowActionTarget](/powershell/module/teams/set-cscallqueue#-overflowactiontarget) | +| [-TimeOutActionTarget](/powershell/module/teams/new-cscallqueue#-timeoutactiontarget) | [-TimeOutActionTarget](/powershell/module/teams/set-cscallqueue#-timeoutactiontarget) | +| [-NoAgentActionTarget](/powershell/module/teams/new-cscallqueue#-noagentactiontarget) | [-NoAgentActionTarget](/powershell/module/teams/set-cscallqueue#-noagentactiontarget) | -Modify an existing call queue: -````PowerShell -Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf - "Tone1" -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget -```` -##### Calls become eligible for callback when there are 2 times more calls than agents +#### PowerShell example -Create a new call queue: -````PowerShell -New-CsCallQueue -Name "Callback Eligible After 2x calls to agents" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -CallToAgentRatioThresholdBeforeOfferingCallback 2 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget -```` +##### Overflow to another Auto attendant or Call queue -Modify an existing call queue: +To modify an existing call queue, use the Set-CsCallQueue cmdlet, as shown in the following examples: + +Overflow ````PowerShell -Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf - "Tone1" -CallToAgentRatioThresholdBeforeOfferingCallback 2 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +Set-CsCallQueue -Identity -OverflowAction Forward -OverflowActionTarget ```` -##### Calls become eligible for callback after waiting 60 seconds or when there are more than 50 calls in queue - -Create a new call queue: +Timeout ````PowerShell -New-CsCallQueue -Name "Callback Eligible After 60s or 50 calls" -UseDefaultMusicOnHold $true -LanguageID en-US -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +Set-CsCallQueue -Identity -OverflowAction Forward -TimeOutActionTarget ```` -Modify an existing call queue: +No Agents ````PowerShell -Set-CsCallQueue -Identity -IsCallbackEnabled $true -CallbackRequestDtmf "Tone1" -WaitTimeBeforeOfferingCallbackInSecond 60 -NumberOfCallsInQueueBeforeOfferingCallback 50 -CallbackOfferTextToSpeechPrompt "If you would like to have a callback when an agent becomes available, press 1" -CallbackEmailNotificationTarget +Set-CsCallQueue -Identity -OverflowAction Forward -NoAgentActionTarget ```` -### Hiding authorized users - -Hidden authorized users are authorized users who shouldn't appear on the list of supervisors for the agents who are members of a particular call queue. - -Hidden authorized users aren't visible to Queues app users. - -For more information, see: - -|New-CsCallQueue (For new call queues) |Set-CsCallQueue (For existing call queues) | -|:---------------------------------------|:-------------------| -| [-HideAuthorizedUsers](/powershell/module/teams/new-cscallqueue#-hideauthorizedusers) | [-HideAuthorizedUsers](/powershell/module/teams/set-cscallqueue#-hideauthorizedusers) | - ## Resources for complex scenarios ### Call queue feature compatibility -|Feature |Teams Desktop1 |Teams Web | Teams Mobile App2 |Teams Phone Mobile3 |Skype for Business |IP Phones | Standard Call Queues |Channel Based Call Queues | Comment | -|:--------------------------------|:------------------------:|:--------:|:----------------------------:|:-----------------------------:|:-----------------:|:--------:|:--------------------:|:------------------------:|:-------------| -|**Agent Routing Methods** | | | | | | | | | | -|Attendant Routing |Y |Y |Y |Y |Y |Y |Y |Y |*Default* | -|Longest Idle4 |Y |Y |Y |Y |N |Y |Y |Y |*Recommended* | -|Round Robin |Y |Y |Y |Y |Y |Y |Y |Y |*Recommended* | -|Serial |Y |Y |Y |Y |Y |Y |Y5 |Y5 | | -|**Agent Routing Options** | | | | | | | | | | -|Presence Based Routing4|Y |Y |Y |Y11 |N |Y |Y |Y |*Default* | -|Agents can opt out |Y |Y |Y |Y11 |Y8 |Y8|Y |Y |*Default* | -|**Transfer Modes** | | | | | | | | | | -|Conference Mode6 |Y |Y |Y |Y |Y |Y |Y |Y |*Default* | -|Transfer Mode |Y |Y |Y |Y |Y |Y |Y |Y | | -|**Collaborative Calling** | | | | | | | | | | -|Channel Based Queues |Y |N |N |N |N |N |N/A |Y9 |Agents on non-supported devices can still answer calls however they won't have the collaborative calling user interface | -|**Dynamic caller ID** | | | | | | | | | | -|Standard Call queue |Y |Y |Y |N |N |N |Y |N/A | | -|Channel based Call queue |Y |N/A |N/A |N/A |N/A |N/A |N/A |Y | | -|**PSTN Connectivity Methods** | | | | | | | | |See Note 10 | -|Calling Plans |Y |Y |Y |Y |Y |Y |Y |Y | | -|Direct Routing |Y |Y |Y |Y |N12 |Y |Y7 |Y | | -|Operator Connect |Y |Y |Y |Y |N |Y |Y7 |Y | | -|**Miscellaneous** | | | | | | | | | | -|Call toast shows Resource Account Name |Y |N |Y |N |Y | |Y |Y | | -|Click-to-call | Y |N |N |N |N |N |Y |Y | | -|[Compliance recording](teams-recording-policy.md) |N/A |N/A |N/A |N/A |N/A |N/A |N/A |N/A |Not supported | -|[Location based routing](location-based-routing-plan.md#inbound-calls-through-auto-attendants) |N/A |N/A |N/A |N/A |N/A |N/A |N/A |N/A |Not supported | +| Feature | Teams Desktop1 | Teams Web | Teams Mobile App2 | Teams Phone Mobile3 | Skype for Business | IP Phones | Standard Call Queues | Channel Based Call Queues | Comment | +|:-|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-| +| **Agent Routing Methods** | | | | | | | | | | +| Attendant Routing | Y | Y | Y | Y | Y | Y | Y | Y | *Default* | +| Longest Idle4 | Y | Y | Y | Y | N | Y | Y | Y | *Recommended* | +| Round Robin | Y | Y | Y | Y | Y | Y | Y | Y | *Recommended* | +| Serial | Y | Y | Y | Y | Y | Y | Y5 | Y5 | | +| **Agent Routing Options** | | | | | | | | | | +| Presence Based Routing4 | Y | Y | Y | Y11 | N | Y | Y | Y | *Default* | +| Agents can opt out | Y | Y | Y | Y11 | Y8 | Y8 | Y | Y | *Default* | +| **Transfer Modes** | | | | | | | | | | +| Conference Mode6 | Y | Y | Y | Y | Y | Y | Y | Y | *Default* | +| Transfer Mode | Y | Y | Y | Y | Y | Y | Y | Y | | +| **Collaborative Calling** | | | | | | | | | | +| Channel Based Queues | Y | N | N | N | N | N | N/A | Y9 | Agents on non-supported devices can still answer calls however they won't have the collaborative calling user interface | +| **Dynamic caller ID** | | | | | | | | | | +| Standard Call queue | Y | Y | Y | N | N | N | Y | N/A | | +| Channel based Call queue | Y | N/A | N/A | N/A | N/A | N/A | N/A | Y | | +| **PSTN Connectivity Methods** | | | | | | | | | See Note 10 | +| Calling Plans | Y | Y | Y | Y | Y | Y | Y | Y | | +| Direct Routing | Y | Y | Y | Y | N12 | Y | Y7 | Y | | +| Operator Connect | Y | Y | Y | Y | N | Y | Y7 | Y | | +| **Miscellaneous** | | | | | | | | | | +| Call toast shows Resource Account Name | Y | N | Y | N | Y | | Y | Y | | +| Click-to-call | Y | N | N | N | N | N | Y | Y | | +| Compliance recording | | | | | | | | | See [Compliance recording](teams-recording-policy.md) | +| [Location based routing](location-based-routing-plan.md#inbound-calls-through-auto-attendants) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | Not supported | #### Notes @@ -627,7 +665,7 @@ If you're an administrator, you can use the following diagnostic tool to validat 2. In the Run diagnostic pane, enter the Resource Account in the **Username or Email** field, and then select **Run Tests**. -3. The tests will return the best next steps to address any tenant, policy, and resource account configurations to validate that the Call queue is able to receive calls. +3. The tests return the best next steps to address any tenant, policy, and resource account configurations to validate that the Call queue is able to receive calls. ## Related articles diff --git a/Teams/create-and-manage-dial-plans.md b/Teams/create-and-manage-dial-plans.md index 10aded963e..fbe1bec311 100644 --- a/Teams/create-and-manage-dial-plans.md +++ b/Teams/create-and-manage-dial-plans.md @@ -1,7 +1,7 @@ --- title: "Create and manage dial plans" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 02/22/2024 diff --git a/Teams/create-custom-meeting-template.md b/Teams/create-custom-meeting-template.md index 27063102dc..3a3f5f6db3 100644 --- a/Teams/create-custom-meeting-template.md +++ b/Teams/create-custom-meeting-template.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: janineco -ms.date: 01/08/2024 +ms.reviewer: idilates +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,9 +25,9 @@ description: Learn how Microsoft Teams administrators can create a custom meetin [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -Microsoft Teams custom meeting templates (a Teams Premium feature) allow you to specify values for many of the meeting options available to meeting organizers. Templates can be used to configure options that meeting organizers can change or can be used to lock options so that meeting organizers can't change them. For more information about custom meeting templates, see [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md). +Microsoft Teams Premium's custom meeting templates allow you to specify values for many of the meeting options available to meeting organizers. Templates can be used to configure options that meeting organizers can change or can be used to lock options so that meeting organizers can't change them. For more information about custom meeting templates, see [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md). -You can create up to 50 custom templates. See [Manage meeting templates in Microsoft Teams](manage-meeting-templates.md) for information on how to manage which templates are available to your users. +You can create up to 50 custom templates. For information on how to manage which templates are available to your user, see [Manage meeting templates in Microsoft Teams](manage-meeting-templates.md). For each option in the template, you can define the following: @@ -50,17 +50,17 @@ To create a custom meeting template 1. In the Teams admin center, expand **Meetings** and select **Meeting templates**. 1. Select **Add**. -1. Type a name and description for the template. Note that the name and description will truncate after 40 characters when viewed in Teams, but the full name and description are viewable on hover. +1. Enter a name and description for the template. The name and description truncates after 40 characters when viewed in Teams, but the full name and description are viewable on hover. 1. Choose the options that you want to use for this template. (See the sections below for descriptions of each option.) 1. To prevent the meeting organizer from changing an option, select the option and then select **lock**. 1. To prevent the meeting organizer from seeing an option, select the option and then select **Hide**. 1. Select **Save**. -Once the template has been created, it may take up to 24 hours to be available to your users. + Once you create the template, it may take up to 24 hours for your users to see it. -Note that if you change the options of an existing template, the changes affect new meetings scheduled using that template as well as any meetings that have already been scheduled with that template. + If you change the options of an existing template, the changes affect new meetings scheduled using that template, as well as any meetings that are already scheduled with that template. -#### Security +### Security |Option|Description| |:------|:----------| @@ -70,30 +70,31 @@ Note that if you change the options of an existing template, the changes affect |End-to-end encryption|Specifies if the meeting uses end-to-end encryption. Recording and transcription don't work if this is on.| |Enable watermark for screenshare|Specifies if a watermark is overlaid on content that is shared on screen in the meeting.| |Enable watermark for video|Specifies if a watermark is overlaid on attendees' video feeds in the meeting.| +|Require verification checks from|Controls whether anonymous users must complete a verification check to join meetings and webinars in your org.| |Restrict participants from copying or forwarding meeting chat messages|Prevents participants from copying or forwarding content in the meeting chat.| -#### Audio & video +### Audio & video |Option|Description| |:------|:----------| |Allow mic for attendees|When **On**, attendees can unmute.| |Allow camera for attendees|When **On**, attendees can turn on their cameras.| -#### Recording & transcription +### Recording & transcription |Option|Description| |:------|:----------| |Record meetings automatically|When **On** meetings are recorded automatically.| |Who can record|Specifies whether meetings can be recorded by organizers and co-organizers only or by organizers, co-organizers, and presenters.| -|Copilot|Specifies if Copilot uses a meeting transcript.| +|Allow Copilot|Specifies when Copilot is available and how Copilot uses meeting transcripts.| -#### Roles +### Roles |Option|Description| |:------|:----------| |Announce when people dialing in join or leave|Specifies if a sound is played when people calling in by phone join or leave the meeting.| -#### Meeting engagement +### Meeting engagement |Option|Description| |:------|:----------| @@ -104,8 +105,7 @@ Note that if you change the options of an existing template, the changes affect ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Predefined meeting templates in Microsoft Teams](predefined-meeting-template-reference.md) diff --git a/Teams/custom-meeting-backgrounds.md b/Teams/custom-meeting-backgrounds.md index 739b077c70..7df1ff5f84 100644 --- a/Teams/custom-meeting-backgrounds.md +++ b/Teams/custom-meeting-backgrounds.md @@ -24,7 +24,7 @@ description: Using approved corporate assets like backgrounds to create custom b # IT Admins- Manage and create custom meeting backgrounds for Teams meetings -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/custom-meeting-templates-overview.md b/Teams/custom-meeting-templates-overview.md index 02fed63997..3f973882d6 100644 --- a/Teams/custom-meeting-templates-overview.md +++ b/Teams/custom-meeting-templates-overview.md @@ -31,25 +31,28 @@ The following meeting options can be controlled by using a meeting template: |Option|Description| |:------|:----------| -|*Security*|| +|**Security**|| |Sensitivity label|Specifies the sensitivity label to be used for the meeting.| |Lobby|Specifies who can bypass the lobby and join the meeting directly.| |End-to-end encryption|Specifies if the meeting is encrypted.| |Watermarks|Specifies if watermarks are used for camera feeds and content that is shared on screen in the meeting.| |Restrict participants from copying or forwarding meeting chat messages|Prevents participants from copying or forwarding content in the meeting chat.| -|*Audio & video*|| +|Require a verification check from|Controls whether anonymous users must complete a verification check to join meetings and webinars in your org.| +|**Audio & video**|| |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 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*|| +|**Meeting engagement**|| |Meeting chat|Specifies if the meeting chat is available. Can also be used to prevent chat before and after the meeting.| |Allow reactions|Specifies if attendees can use reactions or raise their hand in the meeting.| |Q&A|Specifies if attendees can use the Q&A feature to ask questions during the meeting.| |Manage what attendees see|Specifies if meeting organizers can preview and approve content being shared on screen before other meeting participants can see it.| +|Require a verification check from|**Not required**|Label or Template|Yes| + Some examples of when a template can be useful are: - Enforcing automatic meeting recording for certain types of meetings. @@ -71,6 +74,7 @@ Templates have the option of specifying a sensitivity label. Labels can also be - Meeting chat - Prevent copying chat content to clipboard - Record meetings automatically +- Require a verification check from - Who can bypass the lobby? - Who can present - Who can record diff --git a/Teams/custom-meetings-overview.md b/Teams/custom-meetings-overview.md index 99c47cec9c..3fa8df0029 100644 --- a/Teams/custom-meetings-overview.md +++ b/Teams/custom-meetings-overview.md @@ -7,7 +7,7 @@ ms.topic: conceptual ms.service: msteams audience: admin ms.reviewer: margidesai, nraghavan -ms.date: 12/18/2023 +ms.date: 11/1/2024 ms.localizationpriority: medium search.appverid: MET150 ms.collection: @@ -93,3 +93,10 @@ Collaborating with each team to define a standardized set of needs for meetings Consider the compliance implications of your customization features. Establish policies and guidelines to prevent the use of inappropriate or offensive images. I'ts important to ensure compliance with data protection and privacy regulations. Have your compliance team review meeting compliance features to find out which settings need to be on for all users in your org, specific users, or specific groups. Keep in mind that meeting background images are visible to external participants, so you should choose images that you’re okay with anyone viewing. + +## Related topics + +- [Plan for Teams meetings](plan-meetings.md) +- [Custom meeting backgrounds](custom-meeting-backgrounds.md) +- [Meeting themes](meeting-themes.md) +- [Custom meeting templates](custom-meeting-templates-overview.md) diff --git a/Teams/customize-meeting-invitations.md b/Teams/customize-meeting-invitations.md index 72b01f1347..d187407348 100644 --- a/Teams/customize-meeting-invitations.md +++ b/Teams/customize-meeting-invitations.md @@ -4,7 +4,7 @@ ms.author: wlibebe author: wlibebe manager: pamgreen ms.reviewer: -ms.date: 11/13/2023 +ms.date: 10/14/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -44,7 +44,7 @@ Now that you have your logo, you can customize your meeting invitations. ## Customize your meeting invitations using the Teams admin center 1. Navigate to the Teams admin center -2. In the left navigation, go to **Meetings** > **Meeting settings**. +2. In the left navigation, expand **Meetings** > **Meeting settings**. 3. Under **Email invitation**, do the following: - **Logo URL** Enter the URL where your logo is stored. @@ -54,3 +54,7 @@ Now that you have your logo, you can customize your meeting invitations. 4. Select **Preview invite** to see a preview of your meeting invitation. 5. When you're done, select **Save**. 6. Wait an hour or so for the changes to propagate and schedule a Teams meeting to see what the meeting invitation looks like. + +## Related topics + +- [Plan meetings](plan-meetings.md) diff --git a/Teams/delete-exchange-online-transcripts.md b/Teams/delete-exchange-online-transcripts.md index 9070160681..f6688f6a64 100644 --- a/Teams/delete-exchange-online-transcripts.md +++ b/Teams/delete-exchange-online-transcripts.md @@ -23,7 +23,10 @@ appliesto: # Delete Exchange Online and OneDrive transcript files -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls + +> [!NOTE] +> When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off. To learn more about Copilot, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). In Microsoft Teams, the current storage location of meeting transcript files is known as Exchange Online transcript or substrate transcript. Exchange Online transcript is scheduled for deprecation in 2024. The new storage location is OneDrive. diff --git a/Teams/deploy-chat-teams-channels-microsoft-teams-landing-page.md b/Teams/deploy-chat-teams-channels-microsoft-teams-landing-page.md index 65d879da72..49cce58abc 100644 --- a/Teams/deploy-chat-teams-channels-microsoft-teams-landing-page.md +++ b/Teams/deploy-chat-teams-channels-microsoft-teams-landing-page.md @@ -1,9 +1,9 @@ --- title: Chat, teams, channels, & apps in Microsoft Teams -ms.reviewer: -ms.date: 10/30/2018 -author: MicrosoftHeidi -ms.author: heidip +ms.reviewer: karuanag +ms.date: 11/04/2024 +author: DaniESmith +ms.author: danismith manager: jtremper ms.topic: article ms.service: msteams @@ -29,19 +29,13 @@ appliesto: Teams provides a great out-of-the-box collaboration experience for your organization, and most organizations find that the default settings work for them. This article helps you decide whether to change any of the default settings, based on your organization's profile and business requirements, then it walks you through each change. We've split the settings into two groups, starting with the core set of [changes you're more likely to make](#core-deployment-decisions). The second group includes the [additional settings](#additional-deployment-decisions) you may want to configure, based on your organization's needs. -To get started, watch our short Teams chat, teams, and channels video (4:30 minutes): - -
- -> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE476Yj?autoplay=false] - -You can use [Advisor for Teams](use-advisor-teams-roll-out.md) to help you roll out Microsoft Teams. Advisor for Teams walks you through your Teams rollout. It assesses your Microsoft 365 environment and identifies the most common configurations that you may need to update or modify before you can successfully roll out Teams. +Use [Advisor for Teams](use-advisor-teams-roll-out.md) to help you roll out Microsoft Teams. It assesses your Microsoft 365 environment and identifies the most common configurations that you may need to update or modify before you can successfully roll out Teams. > [!TIP] -> We recommend that you include our featured apps -- such as Planner -- in your initial Teams rollout. Add other [Teams apps](apps-in-teams.md) as you drive Teams adoption. +> We recommend that you include our featured apps, such as Planner, in your initial Teams rollout. Add other [Teams apps](apps-in-teams.md) as you drive Teams adoption. - > [!Note] - > For details about Teams features on different platforms, see [Teams features by platform](https://support.microsoft.com/office/teams-features-by-platform-debe7ff4-7db4-4138-b7d0-fcc276f392d3). +> [!NOTE] +> For details about Teams features on different platforms, see [Teams features by platform](https://support.microsoft.com/office/teams-features-by-platform-debe7ff4-7db4-4138-b7d0-fcc276f392d3). ## Chat deployment prerequisites @@ -71,9 +65,9 @@ In addition to administrator roles, Teams lets you assign owner and member user |Ask yourself|Action | |------------|-------| -|Who should be assigned to each role? | To compare the capabilities of each role, see [Assign team owners, moderators, and members in Microsoft Teams](assign-roles-permissions.md). -|How do I assign a user role? | To assign or change a role, see [Assign a user role](assign-roles-permissions.md). -|Do I need to control who can post and reply in a channel? | To configure moderation, see [Set up and manage channel moderation in Microsoft Teams](manage-channel-moderation-in-teams.md). +|Who should be assigned to each role? | To compare the capabilities of each role, see [Assign team owners, moderators, and members in Microsoft Teams](assign-roles-permissions.md).| +|How do I assign a user role? | To assign or change a role, see [Assign a user role](assign-roles-permissions.md).| +|Do I need to control who can post and reply in a channel? | To configure moderation, see [Set up and manage channel moderation in Microsoft Teams](manage-channel-moderation-in-teams.md).| ### Messaging policies @@ -98,7 +92,7 @@ External access (federation) lets your users communicate with people outside of Guest access in Teams lets individuals outside your organization access teams and channels. You can use the guest access settings to control which features guests can or can't use. Guest access is turned on by default. To learn more, see [Guest access in Teams](./guest-access.md). > [!NOTE] -> For more on external access and guest access see here - [Communicate with users from other organizations in Microsoft Teams](communicate-with-users-from-other-organizations.md) +> For more on external access and guest access, see [Communicate with users from other organizations in Microsoft Teams](communicate-with-users-from-other-organizations.md). |Ask yourself|Action | |------------|-------| @@ -111,7 +105,7 @@ Private channels allow a subset of team members to collaborate in a private spac |Ask yourself|Action | |------------|-------| -|Do I want to allow team owners and members to create private channels?|To set private channels policy for your organization, see [Manage channel policies in Microsoft Teams](teams-policies.md)| +|Do I want to allow team owners and members to create private channels?|To set private channels policy for your organization, see [Manage channel policies in Microsoft Teams](teams-policies.md).| ### Shared channels @@ -200,11 +194,11 @@ Your organization might require that you implement controls on how teams are nam ### Teams application policy (side-rail control) -A pinned app shows up in the side rail in Teams. By creating Teams application policies, you can preconfigure sets of pinned Teams apps to personalize Teams for select groups of users. By default, the **Allow external apps in Microsoft Teams** setting is turned on. +A pinned app shows up in the side rail in Teams. By creating Teams application policies, you can pre-configure sets of pinned Teams apps to personalize Teams for select groups of users. By default, the **Allow external apps in Microsoft Teams** setting is turned on. | Ask yourself | Action | |--------------|--------| -|Should I create preconfigured sets of pinned Teams applications? | Read [Admin settings for apps in Teams](admin-settings.md).| +|Should I create pre-configured sets of pinned Teams applications? | Read [Admin settings for apps in Teams](admin-settings.md).| |How will I decide which groups receive these app groupings?|Read [Teams apps permissions and considerations](app-permissions.md).| ### Archiving and compliance @@ -223,7 +217,7 @@ Teams relies heavily on Exchange and SharePoint for core productivity scenarios, | Ask yourself | Action | |--------------|--------| -|
Will I need to configure conditional access for Teams?|
  • To understand how access policies work, see [How do conditional access policies work for Teams?](security-compliance-overview.md#how-conditional-access-policies-work-for-teams)
  • To set up multi-factor authentication (MFA) for Teams, see:
    • [Quickstart: Require MFA for specific apps with Microsoft Entra Conditional Access](/azure/active-directory/conditional-access/app-based-mfa)
    • [Microsoft Entra Conditional Access settings reference](/azure/active-directory/conditional-access/technical-reference)
| +|Will I need to configure conditional access for Teams?|
  • To understand how access policies work, see [How do conditional access policies work for Teams?](security-compliance-overview.md#how-conditional-access-policies-work-for-teams)
  • To set up multi-factor authentication (MFA) for Teams, see:
    • [Quickstart: Require MFA for specific apps with Microsoft Entra Conditional Access](/azure/active-directory/conditional-access/app-based-mfa)
    • [Microsoft Entra Conditional Access settings reference](/azure/active-directory/conditional-access/technical-reference)
| ### Education (EDU) @@ -246,6 +240,6 @@ The use of Office 365 for Government - GCC (Government Community Cloud) is appro ## Next steps - [Drive adoption](adopt-microsoft-teams-landing-page.md) of chat, teams, channels, & apps. -- Include featured apps - such as Planner - in your initial Teams rollout. Add other [Teams app](apps-in-teams.md) as you drive Teams adoption. -- [Roll out meetings & conferencing](deploy-meetings-microsoft-teams-landing-page.md) -- [Roll out cloud voice](cloud-voice-landing-page.md) +- Include featured apps, such as Planner, in your initial Teams rollout. Add other [Teams app](apps-in-teams.md) as you drive Teams adoption. +- [Roll out meetings & conferencing](deploy-meetings-microsoft-teams-landing-page.md). +- [Roll out cloud voice](cloud-voice-landing-page.md). diff --git a/Teams/deploy-overview.md b/Teams/deploy-overview.md index d717e1ed9b..1c50eac2e4 100644 --- a/Teams/deploy-overview.md +++ b/Teams/deploy-overview.md @@ -3,7 +3,7 @@ title: IT Admins - Microsoft Teams deployment overview author: MicrosoftHeidi ms.author: heidip manager: jtremper -ms.date: 10/09/2023 +ms.date: 10/28/2024 ms.topic: concept-article ms.service: msteams audience: admin diff --git a/Teams/devices/android-version-support.md b/Teams/devices/android-version-support.md index db017b5f68..30ffa40fc5 100644 --- a/Teams/devices/android-version-support.md +++ b/Teams/devices/android-version-support.md @@ -46,13 +46,13 @@ You can learn more about end of certification of Teams devices by visiting [Devi ## Microsoft Teams Devices Applications Support -Microsoft Teams applications running on Android Teams devices and other Microsoft applications present on Teams on Android devices (as needed for authentication and device management) are governed by [Modern Lifecycle Policy](/lifecycle/policies/modern). +Microsoft Teams applications running on Android Teams devices and other Microsoft applications present on Teams on Android devices (as needed for authentication and device management) are governed by [Modern Lifecycle Policy](/lifecycle/policies/modern). -Microsoft applications are updated from Microsoft Teams Admin Center (TAC) or Teams Rooms Pro management portal (PMP), where device admins can configure policies for automatic or manual updates of these applications. Microsoft recommends customers to use auto-update setting to ensure Teams on Android devices stays up to date and functional. In cases where customers may need to set up manual updates, customers must make sure to stay current on Microsoft applications. Microsoft tests and supports the latest and latest-1 versions of Microsoft applications on the device. Keeping devices on older versions of the application can leave your Teams Rooms devices unstable and unusable. +Microsoft applications are updated from Microsoft Teams Admin Center (TAC) or Teams Rooms Pro management portal (PMP), where device admins can configure policies for automatic or manual updates of these applications. Microsoft recommends customers to use auto-update setting to ensure Teams on Android devices stays up to date and functional. In cases where customers may need to set up manual updates, customers must make sure to stay current on Microsoft applications. Microsoft tests and supports the latest and latest-1 versions of Microsoft applications on the device. Keeping devices on older versions of the application can leave your Teams devices unstable and unusable. -Teams on Android devices customers should follow Modern Lifecycle Policy guidelines to receive Teams device applications on Android device support from Microsoft. While the latest and latest-1 versions of Microsoft applications on the device, the support structure for Teams Rooms devices applications is dynamic and depends on the availability of the latest version. When you encounter a code defect in a version of the application that's not the latest, you must install the latest version to receive a fix. +Teams on Android devices customers should follow Modern Lifecycle Policy guidelines to receive Teams device applications on Android device support from Microsoft. While the latest and latest-1 versions of Microsoft applications on the device, the support structure for Teams Rooms devices applications is dynamic and depends on the availability of the latest version. When you encounter a code defect in a version of the application that's not the latest, you must install the latest version to receive a fix. -All Teams rooms devices applications Android releases are listed at [What's new in Microsoft Teams devices](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2). +All Teams devices applications Android releases are listed at [What's new in Microsoft Teams devices](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2). > [!IMPORTANT] >If you are installing Teams devices applications from a device Original Equipment Manufacturers (OEM) provided service, make sure to validate that Microsoft applications provided by the device OEMs are listed and supported in Teams Admin Center, Teams Rooms Pro management portal or listed at [Devices for Teams](/microsoftteams/devices/teams-ip-phones#product-release-information-for-teams-phones) or [Teams Rooms on Android app and firmware versions](/microsoftteams/rooms/android-app-firmware). @@ -65,13 +65,14 @@ Android operating system and firmware updates installed through device hardware Microsoft applications running on this Android operating system provided by Original Equipment Manufacturers (OEM) partners are bound to Google’s support cycle for the Android OS operating system versions. -The following Android operating systems that are supported on Teams Rooms on Android: +The following Android operating systems that are supported on Teams on Android devices: -|**Android OS version**|**Android OS Google release date**|**Microsoft Teams Certification end date**|**Microsoft ‘best effort’ support end date**| +|**Android OS version**|**Android OS Google release date**|**Microsoft Teams Certification end date**|**Microsoft support end date**| |:-----|:-----|:-----|:-----| |Android 9|August 6, 2018|August 5, 2023|August 5, 2025| |Android 10|September 3, 2019|September 3, 2025|September 3, 2027| |Android 11|September 8, 2020|September 3, 2025|September 3, 2027| |Android 12|October 4, 2021|August 15, 2027|August 15, 2029| |Android 13|August 15, 2022|August 15, 2027|August 15, 2029| -|Android 14|October 4, 2023|October 4, 2028|October 4, 2030| \ No newline at end of file +|Android 14|October 4, 2023|October 4, 2028|October 4, 2030| +|Android 15|October 15, 2024|October 15, 2029|October 15, 2031| \ No newline at end of file diff --git a/Teams/devices/authentication-best-practices-for-android-devices.md b/Teams/devices/authentication-best-practices-for-android-devices.md index 7e26715039..804c4fd1b9 100644 --- a/Teams/devices/authentication-best-practices-for-android-devices.md +++ b/Teams/devices/authentication-best-practices-for-android-devices.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: dimehta -ms.date: 09/30/2024 +ms.date: 10/21/2024 ms.topic: article ms.service: msteams ms.subservice: itpro-devices @@ -22,11 +22,9 @@ ms.localizationpriority: Medium description: Best practices on shared android device management in Teams. This features Conditional Access, password policy, multifactor authentication advice and more. --- -# Authentication best practices for Teams shared device management on Android devices +# Authentication best practices for Teams Rooms on Android and Teams panels -The goals of devices used with Teams make different device management strategies necessary. For example, a personal business tablet used by a single sales person has a different set of needs from an on-call phone shared by many customer service people. - -Security administrators and operations teams must plan for the devices that can be used in the organization. They must implement *security* measures best suited to each purpose. This article's recommendations make some of those decisions easier. +The goals of devices used with Teams make different device management and security strategies necessary. For example, a personal business tablet used by a single sales person has a different set of needs from an on-call phone shared by many customer service people. Security administrators and operations teams must plan for the devices that are used in the organization. They must implement security measures best suited to each purpose. This article's recommendations make some of those decisions easier. Commonly, Teams Rooms on Android and Teams panel devices are deployed with resource accounts which should be configured specifically for their function. If, there are users in your organization using Teams Rooms on Android in a *personal mode*, specific security configurations must be made to ensure they can sign in to the device successfully. >[!NOTE] >Conditional Access requires a Microsoft Entra ID P1 or P2 subscription. @@ -34,80 +32,73 @@ Security administrators and operations teams must plan for the devices that can >[!NOTE] >Policies for Android mobile devices may not apply to Teams Android devices. -## Authentication recommendations are different for personal versus shared android devices +## Challenges with using the same controls for personal accounts and Teams resource accounts -Shared Teams devices can't use the same requirements for enrollment and compliance that are used on personal devices. Applying personal device authentication requirements to shared devices cause sign in issues. +Shared Teams devices can't use the same requirements for enrollment and compliance that are used on personal accounts and devices. Applying personal device authentication requirements to shared devices cause sign in issues. Some challenges with personal account security on resource accounts are: -1. **Devices are signed out due to password policies.** +1. **Devices are signed out due to passwords expiry.** - Accounts used on Teams devices have a password-expiration policy. The accounts used with shared devices don't have a specific user to update and restore them to a working state when their passwords expire. If your organization requires passwords to expire and reset occasionally, these accounts stop working on Teams devices until a Teams administrator resets the password and signs back in. + If the accounts used on Teams devices have a password-expiration policy, when the password expires the Teams Room or panel device will sign out automatically. The accounts used with shared space devices don't have a specific user to update and restore them to a working state when their passwords expire. If your organization requires passwords to expire and reset occasionally, these accounts stop working on Teams devices until a Teams device administrator resets the password and manually signs the device back in. Teams resource accounts should be excluded from password expiration. - **Challenge**: When it comes to accessing. Teams from a device, a person's account has a password-expiration policy. When the password is going to expire, they change it. But accounts used on *shared devices*(Resource accounts) may not be connected to a single person who can change a password as required. This means a password can expire and leave workers on the spot, not knowing how to resume their work. + If the account is a users personal account, when their password expires, they can easily sign the device back in again. - When your organization requires a password reset or enforces password expiration, be sure a Teams administrator is prepared to reset the password so these shared accounts can sign back in. +2. **Devices fail to sign in due to conditional access policies requiring user interactive multi-factor authentication.** -2. **Devices fail to sign in due to conditional access policies.** + If the account used on a Teams device is subject to Conditional Access policies and the multifactor authentication (MFA) policy is enabled, a Teams resource account won't sign in successfully as it doesn't have a secondary device to approve the MFA request. Teams resource accounts should be secured using alternative second factor authentication such as known network or compliant device. Or if a conditional access policy is enabled to require reauthentication ever X days, the Teams Room on Android or Teams panel device will sign out and require an IT administrator to sign back in every X days. - **Challenge**: Shared devices can't comply with Microsoft Entra Conditional Access policies for user accounts or personal devices. If shared devices are grouped with user accounts or personal devices for a Conditional Access policy, the sign-in will *fail*. + If the account is a users personal account, user interactive MFA can be required for Teams Rooms on Android or Teams panels as the user will have a second device they can approve the authentication request on. - For example, if multifactor authentication is required for accessing Teams, user entry of a code is needed to complete that authentication. Shared devices don't generally have a single user that can configure and complete multifactor authentication. Also, if the account must reauthenticate every X days, a shared device can't resolve the challenge without a user's intervention. ## Best practices for the deployment of shared android devices with Teams Microsoft recommends the following settings when deploying Teams devices in your organization. -### **Use a Resource account and curtail its password expiration** - -Teams shared devices should use an [Exchange resource mailbox](/exchange/recipients-in-exchange-online/manage-resource-mailboxes). Creating these mailboxes generates an account automatically. You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. - -Starting with Teams devices CY21 [Update #1](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones) (Teams version 1449/1.0.94.2021022403 for Teams phones) and [CY2021 Update #2](https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_Rooms_on_Android) (Teams version 1449/1.0.96.2021051904 for Microsoft Teams Rooms on Android), tenant administrators can sign into Teams devices remotely. Instead of sharing passwords with technicians to set up devices, Tenant administrators should use remote sign-in to issue verification codes. You can sign into these devices from the Teams admin center. - -For more information, see [Remote provisioning and sign in for Teams Android devices](/MicrosoftTeams/devices/remote-provision-remote-login). +### Use a Teams Rooms resource account and disable password expiration -### **Review these Conditional Access policies** +Teams shared devices should use a [Teams Rooms resource account](../rooms/create-resource-account.md). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. -Microsoft Entra Conditional Access sets other requirements that devices must meet in order to sign in. For Teams devices, review the guidance that follows to determine if you have authored the policies that allow shared device users to do their work. +### Use remote sign in -> [!TIP] -> For an overview of Conditional Access, see [What is Conditional Access](/azure/active-directory/conditional-access/overview)? +Tenant administrators can sign into Teams Rooms on Android and Teams panels remotely. Instead of sharing passwords with technicians to set up devices, Tenant administrators should use remote sign-in to issue verification codes. You can sign into these devices from the Teams admin center. For more information, see [Remote provisioning and sign in for Teams Android devices](/MicrosoftTeams/devices/remote-provision-remote-login). +### Create a unique Conditional Access policy for resource accounts ->[!TIP] ->Use either [named location](/azure/active-directory/conditional-access/location-condition) or [require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) to secure shared devices. +Microsoft Entra [Conditional Access](/azure/active-directory/conditional-access/overview) sets requirements that devices or accounts must meet in order to sign in. For Teams Rooms resource accounts, we recommend creating a new Conditional Access policy specific to your Teams Rooms resource accounts and then excluding the accounts from all other organization Conditional Access policies. To achieve multifactor authentication (MFA) with shared device accounts, we recommend a combination of known network location and compliant device. -### You can use location-based access with named locations +#### Use location-based access with named locations -If shared devices are provisioned in a well-defined location that can be identified with a range of IP addresses, you can configure Conditional Access using [named locations](/azure/active-directory/conditional-access/location-condition) for these devices. This conditional will allow these devices to access your corporate resources only when they are within your network. +If shared devices are installed in a defined location that can be identified with a range of IP addresses, you can configure Conditional Access using [named locations](/azure/active-directory/conditional-access/location-condition) for these devices. This condition allows these devices to access your corporate resources only when they are within your network. -### When and when not to require compliant shared devices +#### Use compliant devices >[!NOTE] ->Device compliance requires an Intune license. +>Device compliance requires Intune enrollment. -If you're enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant or Microsoft Entra hybrid joined device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). +You can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams devices can be configured for Conditional Access policies based on device compliance. For more information, see [Conditional Access: Require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device). -To set compliance setting for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/intune/protect/device-compliance-get-started). +To set compliance policies for your devices using Intune, see [Use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). ->[!NOTE] -> Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. -> To increase security, you can also [require multi-factor authentication](/azure/active-directory/authentication/tutorial-enable-azure-mfa) for *hot-desking users / user accounts* in addition to the named location policies. - -### Exclude shared devices from sign-in frequency conditions +#### Exclude resource accounts from sign-in frequency conditions -In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for room accounts, shared devices sign out until they're signed in again by an admin. Microsoft recommends excluding shared devices from any sign-in frequency policies. +In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for resource accounts, devices sign out until they're signed in again by an admin. -### Using Filters for devices +#### Using filters for devices -[Filters for devices](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) is a feature in Conditional Access that allows you to configure more granular policies for devices based on device properties available in Microsoft Entra ID. You can also use your own custom values by setting extension attributes 1-15 on the device object and then using those. +For more granular control for what can sign in to Teams using a resource account or for controlling policies for users signing into a Teams Room on Android device with their personal account, device filters can be used. [Filters for devices](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) is a feature in Conditional Access that allows you to configure more granular policies for devices based on device properties available in Microsoft Entra ID. You can also use your own custom values by setting extension attributes 1-15 on the device object and then using those. -Use filters for devices to identify your common-area devices and enable policies in two key scenarios: +Use filters for devices to identify your shared devices and enable policies in two key scenarios: 1. Excluding shared devices from policies applied for personal devices. For example, requiring device compliance *isn't enforced* for shared devices used for hot-desking, but *is enforced* for all other devices, based on model number. -2. Enforcing special policies on shared devices that *shouldn't* be applied to personal devices. For example, requiring named locations as policy only for common-area devices based on an extension attribute you set for these devices (for example: “CommonAreaPhone”). +2. Enforcing special policies on shared devices that *shouldn't* be applied to personal devices. For example, requiring named locations as policy only for common-area devices based on an extension attribute you set for these devices (for example: CommonAreaPhone). >[!NOTE] > Some attributes such as **model**, **manufacturer**, and **operatingSystemVersion** can only be set when devices are managed by Intune. If your devices are not managed by Intune, use extension attributes. -### Microsoft Teams Rooms usage report -New capabilities like the camera video minutes and call minutes data have been added to the Teams Rooms Pro management portal in the report section. This data allows users to track engagement during each meeting and have a better understanding of those data. +## Teams Legacy Authorization + +Teams upgrade configuration policies offer a setting called **BlockLegacyAuthorization** which when enabled prevents Teams Rooms on Android and Teams panels from connecting to Teams services. To learn more about this policy see, [Set-CsTeamsUpgradeConfiguration](/powershell/module/skype/set-csteamsupgradeconfiguration) or run Get-CsTeamsUpgradeConfiguration to check if **BlockLegacyAuthorization** is enabled in your tenant. + + ``` Powershell + Get-CsTeamsUpgradeConfiguration | fl BlockLegacyAuthorization + ``` diff --git a/Teams/devices/certified-device-apps.md b/Teams/devices/certified-device-apps.md index 0013954166..492ebfa71d 100644 --- a/Teams/devices/certified-device-apps.md +++ b/Teams/devices/certified-device-apps.md @@ -48,7 +48,7 @@ The following are supported versions of Teams admin agent app: |**Release date**|**App version**|**Related devices**| |:-----|:-----|:-----| -|October 1, 2024|[1.0.0.202407050618.product](#100202407050618)|All certified Teams device models mentioned here for OEMs - Yealink, Poly & Cisco. | +|October 1, 2024|[1.0.0.202407050618.product](#100202407050618)|All certified Teams device models mentioned here for OEMs - Yealink & Poly.| ### 1.0.0.202407050618 diff --git a/Teams/devices/certified-devices-overview.md b/Teams/devices/certified-devices-overview.md index 0cdb7d8709..47076ff76e 100644 --- a/Teams/devices/certified-devices-overview.md +++ b/Teams/devices/certified-devices-overview.md @@ -29,8 +29,6 @@ Through the Microsoft Teams Device Certification Program, Microsoft tests person This program tests the devices based on a set of rigorous specifications, covering aspects such as audio and video quality, user interface, device management, and security. Only devices that successfully pass all certification requirements, and associated testing receive the designation of **Certified for Microsoft Teams**. -Certification programs are designed to ensure all certified devices run supported versions with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android or Windows version running on the device when it enters into the certification program. Microsoft OEM partners are working to extend the lifetime of the certification by upgrading the Android or Windows version and recertifying, or by releasing new models that are state-of-the-art. - - [Teams Rooms on Windows certified devices](../rooms/certified-hardware.md) - [Teams Rooms on Android certified devices](certified-hardware-android.md) - [Certified Teams panels](teams-panels-certified-hardware.md) diff --git a/Teams/devices/certified-hardware-android.md b/Teams/devices/certified-hardware-android.md index f94738361b..8b26414b1a 100644 --- a/Teams/devices/certified-hardware-android.md +++ b/Teams/devices/certified-hardware-android.md @@ -26,35 +26,17 @@ description: Find lists of certified systems and peripherals for use with Micros # Teams Rooms on Android certified devices -The Microsoft Teams Devices Certification Program ensures certified devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. - ->[!Important] ->The Microsoft Teams Devices Certification Program ensures certified devices meet specific requirements for hardware design and performance only. The certification program doesn't evaluate feature-level or cloud environment support. - -Certified Microsoft Teams Rooms systems are available on both Windows and Android operating systems. Whether you should choose a Teams Rooms system on Windows or Android depends on your specific needs and budget. Select the **Teams Rooms for Windows** and **Teams Rooms for Android** tabs for a complete list of certified systems and links to their respective product sites. For additional certification information specific to **Teams Rooms for Android** see details below. - -For a comparison of features available on each operating system, check out [Teams Rooms on Windows and Android feature comparison](../rooms/teams-devices-feature-comparison.md). - -To see Teams Rooms pricing, see the [Teams Rooms product showcase](https://www.microsoft.com/microsoft-teams/across-devices/devices/category/teams-rooms/20). - -Numerous certified peripherals, from speakers to microphones and cameras, are available for use with Teams Rooms systems. Select the **Peripherals** tab for a complete list of peripherals and links to their respective product sites. - -To see peripherals pricing, see the [Rooms systems accessories product showcase](https://www.microsoft.com/microsoft-teams/across-devices/devices/category/room-systems-accessories/73). - -## Teams Rooms for Android certification program - -> [!Important] -> The following information pertains to **Teams Rooms for Android** only. -> For additional Android based devices that are Microsoft certified, please visit [Microsoft Teams certified Android devices](/microsoftteams/devices/teams-ip-phones). +The Microsoft Teams devices Certification Program ensures devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Our OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. -After certification end date, Microsoft is committed to making efforts to support the most recent version of the Teams client on such devices for two years following the end of the certification period. +Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. + +We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. -> [!Note] -> Certification end dates are based on the Android version release date plus five years. Once the device passes the certification requirements and OEM partners provide the firmware that enables the upgrade to a newer Android version, the certification end date will be extended to match the new Android OS version release date plus five years. +Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, these changes will be communicated through the established customer facing communication channels. ## [Teams Rooms for Android](#tab/Android) @@ -65,10 +47,9 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | Device model | Firmware version | Current certification end date | Room size | Android OS version | |:-|:-|:-|:-|:-| -| Poly Studio X72 | `PolyOS 4.2.5`| September 3, 2025 | Large rooms (4.5 m x 8.5 m) | 10 | -| AudioCodes RXV200 | `2.2.335` | September 3, 2025 | Focus room(3 m x 3 m) | 10 | -| Audiocodes RXPad Touch console | `2.0.282` | August 15, 2027 | Compatible with Audiocodes RXV81 and RXV200 Collaboration bars. | 12 | -| Audiocodes RXV81 Collaboration Bar | `2.0.0` | August 15, 2027 | Small meeting room (4.5 m x 4.5 m) | 12 | +| AudioCodes RXV200 | `2.2.335` | September 3, 2025 | Focus room (3 m x 3 m) | 10 | +| AudioCodes RXPad Touch console | `2.0.282` | August 15, 2027 | Compatible with AudioCodes RXV81 and RXV200 Collaboration bars. | 12 | +| AudioCodes RXV81 Collaboration Bar | `2.0.0` | August 15, 2027 | Small meeting room (4.5 m x 4.5 m) | 12 | | Cisco Room Bar Pro | `RoomOS11.9` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 11 | | Cisco Board Pro 55 | `11.3.1.13` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 11 | | Cisco Board Pro 75 | `11.3.1.13` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 11 | @@ -83,27 +64,32 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | Crestron AIO Video Bar 70 | `1.240618.1240` | September 3, 2025 | Large meeting room (4.5 m x 8.5 m) | 10| | Crestron Touch Panel TS-1070 | `2.005.1030` | September 3, 2025 | Compatible with Crestron AIO Video Bar 70 | 10 | | DTEN Bar | `1.0.2` | August 15, 2027| Small size room (4.5 m x 4.5 m) | 12 | +| DTEN D7X 55" + Vue Pro | `1.5.8` |August 15, 2027| Small size room (4.5 m x 4.5 m) | 12 | +| DTEN D7X 55" + Vue | `1.5.8` |August 15, 2027| Small size room (4.5 m x 4.5 m) | 12 | | DTEN D7X 75" + Vue Pro | `1.5.8` |August 15, 2027| Medium size room (4.5 m x 6 m) | 12 | | DTEN D7X 75" + Vue | `1.5.8` |August 15, 2027| Medium size room (4.5 m x 6 m) | 12 | | DTEN D7X 75" | `1.2.8` | August 15, 2027 | Medium size room (4.5 m x 6 m) | 12 | -| DTEN Mate Touch Console | `2.0.2.0` | Septmber 3, 2025 | Compatible with DTEN DCR200 Bar, DTEN D7X 55" and DTEN D7X 75" Meeting Board | 10 | +| DTEN Mate Touch Console | `2.0.2.0` | September 3, 2025 | Compatible with DTEN DCR200 Bar, DTEN D7X 55" and DTEN D7X 75" Meeting Board | 10 | | DTEN D7X 55" | `1.2.2` |August 15, 2027| Small meeting room (4.5 m x 4.5 m) | 12 | +| DTEN Bar + Vue | `1.3.0` | October 4, 2026 | Small Meeting Room (4.5 m x 4.5 m) | 12 | +| DTEN Bar + Vue Pro | `1.3.0` | October 4, 2026 | Small Meeting Room (4.5 m x 4.5 m) | 12 | | EPOS Expand 5T | `1.2.22362.04` | September 3, 2025 | Small meeting room (4.5 m x 4.5 m) | 10 | | EPOS EXPAND Control Touch Console | `1.2.22250.08` | September 3, 2025 | Compatible with EPOS Expand 5T Collaboration Bar. | 10 | -| :::no-loc text="Jabra"::: :::no-loc text="Panacast"::: 50 VBS | `1.1.0-1` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | -| :::no-loc text="Jabra"::: :::no-loc text="Panacast"::: 50 Touch Console | `1.1.0-1` | September 3, 2025 | Compatible with :::no-loc text="Jabra"::: :::no-loc text="Panacast"::: 50 VBS | 10 | +| Jabra PanaCast 50 VBS | `1.1.0-1` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | +| Jabra PanaCast 50 Touch Console | `1.1.0-1` | September 3, 2025 | Compatible with Jabra PanaCast 50 VBS | 10 | | Logitech Rally Bar Huddle (VR0034) | `0.903.73` | September 3, 2025 | Focus room(3 m x 3 m) | 11 | | Logitech Tap IP (VR0029) | `1.6.565` | September 3, 2025 | Compatible with Logitech RoomMate, Rally Bar, and Rally Bar Mini | 10 | | Logitech Roommate (VR0030) | `1.4.71` | September 3, 2025 | Large meeting room (4.5 m x 8.5 m) | 10 | -| Logitech Tap USB Touch Console | `1.2.982` | September 3, 2025 | Compatible with Logitech Rally Bar, Rally Bar Mini and Roommate | 10 | +| Logitech Tap USB Touch Console | `1.2.982` | September 3, 2025 | Compatible with Logitech Rally Bar, Rally Bar Mini, and Roommate | 10 | | Logitech Rally Bar Mini (VR0020) | `1.2.982` | September 3, 2025 | Small Meeting Room (4.5 m x 4.5 m) | 10 | | Logitech Rally Bar (VR0019) | `1.2.788` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Neat Bar Pro | `NFD1.20220914.1210` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Neat Bar | `NFF1.20220914.1210` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | -| Neat Pad Touch Console | `NFA1.20230928.0108` | September 3, 2025 | Compatible with Neat Bar Gen 2, Neat Bar, Neat Bar Pro, Neat Board 50 & Neat Board | 10 | +| Neat Pad Touch Console | `NFA1.20230928.0108` | September 3, 2025 | Compatible with Neat Bar Gen 2, Neat Bar, Neat Bar Pro, Neat Board 50, Neat Board & Neat Board Pro 65 | 10 | | Neat Board | `NFC1.20220914.1210` | September 3, 2025 | Small Meeting Room (4.5 m x 4.5 m) | 10 | | Neat Board 50 |`NFH1.20230824.0001` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Neat Bar Gen2 | `NFA1.20231116.0626 ` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | +| Neat Board Pro 65 | `NFK1.20240620.0209` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Poly Studio X30 | `4.0.0.100885` | September 3, 2025 | Small meeting room(4.5 m x 4.5 m) | 10 | | Poly Studio X50 | `4.0.0.100885` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Poly Studio X70 | `4.0.0-376092` | September 3, 2025 | Large meeting room (4.5 m x 8.5 m) | 10 | @@ -113,6 +99,7 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | Poly Studio X52 | `4.1.0.382110` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10 | | Poly G7500 + Shure Large Room Kit | `4.0.1` | September 3, 2025 | Large meeting room (4.5 m x 8.5 m) | 10 | | Poly G62 | `PolyOS 4.1.5` | September 3, 2025 | Large meeting room (4.5 m x 8.5 m) | 10 | +| Poly Studio X72 | `PolyOS 4.2.5`| September 3, 2025 | Large rooms (4.5 m x 8.5 m) | 10 | | Yealink DeskVision A24 | `156.15.0.29` | September 3, 2025 | Phone room (2 m x 2 m) | 10 | | Yealink CTP18 touch console | `137.320.0.29` | September 3, 2025 | Compatible with Yealink MeetingBar A20 and Yealink MeetingBar A30 | 10 | | Yealink MeetingBar A10 | `278.15.0.6` | September 3, 2025 | Small meeting room (4.5 m x 4.5 m) | 11 | @@ -123,6 +110,7 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | Yealink CTP25 touch console | `311.320.0.2` | August 15, 2027 | Compatible with Yealink MeetingBar A40 | 13 | | Yealink MeetingBar A40 | `289.320.0.11` | August 15, 2027 | Medium size room (4.5 m x 6 m) | 13 | | Yealink MeetingBoard 65"/86" with MB-Camera-6X | `155.15.0.37 ` | September 3, 2025 | Medium size room (4.5 m x 6 m) | 10| +| Yealink MeetingBoard 75 Pro | `300.320.0.7 ` | August 15, 2027 | Medium size room (4.5 m x 6 m) | 13| ## [Firmware](#tab/firmware) @@ -136,6 +124,9 @@ 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 | |:-------------------|:----------------------------|:--------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Audiocodes RXV81 | `2.6.280` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202407050618.product` | October 18, 2024| +| Audiocodes RX-Pad | `2.6.280` | N/A | `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202407050618.product` | October 18, 2024| +| Audiocodes RXV200 | `2.6.280` | N/A | `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202407050618.product` | October 18, 2024| | Audiocodes RXV81 | `2.6.228` | N/A| `1449/1.0.96.2024061103` | `5.0.6152.0`| `1.0.0.202402202353.product` | September 4, 2024| | Audiocodes RX-Pad | `2.6.228` | N/A | `1449/1.0.96.2024061103` | `5.0.6152.0`| `1.0.0.202402202353.product` | September 4, 2024| | Audiocodes RXV200 | `2.6.228` | N/A | `1449/1.0.96.2024061103` | `5.0.6152.0`| `1.0.0.202402202353.product` | September 4, 2024| @@ -161,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.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| +| Cisco Room Kit Pro | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product`| November 4, 2024| +| Cisco Desk Pro | `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 Pro | `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 Kit EQ | `ce11.21.1.8` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202407050618.product` | November 4, 2024| +| Cisco Navigator | `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 Kit EQX | `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 G2 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 G2 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 Board Pro 55 | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 26, 2024| | Cisco Board Pro 75 | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 26, 2024| | Cisco Room Bar | `11.18.1.8` | N/A | `1449/1.0.96.2024061103` | `5.0.6061.0` | `1.0.0.202402202353.product` | August 26, 2024| @@ -236,11 +238,23 @@ For information about the latest Teams app releases, see [What's new in Microsof | Cisco Board Pro 55 | `11.3.1.16` | N/A | `1449/1.0.96.2023010302` | `5.0.5484.0` | `1.0.0.202209060820.product` | March 30, 2023 | | Cisco Board Pro 75 | `11.3.1.16` | N/A | `1449/1.0.96.2023010302` | `5.0.5484.0` | `1.0.0.202209060820.product` | March 30, 2023 | +#### Crestron + +| Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | +|:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Crestron AIO Video Bar 70 | `1.240912.1415` | N/A | `1449/1.0.96.2024080804 ` | `5.0.6152.0` | `1.0.0.202402202353.product`| November 11, 2024 | +| Crestron Touch Panel TS-1070 | `2.005.1054.001` | N/A | `1449/1.0.96.2024080804 ` | `5.0.6152.0` | `1.0.0.202402202353.product`| November 11, 2024 | #### DTEN | Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| DTEN Bar |`1.3.2.0` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| November 21, 2024| +| DTEN Mate Touch Console | `2.3.2.1` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| November 21, 2024| +| DTEN Bar |`1.3.1.1` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| October 15, 2024| +| DTEN D7X 75" |`1.6.6.1` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| October 15, 2024| +| DTEN D7X 55" |`1.6.6.1` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| October 15, 2024| +| DTEN Mate Touch Console | `2.3.1.2` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| October 15, 2024| | DTEN Bar |`1.3.0.4` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| September 20, 2024| | DTEN D7X 75" |`1.6.5.4` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| September 20, 2024| | DTEN D7X 55" |`1.6.5.4` | N/A| `1449/1.0.96.2024080804` | `5.0.6152.0`| `1.0.0.202402202353.product`| September 20, 2024| @@ -296,6 +310,11 @@ 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 | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Logi Rallybar (VR0019) | `1.13.127` | N/A | `1449/1.0.96.2024042606` | `5.0.6152.0`| `1.0.0.202402202353.product` | October 3, 2024| +| Logi Rallybar Mini (VR0020) | `1.13.127` | N/A | `1449/1.0.96.2024042606` | `5.0.6152.0`| `1.0.0.202402202353.product` | October 3, 2024| +| Logi RoomMate (VR0030) | `1.13.124` | N/A | `1449/1.0.96.2024042606` | `5.0.6152.0`| `1.0.0.202402202353.product` | October 3, 2024| +| Logi Rallybar Huddle (VR0034) | `1.13.121` | N/A | `1449/1.0.96.2024042606` | `5.0.6152.0`| `1.0.0.202402202353.product` | October 3, 2024| +| Logi TAP IP (VR0029) | `1.13.124`| N/A | `1449/1.0.96.2024042606` | `5.0.6152.0`| `1.0.0.202402202353.product` | October 3, 2024| | Logi Rallybar (VR0019) | `1.12.268` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 21, 2024| | Logi Rallybar Mini (VR0020) | `1.12.268` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 21, 2024| | Logi Rallybar (VR0019) | `1.12.264` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | July 2, 2024| @@ -346,6 +365,13 @@ 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 | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Neat Bar Gen2 | `NFE1.20240924.0005 ` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Bar | `NFB1.20240924.0005` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Bar Pro| `NFD1.20240924.0007` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Board | `NFC1.20240924.0005` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Board 50 | `NFH1.20240924.0005` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Pad touch console | `NFA1.20240924.0507` | N/A | `1449/1.0.96.2024091202`| `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| +| Neat Board Pro 65 | `NFK1.20240924.0007` | N/A | `1449/1.0.96.2024091202` | `5.0.6152.0` | `1.0.0.202402202353.product`| November 13, 2024| | Neat Bar Gen2 | `NFE1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| August 23, 2024| | Neat Bar | `NFB1.20240620.0015` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| August 23, 2024| | Neat Bar Pro| `NFD1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| August 23, 2024| @@ -393,6 +419,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 | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| Poly Studio X30 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly Studio X50 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly Studio X52 | `4.3.2.422023` |`N/A` |`1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly Studio X70 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly Studio X72 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| November 11, 2024| +| Poly Studio G7500 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly Studio G62 | `4.3.2.422023` | `N/A`| `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly TC8 | `6.3.2.211744` | N/A | `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| +| Poly TC10 | `6.3.2.211744` | N/A | `1449/1.0.96.2024080804`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 10, 2024| | Poly Studio X30 | `4.2.2-408037` | `4.1.0_00.180034`| `1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| June 21, 2024| | Poly Studio X50 | `4.2.2-408037` | `4.1.0_00.180034`| `1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| June 21, 2024| | Poly Studio X52 | `4.2.2-408037` |`4.1.0.382189` |`1449/1.0.96.2024020802`| `5.0.6061.0` | `1.0.0.202310260109.product`| June 21, 2024| @@ -535,16 +570,41 @@ 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 | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:-----------------| -| Logi Rallybar (VR0019) | `1.12.264` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| -| Logi Rallybar Mini (VR0020) | `1.12.264` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| -| Logi RoomMate (VR0030) | `1.12.240` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| -| Logi Rallybar Huddle (VR0034) | `1.12.135` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| -| Logi TAP IP (VR0029) | `1.12.184`| N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| +| Logi Rallybar (VR0019) | `1.12.268` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | October 7, 2024| GCCH| +| Logi Rallybar Mini (VR0020) | `1.12.268` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | October 7, 2024| GCCH| +| Logi Rallybar (VR0019) | `1.12.264` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| GCCH| +| Logi Rallybar Mini (VR0020) | `1.12.264` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| GCCH| +| Logi RoomMate (VR0030) | `1.12.240` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| GCCH| +| Logi Rallybar Huddle (VR0034) | `1.12.135` | N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| GCCH| +| Logi TAP IP (VR0029) | `1.12.184`| N/A | `1449/1.0.96.2024042606` | `5.0.5484.0`| `1.0.0.202402202353.product` | August 23, 2024| GCCH| | Logi RoomMate (VR0030) | `1.11.215` | N/A | `1449/1.0.96.2023062301` | `5.0.5484.0`| `1.0.0.202306202019.product` | February 20, 2024| GCCH| | Logi TAP IP (VR0029) | `1.11.202`| N/A | `1449/1.0.96.2023062301` | `5.0.5484.0`| `1.0.0.202306202019.product` | February 20, 2024| GCCH| | Logi RoomMate (VR0030) | `1.10.175` | N/A | `1449/1.0.96.2023062301` | `5.0.5484.0`| `1.0.0.202306202019.product` | February 2, 2023| GCCH| | Logi TAP IP (VR0029) | `1.10.129` | N/A | `1449/1.0.96.2023062301` | `5.0.5484.0`| `1.0.0.202306202019.product` | February 2, 2023| GCCH| +#### Neat + +| Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | Cloud | +|:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:---------------------------------| +| Neat Bar Gen2 | `NFE1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Bar | `NFB1.20240620.0015` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Bar Pro| `NFD1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Board | `NFC1.20240620.0015` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Board 50 | `NFH1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Pad touch console | `NFA1.20240620.1740` | N/A | `1449/1.0.96.2024061103`| `5.0.6061.0` | `1.0.0.202402202353.product`| October 7, 2024| GCCH | +| Neat Bar Gen2 | `NFE1.20240516.0009` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Bar | `NFB1.20240516.0658` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Bar Pro| `NFD1.20240516.0007` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Board | `NFC1.20240516.0658` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Board 50 | `NFH1.20240516.0007` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Pad touch console | `NFA1.20240516.0501` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | +| Neat Bar Gen2 | `NFE1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | +| Neat Bar | `NFB1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | +| Neat Bar Pro| `NFD1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | +| Neat Board | `NFC1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | +| Neat Board 50 | `NFH1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | +| Neat Pad touch console | `NFA1.20240312.0503` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | + #### HP | Poly | Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | Cloud | @@ -576,32 +636,9 @@ For information about the latest Teams app releases, see [What's new in Microsof | Poly Studio G7500 | `4.0.2.384012` | N/A | `5.0.5484.0` | `1449/1.0.96.2023031201`| `1.0.0.202301162118.product` | June 16, 2023 | GCCH | | Poly TC8 | `4.0.2.211096` | N/A | `5.0.5484.0` | `1449/1.0.96.2023031201`| `1.0.0.202301162118.product` | June 16, 2023 | GCCH | -#### Neat - -| Device model | Latest Firmware version | Minimum Firmware version required | Teams client | Company Portal | Admin Agent | Release date | Cloud | -|:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------|:---------------------------------| -| Neat Bar Gen2 | `NFE1.20240516.0009` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Bar | `NFB1.20240516.0658` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Bar Pro| `NFD1.20240516.0007` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Board | `NFC1.20240516.0658` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Board 50 | `NFH1.20240516.0007` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Pad touch console | `NFA1.20240516.0501` | N/A | `1449/1.0.96.2024042606`| `5.0.6061.0` | `1.0.0.202402202353.product`| July 6, 2024| GCCH | -| Neat Bar Gen2 | `NFE1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | -| Neat Bar | `NFB1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | -| Neat Bar Pro| `NFD1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | -| Neat Board | `NFC1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | -| Neat Board 50 | `NFH1.20240312.0005` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | -| Neat Pad touch console | `NFA1.20240312.0503` | N/A | `1449/1.0.96.2024032804`| `5.0.6061.0` | `1.0.0.202310260109.product`| April 30, 2024| GCCH | - ## [End of certification](#tab/eol) -Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. - -We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. - -Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, they will be communicated through the established customer facing communication channels. - -| Device Category | Device Model | Android OS Versio | Certification end date | Microsoft support end date | +| Device Category | Device Model | Android OS Version | Certification end date | Microsoft support end date | |:----------------|:-------------------|:----------------------------|:--------------------------|:----------------------| |Teams Rooms for Android | Yealink VC210 | 9 | August 5, 2023 | August 5, 2025 | -|Teams Rooms for Android | EPOS Expand Vision 3T | 9 | August 5, 2023| August 5, 2025 | \ No newline at end of file +|Teams Rooms for Android | EPOS Expand Vision 3T | 9 | August 5, 2023| August 5, 2025 | diff --git a/Teams/devices/check-in-and-auto-release.md b/Teams/devices/check-in-and-auto-release.md index 213b0208dc..4272f851ac 100644 --- a/Teams/devices/check-in-and-auto-release.md +++ b/Teams/devices/check-in-and-auto-release.md @@ -76,6 +76,10 @@ To turn on check-in notifications, **Answer:** Yes, there are. At this time, the user will be automatically checked in if the room is the organizer of the meeting, the room was invited after the meeting start time, it's a 3P meeting such as Zoom meeting, or it's an in-person meeting as in there is no online Teams link. We'll be requiring check-in for 3P and in-person meetings in the future. +**Question: Does this feature support on-premises mailboxes?** + +**Answer:** No, this feature is only available for room mailboxes created in Exchange Online after Teams app 1449/1.0.97.2024061108. To learn more about how to manage room mailboxes, see [Manage resource mailboxes in Exchange Online](/exchange/recipients-in-exchange-online/manage-resource-mailboxes). + ## Related topics - [How to use Microsoft Teams panels](use-teams-panels.md) diff --git a/Teams/devices/collab-bar-deploy.md b/Teams/devices/collab-bar-deploy.md deleted file mode 100644 index 2668eb4239..0000000000 --- a/Teams/devices/collab-bar-deploy.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Deploy Microsoft Teams Rooms on Android -author: mstonysmith -ms.author: tonysmit -manager: pamgreen -ms.reviewer: tjaved -ms.date: 08/21/2024 -ms.topic: article -ms.service: msteams -ms.subservice: itpro-devices -audience: Admin -appliesto: - - Microsoft Teams -ms.collection: - - teams-rooms-devices - - M365-collaboration - - Teams_ITAdmin_Devices - - Tier1 -f1.keywords: - - NOCSH -ms.localizationpriority: medium -ms.assetid: 678689e4-d547-499b-be64-7d8f16dd8668 -description: Read this article to learn about deploying Microsoft Teams Rooms on Android. ---- - -# Deploy Microsoft Teams Rooms on Android - -Deployment of Microsoft Teams Rooms on Android can be broken down into the following phases: - -- **Site readiness** - Confirm that your deployment locations (rooms) meet the deployment requirements. -- **Service readiness** - Create resource accounts and assign them to the devices. (See [Create a resource account using the Microsoft 365 admin center](resource-account-ui.md).) -- **Configuration and deployment** - Set up Teams Rooms and connect the peripheral devices you need. (See the manufacturer's documentation for details.) - -To manage Teams Rooms, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](../using-admin-roles.md). - -> [IMPORTANT] -> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. - -## Site readiness - -While the ordered devices are being delivered to your organization, work with your networking, facilities, and audio-visual teams to make sure that deployment requirements are met and each site and room is ready in terms of power, networking, and display. - -Our recommendations for Teams Rooms on Android sites are: -- Dedicated resource accounts -- Touch-enabled displays -- Ethernet cabling -- Quality of Service (QoS) enabled on the network for Microsoft Teams media - -For physical installation considerations, see the manufacturer's documentation and, if you have one, leverage the experience of your audio-visual team before you install and mount screens and run cabling. - -> [!TIP] -> Be sure to check out [Prepare your network for Teams](../prepare-network.md) for bandwidth planning and assessing your network’s suitability for real-time traffic. -> -> We don't recommend placing proxy servers between Teams devices and the Internet. For more information about proxy servers and Teams, check out [Proxy servers for Teams](../proxy-servers-for-skype-for-business-online.md). - -| | | -|-----------|------------| -| ![An icon depicting decision points.](../media/audio_conferencing_image7.png)
Decision points|
  • Confirm that your sites meet the site readiness requirements for Teams Rooms on Android.
  • Confirm that you've provided sufficient bandwidth for each site.
| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|
  • Start to plan your Teams Rooms on Android deployment and configuration.
| - -## Service readiness - -Before you deploy Teams Rooms, you need to decide if they'll use Microsoft 365 resource accounts, end-user accounts, or a mixture of both. Microsoft 365 resource accounts are mailbox and Teams accounts that are dedicated to specific resources, such as a room, projector, and so on. These resource accounts can automatically respond to meeting invites using rules you define when they're created. Unless Teams Rooms is dedicated to a specific individual for their private use, we recommend setting up a Microsoft 365 resource account for it. - -### Using a resource account - -To set up a Microsoft 365 resource account, you'll need to purchase a Meeting Room license for it. The Meeting Room license includes a resource mailbox that enables people in your organization to book the meeting room via Outlook or Teams. The license also enables video and audio conferencing and screen sharing among meeting participants. - -If you need to receive or make calls to or from an external telephone number, you may need a Calling Plan or Microsoft 365 Business Voice [add-on license](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md?tabs=small-business). If you have Direct Routing enabled in your organization, you only need the Meeting Room Pro SKU. - -When you create a resource account, you can choose whether to let the account automatically accept or decline meeting requests, allow recurring meetings, specify how far in advance people can book the resource, and so on. - -[!INCLUDE [m365-teams-resource-account-difference](../includes/m365-teams-resource-account-difference.md)] - -For more information about Microsoft 365 resource accounts, see [Create a resource account using the Microsoft 365 admin center](resource-account-ui.md). - -| | | -|-----------|------------| -| ![An icon depicting decision points.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide whether you want to make or receive external phone calls and identify licensing requirements for your resource accounts.
| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|
  • Prepare resource accounts.
| - -## Configuration and deployment - -Planning for configuration and deployment covers the following key areas: - -- Resource account provisioning -- Device deployment -- Teams Rooms application and peripheral device configuration -- Testing -- Asset management - -### Account provisioning - -If you plan on using Microsoft 365 resource accounts to let users book Teams Rooms on Android devices, follow the instructions in [Create a resource account using the Microsoft 365 admin center](resource-account-ui.md) to create a Microsoft 365 resource account for each Teams Rooms on Android device that needs one. This is also where you'll need to add a Meeting Room license to the resource account and, if you want to make or receive calls to or from external phone numbers, a Calling Plan or Business Voice license if your organization is not using Direct Routing. - -> [!TIP] -> Make the display names for your Microsoft 365 resource accounts descriptive and easy to understand. These are the names that users will see when searching for and adding Teams Rooms to meetings. You could use a convention like *Site*-*Room Name*(*Max Room Capacity*), so for example Curie, a 4-person meeting room in London, might have the display name LON-CURIE(4). - -| | | -|-----------|------------| -| ![An icon depicting decision points.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide the naming convention for your dedicated resource accounts.
  • Decide whether you’ll create individual accounts or use bulk-provisioning scripts.
| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|
  • Start to plan your device deployment.
| - -### Device deployment - -Next, you need to create your plan to deliver the devices and their assigned peripheral devices to your rooms, and then proceed with installation and configuration. - -| | | -|-----------|------------| -| ![An icon depicting decision points.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide who will manage the site-by-site deployment.
  • Identify the resources who will install Teams Rooms on site and undertake the configuration and testing.
| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|
  • Start device testing.
| - -### Testing - -After you have deployed Teams Rooms, you should test them. Sign in to Teams Rooms and check that the expected capabilities are working. We highly recommend that you verify that they appear in the **Teams Rooms on Android** section under the **Teams Devices** tab of Microsoft Teams admin center. It's also important that you make a number of test calls and meetings to check quality and performance. - -We recommend that as part of the general Microsoft Teams rollout, you configure building files for Call Quality Dashboard (CQD), monitor quality trends, and engage in the Quality of Experience Review process. For more information, see the [Quality of Experience Review Guide](../quality-of-experience-review-guide.md). - -### Asset management - -As part of the deployment, you'll want to update your asset register with the room name, signed-in resource account, and assigned peripheral devices. - -## Related topics - -[Create resource accounts for rooms and shared Teams devices](../rooms/create-resource-account.md) - - diff --git a/Teams/devices/custom-names.md b/Teams/devices/custom-names.md new file mode 100644 index 0000000000..98ac1808a2 --- /dev/null +++ b/Teams/devices/custom-names.md @@ -0,0 +1,63 @@ +--- +title: Add a custom name for Teams panels +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: eviegrimshaw +ms.date: 11/18/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +search.appverid: MET150 +ms.localizationpriority: medium +description: This article provides the information required when you want to add in a custom name for a Microsoft Teams panel. +--- + +# Add a custom name for Teams panels + +## Heading 2 + +insert text + +### Heading 3 + +insert text + +#### Heading 4 + +**Bold text** + +*italic text* + +Numbered list: +1. +2. +3. +4. + +Bulleted list: +- +- +- +- + +> [!IMPORTANT] +> Important note. + +> [!NOTE] +> Normal note. + +## Related articles + +- [Insert link text](/powershell/module/teams/new-csteamsipphonepolicy) +- [Plan for Teams panels](/microsoftteams/devices/teams-panels) +- [Certified Teams panels](teams-panels-certified-hardware.md) \ No newline at end of file diff --git a/Teams/media/edit-filter.png b/Teams/devices/media/edit-filter.png similarity index 100% rename from Teams/media/edit-filter.png rename to Teams/devices/media/edit-filter.png diff --git a/Teams/media/exclude-attribute-set.png b/Teams/devices/media/exclude-attribute-set.png similarity index 100% rename from Teams/media/exclude-attribute-set.png rename to Teams/devices/media/exclude-attribute-set.png diff --git a/Teams/media/include-all-apps-settings.png b/Teams/devices/media/include-all-apps-settings.png similarity index 100% rename from Teams/media/include-all-apps-settings.png rename to Teams/devices/media/include-all-apps-settings.png diff --git a/Teams/media/powershell-output-expected.png b/Teams/devices/media/powershell-output-expected.png similarity index 100% rename from Teams/media/powershell-output-expected.png rename to Teams/devices/media/powershell-output-expected.png diff --git a/Teams/media/require-mfa-selection.png b/Teams/devices/media/require-mfa-selection.png similarity index 100% rename from Teams/media/require-mfa-selection.png rename to Teams/devices/media/require-mfa-selection.png diff --git a/Teams/devices/phones-panels-deploy.md b/Teams/devices/mtra-panels-deploy.md similarity index 80% rename from Teams/devices/phones-panels-deploy.md rename to Teams/devices/mtra-panels-deploy.md index cad1ac9dce..a29ba6ccab 100644 --- a/Teams/devices/phones-panels-deploy.md +++ b/Teams/devices/mtra-panels-deploy.md @@ -1,10 +1,10 @@ --- -title: Deploy Teams Phones, Teams panels, and Microsoft Teams Rooms on Android using Intune +title: Deploy Teams Rooms on Android and Teams panels author: mstonysmith ms.author: tonysmit manager: pamgreen -ms.date: 04/25/2024 -ms.reviewer: prashibadkur +ms.date: 10/16/2024 +ms.reviewer: eviegrimshaw ms.topic: article ms.service: msteams ms.subservice: itpro-devices @@ -20,16 +20,16 @@ ms.collection: - Tier1 search.appverid: MET150 ms.localizationpriority: medium -description: This article provides an overview of and features supported by Microsoft Teams Android devices. +description: This article gives you an overview of how to deploy Teams panels, and Microsoft Teams Rooms on Android using Conditional Access and Intune. --- -# Deploy Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android using Intune +# Deploy Teams panels and Microsoft Teams Rooms on Android using Intune -This article gives you an overview of how to deploy Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android using Intune. +This article gives you an overview of how to deploy Teams panels and Microsoft Teams Rooms on Android using Conditional Access and Intune. ## Conditional Access -Conditional Access is a Microsoft Entra feature that helps you to ensure devices accessing your Office 365 resources are properly managed and secure. If you apply Conditional Access policies to the Teams service, all devices including Teams Phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android need to be enrolled into Intune and their settings need to comply with your organizational policies. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents a user from signing in or using the Teams app on the device. +Conditional Access is a Microsoft Entra feature that helps you to ensure devices accessing your Office 365 resources are properly managed and secure. If you apply Conditional Access policies to the Teams service, all devices including Teams phones, Teams displays, Teams panels, and Microsoft Teams Rooms on Android need to be enrolled into Intune and their settings need to comply with your organizational policies. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents a user from signing in or using the Teams app on the device. Typically, compliance policies defined within Intune are assigned to groups of users. This means that if you assign an Android compliance policy to user@contoso.com, that policy applies equally to their Android smartphone and to any Android-based Teams device that user@contoso.com signs into. @@ -38,9 +38,11 @@ If you use Conditional Access, which requires Intune enrollment to be enforced, - **Intune license** The user signing into the Teams device must be licensed for Intune. As long as the Teams device is signed in to a user account that has a valid Intune license, the device is automatically enrolled in Microsoft Intune as part of the sign in process. - **Configure Intune** You must have a properly configured Intune tenant set up for Android Device Administrator enrollment. +Teams Android-based devices including Teams panels and Teams Rooms on Android are managed by Intune using Android Device Administrator (DA) management. + ## Configure Intune to enroll Teams Android-based devices -Teams Android-based devices are managed by Intune via Android Device Administrator (DA) management. Customers must enroll their devices using Android Device Administrator. Before devices can be enrolled into Intune, there are a few basic steps to perform. If you're already managing devices with Intune today, you probably have already done all these things. If not, here's what to do: +Customers must enroll their devices using Android Device Administrator. Before devices can be enrolled into Intune, there are a few basic steps to perform. If you're already managing devices with Intune today, you probably have already done all these things. If not, here's what to do: > [!NOTE] > - If tenant admins want common area phones to be enrolled into Intune, they need to add an Intune license to the account and follow the steps for Intune enrollment. diff --git a/Teams/devices/smartvision-admin.md b/Teams/devices/multistream-intelliframe.md similarity index 100% rename from Teams/devices/smartvision-admin.md rename to Teams/devices/multistream-intelliframe.md diff --git a/Teams/devices/qos-on-teams-devices.md b/Teams/devices/qos-on-teams-devices.md index 97ee4b458e..24ee0b1e8a 100644 --- a/Teams/devices/qos-on-teams-devices.md +++ b/Teams/devices/qos-on-teams-devices.md @@ -32,7 +32,7 @@ This article explains: 1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-rooms-bandwidth-usage) 1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-rooms) -Wired network connectivity is recommended for Microsoft Teams Rooms devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-plan.md#wireless-network-considerations). +Wired network connectivity is recommended for Microsoft Teams Rooms devices. If wireless network connectivity is the only option, see best practice guidance [here](../rooms/rooms-prep.md#wireless-network-considerations). ## How much bandwidth does a Microsoft Teams Rooms device use? diff --git a/Teams/devices/remote-sign-in-and-sign-out.md b/Teams/devices/remote-sign-in-and-sign-out.md index f740ea40ac..66649e350f 100644 --- a/Teams/devices/remote-sign-in-and-sign-out.md +++ b/Teams/devices/remote-sign-in-and-sign-out.md @@ -1,5 +1,5 @@ --- -title: Remote sign in and sign out for Teams Android devices +title: Remotely sign in and sign out for Teams Android devices author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -22,7 +22,7 @@ search.appverid: MET150 description: Learn how to remotely sign in and sign out of Teams Android devices. --- -# Remote sign in and sign out for Teams Android devices +# Remotely sign in and sign out for Teams Android devices This article describes how to remote sign in and sign out Teams Android devices from the Teams admin center. If you haven't provisioned a device yet, or the device is provisioned but has never been signed-in, see [Remote provisioning and sign in for Teams Android devices](remote-provision-remote-login.md). diff --git a/Teams/sip-gateway-configure.md b/Teams/devices/sip-gateway-configure.md similarity index 90% rename from Teams/sip-gateway-configure.md rename to Teams/devices/sip-gateway-configure.md index bbfe6f8129..7b07bba865 100644 --- a/Teams/sip-gateway-configure.md +++ b/Teams/devices/sip-gateway-configure.md @@ -128,15 +128,15 @@ Conditional Access is a Microsoft Entra feature that helps ensure that devices t 1. Exclude your site public IP addresses and the following SIP Gateway service IP addresses from Conditional Access checks: -- North America: - - East US: 52.170.38.140 - - West US: 40.112.144.212 -- EMEA region: - - North EU: 40.112.71.149 - - West EU: 40.113.112.67 -- APAC region: - - Australia East: 20.92.120.71 - - Australia Southeast: 13.73.115.90 + - North America: + - East US: 52.170.38.140 + - West US: 40.112.144.212 + - EMEA region: + - North EU: 40.112.71.149 + - West EU: 40.113.112.67 + - APAC region: + - Australia East: 20.92.120.71 + - Australia Southeast: 13.73.115.90 2. Exclude the Teams app from Conditional Access checks. @@ -259,21 +259,21 @@ Bulk sign-in is very helpful and can be used in these scenarios. 1. You must add your site public IP address or ranges to the [trusted IPs for the tenant](/microsoftteams/manage-your-network-topology) in Teams admin center at least 24 hours prior to running the bulk sign in cmdlets. 2. You must add your organization's tenant ID to the provisioning URL for the devices. - > [!NOTE] - > The examples below are for the North America region. + > [!NOTE] + > The examples below are for the North America region. -- For Alcatel-Lucent Enterprise, AudioCodes, and Yealink IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid/` -- For Cisco IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//$PSN.xml` -- For analog devices that connect to AudioCodes ATAs use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//mac.ini` + - For Alcatel-Lucent Enterprise, AudioCodes, and Yealink IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid/` + - For Cisco IP phones use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//$PSN.xml` + - For analog devices that connect to AudioCodes ATAs use: `http://noam.ipp.sdg.teams.microsoft.com/tenantid//mac.ini` - > [!IMPORTANT] - > For Cisco ATA replace mac.ini with mac.cfg. - > For Poly ATA replace mac.ini with $mac.cfg. + > [!IMPORTANT] + > For Cisco ATA replace mac.ini with mac.cfg. + > For Poly ATA replace mac.ini with $mac.cfg. 3. You must install Microsoft Teams Power Shell 5.6.0 or later. - > [!NOTE] - > The bulk sign in cmdlets aren't included with previous versions. + > [!NOTE] + > The bulk sign in cmdlets aren't included with previous versions. 4. You must apply [CommonAreaPhone policy](/microsoftteams/set-up-common-area-phones) to the accounts that are part of a bulk sign in request. 5. The accounts must not have Multi Factor Authentication (MFA) enabled. @@ -281,13 +281,13 @@ Bulk sign-in is very helpful and can be used in these scenarios. 7. The accounts must have the SIP device calling policy assigned. [AllowSIPDevicesCalling policy](/microsoftteams/sip-gateway-configure) 8. You must use an account that has the **Global Administrator, Privileged Authentication Administrator or the Authentication Administrator** role to run the cmdlets. -> [!IMPORTANT] ->Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + > [!IMPORTANT] + > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. 1. The **BulkSignIn** attribute must be set to `Enabled` in [TeamsSipDevicesConfiguration](/powershell/module/teams/set-csteamssipdevicesconfiguration) -> [!NOTE] -> As a best practice, try running bulk sign in cmdlet at least 1 hour and at most 70 hours after device provisioning. + > [!NOTE] + > As a best practice, try running bulk sign in cmdlet at least 1 hour and at most 70 hours after device provisioning. ### How to create a bulk sign in request @@ -306,26 +306,27 @@ Bulk sign-in is very helpful and can be used in these scenarios. 3. Run the following: - ```PowerShell - Import-Module MicrosoftTeams - $credential = Get-Credential // Enter your admin’s email and password - Connect-MicrosoftTeams –Credential $credential - $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC - ``` + ```PowerShell + Import-Module MicrosoftTeams + $credential = Get-Credential // Enter your admin’s email and password + Connect-MicrosoftTeams –Credential $credential + $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC + ``` -The `DeviceDetailsFilePath` parameter specifies the location of the CSV you created and saved. The `Region` parameter specifies the SIP gateway provisioning region where the devices are being deployed. The values are: APAC, EMEA, NOAM. + The `DeviceDetailsFilePath` parameter specifies the location of the CSV you created and saved. The `Region` parameter specifies the SIP gateway provisioning region where the devices are being deployed. The values are: APAC, EMEA, NOAM. 4. To check the status of a bulk sign-in batch, run the following: - ```PowerShell -$newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC -$newBatchResponse.BatchId -$getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId -$getBatchStatusResponse | ft -$getBatchStatusResponse.BatchItem -``` + ```PowerShell + $newBatchResponse = New-CsSdgBulkSignInRequest  -DeviceDetailsFilePath .\Example.csv  -Region APAC + $newBatchResponse.BatchId + $getBatchStatusResponse = Get-CsSdgBulkSignInRequestStatus -Batchid $newBatchResponse.BatchId + $getBatchStatusResponse | ft + $getBatchStatusResponse.BatchItem + ``` ### Bulk sign in error messages + To help you troubleshoot and fix common issues, these are common error messages that you might see and what you should do to fix it. | Error message | Potential solution | @@ -400,9 +401,8 @@ How to set Japanese for Cisco phones: > > - If **Sign in to make an emergency call** text is not translated to other languages, an abbreviated version in English only will be presented on **Press Sign In** on the following IP phone models due to a screensize limitations: > - -> - Poly VVX 150, VVX 201 -> - Cisco CP-6821, CP-7811, CP-7821, CP-7841, CP-7861 +> - Poly VVX 150, VVX 201 +> - Cisco CP-6821, CP-7811, CP-7821, CP-7841, CP-7861 > > - Voice mail softkey label is hardcoded with **VM** text across all languages for Poly VVX because of a limitation of string length. diff --git a/Teams/sip-gateway-dynamic-filters.md b/Teams/devices/sip-gateway-dynamic-filters.md similarity index 86% rename from Teams/sip-gateway-dynamic-filters.md rename to Teams/devices/sip-gateway-dynamic-filters.md index 66fb6f9cb6..518848f4a3 100644 --- a/Teams/sip-gateway-dynamic-filters.md +++ b/Teams/devices/sip-gateway-dynamic-filters.md @@ -45,12 +45,13 @@ To add or deactivate custom security attributes definitions, you must have: 2. Browse to **Protection** > **Custom security attributes**. 3. Select **Add attribute set** to add a new attribute set. - >[!NOTE] - >If **Add attribute set** is disabled, ensure that you're assigned the Attribute Definition Administrator role. For more information, see [Troubleshoot custom security attributes](/entra/fundamentals/custom-security-attributes-troubleshoot). + > [!NOTE] + > If **Add attribute set** is disabled, ensure that you're assigned the Attribute Definition Administrator role. For more information, see [Troubleshoot custom security attributes](/entra/fundamentals/custom-security-attributes-troubleshoot). 4. Enter a name, description, and maximum number of attributes. - > [!TIP] - > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). + + > [!TIP] + > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). 5. When finished, select **Add**. 6. The new attribute set appears in the list of attribute sets. @@ -63,25 +64,31 @@ To add or deactivate custom security attributes definitions, you must have: 4. Select to open the selected attribute set. 5. Select **Add attribute** to add a new custom security attribute to the attribute set. 6. In the **Attribute name** box, enter a custom security attribute name. - > [!TIP] - > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). - :::image type="content" source="media/exclude-attribute-set.png" alt-text="Screenshot displaying the Exclude attribute set."::: + > [!TIP] + > An attribute set name can be 32 characters with no spaces or special characters. Once you've specified a name, you can't rename it. For more information, see [Limits and constraints](/entra/fundamentals/custom-security-attributes-overview). + + :::image type="content" source="media/exclude-attribute-set.png" alt-text="Screenshot displaying the Exclude attribute set." lightbox="media/exclude-attribute-set.png"::: 7. In the **Description** box, enter an optional description. - > [!TIP] - > A description can be 128 characters long. If necessary, you can later change the description. + + > [!TIP] + > A description can be 128 characters long. If necessary, you can later change the description. + 8. From the **Data type** list, select the data type for the custom security attribute. - - Data type: A description. - - Boolean: A Boolean value that can be true or false. - - Integer: A 32-bit integer. - - String: A string that can be X characters long. + - Data type: A description. + - Boolean: A Boolean value that can be true or false. + - Integer: A 32-bit integer. + - String: A string that can be X characters long. + 9. For **Allow multiple values to be assigned**, select **Yes** or **No**. - - Select **Yes** to allow multiple values to be assigned to this custom security attribute. - - Select **No** to only allow a single value to be assigned to this custom security attribute. + - Select **Yes** to allow multiple values to be assigned to this custom security attribute. + - Select **No** to only allow a single value to be assigned to this custom security attribute. + 10. For **Only allow predefined values to be assigned**, select **Yes** or **No**. - Select **Yes**, if custom security attribute can be assigned values from a predefined values list. - Select **No** to allow this custom security attribute to be assigned user-defined values or potentially predefined values. + 11. If **Only allow predefined values to be assigned** is selected Yes, then select **Add value** to add predefined values. An active value is available for assignment of objects. A value that isn't active is defined, but not yet available for assignment. 12. When finished, select **Save**. 13. The new custom security attribute appears in the list of custom security attributes. @@ -186,6 +193,7 @@ New-MgServicePrincipal -AppId "61c8fd69-c13e-4ee6-aaa6-24ff71c09bca" - From **Select what this policy applies to** list, choose **Cloud apps**. - On the **Include** tab, select **All** apps option. - Change tab to **Exclude** and under **Select excluded cloud apps**, search for **Microsoft Teams Services** and click on **Select**. + 5. Select **Edit filter**. 6. On the **Edit filter** page, set **Configure** to **Yes**. 7. Select the attribute you created earlier (in this case 'exclAttrAllowMultiple'). diff --git a/Teams/sip-gateway-plan.md b/Teams/devices/sip-gateway-plan.md similarity index 98% rename from Teams/sip-gateway-plan.md rename to Teams/devices/sip-gateway-plan.md index 04eb6009a6..3ed51bfae1 100644 --- a/Teams/sip-gateway-plan.md +++ b/Teams/devices/sip-gateway-plan.md @@ -61,7 +61,7 @@ Teams users must have a phone number with PSTN calling enabled to use SIP Gatewa > DND - > \*30\* (Set DND From SIP Device) > \*31\* (Reset Teams DND Status from SIP Device) -> Call Forwarding - (https://support.microsoft.com/en-us/office/call-forwarding-call-groups-and-simultaneous-ring-in-microsoft-teams-a88da9e8-1343-4d3c-9bda-4b9615e4183e) +> Call Forwarding - (https://support.microsoft.com/office/call-forwarding-call-groups-and-simultaneous-ring-in-microsoft-teams-a88da9e8-1343-4d3c-9bda-4b9615e4183e) > \*32\* - Reset Call Forwarding Status > \*33\* (Set "Call Forwarded To" Number) > \*34\* (Set "Forward on Timeout") @@ -78,8 +78,8 @@ If you have a 3PIP or SIP device, you must have the following: - [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software) - Skype for Business Online (Plan 2) - *Skype for Business Online (Plan 2)* isn't a standalone license that can be purchased. -- [Microsoft Phone System](what-is-phone-system-in-office-365.md) -- [PSTN Connectivity](pstn-connectivity.md) +- [Microsoft Phone System](../what-is-phone-system-in-office-365.md) +- [PSTN Connectivity](../pstn-connectivity.md) ## Compatible devices diff --git a/Teams/devices/teams-displays-certified-hardware.md b/Teams/devices/teams-displays-certified-hardware.md index 72c28a14fa..2ddc8b436f 100644 --- a/Teams/devices/teams-displays-certified-hardware.md +++ b/Teams/devices/teams-displays-certified-hardware.md @@ -26,25 +26,17 @@ description: Find lists of certified Teams displays that run on Android. # Certified Teams displays -This article will help you find the resources for Teams displays that are certified under the Android Certification program including supported devices, firmware versioning, and End of Life (EOL) information. +The Microsoft Teams devices Certification Program ensures devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. -## Microsoft Teams certified Android device certification - -The Microsoft Teams Devices Certification Program ensures certified devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and Original Equipment Manufacturers (OEMs) partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. - -> [!IMPORTANT] -> The Microsoft Teams Devices Certification Program ensures certified devices meet specific requirements for hardware design and performance only. The certification program doesn't evaluate feature-level or cloud environment support. -> -> For information about what features are supported on Teams Rooms on Windows and Teams Rooms on Android, including cloud environment support, see [Teams Rooms on Windows and Android feature comparison](../rooms/teams-devices-feature-comparison.md). - -Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Microsoft OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. Once a device passes the certification requirements and OEM partners provide the firmware that enables the upgrade to a newer Android version, the certification end date will be extended. +Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Our OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. -After certification end date, Microsoft is committed to make efforts to support the most recent version of the Teams devices applications on such devices for two (2) years following the end of the certification period. +Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. -> [!NOTE] -> Certification end dates for Android 12 based devices has been extended by one year, from October 4, 2026, to August 15, 2027. Information below reflects current certification end dates. +We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. + +Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, these changes will be communicated through the established customer facing communication channels. ## Product release information for Teams displays @@ -82,7 +74,7 @@ The following Teams displays are certified under the Android Certification Progr | ThinkSmart View Plus | `10.1.t.2.38` | N/A | Teams client: `1449/1.0.95.2023061601`
Company Portal: `5.0.5954.0`
Admin Agent: `1.0.0.202306202019.product`| September 22, 2023| #### Neat -| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | elease date | +| Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:-----------------------------------------------------------|:--------------------------| | Neat Frame | `NFF1.20240620.1740` | N/A | Teams client: `1449/1.0.95.2023101102`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| August 26, 2024| | Neat Frame | `NFF1.20240516.0007` | N/A | Teams client: `1449/1.0.95.2023101102`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| August 7, 2024| @@ -100,14 +92,8 @@ The following Teams displays are certified under the Android Certification Progr ## [End of certification](#tab/eol) -Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. - -We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. - -Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, they will be communicated through the established customer facing communication channels. - | Device category | Device model | Android OS version | Certification end date | Microsoft support end date | |:----------------|:-------------------|:----------------------------|:--------------------------|:----------------------| |Teams displays| Lenovo ThinkSmart View | 8.1 | December 31, 2021| October 4, 2023 | |Teams displays | Crestron UC-P8-TD | 9 | August 5, 2023 | August 5, 2025| -|Teams displays | Crestron UC-P10-TD| 9 | August 5, 2023 | August 5, 2025 | \ No newline at end of file +|Teams displays | Crestron UC-P10-TD| 9 | August 5, 2023 | August 5, 2025 | diff --git a/Teams/devices/teams-panels-certified-hardware.md b/Teams/devices/teams-panels-certified-hardware.md index 2b8de4d29f..ff6321d675 100644 --- a/Teams/devices/teams-panels-certified-hardware.md +++ b/Teams/devices/teams-panels-certified-hardware.md @@ -26,29 +26,25 @@ description: Find lists of certified Teams panels running on Android. # Certified Teams panels -This article will help you find the resources for Teams panels that are certified under the Android Certification program including supported devices, firmware versioning, and End of Life (EOL) information. +The Microsoft Teams devices Certification Program ensures devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. -## Microsoft Teams certified Android device certification +Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Our OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. -The Microsoft Teams Devices Certification Program ensures certified devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and Original Equipment Manufacturers (OEMs) partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. +Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. -> [!IMPORTANT] -> The Microsoft Teams Devices Certification Program ensures certified devices meet specific requirements for hardware design and performance only. The certification program doesn't evaluate feature-level or cloud environment support. -> -> For information about what features are supported on Teams Rooms on Windows and Teams Rooms on Android, including cloud environment support, see [Teams Rooms on Windows and Android feature comparison](../rooms/teams-devices-feature-comparison.md). +Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. -Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Microsoft OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. Once a device passes the certification requirements and OEM partners provide the firmware that enables the upgrade to a newer Android version, the certification end date will be extended. +We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. -Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. +Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, these changes will be communicated through the established customer facing communication channels. -After certification end date, Microsoft is committed to make efforts to support the most recent version of the Teams devices applications on such devices for two (2) years following the end of the certification period. -> [!NOTE] -> Certification end dates for Android 12 based devices has been extended by one year, from October 4, 2026, to August 15, 2027. Information below reflects current certification end dates. ## [Certified Teams panels](#tab/certified-panels) The following devices are Certified under the Microsoft Teams panels Android Certification Program. +> [!NOTE] +> Certification end dates for Android 12 based devices has been extended by one year, from October 4, 2026, to August 15, 2027. Information below reflects current certification end dates. | Device model | Firmware version | Current certification end date | Android OS version | |:------------------------|:-----------------|:--------------|-----------------------| @@ -63,6 +59,7 @@ The following devices are Certified under the Microsoft Teams panels Android Cer |Poly TC10 | `5.0.0.211194`|September 3, 2025 | 11 | |Yealink RoomPanel | `147.520.0.4 `|September 3, 2025 | 10 | |Yealink RoomPanel Plus | `269.520.0.2 `|September 3, 2025 | 11 | +|Yealink RoomPanel E2 | `324.520.0.3 `|August 15, 2027 | 13 | ## [Firmware](#tab/firmware) @@ -77,6 +74,7 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Audiocodes | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:---------------------------------------------------------------|:----------------------------| +| RX Panel | `2.6.280` | N/A| Teams client: `1449/1.0.97.2024081207`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202407050618.product`| October 16, 2024| | RX Panel | `2.6.228` | N/A| Teams client: `1449/1.0.97.2024053104`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 21, 2024| | RX Panel | `2.4.124` | N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 1, 2024| | RX Panel | `2.4.55` | N/A| Teams client: `1449/1.0.97.2024010401`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| May 16, 2024| @@ -104,6 +102,8 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Logitech | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:--------------------------------------------------------------------|:--------------------------------| +| DockFlex (VR0035) | `1.13.118`| N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| October 3, 2024| +| TAP Scheduler (VR0028) | `1.13.124`| N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| October 3, 2024| | DockFlex (VR0035) | `1.12.149`| N/A| Teams client: `1449/1.0.97.2024040202`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| June 6, 2024| | TAP Scheduler (VR0028) | `1.12.708`| N/A| Teams client: `1449/1.0.97.2024040202`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| June 6, 2024| | DockFlex (VR0035) | `1.12.146`| N/A| Teams client: `1449/1.0.97.2024010401`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| May 16, 2024| @@ -120,6 +120,7 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Neat | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | |:----------------|:-------------------|:----------------------------|:-------------------------------------------------------------------------|:-------------------------------------| +| Neat Pad | `NFA1.20240924.0507` | N/A| Teams client: `1449/1.0.97.2024081207`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| November 11, 2024| | Neat Pad | `NFA1.20240620.1740` | N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| August 26, 2024| | Neat Pad | `NFA1.20240516.0501` | N/A| Teams client: `1449/1.0.97.2024040202`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| June 21, 2024| | Neat Pad | `NFA1.20240312.0503` | N/A| Teams client: `1449/1.0.97.2024010401`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| April 16, 2024| @@ -131,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.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| | TC10 | `5.0.0.211238` | N/A| Teams client: `1449/1.0.97.2023060102`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202306202019.product`| September 12, 2023| @@ -149,6 +151,7 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Crestron | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | Cloud | |:----------------|:-------------------|:----------------------------|:----------------------------------------------------------------------------|:-----------------|:-------------------------------------| +| TSS-770/TSS-1070 | `2.006.0054` | N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| October 17, 2024| GCCH| | TSS-770/TSS-1070 | `2.004.1054` | N/A| Teams client: `1449/1.0.97.2023080401`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202306202019.product`| January 17, 2024| GCCH| | TSS-770/TSS-1070 | `2.004.1029` | N/A| Teams client: `1449/1.0.97.2022748302`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202301162118.product`| July 18, 2023| GCCH| @@ -163,6 +166,7 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s #### Neat | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications | Release date | Cloud | |:----------------|:-------------------|:----------------------------|:-------------------------------------------------------------------------|:-------------------------------------|:--------------------| +| Neat Pad | `NFA1.20240620.1740` | N/A| Teams client: `1449/1.0.97.2024061108`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| September 27, 2024| GCCH| | Neat Pad | `NFA1.20240516.0501` | N/A| Teams client: `1449/1.0.97.2024040202`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202402202353.product`| July 30, 2024| GCCH| | Neat Pad | `NFA1.20240120.0109` | N/A| Teams client: `1449/1.0.97.2023111003`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202310260109.product`| March 26, 2024| GCCH| @@ -173,14 +177,5 @@ See [Microsoft Teams panels](../devices/overview-teams-panels.md) for features s ## [End of certification](#tab/eol) -Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo re-certification, while others might not get re-certified and will ultimately be discontinued by the OEM. - -We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. - -Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft will make every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, they will be communicated through the established customer facing communication channels. - \ No newline at end of file + No Teams panels devices have reached this milestone. diff --git a/Teams/devices/teams-phones-certified-hardware.md b/Teams/devices/teams-phones-certified-hardware.md index 29d4a26d79..e80c0a612b 100644 --- a/Teams/devices/teams-phones-certified-hardware.md +++ b/Teams/devices/teams-phones-certified-hardware.md @@ -26,30 +26,27 @@ description: Find lists of certified Teams phones running on Android. # Certified Teams phones -This article helps you find the resources for Teams phones that are certified under the Android Certification program including supported devices, firmware versioning, and End of Life (EOL) information. +The Microsoft Teams devices Certification Program ensures devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and OEM partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. -## Microsoft Teams certified Android device certification +Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Our OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. -The Microsoft Teams Devices Certification Program ensures certified devices meet a high standard, with higher performance targets and quality metrics across the entire Teams experience (audio, video, user interface). Microsoft and Original Equipment Manufacturers (OEMs) partners are actively working together to ensure devices meet all certification requirements, including security, audio and video quality, Teams experience, and accessibility. +Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. -> [!IMPORTANT] -> The Microsoft Teams Devices Certification Program ensures certified devices meet specific requirements for hardware design and performance only. The certification program doesn't evaluate feature-level or cloud environment support. -> -> For information about what features are supported on Teams Rooms on Windows and Teams Rooms on Android, including cloud environment support, see [Teams Rooms on Windows and Android feature comparison](../rooms/teams-devices-feature-comparison.md). +Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will need to be re-certified, while others may not be recertified and will be discontinued by the OEM. -Certification programs are designed to ensure all certified devices run an Android version with the required feature set for Teams and Teams Admin Center. Certification end dates are based on the Android version running on the device when it enters into the certification program. Microsoft OEM partners are working to extend the lifetime of the certification by upgrading the Android version and recertifying, or by releasing new models that are state-of-the-art. Once a device passes the certification requirements and OEM partners provide the firmware that enables the upgrade to a newer Android version, the certification end date is extended. +We recognize that device certification expiration can impact your business. Our OEM partners will detail their End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, consult our OEM partners' websites. -Microsoft is committed to certifying devices on latest Android versions available for Teams devices as long as OEM partners and SoC manufacturers are able to meet all certification requirements in effect at the time device enters certification. +Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft makes every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, these changes are communicated through the established customer facing communication channels. -After certification end date, Microsoft is committed to make efforts to support the most recent version of the Teams devices applications on such devices for two (2) years following the end of the certification period. -> [!NOTE] -> Certification end dates for Android 12 based devices has been extended by one year, from October 4, 2026, to August 15, 2027. The folowing information reflects current certification end dates. ## [Certified Teams phones](#tab/certified-phones) The following devices are certified under the Microsoft Teams phones Android Certification Program. +> [!NOTE] +> Certification end dates for Android 12 based devices has been extended by one year, from October 4, 2026, to August 15, 2027. The following information reflects current certification end dates. + | Device model | Firmware version | Current certification end date | Android OS version | |:---------------------------------------|:-----------------------------------------|:-----------------------------|-----------------------------------| | AudioCodes C430HD | `2.3.364` | August 15, 2027 | 12 | @@ -88,6 +85,7 @@ See [Microsoft Teams phones feature set](phones-for-teams.md) for information on #### Audiocodes | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications** | Release date | |:----------------|:-------------------|:----------------------------|:---------------------------------------------------------------------------------------------------------------|:------------------------------------------| +| C430HD | `2.3.461` | `1.19.584`| Teams client: `1449/1.0.94.2024080808`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202407050618.product`| November 20, 2024| | C435HD/C455HD/C470HD | `2.3.453` | `1.19.584`| Teams client: `1449/1.0.94.2024080808`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| September 19, 2024| | C430HD | `2.3.423` | `N/A`| Teams client: `1449/1.0.94.2024062010`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| September 17, 2024| | C448HD/C450HD | `1.19.712` | `N/A`| Teams client: `1449/1.0.94.2024062301`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| July 22, 2024| @@ -112,7 +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.0.10460` | `N/A`| Teams client: `1449/1.0.94.2024080808`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 28, 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 | | CCX350/CCX400/CCX500/CCX505/CCX600 | `8.1.5.1732` | `8.1.3.1301`| Teams client: `1449/1.0.94.2023072509`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202306202019.product`| January 12, 2024| @@ -131,9 +129,12 @@ See [Microsoft Teams phones feature set](phones-for-teams.md) for information on #### Yealink | Device model | Latest firmware version | Minimum firmware version | Included Microsoft applications** | Release date | |:----------------|:-------------------|:----------------------------|:----------------------------------------------------------------------------------------------|:--------------------------------------------| -|MP52| `145.15.0.97`| N/A | Teams client: `1449/1.0.94.2024060310`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 29, 2024| -|MP54/MP56/MP58| `122.15.0.157`| `N/A` | Teams client: `1449/1.0.94.2024071104`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 7, 2024| -|CP965| `143.15.0.65`| `N/A` | Teams client: `1449/1.0.94.2024071104`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 7, 2024| +|MP52 E2/MP54 E2/MP56 E2/MP58 E2| `176.15.0.25`| `N/A` | Teams client: `1449/1.0.94.2024082806`
Company Portal: `5.0.6152.0`
Admin Agent: ` 1.0.0.202402202353.product`| October 23, 2024| +|MP54/MP56/MP58| `122.15.0.160`| `122.15.0.142` | Teams client: `1449/1.0.94.2024082806`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| September 30, 2024| +|CP965| `143.15.0.68`| `143.15.0.54` | Teams client: `1449/1.0.94.2024082806`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| September 30, 2024| +|MP52| `145.15.0.97`| `N/A` | Teams client: `1449/1.0.94.2024060310`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| August 29, 2024| +|MP54/MP56/MP58| `122.15.0.157`| `122.15.0.142` | Teams client: `1449/1.0.94.2024071104`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| Recalled| +|CP965| `143.15.0.65`| `143.15.0.54 ` | Teams client: `1449/1.0.94.2024071104`
Company Portal: `5.0.6152.0`
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`
Company Portal: `5.0.6152.0`
Admin Agent: ` 1.0.0.202402202353.product`| July 31, 2024| |MP52| `145.15.0.94`| N/A | Teams client: `1449/1.0.94.2024060310`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| July 2, 2024| |VP59| `91.15.0.147`| N/A | Teams client: `1449/1.0.94.2024060310`
Company Portal: `5.0.6152.0`
Admin Agent: `1.0.0.202402202353.product`| July 2, 2024| @@ -170,12 +171,6 @@ See [Microsoft Teams phones feature set](phones-for-teams.md) for information on ## [End of certification](#tab/eol) -Microsoft and its Original Equipment Manufacturers (OEM) partners continually develop products to meet the needs of the market and elevate the Teams devices experience. During the product lifecycle, some products may receive an OS upgrade before their certification expires and will undergo recertification, while others might not get recertified and will ultimately be discontinued by the OEM. - -We recognize that device certification expiration can impact your business. Our OEM partners have detailed End-of-Life policies to assist and direct you towards adopting newer technologies. For the most current information on Teams certified devices referenced here, please consult our OEM partners' websites. - -Following a certification expiration, Microsoft is committed to supporting the latest version of the Teams devices applications on certified devices for a span of two (2) years after the certification period concludes. While Microsoft makes every effort to maintain support as described here, it retains the discretion to modify its support policy if necessary. Should any changes occur, they're communicated through the established customer facing communication channels. - | Device Category | Device Model | Android OS Version | Certification end date | Microsoft support end date | |:----------------|:-------------------|:----------------------------|:--------------------------|:----------------------| |Teams phones - conference|Poly Trio 8500/8800|7|October 4, 2021| October 4, 2023 | @@ -192,4 +187,4 @@ Following a certification expiration, Microsoft is committed to supporting the l |Teams phones | Crestron UC-P8| 9 | August 5, 2023 | August 5, 2025 | |Teams phones | Crestron UC-P10 | 9 | August 5, 2023 | August 5, 2025| |Teams phones - video| Crestron UC-P8-C | 9 | August 5, 2023 | August 5, 2025| -|Teams phones - video | Crestron UC-P10-C | 9 | August 5, 2023 | August 5, 2025 | \ No newline at end of file +|Teams phones - video | Crestron UC-P10-C | 9 | August 5, 2023 | August 5, 2025 | diff --git a/Teams/devices/usb-devices.md b/Teams/devices/usb-devices.md index 156b390720..074e4d01bc 100644 --- a/Teams/devices/usb-devices.md +++ b/Teams/devices/usb-devices.md @@ -31,14 +31,14 @@ For more information about call control support with Teams, see [control calls u ### Special usage designations -- **Native Bluetooth Certified Audio Peripherals** Most Bluetooth headsets and speakerphones that are certified for Microsoft Teams are designed to be used with a USB dongle for connectivity to PCs and Mac hosts. Many users have been asking for the option to directly pair their device with the host, because they don't have enough USB ports, or they don't want to have to remember to bring the USB dongle with them when they work in different locations. +- **Native Bluetooth Certified Audio Peripherals**: Most Bluetooth headsets and speakerphones that are certified for Microsoft Teams are designed to be used with a USB dongle for connectivity to PCs and Mac hosts. Many users have been asking for the option to directly pair their device with the host, because they don't have enough USB ports, or they don't want to have to remember to bring the USB dongle with them when they work in different locations. Native Bluetooth-certified devices, including headsets and speakerphones, are supported on Windows PCs (macOS may be supported in the future). Devices are tested for audio performance, call control, and Teams button integration, both with and without the use of a USB dongle. The performance in native Bluetooth mode is impacted by the Bluetooth radio on the host PC, so we recommend installing the latest firmware updates for both devices and Bluetooth radio. A small portion of users may need to continue to use the USB dongle, such as when working in a high-density radio environment, if their PC Bluetooth is heavily used by multiple paired devices, or with certain PCs that have poor-performing Bluetooth radios. -- **Premium Microphone for Open Office** All headsets are tested to provide clear audio, but open office and other noisy environments pose a greater challenge. Headsets with this designation pick up the voice of the headset user but don't transmit the sound of their neighbors. -- **Meeting room size** Shared devices such as speakerphones and cameras have a supported usage distance. Recommended distances may be different depending on the manufacturer. To give customers clear guidance, all shared devices are tested at certification against well-defined rooms sizes and noise environments. +- **Premium Microphone for Open Office**: All headsets are tested to provide clear audio, but open office and other noisy environments pose a greater challenge. Headsets with this designation pick up the voice of the headset user but don't transmit the sound of their neighbors. +- **Meeting room size**: Shared devices such as speakerphones and cameras have a supported usage distance. Recommended distances may be different depending on the manufacturer. To give customers clear guidance, all shared devices are tested at certification against well-defined rooms sizes and noise environments. ## End-user experience @@ -91,7 +91,7 @@ If you're a manufacturer and want to join the certification program, see [How to |Yealink |DeskVision A24 Monitor – Peripheral Mode |2/8/2024 |Certified for Microsoft Teams | |Yealink |BH70 Dual/ Mono Headset |2/8/2024 |Certified for Microsoft Teams | |Jabra |Evolve 65 SE/ 2 55/ 2 65/ 2 65 Flex/ 2 75/ 2 85/ 2 BUDS headsets with Link 390 dongle | 1/29/2024 |Certified for Microsoft Teams | -|HP |960 4K Streaming Webcam |11/20/2023 |Certified for Microsoft Teams | +|HP |960/965 4K Streaming Webcam |11/20/2023 |Certified for Microsoft Teams | |Dell |WL5024 Headset |11/17/2023 |Certified for Microsoft Teams | |Dell |WH5024 Headset |11/17/2023 |Certified for Microsoft Teams | |Anker |PowerConf S3 Speakerphone |11/17/2023 |Certified for Microsoft Teams | @@ -115,7 +115,7 @@ If you're a manufacturer and want to join the certification program, see [How to |EPOS |IMPACT 1060T |5/25/2023 |Certified for Microsoft Teams | |EPOS |IMPACT 1061T ANC |5/25/2023 |Certified for Microsoft Teams | |EPOS |IMPACT 1060T ANC |5/25/2023 |Certified for Microsoft Teams | -|Poly |Voyager Surround 80 UC Headset |5/12/2023 |Certified for Microsoft Teams | +|Poly |Voyager Surround 80 UC/85 UC Headset |5/12/2023 |Certified for Microsoft Teams | |Poly |Savi 7410/7420 Office Series headsets |4/24/2023 |Certified for Microsoft Teams | |Poly |Savi 8410/8420/8445 Office Series headsets |4/24/2023 |Certified for Microsoft Teams | |Lenovo |ThinkVision MC60 Monitor Webcam |4/13/2023 |Certified for Microsoft Teams | diff --git a/Teams/dial-voice-reference.md b/Teams/dial-voice-reference.md index 5d4cdd775f..b0af9b3172 100644 --- a/Teams/dial-voice-reference.md +++ b/Teams/dial-voice-reference.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 09/17/2024 +ms.date: 11/22/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -14,9 +14,9 @@ ms.collection: - m365initiative-voice - tier1 audience: Admin -appliesto: - - Skype for Business +appliesto: - Microsoft Teams + - Skype for Business ms.localizationpriority: medium f1.keywords: - CSH @@ -30,7 +30,7 @@ description: Learn about the Auto attendant and Call queue dialing and voice rec --- # Auto attendant and Call queue dialing and voice recognition reference -Dial by Name or Extension is an Auto attendant feature that enables callers to reach Teams users in your organization. Using their voice or phone keypad callers can say or enter the full or partial name, or extension of the person they would like to reach. The Auto attendant searches the company directory, locates the person, and then transfers the caller to them. Dial by Name or Dial by Extension are options you set up when you [configure the call flow settings in an Auto attendant](create-a-phone-system-auto-attendant.md?tabs=call-flow). +Dial by Name or Extension is an Auto attendant feature that enables callers to reach Teams users in your organization. Callers can use their voice or phone keypad to say or enter the full or partial name or extension of the person they would like to reach. The Auto attendant searches the company directory, locates the person, and then transfers the caller to them. As an admin, Dial by Name or Dial by Extension are options you set up when you [configure the call flow settings in an Auto attendant](create-a-phone-system-auto-attendant.md?tabs=call-flow). ## Searching for users @@ -49,16 +49,18 @@ There's no limit on the number of Active Directory users that search can support |DTMF (keypad entry) |Partial
FirstName + LastName
LastName + FirstName |No limit | |Speech (voice input) |FirstName
LastName
FirstName + LastName
LastName + FirstName | No limit | -> [!NOTE] -> You can use the [Dial Scope](create-a-phone-system-auto-attendant.md?tabs=dial-scope) feature to narrow down the names that are reachable by changing the scope for a particular Auto attendant. - ### Search Considerations Auto attendant search is a part of the main Address Book search of Microsoft. Exchange Address Book settings affect searches performed via the Auto attendant service. For example, if some users in your Address Book settings have the property `-HiddenFromAddressListsEnabled = $true`, then Auto attendant search won't return these users. This is similar to the Address Book search experience in Exchange, Teams, and other products. For more information about hiding users from the Address Book, see [Manage address lists in Exchange Online](/exchange/address-books/address-lists/manage-address-lists#hide-recipients-from-address-lists). Once the main address book settings are verified, the search then proceeds to apply any configured [Dial Scope](create-a-phone-system-auto-attendant.md?tabs=dial-scope) Include or Exclude lists. -Note that it might take up to 24 hours for Active Directory Address Book updates to be reflected in the Auto attendant search results. This timeframe also applies to the addition of new users or the removal of existing ones. +> [!NOTE] +> You can use the [Dial Scope](create-a-phone-system-auto-attendant.md?tabs=dial-scope) feature to narrow down the names that are reachable by changing the scope for a particular Auto attendant. +> +> If more than 5 names remain after any Dial Scope Include or Exclude lists are applied, the search fails and the caller is told that too many names were found. +> +> It might take up to 24 hours for Active Directory Address Book updates to be reflected in the Auto attendant search results. This timeframe also applies to the addition of new users or the removal of existing ones. ## Dial by Name - Keypad (DTMF) entry @@ -66,9 +68,6 @@ People calling in can use Dial by Name to reach users by specifying either the f When people search your organization's directory, they can use the '0' (zero) key to indicate a space between the first name and last name or last name and first name. When they enter a name, they're asked to terminate their keypad entry with the # key. For example, "After you enter the name of the person you're trying to reach, press #." If there are multiple names that are found, the person calling is given a list of names to select from. -> [!NOTE] -> If more than 5 names remain after any Dial Scope Include or Exclude lists are applied, the search fails and the caller is told that too many names were found. - People can search for names in your organization using the following search formats on their phone keypad: |Name format|Search type|Example|Search result| @@ -97,9 +96,6 @@ You can enable speech recognition for an Auto attendant, but phone keypad entry As with phone keypad entry, if multiple names are found, the person calling hears a list of names to select from. -> [!NOTE] -> If more than 5 names remain after any Dial Scope Include or Exclude lists are applied, the search fails and the caller is told that too many names were found. - Callers can say names in the following formats: |Name with speech|Search type|Example|Search result| @@ -111,6 +107,27 @@ Callers can say names in the following formats: |FirstName or LastName |Partial |Mar |Press or say 1 for Mary Marble
Press or say 2 for Mary Jones
Press or say 3 for Amos Marcus | |FirsName + LastName |Partial |Amos Mar |Press or say 1 for Amos Marble
Press or say 2 for Amos Marcus | +### Dial by Name - Multiple users with the same name + +If there are multiple users with the same name, it's possible that a Dial by Name search returns these users. In this case, the default behavior is to say each name followed by the option to select. For example, if the caller searches for `John Smith` and there are three people with that name in the organization, the caller hears: + +- For John Smith, press 1. +- For John Smith, press 2. +- For John Smith, press 3. + +In these situations, you can extend the information the caller is presented with by configuring the [-UserNameExtension](/powershell/module/teams/new-csautoattendant#-usernameextension) parameter. + +The `-UserNameExtension` parameter specifies how to extend the information returned in a Dial by Name search with additional information. Possible values are: + +- **None**: The username is pronounced as is. This is the default value. +- **Office**: Adds office information from the user profile. +- **Department**: Adds department information from the user profile. + +If `-UserNameExtension` is configured with `Department`, and if the caller searches for `John Smith` when there are three people with that name in the organization, the caller hears: + +- For John Smith in accounting, press 1. +- For John Smith in sales, press 2. +- For John Smith in support, press 3. ### Dial by Extension @@ -129,11 +146,22 @@ The required format to enter the extension in the user phone number field can be - *+\x\* - *x\* -- Example 1: Update-MgUser -UserId 'usern@domain.com' -MobilePhone '15555555678;ext=5678' -- Example 2: Update-MgUser -UserId 'usern@domain.com' -MobilePhone '+15555555678x5678' -- Example 3: Update-MgUser -UserId 'usern@domain.com' -MobilePhone 'x5678' +Example 1: + +```PowerShell +Update-MgUser -UserId 'usern@domain.com' -MobilePhone '15555555678;ext=5678' +``` +Example 2: -You can set the extension in the [Microsoft 365 admin center](https://admin.microsoft.com/) or the [Microsoft Entra admin center](https://aad.portal.azure.com). +```PowerShell +Update-MgUser -UserId 'usern@domain.com' -MobilePhone '+15555555678x5678' +``` + +Example 3: +```PowerShell +Update-MgUser -UserId 'usern@domain.com' -MobilePhone 'x5678' +``` +You can set the extension in the [Microsoft 365 admin center](https://admin.microsoft.com/) or the [Microsoft Entra admin center](https://aad.portal.azure.com). For more information on the Update-MgUser cmdlet, see [Update-MgUser](/powershell/module/microsoft.graph.users/update-mguser). > [!NOTE] > If using the TelephoneNumber field to define the extension, Microsoft recommends that you use the format *+\;ext=\*. If the user is also assigned a Teams Phone Number, you should define both numbers the same way. @@ -164,6 +192,8 @@ The following voice commands are available for speech recognition: ## Related articles +[Plan for Teams Auto attendants and Call queues](plan-auto-attendant-call-queue.md) + [Getting service phone numbers for Skype for Business and Microsoft Teams](./getting-service-phone-numbers.md) [Country and region availability for Audio Conferencing and Calling Plans](country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans.md) diff --git a/Teams/direct-routing-sbc-multiple-tenants.md b/Teams/direct-routing-sbc-multiple-tenants.md index c29dc70af6..f0b05d2cf4 100644 --- a/Teams/direct-routing-sbc-multiple-tenants.md +++ b/Teams/direct-routing-sbc-multiple-tenants.md @@ -233,7 +233,7 @@ With the initial release of Direct Routing, Microsoft required a trunk to be add However, this method isn't optimal for two reasons: -- **Overhead management**. Offloading or draining an SBC, for example, changes some parameters, like enabling or disabling media bypass. Changing the port requires changing parameters in multiple tenants (by running Set-CSOnlinePSTNGateway), but it is in fact the same SBC. +- **Overhead management**. Offloading or draining an SBC, for example, or changes to some parameters, like enabling or disabling media bypass or changing a port requires changing the parameters in multiple tenants (by running Set-CSOnlinePSTNGateway), but it is in fact the same SBC. - **Overhead processing**. Gathering and monitoring trunk health data - SIP options collected from multiple logical trunks that are, in reality, the same SBC and the same physical trunk, slows down processing of the routing data. @@ -253,9 +253,25 @@ Two new entities were introduced: - Carriers need to set up and manage only a single trunk (the carrier trunk in the carrier domain) by using the New-CSOnlinePSTNGateway command. In the preceding example, the trunk is sbc1.adatum.biz. -- In the customer tenant, the carrier needs to add the derived trunk FQDN to the voice routes. There's no need to run New-CSOnlinePSTNGateway for a trunk. +- In the customer tenant, the derived trunk FQDN needs to be added to the voice routes. To add a derived trunk FQDN to a voice route, perform the following steps in Teams Admin Center: + 1. Open the Teams Admin Center. + 2. From the left siderail, expand **Voice**, and select **Direct Routing**. + 3. From Direct Routing tabs, select **Voice routes**. + 4. Select **Add** (or select existing Voice route). + 5. In the Voice route profile, under SBCs enrolled, select **Add SBCs**. + 6. From the right side panel, under *Add SBC as derived trunk* enter SBC FQDN for your tenant, and select **Add**. + 7. Select **Apply**. + + + Or, use the PowerShell command CsOnlineVoiceRoute with the [-OnlinePstnGatewayList](/powershell/module/teams/set-csonlinevoiceroute) parameter: + ```PowerShell + Set-CsOnlineVoiceRoute -Identity OnlineVoiceRoute_1 -OnlinePstnGatewayList @{add="woodgrovebank.sbc1.adatum.biz"} + ``` + + - If the specified derived trunk is invalid, then the service will not allow the configuration to be applied. + - There's no need to run New-CSOnlinePSTNGateway for a trunk. + - The derived trunk, as the name suggests, inherits and derives all the configuration parameters from the carrier trunk. -- The derived trunk, as the name suggests, inherits or derives all the configuration parameters from the carrier trunk. Examples: - sbc1.adatum.biz – the carrier trunk that needs to be created in the carrier tenant. diff --git a/Teams/direct-routing-survivable-branch-appliance.md b/Teams/direct-routing-survivable-branch-appliance.md index 8b347512db..d43ce1995d 100644 --- a/Teams/direct-routing-survivable-branch-appliance.md +++ b/Teams/direct-routing-survivable-branch-appliance.md @@ -1,7 +1,7 @@ --- title: Direct Routing SBA -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 08/15/2024 ms.topic: article @@ -30,7 +30,7 @@ Occasionally, a customer site using Direct Routing to connect to Microsoft Teams In this scenario, assume that the customer site--called a branch--temporarily can't connect to the Microsoft cloud through Direct Routing. However, the intranet inside the branch is still fully functional, and users can connect to the Session Border Controller (SBC) that is providing PSTN connectivity. -This article describes how to use a Survivable Branch Appliance (SBA) to enable Teams Phone to continue to make and receive Public Switched Telephone Network (PSTN) calls in case of an outage. +This article describes how to use a Survivable Branch Appliance (SBA) with Teams Phone to support continuity of making and receiving Public Switched Telephone Network (PSTN) calls in case of an outage. ## Prerequisites @@ -231,17 +231,23 @@ For step-by-step guidance on how to configure your Session Border Controller wit The following are known issues and considerations: -- Because the SBA relies on authentication tokens that are valid for 24 hours and are renewed daily, the SBA can support outages for up to 24 hours from the last authentication. If an outage occurs 20 hours after the last authentication token renewal, the SBA will be operational only for the remaining 4 hours. +- In SBA mode + - the SBA supports expired client authentication tokens for up to 7 days from the token expiration. + - the Teams client won't be able to connect to the SBA if the Teams client is triggered to negotiate a new token. For example, if a user quits and restarts their Teams client or restarts their device. + - the Teams client won't be able to validate itself with an SBA that it hasn't previously connected with, in the last 24 hours. -- If the tenant is using Continuous Access Evaluation (CAE) tokens, the SBA will be operational only for about 30 minutes, due to the nature of continuous access evaluation. An alternative would be to dissable CAE for the tenant. +- In SBA mode, the following user actions aren't supported: + - switching their Teams client to another tenant + - sharing location information during an emergency call (E911). Users can still make emergency call but location information won't be shared. + - reaching other Teams users with reverse number lookup against Microsoft Entra ID Contacts. A dialed number will still be processed by SBA and routed over PSTN. -- When you add new Survivable Branch Appliances, it might take time before you can use them in Survivable Branch Appliance policies. -- When you assign a Survivable Branch Appliance policy to a user, it might take time before the SBA is shown in the output of Get-CsOnlineUser. +- If the tenant is using Continuous Access Evaluation (CAE) tokens, the SBA will be operational only for about 30 minutes, due to the nature of continuous access evaluation. An alternative would be to disable CAE for the tenant. + +- When you add new Survivable Branch Appliances, it might take time before you can use them in Survivable Branch Appliance policies. -- Reverse number lookup against Microsoft Entra ID Contacts isn't performed. +- When you assign a Survivable Branch Appliance policy to a user, it might take time before the SBA is shown in the output of Get-CsOnlineUser. -- Making an emergency call to an emergency number configured for dynamic emergency calling (E911) is not supported. ## Report an issue diff --git a/Teams/direct-routing-whats-new.md b/Teams/direct-routing-whats-new.md index 63485603ab..9f686c00dc 100644 --- a/Teams/direct-routing-whats-new.md +++ b/Teams/direct-routing-whats-new.md @@ -1,9 +1,9 @@ --- title: What's New Direct Routing -ms.reviewer: CarolynRowe -ms.date: 09/22/2023 -author: CarolynRowe -ms.author: crowe +ms.reviewer: teddygyabaah +ms.date: 11/07/2024 +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: article audience: admin @@ -22,6 +22,12 @@ ms.collection: # What's new for Direct Routing This article describes what's new in Direct Routing. Check back often for updates. + +## Network Effectiveness Ratio (NER) metric update + +To improve the experience with visibility of possible issues affecting your Direct Routing reliability, we are updating the formula to calculate the metric for Network Effectiveness Ratio (NER). Starting from November 11, 2024, you might notice a slight change in the reported NER for your trunks in the Teams Admin Center (TAC). +If you notice a drop in the NER value, you can identify the cause of a call failure by looking at specific response codes. For a list of the most common errors and suggested actions to resolve them, see [Microsoft and SIP response codes](/microsoftteams/troubleshoot/phone-system/direct-routing/microsoft-sip-response-codes). + ## New Survivable Branch Appliance version (v2024.8.15.1) is available New Survivable Branch Appliance (SBA) for Direct Routing version is available starting September 23, 2024. Latest version supports following functionality: @@ -34,17 +40,17 @@ Latest version supports following functionality: - Redirect of incoming PSTN call to a Call queue or Auto attendant number to a local agent. - Redirect of incoming PSTN call to a Call queue or Auto attendant number to an alternative Call queue or Auto attendant number. - VoIP Fallback. If a VoIP call can't be initiated and the receiving party has a PSTN number, a PSTN call is attempted. -- VoIP calls between local users. If both users are registered behind the same SBA, a VoIP call can be initiated instead of PSTN call, and the SBA will support the call. -To get the latest version please contact your SBC vendor. For the list of supported SBC vendors please refer to [Session Border Controller configuration](/microsoftteams/direct-routing-survivable-branch-appliance#session-border-controller-configuration). -To learn more about about Survivable Branch Appliance (SBA), see [Survivable Branch Appliance (SBA) for Direct Routing](/microsoftteams/direct-routing-survivable-branch-appliance). +- VoIP calls between local users. If both users are registered behind the same SBA, a VoIP call can be initiated instead of PSTN call, and the SBA supports the call. +To get the latest version, contact your SBC vendor. For the list of supported SBC vendors, refer to [Session Border Controller configuration](/microsoftteams/direct-routing-survivable-branch-appliance#session-border-controller-configuration). +To learn more about Survivable Branch Appliance (SBA), see [Survivable Branch Appliance (SBA) for Direct Routing](/microsoftteams/direct-routing-survivable-branch-appliance). ## SBC certificates EKU extensions test On March 5, 2024 (starting 9 AM UTC), Microsoft will conduct a 24-hour test of its infrastructure. During this time, Session Border Controllers (SBCs) certificates are required to include both Client and Server Authentication for their Extended Key Usage (EKU) extensions. We kindly ask that you ensure that the EKU extension of your certificate includes Server Authentication and Client Authentication to avoid any service degradation. -If your SBCs certificate EKU extension doesn't include both Server and Client Authentication, your SBCs will not be able to connect with Microsoft infrastructure. +If your SBC's certificate EKU extension doesn't include both Server and Client Authentication, your SBCs won't connect with Microsoft infrastructure. -Please note that the final switch to request both Server and Client authentication for EKU will be performed on March 19, 2024. +Note that the final switch to request both Server and Client authentication for EKU will be performed on March 19, 2024. For more information, see [Public trusted certificate for the SBC](direct-routing-plan.md#public-trusted-certificate-for-the-sbc). @@ -52,7 +58,7 @@ For more information, see [Public trusted certificate for the SBC](direct-routin Microsoft 365 is updating services powering messaging, meetings, telephony, voice, and video to use TLS certificates from a different set of Root Certificate Authorities (CAs). Affected endpoints include Microsoft Teams Direct Routing SIP endpoints used for PSTN traffic in Office 365 Government - GCC High (GCCH) and DoD deployments. The transition to certificates issued by the new CA for SIP endpoints begins in May 2024. This means that action needs to be taken before end of April 2024. -The new Root CA "DigiCert Global Root G2" is widely trusted by operating systems including Windows, macOS, Android, and iOS and by browsers such as Microsoft Edge, Chrome, Safari, and Firefox. However, it's likely that your SBC has a certificate root store that is manually configured. If so, then the YOUR SBC CA STORE NEEDS TO BE UPDATED TO INCLUDE THE NEW CA TO AVOID SERVICE IMPACT. SBCs that don't have the new Root CA in their list of acceptable CAs receive certificate validation errors, which may impact the availability or function of the service. Both the old and the new CA MUST be trusted by the SBC – DON’T REMOVE THE OLD CA. Please refer to SBC vendor documentation on how to update the accepted certificate list on your SBC. Both the old and new root certificates need to be trusted by the SBC. +The new Root CA "DigiCert Global Root G2" is widely trusted by operating systems including Windows, macOS, Android, and iOS and by browsers such as Microsoft Edge, Chrome, Safari, and Firefox. However, it's likely that your SBC has a certificate root store that is manually configured. If so, then the YOUR SBC CA STORE NEEDS TO BE UPDATED TO INCLUDE THE NEW CA TO AVOID SERVICE IMPACT. SBCs that don't have the new Root CA in their list of acceptable CAs receive certificate validation errors, which may impact the availability or function of the service. Both the old and the new CA MUST be trusted by the SBC – Do not remove the old CA. Refer to SBC vendor documentation on how to update the accepted certificate list on your SBC. Both the old and new root certificates need to be trusted by the SBC. Today, the TLS certificates used by Microsoft SIP interfaces chain up to the following Root CA: Common Name of the CA: DigiCert Global Root CA @@ -64,7 +70,7 @@ Common Name of the CA: DigiCert Global Root G2 Thumbprint (SHA1): df3c24f9bfd666761b268073fe06d1cc8d4f82a4 The new CA certificate can be downloaded directly from DigiCert: https://cacerts.digicert.com/DigiCertGlobalRootG2.crt -For more details, please refer to the technical guidance at https://docs.microsoft.com/en-us/microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide +For more details, refer to the technical guidance at [Azure Certificate Authority details](/microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide). To test and confirm your SBCs certificate configuration prior to the change, Microsoft has prepared a testing endpoint that can be used to verify that SBC appliances trust certificates issued from the new root CA (DigiCert Global Root G2). If your SBC can establish a TLS connection to this endpoint, then your connectivity to Teams services shouldn't be affected by the change. These endpoints should be used only for SIP OPTIONS ping messages and not for voice traffic. They aren't production endpoints and aren't backed by redundant configuration. This means they'll experience downtime that lasts for several hours—expect about 95% availability. Test endpoint FQDN for GCCH: x.sip.pstnhub.infra.gov.teams.microsoft.us @@ -78,11 +84,11 @@ Port: 5061 Following two tests on September 5 and 19, Microsoft will perform the final switch to the new Certificate Authority (CA) on October 3, starting at 10 AM UTC. All Microsoft SIP endpoints are gradually switched over to use certificates where the certificate chain rolls up to “DigiCert Global Root G2” Certificate Authority (CA). -If your Session Border Controllers (SBCs) aren't properly configured with the new Certificate Authority (CA), your Direct Routing incoming and outgoing calls will fail after the switch. Please work with your SBC vendor directly for further guidance on SBC configuration. +If your Session Border Controllers (SBCs) aren't properly configured with the new Certificate Authority (CA), your Direct Routing incoming and outgoing calls will fail after the switch. Work with your SBC vendor directly for further guidance on SBC configuration. The change requirement and test were communicated to Direct Routing customers through Message Center posts as well as Service Health Incidents in the Microsoft Admin Portal (MC540239, TM614271, MC663640, TM674073, MC674729). -## SIP certificate to MSPKI Certificate Authority change additional testing +## SIP certificate to MSPKI Certificate Authority change, extra testing On September 19 (starting at 4 PM UTC), Microsoft will perform a 24 hour test where all Microsoft SIP endpoints will be switched over to use certificates where the certificate chain will roll up to “DigiCert Global Root G2” Certificate Authority (CA). New Certificate Authority (CA) must be added in your SBC configuration and old Baltimore CA must be retained; don't replace the old CA. If your SBC doesn’t trust this CA, you won't be able to connect to Teams SIP endpoints during the test. The final switch to the new Certificate Authority (CA) will be performed on October 3. @@ -92,7 +98,7 @@ Test endpoint FQDN: sip.mspki.pstnhub.microsoft.com Port: 5061 -## SIP certificate to MSPKI Certificate Authority change test +## SIP certificate to MSPKI Certificate Authority change, test On September 5 (starting at 9 AM UTC), Microsoft will perform a 24-hour test where all Microsoft SIP endpoints will be switched over to use certificates where the certificate chain will roll up to “DigiCert Global Root G2” Certificate Authority (CA). If your SBC doesn’t trust this CA, you might not be able to connect to Teams SIP endpoints. @@ -123,7 +129,7 @@ The new CA certificate can be downloaded directly from DigiCert: DigiCert Global For more information, see [Office TLS Certificate Changes](/purview/encryption-office-365-tls-certificates-changes) ## New Direct Routing SIP endpoints -Microsoft will introduce new signaling IPs to Teams Direct Routing SIP endpoints. To ensure this change doesn’t affect your service availability, make sure your Session Border Controller and Firewall are configured to use the recommended subnets 52.112.0.0/14 and 52.122.0.0/15 for classification and ACL rules. For more information, see [Microsoft 365, Office 365, and Office 365 GCC environments](direct-routing-plan.md#microsoft-365-office-365-and-office-365-gcc-environments). +Microsoft introduces new signaling IPs to Teams Direct Routing SIP endpoints. To ensure this change doesn’t affect your service availability, make sure your Session Border Controller and Firewall are configured to use the recommended subnets 52.112.0.0/14 and 52.122.0.0/15 for classification and ACL rules. For more information, see [Microsoft 365, Office 365, and Office 365 GCC environments](direct-routing-plan.md#microsoft-365-office-365-and-office-365-gcc-environments). ## Trunk demoting logic based on SIP Options diff --git a/Teams/easy-policy-setup-edu.md b/Teams/easy-policy-setup-edu.md index 437b98e4e2..f14726d5d1 100644 --- a/Teams/easy-policy-setup-edu.md +++ b/Teams/easy-policy-setup-edu.md @@ -21,11 +21,11 @@ description: Learn how to use the Teams for Education policy wizard to easily ap f1keywords: --- -# Use the Teams for Education Policy Wizard to easily apply policies for a safe learning environment +# Use the Teams for Education Policy Wizard to easily apply policies and apps for a safe learning environment ## Overview -The Microsoft Teams for Education Policy Wizard simplifies managing policies for your students and educators. Use it to easily and quickly apply the most important set of policies relevant to creating a safe and productive learning experience. +The Microsoft Teams for Education Policy Wizard simplifies managing policies and apps for your students and educators. Use it to easily and quickly apply important set of policies and apps relevant to creating a safe and productive learning experience. Policies in Teams let you control how Teams behaves in your environment and what features are available to users. For example, there are calling policies, meeting policies, and messaging policies, to name a few, and each policy area can be customized to meet your organization's needs. @@ -33,30 +33,28 @@ To maintain a safe and focused learning environment, it's important to set polic Policies must be adjusted for both students and educators to keep the learning experience safe. Policies for students need to be more restrictive to reduce their risk of receiving inappropriate levels of access. Educators and staff need a separate set of policies that can be more permissive to enable them to be successful. For example, allow educators to schedule meetings and restrict students from doing so. -:::image type="content" source="media/easy-policy-setup-institution-type.png" alt-text="Screenshot of wizard."::: - This article walks you through how to run the wizard. > [!IMPORTANT] -> The policies applied by the wizard will satisfy the needs of the majority of Teams for Education customers. The wizard adjusts the Global (Org-wide default) definition of a core set of policies with settings that we recommend for student safety and applies it to students. The wizard also creates and assigns a set of custom policies to educators and staff. Most Teams for Education customers won't need to use other policy assignment methods after running this wizard. Use other policy assignment methods *only* if you want to manually create and manage policies for your students, educators and staff. +> The policies applied by the wizard will satisfy the needs of the majority of Teams for Education customers. The wizard adjusts the Global (Org-wide default) definition of a core set of policies with settings that we recommend for student safety and applies it to students. The wizard also creates and assigns a set of custom policies to educators and staff, and enables apps for them. Most Teams for Education customers won't need to use other policy assignment methods after running this wizard. Use other policy assignment methods *only* if you want to manually create and manage policies for your students, educators and staff. ## Teams for Education Policy Wizard -The wizard applies a set of core policy definitions to students and a separate set of core policy definitions to educators and staff, with settings that are appropriate for each. Here's what happens when you run the wizard. +The wizard applies a set of core policy definitions to students and a separate set of core policy definitions and apps to educators and staff, with settings that are appropriate for each. Here's what happens when you run the wizard. The wizard sets up policies based on educational institution type (**Primary or Secondary** or **Higher education**). You select your institution type, and the wizard does the following: - **Students**: The wizard adjusts the Global (Org-wide default) policy definition of each policy area covered by the wizard with new default settings that are appropriate to keep your students safe. This ensures that your current students and all new students get the most restrictive set of policies. -- **Educators and staff**: The wizard creates a set of custom policy definitions for each policy area covered by the wizard with settings tailored to the needs of educators and staff. Then, it assigns the policy definitions to the group of educators and staff that you choose. In this way, your educators and staff get a more permissive set of policies to enable them to be successful. +- **Educators and staff**: The wizard creates a set of custom policy definitions for each policy area covered by the wizard with settings tailored to the needs of educators and staff. Then, it assigns the policy definitions to the group of educators and staff that you choose. In this way, your educators and staff get a more permissive set of policies to enable them to be successful. The wizard also enables apps for educators depending on the institution type. -You only need to run the wizard one time. New students automatically get the Global (Org-wide default) policy definitions applied by the wizard and new staff that you add to the group you selected are automatically assigned the custom policies. +You only need to run the wizard one time. New students automatically get the Global (Org-wide default) policy definitions applied by the wizard and new staff that you add to the group you selected are automatically assigned the custom policies and apps. Also, whenever a new feature is added to Teams, the appropriate EDU relevant default value of the policy for that feature will be automatically added to the Global (Org-wide default) without requiring any admin intervention. This helps to ensure that the right policies are in place to keep students secure and engaged. > [!NOTE] -> See [Policies applied by the wizard](#policies-applied-by-the-wizard) for a detailed list of policy definitions applied by the wizard. +> See [Policies and apps applied by the wizard](#policies-and-apps-applied-by-the-wizard) for a detailed list of policy definitions applied by the wizard. Now, let's get started! @@ -66,27 +64,24 @@ Now, let's get started! Follow these steps to run the wizard. -1. If you're new to Teams, the wizard automatically starts. Otherwise, you can start the wizard any time from the dashboard. In the left navigation of the Microsoft Teams admin center, go to **Home**, and then in the **Easy policy setup for a safe learning environment** tile, select **Quick setup**. - - :::image type="content" source="media/easy-policy-setup-quick-setup.png" alt-text="Screenshot of the wizard in the dashboard."::: - -2. Select your educational institution type (**Primary or Secondary** or **Higher education**), and then select **Next**. +1. The wizard automatically starts if you’ve not yet filled up your institution type. You can also start the wizard any time from the dashboard. In the left navigation of the Microsoft Teams admin center, go to **Home**, and run the wizard from the **Easily manage policies and apps** tile. - :::image type="content" source="media/easy-policy-setup-institution-type.png" alt-text="Screenshot of the page in wizard to select institution type."::: + +2. Select your educational institution type **K-12 (Primary or Secondary)** or **Higher education**, and then select **Save & continue**. -3. Search for and select groups that contain your educators and staff, and then select **Next**. If you don't have any groups set up yet for your educators and staff, [create a group](/microsoft-365/admin/create-groups/create-groups), and then re-run the wizard.

You can select up to three groups. Educators and staff in the groups you select will be assigned [a set of custom policies](#policies-applied-by-the-wizard) tailored to their needs. Remember that this set of policies is separate from the policies applied to students. + > [!NOTE] + > [Parents app](https://support.microsoft.com/topic/communicate-with-guardians-in-microsoft-teams-01471ecd-eb5d-4eda-9c5d-0064d672960e) is enabled for educators once you save your institution type as K-12 (Primary or Secondary). - :::image type="content" source="media/edu-policy-wizard-add-3-groups.png" alt-text="Screenshot of page in wizard to select educator and staff groups."::: +3. Search for and select groups that contain your educators and staff, and then select **Next**. If you don't have any groups set up yet for your educators and staff, [create a group](/microsoft-365/admin/create-groups/create-groups), and then re-run the wizard.

You can select up to three groups. Educators and staff in the groups you select will be assigned [a set of custom policies](#policies-and-apps-applied-by-the-wizard) tailored to their needs. Remember that this set of policies is separate from the policies applied to students. + 4. Review your selections. - :::image type="content" source="media/edu-policy-wizard-3-groups-review.png" alt-text="Screenshot of page in wizard to review selections."::: - + 5. Select **Apply** to apply your changes. This may take a few minutes to complete.

The Global (Org-wide default) policy definitions are immediately applied to students. For your educators and staff, it could take a few hours for the custom policies to be assigned to each member of the groups you selected, depending on the size of the groups. This happens in the background, after you successfully complete this step. 6. You're on your way, but you're not done yet! There're a few more things to consider. Next, check out the steps in the [What to do after running the wizard](#what-to-do-after-running-the-wizard) section of this article. - :::image type="content" source="media/easy-policy-setup-on-way.png" alt-text="Screenshot of page in wizard for next steps."::: - + ## What to do after running the wizard @@ -113,7 +108,7 @@ If more than one of these policy assignments exist for a user, Teams uses the fo Because of this order, the policies created by the wizard won't take effect if a user has existing direct assignments or group assignments. This means that you'll have to remove the existing policy assignments from the user so the policy applied by the wizard takes effect. -For each [policy area applied by the wizard](#policies-applied-by-the-wizard), do the following: +For each [policy area applied by the wizard](#policies-and-apps-applied-by-the-wizard), do the following: - Remove all existing direct assignments and group assignments from your students so that the Global (Org-wide default) policy definition applied by the wizard takes effect. - Remove any conflicting direct assignments for your educators and staff so that the custom policy definition created by the wizard takes effect. Use the above table to determine the scenarios that apply to you.

Keep in mind that the wizard assigns policies to your educators and staff group using a [group assignment ranking](assign-policies-users-and-groups.md#group-assignment-ranking) of 1, which is the highest ranking. If your educators and staff group has an existing policy of the same policy area assigned to it, that existing policy is moved to a lower ranking and the policy assigned by the wizard takes effect. @@ -126,7 +121,7 @@ For example, you assigned a meeting policy directly to educators and your studen ### Step 2: Check for additional measures that you can take for student safety -The wizard automatically adjusts and applies [these policies](#policies-applied-by-the-wizard). There are few additional measures, which you may want to take based on the needs of your institution to stay safe. +The wizard automatically adjusts and applies [these policies and apps](#policies-and-apps-applied-by-the-wizard). There are few additional measures, which you may want to take based on the needs of your institution to stay safe. See [Keeping students safe while using Teams for distance learning](https://support.microsoft.com/office/keeping-students-safe-while-using-teams-for-distance-learning-f00fa399-0473-4d31-ab72-644c137e11c8#ID0EBBAAA) for additional safety recommendations. @@ -144,18 +139,18 @@ But do check the [Message Center](https://admin.microsoft.com/AdminPortal/Home?# If you need to make changes after you run the wizard, you can re-run it and change your selections. -1. In the left navigation of the Microsoft Teams admin center, go to **Home**, and then in the **Easy policy setup for a safe learning environment** tile, select **Change**. +1. In the left navigation of the Microsoft Teams admin center, go to **Home**, and make changes through the **Easily manage policies and apps** tile. 2. From here, continue through each page of the wizard to make your changes. You can change your institution type, the groups of educators and staff to which you want to assign policies, or both. The following table summarizes what happens when you make a change in the wizard. |Type of change|Policy behavior| |---|---| -|Change both the educational institution type and the educators and staff groups|

  • **Students**: The Global (Org-wide default) policy definitions based on the new educational institution type are applied to students.
  • **Educators and staff**: A set of custom policy definitions based on the new educational institution type is created and assigned to the new educator and staff groups. The previous custom policy definitions are removed from the previous educators and staff groups.
| -|Change only the educational institution type|
  • **Students**: The Global (Org-wide default) policy definitions based on the new educational institution type are applied to students.
  • **Educators and staff**: A set of custom policy definitions based on the new educational institution type is created and assigned to the educators and staff groups. The custom policy definitions created for the previous educational institution type are removed from the educators and staff groups.
| +|Change both the educational institution type and the educators and staff groups|
  • **Students**: The Global (Org-wide default) policy definitions based on the new educational institution type are applied to students.
  • **Educators and staff**: A set of custom policy definitions based on the new educational institution type is created and assigned to the new educator and staff groups. The previous custom policy definitions are removed from the previous educators and staff groups. [Parents app](https://support.microsoft.com/topic/communicate-with-guardians-in-microsoft-teams-01471ecd-eb5d-4eda-9c5d-0064d672960e) is enabled for educators once the institution type is saved as K-12 (Primary or Secondary). It remains enabled if you change your saved selection from K12 to Higher education.
| +|Change only the educational institution type|
  • **Students**: The Global (Org-wide default) policy definitions based on the new educational institution type are applied to students.
  • **Educators and staff**: A set of custom policy definitions based on the new educational institution type is created and assigned to the educators and staff groups. The custom policy definitions created for the previous educational institution type are removed from the educators and staff groups. [Parents app](https://support.microsoft.com/topic/communicate-with-guardians-in-microsoft-teams-01471ecd-eb5d-4eda-9c5d-0064d672960e) is enabled for educators once the institution type is saved as K-12 (Primary or Secondary). It remains enabled if you change your saved selection from K12 to Higher education.
| |Change only the educators and staff groups|
  • **Students**: No change to the Global (Org-wide default) policy definitions applied to students.
  • **Educators and staff**: The custom policy definitions are assigned to the new educators and staff groups and removed from the previous educators and staff groups.
| -## Policies applied by the wizard +## Policies and apps applied by the wizard @@ -185,12 +180,13 @@ Here's the policy areas and corresponding policy names covered by the wizard. To |Messaging policy|Primary or Secondary Educators and Staff - Messaging|Higher Education Educators and Staff - Messaging| |Calling policy|Primary or Secondary Educators and Staff - Calling|Higher Education Educators and Staff - Calling| + ### Policy settings Here's a summary of the settings applied by the wizard for each policy area. > [!NOTE] -> Only team owners can create shared channels.

Shared channels with other organizations requires configuration of [Microsoft Entra B2B direct connect](/azure/active-directory/external-identities/b2b-direct-connect-overview) which is disabled by default. See [Collaborate with external participants in a channel](/microsoft-365/solutions/collaborate-teams-direct-connect) to enable this feature. +> Only team owners can create shared channels. Shared channels with other organizations requires configuration of [Microsoft Entra B2B direct connect](/azure/active-directory/external-identities/b2b-direct-connect-overview) which is disabled by default. See [Collaborate with external participants in a channel](/microsoft-365/solutions/collaborate-teams-direct-connect) to enable this feature. #### [**Students**](#tab/student-settings/) @@ -331,6 +327,13 @@ Here's a list of the custom policy definitions assigned to the educators and sta |||Busy on busy is available when in a call|Off|Off| |||Allow web PSTN calling|On|On| +--- + +### Apps +[Parents app](https://support.microsoft.com/topic/communicate-with-guardians-in-microsoft-teams-01471ecd-eb5d-4eda-9c5d-0064d672960e) is enabled for educators once the institution type is saved as K-12 (Primary or Secondary). + +It remains enabled if you change your saved selection from K12 to Higher education. At any time, the app can be turned off at the tenant level using  [Allow and block apps](manage-apps.md#allow-or-block-apps) in the Teams admin center. If it's turned off at the tenant level, it will be blocked for all users, even if user-level permissions are turned on. The Parents app can also be turned off at the user level using [Manage app permission policies in Microsoft Teams](teams-app-permission-policies.md). + ## Related topics - [Teams policies and policy packages for Education](policy-packages-edu.md) diff --git a/Teams/edu-parents-app.md b/Teams/edu-parents-app.md index 70dac6d33d..ae52532808 100644 --- a/Teams/edu-parents-app.md +++ b/Teams/edu-parents-app.md @@ -64,11 +64,15 @@ The Parents Connection allows educators and guardians to chat, email, and call u ## Turn on the Parents app in the Teams admin center -The Parents app is turned off by default, so class team owners won't see it in their class teams until it's allowed through the Teams admin center. The Parents app is turned on in the Teams admin center using [Allow apps blocked by developers](manage-apps.md#allow-or-block-apps). +The Parents app is turned off by default, so the class team owners won't see it in their class teams until it's allowed through the Teams admin center. The Parents app can be turned on in the Teams admin center in either of the following ways: -At any time, the app can be turned off at the tenant level using [Allow and block apps](manage-apps.md#allow-or-block-apps) in the Teams admin center. If it's turned off at the tenant level, it will be blocked for all users, even if user-level permissions are turned on. +1. If administrators save their institution type as K12 (Primary or Secondary) in the [Teams for Education Policy Wizard](easy-policy-setup-edu.md), the Parents app gets enabled for their tenant. -The Parents app can also be turned off at the user level using [Manage app permission policies in Microsoft Teams](teams-app-permission-policies.md). +1. Administrators can also control access to Parents app using [Allow apps blocked by developers](manage-apps.md#allow-or-block-apps). Sign in to the Teams admin center and access **Teams apps** > [Manage apps](https://admin.teams.microsoft.com/policies/manage-apps). Search for **Parents** on the  **Manage** apps page to find the Parents app published by Microsoft, and select  **Allow** or **Block**  option. + +At any time, the app can be turned off at the tenant level using [Allow and block apps](manage-apps.md#allow-or-block-apps)  in the Teams admin center. If it's turned off at the tenant level, it will be blocked for all users, even if user-level permissions are turned on. + +The Parents app can also be turned off **at the user level** using  [Manage app permission policies in Microsoft Teams](teams-app-permission-policies.md). > [!TIP] > If you want to learn about School Connection, which empowers parents and guardians to stay informed about their child’s classroom progress in real-time with no extra work required from educators, see  [Set up School Connection](/microsoft-365/education/deploy/school-connection-app). diff --git a/Teams/emergency-calling-dispatchable-location.md b/Teams/emergency-calling-dispatchable-location.md index 39ea7de92a..244ebe854d 100644 --- a/Teams/emergency-calling-dispatchable-location.md +++ b/Teams/emergency-calling-dispatchable-location.md @@ -77,7 +77,7 @@ The following table shows the types of emergency addresses and associated routin | Emergency address obtained from the operating system and manually edited and confirmed by the user. | Screened and Transferred to PSAP. | | Emergency address entered manually and confirmed by the user. | Screened and Transferred to PSAP. | | Emergency address entered through address autosuggest and confirmed by the user. | Direct to PSAP. | -| Emergency address statically assigned to a Common Area Phone. | Direct to PSAP.| +| Emergency address statically assigned to a Common Area Phone or Microsoft Teams Room. | Direct to PSAP.| | Emergency address statically assigned to the user/number. | Screened and Transferred to PSAP. | | Null | Screened and Transferred to PSAP. | diff --git a/Teams/emergency-calling-security-desk-notifications.md b/Teams/emergency-calling-security-desk-notifications.md index 24d3f0669c..be79b94211 100644 --- a/Teams/emergency-calling-security-desk-notifications.md +++ b/Teams/emergency-calling-security-desk-notifications.md @@ -1,7 +1,7 @@ --- title: Configure security desk notifications -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 05/03/2024 diff --git a/Teams/emergency-calling-terms-and-conditions.md b/Teams/emergency-calling-terms-and-conditions.md index 7363ca95f6..bc5f678f8d 100644 --- a/Teams/emergency-calling-terms-and-conditions.md +++ b/Teams/emergency-calling-terms-and-conditions.md @@ -1,7 +1,7 @@ --- title: "Emergency calling terms and conditions" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 11/28/2017 diff --git a/Teams/emergency-numbers-reference.md b/Teams/emergency-numbers-reference.md index 016bc580a5..a595b7a6c9 100644 --- a/Teams/emergency-numbers-reference.md +++ b/Teams/emergency-numbers-reference.md @@ -1,8 +1,8 @@ --- ms.date: 05/01/2024 title: Emergency numbers country reference -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: pavellatif ms.topic: article diff --git a/Teams/enable-users-to-record-their-name-when-they-join-a-meeting-in-teams.md b/Teams/enable-users-to-record-their-name-when-they-join-a-meeting-in-teams.md index 4762b675bf..ec6ddc3d61 100644 --- a/Teams/enable-users-to-record-their-name-when-they-join-a-meeting-in-teams.md +++ b/Teams/enable-users-to-record-their-name-when-they-join-a-meeting-in-teams.md @@ -1,10 +1,10 @@ --- -title: "Enable users to record their name for a meeting" +title: "Allow users to record their name for a meeting" ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/14/2023 +ms.date: 11/1/2024 ms.topic: article ms.assetid: 1d649328-ada7-422d-a074-d6da4da36970 ms.tgt.pltfrm: cloud @@ -24,16 +24,16 @@ f1.keywords: ms.custom: - Audio Conferencing - seo-marvel-mar2020 -description: "Learn how to enable or disable whether your users can record their names when they join a meeting in Microsoft Teams." +description: "Learn how to manage whether your users can record their names when they join a meeting in Microsoft Teams." --- -# Enable users to record their name when they join a meeting in Microsoft Teams +# Allow users to record their name when they join a meeting in Microsoft Teams When you set up Audio Conferencing in Microsoft 365 or Office 365, you get phone numbers for your users through an audio conferencing bridge. A conferencing bridge can have one or more phone numbers that are included at the bottom of the meeting invite. These phone numbers allow users to join Microsoft Teams meetings by dialing in. As an admin, you can manage whether callers who dial in can record their name before joining a meeting. -## Manage whether callers can record their name in the Teams admin center +## Allow callers to record their name in the Teams admin center Using the Microsoft Teams admin center: @@ -41,21 +41,22 @@ Using the Microsoft Teams admin center: 2. At the top of the **Conference Bridges** page, select **Bridge settings**. -3. Enable or disable **Meeting entry and exit notifications**. +3. Toggle **Meeting entry and exit notifications** to on. -4. If enabling entry and exit notifications, choose **Names or phone numbers** for **Entry/exit announcement type**, and then toggle **Ask callers to record their name before joining a meeting** to **On**. +4. For **Entry/exit announcement type** select **Names or phone numbers** from the dropdown. -5. Select **Save**. +5. Toggle **Ask callers to record their name before joining a meeting** to **On**. + +6. Select **Save**. > [!NOTE] > [!INCLUDE [updating-admin-interfaces](includes/updating-admin-interfaces.md)] -## Turn on or off entry and exit announcements with PowerShell - -To turn entry and exit announcements on or off with PowerShell, use the **`-EnableNameRecording`** parameter within the PowerShell CsOnlineDialInConferencingTenantSettings cmdlet. +## Manage whether callers can record their names with PowerShell -For CsOnlineDialInConferencingBridge script examples, see [Set-CsOnlineDialInConferencingBridge](/powershell/module/teams/Set-csonlinedialinconferencingtenantsettings). +To manage whether callers can record their names with PowerShell, use the **`-EnableNameRecording`**. **`-EntryExitAnnouncementsType`**, and **`-EnableNameRecording`** parameters, within the PowerShell [Set-CsOnlineDialInConferencingTenantSettings](/powershell/module/teams/set-csonlinedialinconferencingtenantsettings) cmdlet. For script examples, see [Set-CsOnlineDialInConferencingBridge](/powershell/module/teams/Set-csonlinedialinconferencingtenantsettings). ## Related topics - [Change the settings for an audio conferencing bridge](change-the-settings-for-an-audio-conferencing-bridge.md) +- [Turn on or off entry and exit announcements for meetings in Teams](turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md) diff --git a/Teams/end-to-end-encrypted-meetings.md b/Teams/end-to-end-encrypted-meetings.md index 1391d279f9..17133caa81 100644 --- a/Teams/end-to-end-encrypted-meetings.md +++ b/Teams/end-to-end-encrypted-meetings.md @@ -23,7 +23,7 @@ description: Learn how to enable end-to-end encryption for Teams meetings. # Require end-to-end encryption for sensitive Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] diff --git a/Teams/enhanced-teams-experience.md b/Teams/enhanced-teams-experience.md index cc8aab061d..a2c755013c 100644 --- a/Teams/enhanced-teams-experience.md +++ b/Teams/enhanced-teams-experience.md @@ -41,17 +41,6 @@ This article, written for IT Pros and admins who are deploying and configuring T > > For admins to manage Teams Premium features, their tenant needs at least one user with an active [Teams Premium license](/MicrosoftTeams/teams-add-on-licensing/licensing-enhance-teams). -The following sections in this article describe the Teams Premium enhancements for: - -- [Protection and advanced management for meetings](#protection-and-advanced-management-for-meetings) -- [Personalized meetings](#personalized-meetings) -- [Premium events](#premium-events) -- [Virtual Appointments](#advanced-virtual-appointments) -- [Intelligent meeting features](#intelligent-meeting-features) -- [Custom 3D Immersive Mesh Experiences](#custom-3d-immersive-mesh-experiences) -- [Intelligent call recap](#intelligent-call-recap) -- [Queues app](#queues-app) - For more general information about Teams meetings and premium events, see the following articles: - [Meetings, webinars, and town halls](overview-meetings-webinars-town-halls.md) @@ -72,6 +61,8 @@ Teams Premium provides more ways to safeguard and monitor users' Teams experienc - **Custom user policy packages** - Create policy packages to simplify, streamline, and help provide consistency when managing policies for groups of users across your organization. +- **Microsoft eCDN** - Optimize network performance for video streaming within an enterprise network. Microsoft eCDN allows millions of enterprise users around the world to communicate face-to-face efficiently and reliably. Organizers with a Teams Premium license use the Microsoft eCDN by default, but you can also select one of our partner providers for these organizers. + - **End-to-end encryption** - Enforced through a sensitivity label, end-to-end encryption provides increased security for meetings that require a higher level of protection. - **Hide attendee names** - Meeting and webinar organizers can hide the names of attendees from other attendees in the stage, roster, and chat. @@ -82,7 +73,7 @@ Teams Premium provides more ways to safeguard and monitor users' Teams experienc - **Screen sharing quality alerts** - Set up alerts for in-progress meeting screen sharing issues and get notified immediately when your specified users experience issues. -- **Sensitivity labels** - Extended capabilities for sensitivity labels to control meeting settings normally controlled by the meeting organizer. These capabilities include new settings to control lobby, chat, chat copy, presentation, and recording functions. +- **Sensitivity labels** - Extended capabilities for sensitivity labels to control meeting and event settings normally controlled by the organizer. These capabilities include new settings to control lobby, chat, chat copy, presentation, and recording functions. - **Real time telemetry and retention** - Real-time telemetry is gathered automatically for all users who have a Teams Premium license and retained for seven days. @@ -90,30 +81,32 @@ Teams Premium provides more ways to safeguard and monitor users' Teams experienc - **Video quality alerts** - Set up alerts for in-progress meeting video issues and get notified immediately when your specified users experience issues. -- **Watermarking** - Enforced through a sensitivity label, watermarks display the email address of a meeting participant. Watermarks are useful for protecting confidential information shared in meetings. - -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | -| --------- | -----------| ----------- | ------------ | -| Advanced collaboration analytics |No, contact support for assistance.| [Advanced Collaboration Analytics for Microsoft Teams](advanced-collaboration-analytics.md) | No end-user control | -| Audio quality alerts |Yes, you can add or remove users.| [Alerts for in-progress meeting audio quality issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-audio) | No end-user control | -| Custom user policy packages |Yes| [Managing policy packages in Teams](manage-policy-packages.md) | No end-user control | -| End-to-end encryption (E2EE) | Yes |[Encryption for sensitive meetings](end-to-end-encrypted-meetings.md) | [Use encryption](https://support.microsoft.com/office/use-end-to-end-encryption-for-teams-meetings-a8326d15-d187-49c4-ac99-14c17dbd617c) | -| Hide attendee names | Yes |[Allow meeting and webinar organizers to hide the names of attendees](hide-attendee-names.md) | [Hide attendee names in Teams meetings and webinars](https://support.microsoft.com/office/hide-attendee-names-in-teams-meetings-and-webinars-00389c74-ee61-48b5-bad8-8295600085ed) | -| Manage what attendees see | No, contact support for assistance.| No admin control | [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)| -| Prevent copying chat content to clipboard |Yes, use the Teams admin center to add or delete chat content copying restrictions in your meeting templates. Use the Microsoft Purview compliance portal to turn labels with chat content copying restrictions on or off.| [Manage chat for sensitive Teams meetings](manage-chat-sensitive-meetings.md) | No end-user control | -| Prevent users from sharing content in external meetings|Yes| [Prevent users from sharing content in external meetings](block-external-content-share.md) | No end-user control | -| Real-time telemetry and retention|No, contact support for assistance.| [Use real-time telemetry to troubleshoot poor meeting quality](use-real-time-telemetry-to-troubleshoot-poor-meeting-quality.md#where-to-find-per-user-real-time-troubleshooting-telemetry) | No end-user control | -| Restrict who can record | Yes, use the Teams admin center to add or delete recording restrictions in your meeting templates. Use the Microsoft Purview compliance portal to turn labels with recording restrictions on or off.|[Manage recordings for sensitive meetings](manage-meeting-recording-options.md) | [Record a meeting](https://support.microsoft.com/office/record-a-meeting-in-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24?storagetype=stage#bkmk_whocanstartorstoparecording) | -| Screen sharing quality alerts|Yes, you can add or remove users.| [Alerts for in-progress meeting screen sharing issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-screen-sharing) | No end-user control | -| Sensitivity labels | Yes, use the Microsoft Purview compliance portal to turn labels on or off.|[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) | [Sensitivity labels for Teams meetings](https://support.microsoft.com/office/sensitivity-labels-for-teams-meetings-2b244d1d-72d0-471e-8e58-c41079e190fb)| -| Teams Premium feature usage report|No, contact support for assistance.| [Teams Premium feature usage report](/microsoftteams/teams-analytics-and-reports/teams-premium-usage-report) | No end-user control | -| Templates, labels, and policies |Yes, use the Teams admin center to add or delete meeting templates. Use the Microsoft Purview compliance portal to turn labels on or off.| [Templates, sensitivity labels, and policies](meeting-templates-sensitivity-labels-policies.md) | [Use custom templates](https://support.microsoft.com/office/use-custom-templates-for-teams-meetings-78279be9-3283-4999-b24e-96fb0da2fb4f) | -| Video quality alerts|Yes, you can add or remove users.| [Alerts for in-progress meeting video quality issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-video) | No end-user control | -| Watermarks | Yes | [Require a watermark for meetings](watermark-meeting-content-video.md) | [Watermarks for meetings](https://support.microsoft.com/office/watermark-for-teams-meetings-a9166432-f429-4a19-9a72-c9e8fdf4f589)| +- **Watermarking** - Enforced through a sensitivity label, watermarks display the email address of a meeting or webinar participant. Watermarks are useful for protecting confidential information shared in meetings and webinars. + + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | + | --------- | -----------| ----------- | ------------ | + | Advanced collaboration analytics |No, contact support for assistance.| [Advanced Collaboration Analytics for Microsoft Teams](advanced-collaboration-analytics.md) | No end-user control | + | Audio quality alerts |Yes, you can add or remove users.| [Alerts for in-progress meeting audio quality issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-audio) | No end-user control | + | Custom user policy packages |Yes| [Managing policy packages in Teams](manage-policy-packages.md) | No end-user control | + | End-to-end encryption (E2EE) | Yes |[Encryption for sensitive meetings](end-to-end-encrypted-meetings.md) | [Use encryption](https://support.microsoft.com/office/use-end-to-end-encryption-for-teams-meetings-a8326d15-d187-49c4-ac99-14c17dbd617c) | + | Hide attendee names | Yes |[Allow meeting and webinar organizers to hide the names of attendees](hide-attendee-names.md) | [Hide attendee names in Teams meetings and webinars](https://support.microsoft.com/office/hide-attendee-names-in-teams-meetings-and-webinars-00389c74-ee61-48b5-bad8-8295600085ed) | + | Manage what attendees see | No, contact support for assistance.| No admin control | [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)| + | Manage which eCDN provider view-only meetings use |Yes |[Enterprise content delivery networks for streaming Microsoft Teams events](streaming-ecdn-enterprise-content-delivery-network.md#manage-the-ecdn-solution-for-premium-town-halls-and-view-only-meetings)|No end user control | + | Microsoft eCDN |Yes |[How to enable Microsoft eCDN](/ecdn/how-to/enable-microsoft-ecdn-for-your-tenant)|No end user control | + | Prevent copying chat content to clipboard |Yes, use the Teams admin center to add or delete chat content copying restrictions in your meeting templates. Use the Microsoft Purview compliance portal to turn labels with chat content copying restrictions on or off.| [Manage chat for sensitive Teams meetings](manage-chat-sensitive-meetings.md) | No end-user control | + | Prevent users from sharing content in external meetings|Yes| [Prevent users from sharing content in external meetings](block-external-content-share.md) | No end-user control | + | Real-time telemetry and retention|No, contact support for assistance.| [Use real-time telemetry to troubleshoot poor meeting quality](use-real-time-telemetry-to-troubleshoot-poor-meeting-quality.md#where-to-find-per-user-real-time-troubleshooting-telemetry) | No end-user control | + | Restrict who can record | Yes, use the Teams admin center to add or delete recording restrictions in your meeting templates. Use the Microsoft Purview compliance portal to turn labels with recording restrictions on or off.|[Manage recordings for sensitive meetings](manage-meeting-recording-options.md) | [Record a meeting](https://support.microsoft.com/office/record-a-meeting-in-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24?storagetype=stage#bkmk_whocanstartorstoparecording) | + | Screen sharing quality alerts|Yes, you can add or remove users.| [Alerts for in-progress meeting screen sharing issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-screen-sharing) | No end-user control | + | Sensitivity labels | Yes, use the Microsoft Purview compliance portal to turn labels on or off.|[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) | [Sensitivity labels for Teams meetings](https://support.microsoft.com/office/sensitivity-labels-for-teams-meetings-2b244d1d-72d0-471e-8e58-c41079e190fb)| + | Teams Premium feature usage report|No, contact support for assistance.| [Teams Premium feature usage report](/microsoftteams/teams-analytics-and-reports/teams-premium-usage-report) | No end-user control | + | Templates, labels, and policies |Yes, use the Teams admin center to add or delete meeting templates. Use the Microsoft Purview compliance portal to turn labels on or off.| [Templates, sensitivity labels, and policies](meeting-templates-sensitivity-labels-policies.md) | [Use custom templates](https://support.microsoft.com/office/use-custom-templates-for-teams-meetings-78279be9-3283-4999-b24e-96fb0da2fb4f) | + | Video quality alerts|Yes, you can add or remove users.| [Alerts for in-progress meeting video quality issues](/MicrosoftTeams/alerts/alerts-in-progress-meeting-video) | No end-user control | + | Watermarks | Yes | [Require a watermark for meetings](watermark-meeting-content-video.md) | [Watermarks for meetings](https://support.microsoft.com/office/watermark-for-teams-meetings-a9166432-f429-4a19-9a72-c9e8fdf4f589)| ## Personalized meetings -Teams Premium provides more ways to personalize your Teams meeting experiences with the following key features: +Teams Premium provides more ways to personalize your Teams meeting experiences with the following key features. For an overview on personalized meetings, see [Custom meetings overview](custom-meetings-overview.md): - **Custom meeting backgrounds for organizations** - Create and define custom meeting backgrounds that your users can use during meetings and events. @@ -125,13 +118,13 @@ Teams Premium provides more ways to personalize your Teams meeting experiences w - **Real Time Messaging Protocol (RTMP)-In** - Organizers can produce their Teams meetings directly from an external hardware or software-based encoder. -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | -| -------------------- | ----------- | ----------- | ------------ | -| Custom meeting backgrounds for organizations | Yes| [Meeting backgrounds](custom-meeting-backgrounds.md)| [Use meeting themes](https://support.microsoft.com/office/use-meeting-themes-for-teams-meetings-fbfd826d-1112-4790-918a-5a82cac8250e) | -| Custom together mode scenes for organizations | No, contact support for assistance.|[Content for you and your developers](/microsoftteams/platform/apps-in-teams-meetings/teams-together-mode)| | -| Meeting templates | Yes| - [Overview](custom-meeting-templates-overview.md)
- [Create a custom meeting template](create-custom-meeting-template.md)| [Use custom templates](https://support.microsoft.com/office/use-custom-templates-for-teams-meetings-78279be9-3283-4999-b24e-96fb0da2fb4f) | -| Meeting themes | Yes| [Themes for Teams meetings](meeting-themes.md) | [Use meeting themes](https://support.microsoft.com/office/use-meeting-themes-for-teams-meetings-fbfd826d-1112-4790-918a-5a82cac8250e) | -| RTMP-In | Yes| [Manage RTMP-In for Teams meetings](meetings-rtmp-in.md)|[Use RTMP-In in a Teams meeting](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f) | + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | + | -------------------- | ----------- | ----------- | ------------ | + | Custom meeting backgrounds for organizations | Yes| [Meeting backgrounds](custom-meeting-backgrounds.md)| [Use meeting themes](https://support.microsoft.com/office/use-meeting-themes-for-teams-meetings-fbfd826d-1112-4790-918a-5a82cac8250e) | + | Custom together mode scenes for organizations | No, contact support for assistance.|[Content for you and your developers](/microsoftteams/platform/apps-in-teams-meetings/teams-together-mode)| | + | Meeting templates | Yes| - [Overview](custom-meeting-templates-overview.md)
- [Create a custom meeting template](create-custom-meeting-template.md)| [Use custom templates](https://support.microsoft.com/office/use-custom-templates-for-teams-meetings-78279be9-3283-4999-b24e-96fb0da2fb4f) | + | Meeting themes | Yes| [Themes for Teams meetings](meeting-themes.md) | [Use meeting themes](https://support.microsoft.com/office/use-meeting-themes-for-teams-meetings-fbfd826d-1112-4790-918a-5a82cac8250e) | + | RTMP-In | Yes| [Manage RTMP-In for Teams meetings](meetings-rtmp-in.md)|[Use RTMP-In in a Teams meeting](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f) | ## Premium events @@ -148,22 +141,24 @@ The following sections describe Teams Premium feature enhancements for town hall Teams Premium provides more ways to elevate Teams town halls in your org with the following key features: - **Custom emails for town halls** - Organizers and co-organizers can customize the town hall email templates sent to attendees. -- **Increased broadcast and Q&A capacity**- Organizers can broadcast their town halls to 20,000 attendees. All attendees can use Q&A to interact with presenters, organizers, and co-organizers. +- **Event chat** - Organizers can allow attendees to use chat during town halls. +- **Increased broadcast and Q&A capacity** - Organizers can broadcast their town halls to 20,000 attendees. All attendees can use Q&A to interact with presenters, organizers, and co-organizers. - **Live translated captions**- Organizers can choose up to 10 languages for attendees to use when translating captions during the town hall. - **Microsoft eCDN** - Optimize network performance for video streaming within an enterprise network. Microsoft eCDN allows millions of enterprise users around the world to communicate face-to-face efficiently and reliably. You can use the Microsoft eCDN or select one of our partner providers for Premium town halls. - **Real time monitoring of the attendee experience** - Admins can use the eCDN analytics dashboard to troubleshoot the attendee experience during live town halls. - **Town hall attendee reactions** - Organizers can allow attendees to engage and provide feedback during a town hall with live reactions. - **Town hall insights** - Town hall organizers can troubleshoot town halls while they're live. -| Feature/Task | Can admins turn this feature on/off? |Documentation for admins| Documentation for your end users | -| -------------------- | ----------- | ----------- | ----------- | -| Custom emails for town halls | Yes | [Manage email communications](manage-email-communications.md) |[Schedule a town hall in Microsoft Teams](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_town_hall_invites) | -| Live translated captions | Yes |[Configure transcription and captions for Teams meetings](meeting-transcription-captions.md)|[Use live captions in Microsoft Teams meetings](https://support.microsoft.com/office/use-live-captions-in-microsoft-teams-meetings-4be2d304-f675-4b57-8347-cbd000a21260) | -| Microsoft eCDN |Yes |[How to enable Microsoft eCDN](/ecdn/how-to/enable-microsoft-ecdn-for-your-tenant)|No end user control | -| Manage which eCDN provider Premium town halls use |Yes |[Enterprise content delivery networks for streaming Microsoft Teams events](streaming-ecdn-enterprise-content-delivery-network.md#manage-the-ecdn-solution-for-premium-town-halls)|No end user control | -| Real time monitoring of the attendee experience | No, contact support for assistance. |[eCDN Analytics](/ecdn/technical-documentation/analytics)|No end user control | -| Town hall attendee reactions | No, contact support for assistance. | No admin control|[Schedule a town hall in Microsoft Teams](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_townhall_reactions) | -| Town hall insights | No, contact support for assistance. | No admin control|[Town hall insights in Microsoft Teams](https://support.microsoft.com/office/town-hall-insights-in-microsoft-teams-def99575-61bf-4ea2-ad0e-c6e75dce7741) | + | Feature/Task | Can admins turn this feature on/off? |Documentation for admins| Documentation for your end users | + | -------------------- | ----------- | ----------- | ----------- | + | Custom emails for town halls | Yes | [Manage email communications](manage-email-communications.md) |[Schedule a town hall in Microsoft Teams](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_town_hall_invites) | + | Event chat| Yes | [Manage event chat for Microsoft Teams town halls](town-hall-chat.md) |[Chat in a town hall in Microsoft Teams](https://support.microsoft.com/office/chat-in-a-town-hall-in-microsoft-teams-a4a0e102-ca45-4605-a0a8-83a884547338) | + | Live translated captions | Yes |[Configure transcription and captions for Teams meetings](meeting-transcription-captions.md)|[Use live captions in Microsoft Teams meetings](https://support.microsoft.com/office/use-live-captions-in-microsoft-teams-meetings-4be2d304-f675-4b57-8347-cbd000a21260) | + | Manage which eCDN provider Premium town halls use |Yes |[Enterprise content delivery networks for streaming Microsoft Teams events](streaming-ecdn-enterprise-content-delivery-network.md#manage-the-ecdn-solution-for-premium-town-halls-and-view-only-meetings)|No end user control | + | Microsoft eCDN |Yes |[How to enable Microsoft eCDN](/ecdn/how-to/enable-microsoft-ecdn-for-your-tenant)|No end user control | + | Real time monitoring of the attendee experience | No, contact support for assistance. |[eCDN Analytics](/ecdn/technical-documentation/analytics)|No end user control | + | Town hall attendee reactions | No, contact support for assistance. | No admin control|[Schedule a town hall in Microsoft Teams](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_townhall_reactions) | + | Town hall insights | No, contact support for assistance. | No admin control|[Town hall insights in Microsoft Teams](https://support.microsoft.com/office/town-hall-insights-in-microsoft-teams-def99575-61bf-4ea2-ad0e-c6e75dce7741) | ### Webinars @@ -178,15 +173,15 @@ Teams Premium provides more ways to elevate Teams webinars in your org with the - **Manually approve registrants** - Organizers can approve or deny requests to register for their webinar. - **Real Time Messaging Protocol (RTMP)-In** - Organizers can produce their Teams webinar directly from an external hardware or software-based encoder. -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | -| -------------------- | ----------- | ----------- | ----------- | -| Custom emails for webinars| Yes| [Manage email communications](manage-email-communications.md) |[Manage webinar emails in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-emails-in-microsoft-teams-d0006848-f707-494f-b0a4-eeebcbc723be) | -| Enable and manage the waitlist for webinars beyond capacity| No, contact support for assistance.| No admin control|[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | -| Hide attendee names | Yes | [Allow meeting and webinar organizers to hide the names of attendees](hide-attendee-names.md) | [Hide attendee names in Teams meetings and webinars](https://support.microsoft.com/office/hide-attendee-names-in-teams-meetings-and-webinars-00389c74-ee61-48b5-bad8-8295600085ed)| -| Limit registration start and end times | No, contact support for assistance.| No admin control|[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | -| Manage what attendees see | No, contact support for assistance.| No admin control | [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)| -| Manually approve registrants |No, contact support for assistance.| No admin control |[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | -| RTMP-In | Yes| [Manage RTMP-In for Teams meetings](meetings-rtmp-in.md)|[Use RTMP-In in a Teams meeting](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f) | + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | + | -------------------- | ----------- | ----------- | ----------- | + | Custom emails for webinars| Yes| [Manage email communications](manage-email-communications.md) |[Manage webinar emails in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-emails-in-microsoft-teams-d0006848-f707-494f-b0a4-eeebcbc723be) | + | Enable and manage the waitlist for webinars beyond capacity| No, contact support for assistance.| No admin control|[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | + | Hide attendee names | Yes | [Allow meeting and webinar organizers to hide the names of attendees](hide-attendee-names.md) | [Hide attendee names in Teams meetings and webinars](https://support.microsoft.com/office/hide-attendee-names-in-teams-meetings-and-webinars-00389c74-ee61-48b5-bad8-8295600085ed)| + | Limit registration start and end times | No, contact support for assistance.| No admin control|[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | + | Manage what attendees see | No, contact support for assistance.| No admin control | [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)| + | Manually approve registrants |No, contact support for assistance.| No admin control |[Manage webinar registration in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-registration-in-microsoft-teams-923f382a-0cca-433a-b38d-7461971192d1) | + | RTMP-In | Yes| [Manage RTMP-In for Teams meetings](meetings-rtmp-in.md)|[Use RTMP-In in a Teams meeting](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f) | ## Advanced Virtual Appointments @@ -202,10 +197,10 @@ Teams Premium provides advanced Virtual Appointment capabilities, such as: - Queue of scheduled and on-demand appointments - Short Message Service (SMS) notifications -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins | -| -------------------- | ----------- | ----------- | -| Reporting | No, contact support for assistance.| [Virtual Appointments usage report](/microsoft-365/frontline/virtual-appointments-usage-report?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json)
[Advanced Virtual Appointments activity report](/microsoft-365/frontline/advanced-virtual-appointments-activity-report?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json) | -| SMS notifications | Yes| [SMS text notifications](bookings-app-admin.md#sms-text-notifications) | + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins | + | -------------------- | ----------- | ----------- | + | Reporting | No, contact support for assistance.| [Virtual Appointments usage report](/microsoft-365/frontline/virtual-appointments-usage-report?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json)
[Advanced Virtual Appointments activity report](/microsoft-365/frontline/advanced-virtual-appointments-activity-report?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json) | + | SMS notifications | Yes| [SMS text notifications](bookings-app-admin.md#sms-text-notifications) | ## Intelligent meeting features @@ -216,12 +211,12 @@ Teams Premium provides the following key AI-powered meetings features: - **Live translated captions** - Allow your users to see captions translated into the language they’re most comfortable with. - **Live translated transcription** - Your users can understand each other better during a meeting or event by translating the meeting transcript into the language they're most comfortable with. -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | -| -------------------- | -----------| ----------- | ------------ | -| Decorate my background | No, contact support for assistance. | No admin control | [Decorate your background](https://adoption.microsoft.com/microsoft-teams-premium/decorate-your-background/)| -| Intelligent meeting recap| No, contact support for assistance.1|[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) | [Meeting recap in Microsoft Teams](https://support.microsoft.com/office/meeting-recap-in-microsoft-teams-c2e3a0fe-504f-4b2c-bf85-504938f110ef#bkmk_intelligent_meeting_recap) | -| Live translated captions | Yes | [Configure transcription and captions for Teams meetings](meeting-transcription-captions.md)|[Use live captions in Microsoft Teams meetings](https://support.microsoft.com/office/use-live-captions-in-microsoft-teams-meetings-4be2d304-f675-4b57-8347-cbd000a21260) | -| Live translated transcription | Yes | [Configure transcription and captions for Teams meetings](meeting-transcription-captions.md) | [View live transcription in Microsoft Teams meetings](https://support.microsoft.com/office/view-live-transcription-in-microsoft-teams-meetings-dc1a8f23-2e20-4684-885e-2152e06a4a8b)| + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins | Documentation for your end users | + | -------------------- | -----------| ----------- | ------------ | + | Decorate my background | No, contact support for assistance. | No admin control | [Decorate your background](https://adoption.microsoft.com/microsoft-teams-premium/decorate-your-background/)| + | Intelligent meeting recap| No, contact support for assistance.1|[Data, privacy, and security for intelligent recap in Teams Premium](/microsoftteams/privacy/intelligent-recap) | [Meeting recap in Microsoft Teams](https://support.microsoft.com/office/meeting-recap-in-microsoft-teams-c2e3a0fe-504f-4b2c-bf85-504938f110ef#bkmk_intelligent_meeting_recap) | + | Live translated captions | Yes | [Configure transcription and captions for Teams meetings](meeting-transcription-captions.md)|[Use live captions in Microsoft Teams meetings](https://support.microsoft.com/office/use-live-captions-in-microsoft-teams-meetings-4be2d304-f675-4b57-8347-cbd000a21260) | + | Live translated transcription | Yes | [Configure transcription and captions for Teams meetings](meeting-transcription-captions.md) | [View live transcription in Microsoft Teams meetings](https://support.microsoft.com/office/view-live-transcription-in-microsoft-teams-meetings-dc1a8f23-2e20-4684-885e-2152e06a4a8b)| 1If you toggle the **Transcription** and **Recording** settings to **Off** in your **Meeting policies**, intelligent meeting recap isn't available for users with this policy. @@ -236,13 +231,34 @@ Teams Premium provides custom Mesh experience capabilities for your users, such - **Create custom avatars, explore environments, and communicate virtually** - Customizable avatars can navigate around 3D environments to experience content and have multiple simultaneous discussions with colleagues using spatial audio built-in to the experience. - **Integrated with Microsoft 365** - Mesh provides enterprise-grade security and privacy, built on trusted platforms. + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins |Documentation for end users | + | -------------------- | ----------- | ----------- |----------- | + | Set up Mesh | Yes, use [App centric management](app-centric-management.md) to allow or prevent users from using Mesh.| [Configure Microsoft Mesh](/mesh/setup/content/setup-m365-mesh)
[Preparing your organization for Mesh](/mesh/setup/content/preparing-your-organization) | No end user control.| + | Create your event | Yes| No admin control. |[Overview of Mesh events](/mesh/events-guide/events-overview) | + | Customize your avatar | Yes| No admin control. |[Personalize your avatar](/mesh/user-guide/avatars) | + | Develop a custom environment | Yes| No admin control. |[Mesh Development Overview](/mesh/develop/development-overview) | + | Download the Mesh app | Yes| No admin control. |[Getting started with events in Microsoft Mesh](/mesh/user-guide/getting-started) | + +## Advanced Places workplace collaboration + +Microsoft Places allows you and your organization to build a smart workplace. With a Teams Premium license, your users can experience advanced features that support the booking experience in Places. As an admin, you have access advanced management capabilities and reports. + +Teams Premium provides the following advanced capabilities in Places: + +- **Auto release and check-in for rooms** - If you create auto release for rooms, when a room that you enable for auto release isn't being used, Teams and Places free up the room for others to reserve. +- **Individual desk booking** - Allow users to select and book individual desks for their day in the office. +- **Places explorer** - Get a singular view of the people, spaces, and experiences at each workplace location.​ +- **Places finder** - Your users can book and check into workspaces, as well as use seat assignments to sit near collaborators. +- **Quick book** - For in-office meetings without a space booked, your users can get intelligent suggestions for each meeting for the day and book at once in bulk. +- **Space analytics** - You can learn which desks and rooms are most frequently used, and get suggestions on how to optimize space management. You can also identify trends for key buildings, bookable rooms, and shared work spaces. +- **Team guidance** - Managers and leaders in your organization can find the best work patterns for teams by establishing expectations and adjusting the rhythm to meet the needs of the group. + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins |Documentation for end users | | -------------------- | ----------- | ----------- |----------- | -| Set up Mesh | Yes, use [App centric management](app-centric-management.md) to allow or prevent users from using Mesh.| [Configure Microsoft Mesh](/mesh/setup/content/setup-m365-mesh)
[Preparing your organization for Mesh](/mesh/setup/content/preparing-your-organization) | No end user control.| -| Create your event | Yes| No admin control. |[Overview of Mesh events](/mesh/events-guide/events-overview) | -| Customize your avatar | Yes| No admin control. |[Personalize your avatar](/mesh/user-guide/avatars) | -| Develop a custom environment | Yes| No admin control. |[Mesh Development Overview](/mesh/develop/development-overview) | -| Download the Mesh app | Yes| No admin control. |[Getting started with events in Microsoft Mesh](/mesh/user-guide/getting-started) | +| Auto release for rooms| Yes|[How to enable specific rooms for Auto Release](/microsoft-365/places/enable-auto-release) | [Overview of Auto Release](/microsoft-365/places/enable-auto-release#room-check-in-and-autorelease-experience)| +| Individual desk booking| Yes|[Configure desk pools and workspaces (optional)](/microsoft-365/places/setting-up-desk-workspaces-in-places-finder) | [Get started with Microsoft Places](https://support.microsoft.com/office/get-started-with-microsoft-places-49b7ea21-b9e1-4ccd-acd6-c600f3da633c)| +| Places finder| Yes| [Enabling Microsoft Places Finder in Outlook](/microsoft-365/places/enabling-places-finder) |[Get started with Microsoft Places](https://support.microsoft.com/office/get-started-with-microsoft-places-49b7ea21-b9e1-4ccd-acd6-c600f3da633c)| +| Space analytics| Yes, remove users from the Places Advanced and Analytics Users [security groups](/microsoft-365/places/places-analytics). |[Microsoft Places Analytics](/microsoft-365/places/places-analytics) | [Get started with Microsoft Places](https://support.microsoft.com/office/get-started-with-microsoft-places-49b7ea21-b9e1-4ccd-acd6-c600f3da633c)| ## Calls @@ -255,19 +271,19 @@ Teams Premium provides custom Mesh experience capabilities for your users, such ### Queues app -Teams Premium and Teams Phone provides access to Queues app, a Teams-native solution that unlocks a set of advanced call functionalities for Teams Phone Call queues and Auto attendants, such as: +Teams Premium and Teams Phone provide access to Queues app, a Teams-native solution that unlocks a set of advanced call functionalities for Teams Phone Call queues and Auto attendants, such as: - **Call queue management**: Admins can now delegate authorized users, also known as leads or supervisors, to manage and configure Call queues and Auto attendants directly from the Teams client. Authorized users can configure Call queues and Auto attendants from Call settings and they can opt agents into and out of the queue from Queues app. - **Real-time metrics**: The number of waiting calls, average wait time, longest call waiting time metrics, and more are included in real-time metrics within the Queues app. The analytics report shows activity made in the queue from 12:00 AM local time of the signed in user. For more information on real-time reports, see [Auto attendant and Call queue real-time reports](aa-cq-real-time-reports.md). - **Historical reporting**: View historical metrics for call queues, and auto attendants, and agent queue actions. Historical metrics report up to the past 27 days. For more information on historical reports, see [Auto attendant and Call queue historical reports](aa-cq-cqd-historical-reports.md). -| Feature/Task | Can admins turn this feature on/off? | Documentation for admins |Documentation for end users | -| -------------------- | ----------- | ----------- |----------- | -|Call queue management|Yes, with [voice application policies](manage-voice-applications-policies.md) for Authorized users|[Manage the Queues app for Microsoft Teams](manage-queues-app.md)|[Use the Queues app for Microsoft Teams](https://support.microsoft.com/office/370ad83e-c2c1-4a9f-8a59-16c98be102e9)| -|Real-time metrics|Yes, with [voice application policies](manage-voice-applications-policies.md) for Authorized users|[Auto attendant and Call queue real-time reports](aa-cq-real-time-reports.md)|No end user control, can view reports if authorized.| -|Historical reporting|Yes, with voice application policies for Authorized users|[Auto attendant and Call queue historical reports](aa-cq-cqd-historical-reports.md)|No end user control, can view reports if authorized.| + | Feature/Task | Can admins turn this feature on/off? | Documentation for admins |Documentation for end users | + | -------------------- | ----------- | ----------- |----------- | + |Call queue management|Yes, with [voice application policies](manage-voice-applications-policies.md) for Authorized users|[Manage the Queues app for Microsoft Teams](manage-queues-app.md)|[Use the Queues app for Microsoft Teams](https://support.microsoft.com/office/370ad83e-c2c1-4a9f-8a59-16c98be102e9)| + |Real-time metrics|Yes, with [voice application policies](manage-voice-applications-policies.md) for Authorized users|[Auto attendant and Call queue real-time reports](aa-cq-real-time-reports.md)|No end user control can view reports if authorized.| + |Historical reporting|Yes, with voice application policies for Authorized users|[Auto attendant and Call queue historical reports](aa-cq-cqd-historical-reports.md)|No end user control can view reports if authorized.| -Queues app is in public preview and is enabled by default for all Teams users in your organization who are assigned both a Teams Premium and Teams Phone license and who and are voice enabled. +Queues app is now generally available and is enabled by default for all Teams users in your organization who are assigned both a Teams Premium and Teams Phone license and who and are voice enabled. For more information about Queues app, see [Manage the Queues app for Microsoft Teams](manage-queues-app.md). For end user documentation, see [Use the Queues app for Microsoft Teams](https://support.microsoft.com/office/370ad83e-c2c1-4a9f-8a59-16c98be102e9). diff --git a/Teams/export-teams-content.md b/Teams/export-teams-content.md index 0ff87756dd..b7a06b3850 100644 --- a/Teams/export-teams-content.md +++ b/Teams/export-teams-content.md @@ -55,10 +55,6 @@ Here are some examples on how you can use these export APIs: To learn more about Teams Retention policy, see the [Manage retention policies for Microsoft Teams](/microsoftteams/retention-policies) for further details. -## What isn't supported by the Teams Export APIs? - -- **Teams Copilot Interactions & Microsoft 365 Chat:** Export API doesn't support user to Copilot interaction messages and Microsoft 365 chat messages sent by the bot. - ## How to access Teams Export APIs - **Example 1** is a simple query to retrieve all the messages of a user or team without any filters: @@ -100,7 +96,6 @@ Here are some examples on how you can use these export APIs: GET https://graph.microsoft.com/v1.0/users/{id}/onlineMeetings/getAllTranscripts(meetingOrganizerUserId='{userId}',startDateTime={startDateTime},endDateTime={endDateTime}) ``` - > [!NOTE] > The API returns response with next page link in case of multiple results. For getting next set of results, simply call GET on the url from @odata.nextlink. If @odata.nextlink isn't present or null then all messages are retrieved. @@ -338,7 +333,6 @@ No model declaration enables access to APIs with limited usage per each requesti For more information, see [Use Graph APIs to fetch transcript](/microsoftteams/platform/graph-api/meeting-transcripts/api-transcripts#get-calltranscript-content). - ## Export API filters Export API hosted on the Teams Graph Service gets all user messages from the Substrate user mailbox using `users/{userId}/chats/getAllMessages`. Export API retrieves both sent and received messages for a user which leads to export of duplicate messages when calling the API for all users in the chat thread. @@ -396,3 +390,26 @@ $filter=from/application/applicationIdentityType eq '' or from/user/id - the query returns messages sent by the system if `messageType eq 'systemEventMessage'` is present These parameters can be combined between them using the OR operators as well as by combining with the `lastModifiedDateTime` `$filter` parameter. + +## Microsoft 365 Copilot Interactions & Microsoft 365 Chat (Preview) + +The new Copilot Activity Export API will allow you to export Copilot interactions data which includes the user prompt to Copilot and the Copilot response back to the user. This API will capture the user intent and Copilot accessed resources and the response back to the user across Microsoft 365 Copilot apps such as Teams, Word and Outlook. + +## How to access Copilot Activity Export APIs (Preview) + +- **Example 1** is a simple query to retrieve all the copilot interactions without any filters (beta): + + ```HTTP + GET https://graph.microsoft.com/beta/copilot/users/{id}/interactionHistory/getAllEnterpriseInteractions + ``` +- **Example 2** is a simple query to retrieve all the copilot interactions with appclass filters (beta): + + ```HTTP + GET https://graph.microsoft.com/beta/copilot/users/{id}/interactionHistory/getAllEnterpriseInteractions?$filter=appClass eq 'IPM.SkypeTeams.Message.Copilot.Teams or appClass eq 'IPM.SkypeTeams.Message.Copilot.BizChat' (beta) + ``` +## Prerequisites to access Copilot Activity Export APIs (Preview) + +Application permissions are used by apps that run without a signed-in user present; application permissions can only be approved by an administrator. The following permissions are needed: + + - *AiEnterpriseInteraction.Read.All*: enables access to all copilot interactions across Microsoft 365 apps and Microsoft 365 Chat + - A **Microsoft 365 Copilot license** is required for accessing the new Copilot Activity Export API. diff --git a/Teams/external-meeting-join.md b/Teams/external-meeting-join.md index ff90fc7b61..694a0467bf 100644 --- a/Teams/external-meeting-join.md +++ b/Teams/external-meeting-join.md @@ -26,7 +26,7 @@ description: Learn how to prevent or block users in your organization from joini # Prevent users from joining external Microsoft Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls As an admin, you can control which types of Microsoft Teams meetings users in your org can join. Managing the types of meetings your users can join can be helpful in privacy and compliance scenarios, where you might not want specific users or groups in your org joining meetings with external non-trusted trusted or even trusted organizations. diff --git a/Teams/facilitator-teams.md b/Teams/facilitator-teams.md new file mode 100644 index 0000000000..d7e46529ff --- /dev/null +++ b/Teams/facilitator-teams.md @@ -0,0 +1,134 @@ +--- +title: Set up Facilitator in Microsoft Teams for collaborative AI notes +author: DaniESmith +ms.author: danismith +manager: jtremper +ms.reviewer: solomon.alex, grace.culver +ms.date: 11/18/2024 +ms.topic: article +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +ms.collection: + - M365-collaboration +ms.custom: + - admindeeplinkTEAMS +f1.keywords: +- NOCSH +appliesto: + - Microsoft Teams +ms.localizationpriority: high +search.appverid: MET150 +description: Learn about how Facilitator in Microsoft Teams can take collaborative AI-generated notes powered by Copilot. +--- + +# Set up Facilitator in Microsoft Teams for collaborative AI-generated notes + +> [!IMPORTANT] +> This feature is currently in Teams Public preview. +> +> Features in preview might not be complete and could undergo changes before becoming available in the public release. They're provided for evaluation and exploration purposes only. + +Facilitator is a collaborative communication agent available to your users in Teams conversations. It combines the power of large language models (LLMs) and Teams data to record notes and help users be productive during collaboration. Stay in the flow of conversation and receive powerful, AI-generated notes within a single workspace. No need for users to switch from reference to reference or app to app. + +Use Facilitator in peer-to-peer: + +- Chats +- Meetings + +Unlike an individual user's queries to Copilot in Teams, Facilitator displays Copilot's notes within the group's conversation. Users can focus on the conversation and let Facilitator take care of the note-taking for everyone. + +Facilitator also continuously updates as the conversation progresses. For example, the AI-generated notes display the options being considered by the team and then replaces those options with a single choice once the group decides. Now, that's intelligent collaboration right in Teams. + +> [!IMPORTANT] +> Facilitator's notes are communally shared between collaborators. +> +> However, when an individual user queries Copilot in Teams using the Copilot in Teams pane, their queries and responses from Copilot remain private to that user. +> +> Users are shown a notice when their queries are private or shared with others. + +For more information about how users can integrate AI-generated notes into their Teams chats, see [Keep track of chats with AI notes in Microsoft Teams](https://support.microsoft.com/office/keep-track-of-chats-with-AI-notes-in-Microsoft-Teams-0b7efbd0-fd3e-48e7-9a4b-4ea22cdc12c0). + +For more information about how users can integrate AI-generated notes into their Teams meetings, see [Automate notetaking in Microsoft Teams meetings](https://support.microsoft.com/office/automate-notetaking-in-Microsoft-Teams-meetings-37657f91-39b5-40eb-9421-45141e3ce9f6). + +## Security, Compliance, and Privacy + +Facilitator, Copilot, and Microsoft 365 are built on Microsoft's comprehensive approach to security, compliance, and privacy. + +When you use Microsoft Purview for your security and compliance management, AI-generated notes are supported by new auditing events that surface in [Data Security Posture Management for AI](/purview/ai-microsoft-purview#data-security-posture-management-for-ai-provides-insights-policies-and-controls-for-ai-apps) and can be used by [eDiscovery with a KQL query](/purview/edisc-keyword-query-language). + +To automatically retain or delete the notes, use a Microsoft Purview Data Lifecycle Management retention policy with the **Teams chat** location for AI-generated notes in chat, and a retention policy for **OneDrive accounts** for AI-generated notes in meetings. + +Other Microsoft Purview solutions either aren't applicable for AI-generated notes or aren't yet supported. + +For more information about security and privacy in Microsoft 365 Copilot, see the following articles: + +- [Data, Privacy, and Security for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-privacy) for Microsoft 365 Copilot in your organization (work or school). +- [Microsoft Purview data security and compliance protections for generative AI apps](/purview/ai-microsoft-purview). +- [Copilot Pro: Microsoft 365 apps and your privacy](https://support.microsoft.com/office/copilot-pro-microsoft-365-apps-and-your-privacy-6f0d8d80-f4bb-4c9f-989e-64a4adfd62e5) for Microsoft 365 Copilot apps at home. + +### Facilitator limitations + +#### General Facilitator limitations + +- Currently, AI-generated notes aren't supported in [external chats and meetings](trusted-organizations-external-meetings-chat.md). +- Retention labels aren't currently supported for AI-generated notes, which includes applying retention labels for cloud attachments. + +#### AI-generated notes for meetings limitations + +- AI-generated notes for meetings aren't automatically collected as cloud attachments in [Microsoft Preview eDiscovery](/purview/ediscovery-cloud-attachments) because it isn't currently supported. +- Meeting settings like [Prevent copy and paste](manage-chat-sensitive-meetings.md#prevent-copying-or-forwarding-of-chat) and [Watermarks](watermark-meeting-content-video.md) aren't applied to AI-generated notes in meetings. +- AI-generated notes for meetings don't inherit the meeting's sensitivity label; however, a sensitivity label can be applied to the notes' Loop component in the [Loop app or OneDrive](/purview/sensitivity-labels-loop). + +## Prerequisites and licensing + +The following list contains the prerequisites for users to be able to access Facilitator features in Teams chats and meetings: + +- An eligible *Microsoft 365* base license. + - For the list of eligible base licenses, see [Understand licensing requirements for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-licensing). +- A *Microsoft 365 Copilot* license. + - For information on how to acquire *Microsoft 365 Copilot* licenses, see [Where can I get Microsoft Copilot?](https://support.microsoft.com/topic/where-can-i-get-microsoft-copilot-40a622db-6d25-4266-b008-4bbcb55cf52f). +- Be a Microsoft Teams Public preview participant. + - For information on how to access Teams Public preview features, see [Microsoft Teams Public preview](/microsoftteams/public-preview-doc-updates). + +## Turn on Facilitator for chats and meetings + +As an admin, you control whether Facilitator is available to your entire organization or to a certain group of users. + +Facilitator is turned on by default. However, if all apps are blocked for your organization, Facilitator will also be blocked. + +To turn off or on Facilitator for users, complete the following steps: + +### 1. Turn on Facilitator in the Teams admin center + +1. Sign in to the [Teams admin center](https://admin.teams.microsoft.com/dashboard) with your Teams admin credentials. +1. In the left rail navigation, select **Teams apps** > **Manage apps**. +1. In the apps list's search box, search for **Facilitator**. +1. Select **Facilitator** from the app list. +1. In the actions menu, select **Allow** or **Block**. +1. In the pop-up, select the **Allow** or **Block** button. + 1. AI-generated notes are turned on when **Facilitator** is turned on. + +You can also use [app centric management](/microsoftteams/app-centric-management) to allow and block, create policies, and assign users. + +For more information about managing apps in Teams, see [Manage apps](manage-apps.md). + +### 2. Allow Facilitator for a group of users + +To allow Facilitator for users, a new app policy needs to be created and then assigned to users. + +Follow the instructions at [Use app permission policies to control user access to apps](teams-app-permission-policies.md) to create a new app policy for Facilitator. + +You can then assign the policy to your entire tenant or to a select group of users. Follow the instructions at [Add or modify app availability for users](/microsoftteams/app-centric-management#add-or-modify-app-availability-for-users) to assign the policy to users using app-centric management. + +### 3. Turn on Loop experiences in Teams for AI-generated notes in meetings + +Loop experiences in Teams need to be turned on in order for AI to generate notes in Teams meetings. + +To turn on Loop experiences in Teams, follow the instructions at [Settings management for Loop functionality in Teams](/microsoft-365/loop/loop-components-configuration#settings-management-for-loop-functionality-in-teams). + +## Related articles + +- [What is responsible AI?](https://support.microsoft.com/topic/what-is-responsible-ai-33fc14be-15ea-4c2c-903b-aa493f5b8d92) +- [Frequently asked questions: AI, Microsoft Copilot, and Microsoft Designer](https://support.microsoft.com/topic/frequently-asked-questions-ai-microsoft-copilot-and-microsoft-designer-987b275d-f6f2-4d5d-94c5-e927cffae705) +- [Providing feedback about Microsoft Copilot with Microsoft 365 apps](https://support.microsoft.com/topic/providing-feedback-about-microsoft-copilot-with-microsoft-365-apps-c481c26a-e01a-4be3-bdd0-aee0b0b2a423?ocid=CopilotLab_SMC_Privacy_Feedback) diff --git a/Teams/flw-realwear.md b/Teams/flw-realwear.md deleted file mode 100644 index 288ba9c3b6..0000000000 --- a/Teams/flw-realwear.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: IT admin information for Microsoft Teams for RealWear client (Preview) -author: MicrosoftHeidi -ms.author: heidip -manager: jtremper -ms.topic: reference -ms.service: msteams -audience: admin -ms.reviewer: -ms.date: 03/30/2020 -description: IT admin walkthrough of the Microsoft Teams for RealWear client. -ms.localizationpriority: high -search.appverid: MET150 -f1.keywords: - - NOCSH -ms.collection: - - M365-collaboration - - remotework - - m365-frontline - - tier2 - - highpri -appliesto: - - Microsoft Teams ---- -# Microsoft Teams for RealWear - -This article covers the Microsoft Teams client for RealWear head-mounted wearables. Frontline workers using RealWear HMT-1 and HMT-1Z1 can now collaborate with a remote expert using video calling on Teams. Through a voice-controlled user interface, Teams for RealWear allows field workers to remain 100% hands-free while maintaining situational awareness in loud and hazardous environments. By showing what they see in real-time, field workers can accelerate the time to resolve issues and reduce the risk of an expensive downtime. - -## How to deploy Microsoft Teams for RealWear - -- RealWear devices updated to release 11.2 or above. More information [here](https://realwear.com/knowledge-center/configure-on-release-10/wireless-update/). -- Access to [RealWear Foresight](https://cloud.realwear.com/) for distributing the Microsoft Teams client for Realwear. - -## Required Licenses - -Microsoft Teams licenses are part of Microsoft 365 and Office 365 subscriptions. No additional licensing is required to use Teams for RealWear. For more information about getting Teams, check out [How do I get access to Microsoft Teams](https://support.office.com/article/fc7f1634-abd3-4f26-a597-9df16e4ca65b). - -## Managing RealWear devices - -### Microsoft Endpoint Manager - -RealWear devices can be managed using Android Device Administrator mode. Support for management via Android Enterprise is limited, as the devices currently don't have Google Mobile Services (GMS) available. - -- To learn more about managing RealWear devices on Microsoft Endpoint Manager, see [Android device administrator enrollment in Intune](/mem/intune/enrollment/android-enroll-device-administrator). -- For more details on policies, see [How to use Intune in environments without Google Mobile Services](/mem/intune/apps/manage-without-gms). - -### Third-party Enterprise Mobility Managers (EMMs) - -For guidance on third-party EMMs, see [Supported Enterprise Mobility Management Providers](https://www.realwear.com/knowledge-center/configure-on-release-10/remote-from-a-web-browser/emm/). - -## End-user content - -For further reading on this from an end-user perspective, check out [Using Microsoft Teams for RealWear](https://support.office.com/article/using-microsoft-teams-for-realwear-af20d232-d18c-476f-8031-843a4edccd5f). diff --git a/Teams/get-clients.md b/Teams/get-clients.md index ae234c5ab1..35e850062b 100644 --- a/Teams/get-clients.md +++ b/Teams/get-clients.md @@ -10,7 +10,7 @@ ms.collection: - M365-collaboration - m365initiative-deployteams ms.reviewer: rafarhi -ms.date: 10/13/2023 +ms.date: 10/30/2024 ms.localizationpriority: medium search.appverid: MET150 description: Learn how to install the various clients available for classic Microsoft Teams on PCs, Macs, and mobile devices. @@ -22,6 +22,9 @@ appliesto: # Get clients for classic Microsoft Teams +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + > [!TIP] > **Want to install Teams on your PC, Mac, or mobile device?** Check out [Install the Teams client](https://go.microsoft.com/fwlink/?linkid=855754). diff --git a/Teams/get-started-with-teams-templates-in-the-admin-console.md b/Teams/get-started-with-teams-templates-in-the-admin-console.md index 068e6458af..2ac4010b1e 100644 --- a/Teams/get-started-with-teams-templates-in-the-admin-console.md +++ b/Teams/get-started-with-teams-templates-in-the-admin-console.md @@ -7,7 +7,7 @@ audience: Admin ms.topic: conceptual ms.service: msteams ms.reviewer: yinchang -ms.date: 09/12/2018 +ms.date: 10/30/2024 ms.localizationpriority: medium search.appverid: MET150 ms.collection: diff --git a/Teams/getting-phone-numbers-for-your-users.md b/Teams/getting-phone-numbers-for-your-users.md index 4feb6a8a32..c6a703b175 100644 --- a/Teams/getting-phone-numbers-for-your-users.md +++ b/Teams/getting-phone-numbers-for-your-users.md @@ -1,7 +1,7 @@ --- title: "Get phone numbers for your users" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 08/29/2023 diff --git a/Teams/google-workspace-addon-teams.md b/Teams/google-workspace-addon-teams.md index 7430b46857..02c9b6c426 100644 --- a/Teams/google-workspace-addon-teams.md +++ b/Teams/google-workspace-addon-teams.md @@ -2,8 +2,8 @@ title: Set up Microsoft Teams meeting add-on for Google Workspace ms.author: wlibebe author: wlibebe -ms.reviewer: aravin -ms.date: 01/11/2021 +ms.reviewer: jason.hochstadt +ms.date: 10/31/2024 manager: pamgreen ms.topic: article audience: admin @@ -27,20 +27,16 @@ appliesto: # Set up Microsoft Teams meeting add-on for Google Workspace -Using the Microsoft Teams meeting add-on lets Google calendar users schedule and join a Microsoft Teams meeting directly from Google Workspace. Users will get access to Teams meetings features including video and audio conferencing, screen sharing, meeting chat, digital whiteboards, and more. Stay connected and organized to get more done together across work, school, and life. +The Microsoft Teams meeting add-on lets Google calendar users schedule and join a Microsoft Teams meeting directly from Google Workspace. These get access to Teams meetings features including video and audio conferencing, screen sharing, meeting chat, digital whiteboards, and more. -The Microsoft Teams meeting add-on for Google Workspace must be enabled by a Teams admin before tenant users can access the app. +The Microsoft Teams meeting add-on for Google Workspace is on by default. To learn about how your users use the Microsoft Teams meeting add-on for Google Workspace, see [Install the Microsoft Teams meeting add-on for Google Workspace](https://support.microsoft.com/office/install-the-microsoft-teams-meeting-add-on-for-google-workspace-bba2dfbe-0b2b-4ee7-be10-261ad80ddb60). -## Enable or disable Microsoft Teams meeting add-on for Google Workspace in the Azure portal +## Turn the Microsoft Teams meeting add-on for Google Workspace on or off in the Azure portal -As a tenant administrator, you can enable or disable a Microsoft Teams meeting add-on for Google Workspace from your organization's admin account using the Azure portal. - -The add-on is enabled by default. +As an admin, you can turn the Microsoft Teams meeting add-on for Google Workspace on or off using the Azure portal. 1. Sign in to the Azure portal. - 2. Select **Enterprise applications** > **All applications**. - 3. Search for **Microsoft Teams meeting add-on for Google Workspace**. ![Azure portal showing all applications.](media/aad-add-google-workspace.png) @@ -51,7 +47,7 @@ The add-on is enabled by default. 5. (Optional) To disable the add-on, select **No** instead of **Yes** in Step 4. -## Disable Microsoft Teams meeting add-on for Google Workspace using PowerShell +## Turn the Microsoft Teams meeting add-on for Google Workspace off using PowerShell ```powershell Connect-MgGraph -Scopes "Application.ReadWrite.All" @@ -61,6 +57,7 @@ $appId = '7969c887-ba98-48bb-8832-6c9239929d7c' ``` ## Check if a service principal already exists for the app + ```powershell $ServicePrincipalUpdate =@{ "accountEnabled" = "false" @@ -87,7 +84,7 @@ See the Google documentation [Delete a Google Workspace Marketplace app](https:/ ## Create the Microsoft Teams meeting add-on for Google Workspace using PowerShell -In case the Microsoft Teams meeting add-on is not present in your tenant, you can create it using PowerShell: +In case the Microsoft Teams meeting add-on isn't present in your tenant, you can create it using PowerShell: ```powershell Connect-MgGraph -Scopes "Application.ReadWrite.All" @@ -106,3 +103,7 @@ if ($servicePrincipal) { Write-Host "Created the Service Principal" } ``` + +## Related topics + +- [Plan for Teams meetings](plan-meetings.md) diff --git a/Teams/hardware-decoders-and-encoders.md b/Teams/hardware-decoders-and-encoders.md index 3d5945e1fb..f1b0f5b298 100644 --- a/Teams/hardware-decoders-and-encoders.md +++ b/Teams/hardware-decoders-and-encoders.md @@ -23,6 +23,9 @@ appliesto: # Hardware decoder and encoder driver recommendations +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + Microsoft supports all decoders and encoders except those listed in this article. ## Hardware decoder driver recommendations - Intel diff --git a/Teams/hardware-requirements-for-the-teams-app.md b/Teams/hardware-requirements-for-the-teams-app.md index 4147b2e7fe..9427bdb1ba 100644 --- a/Teams/hardware-requirements-for-the-teams-app.md +++ b/Teams/hardware-requirements-for-the-teams-app.md @@ -25,7 +25,10 @@ appliesto: # Hardware requirements for Microsoft Teams -All of the requirements in the following sections apply to both the Microsoft Teams desktop app and the Teams Web app. +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + +All of the requirements in the following sections apply to both the classic Microsoft Teams desktop app and the classic Teams Web app. ## Hardware requirements for Teams on a Windows PC diff --git a/Teams/here-s-what-you-get-with-phone-system.md b/Teams/here-s-what-you-get-with-phone-system.md index 1849670124..8398546b5e 100644 --- a/Teams/here-s-what-you-get-with-phone-system.md +++ b/Teams/here-s-what-you-get-with-phone-system.md @@ -2,8 +2,8 @@ title: "Teams Phone features" ms.reviewer: ms.date: 08/15/2023 -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen msreviewer: jastarck, roykuntz ms.topic: conceptual diff --git a/Teams/hide-attendee-names.md b/Teams/hide-attendee-names.md index 1e1b06a980..60abd447fc 100644 --- a/Teams/hide-attendee-names.md +++ b/Teams/hide-attendee-names.md @@ -17,7 +17,7 @@ appliesto: --- # Allow meeting and webinar organizers to hide the names of attendees -**APPLIES TO:** ✔️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/how-many-phone-numbers-can-you-get.md b/Teams/how-many-phone-numbers-can-you-get.md index 94f08006cd..760964606f 100644 --- a/Teams/how-many-phone-numbers-can-you-get.md +++ b/Teams/how-many-phone-numbers-can-you-get.md @@ -1,7 +1,7 @@ --- title: "How many telephone numbers can you get?" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: davlick, roykuntz, jastark ms.date: 03/13/2024 diff --git a/Teams/includes/m365-teams-resource-account-difference.md b/Teams/includes/m365-teams-resource-account-difference.md index f76b02e3ef..c063cd6269 100644 --- a/Teams/includes/m365-teams-resource-account-difference.md +++ b/Teams/includes/m365-teams-resource-account-difference.md @@ -1,5 +1,5 @@ > [!IMPORTANT] -> Microsoft 365 resource accounts aren't the same as Teams resource accounts. Teams resource accounts can be used with call queues and auto attendants to accept phone calls from external phone numbers. Microsoft 365 resource accounts are tied to an Exchange Online mailbox and enable booking of shared resources, such as rooms, projectors, and so on. +> Microsoft 365 resource accounts used for Teams devices aren't the same as Teams resource accounts. Teams resource accounts can be used with call queues and auto attendants to accept phone calls from external phone numbers. Microsoft 365 resource accounts are tied to an Exchange Online mailbox and enable booking of shared resources, such as rooms, projectors, and so on. > > If you want to know more about Teams resource accounts, see [Manage resources accounts in Microsoft Teams](../manage-resource-accounts.md). diff --git a/Teams/includes/mtr-device-config-account-include.md b/Teams/includes/mtr-device-config-account-include.md index 6d022389f6..76019114fd 100644 --- a/Teams/includes/mtr-device-config-account-include.md +++ b/Teams/includes/mtr-device-config-account-include.md @@ -1,29 +1,23 @@ ---- -ms.date: 08/03/2022 ---- -Each Microsoft Teams Rooms device needs its own resource account. The resource account is the account the Teams Rooms device logs into and is what users in your organization invite to book the Teams Room. +> [!TIP] +> You can automatically create and configre Teams Rooms resource accounts via the [Surface Hub and Microsoft Teams Rooms automated setup guide](https://go.microsoft.com/fwlink/?linkid=2221605). +> +> We recommend that you create all resource accounts as cloud only using Microsoft Entra ID and Exchange Online. If using Exchange on-premise, you must be in hybrid for the Teams Rooms device to read the calendar. -When you create the resource mailbox, you can specify whether you want to allow recurring meetings, have the room auto accept invites, how many days into the future to accept invites, and so on. +Each Microsoft Teams Rooms device needs its own resource account. The Teams Rooms device uses the resource account to log into Microsoft 365 and it's what users in your organization invite in Exchange to book the room. > [!TIP] -> When naming your resource accounts, we recommend using a standard naming convention to the beginning of the e-mail address. This will help with creating dynamic groups to ease management in Microsoft Entra ID. For example, you could use "mtr-" for all resource accounts that will be associated with Microsoft Teams Rooms. +> When naming your resource accounts, we recommend using a standard naming convention to the beginning of the e-mail address. This will help with creating dynamic groups to ease management. For example, you could use "mtr-" for all resource accounts that will be associated with Microsoft Teams Rooms. -> [!TIP] -> We recommend that you create all resource accounts using Exchange Online and Microsoft Entra ID. -> -> You can automatically configure recommended Teams Rooms resource settings via the [Surface Hub and Microsoft Teams Rooms automated setup guide](https://go.microsoft.com/fwlink/?linkid=2221605). Create a resource account using a method from one of the following tabs: #### [**In Microsoft 365 admin center**](#tab/m365-admin-center) -1. Sign in to the Microsoft 365 admin center. +1. Sign in to the Microsoft 365 admin center with administrative credentials for your Microsoft 365 tenant. -2. Provide the admin credentials for your Microsoft 365 tenant. +2. Go to **Resources** in the left panel, and then select **Rooms & equipment**. (If these options aren't available in the panel, you may need to select **Show all** first.) -3. Go to **Resources** in the left panel, and then select **Rooms & equipment**. If these options aren't available in the left panel, you may need to select **Show all** first. - -4. Select **Add resource** to create a new resource account. Enter a display name and email address for the account and then select **Save**. +3. Select **Add resource** to create a new resource account. Enter a name, email address, and capacity for the account, then select **Save**. 5. By default, resource accounts are configured with the following settings: @@ -39,11 +33,13 @@ Create a resource account using a method from one of the following tabs: 7. Next, assign a password to the resource account. In the panel, select **Reset password**. -8. Requiring users to change the password on a shared device will cause sign in problems. Uncheck **Require this user to change their password when they first sign in**, and select **Reset password**. +8. Requiring a password change on first login for a Teams Rooms device causes sign in problems. Uncheck **Require this user to change their password when they first sign in**, and select **Reset password**. + +9. Assign the Teams Rooms license, purchased in the earlier step. In the panel, select **Licenses and apps**. -You may also need to apply bandwidth policies or meeting policies to this account. You can set mailbox policies in a later step. +10. Check the box next to **Microsoft Teams Rooms Pro** or **Microsoft Teams Rooms Basic**, and select **Save changes** -#### [**With Exchange Online**](#tab/exchange-online) +#### [**With Exchange Online PowerShell**](#tab/exchange-online) 1. Connect to [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). @@ -51,7 +47,7 @@ You may also need to apply bandwidth policies or meeting policies to this accoun Connect-ExchangeOnline ``` -2. By default, room mailboxes don't have associated accounts. Add an account when you create a room mailbox so it can authenticate with Microsoft Teams. +2. Room mailboxes don't have accounts associated by default. Add an account when you create a room mailbox so it can authenticate with Microsoft Teams. If you're creating a new resource mailbox: @@ -67,13 +63,18 @@ You may also need to apply bandwidth policies or meeting policies to this accoun - Alias: ConferenceRoom01 - - Account password: P@$$W0rd5959 + - Account password: ``` PowerShell New-Mailbox -MicrosoftOnlineServicesID ConferenceRoom01@contoso.com -Name "ConferenceRoom01" -Alias ConferenceRoom01 -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String 'P@$$W0rd5959' -AsPlainText -Force) ``` -If you're in an Exchange hybrid configuration, you need to add an email address for your on-premises domain account. See [Sync on-premises and Office 365 user accounts directories](https://support.microsoft.com/topic/how-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office-365-user-accounts-for-directory-synchronization-75673b94-e1b8-8a9e-c413-ee5a2a1a6a78) for more information. +3. To assign the Teams Rooms license, purchased in the earlier step, sign in to the Microsoft 365 admin center with administrative credentials for your Microsoft 365 tenant. + +4. Go to **Users** > **Active users**, and select the room you created to open the properties panel. In the panel, select **Licenses and apps**. + +5. Check the box next to **Microsoft Teams Rooms Pro** or **Microsoft Teams Rooms Basic**, and select **Save changes** + #### [**With Exchange Server**](#tab/exchange-server) @@ -93,11 +94,20 @@ If you're in an Exchange hybrid configuration, you need to add an email address - Alias: ConferenceRoom01 - - Account password: P@$$W0rd5959 + - Account password: - ``` PowerShell - New-Mailbox -UserPrincipalName ConferenceRoom01@contoso.com -Name "ConferenceRoom01" -Alias ConferenceRoom01 -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String 'P@$$W0rd5959' -AsPlainText -Force) - ``` + ``` PowerShell + New-Mailbox -UserPrincipalName ConferenceRoom01@contoso.com -Name "ConferenceRoom01" -Alias ConferenceRoom01 -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String 'P@$$W0rd5959' -AsPlainText -Force) + ``` + +3. To assign the Teams Rooms license, purchased in the earlier step, sign in to the Microsoft 365 admin center with administrative credentials for your Microsoft 365 tenant. + +4. Go to **Users** > **Active users**, and select the room you created to open the properties panel. In the panel, select **Licenses and apps**. + +5. Check the box next to **Microsoft Teams Rooms Pro** or **Microsoft Teams Rooms Basic**, and select **Save changes** + +> [!IMPORTANT] +> You must be in operating in an Exchange hybrid configuration for a Teams Rooms device to access the Exchange calendar. In hybrid, you'll also need to add an email address for your on-premises domain account. For more information, see [sync on-premises and Office 365 user accounts directories](https://support.microsoft.com/topic/how-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office-365-user-accounts-for-directory-synchronization-75673b94-e1b8-8a9e-c413-ee5a2a1a6a78). #### [**Modify an existing Exchange room mailbox**](#tab/existing-account) @@ -107,20 +117,21 @@ To modify an existing room mailbox to become a resource account, use the followi Set-Mailbox -Identity -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String '' -AsPlainText -Force) ``` -This example enables the account for the existing room mailbox that has the alias value ConferenceRoom02, and sets the password to 9898P@$$W0rd. +This example enables the account for the existing room mailbox that has the alias value ConferenceRoom02. ``` PowerShell Set-Mailbox -Identity ConferenceRoom02 -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String '9898P@$$W0rd' -AsPlainText -Force) ``` -If you're in an Exchange hybrid configuration, you'll also need to add an email address for your on-premises domain account. See [Sync on-premises and Office 365 user accounts directories](https://support.microsoft.com/topic/how-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office-365-user-accounts-for-directory-synchronization-75673b94-e1b8-8a9e-c413-ee5a2a1a6a78) for more information. - For detailed syntax and parameter information, see [New-Mailbox](/powershell/module/exchange/mailboxes/new-mailbox) and [Set-Mailbox](/powershell/module/exchange/mailboxes/set-mailbox). -> [!NOTE] -> If you're creating this account for Teams Room on Surface Hub, you should also enable ActiveSync on this account. This will allow you to send e-mail directly from the Surface Hub, which you can use for features like Whiteboard. See [Applying ActiveSync policies to device accounts (Surface Hub)](/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts) to learn more. +1. To assign the Teams Rooms license, purchased in the earlier step, sign in to the Microsoft 365 admin center with administrative credentials for your Microsoft 365 tenant. ---- +2. Go to **Users** > **Active users**, and select the room you created to open the properties panel. In the panel, select **Licenses and apps**. + +3. Check the box next to **Microsoft Teams Rooms Pro** or **Microsoft Teams Rooms Basic**, and select **Save changes** > [!IMPORTANT] -> If you're only using this resource account to book space and automatically accept or decline invitations, you've completed the set up. If you're using this resource account for PSTN calling, see [Microsoft Teams add-on licenses](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md) to determine what license it needs. +> You must be in operating in an Exchange hybrid configuration for a Teams Rooms device to access the Exchange calendar. In hybrid, you'll also need to add an email address for your on-premises domain account. For more information, see [Sync on-premises and Office 365 user accounts directories](https://support.microsoft.com/topic/how-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office-365-user-accounts-for-directory-synchronization-75673b94-e1b8-8a9e-c413-ee5a2a1a6a78). + +--- diff --git a/Teams/includes/mtr-device-config-calendar-include.md b/Teams/includes/mtr-device-config-calendar-include.md index 7306a9000c..e55951c4b8 100644 --- a/Teams/includes/mtr-device-config-calendar-include.md +++ b/Teams/includes/mtr-device-config-calendar-include.md @@ -1,19 +1,19 @@ -To help your users more easily schedule meetings in a Teams Room, you can create room lists and places in Exchange Online. +To help your users more easily schedule meetings in a Teams Room, you can create room lists in Exchange Online. -Exchange room lists and Outlook Places are used to control which resource accounts (and therefore the Teams Rooms they're associated with) appear in Outlook's Room Finder. Room Finder is an Outlook feature that helps users find rooms that are near them, available for reservation, and meet other criteria such as the availability of a display. +Exchange room lists are used to control which resource accounts (and therefore the Teams Rooms they're associated with) appear in the Room Finder. Room Finder is an Outlook feature that helps users find rooms that are near them, available for reservation, and meet other criteria such as the availability of a display. -Room lists are a special type of Exchange distribution group that let you group resource accounts (and therefore the Teams Rooms they're associated with) together in a meaningful way. For example, you might want to create room lists for all the rooms in each building on your campus. +Room lists are a special type of Exchange distribution group that lets you group resource accounts (and therefore the Teams Rooms they're associated with) together in a meaningful way. For example, you might want to create room lists for all the rooms in each building on your campus. -Outlook Places lets you set specific attributes about a resource account and its Teams Room. Some of the attributes you can set are: +Microsoft Places lets you set specific attributes about a resource account and its Teams Room. Some of the attributes you can set are: - Building - City - Capacity -- Whether the location is wheelchair-accessible -- Audio, video, and display names +- Wheelchair-accessible +- Room features -Using a combination of room lists and place attributes selected by a user, Room Finder in Outlook will show a list of rooms available to them for reservation. To make the best use of room lists and places, create room lists based on a place attribute, such as building. For example, set the city and building place attributes for each resource account, and then add each resource account to a building room list. When a user tries to choose a room to reserve, Outlook will show a list of cities and the room lists available in each of those cities. +Room Finder in Outlook shows a list of rooms available to them for reservation based on a combination of room lists and place attributes selected by a user. To make the best use of room lists and places, create room lists based on a place attribute, such as building. For example, set the city and building place attributes for each resource account, and then add each resource account to a building room list. When a user tries to choose a room to reserve, Outlook shows a list of cities and the room lists available in each of those cities. > [!IMPORTANT] > Each resource account needs to have its place attributes set. If these attributes, especially city, building, and capacity, aren't set, those rooms won't show up as available options for reservation even if a room list contains them. @@ -21,4 +21,3 @@ Using a combination of room lists and place attributes selected by a user, Room To create a room list, follow the instructions in [Create a rooms list](/exchange/recipients/room-mailboxes?view=exchserver-2019&preserve-view=true#create-a-room-list). To configure the place attributes for a resource account, see [Set-Place](/powershell/module/exchange/set-place). - diff --git a/Teams/includes/mtr-device-config-license-include.md b/Teams/includes/mtr-device-config-license-include.md index 0cfafa5834..9d480b1a51 100644 --- a/Teams/includes/mtr-device-config-license-include.md +++ b/Teams/includes/mtr-device-config-license-include.md @@ -1,10 +1,7 @@ -In the next step you'll create a resource account for your Teams Rooms console. Before you do that, you need to purchase a license because each resource account you want to associate with a Teams Rooms console needs a Teams Rooms license. +In the next step, you'll create a resource account for each your Teams Rooms device. Before you do that, you need to purchase licenses, each resource account you want to associate with a Teams Rooms device needs a Teams Rooms license. -Follow the steps below to purchase a Teams Rooms Basic or Teams Rooms Pro license that you can assign to a resource account in a later step. For a comparison between the Teams Rooms Basic and Teams Rooms Pro licenses, see [Teams Meeting Room Licensing Update](../rooms/rooms-licensing.md). - -> [!NOTE] -> If you have multiple Teams Rooms consoles, we recommend that you purchase a Teams Rooms Pro license for each of your consoles. The Teams Rooms Pro license enables more advanced remote management and analytics for Teams Rooms, enabling you to create a more consistent and robust Teams Rooms and meeting experience. +Follow these steps to purchase a Teams Rooms Basic or Teams Rooms Pro license that you can assign to a resource account in a later step. For a comparison between the Teams Rooms Basic and Teams Rooms Pro licenses, see [Teams Meeting Rooms Licenses](../rooms/rooms-licensing.md). 1. Go to the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339) and log in with an account that has license admin permissions. 1. In the admin center, go to the **Billing** > [Purchase services](https://go.microsoft.com/fwlink/p/?linkid=868433) page. @@ -12,9 +9,3 @@ Follow the steps below to purchase a Teams Rooms Basic or Teams Rooms Pro licens 1. Select **Details** under either **Teams Rooms Basic** or **Teams Rooms Pro**. 1. Select the number of licenses you want to purchase in **Select license quantity**. 1. Select how often you want to be billed under **Select billing frequency** and then click **Buy**. - -> [!NOTE] -> You can purchase up to 25 Teams Rooms Basic licenses. Any additional licenses you purchase beyond 25 must be Teams Rooms Pro licenses. -> -> You can purchase a Teams Rooms Basic license for a Teams Rooms console and later change the license for that console to Teams Rooms Pro. First make sure you have an available Teams Rooms Pro license and then follow the instructions in [Change the apps and services a user has access to](/microsoft-365/admin/manage/assign-licenses-to-users#change-the-apps-and-services-a-user-has-access-to). - diff --git a/Teams/includes/mtr-device-config-mailbox-include.md b/Teams/includes/mtr-device-config-mailbox-include.md index 25f3f8c5c9..e0eea656cd 100644 --- a/Teams/includes/mtr-device-config-mailbox-include.md +++ b/Teams/includes/mtr-device-config-mailbox-include.md @@ -1,30 +1,30 @@ -You can improve your Teams Rooms meeting experience by customizing how the resource account responds to, and processes, meeting invitations. Using Exchange Online PowerShell, you can set the following resource account properties: +Based on organizational requirements, you may wish to customize how the resource account responds to and processes meeting invitations. Using Exchange PowerShell, you can set many properties, review the [Set-CalendarProcessing](/powershell/module/exchange/mailboxes/set-calendarprocessing) cmdlet for all available configurations. The following are recommended for Teams Rooms: - **AutomateProcessing: `AutoAccept`** Meeting organizers receive the room reservation decision directly without human intervention. -- **AddOrganizerToSubject: `$false`** The meeting organizer isn't added to the subject of the meeting request. +- **AddOrganizerToSubject: `$false`** The meeting organizer isn't added to the subject of the meeting request on the resource account calendar. -- **DeleteComments: `$false`** Keep any text in the message body of incoming meeting requests. This is required to process external Teams and third-party meetings to provide One Touch Join experience. +- **AllowRecurringMeetings: `$true`** Recurring meetings are accepted. -- **DeleteSubject: `$false`** Keep the subject of incoming meeting requests. +- **DeleteAttachments: `$true`** Teams Rooms devices can't access meeting attachments, deleting attachments ensures they're not stored on the resource account calendar. -- **ProcessExternalMeetingMessages: `$true`** Specifies whether to process meeting requests that originate outside the Exchange organization. Required for external Teams meetings and [third-party meetings](/microsoftteams/rooms/third-party-join). +- **DeleteComments: `$false`** Keep any text in the message body of incoming meeting requests which is required to create join buttons for [third-party meetings](/microsoftteams/rooms/third-party-join) on a Teams Rooms device. -- **RemovePrivateProperty: `$false`** Ensures the private flag that was sent by the meeting organizer in the original meeting request remains as specified. +- **DeleteSubject: `$false`** Keep the subject of incoming meeting requests on the resource accounts calendar. + +- **ProcessExternalMeetingMessages: `$true`** Specifies whether to process meeting requests organized outside your Exchange environment. This option is required for meeting invites sent directly by an external organizer as well external organized meetings forwarded by an internal user. + +- **RemovePrivateProperty: `$false`** Ensures the private flag that sent by the meeting organizer in the original meeting request remains as specified. - **AddAdditionalResponse: `$true`** The text specified by the AdditionalResponse parameter is added to meeting requests. -- **AdditionalResponse: "This is a Microsoft Teams Meeting room!"** The additional text to add to the meeting acceptance response. +- **AdditionalResponse: "This is a Microsoft Teams Meeting room!"** The text to add to the meeting acceptance body. You can also format HTML content in the automatic reply if you wish. To configure these properties, you need to connect to Exchange Online PowerShell. For more information, see [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps&preserve-view=true). -After you've connected to Exchange Online PowerShell, you can configure the mailbox properties on a resource account by using the [Set-CalendarProcessing](/powershell/module/exchange/mailboxes/set-calendarprocessing) cmdlet. - The following example sets the properties for the `ConferenceRoom01` resource account: ``` PowerShell -Set-CalendarProcessing -Identity "ConferenceRoom01" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -DeleteComments $false -DeleteSubject $false -ProcessExternalMeetingMessages $true -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This is a Microsoft Teams Meeting room!" +Set-CalendarProcessing -Identity "ConferenceRoom01" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -AllowRecurringMeetings $true -DeleteAttachments $true -DeleteComments $false -DeleteSubject $false -ProcessExternalMeetingMessages $true -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This is a Microsoft Teams Meeting room!" ``` - - diff --git a/Teams/includes/mtr-device-config-password-include.md b/Teams/includes/mtr-device-config-password-include.md index e5b3453f8b..3199543248 100644 --- a/Teams/includes/mtr-device-config-password-include.md +++ b/Teams/includes/mtr-device-config-password-include.md @@ -1,72 +1,45 @@ --- -ms.date: 11/16/2023 +ms.date: 10/10/2024 ms.custom: - has-azure-ad-ps-ref, azure-ad-ref-level-one-done --- -Like any Microsoft 365 account, a newly created resource account's password is set to expire automatically after a period of time. However, if the resource account password expires, the Teams Rooms device it's signed into won't be able to sign in again after the expiration date. - -To avoid resetting the resource account's password and logging into each Teams Rooms device again, you can turn off password expiration for the account. +Based on organization policies, resource account passwords may be set to expire automatically after a period of time. If the resource account password expires, the Teams Rooms device with sign out and can't sign in again without manual intervention. > [!NOTE] -> Setting **Password never expires** is a requirement for shared Microsoft Teams devices. If your domain rules prohibit passwords that don't expire, you'll need to create an exception for each Teams device resource account. +> Setting **Password never expires** is a requirement for shared Microsoft Teams devices. If your organization prohibits passwords that don't expire, you'll need to create an exception for Teams device resource accounts. -Follow the steps in one of the following tabs to turn off password expiration: +To turn off password expiration, follow the steps in one of the following tabs: #### [**Microsoft Graph PowerShell**](#tab/graph-powershell-password/) -First, connect to the Microsoft Graph PowerShell: - -```PowerShell - Connect-MgGraph -Scopes "User.ReadWrite.All" -``` - -This example sets the password for the account ConferenceRoom01@contoso.com to never expire. - -```PowerShell -Update-MgUser -UserId ConferenceRoom01@contoso.com -PasswordPolicies DisablePasswordExpiration -PassThru -``` - -#### [**Microsoft Entra ID 2.0/AzureAD**](#tab/azure-active-directory2-password/) +1. Connect to [Microsoft Graph PowerShell](/microsoft-365/enterprise/connect-to-microsoft-365-powershell): -First, connect to Active Directory PowerShell: - -```PowerShell - Connect-AzureAD -``` - -Then, see [Set a password to never expire](/microsoft-365/admin/add-users/set-password-to-never-expire#set-a-password-to-never-expire). - -This example sets the password for the account ConferenceRoom01@contoso.com to never expire. + ```PowerShell + Connect-MgGraph -Scopes "User.ReadWrite.All" + ``` -```PowerShell -Set-AzureADUser -ObjectID ConferenceRoom01@contoso.com -PasswordPolicies DisablePasswordExpiration -``` +2. Set the password to never expire, this example sets the password for the account ConferenceRoom01@contoso.com to never expire. + ```PowerShell + Update-MgUser -UserId ConferenceRoom01@contoso.com -PasswordPolicies DisablePasswordExpiration -PassThru + ``` -#### [**Active Directory (On premises)**](#tab/active-directory1-password/) +#### [**Active Directory (On-premises)**](#tab/active-directory1-password/) -1. Connect to Active Directory PowerShell: +1. Connect to [Active Directory PowerShell](/powershell/module/activedirectory): ```PowerShell Import-Module ActiveDirectory ``` - For details about Active Directory PowerShell, see [ActiveDirectory](/powershell/module/activedirectory). - -2. Set the password to never expire by using the following syntax: - ```PowerShell - Set-ADUser -Identity -PasswordNeverExpires $true - ``` - - This example sets the password for the account ConferenceRoom01@contoso.com to never expire. +2. Set the password to never expire, this example sets the password for the account ConferenceRoom01@contoso.com to never expire. ```PowerShell Set-ADUser -Identity ConferenceRoom01@contoso.com -PasswordNeverExpires $true ``` - --- diff --git a/Teams/includes/mtr-device-config-policies-include.md b/Teams/includes/mtr-device-config-policies-include.md index 0bb4769d62..4a91ef9b15 100644 --- a/Teams/includes/mtr-device-config-policies-include.md +++ b/Teams/includes/mtr-device-config-policies-include.md @@ -1,4 +1,7 @@ -You may need to apply custom network, bandwidth, or meeting policies to this account. For more information on network and bandwidth policies, see [Meeting policy settings for audio & video](/microsoftteams/meeting-policies-audio-and-video). For Teams Rooms, we recommend you set the meeting policy bandwidth to 10 Mbps. +You may need to apply custom bandwidth or meeting policies to this account. For more information, see [Meeting policy settings for audio & video](/microsoftteams/meeting-policies-audio-and-video). For Teams Rooms, we recommend you set the bandwidth policy no lower than 10 Mbps. -For collaboration purposes, turn on PowerPoint Live, Whiteboard, and shared notes. It is recommended that you enable the meeting policy setting "Meet now in private meetings". You may want to create a meeting policy to adjust participants and guest settings for Teams Rooms. For example, review the lobby settings such as which attendees to automatically admit to meetings. For more information on Teams meeting policies, see [Manage meeting policies in Microsoft Teams](/microsoftteams/meeting-policies-overview). +For collaboration purposes, turn on PowerPoint Live, Whiteboard, and shared notes. We recommend you enable the meeting policy setting "Meet now in private meetings" to ensure the "Meet now" functionality on the Teams Rooms console functions. For more information on Teams meeting policies, see [Manage meeting policies in Microsoft Teams](/microsoftteams/meeting-policies-overview). +Teams Rooms devices include a Net Promotor Score (NPS) survey, this survey can be controlled with Teams feedback policies. For more information, see [Manage feedback policies in Microsoft Teams](/microsoftteams/manage-feedback-policies-in-teams). + +Teams public preview can be enabled on Teams devices to see Teams features earlier than general availability. For more information, see [Microsoft Teams Public preview](/microsoftteams/public-preview-doc-updates?tabs=new-teams-client) on how to enable public preview. diff --git a/Teams/includes/set-up-resource-account-steps.md b/Teams/includes/set-up-resource-account-steps.md index de47358a29..e15392b9d4 100644 --- a/Teams/includes/set-up-resource-account-steps.md +++ b/Teams/includes/set-up-resource-account-steps.md @@ -98,6 +98,8 @@ You can create a resource account with the New-CsOnlineApplicationInstance Power For each resource account, you must assign a **Microsoft Teams Phone Resource Account** license. +Nested auto attendants and call queues that transfer calls externally don't require resource accounts or respective licensing. When nesting auto attendants or call queues, license the resource account on the first auto attendant or call queue receiving the call. + 1. Sign into the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339). 2. Expand **Users**, then select **Active users**. 3. Select the resource account to which you want to assign a license. The resource account's user pane will appear. diff --git a/Teams/ip-relay-canada-email-signup.md b/Teams/ip-relay-canada-email-signup.md index 4a95b58e1c..29725ee369 100644 --- a/Teams/ip-relay-canada-email-signup.md +++ b/Teams/ip-relay-canada-email-signup.md @@ -1,7 +1,7 @@ --- title: "IP Relay in Canada" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: ms.date: 04/04/2018 diff --git a/Teams/ip-relay-canada-user-guide.md b/Teams/ip-relay-canada-user-guide.md index ddfa7a2b3d..f15dbd3ea8 100644 --- a/Teams/ip-relay-canada-user-guide.md +++ b/Teams/ip-relay-canada-user-guide.md @@ -1,7 +1,7 @@ --- title: "IP Relay in Canada - user guide" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: ms.date: 11/17/2023 diff --git a/Teams/join-verification-check.md b/Teams/join-verification-check.md new file mode 100644 index 0000000000..b5f5bb4560 --- /dev/null +++ b/Teams/join-verification-check.md @@ -0,0 +1,103 @@ +--- +title: Require verification checks to join Teams meetings and webinars in your org +ms.author: wlibebe +author: wlibebe +manager: pamgreen +ms.reviewer: ivah +ms.date: 11/30/2024 +ms.topic: how-to +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +appliesto: + - Microsoft Teams +ms.localizationpriority: medium +search.appverid: MET150 +f1.keywords: +- CSH +ms.custom: +ms.collection: + - M365-collaboration + - m365initiative-meetings + - highpri + - Tier1 +description: Learn how to require verification checks for Microsoft Teams meetings and webinars in your org to prevent bots from joining. +--- + +# Require verification checks to join Teams meetings and webinars in your org + +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls + +For a seamless experience, it's important to manage how anonymous participants join meetings and webinars in your org. Anonymous participants include users who join a Teams meeting without signing in, via the Teams web app, or through external meeting platforms. + +If your organizers allow anonymous users to bypass the lobby, web bots might join and disrupt their meetings and webinars. As an admin, you can require human verification checks for anonymous users to join meetings in your org. Requiring a CAPTCHA challenge can prevent unwanted web-based bots from joining, recording, and causing disturbances in meetings and webinars. + +:::image type="content" source="media/captcha-audio-small.png" alt-text="Screenshot of a user named Daniela completing an audio CAPTCHA challenge to join a meeting." lightbox="media/captcha-audio-expand.png"::: +:::image type="content" source="media/captcha-text-small.png" alt-text="Screenshot of a user named Daniela completing a text CAPTCHA challenge to join a meeting." lightbox="media/captcha-text-expand.png"::: + +## Manage verification checks for meetings and webinars in your org + +You can use the Teams admin center or PowerShell manage verification checks for meetings and webinars in your org. You could also use a sensitivity label in Purview or a meeting template to require verification checks. To use meeting templates and sensitivity labels, you must have a Teams Premium license. + +|Teams admins center policy value |PowerShell setting value | Behavior| +|---------|---------|---------------| +|Not required|NotRequired| **This is the default value**. When organizers with this policy create meetings and webinars, no users in that meeting complete a verification check before joining the meeting.| +|Anonymous users and people from untrusted organizations|AnonymousUsersAndUntrustedOrganizations| When organizers with this policy create meetings and webinars, anonymous users and people from untrusted organizations must complete a verification check before joining the meeting. | + +### Manage verification checks in the Teams admin center + +1. Open the Teams admin center. +2. Expand **Meetings** from the navigation pane. +3. Under **Meetings**, select **Meeting Policies**. +4. Either select an existing policy or create a new one. +5. Navigate to the **Meeting join & lobby** section and select one of the following options for **Require a verification check from:** + - Not required (default) + - Anonymous users and people from untrusted organizations +6. Select **Save** + +### Manage verification checks using PowerShell + +To manage how users in your org use Copilot for Teams meetings and events, use the **`-CaptchaVerificationForMeetingJoin`** parameter within the PowerShell [**CsTeamsMeetingPolicy**](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet. + +Require anonymous users and users from untrusted organizations to complete a verification check before joining meetings and webinars created by organizers with this policy: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -CaptchaVerificationForMeetingJoin AnonymousUsersAndUntrustedOrganizations +``` + +Prevent users from completing a verification check before joining meetings and webinars created by organizers with this policy: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -CaptchaVerificationForMeetingJoin NotRequired +``` + +## Client and platform support + +### Supported + +Verification checks are supported on the following clients and platforms: + +**Clients:** Teams (T2.1, T2.2), Outlook + +**Platforms:** Desktop, Web, Virtualized Desktop Infrastructure (VDI), and mobile application (iOS and Android) + +### Not supported + +When participants from the following clients and platforms attend meetings that require a verification check, they join without completing the CAPTCHA challenge: + +**Clients:** Cloud Video Interop (CVI), Azure Communication Services (ACS) platform, MTR Android devices + +**Platforms:** Third party devices + +## Related articles + +- [Manage meeting templates in Microsoft Teams - Microsoft Teams | Microsoft Learn](manage-meeting-templates.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with baseline protection - Microsoft Teams | Microsoft Learn](configure-meetings-baseline-protection.md) +- [Configure Teams meetings with protection for sensitive data](configure-meetings-sensitive-protection.md) +- [Configure Teams meetings with protection for highly sensitive data](configure-meetings-highly-sensitive-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [IT admins - Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md) +- [Use sensitivity labels to protect calendar items, Teams meetings, and chat](meeting-templates-sensitivity-labels-policies.md) +- [Plan for Teams meetings](plan-meetings.md) +- [Plan for Teams webinars](plan-webinars.md) diff --git a/Teams/languages-for-voicemail-greetings-and-messages.md b/Teams/languages-for-voicemail-greetings-and-messages.md index ad4e71180d..e50a6f1faf 100644 --- a/Teams/languages-for-voicemail-greetings-and-messages.md +++ b/Teams/languages-for-voicemail-greetings-and-messages.md @@ -1,7 +1,7 @@ --- title: "Teams languages for voicemail greetings and messages" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: colongma ms.date: 05/19/2021 diff --git a/Teams/legacy-login-issues.md b/Teams/legacy-login-issues.md index 63c0866e64..8c25cd4d4b 100644 --- a/Teams/legacy-login-issues.md +++ b/Teams/legacy-login-issues.md @@ -1,8 +1,8 @@ --- title: Issues receiving messages and calls on legacy systems in Teams ms.reviewer: -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 05/29/2020 ms.topic: troubleshooting diff --git a/Teams/limits-specifications-teams.md b/Teams/limits-specifications-teams.md index a710f82f68..f190719747 100644 --- a/Teams/limits-specifications-teams.md +++ b/Teams/limits-specifications-teams.md @@ -92,12 +92,13 @@ The following limitations also apply: Users who participate in conversations that are part of the chat list in Teams must have an Exchange Online (cloud-based) mailbox for an admin to search chat conversations. That's because conversations that are part of the chat list are stored in the cloud-based mailboxes of the chat participants. If a chat participant doesn't have an Exchange Online mailbox, the admin can't search or place a hold on chat conversations. For example, in an Exchange hybrid deployment, users with on-premises mailboxes might be able to participate in conversations that are part of the chat list in Teams. However, in this case, content from these conversations isn't searchable and can't be placed on hold because the users don't have cloud-based mailboxes. (For more, see [How Exchange and Microsoft Teams interact](exchange-teams-interact.md).) -|Feature | Maximum limit | -|---------|---------| -|Number of people in a private chat1 | 2502 | -|Number of people in a video or audio call from chat | 20 | -|Number of file attachments3 |10 | -|Chat size | Approximately 28 KB per post4 | +|Feature | Maximum limit | +|----------------------------------------------------|------------------------------------------| +|Number of people in a private chat1 | 2502 | +|Number of people in a video or audio call from chat | 20 | +|Number of file attachments3 |10 | +|File size limitation |100 MB | +|Chat size | Approximately 28 KB per post4 | 1 If you have more than 20 people in a chat, the following chat features are turned off: Outlook automatic replies and Teams status messages; typing indicator; video and audio calling; sharing; read receipts. The "Set Delivery Options" button (!) is also removed when private group chats contain more than 20 members. @@ -149,7 +150,7 @@ Channel names also can't start with an underscore (_) or period (.), or end with |Number of people in a video or audio call from chat | 20 | |Max PowerPoint File Size | 2 GB| |Teams keeps [meeting recordings](meeting-recording.md) that don't get uploaded to Microsoft Stream, available for local download | 20 days | -| Meeting recording maximum length | 4 hours or 1.5 GB. When this limit is reached, the recording ends and automatically restarts. +| Meeting recording maximum length | 4 hours or 1.5 GB. When this limit is reached, the recording ends and automatically restarts.| For more information, see [Meetings, webinars, and live events](/microsoftteams/quick-start-meetings-live-events). diff --git a/Teams/location-based-routing-configure-network-settings-india.md b/Teams/location-based-routing-configure-network-settings-india.md index aaad8b110c..95d46649d9 100644 --- a/Teams/location-based-routing-configure-network-settings-india.md +++ b/Teams/location-based-routing-configure-network-settings-india.md @@ -1,7 +1,7 @@ --- title: Configure network settings - Location-Based Routing -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.topic: article ms.reviewer: roykuntz diff --git a/Teams/location-based-routing-configure-network-settings.md b/Teams/location-based-routing-configure-network-settings.md index e6c7040430..05a5b14ed9 100644 --- a/Teams/location-based-routing-configure-network-settings.md +++ b/Teams/location-based-routing-configure-network-settings.md @@ -1,7 +1,7 @@ --- title: Configure network settings - Location-Based Routing -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.topic: article ms.reviewer: roykuntz diff --git a/Teams/location-based-routing-enable.md b/Teams/location-based-routing-enable.md index 46933354aa..e0f859d444 100644 --- a/Teams/location-based-routing-enable.md +++ b/Teams/location-based-routing-enable.md @@ -1,7 +1,7 @@ --- title: Enable Location-Based Routing for Direct Routing -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.topic: article ms.reviewer: roykuntz diff --git a/Teams/location-based-routing-india-plan.md b/Teams/location-based-routing-india-plan.md index d7c188690e..33d511bd27 100644 --- a/Teams/location-based-routing-india-plan.md +++ b/Teams/location-based-routing-india-plan.md @@ -1,7 +1,7 @@ --- title: Plan Location-Based Routing for Operator Connect for India -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.service: msteams diff --git a/Teams/location-based-routing-plan.md b/Teams/location-based-routing-plan.md index 82af4a9c8b..a26d22dd2b 100644 --- a/Teams/location-based-routing-plan.md +++ b/Teams/location-based-routing-plan.md @@ -1,7 +1,7 @@ --- title: Plan Location-Based Routing for Direct Routing -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.service: msteams diff --git a/Teams/location-based-routing-scenarios.md b/Teams/location-based-routing-scenarios.md index c6f4515e2c..74f895c563 100644 --- a/Teams/location-based-routing-scenarios.md +++ b/Teams/location-based-routing-scenarios.md @@ -1,7 +1,7 @@ --- title: Scenarios for Location-Based Routing for Direct Routing -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.service: msteams @@ -9,7 +9,7 @@ audience: admin ms.reviewer: roykuntz ms.date: 08/10/2023 search.appverid: MET150 -description: Learn how to plan Location-Based Routing for Teams Phone Direct Routing. +description: Learn different scenarios for Location-Based Routing for Direct Routing. ms.localizationpriority: medium f1.keywords: - NOCSH diff --git a/Teams/m365-custom-connectors.md b/Teams/m365-custom-connectors.md index e0ef6ad727..6c12a203bb 100644 --- a/Teams/m365-custom-connectors.md +++ b/Teams/m365-custom-connectors.md @@ -7,7 +7,7 @@ ms.topic: article ms.service: msteams ms.subservice: teams-apps audience: admin -ms.date: 02/14/2024 +ms.date: 10/18/2024 ms.collection: - M365-collaboration ms.reviewer: vivg @@ -29,6 +29,42 @@ Teams and Microsoft 365 groups use connectors. You can use the same connectors i Any team member can add a connector to a channel, if the team permissions allow it. The updates from the service, that the connector fetches information from, notifies all the team members. Any team member with the permissions to add or remove can modify connectors setup done by other members. +> [!IMPORTANT] +> Developers can't register new connectors on the [Connector developer portal](https://aka.ms/connectorsdashboard). + +## Update connectors URL + +The [Teams connectors are transitioning](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams) to a new URL to enhance security. During this transition, you may receive notifications to update your configured connector to use the new URL. We strongly recommended that you update your connector immediately to prevent any disruption to connector services. + +This change is needed only for webhook-based Connectors such as Incoming Webhook and third-party connectors. The change isn't required for polling connectors such as RSS. You must update the URL for the connector to continue posting notifications into Teams after December 31, 2024. + +> [!TIP] +> We recommend that you note the URL that you update. After it is updated, you can’t view the previous URL anymore. An old URL can be useful to find and identify the systems still using it that you must update with the new URL. + +To update the URL, follow these steps: + +1. Go to **Manage channel** in a Teams channel, select **Edit** under the Connectors option, and select **Configured** section. Check the existing connector connections on this page. + + :::image type="content" source="media/manage-channel-option.png" alt-text="Screenshot showing the manage channel option in Teams."::: + +1. Update only those connections that display `Attention required` under the **Manage** option. + + :::image type="content" source="media/connectors-attention-required.png" alt-text="Screenshot showing the configured connections in a Teams channel that need attention."::: + +1. Do one of the following: + + * For connectors that contain a webhook URL, select **Manage** and **Update URL**. + + :::image type="content" source="media/connectors-update-url.png" alt-text="Screenshot showing the option to update a webhook URL."::: + + * For other types of connectors, remove the connector and recreate the connector configuration. + +1. Use the updated URL or the new connection in the systems that were posting to the old URL. The Configure page displays that the URL is updated. + + :::image type="content" source="media/connectors-url-updated.png" alt-text="Screenshot showing a confirmation after URL update."::: + +To know more or to share more information with your app developers, see [Connectors deprecation information](/microsoftteams/platform/webhooks-and-connectors/what-are-webhooks-and-connectors). + ## Enable or disable connectors in Teams The Exchange Online PowerShell v2 module uses modern authentication and works with multifactor authentication (MFA) to connect to all Exchange related PowerShell environments in Microsoft 365. Admins can use Exchange Online PowerShell to disable connectors for an entire organization or a specific group mailbox. If a connector is disabled, it affects all users in that org or mailbox. You can't disable a connector for a few specific users. diff --git a/Teams/manage-apps-across-m365.md b/Teams/manage-apps-across-m365.md index cce969c2b7..e568d4f06b 100644 --- a/Teams/manage-apps-across-m365.md +++ b/Teams/manage-apps-across-m365.md @@ -8,7 +8,7 @@ ms.service: msteams ms.subservice: teams-apps ms.custom: intro-get-started audience: admin -ms.date: 07/08/2024 +ms.date: 11/12/2024 ms.collection: - M365-collaboration - tier2 @@ -83,7 +83,7 @@ Outcomes of app availability setting applied to a particular app. | No one | No user in the organization can install | No one | | No one | All users in the organization can install | Everyone | | No one | Specific users/groups can install | Specific users & groups | -| Specific users & groups | Specific users/groups can install | Specific users & groups | +| Specific users & groups | All users in the organization can install | Everyone | | Specific users & groups (example: Marketing, Legal) | Specific users/groups can install (example: Marketing, Design) | Specific users & groups (example: Legal, Design, Marketing) | | Specific users & groups | No user in the organization can install | Specific users & groups | | Everyone | All users in the organization can install | Everyone | diff --git a/Teams/manage-apps.md b/Teams/manage-apps.md index c5f987d7d2..34272e6fd0 100644 --- a/Teams/manage-apps.md +++ b/Teams/manage-apps.md @@ -8,7 +8,7 @@ ms.service: msteams ms.subservice: teams-apps ms.custom: intro-get-started audience: admin -ms.date: 09/04/2024 +ms.date: 11/12/2024 ms.collection: - M365-collaboration - tier2 @@ -24,11 +24,15 @@ ms.localizationpriority: high --- # Overview of app management and governance in Teams admin center -In the Teams admin center, we provide a few dedicated pages to manage your apps with granularity and complete control. You manage apps for your organization in the **Manage apps** page in the Teams admin center portal. Use the URL [https://admin.teams.microsoft.com/policies/manage-apps](https://admin.teams.microsoft.com/policies/manage-apps) to view and govern all Teams apps that are available in your organization's app catalog, define access to apps using policies, cater to prominent use cases for app management, and more. +In the Teams admin center, we provide a few dedicated pages and UIs to manage your apps. You manage apps for your organization in the **Manage apps** page in the Teams admin center portal. Use the URL [https://admin.teams.microsoft.com/policies/manage-apps](https://admin.teams.microsoft.com/policies/manage-apps) to view and govern the apps that are available in your organization's app catalog, evaluate apps before allowing those and find support information, manage availability of apps across your org on a per-user or per-app basis, and do more. -:::image type="content" source="media/manage-apps.png" alt-text="Screenshot showing the Manage apps page in Teams admin center." lightbox="media/manage-apps.png"::: +:::image type="content" source="media/manage-apps-policy-org.png" alt-text="Screenshot showing the Manage apps page in Teams admin center." lightbox="media/manage-apps-policy-org.png"::: -To use Teams admin center, you must have a Teams Administrator role. For details, see [Teams administrator roles](./using-admin-roles.md) and [Microsoft 365 administrator roles](/microsoft-365/admin/add-users/about-admin-roles). Some admins with a higher privilege role can accomplish app governance tasks but we recommend using the lower privilege role when possible. +If your organization uses [app centric management](app-centric-management.md) (whether migrated automatically or manually), you see a slightly different Manage Apps UI. + +:::image type="content" source="media/manage-apps-acm-org.png" alt-text="Screenshot showing the Manage apps page in Teams admin center after migration to app centric management." lightbox="media/manage-apps-acm-org.png"::: + +To use Teams admin center, you must have a Teams Administrator role. Some admins with a higher privilege role can accomplish app governance tasks but we recommend using the lower privilege role where possible. For details, see [Teams administrator roles](./using-admin-roles.md) and [Microsoft 365 administrator roles](/microsoft-365/admin/add-users/about-admin-roles). App developers [extend Microsoft 365 Copilot](/microsoft-365-copilot/extensibility/) by creating Copilot agents, for example, Microsoft Teams message extension or a Power Platform connector. These Copilot agents increase user productivity across daily tasks and workflows. Admins manage Copilot agents in the [Integrated apps page](/microsoft-365/admin/manage/manage-plugins-for-copilot-in-integrated-apps) of the Microsoft 365 admin center. @@ -63,17 +67,15 @@ App management tasks that are supported on other portals are in the table below. ## Allow or block apps -As an admin, you control access to all [types of apps](apps-in-teams.md#types-of-teams-apps) that are used across your organization. Teams provides granular controls to configure access for each app and for each user. - -To allow an app, you must do all of the following settings. To block an app, just use any one of these settings. +As an admin, you control access to all [types of apps](apps-in-teams.md#types-of-teams-apps) that are used across your organization. Teams provides granular controls to configure access for each app and for each user. To allow an app or a Copilot agent, you must do all of the following settings. To block an app, just use any one of these settings. Ensure that the app that you want to allow in Teams admin center is allowed in the Microsoft 365 admin center. | Method | Scope | Use case | |:-----------------------------------------------------------------------------------------------------------------|:-----------|:------------------------------------------------------------------------------------------| | [Org-wide app settings](#manage-org-wide-app-settings) | Org-level | Use this setting to allow use of relevant apps in your org. | -| Block or unblock apps | App-level | Use this setting to allow a specific app in your org. You control which users use an app. | +| Block or unblock apps | App-level | Use this setting to allow a few specific apps in your org. | | [App permission policy](teams-app-permission-policies.md) or [app centric management](app-centric-management.md) | User-level | Let all users or let specific users use an app. | -You allow or block specific apps on either the Manage apps page or in the app details page. Manage apps page displays all the available app and the current org-level app status. To allow or block an app, follow these steps: +You allow or block specific apps or a Copilot agent on either the Manage apps page or in the app details page. If you [allow or block a Copilot agent in Microsoft 365 admin center](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps), then ensure that the allow or block settings match in the Teams admin center and those match for the same group of people. Manage apps page displays all the available app and the current org-level app status. To allow or block an app, follow these steps: 1. Sign in to the Teams admin center and access **Teams apps** > **[Manage apps](https://admin.teams.microsoft.com/policies/manage-apps)**. @@ -105,6 +107,8 @@ As an admin, you use one of the following methods to define access to apps for y * [App permission policies](teams-app-permission-policies.md) if you use policy-based method to define app access. * App assignment if you use [app centric management](app-centric-management.md) to define app access. +To make any apps or copilot agents available in your organization, ensure that the settings to allow these are the same in Teams admin center and in [Microsoft 365 admin center](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps) in the Integrated Apps page. + ## Manage org-wide app settings Use org-wide app settings to control whether users with an [F license](https://www.microsoft.com/microsoft-365/enterprise/frontline) get the tailored frontline app experience, whether users can install third-party apps, and whether users can upload custom apps in your organization. @@ -113,9 +117,8 @@ Use org-wide app settings to control whether users with an [F license](https://w :::image type="content" source="media/manage-apps-org-wide-app-settings.png" alt-text="Screenshot of the Org-wide app settings pane on the Manage apps page"::: -1. Under **Tailored apps**, turn off or turn on **Show tailored apps**. When this setting is on, users with an [F license](https://www.microsoft.com/microsoft-365/enterprise/frontline#office-SKUChooser-0dbn8nt) get the tailored frontline app experience. This experience pins the most relevant apps in Teams for frontline workers. To learn more, see [Tailor Teams apps for your frontline workers](pin-teams-apps-based-on-license.md). +1. Under **Tailored apps**, turn off or turn on **Show tailored apps**. When this setting is on, users with an [F license](https://www.microsoft.com/microsoft-365/enterprise/frontline#office-SKUChooser-0dbn8nt) get the tailored frontline app experience. This experience pins the most relevant apps in Teams for frontline workers. To learn more, see [Tailor Teams apps for your frontline workers](pin-teams-apps-based-on-license.md). This feature is available for F licenses. - This feature is available for F licenses. Other license types will be supported in the future. 1. Under **Third-party apps**, turn off or turn on these settings to control access to third-party apps in your organization: * **Allow third-party apps**: This setting controls whether users can use third-party apps. If you turn off this setting, your users can't add or use any third-party apps. App status of these apps shows as **Blocked org-wide**. @@ -171,7 +174,7 @@ You may have queries about admin settings or configuration, user flows and app f * We don't provide direct customer support for Teams apps but we provide the following safeguards, health checks, and certification methods for apps: * We proactively check Teams apps for issues and inform the developer to update their app. Scenarios covered are related to app health, functional issues reported by users to Microsoft, security issues, and so on. For details, see [Microsoft enforcement actions for published apps](/microsoftteams/platform/concepts/deploy-and-publish/appsource/post-publish/overview#possible-enforcement-actions). - * For Publisher Attested and Microsoft 365 certified apps, Microsoft provides the [security and compliance information of apps](overview-of-app-certification.md). + * For Publisher Attested and Microsoft 365 certified apps, Microsoft offers [security and compliance information](overview-of-app-certification.md#microsoft-365-certification). If app developers consent, Microsoft provides admins with the option to [download the detailed evidence submitted by developers](overview-of-app-certification.md#microsoft-365-certification) during the certification audits for apps or copilot agents. * Testing of all apps as part of its [app validation program](overview-of-app-validation.md) to ensure that all apps work as advertised. If apps don't work as suggested in the app listing, then we contact app developers to request either an update to the app. If app developers don't make the requested updates after a few reminders, we proactively remove the apps from Teams. * Certification to apps using [Microsoft 365 app compliance program](overview-of-app-certification.md) ensures that apps are compliant with the industry-standard frameworks. diff --git a/Teams/manage-bridge-settings.md b/Teams/manage-bridge-settings.md index 33c96f1f07..3212013ae1 100644 --- a/Teams/manage-bridge-settings.md +++ b/Teams/manage-bridge-settings.md @@ -1,7 +1,7 @@ --- title: Manage bridge settings in Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: ms.date: 09/04/2020 diff --git a/Teams/manage-email-communications.md b/Teams/manage-email-communications.md index 4a63765ec2..dd7f133a18 100644 --- a/Teams/manage-email-communications.md +++ b/Teams/manage-email-communications.md @@ -18,7 +18,7 @@ appliesto: --- # Manage email communications for events -**APPLIES TO:** ✖️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/manage-emergency-call-routing-policies.md b/Teams/manage-emergency-call-routing-policies.md index 2b5a143832..153a0e046f 100644 --- a/Teams/manage-emergency-call-routing-policies.md +++ b/Teams/manage-emergency-call-routing-policies.md @@ -1,7 +1,7 @@ --- title: Manage emergency call routing policies for Direct Routing -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jastark, roykuntz ms.date: 10/02/2019 diff --git a/Teams/manage-emergency-calling-policies.md b/Teams/manage-emergency-calling-policies.md index f6101319b8..1b3296a71c 100644 --- a/Teams/manage-emergency-calling-policies.md +++ b/Teams/manage-emergency-calling-policies.md @@ -1,7 +1,7 @@ --- title: Manage emergency calling policies in Microsoft Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jastark, roykuntz ms.date: 05/07/2024 diff --git a/Teams/manage-meeting-chat.md b/Teams/manage-meeting-chat.md index ae3c29dc99..ef7093a2e0 100644 --- a/Teams/manage-meeting-chat.md +++ b/Teams/manage-meeting-chat.md @@ -25,11 +25,13 @@ description: Learn to manage meeting chat in Teams meetings and manage meeting c # Manage chat in Microsoft Teams meetings -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls ## Overview -In Microsoft Teams, chat allows participants to exchange messages to each other before, during, and after meetings and webinars. For town halls, only presenters, organizers, and co-organizers can use chat with each other. As an admin you can control: +In Microsoft Teams, chat allows participants to exchange messages to each other before, during, and after meetings and webinars. For town halls, only presenters, organizers, and co-organizers can use chat with each other. To learn how attendees can use chat during town halls, see [Manage event chat for Microsoft Teams town halls](town-hall-chat.md). + +As an admin you can control: - Whether participants in your users' meetings and webinars can read and write chat messages. - Whether users in your organization can use chat when they're participants in Teams meetings hosted by other organizations where there isn’t a trusted relationship. diff --git a/Teams/manage-meeting-presentation-experience.md b/Teams/manage-meeting-presentation-experience.md index f39c54584d..2b2b79d93b 100644 --- a/Teams/manage-meeting-presentation-experience.md +++ b/Teams/manage-meeting-presentation-experience.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 12/11/2023 +ms.reviewer: nakulm, bryannyce +ms.date: 11/12/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -23,13 +23,13 @@ description: Learn about admin options for managing who can present, how content [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -Using Teams admin policies, sensitivity labels, and templates, you can control a wide variety of settings that determine the in-meeting experience for participants, including: +As an admin, with Teams admin policies, sensitivity labels, and templates, you can control various settings that determine the in-meeting experience for participants, including: - Who can present and who can give or request control - How content is shared and what collaboration tools are available - Attendee video, audio, and reactions -Meeting organizers can specify many of theses settings when they create the meeting, but you can enforce specific options for different users and groups in your organization by using admin policies, or for different types or meetings by using sensitivity labels and templates. This can help you meet your compliance needs for different types of meetings and meetings where sensitive information is being shared. +Meeting organizers can specify some of theses settings when they create a meeting. However, you can enforce specific options for different users and groups in your organization by using admin policies. You can also use sensitivity labels and templates to enforce these options for different types or meetings. These options can help you with meetings in your organization where sensitive information is being shared. > [!NOTE] > Meeting settings in sensitivity labels and custom meeting templates require Teams Premium. @@ -44,7 +44,7 @@ The following table shows where settings are available to manage who can present |Participants can give or request control|Yes|No|No|No| |External participants can give or request control|Yes|No|No|No| -By using these controls, you can limit who is able to share content on screen in meetings. +By using these controls, you can limit who can share content on screen in meetings. ### Default value for who can present in meetings @@ -54,18 +54,15 @@ The Teams admin meeting policy **Who can present** has the following options: - People in my org and guests - Everyone -This setting doesn't enforce the value, but rather specifies the default for new meetings created by users. Users can override this setting and choose any of the other options unless a specific value is enforced by a sensitivity label. +This setting doesn't enforce the value, but rather specifies the default for new meetings created by users. Users can override this setting and choose any of the other options unless a sensitivity label enforces a specific value. The default value of **Everyone** allows anyone to present in a meeting by default. If you have compliance requirements in your organization around who can present in meetings, consider changing this value to **People in my org and guests** or **Only organizers and co-organizers** to provide a more secure default for users. -To set the **Who can present** policy +To manage the **Who can present** policy, follow these steps: 1. In the Teams admin center, expand **Meetings**, and then select **Meeting policies**. - -1. Select the policy that you want to modify. - -1. Under **Meeting join & lobby**, select a value for **Who can present**. - +1. Select the policy that you want to edit. +1. In the **Meeting join & lobby** section, select a value for **Who can present**. 1. Select **Save**. ### Manage who can present by using sensitivity labels @@ -77,13 +74,13 @@ Meeting organizers can choose from the following options for who can present in - Specific people - Everyone -The default value shown when a user creates a meeting is specified by the **Who can present** policy mentioned above. +The **Who can present** policy specifies the default value shown when a user creates a meeting. You can restrict this setting by using a sensitivity label. For sensitive or highly sensitive meetings, consider restricting this setting to **Only me and co-organizers** or **Specific people** by using a sensitivity label. ### Teams admin policy: Participants can give or request control -By default, meeting participants can give control of their shared screen to another participant in the meeting. This is controlled by two Teams admin meeting policies: +By default, meeting participants can give control of their shared screen to another participant in the meeting. Two Teams admin meeting policies control this capability: - **Participants can give or request control** - This setting determines whether the user with this policy can give control of their shared desktop or window to other meeting participants. It's **On** by default. @@ -91,18 +88,14 @@ By default, meeting participants can give control of their shared screen to anot Depending on the compliance requirements of your organization, you can change these settings for some or all of your users. -To configure who can give control of a shared screen +To configure who can give control of a shared screen, follow these steps: 1. In the Teams admin center, expand **Meetings**, and then select **Meeting policies**. - 1. Select the policy that you want to modify. - 1. Under **Content sharing**: + - To prevent participants from giving control of a screen share to others, set **Participants can give or request control** to **Off**. - 1. To prevent participants from giving control of a screen share to others, set **Participants can give or request control** to **Off**. - - 1. To prevent external participants from being given control of a screen share, set **External participants can give or request control** to **On**. - + - To prevent external participants from being given control of a screen share, set **External participants can give or request control** to **On**. 1. Select **Save**. ## Manage which content and video is shared with attendees @@ -116,9 +109,9 @@ The following table shows settings that can help manage what content and video i |Screen sharing|Yes|No|No|No| |Manage what attendees see|No|No|Yes|Yes| -**Screen sharing** is a teams admin policy. With this policy, you can control if meeting attendees can share their entire screen or only a single application. Sharing the entire screen can be convenient, but it can increase the chances of accidentally sharing inappropriate information such as an email or open document. Consider if you want to restrict sharing to a single application for users or departments that often present sensitive information. You can also turn off screen sharing entirely with this policy. For more information, see [Manage meeting policies for content sharing](meeting-policies-content-sharing.md). +**Screen sharing** is a Teams admin policy. With this policy, you can control if meeting attendees can share their entire screen or only a single application. Sharing the entire screen can be convenient, but it can increase the chances of accidentally sharing inappropriate information such as an email or open document. Consider if you want to restrict sharing to a single application for users or departments that often present sensitive information. You can also turn off screen sharing entirely with this policy. For more information, see [Manage meeting policies for content sharing](meeting-policies-content-sharing.md). -**Manage what attendees see** is an option available to meeting organizers that can also be set by using a template. When this option is enabled, meeting organizers can control what content is shared on screen and who's video is visible. Organizers must intentionally bring shared content and video on screen before attendees can see it. This can help minimize the risk of sharing inappropriate content in a meeting. Consider if you want to enable or enforce this experience for sensitive meetings by using a meeting template. For more information, see [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16). +**Manage what attendees see** is an option available to meeting organizers that can also be set by using a template. When this option is enabled, meeting organizers can control what content is shared on screen and who's video is visible. Organizers must intentionally bring shared content and video on screen before attendees can see it. This feature can help minimize the risk of sharing inappropriate content in a meeting. Consider if you want to enable or enforce this experience for sensitive meetings by using a meeting template. For more information, see [Manage what attendees see in Teams meetings](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16). ## Manage presentation tools @@ -132,9 +125,9 @@ Teams offers several presentation tools that allow for interactive participation Each of these features can be managed through admin policies, but not through templates or sensitivity labels, nor by the meeting organizer. As such, they can be applied to users or groups, but not to specific meetings. For more information, see [Meeting policy settings - Content sharing](meeting-policies-content-sharing.md). -If you have meetings where sensitive information is being shared, you may want to disable Whiteboard and shared notes to avoid having sensitive information added to them. +You might want to turn off Whiteboard and shared notes to avoid having sensitive information added to specific meetings. -PowerPoint Live allows attendees to navigate forward and back in a PowerPoint presentation being shared on screen. This may allow attendees to see sensitive information before it's presented by the organizer. +PowerPoint Live allows attendees to navigate forward and back in a PowerPoint presentation being shared on screen. However, attendees might see sensitive information before the organizer presents it. Consider if there are users or groups in your organization who shouldn't use these features to avoid sharing sensitive information. @@ -148,16 +141,15 @@ The following table shows features that can help manage how meeting attendees in |Allow mic for attendees|No|No|Yes|Yes| |Reactions|Yes|No|Yes|Yes| -Attendee audio and video can make it easy for attendees to communicate during a meeting. These can both be controlled by the meeting organizer or by a meeting template. Depending on the type of meeting, you may want to allow or restrict these capabilities. +Attendee audio and video can make it easy for attendees to communicate during a meeting. The meeting organizer or a meeting template can control both of these features. Depending on the type of meeting, you might want to allow or restrict these capabilities. -For meetings that are presentations with minimal interaction from attendees, turning video and audio off can minimize distractions. +For meetings that are presentations with minimal interaction from attendees, turning off audio and video can minimize distractions. You could also advise meeting organizers to use a town hall instead. For details on town halls, see [Plan for town halls(plan-town-halls.md). -When recording meetings, video from participants might be considered personal data and infer regulatory requirements. +When users record meetings, video from participants might be considered personal data and can infer regulatory requirements. -If you choose to turn off reactions, remember that this will disable the hand-raise feature. (For presentation-style meetings, the Q&A feature may allow the needed interaction for attendees to ask questions.) +If you choose to turn off reactions, remember that this option disables the hand-raise feature. (For presentation-style meetings, the Q&A feature might allow the needed interaction for attendees to ask questions.) ## Related topics -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - -[Manage access to Microsoft Whiteboard for your organization](/microsoft-365/whiteboard/manage-whiteboard-access-organizations) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Manage access to Microsoft Whiteboard for your organization](/microsoft-365/whiteboard/manage-whiteboard-access-organizations) diff --git a/Teams/manage-meeting-recording-options.md b/Teams/manage-meeting-recording-options.md index aa85f2a1a4..e9444a6fb0 100644 --- a/Teams/manage-meeting-recording-options.md +++ b/Teams/manage-meeting-recording-options.md @@ -1,12 +1,12 @@ --- -title: Manage Microsoft Teams meeting recording options for sensitive meetings +title: Manage Microsoft Teams meeting recording and transcription options for sensitive meetings ms.author: wlibebe author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 12/11/2023 +ms.reviewer: lisma, ritikag +ms.date: 11/12/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -16,75 +16,101 @@ ms.collection: - m365initiative-meetings appliesto: - Microsoft Teams -description: Learn how to manage who can record Teams meetings, automatic recording, and the recording lifecycle for sensitive meetings. +description: Learn how to manage who can record and transcribe Teams meetings, automatic recording, and the recording lifecycle for sensitive meetings. --- -# Manage Microsoft Teams meeting recording options for sensitive meetings +# Manage Microsoft Teams meeting recording and transcription options for sensitive meetings [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -Teams is designed to allow easy recording for meeting participants. If you have compliance requirements around how meeting recordings are used, there are several options available for administrators and meeting organizers to help you use meeting recordings in a compliant way. +> [!NOTE] +> When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off. To learn more about Copilot, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). -The following table shows the features available to help you manage meeting recordings and where they're configured. +Teams is designed to allow easy recording and transcription for meeting participants and organizers. If you have compliance requirements around how meeting recordings and transcripts are used, there are several options available for you, as an admin and your meeting organizers to use meeting recordings and transcripts in a way that fits your needs. + +The following table shows the features available to help you manage meeting recordings and transcripts, and where they're configured. |Setting|Admin policy|Sensitivity label|Template|Meeting organizer| |:------|:----------:|:---------------:|:------:|:---------------:| +|Block or allow download of channel meeting recordings|Yes|No|No|No| +|Microsoft 365 Copilot in Teams meetings and events|Yes|No|Yes|Yes| |Meeting recording overall|Yes|No|No|No| -|Who can record|No|Yes|Yes|Yes| +|Privacy and Security URL|Yes|No|No|No| +|Record and transcribe automatically|No|Yes|Yes|Yes| +|Recordings and transcripts expiration|Yes|No|No|No| +|Transcription|Yes|No|No|Yes| |Require participant agreement for recording|Yes|No|No|No| -|Record automatically|No|Yes|Yes|Yes| -|Recording expiration|Yes|No|No|No| +|Who can record and transcribe|No|Yes|Yes|Yes| + +You control whether the ability to record meetings is available in your organization. Through sensitivity labels, meeting templates, and meeting organizer settings, both you and your meeting organizers can manage who can record and transcribe and whether meetings are automatically recorded and transcribed. -The Teams Administrator has overall control over whether meeting recording is enabled. Both meeting organizers and administrators can configure who can record and whether meetings are automatically recorded by using sensitivity labels, meeting templates, and meeting organizer settings. +## Block or allow download of channel meeting recordings -## Manage who can record meetings +You can set a Teams admin policy through PowerShell's **`-ChannelRecordingDownload`** parameter in the[Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) to control whether channel members can download meeting recordings. If you block the download of channel recordings, members can watch recordings, but can't download them. To learn more, see [Manage Teams recording policies for meetings and events](meeting-recording.md#block-or-allow-download-of-channel-meeting-recordings). -There are two options for who can record a meeting: +## Manage who can record and transcribe meetings + +There are two options for who can record and transcribe a meeting: - Organizers and co-organizers - Organizers, co-organizers, and presenters -This choice is normally made by the meeting organizer when they create the meeting. If you have meetings where sensitive information is being shared and you want to limit the ability to record to organizers only, you can enforce this setting by using a meeting template or sensitivity label. +The meeting organizer normally makes this choice when they create the meeting. To restrict recording to organizers in meetings with sensitive information, use a meeting template or sensitivity label to enforce this setting. + +If you need to prevent meetings from being recorded entirely, you must use the [Meeting recording meetings policy](meeting-recording.md#allow-or-prevent-users-from-recording-meetings) in the Teams admin center. This setting applies to the people or groups that you specify, but can't be applied via a meeting template or sensitivity label. + +## Microsoft 365 Copilot in Teams meetings and events + +With a Teams admin policy or meeting template, you can manage how meeting transcripts are used with Copilot. The only Copilot policy setting that you can enforce is **On with saved transcript required**. The other settings create a default that your organizers can change. For details, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). + +## Privacy and security URL -If you need to prevent meetings from being recorded entirely, you must configure the **Meeting recording** meetings policy in the Teams admin center. This setting applies to the people or groups that you specify. It can't be applied via a meeting template or sensitivity label. +With a Teams admin policy, you can add your custom privacy statement to Teams meeting recordings and transcripts in your organization. If your organization has a legal website that you want people to go to for any legal concerns, this policy allows you to display the URL. To learn more, see [Manage Teams recording policies for meetings and events](meeting-recording.md#set-a-custom-privacy-policy-url). ## Require participant agreement for recording -You can require participants to agree to being recorded before they can unmute or turn on their camera. Consent results are stored in the meeting attendance report. This is controlled through a Teams meeting policy. For details, see [Require participant agreement for recording](meeting-recording.md#require-participant-agreement-for-recording-and-transcription). +With a Teams meeting policy, you can require participants to agree to being recorded before they can unmute or turn on their camera. Consent results are stored in the meeting attendance report. For details, see [Require participant agreement for recording](meeting-recording.md#require-participant-agreement-for-recording-and-transcription). -## Automatic recording +## Record and transcribe automatically Meetings can be set to record automatically when they start. Normally, the meeting organizer makes this choice when they create the meeting. If there are certain types of meetings that should always be recorded, you can enforce this option by using a meeting template or a sensitivity label. -If all of a particular type of meeting must be recorded (for example, all sensitive meetings), consider enforcing this by using a sensitivity label. If only certain sensitive meetings need to be recorded, consider using meeting templates to configure this setting. You can create two templates that both use the same label, one which automatically records and another which doesn't. +If all of a particular type of meeting must be recorded (for example, all sensitive meetings), consider enforcing this option by using a sensitivity label. If only certain sensitive meetings need to be recorded, consider using meeting templates to configure this setting. You can create two templates that both use the same label, one which automatically records and another which doesn't. -## Recording lifecycle +For details on managing this option with meeting templates, see [IT admins - Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md#recording--transcription). -By default, meeting recordings are deleted after 120 days. This is configured by using two policies in the Teams admin center: +## Recording and transcription lifecycle -- **Recordings automatically expire** determines if meeting recordings are automatically deleted after a specified time. -- **Default expiration time** specifies the number of days after which recordings are deleted. The default is 120. +By default, meeting recordings and transcripts are deleted after 120 days. The following policies in the Teams admin center manage the recording lifecycle: -When a meeting participant records a meeting, the recording is stored in their OneDrive. Channel meetings are stored in the SharePoint site associated with the channel. Because meeting recordings are .mp4 files, they can be moved or deleted like any other file. If a meeting recording is moved from its original location, the expiration setting will no longer affect it. +- **Recordings automatically expire** determines if meeting recordings and transcripts are automatically deleted after a specified time. +- **Default expiration time** specifies the number of days after which recordings and transcripts are deleted. The default is 120. -The expiration feature is meant for removing old recordings to save storage space. It's not meant for enforcing compliance requirements. If you have compliance requirements around how long meeting recordings are retained or when they're deleted, consider storing them in a SharePoint library where you can apply [Microsoft Purview retention policies](/microsoft-365/compliance/retention). +When a meeting participant records a meeting, the recording is stored in the organizer's OneDrive. Channel meetings are stored in the SharePoint site associated with the channel. Because meeting recordings are .mp4 files, they can be moved or deleted like any other file. If a meeting recording is moved from its original location, the expiration setting no longer affects it. For details, see [Teams meeting recording storage and permissions in OneDrive and SharePoint](tmr-meeting-recording-change.md). -## Configure recording options for your organization +The expiration feature removes old recordings and transcripts to save storage space, but doesn't enforce compliance requirements. If you have meeting recording retention and deletion compliance requirements, consider storing them in a SharePoint library where you can apply [Microsoft Purview retention policies](/microsoft-365/compliance/retention). -For information about configuring admin meeting policies for meeting recordings, see [Teams meeting recording](meeting-recording.md). +## Transcription -For details about enforcing settings by using meeting templates and sensitivity labels, see [Configure Teams meetings with protection for sensitive data](configure-meetings-sensitive-protection.md) and [Configure Teams meetings with protection for highly sensitive data](configure-meetings-highly-sensitive-protection.md). +With a Teams admin policy, you can control whether captions and transcription features are available during playback of Teams meeting recordings. -## Related topics +Your organizers can manage which users can transcribe their meetings through the **Who can record and transcribe** setting in their **Meeting options**. To restrict transcription to organizers in meetings with sensitive information, use a meeting template or sensitivity label to enforce the **Who can record and transcribe** setting. -[Introduction to Teams policy-based recording for callings & meetings](teams-recording-policy.md) + For details on managing transcription, see [Admins- Manage transcription and captions for Teams meetings](meeting-transcription-captions.md). -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +## Manage recording options for your organization -[Options for meeting organizers in Microsoft Teams](https://support.microsoft.com/office/53261366-dbd5-45f9-aae9-a70e6354f88e) +For information about configuring admin meeting policies for meeting recordings, see [Teams meeting recording](meeting-recording.md). -[Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md) +For details about enforcing settings by using meeting templates and sensitivity labels, see [Configure Teams meetings with protection for sensitive data](configure-meetings-sensitive-protection.md) and [Configure Teams meetings with protection for highly sensitive data](configure-meetings-highly-sensitive-protection.md). + +## Related topics -[Use sensitivity labels to protect calendar items, Teams meetings, and chat](/purview/sensitivity-labels-meetings) +- [Introduction to Teams policy-based recording for callings & meetings](teams-recording-policy.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Options for meeting organizers in Microsoft Teams](https://support.microsoft.com/office/53261366-dbd5-45f9-aae9-a70e6354f88e) +- [Create a custom meeting template in Microsoft Teams](create-custom-meeting-template.md) +- [Use sensitivity labels to protect calendar items, Teams meetings, and chat](/purview/sensitivity-labels-meetings) +- [Meeting options in Microsoft Teams](https://support.microsoft.com/office/meeting-options-in-microsoft-teams-53261366-dbd5-45f9-aae9-a70e6354f88e) diff --git a/Teams/manage-meeting-templates.md b/Teams/manage-meeting-templates.md index 6edd1a41df..899ddf36e0 100644 --- a/Teams/manage-meeting-templates.md +++ b/Teams/manage-meeting-templates.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: janineco -ms.date: 12/11/2023 +ms.reviewer: idilates +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -23,13 +23,13 @@ description: Learn how Microsoft Teams Administrators can specify which meeting [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -You can use meeting template policies in Microsoft Teams to determine which meeting templates are available to users in your organization. +As an admin, you can use meeting template policies in Microsoft Teams to determine which meeting templates are available to users in your organization. ## Specify which meeting templates are available to users By default, the **Global (Org-wide default)** meeting template policy allows users to see all available templates, including default templates and any custom templates that you've created. If you want to limit which templates are available for different people or groups, you can create policies specifying this. -To create a meeting template policy +To create a meeting template policy, follow these steps: 1. In the Teams admin center, expand **Meetings** and select **Meeting template policies**. 1. Select **Add**. @@ -37,13 +37,13 @@ To create a meeting template policy 1. In the **Viewable templates** list, select any templates that you don't want users with this policy to see, and then select **Hide**. 1. Select **Save**. -Once you've created the policy, you need to assign it to users or groups. See [Assign policies to users and groups](assign-policies-users-and-groups.md) for more information. + Once you've created the policy, you need to assign it to users or groups. See [Assign policies to users and groups](assign-policies-users-and-groups.md) for more information. ## Change which meeting templates are visible to users You can update a meeting template policy if you want to change which templates are available to the users with that policy. -To edit a meeting template policy +To edit a meeting template policy, follow these steps: 1. In the Teams admin center, expand **Meetings** and select **Meeting template policies**. 1. Select the policy you want to change, and then select **Edit**. @@ -53,6 +53,6 @@ To edit a meeting template policy ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Predefined meeting templates in Microsoft Teams](predefined-meeting-template-reference.md) diff --git a/Teams/manage-phone-numbers-landing-page.md b/Teams/manage-phone-numbers-landing-page.md index ec4fc34b7a..3147b9e583 100644 --- a/Teams/manage-phone-numbers-landing-page.md +++ b/Teams/manage-phone-numbers-landing-page.md @@ -1,7 +1,7 @@ --- title: "Manage phone numbers for your organization" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: davlick, roykuntz, jenstr ms.date: 08/10/2023 diff --git a/Teams/manage-phone-numbers.md b/Teams/manage-phone-numbers.md index 9a269ea2f3..58d144f742 100644 --- a/Teams/manage-phone-numbers.md +++ b/Teams/manage-phone-numbers.md @@ -1,7 +1,7 @@ --- title: "Manage phone numbers for Calling Plan and services" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 03/21/2024 ms.topic: conceptual diff --git a/Teams/manage-planner-app.md b/Teams/manage-planner-app.md index b8631ff70f..b56779ff62 100644 --- a/Teams/manage-planner-app.md +++ b/Teams/manage-planner-app.md @@ -88,6 +88,14 @@ To pin the Planner app for your users, you can edit the global (Org-wide default As described in the [Frontline workers and managers](#frontline-workers-and-managers) section of this article, there's a default app setup policy for users who are assigned an [F license](https://www.microsoft.com/microsoft-365/enterprise/frontline). +## Use app-powered tasks to provide tailored task experiences + +The app-powered tasks feature offers your organization more control over what users see when they open their tasks in Planner. 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. + +To learn more, see [Manage app-powered tasks in Planner for tailored task experiences](app-powered-tasks-in-planner.md). + ## Frontline workers and managers ### Tailored frontline app experience in Teams diff --git a/Teams/manage-qna-for-teams.md b/Teams/manage-qna-for-teams.md index f1bdb7f954..ad3de99456 100644 --- a/Teams/manage-qna-for-teams.md +++ b/Teams/manage-qna-for-teams.md @@ -19,7 +19,7 @@ description: Learn about how IT Admins can set up, use, and manage Q&A in Q&A fo --- # Manage Q&A in Teams meetings and events -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls Q&A allows presenters, organizers, and co-organizers to take questions from attendees and answer them in real time. This feature is best suited for large, structured meetings and events– like town halls, webinars, all hands, and trainings. Town hall and webinar organizers and co-organizers can export the event's questions and answers to a CSV file. @@ -33,7 +33,7 @@ To learn more about Q&A for your users, see [Q&A in Microsoft Teams meetings](ht ## Prerequisites - Verify that access to [Viva Engage’s IPs and URLs](/microsoft-365/enterprise/urls-and-ip-address-ranges) isn't blocked. - - If you have a GCC tenant, verify that your firewall isn't blocking access to GCC services hosted from . + - If you have a GCC tenant, verify that your firewall isn't blocking access to GCC services hosted from `https://web.gov.yammer.com` and `https://*.rt.gov.yammer.com`. - To allow users in your organization to add Q&A to Teams meetings and events, you must confirm that sign-ins for the Office 365 Viva Engage service are enabled in Microsoft Entra ID. Follow these steps to confirm that sign-ins are enabled: - Go to the **Microsoft Entra admin center** > **Identity** > **Applications** > **Enterprise Applications** > **Viva Engage** > **Properties**. diff --git a/Teams/manage-queues-app.md b/Teams/manage-queues-app.md index baebb049f0..91bbe63ca2 100644 --- a/Teams/manage-queues-app.md +++ b/Teams/manage-queues-app.md @@ -3,7 +3,7 @@ title: Manage Queues app for Microsoft Teams author: mkbond007 ms.author: mabond manager: pamgreen -ms.date: 09/13/2024 +ms.date: 10/21/2024 ms.topic: article ms.reviewer: colongma, emkirby audience: admin @@ -25,9 +25,6 @@ search.appverid: MET150 ## Overview of Queues app -> [!NOTE] -> Queues app is currently in [public preview](public-preview-doc-updates.md). - The Queues app is a Teams-native solution designed to empower organizations to manage customer engagements efficiently, unlocking a set of advanced call functionalities for Teams Phone Call queues and Auto attendants, such as: - **Call queue management**: Admins can now delegate authorized users, also known as leads or supervisors, to manage and configure Call queues and Auto attendants directly from the Teams client. Authorized users can configure Call queues and Auto attendants from Call settings and they can opt agents into and out of the queue from Queues app. For more information, see [Configure Queues app](#configure-users-for-queues-app). @@ -61,7 +58,7 @@ For more information on Teams Phone, see [What is Teams Phone](what-is-phone-sys ### Prerequisites -Queues app is enabled by default for all Teams users in your organization who are assigned both a Teams Premium and Teams Phone license who and are voice enabled. +Queues app is enabled by default for all Teams users in your organization who are assigned both a Teams Premium and Teams Phone license and who are voice enabled. As an IT admin, you can manage Queues app settings and designate *authorized users* to perform various actions such as adding and removing queue members, changing call handling flows, configuring auto attendant greetings, and more. For users who need additional capabilities to manage day-to-day operational changes, such as team leads, you must set up a voice applications policy and assign this policy to authorized users. You can allow authorized users to control call queue membership, greetings, call routing rules, and hours of operation. @@ -96,7 +93,7 @@ App setup policies let you customize Teams to highlight the apps that are most i Any user with a Teams Phone and Teams Premium license has access to Queues app and can pin the app on their Teams client. If the app isn’t pinned by you via an app setup policy, your users can still view Queues app in the app bar flyout under **View more apps**. -To automatically pin the Queues app in the Teams client for your users, do the following: +To automatically pin the Queues app in the Teams client for your users, do the following steps: 1. In the Teams admin center, go to **Teams apps** > **Setup policies**. 1. Select an existing policy or select **Add** to create a new policy. diff --git a/Teams/manage-reactions-meetings.md b/Teams/manage-reactions-meetings.md index 7f9a0cfcc7..1d7178897b 100644 --- a/Teams/manage-reactions-meetings.md +++ b/Teams/manage-reactions-meetings.md @@ -25,7 +25,7 @@ description: Learn to manage meeting reactions in Teams meetings. # Manage reactions in Teams meetings and webinars -**APPLIES TO:** ✔️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls ## Overview diff --git a/Teams/manage-registration-form-webinars.md b/Teams/manage-registration-form-webinars.md index 20936e2ebc..19bd28f848 100644 --- a/Teams/manage-registration-form-webinars.md +++ b/Teams/manage-registration-form-webinars.md @@ -18,7 +18,7 @@ appliesto: --- # Manage the registration form for webinars -**APPLIES TO:** ✖️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls ## Overview diff --git a/Teams/manage-teams-overview.md b/Teams/manage-teams-overview.md index 941032b193..099b747551 100644 --- a/Teams/manage-teams-overview.md +++ b/Teams/manage-teams-overview.md @@ -3,7 +3,7 @@ title: Manage and monitor Teams author: MicrosoftHeidi ms.author: heidip manager: jtremper -ms.date: 10/06/2023 +ms.date: 10/28/2024 ms.topic: concept-article ms.service: msteams audience: admin diff --git a/Teams/manage-the-usage-of-a-phone-number.md b/Teams/manage-the-usage-of-a-phone-number.md index bad8f0e3f3..4ac6d236a4 100644 --- a/Teams/manage-the-usage-of-a-phone-number.md +++ b/Teams/manage-the-usage-of-a-phone-number.md @@ -1,7 +1,7 @@ --- title: "Manage the usage of a phone number" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: garciadaniel ms.date: 01/29/2024 diff --git a/Teams/manage-vod-publishing.md b/Teams/manage-vod-publishing.md index 67243b4e4c..146418f905 100644 --- a/Teams/manage-vod-publishing.md +++ b/Teams/manage-vod-publishing.md @@ -28,11 +28,11 @@ description: Learn how to manage video on demand (VOD) publishing for webinars a # Manage VOD publishing for webinars and town halls -**APPLIES TO:** ✖️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls Video on demand (VOD) for Microsoft Teams events allows webinar and town hall organizers to quickly publish and share event recordings. When organizers record these events, the recordings are uploaded to [OneDrive](tmr-meeting-recording-change.md#meetings-and-events). Once published, all attendees automatically receive an email with a link to view the recording. As an admin, you can manage which types of town halls and webinars organizers can publish recordings for. -For more information on publishing webinar and town halls for your users, see [Manage webinar recordings in Microsoft Teams](https://prod.support.services.microsoft.com/office/manage-webinar-recordings-in-microsoft-teams-8cf1ba61-c9d8-4628-8b5d-0dcdb8503144) and [Manage town hall recordings in Microsoft Teams](https://prod.support.services.microsoft.com/office/manage-town-hall-recordings-in-microsoft-teams-88ac3af7-db67-4556-a202-b73a1d6c2e46). +For more information on publishing webinar and town halls for your users, see [Manage webinar recordings in Microsoft Teams](https://support.microsoft.com/office/manage-webinar-recordings-in-microsoft-teams-8cf1ba61-c9d8-4628-8b5d-0dcdb8503144) and [Manage town hall recordings in Microsoft Teams](https://support.microsoft.com/office/manage-town-hall-recordings-in-microsoft-teams-88ac3af7-db67-4556-a202-b73a1d6c2e46). ## Webinars diff --git a/Teams/manage-voice-applications-policies.md b/Teams/manage-voice-applications-policies.md index 7b19529145..c2214a256d 100644 --- a/Teams/manage-voice-applications-policies.md +++ b/Teams/manage-voice-applications-policies.md @@ -8,7 +8,7 @@ ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams audience: admin -ms.date: 09/16/2024 +ms.date: 10/22/2024 ms.collection: - M365-voice - m365initiative-voice @@ -25,9 +25,6 @@ description: Learn how to use and manage voice applications policies in Microsof # Manage voice applications policies in Microsoft Teams -> [!NOTE] -> Most of these features are now in public preview. See the specific feature for more details. Information in this article is subject to change prior to general availability. - This article is for IT Pros and administrators who want to delegate Auto attendant and Call queue change capabilities to users in their organization. Voice applications policies allow you to create and assign voice application policies to authorized users. Voice application policies control what configuration changes an authorized user can make to the auto attendants and call queues they're authorized for. @@ -103,26 +100,26 @@ Voice applications policies control the configuration changes and actions an aut |Business hours greeting |This setting allows authorized users to change the Business Hours Greeting. |AllowAutoAttendantBusinessHoursGreetingChange |No, Generally Available | |After hours greeting |This setting allows authorized users to change the After Hours Greeting. |AllowAutoAttendantAfterHoursGreetingChange |No, Generally Available | |Holiday greeting |This setting allows authorized users to change the Holiday Greeting. |AllowAutoAttendantHolidayGreetingChange |No, Generally Available | -|Time zone |This setting allows authorized users to change the Time zone. |AllowAutoAttendantTimeZoneChange |Yes3 | -|Language |This setting allows authorized users to change the Lanugage. |AllowAutoAttendantLanguageChange |Yes3 | -|Business hours |This setting allows authorized users to change the auto attendant business hours schedule. |AllowAutoAttendantBusinessHoursChange |Yes, Public Preview | -|Holiday dates and hours |This setting allows authorized users to change the auto attendant holiday schedule.2|AllowAutoAttendantHolidaysChange |Yes, Public Preview | -|Business hours call routing|This setting allows authorized users to change the auto attendant business hours call flow. |AllowAutoAttendantBusinessHoursRoutingChange |Yes, Public Preview | -|After hours call routing|This setting allows authorized users to change the auto attendant after hours call flow. |AllowAutoAttendantAfterHoursRoutingChange |Yes, Public Preview | -|Holiday hours call routing|This setting allows authorized users to change the auto attendant holiday call flow. |AllowAutoAttendantHolidayRoutingChange |Yes, Public Preview | +|Time zone |This setting allows authorized users to change the Time zone. |AllowAutoAttendantTimeZoneChange |Yes3 | +|Language |This setting allows authorized users to change the Lanugage. |AllowAutoAttendantLanguageChange |Yes3 | +|Business hours |This setting allows authorized users to change the auto attendant business hours schedule. |AllowAutoAttendantBusinessHoursChange |Yes | +|Holiday dates and hours |This setting allows authorized users to change the auto attendant holiday schedule.2|AllowAutoAttendantHolidaysChange |Yes | +|Business hours call routing|This setting allows authorized users to change the auto attendant business hours call flow. |AllowAutoAttendantBusinessHoursRoutingChange |Yes | +|After hours call routing|This setting allows authorized users to change the auto attendant after hours call flow. |AllowAutoAttendantAfterHoursRoutingChange |Yes | +|Holiday hours call routing|This setting allows authorized users to change the auto attendant holiday call flow. |AllowAutoAttendantHolidayRoutingChange |Yes | Notes -1. The user requires a Teams Premium license and Queues app to access this functionality. -2. In order to change the holiday schedule, the user must be authorized for all auto attendants that reference the holiday. -3. This option is not currently available in Queues app. +1. The authorized user requires a Teams Premium license and Queues app to access this functionality. +1. In order to change the holiday schedule, the authorized user must be authorized for all auto attendants that reference the holiday. +1. This option isn't currently available for authorized users. ### Auto attendant - Reporting -|Teams voice applications policy setting |Description |PowerShell parameter |Teams Premium required1| -|----------------------------------------------------|---------------------------------------------------------------------------------|------------------------------------------|-----------------------| -|Real-time auto attendant metrics |This setting allows authorized users to access real-time auto attendant metrics. |RealTimeAutoAttendantMetricsPermission |Yes, Public Preview | -|Historical auto attendant metrics |This setting allows authorized users to access historical auto attendant metrics in Power BI and Queues App.|HistoricalAutoAttendantMetricsPermission |Power BI - No, Generally Available
Queues App - Yes, Public Preview| +|Teams voice applications policy setting |Description |PowerShell parameter |Teams Premium required1| +|-----------------------------------------|---------------------------------------------------------------------------------|------------------------------------------|-----------------------| +|Real-time auto attendant metrics |This setting allows authorized users to access real-time auto attendant metrics. |RealTimeAutoAttendantMetricsPermission |Yes | +|Historical auto attendant metrics |This setting allows authorized users to access historical auto attendant metrics in Power BI and Queues App.|HistoricalAutoAttendantMetricsPermission |Power BI - No, Generally Available
Queues App - Yes| Reporting values: @@ -135,7 +132,7 @@ Reporting values: Notes -1. The user requires a Teams Premium license and Queues app to access this functionality. +1. The authorized user requires a Teams Premium license and Queues app to access this functionality. ### Call queues - Features @@ -147,42 +144,42 @@ Notes |Shared voicemail greeting for call timeout|This setting allows authorized users to change the Timeout Shared Voicemail Greeting. |AllowCallQueueTimeoutSharedVoicemailGreetingChange|No, Generally Available| |Shared voicemail greeting for no agents|This setting allows authorized users to change the No Agents Shared Voicemail Greeting. |AllowCallQueueNoAgentSharedVoicemailGreetingChange|No3| |Language |This setting allows authorized users to change the Language. |AllowCallQueueLanguageChange |Yes3 | -|Membership |This setting allows authorized users to change the agents who are part of the call queue. |AllowCallQueueMembershipChange |Yes, Public Preview
See note 2| -|Conference mode |This setting allows authorized users to change the call queue conference mode setting. |AllowCallQueueConferenceModeChange |Yes, Public Preview| -|Agent routing method |This setting allows authorized users to change the call queue agent routing (selection) method. |AllowCallQueueRoutingMethodChange |Yes, Public Preview| -|Presence-based routing |This setting allows authorized users to change the call queue presence-based routing setting. |AllowCallQueuePresenceBasedRoutingChange |Yes, Public Preview| -|Opt out (queue configuration) |This setting allows authorized users to change the call queue opt-out setting. |AllowCallQueueOptOutChange |Yes, Public Preview| -|Routing for call overflow |This setting allows authorized users to change the call queue overflow handling. |AllowCallQueueOverflowRoutingChange |Yes, Public Preview| -|Routing for call timeout |This setting allows authorized users to change the call queue timeout handling. |AllowCallQueueTimeoutRoutingChange |Yes, Public Preview| -|Routing for no agents |This setting allows authorized users to change the call queue no agents handling. |AllowCallQueueNoAgentsRoutingChange |Yes, Public Preview| +|Membership |This setting allows authorized users to change the agents who are part of the call queue. |AllowCallQueueMembershipChange |Yes
See note 2| +|Conference mode |This setting allows authorized users to change the call queue conference mode setting. |AllowCallQueueConferenceModeChange |Yes | +|Agent routing method |This setting allows authorized users to change the call queue agent routing (selection) method. |AllowCallQueueRoutingMethodChange |Yes | +|Presence-based routing |This setting allows authorized users to change the call queue presence-based routing setting. |AllowCallQueuePresenceBasedRoutingChange |Yes | +|Opt out (queue configuration) |This setting allows authorized users to change the call queue opt-out setting. |AllowCallQueueOptOutChange |Yes | +|Routing for call overflow |This setting allows authorized users to change the call queue overflow handling. |AllowCallQueueOverflowRoutingChange |Yes | +|Routing for call timeout |This setting allows authorized users to change the call queue timeout handling. |AllowCallQueueTimeoutRoutingChange |Yes | +|Routing for no agents |This setting allows authorized users to change the call queue no agents handling. |AllowCallQueueNoAgentsRoutingChange |Yes | Notes -1. The user requires a Teams Premium license and Queues app to access this functionality. +1. The authorized user requires a Teams Premium license and Queues app to access this functionality. 1. If the Call queue uses a distribution list, security group, Microsoft 365 group or a Microsoft Teams channel the owner of these can add or remove agents without a Teams Premium license or Queues app. -1. This option is not currently available in Queues app. +1. This option isn't currently available for authorized users. ### Call queues - Agent actions |Teams voice applications policy setting|Description |PowerShell parameter |Teams Premium required1| |--------------------------------|------------------------------------------------------------------------|--------------------------------------|---------------------| -|Opt agent in/out of queue |This setting allows authorized users to change an agent's opt-in status.|AllowCallQueueAgentOptChange |Yes, Public Preview | -|Agent monitor mode |This setting is not currently available for authorized users. |CallQueueAgentMonitorMode |Yes2 | -|Agent monitor notification mode |This setting is not currently available for authorized users. |CallQueueAgentMonitorNotificationMode |Yes2 | +|Opt agent in/out of queue |This setting allows authorized users to change an agent's opt-in status.|AllowCallQueueAgentOptChange |Yes | +|Agent monitor mode |This setting isn't currently available for authorized users. |CallQueueAgentMonitorMode |Yes2 | +|Agent monitor notification mode |This setting isn't currently available for authorized users. |CallQueueAgentMonitorNotificationMode |Yes2 | Notes -1. The user requires a Teams Premium license and Queues app to access this functionality. -1. This option is not currently available in Queues app. +1. The authorized user requires a Teams Premium license and Queues app to access this functionality. +1. This option isn't currently available for authorized users. ### Call queues - Reporting |Teams voice applications policy setting|Description|PowerShell parameter|Teams Premium required1| |------------------------------------------------|--------------------------------|---------------------|---------------------| -|Real-time call queue metrics |This setting allows authorized users to access real-time call queue metrics. |RealTimeQueueMetricsPermission|Yes, Public Preview| -|Real-time agent metrics |This setting allows authorized users to access real-time call queue agent metrics. |RealTimeAgentMetricsPermission|Yes, Public Preview| -|Historical call queue metrics |This setting allows authorized users to access historical call queue metrics in Power BI and Queues App.|HistoricalQueueMetricsPermission|Power BI - No, Generally Available
Queues App - Yes, Public Preview| -|Historical agent metrics |This setting allows authorized users to access historical call queue agent metrics in Power BI and Queues App.|HistoricalAgentMetricsPermission|Power BI - No, Generally Available
Queues App - Yes, Public Preview| +|Real-time call queue metrics |This setting allows authorized users to access real-time call queue metrics. |RealTimeQueueMetricsPermission|Yes | +|Real-time agent metrics |This setting allows authorized users to access real-time call queue agent metrics. |RealTimeAgentMetricsPermission|Yes | +|Historical call queue metrics |This setting allows authorized users to access historical call queue metrics in Power BI and Queues App.|HistoricalQueueMetricsPermission|Power BI - No, Generally Available
Queues App - Yes1| +|Historical agent metrics |This setting allows authorized users to access historical call queue agent metrics in Power BI and Queues App.|HistoricalAgentMetricsPermission|Power BI - No, Generally Available
Queues App - Yes1. This option isn't currently available for authorized users.| Reporting values: @@ -195,7 +192,7 @@ Reporting values: Notes -1. The user requires a Teams Premium license and Queues app to access this functionality. +1. The authorized user requires a Teams Premium license and Queues app to access this functionality. ## Related articles diff --git a/Teams/manage-voice-routing-policies.md b/Teams/manage-voice-routing-policies.md index ecfe6c782e..2aa5025325 100644 --- a/Teams/manage-voice-routing-policies.md +++ b/Teams/manage-voice-routing-policies.md @@ -1,7 +1,7 @@ --- title: Manage call routing policies for Direct Routing -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: filippse ms.date: 11/17/2023 diff --git a/Teams/manage-voicemail-policies.md b/Teams/manage-voicemail-policies.md index 52db7475c9..4c991fc6da 100644 --- a/Teams/manage-voicemail-policies.md +++ b/Teams/manage-voicemail-policies.md @@ -1,7 +1,7 @@ --- title: Manage Voicemail Policies -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 05/21/2021 diff --git a/Teams/manage-voicemail-settings.md b/Teams/manage-voicemail-settings.md index e5f64fb820..b7b8143df4 100644 --- a/Teams/manage-voicemail-settings.md +++ b/Teams/manage-voicemail-settings.md @@ -1,7 +1,7 @@ --- title: Manage Cloud Voicemail settings -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 05/21/2021 diff --git a/Teams/manage-who-can-schedule-meetings.md b/Teams/manage-who-can-schedule-meetings.md index 7eab14ff9a..98468ebc01 100644 --- a/Teams/manage-who-can-schedule-meetings.md +++ b/Teams/manage-who-can-schedule-meetings.md @@ -24,7 +24,7 @@ description: Learn how to use Teams meeting policy settings to control who can s # Manage who can start instant meetings and schedule meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls As an admin, you can control which users can start instant meetings and schedule meetings in Teams. Managing who can schedule meetings can be useful for privacy and compliance reasons, allowing you to prevent certain users from setting up meetings. diff --git a/Teams/manage-your-network-topology.md b/Teams/manage-your-network-topology.md index 1410b4a54b..af64c8e98c 100644 --- a/Teams/manage-your-network-topology.md +++ b/Teams/manage-your-network-topology.md @@ -1,10 +1,10 @@ --- title: Manage your network topology for cloud voice features in Microsoft Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz -ms.date: 12/08/2023 +ms.date: 10/10/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -21,12 +21,14 @@ appliesto: - Microsoft Teams ms.localizationpriority: medium search.appverid: MET150 -description: Learn how to configure network settings for cloud voice features in Microsoft Teams. +description: Learn how to configure your network topology for cloud voice features in Microsoft Teams. --- # Manage your network topology for cloud voice features in Microsoft Teams -If your organization is deploying [Location-Based Routing for Direct Routing](location-based-routing-plan.md) or [dynamic emergency calling](configure-dynamic-emergency-calling.md), you must configure network settings for use with these cloud voice features in Microsoft Teams. Network settings are used to determine the location of a Teams client and include network regions, network sites, subnets, and trusted IP addresses. Depending on the cloud voice feature and capability that you're deploying, you configure some or all these settings. To learn more about these terms, see [Network settings for cloud voice features](cloud-voice-network-settings.md). +If your organization is deploying [Location-Based Routing for Direct Routing](location-based-routing-plan.md) or [dynamic emergency calling](configure-dynamic-emergency-calling.md), you must configure network settings for use with these cloud voice features in Microsoft Teams. + +Network settings are used to determine the location of a Teams client. The settings include network regions, network sites, subnets, and trusted IP addresses. Depending on the cloud voice feature and capability that you're deploying, you configure some or all of these settings. To learn more about these terms, see [Network settings for cloud voice features](cloud-voice-network-settings.md). You configure network settings on the **Network topology** page of the Microsoft Teams admin center or by using Windows PowerShell. @@ -37,7 +39,9 @@ Note that it can take some time (up to four hours) for some changes to network s ## Configure network settings in the Microsoft Teams admin center -You define network regions, network sites, and subnets on the **Network sites** tab of the **Network topology** page. Here, you can create or modify a network site, associate a site with a network region, associate a subnet to the site, turn on Location-based Routing, and assign emergency policies to the site. You can also add network regions that can be used globally for all sites. +You define network regions, network sites, and subnets on the **Network sites** tab of the **Network topology** page. + +You can create or modify a network site, associate a site with a network region, associate a subnet to the site, turn on Location-Based Routing, and assign emergency policies to the site. You can also add network regions that can be used globally for all sites. #### Add and configure a network site @@ -52,9 +56,12 @@ You define network regions, network sites, and subnets on the **Network sites** 5. To assign emergency services policies to the site, do one or both of the following: - If your organization uses Calling Plans, Operator Connect, or Direct Routing, under **Emergency calling policy**, select the policy that you want. - - If your organization deployed Direct Routing, under **Emergency call routing policy**, select the policy that you want. -6. To associate a subnet to the site, under **Subnets**, select **Add subnets**. Specify the IP version, IP address, network range, add a description, and then select **Apply**. Each subnet must be associated with a specific site. + - If your organization deployed Direct Routing, under **Emergency call routing policy**, select the policy that you want. + +6. (Optional) If you want to change the behavior for clients in this site, you can use the network roaming policy. Under **Network roaming policy**, select the policy that you want. For more information, see [Manage audio and video settings for clients](network-roaming-policy.md). + +7. To associate a subnet to the site, under **Subnets**, select **Add subnets**. Specify the IP version, IP address, network range, add a description, and then select **Apply**. Each subnet must be associated with a specific site. 7. Select **Save**. @@ -74,7 +81,7 @@ You manage external trusted IP addresses on the **Trusted IPs** tab on the **Net 1. In the left navigation of the Microsoft Teams admin center, go to **Locations** > **Network topology**, and then select the **Trusted IPs** tab. -2. Select **New**. +2. Select **Add**. 3. In the **Add trusted IP address** pane, specify the IP version, IP address, network range, add a description, and then select **Apply**. @@ -92,7 +99,7 @@ To complete the steps in this section, you need some familiarity with PowerShell ### Define network regions -Use the [New-CsTenantNetworkRegion](/powershell/module/teams/New-CsTenantNetworkRegion) cmdlet to define network regions. Note that the RegionID parameter is a logical name that represents the geography of the region and has no dependencies or restrictions and the CentralSite <site ID> parameter is optional. +To define network regions, use the [New-CsTenantNetworkRegion](/powershell/module/teams/New-CsTenantNetworkRegion) cmdlet. Note that the RegionID parameter is a logical name that represents the geography of the region and has no dependencies or restrictions; the CentralSite <site ID> parameter is optional. ```PowerShell New-CsTenantNetworkRegion -NetworkRegionID @@ -104,17 +111,17 @@ This example creates a network region named India: New-CsTenantNetworkRegion -NetworkRegionID "India" ``` -See also [Set-CsTenantNetworkRegion](/powershell/module/teams/set-cstenantnetworkregion). +For more information, see [Set-CsTenantNetworkRegion](/powershell/module/teams/set-cstenantnetworkregion). ### Define network sites -Use the [New-CsTenantNetworkSite](/powershell/module/teams/new-cstenantnetworksite) cmdlet to define network sites. Each network site must be associated with a network region. +To define network sites, use the [New-CsTenantNetworkSite](/powershell/module/teams/new-cstenantnetworksite) cmdlet. Each network site must be associated with a network region. ```PowerShell New-CsTenantNetworkSite -NetworkSiteID -NetworkRegionID ``` -This example creates two new network sites, Delhi and Hyderabad, in the India region: +The following example creates two new network sites, Delhi and Hyderabad, in the India region: ```PowerShell New-CsTenantNetworkSite -NetworkSiteID "Delhi" -NetworkRegionID "India" @@ -128,17 +135,17 @@ The following table shows the network sites defined in this example: |Site ID | Site 1 (Delhi) | Site 2 (Hyderabad) | |Region ID | Region 1 (India) | Region 1 (India) | -See also [Set-CsTenantNetworkRegion](/powershell/module/teams/set-cstenantnetworksite). +For more information, see [Set-CsTenantNetworkRegion](/powershell/module/teams/set-cstenantnetworksite). ### Define network subnets -Use the [New-CsTenantNetworkSubnet](/powershell/module/teams/new-cstenantnetworksubnet) cmdlet to define network subnets and associate them to network sites. Each network subnet can only be associated with one site. +To define network subnets and associate them to network sites, use the [New-CsTenantNetworkSubnet](/powershell/module/teams/new-cstenantnetworksubnet) cmdlet. You can associate each network subnet with one site only. ```PowerShell New-CsTenantNetworkSubnet -SubnetID -MaskBits -NetworkSiteID ``` -This example creates an association between subnet 192.168.0.0 and the Delhi network site and between subnet 2001:4898:e8:25:844e:926f:85ad:dd8e and the Hyderabad network site: +The following example creates an association between subnet 192.168.0.0 and the Delhi network site, and between subnet 2001:4898:e8:25:844e:926f:85ad:dd8e and the Hyderabad network site: ```PowerShell New-CsTenantNetworkSubnet -SubnetID "192.168.0.0" -MaskBits "24" -NetworkSiteID "Delhi" @@ -159,7 +166,7 @@ For multiple subnets, you can import a CSV file by using a script such as the fo Import-CSV C:\subnet.csv | foreach {New-CsTenantNetworkSubnet –SubnetID $_.Identity -MaskBits $_.Mask -NetworkSiteID $_.SiteID} ``` -In this example, the CSV file looks something like this: +In this example, the CSV file looks like the following: ```console Identity, Mask, SiteID @@ -169,11 +176,11 @@ Identity, Mask, SiteID 172.11.15.0, 28, Paris ``` -See also [Set-CsTenantNetworkSubnet](/powershell/module/teams/set-cstenantnetworksubnet). +For more information, see [Set-CsTenantNetworkSubnet](/powershell/module/teams/set-cstenantnetworksubnet). ### Define external subnets (external trusted IP addresses) -Use the [New-CsTenantTrustedIPAddress](/powershell/module/teams/new-cstenanttrustedipaddress) cmdlet to define external subnets and assign them to the tenant. You can define an unlimited number of external subnets for a tenant. +To define external subnets and assign them to the tenant, use the [New-CsTenantTrustedIPAddress](/powershell/module/teams/new-cstenanttrustedipaddress) cmdlet. You can define an unlimited number of external subnets for a tenant. ```PowerShell New-CsTenantTrustedIPAddress -IPAddress -MaskBits -Description @@ -185,9 +192,9 @@ For example: New-CsTenantTrustedIPAddress -IPAddress 198.51.100.0 -MaskBits 30 -Description "Contoso address" ``` -See also [Set-CsTenantTrustedIPAddress](/powershell/module/teams/set-cstenanttrustedipaddress). +For more information, see [Set-CsTenantTrustedIPAddress](/powershell/module/teams/set-cstenanttrustedipaddress). -## Enabling network roaming policies +## Enable network roaming policies Once you configure your network roaming policies, you need to enable **Network configuration lookup*** within each of your **Meeting Policies** in the Teams admin center under **Meetings > Meeting Policies.** diff --git a/Teams/media/acm-add-modify-access.png b/Teams/media/acm-add-modify-access.png index 891299f804..0802a441cc 100644 Binary files a/Teams/media/acm-add-modify-access.png and b/Teams/media/acm-add-modify-access.png differ diff --git a/Teams/media/acm-app-filter.png b/Teams/media/acm-app-filter.png index 35cf6ee8f1..3b6dd58ffa 100644 Binary files a/Teams/media/acm-app-filter.png and b/Teams/media/acm-app-filter.png differ diff --git a/Teams/media/acm-manage-user-apps-tab.png b/Teams/media/acm-manage-user-apps-tab.png index 6983197a4a..faf2bace8e 100644 Binary files a/Teams/media/acm-manage-user-apps-tab.png and b/Teams/media/acm-manage-user-apps-tab.png differ diff --git a/Teams/media/acm-migration-review-large.png b/Teams/media/acm-migration-review-large.png new file mode 100644 index 0000000000..dadf32b291 Binary files /dev/null and b/Teams/media/acm-migration-review-large.png differ diff --git a/Teams/media/acm-migration-review.png b/Teams/media/acm-migration-review.png index fb29aae8af..789c34b906 100644 Binary files a/Teams/media/acm-migration-review.png and b/Teams/media/acm-migration-review.png differ diff --git a/Teams/media/acm-migration-select-policies-large.png b/Teams/media/acm-migration-select-policies-large.png index e2e352e5d0..4a9b54873d 100644 Binary files a/Teams/media/acm-migration-select-policies-large.png and b/Teams/media/acm-migration-select-policies-large.png differ diff --git a/Teams/media/acm-migration-select-policies.png b/Teams/media/acm-migration-select-policies.png index d6ece9dafd..b05588b316 100644 Binary files a/Teams/media/acm-migration-select-policies.png and b/Teams/media/acm-migration-select-policies.png differ diff --git a/Teams/media/acm-org-wide-app-settings.png b/Teams/media/acm-org-wide-app-settings.png index 2c82d3c35c..1866985b26 100644 Binary files a/Teams/media/acm-org-wide-app-settings.png and b/Teams/media/acm-org-wide-app-settings.png differ diff --git a/Teams/media/acm-policy-retirement.png b/Teams/media/acm-policy-retirement.png new file mode 100644 index 0000000000..9c8c505e22 Binary files /dev/null and b/Teams/media/acm-policy-retirement.png differ diff --git a/Teams/media/acm-remove-access-large.png b/Teams/media/acm-remove-access-large.png index 3b10be63b5..f055ff62fb 100644 Binary files a/Teams/media/acm-remove-access-large.png and b/Teams/media/acm-remove-access-large.png differ diff --git a/Teams/media/acm-remove-access.png b/Teams/media/acm-remove-access.png index 80b1a61752..28a237fb6c 100644 Binary files a/Teams/media/acm-remove-access.png and b/Teams/media/acm-remove-access.png differ diff --git a/Teams/media/acm-start-prompt.png b/Teams/media/acm-start-prompt.png index d97edbc9ca..dd1dba781e 100644 Binary files a/Teams/media/acm-start-prompt.png and b/Teams/media/acm-start-prompt.png differ diff --git a/Teams/media/acm-verify-per-app-large.png b/Teams/media/acm-verify-per-app-large.png index ab7829b3fc..f9beea303f 100644 Binary files a/Teams/media/acm-verify-per-app-large.png and b/Teams/media/acm-verify-per-app-large.png differ diff --git a/Teams/media/acm-verify-per-app.png b/Teams/media/acm-verify-per-app.png index a6514e9638..a78e9af2dc 100644 Binary files a/Teams/media/acm-verify-per-app.png and b/Teams/media/acm-verify-per-app.png differ diff --git a/Teams/media/app-powered-tasks-in-planner.png b/Teams/media/app-powered-tasks-in-planner.png new file mode 100644 index 0000000000..3a7c3256b0 Binary files /dev/null and b/Teams/media/app-powered-tasks-in-planner.png differ diff --git a/Teams/media/captcha-audio-expand.png b/Teams/media/captcha-audio-expand.png new file mode 100644 index 0000000000..1ac7a0dfc6 Binary files /dev/null and b/Teams/media/captcha-audio-expand.png differ diff --git a/Teams/media/captcha-audio-small.png b/Teams/media/captcha-audio-small.png new file mode 100644 index 0000000000..9bad7eb810 Binary files /dev/null and b/Teams/media/captcha-audio-small.png differ diff --git a/Teams/media/captcha-text-expand.png b/Teams/media/captcha-text-expand.png new file mode 100644 index 0000000000..a7b4a83a3b Binary files /dev/null and b/Teams/media/captcha-text-expand.png differ diff --git a/Teams/media/captcha-text-small.png b/Teams/media/captcha-text-small.png new file mode 100644 index 0000000000..3e8969d453 Binary files /dev/null and b/Teams/media/captcha-text-small.png differ diff --git a/Teams/media/circle-check.png b/Teams/media/circle-check.png new file mode 100644 index 0000000000..526069a1a7 Binary files /dev/null and b/Teams/media/circle-check.png differ diff --git a/Teams/media/circle-no.png b/Teams/media/circle-no.png new file mode 100644 index 0000000000..3df92742d1 Binary files /dev/null and b/Teams/media/circle-no.png differ diff --git a/Teams/media/compliance-recorder-expandable.png b/Teams/media/compliance-recorder-expandable.png new file mode 100644 index 0000000000..2b868a5510 Binary files /dev/null and b/Teams/media/compliance-recorder-expandable.png differ diff --git a/Teams/media/compliance-recorder-small.png b/Teams/media/compliance-recorder-small.png new file mode 100644 index 0000000000..cd96556035 Binary files /dev/null and b/Teams/media/compliance-recorder-small.png differ diff --git a/Teams/media/connectors-attention-required.png b/Teams/media/connectors-attention-required.png new file mode 100644 index 0000000000..4e39afcbee Binary files /dev/null and b/Teams/media/connectors-attention-required.png differ diff --git a/Teams/media/connectors-update-url.png b/Teams/media/connectors-update-url.png new file mode 100644 index 0000000000..0c733e8ce6 Binary files /dev/null and b/Teams/media/connectors-update-url.png differ diff --git a/Teams/media/connectors-url-updated.png b/Teams/media/connectors-url-updated.png new file mode 100644 index 0000000000..9e81573094 Binary files /dev/null and b/Teams/media/connectors-url-updated.png differ diff --git a/Teams/media/m365-cert-download-evidence.png b/Teams/media/m365-cert-download-evidence.png new file mode 100644 index 0000000000..6f959194c6 Binary files /dev/null and b/Teams/media/m365-cert-download-evidence.png differ diff --git a/Teams/media/manage-apps-acm-org.png b/Teams/media/manage-apps-acm-org.png new file mode 100644 index 0000000000..e5f639245b Binary files /dev/null and b/Teams/media/manage-apps-acm-org.png differ diff --git a/Teams/media/manage-apps-policy-org.png b/Teams/media/manage-apps-policy-org.png new file mode 100644 index 0000000000..47fca74070 Binary files /dev/null and b/Teams/media/manage-apps-policy-org.png differ diff --git a/Teams/media/manage-apps.png b/Teams/media/manage-apps.png deleted file mode 100644 index bc1efd5f99..0000000000 Binary files a/Teams/media/manage-apps.png and /dev/null differ diff --git a/Teams/media/manage-channel-option.png b/Teams/media/manage-channel-option.png new file mode 100644 index 0000000000..202a07d82e Binary files /dev/null and b/Teams/media/manage-channel-option.png differ diff --git a/Teams/media/mtr-devices/auto-id.png b/Teams/media/mtr-devices/auto-id.png new file mode 100644 index 0000000000..bc961de0ca Binary files /dev/null and b/Teams/media/mtr-devices/auto-id.png differ diff --git a/Teams/media/mtr-devices/captions-and-transcripts-on.png b/Teams/media/mtr-devices/captions-and-transcripts-on.png new file mode 100644 index 0000000000..1fe1901cff Binary files /dev/null and b/Teams/media/mtr-devices/captions-and-transcripts-on.png differ diff --git a/Teams/media/mtr-devices/captions-and-transcripts.png b/Teams/media/mtr-devices/captions-and-transcripts.png new file mode 100644 index 0000000000..5a7be22191 Binary files /dev/null and b/Teams/media/mtr-devices/captions-and-transcripts.png differ diff --git a/Teams/media/mtr-devices/noise-suppression.png b/Teams/media/mtr-devices/noise-suppression.png new file mode 100644 index 0000000000..274ad6fbea Binary files /dev/null and b/Teams/media/mtr-devices/noise-suppression.png differ diff --git a/Teams/media/mtr-devices/voice-isolation.png b/Teams/media/mtr-devices/voice-isolation.png new file mode 100644 index 0000000000..03a46f987e Binary files /dev/null and b/Teams/media/mtr-devices/voice-isolation.png differ diff --git a/Teams/media/mtr-devices/voice-profile.png b/Teams/media/mtr-devices/voice-profile.png new file mode 100644 index 0000000000..9917f64ba4 Binary files /dev/null and b/Teams/media/mtr-devices/voice-profile.png differ diff --git a/Teams/media/watermark-expand.png b/Teams/media/watermark-expand.png new file mode 100644 index 0000000000..d5b36b076e Binary files /dev/null and b/Teams/media/watermark-expand.png differ diff --git a/Teams/media/watermark-small.png b/Teams/media/watermark-small.png new file mode 100644 index 0000000000..2282a1886c Binary files /dev/null and b/Teams/media/watermark-small.png differ diff --git a/Teams/media/x-for-no.png b/Teams/media/x-for-no.png new file mode 100644 index 0000000000..47464b7541 Binary files /dev/null and b/Teams/media/x-for-no.png differ diff --git a/Teams/meeting-policies-audio-and-video.md b/Teams/meeting-policies-audio-and-video.md index 443b979124..7a3aca6a4a 100644 --- a/Teams/meeting-policies-audio-and-video.md +++ b/Teams/meeting-policies-audio-and-video.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: casjacks -ms.date: 03/15/2021 +ms.date: 10/31/2024 audience: admin ms.localizationpriority: medium search.appverid: MET150 @@ -25,48 +25,51 @@ description: Learn to manage meeting policy settings in Teams for audio and vide # Meeting policy settings for audio & video -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls -This article describes the meeting policy settings specific to audio and video for meetings, webinars, and town halls. In town halls, only presenters, organizers, and co-organizers can use their cameras and microphones. +This article describes the audio and video meeting policy settings for meetings, webinars, and town halls. In town halls, only presenters, organizers, and co-organizers can use their cameras and microphones. To access audio and video settings, follow these steps: -1. In the Teams admin center, expand **Meetings**. -1. Select **Meeting policies**. -1. Select the policy that you want to edit. -1. Scroll to the **Audio & video** section of the policy page. +1. In the Teams admin center, expand **Meetings** and select **Meeting policies**. +1. Either select an existing policy or create a new one. +1. Navigate to the **Audio & video** section and select your desired values (described in the following sections) for **Mode for IP audio**, **Mode for IP video**, **Video conferencing**, **Media rate (Kbps)**, and **Participants can use video effects**. 1. When you've completed your changes, select **Save**. +Explore the following articles to learn how to manage these additional meeting audio and video policies: + +- [Stream Teams meetings](stream-teams-meetings.md) +- [Broadcast meeting content](use-NDI-in-meetings.md) +- [Manage your network topology for cloud voice features in Microsoft Teams](manage-your-network-topology.md#configure-network-settings-in-the-microsoft-teams-admin-center) + ## Mode for IP audio This is a per-user policy. This setting controls whether audio can be turned on in meetings and group calls. Here are the values for this setting. |Setting value|Behavior| |---|---| -|**Outgoing and incoming audio enabled**|Outgoing and incoming audio is allowed in the meeting. This is the default setting.| -|**Not enabled**|Outgoing and incoming audio is turned off in the meeting.| +|**Outgoing and incoming audio enabled**|**This is the default setting.** This user can both use and access outgoing and incoming audio in meetings.| +|**Not enabled**|This user can still schedule and organize meetings. However, they can't use audio during the meetings. To join a meeting, they must dial in or have the meeting call them and join by phone.| -If set to **Not enabled** for a user, that user can still schedule and organize meetings but they can't use audio. To join a meeting, they must dial in or have the meeting call and join them by phone. Meeting participants who don't have any policies assigned (for example, anonymous participants) have this set to **Outgoing and incoming audio enabled** by default. On Teams mobile clients, if this setting isn't enabled, the user has to dial in to the meeting. + Meeting participants who don't have any policies assigned (for example, anonymous participants) have **Mode for IP audio** set to **Outgoing and incoming audio enabled**. On Teams mobile clients, if this setting isn't set to **Outgoing and incoming audio enabled**, the user must dial in to the meeting. This setting doesn't apply to 1:1 calls. To restrict 1:1 calls, [configure a Teams calling policy](teams-calling-policy.md) and turn off the **Make private calls** setting in the Teams admin center. This setting also doesn't apply to conference room devices such as Surface Hub and Microsoft Teams Rooms devices. This setting isn't available for Microsoft 365 Government Community Cloud (GCC), GCC High, or Department of Defense (DoD) environments. -To learn more, see [Manage audio/video for meeting participants](#manage-audiovideo-for-meeting-participants). - ## Mode for IP video -This is a per-user policy. This setting controls whether outgoing and incoming video can be turned on in meetings and group calls. Here are the values for this setting. +This is a both a per-user and per-organizer policy. This setting controls both outgoing and incoming video for meetings and group calls that a user organizes or attends. The following table shows the behaviors for this setting: -|Setting value|Behavior| -|---|---| -|**Outgoing and incoming video enabled**|Outgoing and incoming video is allowed in the meeting. This is the default setting.| -|**Not enabled**|Outgoing and incoming video is turned off in the meeting. On Teams mobile clients, users can't share videos or photos in the meeting.

If **Mode for IP audio** is off, then **Mode for IP video** also stays off.| +|**Mode for IP video** policy value|Meetings the user organizes|Meetings the user attends| +|:-|:------------------------|:------------------------| +|**Outgoing and incoming video enabled**|All attendees can use video unless the policy you assigned to them prevents it.|This user can use video unless the organizer's settings prevents it.| +|**Not enabled**|No participants can turn video in the meeting.|This user can't turn on or view video. Other participants can only turn on and view video if both their assigned policy and the organizer's assigned policy allow it.| -If set to **Not enabled** for a user, that user can't turn on video or view videos shared by other meeting participants. Meeting participants who don't have any policies assigned (for example, anonymous participants) have this set to **Outgoing and incoming video enabled** by default. +If set to **Not enabled** for a user, that user can't turn on video or view other meeting participants' videos. Meeting participants who don't have any policies assigned (for example, anonymous participants) have **Mode for IP video** set to **Outgoing and incoming video enabled**. This setting doesn't apply to conference room devices such as Surface Hub and Microsoft Teams Rooms devices. @@ -79,28 +82,19 @@ To learn more, see [Manage audio/video for meeting participants](#manage-audiovi > [!IMPORTANT] > Currently, the **Video conferencing** setting doesn't turn off video for meetings and events. Your organizers should instead use the **Allow camera for attendees** setting in their **Meeting Options** to control video access in their meetings and events. To learn more, see the [Which video conferencing policy setting takes precedence](#which-video-policy-setting-takes-precedence) and [Manage audio/video for meeting participants](#manage-audiovideo-for-meeting-participants) sections in this article. -This is a combination of a per-organizer and per-user policy that controls which users' meetings have outgoing video. The Video conferencing setting controls whether video can be turned on in meetings hosted by a user and in 1:1 and group calls started by a user. On Teams mobile clients, this setting controls whether users can share photos and videos in a meeting. +This is a combination of a per-organizer and per-user policy that controls which users' meetings have outgoing video. The **Video conferencing** setting controls whether video can be turned on in meetings a user organizes and in 1:1 and group calls a user starts. On Teams mobile clients, this setting controls whether users can turn on their cameras in a meeting. When both the meeting organizer and participants have this policy set to **On**, participants can share video during the meeting. Meeting participants who don't have any assigned policies (for example, anonymous and trusted participants) inherit the meeting organizer's policy. -For a given user, if this setting is on: +If you set **Video conferencing** to **On** for a user: -- Meetings they organize will allow video -- They can use their video in meetings they attend +- Meetings they organize allow video +- They can use their video in meetings they attend. -If this setting is off: +If you set **Video conferencing** to **Off** for a user: -- Meetings they organize won't allow video -- They can't use their video in meetings they attend - -For a given user, the **Mode for IP video** setting affects video in both meetings they organize and meetings they attend. See the following table for details. - -||Meetings the user organizes|Meetings the user attends| -|:-|:------------------------|:------------------------| -|**Mode for IP video** set to **On** for the user|All attendees can use video unless the policy assigned to them prohibits it.|User can use video unless the organizer's policy prohibits it.| -|**Mode for IP video** set to **Off** for the user|No attendees can use video.|User can't use video. Other attendees may be able to use video if the policy assigned to them and the policy assigned to the meeting organizer allow it.| - -To learn more, see [Manage audio/video for meeting participants](#manage-audiovideo-for-meeting-participants). +- Meetings they organize don't allow video +- They can't use their video in meetings they attend. ### Which video policy setting takes precedence? @@ -118,9 +112,9 @@ For a user, the most restrictive policy setting for video takes precedence. Here |If you want to...|Set the following policy settings| |---|---| -|Enable audio and video for participants in meetings|Mode for IP audio: **Outgoing and incoming audio enabled** (default)
Mode for IP video: **Outgoing and incoming video enabled** (default)
Video conferencing: **N/A**| -|Disable audio and video for participants in meetings|Mode for IP audio: **Not enabled**
Mode for IP video: **Disabled**
Video conferencing: **N/A**| -|Disable video for participants in meetings (participants have audio only)|Mode for IP audio: **Enable outgoing and incoming audio**
Mode for IP video: **Not enabled**
Video conferencing: **N/A** +|Turn on audio and video for participants in meetings|Mode for IP audio: **Outgoing and incoming audio enabled** (default)
Mode for IP video: **Outgoing and incoming video enabled** (default)
Video conferencing: **N/A**| +|Turn off audio and video for participants in meetings|Mode for IP audio: **Not enabled**
Mode for IP video: **Not enabled**
Video conferencing: **N/A**| +|Turn on video for participants in meetings (participants have audio only)|Mode for IP audio: **Outgoing and incoming audio enabled**
Mode for IP video: **Not enabled**
Video conferencing: **N/A**| The most restrictive policy between the meeting organizer’s policy and the user’s policy applies. For example, if an organizer has a policy that restricts video and a user’s policy doesn't restrict video, meeting participants inherit the policy of the meeting organizer and don't have access to video in meetings. This means that they can join the meeting with audio only. @@ -153,16 +147,16 @@ This is a per-user policy. This setting controls whether users can customize the Use [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) or [New-CsTeamsMeetingPolicy](/powershell/module/teams/new-csteamsmeetingpolicy) with the *VideoFiltersMode* parameter to configure the values in PowerShell. -> [!NOTE] -> Images uploaded by users aren't screened by Teams. When you use the **All video effects** setting, you should have internal organization policies to prevent users from uploading offensive or inappropriate images, or images your organization doesn't have rights to use for Teams meeting backgrounds. +To learn how to customize your users' backgrounds, see [IT Admins- Manage and create custom meeting backgrounds for Teams meetings](custom-meeting-backgrounds.md). -For information about using custom background images for your organization, see [Custom meeting backgrounds for Teams Meetings](custom-meeting-backgrounds.md). +> [!NOTE] +> Teams doesn't screen the images your users upload. When you use the **All video effects** setting, you should have internal organization policies to prevent users from uploading offensive or inappropriate images, or images your organization doesn't have rights to use for Teams meeting backgrounds. ## Far end camera control (FECC) for pan tilt zoom (PTZ) cameras Far end camera control is a policy that can be assigned to Teams Rooms resource accounts. It allows PTZ cameras that are connected to Teams Rooms to be controlled by meeting participants in the Teams client app during meetings. -To use far end camera control, meeting participants will need to get the **PTZ Camera Controls** app. See [Allow and block apps](manage-apps.md#allow-or-block-apps) to learn how to make the app available in your organization's app store. +To use far end camera control, meeting participants need to get the **PTZ Camera Controls** app. To learn how to make the app available in your organization's app store, see [Allow and block apps](manage-apps.md#allow-or-block-apps). To specify who can use far end camera control in a meeting, create and assign a new policy to a Teams Rooms resource account using the [New-CsTeamsMeetingPolicy](/powershell/module/teams/new-csteamsmeetingpolicy) cmdlet, or use [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) to modify an existing one. Set the `TeamsCameraFarEndPTZMode` parameter to one of the following values: diff --git a/Teams/meeting-policies-content-sharing.md b/Teams/meeting-policies-content-sharing.md index 71d7471873..e7268ec5f4 100644 --- a/Teams/meeting-policies-content-sharing.md +++ b/Teams/meeting-policies-content-sharing.md @@ -25,7 +25,7 @@ description: Learn to manage meeting policy settings in Teams for content sharin # Manage meeting policies for content sharing -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls Content sharing settings control how users present a screen or app during a chat, meeting, webinar, or town hall. You can configure admin settings for screen sharing mode, PowerPoint sharing, whiteboard, and shared notes. (For information about how to manage who can present and who can request control, see [Manage who can present and request control in Teams meetings](meeting-who-present-request-control.md).) diff --git a/Teams/meeting-policies-overview.md b/Teams/meeting-policies-overview.md index e942170e4c..99c63b5e19 100644 --- a/Teams/meeting-policies-overview.md +++ b/Teams/meeting-policies-overview.md @@ -24,7 +24,7 @@ description: Learn to manage meeting and event policy settings in Teams and use --- # Manage meeting and event policies in Microsoft Teams -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls As an admin, you can use meeting and event policies to control the features that are available to organizers and participants of meetings, webinars, and town halls in your organization. Depending on the feature, you can manage meeting policies in the Microsoft Teams admin center or through [PowerShell](teams-powershell-overview.md). diff --git a/Teams/meeting-privacy-statement.md b/Teams/meeting-privacy-statement.md index 10a4ad6424..19ac70d741 100644 --- a/Teams/meeting-privacy-statement.md +++ b/Teams/meeting-privacy-statement.md @@ -24,7 +24,7 @@ appliesto: # Customize and display your privacy statement in the meeting join experience -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls Microsoft Teams enables businesses to schedule and conduct business-to-customer engagements with customers, clients, and other people outside your organization, as well as with employees within your organization. Organizations have a need to make their privacy statement available to attendees when they join a meeting, especially in engagements with external participants. diff --git a/Teams/meeting-recording.md b/Teams/meeting-recording.md index b1bbb78d09..67b7d9880c 100644 --- a/Teams/meeting-recording.md +++ b/Teams/meeting-recording.md @@ -25,9 +25,12 @@ description: Learn how to deploy features in Teams meetings to record audio, vid # Manage Teams recording policies for meetings and events -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +> [!NOTE] +> When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off. To learn more about Copilot, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). + +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls -In Microsoft Teams, your users can record their Teams meetings, webinars, and town halls to capture audio, video, and screen sharing activity. This type of recording is called [convenience recording](teams-recording-policy.md#compliance-vs-convenience-recording). The recording happens in Microsoft 365 and is saved to OneDrive or SharePoint, which must be enabled for the user. For details on OneDrive and SharePoint recording storage, see [Use OneDrive and SharePoint for meeting recordings](tmr-meeting-recording-change.md). +In Microsoft Teams, your users can record their Teams meetings, webinars, and town halls to capture audio, video, and screen sharing activity. This type of recording is called [convenience recording](teams-recording-policy.md). The recording happens in Microsoft 365 and is saved to OneDrive or SharePoint, which must be enabled for the user. For details on OneDrive and SharePoint recording storage, see [Use OneDrive and SharePoint for meeting recordings](tmr-meeting-recording-change.md). To learn about recording for live events, see [Live event recording policies in Teams](teams-live-events/live-events-recording-policies.md). diff --git a/Teams/meeting-speaker-coach.md b/Teams/meeting-speaker-coach.md index a206df680f..31b041c64b 100644 --- a/Teams/meeting-speaker-coach.md +++ b/Teams/meeting-speaker-coach.md @@ -25,12 +25,14 @@ description: IT admins - Learn to turn speaker coach on or off for Teams meeting # Manage Speaker Coach for Microsoft Teams meetings and events -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls ## Overview Speaker Coach in Teams meetings and events processes the user's audio while they present, as well as the audio of all unmuted participants, providing private real-time feedback and suggestions for improvement. For town halls, Speaker Coach only applies to organizers, co-organizers, and presenters. The user who turns on Speaker Coach receives a summary report of the feedback after the meeting or event, which only they can view, but you don't have access to this data. As an admin, you can manage whether users in your organization can use Speaker Coach during meetings and events. +To learn more about how your users use Speaker Coach, see [Speaker Coach in Microsoft Teams meetings](https://support.microsoft.com/office/preview-speaker-coach-in-microsoft-teams-meetings-30f50d15-5f62-4e09-b3bf-cadeb806386a). + ## Manage Speaker Coach using PowerShell You must use PowerShell to manage Speaker Coach through the **`-AllowMeetingCoach`** parameter within the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet. Or, you can create a new Teams meeting policy by using the [New-CsTeamsMeetingPolicy](/powershell/module/teams/new-csteamsmeetingpolicy) cmdlet and assign it to users. diff --git a/Teams/meeting-surveys-anonymous-participants.md b/Teams/meeting-surveys-anonymous-participants.md index 252543e864..a0378cd682 100644 --- a/Teams/meeting-surveys-anonymous-participants.md +++ b/Teams/meeting-surveys-anonymous-participants.md @@ -24,7 +24,7 @@ appliesto: # Manage feedback surveys for anonymous participants in Teams meetings -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ## Overview diff --git a/Teams/meeting-templates-sensitivity-labels-policies.md b/Teams/meeting-templates-sensitivity-labels-policies.md index 415bfa660c..e09f9146b9 100644 --- a/Teams/meeting-templates-sensitivity-labels-policies.md +++ b/Teams/meeting-templates-sensitivity-labels-policies.md @@ -50,6 +50,7 @@ The following table shows a list of Teams features that may be useful for managi |People dialing in can bypass the lobby|Sets the default setting for new meetings.|If the label is controlling who can bypass the lobby, this setting is enforced **On** or **Off**, otherwise it's uncontrolled.|If not controlled by a sensitivity label, can be set to **On** or **Off**. Setting can be enforced or meeting organizer can be allowed to change.|If not enforced by a sensitivity label or template, meeting owner can set to **On** or **Off**.| |Prevent copying chat content to clipboard*|Copy prevention can be disabled (but not enforced) by admin policy. Admin policy is overridden by sensitivity label if used.|Can prevent the meeting chat from being copied or forwarded. |If enabled in admin policy and not controlled by a sensitivity label, can be set to **On** or **Off**. Setting can be enforced or meeting organizer can be allowed to change.|Meeting organizer can turn **On** or **Off** unless setting is disabled by admin policy or enforced by sensitivity label or template.| |Record automatically|Meeting recording can be disabled completely using a meeting policy, but there's no admin policy for *Record automatically*.|Can enforce or prevent automatic meeting recording or be left uncontrolled. Can enforce automatic recording even if admin policy for recording is **Off**.|If meeting recording is allowed by admin policy and automatic recording isn't controlled by a sensitivity label, can be set to **On** or **Off** and can enforce the setting or allow the meeting organizer to change it.|Meeting organizer can turn **On** or **Off** unless the setting is enforced **On** or **Off** by a meeting template or sensitivity label or admin policy prevents recording.| +|Require a verification check from|Control whether anonymous users must complete a verification check to join meetings and webinars in your org.|Can require anonymous users to complete a verification check to join meetings and webinars.|If enabled in admin policy and not controlled by a sensitivity label, can be set to **On** or **Off**.|No setting.| |Who can bypass the lobby|Sets the default setting for new meetings.|Can enforce a particular option for who can bypass the lobby, or can be left uncontrolled.|If not controlled by a sensitivity label, selects a setting for who can bypass the lobby. Setting can be enforced or meeting organizer can be allowed to change.|Meeting organizer can choose who can bypass the lobby unless the setting is enforced by a label or template.| |Who can present|Sets the default setting for new meetings. Available values are **Everyone**, **People in my org and guests**, and **Only organizers and co-organizers**.|Can enforce settings of **Everyone**, **People in my org and guests**, **Let meeting organizer select specific people**, or **Only organizers and co-organizers**, or can be left uncontrolled.|No setting|Meeting organizer can select who can present unless enforced by a sensitivity label.| |Who can record|Meeting recording can be disabled completely using a meeting policy, but there's no admin policy for *Who can record*.|Can enforce settings of **Organizers and co-organizers** or **Organizers and presenters**, or can be left uncontrolled.|If not controlled by a sensitivity label, selects a setting of **Organizers and co-organizers** or **Organizers, co-organizers, and presenters**. Setting can be enforced or meeting organizer can be allowed to change.|Meeting organizer can choose who can record—**Organizers and co-organizers** or **Organizers, co-organizers, and presenters**—unless the setting is enforced by a label or template.| diff --git a/Teams/meeting-themes.md b/Teams/meeting-themes.md index 6450025798..37bf71fc33 100644 --- a/Teams/meeting-themes.md +++ b/Teams/meeting-themes.md @@ -25,7 +25,7 @@ description: Using approved corporate branding assets like images and logos to c # Create and manage meeting themes for Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/meeting-transcription-captions.md b/Teams/meeting-transcription-captions.md index 034d0c85cb..b2740499b0 100644 --- a/Teams/meeting-transcription-captions.md +++ b/Teams/meeting-transcription-captions.md @@ -26,7 +26,10 @@ appliesto: [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls + +> [!NOTE] +> When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off. To learn more about Copilot, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). In Microsoft Teams meetings and events, there's an option for recordings to have automatic transcription. Transcription allows users to play back meeting recordings with closed captions and review important discussion items in the transcript. Transcription and captions help create inclusive content for viewers. diff --git a/Teams/meeting-webinar-town-hall-feature-comparison.md b/Teams/meeting-webinar-town-hall-feature-comparison.md index aaed64bb62..c916fa900b 100644 --- a/Teams/meeting-webinar-town-hall-feature-comparison.md +++ b/Teams/meeting-webinar-town-hall-feature-comparison.md @@ -1,7 +1,7 @@ --- title: Meetings, webinars, and town halls feature comparison -ms.reviewer: -ms.date: 11/13/2023 +ms.reviewer: bryanyce +ms.date: 11/5/2024 ms.topic: article ms.author: wlibebe author: wlibebe @@ -28,60 +28,78 @@ description: Learn which features are available in Teams meetings, webinars, and # Meetings, webinars, and town halls feature comparison -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls The following table shows which features are available in meetings, webinars, and town halls. |Feature|Meetings|Webinars|Town halls| |:------|:-------|:-------|:---------| -|[Announce when callers join or leave](turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md)|✔️|✔️|✔️| -|[Anonymous attendees](anonymous-users-in-meetings.md)|✔️|✔️|✔️| -|[Attendance report](/microsoftteams/teams-analytics-and-reports/meeting-attendance-report)|✔️|✔️|✔️| -|[Attendee mic and camera](meeting-policies-audio-and-video.md)|✔️|✔️|✖️| -|[Breakout rooms](https://support.microsoft.com/office/use-breakout-rooms-in-microsoft-teams-meetings-7de1f48a-da07-466c-a5ab-4ebace28e461)|✔️|✖️2|✖️| -|[CART Captions](https://support.microsoft.com/office/use-cart-captions-in-a-microsoft-teams-meeting-human-generated-captions-2dd889e8-32a8-4582-98b8-6c96cf14eb47)|✔️|✔️|✖️| -|[Channel meeting scheduling](https://support.microsoft.com/office/schedule-a-meeting-in-microsoft-teams-943507a9-8583-4c58-b5d2-8ec8265e04e5)|✔️|✖️|✖️| -|[Choose co-organizers](https://support.microsoft.com/office/roles-in-microsoft-teams-meetings-c16fa7d0-1666-4dde-8686-0a0bfe16e019)|✔️|✔️|✔️| -|[Content sharing](meeting-policies-content-sharing.md)|✔️|✔️|✔️| +|[Announce when callers join or leave](turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.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)| +|[Anonymous participants](anonymous-users-in-meetings.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)| +|[Attendance and engagement reports](/microsoftteams/teams-analytics-and-reports/meeting-attendance-report)|![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)| +|[Attendee mic and camera](meeting-policies-audio-and-video.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 x for no](/office/media/icons/cancel-teams.png)| +|[Breakout rooms](https://support.microsoft.com/office/use-breakout-rooms-in-microsoft-teams-meetings-7de1f48a-da07-466c-a5ab-4ebace28e461)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)1|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[CART Captions](https://support.microsoft.com/office/use-cart-captions-in-a-microsoft-teams-meeting-human-generated-captions-2dd889e8-32a8-4582-98b8-6c96cf14eb47)|![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 x for no](/office/media/icons/cancel-teams.png)| +|[Channel meeting scheduling](https://support.microsoft.com/office/schedule-a-meeting-in-microsoft-teams-943507a9-8583-4c58-b5d2-8ec8265e04e5)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Choose co-organizers](https://support.microsoft.com/office/roles-in-microsoft-teams-meetings-c16fa7d0-1666-4dde-8686-0a0bfe16e019)|![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)| +|[Compliance recording](teams-recording-policy.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)| +|[Content sharing](meeting-policies-content-sharing.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)| +|[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| -|[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|✔️|✖️|✔️| -|[End-to-end encryption](teams-end-to-end-encryption.md)|Premium|✖️|✖️| -|[External participants can give or request control](meeting-who-present-request-control.md)|✔️|✔️|✖️| -|[Green room](https://support.microsoft.com/office/green-room-for-teams-meetings-5b744652-789f-42da-ad56-78a68e8460d5)|✔️|✔️|✔️| -|[Hide attendee names](hide-attendee-names.md)|Premium|Premium|✖️| -|[Interactive participants](view-only-meeting-experience.md)|1,000|1,000|✖️| -|[Language interpretation](https://support.microsoft.com/office/use-language-interpretation-in-microsoft-teams-meetings-b9fdde0f-1896-48ba-8540-efc99f5f4b2e)|✔️|✔️|✖️| -|[Limit presenter role permissions](presenter-role-reduction.md)|✔️|✔️|✔️| -|[Live captions](meeting-transcription-captions.md)|✔️|✔️|✔️| -|[Live transcriptions](https://support.microsoft.com/office/view-live-transcription-in-microsoft-teams-meetings-dc1a8f23-2e20-4684-885e-2152e06a4a8b)|✔️|✔️|✔️| -|[Lobby](who-can-bypass-meeting-lobby.md)|✔️|✔️|✖️| -|[Manage what attendees see](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)|Premium|Premium|✔️| -|[Meeting chat](manage-meeting-chat.md)|✔️|✔️|For organizers, co-organizers, and presenters only.| -|[Meeting themes](meeting-themes.md)|Premium|✖️|✖️| -|[Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md)|✔️|✔️|For organizers, co-organizers, and presenters only.| -|[Organizers and co-organizers can use video effects](https://support.microsoft.com/office/apply-video-filters-in-microsoft-teams-meetings-c04a1326-7f63-4170-a4f7-0778520af465)|✔️|✔️|✔️| -|[Outlook add-in](https://support.microsoft.com/office/schedule-a-microsoft-teams-meeting-from-outlook-883cc15c-580f-441a-92ea-0992c00a9b0f)|✔️|✔️|✔️| -|[Participants can give or request control](meeting-who-present-request-control.md)|✔️|✔️|✖️| -|[PowerPoint Live](https://support.microsoft.com/office/present-from-powerpoint-live-in-microsoft-teams-28b20e74-7165-499c-9bd4-0ad975d448ad)|✔️|✔️|✖️| -|[Q&A](manage-qna-for-teams.md)|✔️|✔️|✔️| -|[Reactions](manage-reactions-meetings.md)|✔️|✔️|✖️| -|[Recording](meeting-recording.md)|✔️|✔️|✔️| -|[Record automatically](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24#bkmk_whocanstartorstoparecording)|✔️|✔️|✔️| -|[Recordings automatically expire](meeting-recording.md)|✔️|✔️|✔️| -|[Registration](set-up-webinars.md)| ✖️|✔️|✖️| -|[RTMP-in](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f)| Premium|Premium|✔️| -|[Shared notes](meeting-policies-content-sharing.md)|✔️|✔️|Only for organizers and co-organizers.| -|[Speaker coach](meeting-speaker-coach.md)|✔️|✔️|For organizers and co-organizers.| -|[Town hall attendee reactions](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_townhall_reactions)|✖️|✖️|Premium| -|[View-only experience](view-only-meeting-experience.md)|10,0001|✖️|✖️| -|[VOD](manage-vod-publishing.md)|✖️|✔️|✔️| -|[Voice isolation](voice-isolation.md)|✔️|✔️|✔️| -|[Watermarks](watermark-meeting-content-video.md)|Premium|✖️|✖️| -|[Whiteboard](meeting-policies-content-sharing.md)|✔️|✔️|✖️| +|[Decorate my background](https://adoption.microsoft.com/microsoft-teams-premium/decorate-your-background/)|Premium|Premium|Premium| +|[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)| +|[End-to-end encryption](teams-end-to-end-encryption.md)|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[External participants can give or request control](meeting-who-present-request-control.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 x for no](/office/media/icons/cancel-teams.png)| +|[Event chat](town-hall-chat.md)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|Premium| +|[Green room](https://support.microsoft.com/office/green-room-for-teams-meetings-5b744652-789f-42da-ad56-78a68e8460d5)|![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)| +|[Hide attendee names](hide-attendee-names.md)|Premium|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Interactive participants](view-only-meeting-experience.md)|1,000|1,000|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Join verification check](join-verification-check.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 x for no](/office/media/icons/cancel-teams.png)| +|[Language interpretation](https://support.microsoft.com/office/use-language-interpretation-in-microsoft-teams-meetings-b9fdde0f-1896-48ba-8540-efc99f5f4b2e)|![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 x for no](/office/media/icons/cancel-teams.png)| +|[Limit presenter role permissions](presenter-role-reduction.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)| +|[Live captions](meeting-transcription-captions.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)| +|[Live stream meetings with RTMP-In](stream-teams-meetings.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 x for no](/office/media/icons/cancel-teams.png)| +|[Live transcriptions](https://support.microsoft.com/office/view-live-transcription-in-microsoft-teams-meetings-dc1a8f23-2e20-4684-885e-2152e06a4a8b)|![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)| +|[Lobby](who-can-bypass-meeting-lobby.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 x for no](/office/media/icons/cancel-teams.png)| +|[Manage what attendees see](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)|Premium|Premium|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|[Meeting chat](manage-meeting-chat.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)|For organizers, co-organizers, and presenters only.| +|[Meeting themes](meeting-themes.md)|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.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)|For organizers, co-organizers, and presenters only.| +|[Organizers and co-organizers can use video effects](meeting-policies-audio-and-video.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)| +|[Outlook add-in](https://support.microsoft.com/office/schedule-a-microsoft-teams-meeting-from-outlook-883cc15c-580f-441a-92ea-0992c00a9b0f)|![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)| +|[Participants can give or request control](meeting-who-present-request-control.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 x for no](/office/media/icons/cancel-teams.png)| +|[PowerPoint Live](https://support.microsoft.com/office/present-from-powerpoint-live-in-microsoft-teams-28b20e74-7165-499c-9bd4-0ad975d448ad)|![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 x for no](/office/media/icons/cancel-teams.png)| +|[Presenters](meeting-who-present-request-control.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)| +|[Prevent copying or forwarding of chat](manage-chat-sensitive-meetings.md#prevent-copying-or-forwarding-of-chat)|![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)| +|[Prevent users from joining external meetings](external-meeting-join.md)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Prevent users from sharing content in external meetings](block-external-content-share.md)|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Q&A](manage-qna-for-teams.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)| +|[Quality of Service (QoS)](meetings-real-time-media-traffic.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)| +|[Reactions](manage-reactions-meetings.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 x for no](/office/media/icons/cancel-teams.png)| +|[Record automatically](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24#bkmk_whocanstartorstoparecording)|![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)| +|[Recordings automatically expire](meeting-recording.md#expiration-policy)|![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)| +|[Recording storage and permissions](tmr-meeting-recording-change.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)| +|[Registration](set-up-webinars.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)| +|[Registration form for webinars](manage-registration-form-webinars.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)| +|[Restrict who can record](manage-meeting-recording-options.md#manage-who-can-record-and-transcribe-meetings)|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[RTMP-In](https://support.microsoft.com/office/use-rtmp-in-in-a-teams-meeting-789d6090-8511-4e2e-add6-52a9f551be7f)| Premium|Premium|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|[Sensitivity labels](/purview/sensitivity-labels-meetings)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Shared notes](meeting-policies-content-sharing.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)|Only for organizers and co-organizers.| +|[Speaker coach](meeting-speaker-coach.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)|For organizers and co-organizers.| +|[Streaming encoders](teams-encoder-setup.md)|![Image of a checkmark for yes](/office/media/icons/success-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)| +|[Town hall attendee reactions](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c#bkmk_townhall_reactions)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|Premium| +|[Town hall insights](https://support.microsoft.com/office/town-hall-insights-in-microsoft-teams-def99575-61bf-4ea2-ad0e-c6e75dce7741)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)|Premium| +|[View-only attendees](view-only-meeting-experience.md)|10,0002|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[VOD](manage-vod-publishing.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 checkmark for yes](/office/media/icons/success-teams.png)| +|[Voice isolation](voice-isolation.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)| +|[Watermarks](watermark-meeting-content-video.md)|Premium|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|[Whiteboard](meeting-policies-content-sharing.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 x for no](/office/media/icons/cancel-teams.png)| -1 The usual 10,000 is increased to 20,000 through June 30, 2024.
+1 Your users can use breakout rooms if a webinar has fewer than 300 attendees. However, if the number of attendees increases to above 300, breakout rooms aren't supported.
-2 Breakout rooms can be used if a webinar has fewer than 300 participants. However, if the number of participants increases to above 300, breakout rooms aren't supported. +2 The usual maximum is increased to 20,000 through June 30, 2024. ## Related topics diff --git a/Teams/meeting-who-present-request-control.md b/Teams/meeting-who-present-request-control.md index c812e56c4e..e94313c52e 100644 --- a/Teams/meeting-who-present-request-control.md +++ b/Teams/meeting-who-present-request-control.md @@ -25,7 +25,7 @@ description: Learn to manage who can present and take control in Teams meetings. # Manage who can present and request control in Teams meetings and webinars -**APPLIES TO:** ✔️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls As an admin, you can manage who can present in meetings and webinars and whether participants and external participants can request control of the presentation. diff --git a/Teams/meetings-real-time-media-traffic.md b/Teams/meetings-real-time-media-traffic.md index 221e40e22c..6f26db122c 100644 --- a/Teams/meetings-real-time-media-traffic.md +++ b/Teams/meetings-real-time-media-traffic.md @@ -1,7 +1,7 @@ --- title: Configure QoS settings in the Teams admin center -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: siunies ms.date: 04/18/2024 @@ -57,7 +57,7 @@ Note: If you enable QoS or change settings in the Microsoft Teams admin center f - If you've enabled Quality of Service, you must manage your port settings. - To specify port ranges, next to **Select a port range for each type of real-time media traffic**, select **Specify port ranges**, and then enter the starting and ending ports for audio, video, and screen sharing. + To specify port ranges, next to **Select a port range for each type of real-time media traffic**, select **Specify port ranges**, and then enter the starting and ending ports for audio, video, and screen sharing. The port ranges for calling and meeting signaling are not customizable currently. Selecting a port range that is too narrow will lead to dropped calls and poor call quality. For more information about choosing port ranges, see [Choose initial port ranges](qos-in-teams.md#step-3-choose-initial-port-ranges-for-each-media-type). @@ -66,4 +66,4 @@ Note: If you enable QoS or change settings in the Microsoft Teams admin center f > [!IMPORTANT] > Do not select **Automatically use any available ports** unless you aren't implementing QoS. If you select this option, available ports between 1024 and 65535 are used. -After using QoS for a while, you can use use [Call Quality Dashboard](cqd-what-is-call-quality-dashboard.md) to determine if changes are required to your QoS configuration. +After using QoS for a while, you can use [Call Quality Dashboard](cqd-what-is-call-quality-dashboard.md) to determine if changes are required to your QoS configuration. diff --git a/Teams/meetings-rtmp-in.md b/Teams/meetings-rtmp-in.md index b8d989b5b3..1ced7ae3c4 100644 --- a/Teams/meetings-rtmp-in.md +++ b/Teams/meetings-rtmp-in.md @@ -24,7 +24,7 @@ description: Learn to set up RTMP-In for Teams meetings for admins. # Manage RTMP-In for Teams meetings, webinars, and town halls -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/microsoft-teams-online-call-flows.md b/Teams/microsoft-teams-online-call-flows.md index ba13bf6d2f..8952268458 100644 --- a/Teams/microsoft-teams-online-call-flows.md +++ b/Teams/microsoft-teams-online-call-flows.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams call flows -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.date: 06/08/2018 ms.topic: conceptual diff --git a/Teams/monitor-call-quality-qos.md b/Teams/monitor-call-quality-qos.md index e0792fee38..c76de7b2be 100644 --- a/Teams/monitor-call-quality-qos.md +++ b/Teams/monitor-call-quality-qos.md @@ -1,7 +1,7 @@ --- title: 'Monitor and improve call quality for Microsoft Teams' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.service: msteams diff --git a/Teams/more-about-calling-line-ID-and-calling-party-name.md b/Teams/more-about-calling-line-ID-and-calling-party-name.md index 8ca2326a2d..2cab07a568 100644 --- a/Teams/more-about-calling-line-ID-and-calling-party-name.md +++ b/Teams/more-about-calling-line-ID-and-calling-party-name.md @@ -1,7 +1,7 @@ --- title: "More about Calling Line ID and Calling Party Name" -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: roykuntz ms.date: 03/06/2024 diff --git a/Teams/msi-deployment.md b/Teams/msi-deployment.md index 924fd6609f..88629db2cc 100644 --- a/Teams/msi-deployment.md +++ b/Teams/msi-deployment.md @@ -6,7 +6,7 @@ manager: jtremper ms.topic: article ms.service: msteams ms.reviewer: amitsri -ms.date: 08/03/2023 +ms.date: 10/30/2024 audience: admin description: Use Windows Installer (MSI) files to distribute the Teams client to multiple users and computers. ms.localizationpriority: medium @@ -24,6 +24,9 @@ appliesto: # Bulk install classic Teams using Windows Installer (MSI) +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + >[!Important] >This article is for classic Teams only. To bulk deploy to new Teams, see: [Bulk upgrade to the new Microsoft Teams client](new-teams-bulk-install-client.md) diff --git a/Teams/network-roaming-policy.md b/Teams/network-roaming-policy.md index fe7a3d7742..60d11e256f 100644 --- a/Teams/network-roaming-policy.md +++ b/Teams/network-roaming-policy.md @@ -1,7 +1,7 @@ --- title: Network roaming policy -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 06/28/2024 diff --git a/Teams/new-teams-bulk-install-client.md b/Teams/new-teams-bulk-install-client.md index 8895a76773..dfabb115b5 100644 --- a/Teams/new-teams-bulk-install-client.md +++ b/Teams/new-teams-bulk-install-client.md @@ -4,7 +4,7 @@ author: MicrosoftHeidi ms.author: heidip manager: jtremper ms.topic: article -ms.date: 11/30/2023 +ms.date: 06/19/2024 ms.service: msteams audience: admin ms.collection: diff --git a/Teams/new-teams-deploy-using-policies.md b/Teams/new-teams-deploy-using-policies.md index bbed1c8933..a192b2087c 100644 --- a/Teams/new-teams-deploy-using-policies.md +++ b/Teams/new-teams-deploy-using-policies.md @@ -25,8 +25,7 @@ ms.localizationpriority: high You can upgrade to the new Teams client to your organization by setting policies in either the Teams Admin Center or by using PowerShell. > [!TIP] ->As a companion to this article, we recommend using the [Microsoft Teams Setup Guide](https://go.microsoft.com/fwlink/?linkid=2270034) when signed in to the Microsoft 365 admin center. This guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup portal](https://go.microsoft.com/fwlink/?linkid=2270204). - +> As a companion to this article, see our [Teams setup guide](https://go.microsoft.com/fwlink/?linkid=2270204) to review best practices and learn to configure Teams features to meet your business needs. This comprehensive guide covers key areas like managing policies, external access, and tags. For a customized experience based on your environment, you can access the [Teams automated setup guide](https://go.microsoft.com/fwlink/?linkid=2270034) in the Microsoft 365 admin center.  ## Prerequisites |Requirement|Version| diff --git a/Teams/new-teams-vdi-requirements-deploy.md b/Teams/new-teams-vdi-requirements-deploy.md index 99c3a9c297..0e1637f712 100644 --- a/Teams/new-teams-vdi-requirements-deploy.md +++ b/Teams/new-teams-vdi-requirements-deploy.md @@ -47,6 +47,9 @@ In addition, virtual machines must meet the minimum requirements listed here: |Settings |Turn on the **Show Notification Banners** setting in System > Notifications > Microsoft Teams to receive Teams Notifications. | |Exclude antivirus and DLP|Add new Teams to antivirus and DLP applications so Teams can start correctly.
Learn more: [Exclude antivirus and DLP applications from blocking Teams](/microsoftteams/troubleshoot/teams-administration/include-exclude-teams-from-antivirus-dlp)| +> [!NOTE] +> Support for Microsoft Teams and Microsoft 365 Apps is defined by the [Modern Lifecycle Policy](/lifecycle/policies/modern), which requires customers maintain an up-to-date configuration to stay supported. End-of-support dates for Windows Server 2019 and Windows Server 2022 are October 2025 and October 2026 respectively. For further information, please check [this link](https://go.microsoft.com/fwlink/?linkid=2274805). + ## Virtualization provider requirements Currently, new Teams on VDI with audio/video (AV) optimization is certified with Azure Virtual Desktops, Windows 365, Citrix, and VMware. @@ -581,6 +584,7 @@ When users connect from an unsupported endpoint, the users are in fallback mode, `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\DisableFallback` `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Teams\DisableFallback` +- This registry key can only be processed by new Teams 24257.x.x.x or higher. - To disable fallback mode, set the value to 1. - To enable audio only, set the value to 2. - If the value isn't present or is set to 0 (zero), fallback mode is enabled. diff --git a/Teams/operator-connect-conferencing-plan.md b/Teams/operator-connect-conferencing-plan.md index d88d8742b3..eaf3a7f248 100644 --- a/Teams/operator-connect-conferencing-plan.md +++ b/Teams/operator-connect-conferencing-plan.md @@ -14,7 +14,7 @@ ms.collection: - m365initiative-meetings - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 f1.keywords: - NOCSH diff --git a/Teams/operator-connect-configure.md b/Teams/operator-connect-configure.md index 7d8eadc379..a7d51cb790 100644 --- a/Teams/operator-connect-configure.md +++ b/Teams/operator-connect-configure.md @@ -1,7 +1,7 @@ --- title: Configure Operator Connect -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 08/10/2023 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 f1.keywords: - NOCSH diff --git a/Teams/operator-connect-india-configure.md b/Teams/operator-connect-india-configure.md index c72732b5e1..bc7a4f541d 100644 --- a/Teams/operator-connect-india-configure.md +++ b/Teams/operator-connect-india-configure.md @@ -1,7 +1,7 @@ --- title: Configure Operator Connect for India -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 09/01/2023 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 f1.keywords: - NOCSH diff --git a/Teams/operator-connect-india-plan.md b/Teams/operator-connect-india-plan.md index 89fbbbd934..3fa6edff2f 100644 --- a/Teams/operator-connect-india-plan.md +++ b/Teams/operator-connect-india-plan.md @@ -1,7 +1,7 @@ --- title: Plan for Operator Connect for India -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 09/01/2023 ms.topic: article diff --git a/Teams/operator-connect-mobile-configure-numbers.md b/Teams/operator-connect-mobile-configure-numbers.md index 67c2139b89..3dab42ae1f 100644 --- a/Teams/operator-connect-mobile-configure-numbers.md +++ b/Teams/operator-connect-mobile-configure-numbers.md @@ -1,7 +1,7 @@ --- title: Manage phone numbers for Teams Phone Mobile -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 07/08/2024 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 description: Learn how to manage phone numbers for Teams Phone Mobile. diff --git a/Teams/operator-connect-mobile-configure.md b/Teams/operator-connect-mobile-configure.md index 1cbf57e38b..ecca05cc3c 100644 --- a/Teams/operator-connect-mobile-configure.md +++ b/Teams/operator-connect-mobile-configure.md @@ -1,7 +1,7 @@ --- title: Configure Teams Phone Mobile -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 07/08/2024 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 description: Learn how to configure Teams Phone Mobile. diff --git a/Teams/operator-connect-mobile-plan.md b/Teams/operator-connect-mobile-plan.md index 6d768ae259..62b28177ca 100644 --- a/Teams/operator-connect-mobile-plan.md +++ b/Teams/operator-connect-mobile-plan.md @@ -1,7 +1,7 @@ --- title: Plan for Teams Phone Mobile -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 07/08/2024 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 description: Learn more about Teams Phone Mobile, such as requirements and planning for deployment. diff --git a/Teams/operator-connect-plan.md b/Teams/operator-connect-plan.md index 8e8e169480..c70aac987a 100644 --- a/Teams/operator-connect-plan.md +++ b/Teams/operator-connect-plan.md @@ -1,7 +1,7 @@ --- title: Plan for Operator Connect -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 03/25/2024 ms.topic: article @@ -12,7 +12,7 @@ ms.collection: - m365initiative-voice - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis search.appverid: MET150 f1.keywords: - NOCSH diff --git a/Teams/outlook-add-in-authentication-policy-requirements.md b/Teams/outlook-add-in-authentication-policy-requirements.md index f9baf9f667..5ffb5570bc 100644 --- a/Teams/outlook-add-in-authentication-policy-requirements.md +++ b/Teams/outlook-add-in-authentication-policy-requirements.md @@ -6,8 +6,8 @@ manager: pamgreen audience: Admin ms.topic: article ms.service: msteams -ms.reviewer: -ms.date: 04/27/2023 +ms.reviewer: mfoland +ms.date: 10/31/2024 ms.localizationpriority: medium search.appverid: MET150 description: IT Admins - Learn about the requirements and policy settings for the Teams Meeting add-in in Outlook @@ -25,39 +25,77 @@ appliesto: # Admin - authentication requirements and functionality of the Teams Meeting add-in in Outlook -This article details authentication requirements and functionality of the Teams Meeting add-in in Outlook for your end users. It also shows how you can enable private meetings and adjust policy settings for users in Island Mode. If you are having issues with the add-in, see our [latest troubleshooting guidance](/MicrosoftTeams/troubleshoot/meetings/resolve-teams-meeting-add-in-issues). +The Teams Meeting add-in lets users schedule a Teams meeting from Outlook. This add-in is available for Outlook on Windows, Mac, web, and mobile. The add-in is for scheduled meetings with specific participants, not for meetings in a channel. Your users must schedule channel meetings within Teams. -The Teams Meeting add-in lets users schedule a Teams meeting from Outlook. The add-in is available for Outlook on Windows, Mac, web, and mobile. +This article details authentication requirements and functionality of the Teams Meeting add-in in Outlook for your users. Additionally, it provides guidance on enabling private meetings and managing policy settings for users in Island Mode. + +If you're having issues with the add-in, see our [Resolve issues that affect the Teams Meeting add-in for classic Outlook](/MicrosoftTeams/troubleshoot/meetings/resolve-teams-meeting-add-in-issues). + +## Prerequisites + +- [Webview2](/microsoft-edge/webview2/concepts/distribution) and .NET 4.8 installation is required to avoid a degraded experience with the Teams Meeting add-in. +- User permissions to execute the Regsvr32.exe file is a minimum requirement to install the Teams Meeting add-in on the computer. This prerequisite doesn't apply to new Teams. +- The Teams Meeting add-in requires an Exchange mailbox for the meeting organizer. Your users need east one Exchange mailbox set up in their Outlook profile and use it to schedule Teams meetings with the add-in. For Exchange requirements, see [How Exchange and Teams interact](exchange-teams-interact.md). + +> [!NOTE] +> The add-in doesn't work if an Authentication Proxy is in the network path of the user's PC and Teams Services. + +### Required meeting policies + +To deploy the add-in, you must turn on **Allow the Outlook Add-in** and **Allow scheduling for private meetings**. + +Use the following steps to turn on these settings: + +1. Open the Teams admin center. +2. Expand **Meetings** from the navigation pane. +3. Under **Meetings**, select **Meeting Policies**. +4. Either select an existing policy or create a new one. +5. Navigate to the **Meeting scheduling** section +6. Toggle **Allow the Outlook Add-in** and **Allow scheduling for private meetings** to **On**. +7. Select **Save** + +:::image type="content" source="media/meeting-schedule-small.png" alt-text="Screenshot of Teams meeting scheduling policies in the Teams admin center." lightbox="media/meeting-schedule-expand.png"::: + +The Teams client installs the correct add-in by determining if users need the 32-bit or 64-bit version. + +> [!NOTE] +> Users might need to restart Outlook after an installation or upgrade of Teams to get the latest add-in. ## Teams Meeting add-in in Outlook for Windows -The Teams Meeting add-in is automatically installed for users who have Microsoft Teams and either Office 2013, Office 2016, Office 2019 or Office 2021 installed on their Windows PC. Users will see the Teams Meeting add-in on the Outlook Calendar ribbon. +The Teams Meeting add-in is automatically installed for users who have Microsoft Teams and either Office 2013, Office 2016, Office 2019, or Office 2021 installed on their Windows PC. Your users see the Teams Meeting add-in on the Outlook Calendar ribbon. ![Screenshot of Teams Meeting add-in on Outlook ribbon.](media/Teams-add-in-for-Outlook.png) -> [!NOTE] -> +If you're using an Office Outlook installation from the Microsoft Store, the Teams Meeting add-in isn't supported. Users who need this add-in should install Click-to-Run version of Office. For details on installing theClick-to-Run version of Office, see [Office on Windows 10 in S mode](https://support.office.com/article/faq-office-on-windows-10-in-s-mode-717193b5-ff9f-4388-84c0-277ddf07fe3f). + +If your users don't see the Teams Meeting add-in, they should follow these steps: + +1. Close both Outlook and Teams. +2. Restart the Teams client. +3. Sign in to Teams. +4. Restart the Outlook client. + +They can also check **Add/Remove programs** for the Teams Meeting add-in; it shows up as "Microsoft Teams Meeting Add-in for Microsoft Office. + +> [!IMPORTANT] > -> - There is **no direct URL** that links to the Teams add-in. -> - There are additional considerations if your organization runs both Teams and Skype for Business. Under some circumstances, the Teams add-in is not available in Outlook. See [Upgrade from Skype for Business to Teams](upgrade-to-Teams-on-prem-tools.md) for details. -> - User permissions to execute the Regsvr32.exe file is a minimum requirement for the Teams Meeting add-in to be installed on the computer. -> - If users do not see the Teams Meeting add-in, instruct them to close Outlook and Teams, then restart the Teams client first, then sign in to Teams, and then restart the Outlook client, in that specific order. -> - If you are using an Office Outlook installation from the Microsoft Store, the Teams Meeting add-in isn't supported. Users who require this add-in are advised to install Click-to-Run version of Office, as outlined in [Office on Windows 10 in S mode](https://support.office.com/article/faq-office-on-windows-10-in-s-mode-717193b5-ff9f-4388-84c0-277ddf07fe3f) article. -> - [Webview2](/microsoft-edge/webview2/concepts/distribution) and .Net 4.8 installation is required to avoid a degraded experience with the Teams Meeting add-in. +> - There's **no direct URL** that links to the Teams add-in. +> - If your organization runs both Teams and Skype for Business, the Teams add-in might not be available in Outlook. For details, see [Upgrade from Skype for Business to Teams](upgrade-to-Teams-on-prem-tools.md). ## Teams Meeting add-in in Outlook for Mac -The Teams Meeting button in Outlook for Mac will appear in the Outlook for Mac ribbon if Outlook is running production build 16.24.414.0 and later and is activated with a Microsoft 365 or Office 365 client subscription. +The Teams Meeting button in Outlook for Mac appears in the Outlook for Mac ribbon if Outlook is running production build 16.24.414.0 and later and is activated with a Microsoft 365 or Office 365 client subscription. -The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks **Send**. +The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user selects **Send**. ## Teams Meeting add-in in Outlook Web App -The Teams Meetings button in Outlook Web App will appear as part of new event creation if the user is on an early version of the new Outlook on the web. See the [Outlook Blog](https://techcommunity.microsoft.com/t5/Outlook-Blog/Designed-to-be-fast-The-Outlook-on-the-web-user-experience-gets/ba-p/234909?utm_source=t.co&utm_medium=referral) to learn about how users can try the early version of the new Outlook on the web. +The Teams Meetings button in Outlook Web App appears as part of new event creation if the user is using Outlook on the web. To learn more, see [Outlook Blog](https://techcommunity.microsoft.com/t5/Outlook-Blog/Designed-to-be-fast-The-Outlook-on-the-web-user-experience-gets/ba-p/234909?utm_source=t.co&utm_medium=referral) . ![Screenshot of Teams Meeting add-in in Outlook Web App.](media/teams-meeting-add-in-web.png) -The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks **Send**. +The meeting coordinates (the Teams join link and dial-in numbers) are added to the meeting invite after the user selects **Send**. ## Teams Meeting add-in in Outlook mobile (iOS and Android) @@ -65,44 +103,47 @@ The Teams Meeting button shows up in latest builds of the Outlook iOS and Androi ![Screenshot of Teams Meeting add-in in Outlook mobile.](media/teams-meeting-add-in-mobile.png) -The meeting coordinates (the Teams join link and dial-in numbers) will be added to the meeting invite after the user clicks **Send**. +The meeting coordinates (the Teams join link and dial-in numbers) are added to the meeting invite after the user selects **Send**. ## Teams Meeting add-in and FindTime for Outlook -FindTime is an add-in for Outlook that helps users reach consensus on a meeting time across companies. Once the meeting invitees have provided their preferred times, FindTime sends out the meeting invite on the user's behalf. If the **Online meeting** option is selected in FindTime, FindTime will schedule a Skype for Business or Microsoft Teams meeting. (FindTime will use whichever has been set by your organization as the default online meeting channel.) +FindTime is an Outlook add-in that creates a meeting poll, allowing participants to select available times so organizers can choose a suitable meeting time. Once the meeting invitees provide their preferred times, FindTime sends out the meeting invite for the organizer. If the **Online meeting** option is selected in FindTime, FindTime schedules a Skype for Business or Microsoft Teams meeting. FindTime uses the default online meeting channel that your organization sets. > [!NOTE] -> If you saved a Skype for Business setting in your [Findtime dashboard](https://support.microsoft.com/office/findtime-organizer-dashboard-cfe12f76-d6f3-4af3-88a4-95f63b952721), FindTime will use that instead of Microsoft Teams. If you want to use Microsoft Teams, delete the Skype for Business setting in your dashboard. +> If you saved a Skype for Business setting in your [FindTime dashboard](https://support.microsoft.com/office/findtime-organizer-dashboard-cfe12f76-d6f3-4af3-88a4-95f63b952721), FindTime uses that instead of Microsoft Teams. If you want to use Microsoft Teams, delete the Skype for Business setting in your dashboard. For more information, see [Schedule meetings with FindTime](https://support.office.com/article/scheduling-meetings-with-findtime-4dc806ed-fde3-4ea7-8c5e-b5d1fddab4a6). ## Authentication requirements -The Teams Meeting add-in requires users to sign in to Teams using Modern Authentication. If users do not use this method to sign in, they'll still be able to use the Teams client, but will be unable to schedule [Teams online meetings](https://www.microsoft.com/microsoft-teams/online-meetings) using the Outlook add-in. You can fix this by doing one of the following: - -- If Modern Authentication is not configured for your organization, you should configure Modern Authentication. -- If Modern Authentication is configured, but they canceled out on the dialog box, you should instruct users to sign in again using multi-factor authentication. +The Teams Meeting add-in requires users to sign in to Teams using Modern Authentication. If users don't use this method to sign in, they can still use the Teams client, but they can't schedule [Teams online meetings](https://www.microsoft.com/microsoft-teams/online-meetings) using the Outlook add-in. If your users run into this issue, you can do one of the following options: -To learn more about how to configure authentication, see [Identity models and authentication in Microsoft Teams](identify-models-authentication.md). +- If Modern Authentication isn't configured for your organization, you should configure Modern Authentication. +- If Modern Authentication is configured, but they canceled out on the dialog box, you should instruct your users to sign in again using Multifactor Authentication. -## Enable private meetings +These requirements are only valid for Outlook Classic with Teams Meeting Add-in. -**Allow scheduling for private meetings** must be enabled in the Microsoft Teams admin center for the add-in to get deployed. In the admin center, go to **Meetings** > **Meeting Policies**, and in the **General** section, toggle **Allow scheduling private meetings** to On.) +To learn more about how to configure authentication, see [Identity models and authentication in Microsoft Teams](identify-models-authentication.md). -![Screenshot of the settings in the Microsoft Teams admin center.](media/teams-add-in-for-outlook-image1.png) +## Allow private meetings -The Teams client installs the correct add-in by determining if users need the 32-bit or 64-bit version. +To allow private meetings, following these steps: -> [!NOTE] -> Users might need to restart Outlook after an installation or upgrade of Teams to get the latest add-in. +1. Open the Teams admin center. +2. Expand **Meetings** from the navigation pane. +3. Under **Meetings**, select **Meeting Policies**. +4. Either select an existing policy or create a new one. +5. Navigate to the **Meeting scheduling** section +6. Toggle **Allow scheduling for private meetings** to **On**. +7. Select **Save** ## Teams upgrade policy and the Teams Meeting add-in for Outlook -Customers can [choose their upgrade journey from Skype for Business to Teams](upgrade-and-coexistence-of-skypeforbusiness-and-teams.md). Tenant admins can use the Teams co-existence mode to define this journey for their users. Tenant admins have the option to enable users to use Teams alongside Skype for Business (Islands mode). +As an admin, you can allow your users to use Teams alongside Skype for Business (Islands mode). When your users who are in Island mode schedule a meeting in Outlook, they can usually choose whether to schedule a Skype for Business or a Teams meeting. In Outlook on the web, Outlook Windows, and Outlook Mac, by default, users see both Skype for Business and Teams add-ins when in Islands mode. -When users who are in Island mode schedule a meeting in Outlook, they typically expect to be able to choose whether to schedule a Skype for Business or a Teams meeting. In Outlook on the web, Outlook Windows, and Outlook Mac, users see both Skype for Business and Teams add-ins when in Islands mode by default. You can configure a Teams meeting policy setting to control whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins. +You can use a Teams meeting policy setting to control whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins. -Due to certain limitations in the initial release, Outlook mobile can only support creating Skype for Business **or** Teams meetings. See the following table for details. +Outlook mobile can only support creating Skype for Business **or** Teams meetings. See the following table for details. | Coexistence mode in the Teams admin center | Default meetings provider in Outlook mobile | | --------------------------------------|---------------------------------------------| @@ -112,25 +153,19 @@ Due to certain limitations in the initial release, Outlook mobile can only suppo | Skype for Business with Teams collaboration and meetings | Teams | | Teams only | Teams | -### Set whether users in Islands mode can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins - -As an admin, you can configure a Teams meeting policy setting to control which Outlook meeting add-in is used for *users who are in Islands mode*. You can specify whether users can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins to schedule meetings in Outlook. +To learn more, see [Choose your upgrade journey from Skype for Business to Teams](upgrade-and-coexistence-of-skypeforbusiness-and-teams.md). -You can only apply this policy to users who are in Islands mode and have the **AllowOutlookAddIn** parameter set to **True** in their Teams meeting policy. For steps on how to set this policy, see [Meeting policy settings - General](meeting-policies-in-teams-general.md#meeting-provider-for-islands-mode). +### Manage Outlook meeting add-in availability for users on Islands mode -## Other considerations +As an admin, you can configure a Teams meeting policy setting to control which Outlook meeting add-in is used for *users who are in Islands mode*. You can specify whether users can only use the Teams Meeting add-in or both the Teams Meeting and Skype for Business Meeting add-ins to schedule meetings in Outlook. You can only apply this policy to users who are in Islands mode and have the **AllowOutlookAddIn** parameter set to **True** in their Teams meeting policy. For steps on how to set this policy, see [Meeting policy settings - General](meeting-policies-in-teams-general.md#meeting-provider-for-islands-mode). -The Teams Meeting add-in is still building functionality, so be aware of the following: +Determines the Outlook meeting add-in availability to users on Islands mode. With the default value of TeamsAndSfb, users see both the Skype for Business and Teams add-ins. If you set this value to Teams, the Skype for Business add-in is removed and only the Teams add-in is shown. -- The Teams Meeting add-in requires an Exchange mailbox for the primary user scheduling the meeting. Ensure that you have at least one Exchange mailbox configured in your Outlook profile and use it to schedule Teams meetings with the add-in. For Exchange requirements, see [How Exchange and Teams interact](./exchange-teams-interact.md). -- The add-in is for scheduled meetings with specific participants, not for meetings in a channel. Channel meetings must be scheduled from within Teams. -- The add-in will not work if an Authentication Proxy is in the network path of the user's PC and Teams Services. -- Users can't schedule live events from within Outlook. Go to Teams to schedule live events. For more information, see [What are Microsoft Teams live events?](teams-live-events/what-are-teams-live-events.md). +You can use the **Preferred app for users to join Skype for Business meetings** to control the Outlook meeting add-in availability for users on Islands mode. To learn more, see [Configure the Skype Meetings App to work with Teams](configure-skype-meetings-app-to-work-with-teams.md). For details on managing this setting through PowerShell, see [Teams settings and policies reference](settings-policies-reference.md#audio--video). Learn more about [meetings and calling in Microsoft Teams](https://support.office.com/article/Meetings-and-calls-d92432d5-dd0f-4d17-8f69-06096b6b48a8). ## Related topics - [Teams Troubleshooting](/MicrosoftTeams/troubleshoot/teams) - - [Schedule a Teams meeting from Outlook](https://support.microsoft.com/office/schedule-a-teams-meeting-from-outlook-883cc15c-580f-441a-92ea-0992c00a9b0f) diff --git a/Teams/overview-meetings-webinars-town-halls.md b/Teams/overview-meetings-webinars-town-halls.md index 7e9931da2f..1f16249fc9 100644 --- a/Teams/overview-meetings-webinars-town-halls.md +++ b/Teams/overview-meetings-webinars-town-halls.md @@ -28,7 +28,7 @@ description: A guide for administrators to roll out and configure meetings, webi # Overview of meetings, webinars, and town halls -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls There are multiple ways to meet in Microsoft Teams: @@ -44,21 +44,21 @@ The following table shows the main features that are different between meetings, |Feature|Meetings|Webinars|Town halls| |:------|:-------|:-------|:---------| -|Lobby|✔️|✔️|✖️| -|Attendee mic and camera|✔️|✔️|✖️| -|End-to-end encryption|Premium|✖️|✖️| -|Watermarks|Premium|✖️|✖️| -|Theme|Premium|✔️|✔️| -|Registration|✖️|✔️|✖️| -|Breakout rooms|✔️|✖️2|✖️| -|Content sharing and interaction|✔️|✔️|Q&A only| -|Interactive participants|1,000 (Enterprise plans)
300 (Business plans)|1,000|Town halls: 10,000
Premium town halls: 20,000| -|View-only participants|10,0001 (Enterprise plans only)|✖️|✖️| -|Maximum total participants|11,0001 (Enterprise plans only)|1,000|Town halls: 10,000
Premium town halls: 20,000| - -1The usual 10,000 is increased to 20,000 through June 30, 2024. The maximum total participants for meetings is the sum of the interactive participants plus streaming participants.
- -2 Breakout rooms can be used if a webinar has fewer than 300 participants. However, if the number of participants increases to above 300, breakout rooms aren't supported. +|Lobby|![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 x for no](/office/media/icons/cancel-teams.png)| +|Attendee mic and camera|![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 x for no](/office/media/icons/cancel-teams.png)| +|End-to-end encryption|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|Watermarks|Premium|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|Theme|Premium|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Registration|![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)| +|Breakout rooms|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)1|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|Content sharing and interaction|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|Q&A only| +|Interactive participants|1,000 (Enterprise plans)
300 (Business plans)
900 (View-only mode)|1,000|Town halls: 10,000
Premium town halls: 20,000| +|View-only participants|10,0002 (Enterprise plans only)|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|Maximum total participants|10,9002 (Enterprise plans only)|1,000|Town halls: 10,000
Premium town halls: 20,000| + +1 Breakout rooms can be used if a webinar has fewer than 300 participants. However, if the number of participants increases to above 300, breakout rooms aren't supported.
+ +2The usual maximum is increased to 20,000 through June 30, 2024. The maximum total participants for meetings is the sum of the interactive participants plus view-only participants. For more information on limits and specifications for Teams webinars, meetings, and town halls, see [Limits and specifications for Microsoft Teams.](limits-specifications-teams.md) @@ -74,7 +74,7 @@ For details, see: ## Meetings -Meetings are generally best for situations where participants need to interact with each other via voice, video, or chat and where multiple people may be presenting. Meetings in Teams include audio, video, and screen sharing for up to 1,000 people and a view-only streaming experience for participants over 1,000. Participants don't need to be a member of an organization (or have a Teams account) to join a Teams meeting. They can join directly from the calendar invitation via the Join meeting link or call in via audio if available. +Meetings are generally best for situations where participants need to interact with each other via voice, video, or chat and where multiple people may be presenting. Meetings in Teams include audio, video, and screen sharing for up to 1,000 people and a view-only experience for participants over 900. Participants don't need to be a member of an organization (or have a Teams account) to join a Teams meeting. They can join directly from the calendar invitation via the Join meeting link or call in via audio if available. In addition to regularly scheduled meetings, your users can create channel meetings. With channel meetings, everybody in a team can see there's a meeting, join the meeting, and use the meeting chat. @@ -119,6 +119,10 @@ To understand key differences between live events and town halls, see [Plan for For detailed information on how to plan for Teams town halls, see [Plan for Teams town halls](plan-town-halls.md). +## Teams Premium + +With a Teams Premium add-on license, you have access to enhanced administrative and telemetry support, as well as enhanced experiences, security, and protection for your users' meetings and events. To learn more, see [Microsoft Teams Premium - Overview for admins](enhanced-teams-experience.md). + ## Best practices for large meetings and events This section provides guidance for admins, along with tips that admins can share with their presenters and organizers. diff --git a/Teams/overview-of-app-certification.md b/Teams/overview-of-app-certification.md index 644132cdfb..d9b3ef317c 100644 --- a/Teams/overview-of-app-certification.md +++ b/Teams/overview-of-app-certification.md @@ -1,5 +1,5 @@ --- -title: Overview of app certification by Microsoft +title: Know about high quality Microsoft certified Teams apps description: Learn about the Microsoft 365 app compliance program for security, compliance, and privacy of third-party apps. ms.topic: article author: ashishguptaiitb @@ -8,7 +8,7 @@ manager: prkosh audience: admin ms.subservice: teams-apps ms.service: msteams -ms.date: 05/08/2024 +ms.date: 10/31/2024 ms.collection: - M365-collaboration f1.keywords: @@ -37,7 +37,7 @@ Before an app developer can submit their app to Microsoft, the developer is requ ## Publisher attestation -Publisher attestation is the next tier in the app compliance program. Publisher attested apps provide confidence to admins about security and compliance measures of an app. It also helps reduce the time to review this information for an app. The attestation will reflect an app's security, data handling, and compliance practices against more than 80 risk factors identified by [Microsoft Defender for Cloud Apps](/defender-cloud-apps/). Publisher attestation process can start before Publisher verification is complete. +Publisher attestation is the next tier in the app compliance program. Publisher attested apps provide confidence to admins about security and compliance measures of an app. It also helps reduce the time to review this information for an app. The attestation reflects an app's security, data handling, and compliance practices against more than 80 risk factors identified by [Microsoft Defender for Cloud Apps](/defender-cloud-apps/). Publisher attestation process can start before Publisher verification is complete. App developers are asked to complete a self-assessment that includes questions frequently asked by customers and IT admins to evaluate the security and compliance of an app. Microsoft then publishes this information for easier and more timely evaluation. To know more, see [Attestation guide](/microsoft-365-app-certification/docs/enterprise-app-attestation-guide). @@ -63,20 +63,22 @@ The attestation details page for an attested or certified app lists the followin App certification is achieved through: -* A qualified analyst's review. * Approval of a comprehensive assessment centering on an app's security and compliance frameworks, processes, and procedures. +* A qualified analyst's review. -We check the app against a series of security controls derived from leading industry-standard frameworks. - -The certificate demonstrates the strong security and compliance practices that are in place to protect customer data when the app is used in an organization. More information about how admins and users benefit from the certification is available at [Overview of Microsoft 365 app compliance program](/microsoft-365-app-certification/docs/enterprise-app-certification-guide). +We check the app against a series of security controls derived from leading industry-standard frameworks. Developers demonstrate following strong security and compliance practices to protect customer data when their app is used in an organization. More information about how admins and users benefit from the certification is available at [Overview of Microsoft 365 app compliance program](/microsoft-365-app-certification/docs/enterprise-app-certification-guide). -Administrators can quickly check for Microsoft 365 certified apps in the following ways. +Administrators can find Microsoft 365 certified apps and information about such apps in the following ways: -* When gathering more information about an app on the web, see the shield icon in [Microsoft documentation about the app](/microsoft-365-app-certification/teams/teams-apps). +* When evaluating an app, you can access app's security and compliance information and in some cases detailed evidences for this information. Developers provide answers to a questionnaire as part of their [Teams app's security and compliance information](/microsoft-365-app-certification/teams/teams-apps) for Publisher Attestation and for Microsoft 365 certification. :::image type="content" source="media/attested-app-doc-details.png" alt-text="View the Microsoft 365 certification information in the detailed help article about security and compliance of an app"::: -* When checking an application in [Teams admin center](https://admin.teams.microsoft.com/policies/manage-apps), sort the list of apps using the Certification column. See the icon and optionally, select the link to access the app-specific page mentioned above. + Developers of some Microsoft 365 certified apps and Copilot agents can choose to provide detailed evidences to help your organization quickly assess their app. Developers submit these comprehensive details as part of the audits done during certification. If developers agree to share these detailed evidence, then you can download these app trust evidences from the app details page in the Teams admin center. The download option is available only in commercial tenants. + + :::image type="content" source="media/m365-cert-download-evidence.png" alt-text="Screenshot showing the option to download detailed evidence provided by developers of certified apps." lightbox="media/m365-cert-download-evidence.png"::: + +* When checking an application in [Teams admin center](https://admin.teams.microsoft.com/policies/manage-apps), sort the list of apps using the Certification column. See the shield icon and optionally, select the link to access the app-specific page. :::image type="content" source="media/m365cert-apps-list1.png" alt-text="View Microsoft 365 certification status of an app in the Teams admin center." lightbox="media/m365cert-apps-list2.png"::: diff --git a/Teams/phone-number-calling-plans/manually-submit-port-order.md b/Teams/phone-number-calling-plans/manually-submit-port-order.md index 572bca740e..b26268fbf0 100644 --- a/Teams/phone-number-calling-plans/manually-submit-port-order.md +++ b/Teams/phone-number-calling-plans/manually-submit-port-order.md @@ -1,7 +1,7 @@ --- title: Manually submit a port order -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 10/24/2019 diff --git a/Teams/phone-number-calling-plans/more-information-about-porting.md b/Teams/phone-number-calling-plans/more-information-about-porting.md index 2b2aa06f56..6a2b15ca85 100644 --- a/Teams/phone-number-calling-plans/more-information-about-porting.md +++ b/Teams/phone-number-calling-plans/more-information-about-porting.md @@ -1,7 +1,7 @@ --- title: More information about porting -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: tonysmit,jastark ms.date: 10/23/2019 diff --git a/Teams/phone-number-calling-plans/port-order-overview.md b/Teams/phone-number-calling-plans/port-order-overview.md index 74445f8849..07e329b11e 100644 --- a/Teams/phone-number-calling-plans/port-order-overview.md +++ b/Teams/phone-number-calling-plans/port-order-overview.md @@ -1,7 +1,7 @@ --- title: What's a port order? -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 11/28/2017 diff --git a/Teams/phone-number-calling-plans/port-order-status.md b/Teams/phone-number-calling-plans/port-order-status.md index 4d82e7771b..b979033604 100644 --- a/Teams/phone-number-calling-plans/port-order-status.md +++ b/Teams/phone-number-calling-plans/port-order-status.md @@ -1,7 +1,7 @@ --- title: What's the status of your port orders? -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark ms.date: 11/28/2017 @@ -26,16 +26,16 @@ ms.collection: # What's the status of your port orders? -To see the status of your port order, in the left navigation of the Microsoft Teams admin center, go to > **Voice** > **Port orders**, and then click **Order history**. Each port order status is listed in the **Status** column. See [how long does it take to port numbers](../phone-number-calling-plans/port-order-overview.md#how-long-does-it-take-to-port-numbers) to learn about the order process. +To see the status of your port order, in the left navigation of the Microsoft Teams admin center, go to > **Voice** > **Port orders**, and then select **Order history**. Each port order status is listed in the **Status** column. See [how long does it take to port numbers](../phone-number-calling-plans/port-order-overview.md#how-long-does-it-take-to-port-numbers) to learn about the order process. -The following table lists port order statuses, as well as actions you can take if needed. +The following table lists port order statuses, and actions you can take if needed. |**Status**|**Can you view the order?**|**Can you edit the order?**|**Can you cancel the order?**|**Can you delete the order?**|**Description**| |:-----|:-----|:-----|:-----|:-----|:-----| |**Processing**
|Yes
|No
|Yes
|No
|The admin created the order, and it's been received by Microsoft.
| |**Contacting carrier**
|Yes
|No
|Yes
|No
|The order has been received and approved by Microsoft, and we're working with the losing carrier to get it approved.
| |**Transfer approved**
|Yes
|No
|Yes
|No
|The order has been accepted by the losing carrier, and the Firm Order Commitment (FOC) date has been set.
| -|**Transfer pending**
|Yes
|No
|No
|No
|The transfer is less than 24 hours away, so the order can no longer be edited or cancelled.
| +|**Transfer pending**
|Yes
|No
|No
|No
|The transfer is less than 24 hours away, so the order can no longer be edited or canceled.
| |**Error**
|No
|Yes
|Yes
|Yes (at this time, you can't delete the port order if there's an error. The port order needs to be re-created, or you need to contact the [TNS Service Desk](../manage-phone-numbers-for-your-organization/contact-tns-service-desk.md).
|The losing carrier rejected the order.
| |**Completed**
|Yes
|No
|No
|No
|The numbers have been successfully transferred.
| |**Cancelled**
|No
|Yes
|No
|No
|The admin canceled the order.
| @@ -44,7 +44,7 @@ For complete step-by-step instructions, see [Transfer phone numbers to Teams](tr If you need help or if you need to get more phone numbers, contact the [TNS Service Desk](../manage-phone-numbers-for-your-organization/contact-tns-service-desk.md). -## Related topics +## Related articles - [What's a port order?](port-order-overview.md) - [Different kinds of phone numbers used for Calling Plans](../different-kinds-of-phone-numbers-used-for-calling-plans.md) diff --git a/Teams/phone-number-calling-plans/supported-rate-centers-coverage-matrix.md b/Teams/phone-number-calling-plans/supported-rate-centers-coverage-matrix.md index b4b14d865a..69656a58a9 100644 --- a/Teams/phone-number-calling-plans/supported-rate-centers-coverage-matrix.md +++ b/Teams/phone-number-calling-plans/supported-rate-centers-coverage-matrix.md @@ -1,7 +1,7 @@ --- title: Supported rate centers and coverage for Calling Plans -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: davlick, julienp ms.date: 08/28/2020 diff --git a/Teams/phone-number-calling-plans/transfer-phone-numbers-to-teams.md b/Teams/phone-number-calling-plans/transfer-phone-numbers-to-teams.md index de72c9c6c8..e1631dee77 100644 --- a/Teams/phone-number-calling-plans/transfer-phone-numbers-to-teams.md +++ b/Teams/phone-number-calling-plans/transfer-phone-numbers-to-teams.md @@ -1,7 +1,7 @@ --- title: Transfer phone numbers to Microsoft Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: parththakkar ms.date: 03/26/2024 diff --git a/Teams/phone-numbers-licensing-changes.md b/Teams/phone-numbers-licensing-changes.md index b62a5c1e04..7eca68a8f9 100644 --- a/Teams/phone-numbers-licensing-changes.md +++ b/Teams/phone-numbers-licensing-changes.md @@ -1,7 +1,7 @@ --- title: "Phone numbers and licensing changes" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 07/28/2021 diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md new file mode 100644 index 0000000000..1fb591809b --- /dev/null +++ b/Teams/phones/authentication-best-practices-phones.md @@ -0,0 +1,108 @@ +--- +title: Authentication best practices for Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: dimehta +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +search.appverid: MET150 +f1.keywords: + - NOCSH +ms.localizationpriority: Medium +description: Best practices for Teams phones. This features Conditional Access, password policy, multifactor authentication advice and more. +--- + +# Authentication best practices for Teams phones + +The goals of devices used with Teams is to make different device management strategies necessary. For example, a personal business tablet used by a single sales person has a different set of needs from an on-call phone shared by many customer service people. Also, there are different requirements for a Teams phone that isn't shared with other people and another Teams phone that is used as a common area phone. See, [Set up common area phones for Microsoft Teams](/microsoftteams/set-up-common-area-phones). + +Security administrators and operations teams must plan for the devices that can be used in the organization. They must implement *security* measures best suited to each purpose. This article's recommendations make some of those decisions easier. + +>[!NOTE] +>Conditional Access requires a Microsoft Entra ID P1 or P2 subscription. + +>[!NOTE] +>Policies for Android mobile devices may not apply to Teams Android devices. + +## Authentication recommendations are different for personal versus shared android devices + +Shared Teams devices such as Teams phones can't use the same requirements for enrollment and compliance that are used on personal devices. Applying personal device authentication requirements to shared devices cause sign in issues. + +1. **Devices are signed out due to password policies.** + + Accounts used on Teams phones have a password-expiration policy. The accounts used with shared devices don't have a specific user to update and restore them to a working state when their passwords expire. If your organization requires passwords to expire and reset occasionally, these accounts stop working on Teams devices until a Teams administrator resets the password and signs back in. + + **Challenge**: When it comes to accessing. Teams from a device, a person's account has a password-expiration policy. When the password is going to expire, they change it. But accounts used on *shared devices*(Resource accounts) may not be connected to a single person who can change a password as required. This means a password can expire and leave workers on the spot, not knowing how to resume their work. + + When your organization requires a password reset or enforces password expiration, be sure a Teams administrator is prepared to reset the password so these shared accounts can sign back in. + +2. **Devices fail to sign in due to conditional access policies.** + + **Challenge**: Shared devices can't comply with Microsoft Entra Conditional Access policies for user accounts or personal devices. If shared devices are grouped with user accounts or personal devices for a Conditional Access policy, the sign-in will *fail*. + + For example, if multifactor authentication is required for accessing Teams, user entry of a code is needed to complete that authentication. Shared devices don't generally have a single user that can configure and complete multifactor authentication. Also, if the account must reauthenticate every X days, a shared device can't resolve the challenge without a user's intervention. + +## Best practices for the deployment of shared Teams phones + +Microsoft recommends the following settings when deploying Teams phones in your organization. + +### **Use a resource account and curtail its password expiration** + +Teams shared phones should use an [resource account](set-up-common-area-phones.md). You can either sync these accounts to Microsoft Entra ID from Active Directory or create them directly in Microsoft Entra ID. Any password expiration policies for users will also apply to accounts used on Teams shared devices, therefore, to avoid disruptions caused by password expiration policies, set the password expiration policy for shared devices to never expire. + +### **Review these Conditional Access policies** + +Microsoft Entra Conditional Access sets other requirements that devices must meet in order to sign in. For Teams phones, review the guidance that follows to determine if you have authored the policies that allow shared device users to do their work. + +> [!TIP] +> For an overview of Conditional Access, see [What is Conditional Access](/azure/active-directory/conditional-access/overview)? Use either [named location](/azure/active-directory/conditional-access/location-condition) or [require compliant device](/azure/active-directory/conditional-access/howto-conditional-access-policy-compliant-device) to secure shared device resource accounts. + +### You can use location-based access with named locations + +If shared Teams phones are provisioned in a well-defined location that can be identified with a range of IP addresses, you can configure Conditional Access using [named locations](/azure/active-directory/conditional-access/location-condition) for these devices. This conditional will allow these devices to access your corporate resources only when they are within your network. + +### When and when not to require compliant shared devices + +>[!NOTE] +>Device compliance requires an Intune license. + +When enrolling shared devices into Intune, you can configure device compliance as a control in Conditional Access so that only compliant devices can access your corporate resources. Teams phones can be configured for Conditional Access policies based on device compliance. For more information, see [AOSP Device Management Compliance Policy](/microsoftteams/rooms/android-migration-guide#creating-a-aosp-management-compliance-policy). + +>[!NOTE] +> Shared devices being used for *hot-desking* should be excluded from compliance policies. Compliance polices prevent the devices from enrolling into the hot desk user account. **Instead, use named locations to secure these devices**. +> To increase security, you can also [require multi-factor authentication](/azure/active-directory/authentication/tutorial-enable-azure-mfa) for *hot-desking users / user accounts* in addition to the named location policies. + +### Exclude shared devices from sign-in frequency conditions + +In Conditional Access, you can [configure sign-in frequency](/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime#user-sign-in-frequency) to require users to sign in again to access a resource after a specified time period. If sign-in frequency is enforced for phone resource accounts, shared devices sign out until they're signed in again by an admin. Microsoft recommends excluding shared devices from any sign-in frequency policies. + +### Using Filters for devices + +[Filters for devices](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) is a feature in Conditional Access that allows you to configure more granular policies for devices based on device properties available in Microsoft Entra ID. You can also use your own custom values by setting extension attributes 1-15 on the device object and then using those. + +Use filters for devices to identify your common-area devices and enable policies in two key scenarios: + +1. Excluding shared devices from policies applied for personal devices. For example, requiring device compliance *isn't enforced* for shared devices used for hot-desking, but *is enforced* for all other devices, based on model number. + +2. Enforcing special policies on shared devices that *shouldn't* be applied to personal devices. For example, requiring named locations as policy only for common-area devices based on an extension attribute you set for these devices (for example: “CommonAreaPhone”). + +>[!NOTE] +> Some attributes such as **model**, **manufacturer**, and **operatingSystemVersion** can only be set when devices are managed by Intune. If your devices are not managed by Intune, use extension attributes. + +## Teams Legacy Authorization + +Teams upgrade configuration policies offer a setting called **BlockLegacyAuthorization** which when enabled prevents Teams phones from connecting to Teams services. To learn more about this policy see, [Set-CsTeamsUpgradeConfiguration](/powershell/module/skype/set-csteamsupgradeconfiguration) or run Get-CsTeamsUpgradeConfiguration to check if **BlockLegacyAuthorization** is enabled in your tenant. + + ``` Powershell + Get-CsTeamsUpgradeConfiguration | fl BlockLegacyAuthorization + ``` diff --git a/Teams/devices/common-area-mobile-phones.md b/Teams/phones/common-area-mobile-phones.md similarity index 67% rename from Teams/devices/common-area-mobile-phones.md rename to Teams/phones/common-area-mobile-phones.md index 4a1fdb5a72..bde8b1c915 100644 --- a/Teams/devices/common-area-mobile-phones.md +++ b/Teams/phones/common-area-mobile-phones.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: prashibadkur -ms.date: 08/25/2024 +ms.date: 10/21/2024 ms.topic: article ms.service: msteams ms.subservice: itpro-devices @@ -29,15 +29,15 @@ description: Learn how to set up common area Android phones A Teams Android mobile app signed in with an account tied to **Microsoft Teams Shared Device** license is used as a shared device by frontline workers to make and receive calls as part of their daily work using Teams. - > [!IMPORTANT] - > To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. +> [!IMPORTANT] +> To use this feature you must have version 1.0.0.2023143401 (2023143401) or later installed on the Android mobile phone. ## Step 1 - Buy the licenses First, you need to purchase a **Teams Shared Devices** license. - > [!NOTE] - > Chat is not supported with a **Teams Shared Devices** license. +> [!NOTE] +> Chat is not supported with a **Teams Shared Devices** license. To purchase the license: @@ -46,17 +46,16 @@ To purchase the license: 1. In the product list, find **Microsoft Teams Shared Devices**, and select **Details**. 1. Enter the number of licenses you need, and select **Buy**. - > [!NOTE] - > If you're using Intune in your environment and have conditional access rules that require device compliance, you'll need to assign an **Microsoft Entra ID P1** and an **Intune** license to the device account that was used to sign in to the Teams mobile app. - > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams Android devices](authentication-best-practices-for-android-devices.md). + > [!NOTE] + > Teams-shared devices can be impacted by conditional access rules and other identity configurations, such as Multi-Factor Authentication. For more information, see [Authentication best practices for Teams phones](authentication-best-practices-phones.md). ## Step 2 - Create a new user account and assign licenses ### Using the Microsoft 365 admin center - > [!NOTE] - > If you're deploying more than one phone at a time, you can use only [PowerShell](../set-up-common-area-phones.md) to create accounts and assign licenses. - > You can use Microsoft 365 admin center to create accounts and assign licenses only if you're deploying one device at a time. +> [!NOTE] +> If you're deploying more than one phone at a time, you can use only [PowerShell](../set-up-common-area-phones.md) to create accounts and assign licenses. +> You can use Microsoft 365 admin center to create accounts and assign licenses only if you're deploying one device at a time. 1. Sign in to [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), and select **Users > Active Users > Add a user**. 1. Enter a username like **Main** for the first name and **Reception** for the second name. @@ -64,14 +63,13 @@ To purchase the license: 1. Enter a username like **BakeryPhone** or **DutyManager**. 1. Manually set the password for your common area phone. To set the password, clear the **Automatically create a password and require this user to change their password when they first sign in** checkbox. -> [!IMPORTANT] -> Manually setting a password for common area phones is recommended to prevent sign-in issues for your end users. + > [!IMPORTANT] + > Manually setting a password for common area phones is recommended to prevent sign-in issues for your end users. 6. Select the usage location of the device and assign the **Teams Shared Devices** license to the account. If any other licenses are needed, such as **Callings Plans**, assign those licenses too to the account. -> [!NOTE] -> -> When you assign a **Teams Shared Device** license to a device, you don't need to assign an additional Phone System license to get other features. To get inbound and outbound calling minutes with Microsoft Phone System you must add a Calling Plan and set up billing. However, if you are using Operator Connect or Direct Routing, you don't need a Calling Plan. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). + > [!NOTE] + > When you assign a **Teams Shared Device** license to a device, you don't need to assign an additional Phone System license to get other features. To get inbound and outbound calling minutes with Microsoft Phone System you must add a Calling Plan and set up billing. However, if you are using Operator Connect or Direct Routing, you don't need a Calling Plan. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). ### Using PowerShell diff --git a/Teams/phones/line-keys.md b/Teams/phones/line-keys.md new file mode 100644 index 0000000000..887a062066 --- /dev/null +++ b/Teams/phones/line-keys.md @@ -0,0 +1,104 @@ +--- +title: Manage line keys for speed dial on Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: prashibadkur +ms.date: 11/04/2024 +ms.topic: article +audience: Admin +appliesto: +- Microsoft Teams +ms.service: msteams +ms.subservice: itpro-devices +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +search.appverid: MET150 +ms.localizationpriority: medium +description: Learn how to set up and manage line or speed dial keys on Microsoft Teams certified phones for quick access to custom contacts and speed dial. +--- + +# Line or speed dial keys on Microsoft Teams certified phones + +This article provides you with guidance on setting up and managing line keys (or speed dial keys) on Microsoft Teams certified phones. This feature allows your users to use a phone line key to set up speed dial for their contacts and phone numbers for quick access using buttons on nontouch devices and sidecars. + +> [!IMPORTANT] +> This feature is only available on non touch Teams phones and not on touch-enabled Teams phones. + +A phone line key is one of the keys used to designate individual lines on a phone. Depending on the model and manufacturer, phones typically have between 2 and 12 phone line keys. + +## Steps to use line keys to set up speed dial + +To set up a line key for speed dial, follow these steps: + +1. **Update the Teams phone to version 1449/1.0.94.2024101709**. After updating the phone, you notice a new home screen experience on your device with a dedicated place for your line keys. To update your Teams phones, see [Update your phones remotely](remote-update-teams-phones.md). Verify that you're running Android version 1449/1.0.94.2024101709. + + You can see the versioning information in the Teams admin center or on the Teams phone. + + To see it in the Teams admin center: + + 1. Sign in to the Teams admin center. + 2. Go to **Teams devices** > **Phones** > then select the phone you want to look at. + 3. Then in the table under **Software type** look for **Teams** and in the **Current version** column you can see the version. + + To see the versioning information on the Teams phone itself: Go to the **Profile** icon > **Settings** > **About**. + + > [!IMPORTANT] + > With this update, you can use line keys to set up speed dial for contacts and phone numbers only. + + > [!NOTE] + > With this update, line keys are available for nontouch Teams phone and Teams phones with sidecars. + +2. **To assign a contact for speed dial:** Select on **Assign line key** and search for an existing contact including with an external phone number, or add a new one. + + - When you first start to assign line keys, you see: + + :::image type="content" source="./media/nontouch-line-keys-empty.jpg" alt-text="Screenshot of a non touch phone with line keys." + + - Find an available line key for you to use, and select **Assign line key**. + + :::image type="content" source="./media/nontouch-line-keys-assign.jpg" alt-text="Screenshot of an available line key on a Teams phone." + + - Press and hold on a line key to assign a contact or phone number: + + :::image type="content" source="./media/nontouch-line-keys-help.jpg" alt-text="Screenshot of how to long press a line key to set it up." + + - After you assign a contact or phone number to the line key, you'll see: + + :::image type="content" source="./media/nontouch-line-keys-assigned.jpg" alt-text="Screenshot of how to long press a line key that is assigned." + +3. **To modify or manage an assigned line key:** Long press an existing line key to see a detailed menu with the following options: + + :::image type="content" source="./media/nontouch-line-keys-manage.jpg" alt-text="Screenshot of line key management options." + + - **Unassign line key:** - Use this setting to remove an assigned line key. + - **Reassign line key:** - Use this setting to modify the contact assigned to this line key. + - **Manage line key:** - Use this setting to access more management options. + +4. **To place a call:** Press or select on the key to place a call to the user or number assigned to that line key. + +## Frequently Asked Questions + +**Question:** When will line keys be supported on touch Teams phones? +**Answer:** Support for touch Teams phone is coming soon. Check the public roadmap for timelines, see [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap?filters=In%20development%2CLaunched%2CRolling%20out%2CMicrosoft%20Teams). + +**Question:** Can line keys be configured on the Teams Admin Center with this update? + +**Answer:** No, currently configuration support is only on the Teams phone. + +**Question:** What other functions can I perform using line keys? + +**Answer:** With this update, you can use line keys for quick access to speed dial only. In the future, we support line keys for call controls and offer enhancements for shared line configuration. + +**Question:** Does this change the existing functionality of sidecars? + +**Answer:** Before the Teams application update to 1449/1.0.94.2024101709, users were able to add contacts to sidecars if the account was marked as a Favorite, speed dial, or assigned as a Boss. Additionally, users could pin groups to sidecars. With this update, contacts on sidecars can only be added by configuring them as line keys on the sidecar. Saved configurations continue to appear on the sidecar with this app. We'll make changes to streamline this experience on sidecars in the future. + +### Related articles + +- [Microsoft Certified Teams phones](../devices/teams-phones-certified-hardware.md) +- [Phones for Microsoft Teams](phones-for-teams.md) diff --git a/Teams/phones/manage-teams-phones.md b/Teams/phones/manage-teams-phones.md new file mode 100644 index 0000000000..9f70928ca9 --- /dev/null +++ b/Teams/phones/manage-teams-phones.md @@ -0,0 +1,106 @@ +--- +title: Manage Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: srpall +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - M365-collaboration + - m365initiative-deployteams + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - CSH +ms.custom: + - ms.teamsadmincenter.managedevices.overview + - ms.teamsadmincenter.devicemanagement.overview +description: Manage Teams phones you deployed in your organization. +ms.localizationpriority: medium +search.appverid: MET150 +--- + +# Manage Teams phones + +You can manage Teams phones used with Microsoft Teams in your organization from Microsoft Teams admin center. You can view and manage the device inventory for your organization and do tasks such as update, restart, and monitor diagnostics for devices. You can also create and assign configuration profiles to a device or groups of devices. + +To manage your phones, such as change device configuration, restart devices, manage updates, or view device and peripheral health, you need to be assigned one of the following Microsoft 365 admin roles: + +- Teams Service admin +- Teams Device admin + +For more information about admin roles in Teams, see [Use Teams administrator roles to manage Teams](../using-admin-roles.md). + +## What Teams phones can you manage? + +You can manage any Teams phone certified for, and enrolled in, Teams. Each Teams phone is automatically enrolled the first time it's signed into Teams on the device. For a list of certified devices that can be managed, see: [Certified Teams phones](/microsoftteams/devices/teams-phones-certified-hardware) + +To manage Teams phones, in the left navigation of the [Microsoft Teams admin center](https://admin.teams.microsoft.com), go to **Teams Devices**, and then select **Phones**. + +## Manage Teams phones + +In the Teams admin center, you can view and manage phones enrolled in Teams in your organization. Information that you'll see for each device includes device name, manufacturer, model, user, status, action, last seen, and history. You can customize the view to show the information that fits your needs. Teams Phones are automatically enrolled in Microsoft Intune if you've signed up for it. After a device is enrolled, device compliance is confirmed and conditional access policies are applied to the device. + +Here are some examples of how you can manage phones in your organization. + +| **Task** | **Action** | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change device information | Select a device > **Edit**. You can edit details such as device name, asset tag, and add notes. | +| Manage software updates | Select a device > **Update**. You can view the list of software and firmware updates available for the device and choose the updates to install. For more information about updating devices, see [Update Teams devices remotely](../devices/remote-update.md) | +| Assign or change configuration policies | Select one or more devices > **Assign configuration**. | +| Add or remove device tags | Select one or more devices > **Manage tags**. For more information about device tags, see [Manage Teams device tags](../devices/manage-device-tags.md). | +| Restart devices | Select one or more devices > **Restart**. | +| Filter devices using device tags | Select the filter icon, select the **Tag** field, specify a device tag to filter on, and select **Apply**. For more information about filtering devices using device tags, see [Use filters to return devices with a specific tag](../devices/manage-device-tags.md#use-filters-to-return-devices-with-a-specific-tag). | +|Schedule device actions|Actions like **Restart** and **Software update** can be scheduled for the preferred date and time.| +| View device history and diagnostics | Under the **History** column, select the **View** link for a device to view its update history and diagnostic details. | +|View device action details|In the **History** tab on the device page, select the action status to view the details of the action.| +|Cancel device actions|From the **History** section, you can cancel any action that is in a Queued or Scheduled state (not in progress or completed) to prevent execution. This option is accessible from the **History** tab in the device page and the **History** column in the list page. You can select multiple actions to cancel at once. Paired actions are canceled together if execution didn't start.| +|Actions on multiple devices|You can select multiple devices from the list page and perform an action on them at once. This is applicable for **Restart**, **Software update**, **Assign configuration**, **Manage tags**, **Remove device**, and **Sign-out**.| + +This video shows how to search for Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fHGQ?autoplay=false] + +### View issues with Teams phones + +You can view issues with Teams phones in the health status column of the device list. + +In addition to the health status of the device, the following issues are also surfaced in the health status column: + +1. **Sign-in errors exist** - There was an issue signing in to the device. Select the health status of the device to view the time the sign-in failure occurred, the account that attempted to sign into the device, the reason for the failure, and a history of previous sign-in failures. +2. **No connection** - The connection between Teams admin center and the device was lost. Restart or update the device through Teams admin center to resolve this error. +3. **Multiple issues** - One or more errors exist. Select the health status of the device to view the list of issues. + +> [!NOTE] +> If you don't see any issues for a device you're having trouble with, make sure the device's firmware is on the latest version. + +### Use configuration profiles in Teams + +Use configuration profiles to manage settings and features for different Teams phones in your organization. You can create or upload configuration profiles to include settings and features you want to enable or disable, and then assign a profile to a device or set of devices. + +#### Create a configuration profile + +To create a configuration profile for a Teams device type: + +1. In the left navigation, go to **Teams Devices** > **Phone** > **Configuration profiles** to create a new configuration profile for Teams phone. +2. Select **Add**. +3. Enter a name for the profile and optionally add a friendly description. +4. Specify the settings you want for the profile, and then Select **Save**. + The newly created configuration profile is displayed in the list of profiles. + +#### Assign a configuration profile + +After creating a configuration profile for a Teams device type, assign it to one or more devices. + +1. In the left navigation, go to **Teams Devices** > **Phones**. +2. Select one or more devices, and then Select **Assign configuration**. +3. In the **Assign a configuration** pane, search for configuration profile to assign to the selected devices. +4. Select **Apply**. + For the devices to which you applied the configuration policy, the **Action** column displays **Config Update** and the **Configuration profile** column displays the configuration profile name. diff --git a/Teams/phones/media/nontouch-line-keys-assign.jpg b/Teams/phones/media/nontouch-line-keys-assign.jpg new file mode 100644 index 0000000000..fa549813b5 Binary files /dev/null and b/Teams/phones/media/nontouch-line-keys-assign.jpg differ diff --git a/Teams/phones/media/nontouch-line-keys-assigned.jpg b/Teams/phones/media/nontouch-line-keys-assigned.jpg new file mode 100644 index 0000000000..b66f8833ad Binary files /dev/null and b/Teams/phones/media/nontouch-line-keys-assigned.jpg differ diff --git a/Teams/phones/media/nontouch-line-keys-empty.jpg b/Teams/phones/media/nontouch-line-keys-empty.jpg new file mode 100644 index 0000000000..70cde3b0ce Binary files /dev/null and b/Teams/phones/media/nontouch-line-keys-empty.jpg differ diff --git a/Teams/phones/media/nontouch-line-keys-help.jpg b/Teams/phones/media/nontouch-line-keys-help.jpg new file mode 100644 index 0000000000..ab462a20e6 Binary files /dev/null and b/Teams/phones/media/nontouch-line-keys-help.jpg differ diff --git a/Teams/phones/media/nontouch-line-keys-manage.jpg b/Teams/phones/media/nontouch-line-keys-manage.jpg new file mode 100644 index 0000000000..d79f94bb1b Binary files /dev/null and b/Teams/phones/media/nontouch-line-keys-manage.jpg differ diff --git a/Teams/devices/media/sign-in-teams.png b/Teams/phones/media/sign-in-teams.png similarity index 100% rename from Teams/devices/media/sign-in-teams.png rename to Teams/phones/media/sign-in-teams.png diff --git a/Teams/devices/media/teams-apps-1.png b/Teams/phones/media/teams-apps-1.png similarity index 100% rename from Teams/devices/media/teams-apps-1.png rename to Teams/phones/media/teams-apps-1.png diff --git a/Teams/phones/phones-deploy.md b/Teams/phones/phones-deploy.md new file mode 100644 index 0000000000..6b7fc5a6ef --- /dev/null +++ b/Teams/phones/phones-deploy.md @@ -0,0 +1,68 @@ +--- +title: Deploy Teams Phones using Conditional Access and Intune +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.date: 10/21/2024 +ms.reviewer: prashibadkur +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +f1.keywords: + - NOCSH +ms.collection: + - teams-rooms-devices + - M365-voice + - Teams_ITAdmin_Devices + - Tier1 +search.appverid: MET150 +ms.localizationpriority: medium +description: This article provides an overview of and features supported by Microsoft Teams Phones. +--- + +# Intune and Conditional Access for Teams Phones + +This article gives you an overview of how to deploy and configure Intune and Conditional Access to support Teams Phones. + +## Configure Intune to allow enrollment Teams Phones + +Customers must enroll their Teams phone devices using Android Device Administrator. Before devices can be enrolled into Intune successfully, there are a few basic steps to perform. If you're managing devices with Intune today, you may be able to skip several steps. If not, here's what to do: + +1. Ensure Intune is set as the MDM (mobile device management) authority. + + You need to set the MDM authority to be Intune before you can enroll devices. For more information, see [Set the mobile device management authority](/mem/intune/fundamentals/mdm-authority-set). Settings the MDM authority is a one-time step that has to be done upon creating a new Intune tenant. +1. Enable Android device administrator. + + Teams Phones are Android-based and without Google Mobile Services (GMS) and therefore are managed in Intune with Android Device Administrator (ADA). Device Administrator enrollment is off by default for newly created tenants. See [Android device administrator enrollment](/mem/intune/enrollment/android-enroll-device-administrator) for steps on how to enable Android Device Administrator in your environment. + > [!NOTE] + > Intune enrollment for Teams Phones will switch to Android Open Source Project (AOSP) Device Management in 2025. + +1. Assign Device Administrator compliance policies. + + Android Device Administrator offers Intune compliance policies which can be used to ensure Teams Phones are compliant with various organization security policies. Create an Android Device Administrator compliance policy then assign it to your Teams phone resource accounts. For more information, see [use compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). + +> [!NOTE] +> - If the user account used to sign into a Teams device isn't licensed for Intune, Intune compliance policies and enrollment restrictions need to be disabled for the account. +> - If the user account used to sign into a Teams device is licensed for Intune, the Teams device will automatically enroll in Intune. + +## Conditional Access + +Conditional Access is a Microsoft Entra ID feature that helps to ensure devices accessing your Microsoft 365 resources are properly managed and secure. For Teams Phones, we recommend using Conditional Access to secure Teams phone resource accounts since resource accounts don't support user interactive multi-factor authentication (MFA). Conditional Access can be used to enforce a different secondary factor, such as known network location or compliant device to match organization security policies. If you apply a Conditional Access policy requiring Teams Phones to be Intune compliance, the Teams phone must be enrolled into Intune with a compliance policy configured. If the device isn't enrolled into Intune, or if its enrolled, but its settings don't comply with your policies, Conditional Access prevents that Teams phone from signing in successfully. + +Typically, compliance policies defined within Intune are assigned to groups of users. This means that if you assign an Android compliance policy to user@contoso.com, that policy applies equally to their Android smartphone and to any Android-based Teams device that user@contoso.com signs into. For more information, review [Teams phone authentication best practices](authentication-best-practices-phones.md). + +If you use Conditional Access compliance policies, Intune enrollment is required. There are a couple things you need to set up to allow for a successful Intune enrollment: + +- **Intune license** The user signing into the Teams phone must be licensed for Intune. As long as the Teams device is signed in to a user account that has a valid Intune license, the device is automatically enrolled in Microsoft Intune as part of the sign in process. +- **Configure Intune** You must have a properly configured Intune tenant set up for Android Device Administrator enrollment. + +## See also + +[Phones for Teams](phones-for-teams.md) + +[Certified Teams Phones](../devices/teams-phones-certified-hardware.md) + +[Teams Marketplace](https://office.com/teamsdevices) diff --git a/Teams/devices/phones-for-teams.md b/Teams/phones/phones-for-teams.md similarity index 90% rename from Teams/devices/phones-for-teams.md rename to Teams/phones/phones-for-teams.md index f292f0ebd9..19f2e95923 100644 --- a/Teams/devices/phones-for-teams.md +++ b/Teams/phones/phones-for-teams.md @@ -64,18 +64,18 @@ For more information about getting Teams, check out [How do I get access to Micr ## Deploy your phones using Intune -To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](phones-panels-deploy.md). +To learn more about how to deploy Teams displays using Intune, see [Deploy Teams phones and Teams panels](../phones/phones-deploy.md). ## Manage your phones -Manage and keep your Teams phones up-to-date using the Microsoft Teams admin center. For more information, see [Manage your devices in Teams](device-management.md). +Manage and keep your Teams phones up-to-date using the Microsoft Teams admin center. For more information, see [Manage your devices in Teams](../devices/device-management.md). ## Upgrade your phones to Teams displays -[Microsoft Teams displays](teams-displays.md) are a category of all-in-one dedicated Teams devices that feature an ambient touchscreen. With Teams displays, users can use a microphone, camera, and speakers (or Bluetooth headset) for a reliable calling and meeting experience. Teams displays integrates with users' Windows PCs to bring a companion experience that allows for seamless cross-device interaction. +[Microsoft Teams displays](../devices/teams-displays.md) are a category of all-in-one dedicated Teams devices that feature an ambient touchscreen. With Teams displays, users can use a microphone, camera, and speakers (or Bluetooth headset) for a reliable calling and meeting experience. Teams displays integrates with users' Windows PCs to bring a companion experience that allows for seamless cross-device interaction. ## See also [Teams Marketplace](https://office.com/teamsdevices) -[Certified Teams phones](teams-phones-certified-hardware.md) \ No newline at end of file +[Certified Teams phones](../devices/teams-phones-certified-hardware.md) \ No newline at end of file diff --git a/Teams/devices/plan-device-deployment.md b/Teams/phones/plan-device-deployment.md similarity index 77% rename from Teams/devices/plan-device-deployment.md rename to Teams/phones/plan-device-deployment.md index e45d44ddda..cde5b91887 100644 --- a/Teams/devices/plan-device-deployment.md +++ b/Teams/phones/plan-device-deployment.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: prashibadkur -ms.date: 08/02/2024 +ms.date: 10/21/2024 ms.topic: article ms.service: msteams ms.subservice: itpro-devices @@ -18,20 +18,18 @@ ms.collection: f1.keywords: - NOCSH search.appverid: MET150 -description: This article provides an overview of the tasks and steps to deploy Teams Phones in your organization. +description: This article provides an overview of the tasks and steps to deploy Teams phones in your organization. --- # Plan your deployment for Teams Phones -Teams Phone devices are a great way to stay connected and productive with your colleagues and customers. These devices are designed to provide a seamless calling and meeting experience. With just three easy steps, you can deploy a [Teams Phone device certified by Microsoft](https://www.microsoft.com/en-us/microsoft-teams/across-devices/devices/category/desk-phones-teams-displays/34?page=1&filterIds=), in your spaces and enjoy advanced calling features. +Teams phones are a great way to stay connected and productive with your colleagues and customers. These devices are designed to provide a seamless calling and meeting experience. With just three easy steps, you can deploy a [Teams Phone device certified by Microsoft](https://www.microsoft.com/en-us/microsoft-teams/across-devices/devices/category/desk-phones-teams-displays/34?page=1&filterIds=), in your spaces and enjoy advanced calling features. -## Step 1: Consider the space Teams Phone device will be used in +## Step 1: Consider the space the Teams Phone device will be used in - **Personal Space**: Used on an employee’s desk to make and receive calls. - **Shared Space**: Used in a shared space, such as a lobby, a building floor, or anywhere your employees and visitors need quick access to make call. -The space you choose will determine the type of license you'll need. - ## Step 2: Pick the licenses and workloads you'll need for the space |License |Calls |People |Voicemail | Walkie Talkie|Calendar| @@ -58,7 +56,7 @@ The space you choose will determine the type of license you'll need. :::image type="content" source="media/teams-apps-1.png" alt-text="Screenshot of teams app." lightbox="media/teams-apps-1.png"::: -## Step 3: Setup desired phone device experience for your users +## Step 3: Setup desired phone device experience for your users First, configure IP Phone Policy [SignInMode](/powershell/module/teams/new-csteamsipphonepolicy#-signinmode) parameter via PowerShell to enable associated apps on phone device. @@ -86,17 +84,12 @@ In addition to the above, you can choose from the following experiences on touch ## Best Practices: -- **Manage firmware and Teams app updates**: Enable [auto updates](remote-update.md#automatic-updates) of firmware via Teams admin center and assign devices to different rings (Validation, General, Final) to roll out updates in phases. You can assign the Validation ring to a small set of test phones and assign other phones to General and Final rings. - - > [!NOTE] - > Auto updates on Teams application is coming soon. Currently, you can [schedule](remote-update.md#manually-update-remote-devices) Teams application update via Teams admin center. +- **Manage firmware and Teams app updates**: Configure [auto updates](../devices/remote-update.md#automatic-updates) phases via Teams Admin Center (Validation, General, Final) to roll out updates in phases. You can assign the Validation ring to a small set of test phones and assign other phones to General and Final rings. -- **Manage Authentication**: For password management, review [Authentication best practices](authentication-best-practices-for-android-devices.md). +- **Manage Authentication**: For password management, review [Authentication best practices](authentication-best-practices-phones.md). - **Configure calling policies**: Configure different [calling policies](../teams-calling-policy.md) based on your needs. -- **Optimize phone memory usage**: To optimize phone performance, enable daily or automatic restart of Teams application on the phone device via [configuration profile](device-management.md#use-configuration-profiles-in-teams). - -- **Secure common area phones**: To provide secured access to settings on phone devices in shared spaces, set an Admin PIN on common area phones via [configuration profile](device-management.md#use-configuration-profiles-in-teams). +- **Secure common area phones**: To provide secured access to settings on phone devices in shared spaces, set an Admin PIN on common area phones via [configuration profile](../devices/device-management.md#use-configuration-profiles-in-teams). - **Secure personal phones**: Ask your users who use phones in personal spaces to set a phone device lock PIN for secured access instead of setting a default phone device lock PIN via configuration profile. diff --git a/Teams/phones/prepare-network-teams-phones.md b/Teams/phones/prepare-network-teams-phones.md new file mode 100644 index 0000000000..4437475525 --- /dev/null +++ b/Teams/phones/prepare-network-teams-phones.md @@ -0,0 +1,82 @@ +--- +title: Prepare your network for Team phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: prashibadkur +ms.date: 10/16/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +search.appverid: MET150 +description: Learn about how to prepare your network infrastructure for deploying Microsoft Teams phones so that you can take advantage of all of the available features. +--- + +# Plan your network environment for Teams Phones + +This section contains an overview of the steps required to prepare your network environment so that you can use all of the features of Microsoft Teams phones. This section also includes information on configuring local administive access to your Teams phones. + +## Confirm network configuration + +In order to function properly, Microsoft Phone devices must have access to a network that meets these requirements: + +- Review access to: Microsoft Teams, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Android Device - Network Security](/microsoftteams/rooms/security?tabs=Android#network-security) + +- Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Phones](qos-on-teams-phones.md) + +- Review if your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url + +- Review if your organization utilizes certificates for network access, you need the certificates for a successful setup + +> [!IMPORTANT] +> Be sure to use a network connection with enough bandwidth (we recommend 100 kbps up/down per Teams Phone) to ensure your calls perform well. + +### Certificates + +Your Microsoft Teams Phone device uses certificates for Microsoft Teams, network usage, and authentication. If the related servers use public certificates, which is the case for online, there should be no further action required on the part of the admin to install certificates. If, on the other hand, the certificate authority is a private CA then the device needs to trust that CA. This means having the CA + CA chain certificates installed on the device. Certificates can be installed via Intune or via OEM tooling. + +### Proxy + +> [!IMPORTANT] +> Microsoft Teams Phones does not support proxy authentication as it may interfere with regular operations of the room. Ensure that Microsoft Teams Phones have been exempted from proxy authentication before going into production. If your proxy server utilizes internally signed certificates, you must install the internal certificate chain, including the root CA, on the Microsoft Teams Phone. + +Proxy settings on Teams Phones vary by device manufacturer. Consult OEM documentation for how to best configure Teams Phone devices for a network with a proxy. + +## Wireless network considerations + +We strongly recommend that you connect your Teams Rooms devices to a wired network for greater stability and performance, ensuring a seamless meeting experience. If using a wired connection isn't available, you may opt to use a wireless connection. + +> [!IMPORTANT] +> Wireless networks can be prone to network interference leading to quality degradation. We strongly recommend that you follow your wireless equipment provider's best practices when configuring a wireless connection to improve video and audio quality. + +Here are some examples of wireless network configuration best practices recommended by various manufacturers: + +- Deploy wireless equipment, such as access points and routers, that can handle and distribute the bandwidth load across all connected devices in the network. +- As much as possible, use access points and routers from a single manufacturer to avoid further congesting the radio-spectrum. +- Ensure wireless equipment is installed in a way that reduces or eliminates interference from objects and other equipment. +- Ensure the wireless network shows strong signal strength (Wi-Fi signal showing full bars is preferred) on Teams Rooms and other device screens. +- Default to prioritizing 5-GHz coverage for devices to optimize for higher bandwidth. +- Enable band steering to ensure that 5 GHz is always given more priority when sharing the same network name as 2.4 GHz. +- Keep wireless channel utilization below 50%. +- Keep access point and router firmware up to date with the latest firmware versions and hot fixes. +- Verify that Teams Rooms devices and at least one access point see each other with a signal strength of -60 dBm or better. A dBm value closer to zero is preferred. Follow your equipment manufacturer's recommendations. +- Implement QoS whenever possible to allow monitoring and resolution of issues in real time. + +For more best practices specific to your wireless network hardware, check your manufacturer's documentation. + +## Tenant Restrictions + +For organizations which utilize [tenant restrictions](/entra/identity/enterprise-apps/tenant-restrictions) features of Microsoft Entra ID, this is supported on some Teams Devices if your organization utilizes the proxy deployment variant with header injection. However, tenant restrictions aren't supported today on Teams Phone devices. Consult with your Android device OEM for potential workarounds. + +## Device administrative access + +Local administrative access to Teams Phone devices is controlled by the Teams device equipment manufacturer. Consult the device documentation for default accounts and passwords and instructions for how to change those passwords. diff --git a/Teams/phones/qos-on-teams-phones.md b/Teams/phones/qos-on-teams-phones.md new file mode 100644 index 0000000000..985d14c600 --- /dev/null +++ b/Teams/phones/qos-on-teams-phones.md @@ -0,0 +1,84 @@ +--- +title: Quality of service (QoS) configuration on Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: mattslomka +ms.date: 10/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn about the key considerations for deploying Quality of Service (QoS) on your network to support Teams phones. +--- + +# Quality of service (QoS) set up on Teams phones + +Deploying one or many Microsoft Teams phone devices requires planning. One of the key considerations is your organization's network capacity and quality of service (QoS) configuration. + +This article explains: + +1. [How much bandwidth does a Microsoft Teams phone device use?](#how-much-bandwidth-does-a-microsoft-teams-phone-device-use) +1. [How to control that bandwidth usage?](#how-do-i-control-microsoft-teams-phone-bandwidth-usage) +1. [How to ensure your devices are optimized with the right quality of service (QoS) configuration to align to your organizations requirements?](#quality-of-service-qos-with-microsoft-teams-phones) + +Wired network connectivity is recommended for Microsoft Teams phone devices. If wireless network connectivity is the only option, see best practice guidance [here](../Phones/prepare-network-teams-phones.md#wireless-network-considerations). + +## How much bandwidth does a Microsoft Teams phone device use? + +Microsoft Teams phone is designed to give the best audio experience regardless of your network conditions. + +The following table provides rough estimates of bandwidth utilized for the various streams in *kbps* (down/up) + +|Feature |Standard |Advanced | +|---------|---------|---------| +|Audio | 58/58 | 76/75 | + +## How do I control Microsoft Teams phone bandwidth usage? + +If you wish to implement a bandwidth policy on your common area phones, we recommend allocating 100 kbps to each Teams phone resource account. This implementation can be accomplished by assigning a Teams meeting policy with a media bitrate limit configured. When setting the meeting policy at 100 kbps, Teams phones still only use the bandwidth required for the call, and dynamically adjusts if its network connection isn't able to sustain 100 kbps. For user signed in devices, the meeting policy assigned to the users account will also apply to the Teams phone device. + +For information on how to configure a Teams meeting policy, see [Meeting policy settings for audio and video](../meeting-policies-audio-and-video.md). You want to create a custom policy and assign it to all Microsoft Teams phone resource accounts, with the limit for media bitrate configured for 100 kbps. + +## Quality of Service (QoS) with Microsoft Teams phones + +Microsoft Teams Rooms supports Quality of Service (QoS) Differentiated Services Code Point (DSCP) markings to ensure you can manage the media traffic on your corporate network. + +We recommend the following QoS markings and port ranges for the audio, video, and application/screen sharing types of media traffic: + +**Audio**: + +- Client source port range: **50,000-50,019** +- Protocol: **TCP/UDP** +- DSCP value: **46** +- DSCP class: **Expedited Forwarding (EF)** + +**Calling and Meetings Signaling**: + +- Client source port range: **50,070-50,089** +- Protocol: **UDP** +- DSCP value: **40** +- DSCP class: **CS5** + +For more information on Teams Media and implementing QoS, see [Implement Quality of Service (QoS) in Microsoft Teams](../QoS-in-Teams.md). + +For Teams phones, you need to configure your Microsoft Teams tenant to insert QoS markings. Teams phone devices honor this policy and apply the markings defined earlier in this document. + +For instructions on how to configure your tenant to insert QoS markings, see [Teams settings and policies reference](../settings-policies-reference.md). + +## Related articles + +- [Implement Quality of Service (QoS) in Microsoft Teams](../QoS-in-Teams.md) +- [Implement Quality of Service (QoS) in Microsoft Teams clients](../QoS-in-Teams-clients.md) +- [Configure the NetworkQoSPolicy CSP](/windows/client-management/mdm/networkqospolicy-csp) +- [Prepare your organization's network for Microsoft Teams](../prepare-network.md) diff --git a/Teams/phones/remote-provision-remote-login-phones.md b/Teams/phones/remote-provision-remote-login-phones.md new file mode 100644 index 0000000000..82a96d7007 --- /dev/null +++ b/Teams/phones/remote-provision-remote-login-phones.md @@ -0,0 +1,111 @@ +--- +title: Remote provisioning and sign in for Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: vapati +ms.date: 10/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn how to remotely provision and sign in to Teams phones that are deployed in your organization. +--- + +# Remote provisioning and sign in for Teams phones + +IT admins can remotely provision and sign in to a Teams phone devices. To provision a Teams phone remotely, the admin needs to upload the MAC addresses of the devices being provisioned and create a verification code. The entire process can be completed remotely from Teams admin center. + +> [!NOTE] +> Once you've signed in to a Teams phone, this feature isn't available. To use it again, the device must be reset to factory default settings. + +## Supported devices + +All Teams phone devices certified by Microsoft can be provisioned remotely from Teams admin center. + +Refer to the following for the list of certified hardware: [Certified Teams phones](../devices/teams-phones-certified-hardware.md) + +## Add a device MAC address + +Complete the following steps to provision a new device. + +1. Sign in to the Teams admin center. +2. Expand **Teams Devices** and select "Phones" +3. Select the **Actions** tab and then **Provision devices**. + +In the **Provision devices** window, you can either add the MAC address manually or upload a file. + +### Manually add a device MAC address + +1. From the **Waiting on activation** tab, select **Add MAC addesses manually**. + + :::image type="content" alt-text="Screenshot of 'Add MAC address' for manually adding a the MAC address for a device." source="../media/remote-provision-6-new.png" lightbox="../media/remote-provision-6-new.png"::: + +1. Enter the MAC address. +1. Enter a location, which helps technicians identify where to install the devices. +1. Select **Save** when finished. + +### Upload a file to add a device MAC address + +1. From the **Waiting on activation** tab, select **Upload multiple MAC addresses**. +2. Download the file template. +3. Enter the MAC ID and location, and then save the file. +4. **Select a file**, and then select **Upload**. + +## Generate a verification code + +You need a verification code for the devices. The verification code is generated in bulk or at the device level and is valid for 24 hours. + +1. From the **Waiting on activation** tab, select an existing MAC address. + A password is created for the MAC address and is shown in the **Verification Code** column. + +2. Provide the list of MAC addresses and verification codes to the field technicians. You can export the detail directly in a file and share the file with the technician who is doing the actual installation work. + +## Provision the device + +When the device is powered on and connected to the network, the technician provisions the device. These steps are completed on the Teams device. + +1. The technician selects **Provision device** from the **Settings**. + + ![Provision new device option from the Actions tab.](../media/provision-device1.png) + +2. The technician enters the device-specific verification code in the provided input field. + + ![Provision new device verification.](../media/provision-device-verification1.png) + + Once the device is provisioned successfully, the tenant name appears on the sign-in page. + + ![Tenant name on sign-in page.](../media/provision-code.png) + +## First time remote sign in + +The provisioned device appears in the **Waiting for sign in** tab. Start the remote sign-in process by selecting the individual device. + +1. Select a device from the **Waiting for sign in** tab. + + ![The window with a list of devices ready for sign in.](../media/remote-device1.png) + +2. Follow the instructions in **Sign in a user**, and then select **Close**. + + ![The Sign in a user window for individual device.](../media/sign-in-user.png) + + This video shows how admins can remotely provision Android-based and SIP devices. + + > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fRYe?autoplay=false] + +## Related articles + +- [Manage your devices in Teams](../devices/device-management.md) +- [Remote sign in and sign out](../devices/remote-sign-in-and-sign-out.md) +- [Update Teams devices remotely](../devices/remote-update.md) + diff --git a/Teams/phones/remote-sign-in-and-sign-out-phones.md b/Teams/phones/remote-sign-in-and-sign-out-phones.md new file mode 100644 index 0000000000..3c33f6fa14 --- /dev/null +++ b/Teams/phones/remote-sign-in-and-sign-out-phones.md @@ -0,0 +1,53 @@ +--- +title: Remote sign in and sign out for Teams phones +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: ayerragangu +ms.date: 09/17/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn how to remotely sign in and sign out of Teams phones. +--- + +# Remote sign in and sign out for Teams phones + +This article describes how to remote sign in and sign out Teams phones from the Teams admin center. + +This video shows how to sign into Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fHGR?autoplay=false] + +## Remote sign in + +After a phone is provisioned and signed in for the first time, it will appear on its corresponding page under the **Teams devices** node of the Teams admin center. + +To sign in a phone, go to the corresponding device page. + +1. Select the phone you want to sign in. + +2. Go to the **Actions** menu, and select **Sign in a user**. + +## Remote sign out + +1. Select the phone you want to sign out from the corresponding page. + +2. Go to the **Actions** menu, and select **Sign out**. + +## Related articles + +- [Remotely provisioning and sign in for Teams Android devices](../devices/remote-provision-remote-login.md) +- [Manage your devices in Teams](../devices/device-management.md) +- [Update Teams devices remotely](../devices/remote-update.md) diff --git a/Teams/phones/remote-update-teams-phones.md b/Teams/phones/remote-update-teams-phones.md new file mode 100644 index 0000000000..938535ec4c --- /dev/null +++ b/Teams/phones/remote-update-teams-phones.md @@ -0,0 +1,186 @@ +--- +title: Updating Teams phones remotely +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: vapati +ms.date: 09/13/2024 +ms.topic: article +ms.service: msteams +ms.subservice: itpro-devices +audience: Admin +appliesto: + - Microsoft Teams +ms.collection: + - teams-rooms-devices + - Teams_ITAdmin_Devices + - Tier1 +f1.keywords: + - NOCSH +ms.localizationpriority: medium +description: Learn how to remotely update the firmware and apps for Teams phones using the Teams admin center. +--- + +# Remotely update firmware and software on Teams phones + +Using Teams admin center, you can update your Teams devices, including Teams phones, remotely. The following software components on your device can be updated from within Teams admin center: + +- **Teams app** - available for Manual and Automatic updates + +- **Device firmware** - available for Manual and Automatic updates + +- **Company Portal app** - available for Manual updates only + +- **Admin agent app** - available for Manual updates only + +Updates for Teams app and device firmware happen automatically by default. However, you can update them manually as well. When you're applying updates manually, they can be applied immediately or scheduled to be updated on a future date and time that you set. + +> [!IMPORTANT] +> Microsoft strongly recommends using Teams Admin Center for managing and updating your Teams devices. Teams Admin Center ensures that all firmware and app updates installed on your Teams devices are validated and supported by Microsoft, which is essential for optimal performance and reliability of your Teams devices. By exclusively using firmware and app updates from the Teams Admin Center, you can avoid the risks and disruptions associated with alternative update methods. If customers use any other way to update, Microsoft can't guarantee to provide regular updates for those devices. + +## Software versions on Teams Admin Center + +All new software versions for Teams devices are made available on Teams admin center once they're published by Microsoft. New releases might have minimum software version requirements. In such cases, the new version is only made available if the device meets the requirements. Verify that the device is meeting those requirements, but especially the firmware is current and updated. + +Only software versions that have been tested by Microsoft are available for automatic or manual updates using Teams admin center. Software versions tested by Microsoft are labeled **Verified by Microsoft**. + +Additionally, earlier versions of the software may also be made available and are labeled as **Microsoft Preview**. Devices can be manually updated to Microsoft Preview versions that are released, and those devices running on these versions are also eligible for receiving automatic updates in future. + +Firmware versions that have not been tested by Microsoft are labeled **Unknown version**. Devices running an unknown firmware version can't be automatically updated. These devices can only be updated manually. + +Refer to this list for the details on new releases and the requirements that must be met. See [Certified Teams phones - Firmware](../devices/teams-phones-certified-hardware.md?tabs=firmware) + +## Automatic updates + +### Assign phones to update phases + +> [!NOTE] +> Devices within a phase will be updated gradually over a few weeks rather than all at once. Also, automatic updates of Teams devices using the Teams admin center isn't available in GCC High and DoD. Organizations in GCC High and DoD can, however, [manually update](#manually-update-remote-devices) using the Teams admin center. + +To choose the automatic update phase for your phones, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**. +3. Select one or more devices and then select **Update**. +4. Under **Automatic updates**, select one of the following phases: + - **Validation** This option is best for lab or test devices on which you can carry out any validation you need to perform. Updates start deployment as soon as the latest software version is released. Previously called **As soon as possible**. + - **General** This is the default option and is best for most of your general-purpose devices. Firmware updates start deployment only after **30 days** from the release of the new firmware version. Teams app updates start deployment only after **15 days** from the release of the new Teams app version. Previously called **Defer by 30 days** (applicable for firmware updates). + - **Final** This option is best for devices used by VIPs and in large settings after large-scale validation is complete. Firmware updates start deployment only after **90 days** from the release of the new firmware version. Teams app updates start deployment only after **45 days** from the release of the new Teams app version. Previously called **Defer by 90 days** (applicable for firmware updates). +5. Select **Update**. + +To see which phase a device is in, see the **Automatic updates** column in the Teams admin center. To see which devices are part of a specific phase, use the **Filter** option then select **Auto-update phase**. + +If you need to revert or remove firmware from a device that has been updated, you need to reset your device to its factory settings. Reset your device using the instructions from its manufacturer. + +### Configure Maintenance window +If you want to configure the Maintenance window for a device, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +1. Navigate to **Teams devices** and then select **Phones**. +1. Follow the steps for [editing or creating a new configuration profile.](manage-teams-phones.md#use-configuration-profiles-in-teams) + +1. Specify a suitable **Time window** by selecting a **Start time** and an **End time**. This time window follows the local timezone of the device. + + 1. The default Time Window is from **01:00 Hrs** to **04:00 Hrs**. + + 1. A minimum time window of 3 hours must be selected. + +1. Specify the **Update frequency** by selecting the days of the week that are suitable for carrying out updates on the devices when available. + +1. Default selection is for **Sunday**. + +1. Once the selection is done, **Save** the profile. If it's a new profile, you can **Assign** it to devices. If you're editing an existing profile, it automatically gets reapplied to the devices to which it's assigned. + +1. You can check the selected Maintenance window settings under the **Details** tab on the device page. + +Automatic updates, when they happen, utilize the maintenance window configured for the device, that is, the **Time window** on the selected days for **Update frequency**. Maintenance window can also be utilized for scheduling manual updates. + +Option to configure maintenance window isn't available in GCC-High and DoD. + +> [!NOTE] +> If an update operation is unable to start execution within the maintenance window it is scheduled for, it is cancelled and rescheduled for the next available maintenance window. + +### Track automatic updates + +If you want to check which software versions are currently rolling out for your devices, do the following steps: + +1. Sign in to Microsoft Teams admin center by going to https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**. +3. Refer to the widget titled **Software auto-updates** to determine the number of active update paths. +4. On this widget, select **View details**. A dialogue box opens showing the list of active update paths with the following details: + + - Device model and manufacturer + - Current version and new version + - Number of eligible devices + - Active phase + - Devices assigned to this update phase are being currently updated. Any device from a previous phase that isn't updated yet will also be included. + - Software component name + +> [!NOTE] +> The new version may not always be the latest available version. Devices running older versions may be updated in a step-wise approach, until they reach the latest version. + +### Pause automatic updates + +You can temporarily pause automatic updates for your tenant. When paused, Android based devices aren't automatically updated for the next 15 days. To pause the updates, do the following steps: + +1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. +2. Navigate to **Teams devices** and then select **Phones**. +3. Under the **Actions** menu, select **Pause auto-updates**. +1. Updates automatically resume after 15 days. If you want to resume the updates before that, select **Resume auto-updates** from under the **Actions** menu. + +## Manually update remote devices + +If you want to manually update devices using the Teams admin center, you can decide whether to update the devices immediately or schedule an update for a future date and time. + +To manually update remote devices, do the following steps: + +1. Sign in to Microsoft Teams admin center by visiting https://admin.teams.microsoft.com. +1. Navigate to **Teams Devices** and then select **Phones**. +3. Select one or more devices and then select **Update**. +1. Under **Manual updates**, select **Schedule** if you want to schedule the update for the upcoming **Maintenance window** or a future date and time. The updates are applied at the date and time in the timezone selected in **Timezone**. + +What you see depends on whether you have one, or multiple, devices selected. The left image below shows a single device selected while the image on the right shows multiple devices selected. + +![Device status update panel with single and multiple devices selected.](../media/mtr-devices/update-manual-together.png) + +When you select multiple devices, you can choose which update types to apply to each selected device. Select the update types you want to apply and select **Update**. + +When you select a single device, updates that are available for the device are shown. If multiple update types are available for the device, select each update type to apply. You can view the **Current version** applied on the device and the **New version** that will be applied. Select the update(s) you want to apply and select **Update**. + +After you select **Update**, updates are applied to your devices at the date and time of the selected scheduling option. If you didn't select a future date and time, updates are applied to your devices within a few minutes. + +To manage devices, you need to be a Global admin, Teams Service admin, or Teams Device admin. For more information about admin roles, see [Use Microsoft Teams administrator roles to manage Teams](../using-admin-roles.md). + +> [!IMPORTANT] +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + +This video shows how to update Teams devices. + +> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE5fxbK?autoplay=false] + +#### Tracking update status + +Administrators can track the status of these update operations from the 'History' section in the device page. Details for each operation are shown in the relevant row. More details are available on selecting the operation status. + +## Frequently asked questions about automatic updates + +1. **Which software components are automatically updated?** Both Firmware and Teams app are automatically updated for eligible devices. Automatic updates for Teams app is a feature still in early phase, therefore you might see some delays in device reaching the update phase. The gradual roll out of the feature is being done to ensure minimal impact on devices. + +1. **How fast does the rollout happen?** Eligible devices receive updates in weekly cycles based on the update phase they are in. For example, devices in General phase start receiving updates only after 15/30 days elapse since the new version was published. To ensure a stable rollout, the devices are updated gradually for a tenant and not all at once. Overall, the rollout of each new version takes a few weeks after the start of each update phase. + +Also, if the device is on an older version, like N-3. It is updated step-wise to intermediate versions, like N-2 and N-1, before it is updated to the latest version (N). Therefore, this device may take longer to reach the latest version than usual, but no intervention is required. + +1. **How do I check if a device has received an update?** Whenever a device receives an update (or has one scheduled), the History tab on the device page shows corresponding details for a software update operation. + +1. **I see that the updates are happening but they are failing. What do I do?** Sometimes the updates can fail due to transient conditions. In such cases, no intervention is required. Updates are automatically retried on the devices. If updates are consistently failing across your inventory, you can check a few things: + + - Devices are online at the time when updates are scheduled. + - Network configuration is done appropriately to allow download of updates. Refer to [URLs and IP address ranges for Microsoft Teams](/microsoft-365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams) for the URLs and IP address ranges that need to be allowed for Teams. + - If this doesn't help, reach out to Microsoft support with the logs. Device logs can be found in the History tab of the device page. They are linked to the Device diagnostics operation that is run with the software update operation. + +1. **The eligible count of devices does not seem to match the available devices.** The device count in **Automatic software updates** section shows the number of eligible devices that are ready to be updated. The devices that are already updated to the **New version** are not counted. It can also include devices from the previous phase that are not updated. + +1. **When do automatic updates happen?** The updates are scheduled to happen during the Maintenance window to minimize impact. If the device is offline at that time, the updates get executed when the device comes back online the next time. If the Maintenance window is already over, the update is rescheduled for the next available window. + +1. **Why do Teams app and Firmware follow a different cadence in update phases?** Updates phases allow Firmware auto-updates to start immediately (Validation phase), only after 30 days (General phase), or only after 90 days (Final phase). Since Firmware changes include significant changes, their rollout through auto-update is done at a slow pace to ensure minimal impact. On the other hand, the update phases allow Teams app to start immediately (for Validation phase), only after 15 days (for General phase), or only after 45 days (for Final phase). Teams app versions include smaller scope of changes for the devices than the Firmware and hence their auto-update rollout is done at a faster pace to bring the devices to recent versions. + diff --git a/Teams/set-up-common-area-phones.md b/Teams/phones/set-up-common-area-phones.md similarity index 70% rename from Teams/set-up-common-area-phones.md rename to Teams/phones/set-up-common-area-phones.md index 7425fcd79b..de17579227 100644 --- a/Teams/set-up-common-area-phones.md +++ b/Teams/phones/set-up-common-area-phones.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: prashibadkur -ms.date: 08/27/2024 +ms.date: 10/21/2024 ms.topic: article audience: Admin ms.service: msteams @@ -31,16 +31,13 @@ description: Learn how to set up common area phones for lobbies, reception areas # Set up common area phones for Microsoft Teams -A common area phone is typically placed in an area like a lobby or another area that is available to many people to make a call: a reception area, lobby, or conference phone. Common area phones are signed in with accounts tied to a **Microsoft Teams Shared Devices** license. +A common area phone is typically placed in an area like a lobby, reception area, or a conference room and is available to many people to make a call. Common area phones are signed in with resource accounts tied to a **Microsoft Teams Shared Devices** license. -This article provides an overview of how to deploy and configure Teams phone devices as common area phones for shared spaces. For a more complete meeting room experience, including audio conferencing, consider purchasing a dedicated **Teams Rooms** license with a Teams Rooms device instead. For more information about Teams Rooms, see [Microsoft Teams Rooms](rooms/index.md). - -> [!NOTE] -> Accounts for common area phones objects created in Skype for Business Server can't be migrated to Microsoft Teams. Follow the steps in this article to recreate those accounts for Teams, and, if required, migrate your Public Switched Telephone Network (PSTN) connectivity. +This article provides an overview of how to deploy and configure Teams phone devices as common area phones for shared spaces. For a more complete meeting room experience, including video, consider a dedicated **Teams Rooms** license with a Teams Rooms device instead. For more information about Teams Rooms, see [Microsoft Teams Rooms](../rooms/index.md). ## Step 1 - Buy the licenses -First, you need to purchase a **Teams Shared Devices** license and make sure that you have a certified phone. To search for and learn more about certified phones, go to [Microsoft Teams devices](https://products.office.com/microsoft-teams/across-devices?ms.url=officecomteamsdevices&rtc=1). +First, you need to purchase a **Teams Shared Devices** license and make sure that you have a certified phone. To search for and learn more about certified Teams Phones, go to [Teams Phones certified hardware](../devices/teams-phones-certified-hardware.md?tabs=certified-phones). 1. In the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339), go to **Billing** > **Purchase services**. @@ -50,12 +47,7 @@ First, you need to purchase a **Teams Shared Devices** license and make sure tha 4. Enter the number of licenses you need, and select **Buy**. -> [!NOTE] -> If you’re using Intune in your environment and have conditional access rules that require device compliance, you’ll need to assign an **Microsoft Entra ID P1**, and **Intune** license to the device account for the common area phone. -> -> Common area phones can be impacted by conditional access rules and other identity configurations, like Multi-Factor Authentication. See [Authentication best practices for Teams Android devices](devices/authentication-best-practices-for-android-devices.md) to learn more. - -## Step 2 - Create a new user account and assign licenses +## Step 2 - Create a new resource account and assign licenses ### Using the Microsoft 365 admin center @@ -81,19 +73,22 @@ If you're deploying one device: > [!NOTE] > You don't need to add a license with Phone System features. It's included with the **Teams Shared Devices** license. > -> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](./teams-add-on-licensing/microsoft-teams-add-on-licensing.md). +> If you aren't using Microsoft Phone System with Direct Routing or Operator Connect, you may want to add **Calling Plans** licenses. For more information on licenses, see [Microsoft Teams add-on licensing](../teams-add-on-licensing/microsoft-teams-add-on-licensing.md). ### Using PowerShell Use PowerShell when you want to create and assign licenses for more than one user account at once. For more information, see [Create Microsoft 365 user accounts with PowerShell](/microsoft-365/enterprise/create-user-accounts-with-microsoft-365-powershell?view=o365-worldwide&preserve-view=true) and [Assign Microsoft 365 licenses to user accounts with PowerShell](/microsoft-365/enterprise/assign-licenses-to-user-accounts-with-microsoft-365-powershell?view=o365-worldwide&preserve-view=true). +> [!NOTE] +> Common area phones can be impacted by conditional access rules and other identity configurations, like user interactive Multi-Factor Authentication (MFA). For more information, see [Authentication best practices for Teams Phones](authentication-best-practices-phones.md). + ## Step 3 - Set policies for common area phones Use policies to control which features are available to users on common area phones. ### IP phone policies -The Teams IP Phone policy can only be modified if the account signing into the phone is licensed with something other than a **Teams Shared Devices** license. If licensed with a Microsoft 365 E3 or E5 subscription, or an Office 365 Enterprise E1, E3, or E5 subscription, you can modify the IP Phone policy. If you're using a **Teams Rooms** license on your common area phone account, it will only let you use `MeetingRoomSignIn` mode. `MeetingRoomSignIn` mode isn't available on most common area phones. For more information about supported overrides for the phone interface, see [Set Microsoft Teams Android devices user interface](/microsoftteams/devices/teams-android-devices-user-interface#override-automatic-user-interface-detection). +The Teams IP Phone policy can only be modified if the account signing into the phone is licensed with something other than a **Teams Shared Devices** license. If licensed with a Microsoft 365 E3 or E5 subscription, or an Office 365 Enterprise E1, E3, or E5 subscription, you can modify the IP Phone policy. If you're using a **Teams Rooms** license on your common area phone account, it will only let you use `MeetingRoomSignIn` mode. `MeetingRoomSignIn` mode isn't available on most common area phones. For more information about supported overrides for the phone interface, see [Set Microsoft Teams Android devices user interface](/microsoftteams/devices/teams-android-devices-user-interface#override-automatic-user-interface-detection). Using the Teams IP Phone policy, set the [SignInMode parameter](/powershell/module/teams/new-csteamsipphonepolicy#parameters) to `CommonAreaPhoneSignIn` to enable the common area phone experience on the Teams phone device. @@ -101,18 +96,18 @@ To configure other parameters, consider creating an [IP phone policy](/powershel ### Calling policies -Use calling policies to enable private calls, using call forwarding, or simultaneous ring on common area phones. To learn more, see [Configure calling policies in Teams](teams-calling-policy.md). +Use calling policies to enable private calls, using call forwarding, or simultaneous ring on common area phones. To learn more, see [Configure calling policies in Teams](../teams-calling-policy.md). -By default, call park isn't enabled for common area phones. You'll need to create a policy to enable it. To learn more, see [Call park and retrieve in Microsoft Teams](call-park-and-retrieve.md). +By default, call park isn't enabled for common area phones. You need to create a policy to enable it. To learn more, see [Call park and retrieve in Microsoft Teams](../call-park-and-retrieve.md). > [!NOTE] > After you assign a policy, sign out of the phone and sign back in. It may take up to an hour for a policy assignment to take effect. ## Step 4 - Acquire and assign phone numbers -See [Manage telephone numbers for your organization](manage-phone-numbers-landing-page.md) to learn how to acquire and assign phone numbers based on your PSTN connectivity option. +See [Manage telephone numbers for your organization](../manage-phone-numbers-landing-page.md) to learn how to acquire and assign phone numbers based on your PSTN connectivity option. -## Step 5 - Sign in +## Step 5 - Sign in the Teams PHone Once you create and configure a user account, you can sign into a phone. Depending on how many phones you're deploying, you have three sign-in options: @@ -120,28 +115,32 @@ Once you create and configure a user account, you can sign into a phone. Dependi - [Sign in from another device](#sign-in-from-another-device). - [Sign in using the Teams admin center](#sign-in-using-the-teams-admin-center). +### Resource Accounts Sign in Test + +Use this tool: [Teams phone sign in test](https://testconnectivity.microsoft.com/tests/TeamsPhoneDeviceSignIn/input) to test that your Teams phone common area resource account is configured for successful sign-on. + ### Local sign-in To sign in locally with a username and password: 1. Turn on the common area phone. 2. Select **Sign in on this device**. -3. Follow the sign-in directions on the device. Once signed in, the phone will display the common area phone user experience. +3. Follow the sign-in directions on the device. Once signed in, the phone displays the common area phone user experience. > [!NOTE] -> If you are using a custom setup policy that unpins the calling app, the dial pad doesn't appear on the common area phone. For more information about Teams setup policies, see [Manage app setup policies in Microsoft Teams](teams-app-setup-policies.md). +> If you are using a custom setup policy that unpins the calling app, the dial pad doesn't appear on the common area phone. For more information, about Teams setup policies, see [Manage app setup policies in Microsoft Teams](../teams-app-setup-policies.md). ### Sign in from another device -You can also sign into to a common area phone from another device using a code. When you sign in this way, you'll enter the username and password on another device, rather than on the phone itself. +You can also sign into to a common area phone from another device using a code. When you sign in this way, you enter the username and password on another device, rather than on the phone itself. For more information see [Remote sign in and sign out for Teams Phones](remote-sign-in-and-sign-out-phones.md). 1. On your common area phone, find the code displayed on the sign-in screen. 2. On another device, go to [https://www.microsoft.com/devicelogin](https://www.microsoft.com/devicelogin). -3. Enter the code and follow the instructions to complete signing in. +3. To complete signing in, enter the code and follow the instructions. ### Sign in using the Teams admin center -As an admin, you can remotely provision and sign into common area phones from the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2066851). This method is the most efficient sign-in method when you're deploying a large number of phones at once. See [Remote provisioning and sign in for Teams Android devices](devices/remote-provision-remote-login.md) to learn more. +As an admin, you can remotely provision and sign into common area phones from the [Teams admin center](https://go.microsoft.com/fwlink/p/?linkid=2066851). This method is the most efficient sign-in method when you're deploying a large number of phones at once. See [Remote provisioning and sign in for Teams Android Phones](remote-provision-remote-login-phones.md) to learn more. ## Step 6 - Set up Advanced calling on common area phones (optional) @@ -149,13 +148,13 @@ By default, the basic calling experience will be on the common area phone's home The following advanced calling features are available for supported Teams phone device models with a **Teams Shared Devices** license and the latest Teams updates (minimum version: 1449/1.0.94.2022061702): -- [Call park and retrieve](call-park-and-retrieve.md). -- [Cloud-based voicemail through Exchange Online Plan 2](set-up-phone-system-voicemail.md). +- [Call park and retrieve](../call-park-and-retrieve.md). +- [Cloud-based voicemail through Exchange Online Plan 2](../set-up-phone-system-voicemail.md). - To disable cloud-based voicemail, see [Voicemail user settings using PowerShell](/powershell/module/teams/set-csonlinevoicemailusersettings). -- [Call queues](create-a-phone-system-call-queue.md). -- [Auto attendants](create-a-phone-system-auto-attendant.md). -- [Group call pickup](call-sharing-and-group-call-pickup.md). -- [Forwarding rules](user-call-settings.md). +- [Call queues](../create-a-phone-system-call-queue.md). +- [Auto attendants](../create-a-phone-system-auto-attendant.md). +- [Group call pickup](../call-sharing-and-group-call-pickup.md). +- [Forwarding rules](../user-call-settings.md). To use these advanced calling features on a supported Teams phone device model, you can turn on the **Advanced calling** toggle in the [Teams admin center](https://admin.teams.microsoft.com/) or on your Teams phone device that is signed into your Teams Shared Devices account. Once you turn on advanced calling home screen experience on the phone, the device will update. @@ -177,7 +176,7 @@ Turning on advanced calling capabilities requires you to purchase hardware model ## Step 7 - Set up Hotline/PLAR on common area phones (optional) -You can set up common area phones as hotline phones also known as PLAR (Private Line Auto Ringdown) phones. You can program this phone to autodial a pre-configured PSTN number or a directory contact when the phone handset is picked up. +You can set up common area phones as hotline phones also known as PLAR (Private Line Auto Ringdown) phones. You can program this phone to autodial a preconfigured PSTN number or a directory contact when the phone handset is picked up. ### Turn on Hotline in the Teams admin center @@ -198,10 +197,10 @@ You can set up common area phones as hotline phones also known as PLAR (Private ## Next steps -Now that you've set up and signed in common area phones for your organization, you can manage them in the Teams admin center. See [Microsoft Teams: Managing your devices](devices/device-management.md) to learn more. +Now that you've set up and signed in common area phones for your organization, you can manage them in the Teams admin center. See [Microsoft Teams: Managing your devices](../devices/device-management.md) to learn more. ## Related articles -- [Update Microsoft Teams devices remotely](devices/remote-update.md). -- [Manage Microsoft Teams device tags](devices/manage-device-tags.md). -- [Microsoft Teams device health monitoring](alerts/device-health-status.md). +- [Update Microsoft Teams devices remotely](../devices/remote-update.md). +- [Manage Microsoft Teams device tags](../devices/manage-device-tags.md). +- [Microsoft Teams device health monitoring](../alerts/device-health-status.md). diff --git a/Teams/devices/teams-android-devices-user-interface.md b/Teams/phones/teams-android-devices-user-interface.md similarity index 98% rename from Teams/devices/teams-android-devices-user-interface.md rename to Teams/phones/teams-android-devices-user-interface.md index 059cf7c6e9..495e17c4d2 100644 --- a/Teams/devices/teams-android-devices-user-interface.md +++ b/Teams/phones/teams-android-devices-user-interface.md @@ -89,7 +89,7 @@ After granting the policy to the meeting room resource account, you'll need to w ## Impact on Microsoft Teams admin center -Microsoft Teams admin center allows you to manage Microsoft Teams devices. For more information on managing devices using Teams admin center, see [Manage your devices in Microsoft Teams](device-management.md). +Microsoft Teams admin center allows you to manage Microsoft Teams devices. For more information on managing devices using Teams admin center, see [Manage your devices in Microsoft Teams](../devices/device-management.md). Teams admin center provides the ability to manage Teams phones. Phones are filtered into one of three tabs based on their function: user phones, common area phones, and conference phone. diff --git a/Teams/plan-auto-attendant-call-queue.md b/Teams/plan-auto-attendant-call-queue.md index 084ee7851d..e9c5893705 100644 --- a/Teams/plan-auto-attendant-call-queue.md +++ b/Teams/plan-auto-attendant-call-queue.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: colongma -ms.date: 01/31/2024 +ms.date: 10/31/2024 ms.topic: article ms.assetid: ab9f05a2-22cb-4692-a585-27f82d1b37c7 ms.tgt.pltfrm: cloud @@ -17,8 +17,8 @@ ms.collection: - tier1 audience: Admin appliesto: - - Skype for Business - Microsoft Teams + - Skype for Business ms.localizationpriority: medium f1.keywords: - CSH @@ -77,11 +77,11 @@ Call queues don't provide separate call routing for off hours and holidays. Even To configure Auto attendants and Call queues, you need the following resources: -- A [Resource Account](manage-resource-accounts.md) for each Auto attendant and each Call queue. +- A [Resource Account](manage-resource-accounts.md) for each Auto attendant or Call queue that directly answers calls. Nested auto attendants or call queues which receive calls from an auto attendant or call queue that has already answered the call don't require a resource account. - A free [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md) for each resource account. - External phone calls: - At least one [Microsoft service number](getting-service-phone-numbers.md), [Operator Connect number](operator-connect-plan.md), [Direct Routing number](direct-routing-plan.md), or a hybrid number for each resource account that you want to be directly dialable from external phone numbers. - - The service number may be a toll or toll-free number. + - The service number may also be a toll or toll-free number. - Web click-to-call: - [Contact centers with Azure Communication Services](/azure/communication-services/tutorials/contact-center) - [Quickstart: Join your calling app to a Teams auto attendant](/azure/communication-services/quickstarts/voice-video-calling/get-started-teams-auto-attendant) @@ -106,28 +106,24 @@ When using a resource account for calling line ID purposes in Call queues, the r - An [online voice routing policy](manage-voice-routing-policies.md). - Phone number assignment is optional when using Direct Routing. -When an Auto attendant or Call queue is transferring calls to an external number, specific resource accounts as outlined below must have a Teams Phone Resource Account license and one of the following assigned: +When an Auto attendant or Call queue is transferring calls to an external number, the resource account must have a Teams Phone Resource Account license and one of the following assigned: - A [Calling Plan](calling-plans-for-office-365.md) license and a phone number assigned. - An [Operator Connect](operator-connect-plan.md) phone number assigned. - An [online voice routing policy](manage-voice-routing-policies.md). - Phone number assignment is optional when using Direct Routing. -Which resource account to license: - -- All resource accounts must have a free [Microsoft Teams Phone Resource Account license](teams-add-on-licensing/virtual-user.md). -- License the resource account on the first Auto attendant receiving the call when that Auto attendant transfers to other Auto attendants or Call queues that transfer calls externally. -- In all other calling scenarios, license the resource account of the Auto attendant or Call queue performing the external transfer. +Nested auto attendants and call queues that transfer calls externally don't require resource accounts or respective licensing. When nesting auto attendants or call queues, license the resource account on the first auto attendant or call queue receiving the call. > [!NOTE] > If the Calling Plan assigned to the resource account becomes disabled or is removed, [Communications Credits](what-are-communications-credits.md), if available in the tenant (without being assigned to the resource account), will be consumed. If there is no Calling Plan or Communications Credits, the call will fail. > > Direct Routing service numbers for Auto attendant and Call queues are supported for Microsoft Teams users and call agents only. -> +> > Transfers between Calling Plan, Operator Connect, and Direct Routing trunks aren't supported. -> +> > In a Hybrid scenario, the resource account must be created on-premises. For more information, see [Plan Cloud call queues](/skypeforbusiness/hybrid/plan-call-queue). -> +> > New Commerce Experience customers are not yet supported for resources accounts when an auto attendant or call queue needs to transfer calls to an external number. ## Business decisions diff --git a/Teams/plan-meetings-external-participants.md b/Teams/plan-meetings-external-participants.md index 30d6101683..cf22cea4d1 100644 --- a/Teams/plan-meetings-external-participants.md +++ b/Teams/plan-meetings-external-participants.md @@ -77,11 +77,11 @@ Cross-cloud meetings are supported as follows: |Meet with:|Commercial|GCC|GCC High|DoD|China| |:---------|:--------:|:-:|:------:|:-:|:---:| -|Commercial| |✔️|✔️ |✔️ |✔️ | -|GCC |✔️ | |✔️ |✔️ |✔️ | -|GCC High |✔️ |✔️| |✔️ | | -|DoD |✔️ |✔️|✔️ | | | -|China |✔️ |✔️| | | | +|Commercial| |![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) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|GCC |![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) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|GCC High |![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) | | +|DoD |![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) | | | +|China |![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png)| | | | [Meet with people in other Microsoft 365 clouds](cross-cloud-meetings.md) diff --git a/Teams/plan-meetings.md b/Teams/plan-meetings.md index 6c120ae9b5..1dcd5fd5db 100644 --- a/Teams/plan-meetings.md +++ b/Teams/plan-meetings.md @@ -1,7 +1,7 @@ --- title: Plan for Teams meetings ms.reviewer: bryanyce -ms.date: 11/13/2023 +ms.date: 10/25/2024 ms.topic: article ms.author: wlibebe author: wlibebe @@ -28,25 +28,16 @@ description: Learn how to plan for meetings in Microsoft Teams. # Plan for Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls -This article, designed for admins, introduces types of meetings, features and functionality, and provides links to more information. The following sections are included in this article: - -- [Meetings](#meetings) -- [Audio Conferencing for meetings](#audio-conferencing-for-meetings) -- [Guests and external participants](#meeting-options-for-guests-and-external-participants) -- [Attendee limits and streaming options](#attendee-limits-and-streaming-options) -- [Recordings](#recordings) -- [Compliance features](#compliance-features) -- [Apps for meetings](#apps-for-meetings) -- [Admin and meeting organizer meeting options](#admin-and-meeting-organizer-meeting-options) +This article, designed for admins, introduces types of meetings, features and functionality, and provides links to more information. > [!NOTE] > While meetings with registration are no longer supported, you and your users can use webinars. To learn more about setting up webinars for your org, see [Plan for Teams webinars](plan-webinars.md). Meetings with registration that were previously scheduled, or created with Graph API are still supported until December 31st, 2024. ## Meetings -Meetings in Teams include audio, video, and screen sharing capabilities for up to 1,000 people and view-only capabilities for participants over 1,000. +Meetings in Teams include audio, video, and screen sharing capabilities for up to around 1,000 people. If you turn on the view-only experience for your organizers, view-only capabilities start when around 900 participants join the meeting. Participants can be users in your organization, or if you allow it, people outside your organization. Meeting organizers can control which features are available in a given meeting. You as the administrator, can control the availability and default value for many of these features by using [meeting policies](#meeting-policies). @@ -66,6 +57,10 @@ Teams administrators and organizers have different policies and settings to cont For a complete list of meeting policies, see [Teams setting and policies reference](settings-policies-reference.md). +## Customization with Teams Premium + +With a Teams Premium license, you can extend your organization's visual identity and compliance requirements across the meeting experience by adding logos and backgrounds that can be displayed in the meeting’s pre-join screen, lobby, and during the meeting experience. To learn more, see [Custom meetings overview](custom-meetings-overview.md). + ## Audio Conferencing for meetings You can assign an Audio Conferencing license to meeting organizers so they can create meetings where attendees can join by dialing in from their phones. These meeting organizers can also dial-out to attendees to connect them to the meeting's audio portion. To learn more about Audio Conferencing, see [Audio Conferencing in Microsoft Teams](audio-conferencing-in-office-365.md). @@ -94,9 +89,9 @@ People from other trusted Microsoft 365 organizations can attend meetings withou ## Attendee limits and streaming options -Up to 10,000 attendees can join a Teams meeting, however, after 1,000 users enter a meeting, extra attendees will join with a view-only experience. View-only attendees don't have access to the meeting chat or be able to share content or video. +Up to 10,000 attendees can join a Teams meeting, however, after around 900 users enter a meeting, extra attendees join with a view-only experience. View-only attendees don't have access to the meeting chat or be able to share content or video. -You can allow or prevent the view-only experience for meetings with more than 1,000 attendees. If you disable the view-only experience, meeting attendance is limited to the first 1,000 attendees. +You can allow or prevent the view-only experience for meetings with more than 900 attendees. If you turn off the view-only experience, meeting attendance is limited to the first 1,000 attendees. For more information about the view-only meeting experience, see [Teams view-only meeting experience](view-only-meeting-experience.md). @@ -130,31 +125,50 @@ Teams admins and organizers have different policies and settings to control the |Feature|Admins|Organizers| |:------|:-----|:---------| +|[Anonymous participants](anonymous-users-in-meetings.md)|Manage how anonymous attendees access Teams meetings in your org.|No control | |[Attendance and engagement reports](/microsoftteams/teams-analytics-and-reports/meeting-attendance-report)|Can enforce on or off or allow organizer to choose.|Can turn on or off if allowed by admin.| |[Audio and video](meeting-policies-audio-and-video.md)|Can set audio and video modes and network settings.|Can allow or prevent attendee mic and cameras.| +|[Breakout rooms](https://support.microsoft.com/office/use-breakout-rooms-in-microsoft-teams-meetings-7de1f48a-da07-466c-a5ab-4ebace28e461)|No control|Can create and manage breakout rooms.| +|[CART captions](https://support.microsoft.com/office/use-cart-captions-in-a-microsoft-teams-meeting-human-generated-captions-2dd889e8-32a8-4582-98b8-6c96cf14eb47)|No control|Can set up and offer Communication access real-time translation(CART) captioning to participants instead of the Microsoft Teams built-in live captions that are automatically generated.| +|[Channel meeting scheduling](https://support.microsoft.com/office/schedule-a-meeting-in-microsoft-teams-943507a9-8583-4c58-b5d2-8ec8265e04e5)|No control|Can schedule meetings from channels.| |[Chat](manage-meeting-chat.md)|Can manage whether users in the org can read and write chat messages. You can also manage chat messages in Teams meetings hosted by other organizations that you don’t have a trusted relationship with.|Can manage whether chat is available for their meetings.| +|[Choose co-organizers](https://support.microsoft.com/office/schedule-a-meeting-in-microsoft-teams-943507a9-8583-4c58-b5d2-8ec8265e04e5)|No control|Can assign different meeting roles in a Teams meeting to give users specific permissions.| |[Collaboration features](meeting-policies-content-sharing.md)|Can control the availability of PowerPoint Live, whiteboard, and shared notes.|No control| +|[Compliance recording](teams-recording-policy.md)|Can implement an admin policy for automatic recording.|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.| +|[Convenience recording](meeting-recording.md)|Can allow or prevent meeting recording and set recording expiration time.|If the admin enables recording, organizers can manage who can record (Teams Premium) and automatic recording.| +|[Custom backgrounds (Teams Premium)](custom-meeting-backgrounds.md)|Can upload images for your users to display in the background of their video feed during meetings.|Can use backgrounds the admin uploaded.| +|[Decorate my background (Teams Premium)](https://adoption.microsoft.com/microsoft-teams-premium/decorate-your-background/)|No control|Organizers and participants can use AI to decorate their backgrounds.| +|[eCDN for view-only meetings](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 view-only meeting organizers with a Premium license and switch to a partner eCDN provider.| No control| |[End-to-end encryption (Teams Premium)](end-to-end-encrypted-meetings.md) |Can allow or prevent end-to-end encryption.|Can enforce end-to-end encryption if allowed by the admin.| -|[Feedback surveys for anonymous participants](meeting-surveys-anonymous-participants.md)| Manage whether anonymous participants who join meetings hosted in your org can rate their meeting experience through surveys. |No control.| -|[Green room](https://support.microsoft.com/office/5b744652-789f-42da-ad56-78a68e8460d5)|No control.|Can choose if green room is used for a meeting.| +|[Feedback surveys for anonymous participants](meeting-surveys-anonymous-participants.md)| Manage whether anonymous participants who join meetings hosted in your org can rate their meeting experience through surveys. |No control| +|[Green room](https://support.microsoft.com/office/5b744652-789f-42da-ad56-78a68e8460d5)|No control|Can choose if green room is used for a meeting.| |[Hide attendee names (Teams Premium)](hide-attendee-names.md) |Can control whether organizers with a Premium license can hide the names and photos of attendees from other attendees in the stage, roster, and chat. | Can hide attendee names during meetings to protect identities and privacy. | -|[Limit presenter role permissions](presenter-role-reduction.md) |Can limit presenter role permissions for the tenant. |No control.| +|[Intelligent meeting recap (Teams Premium)](/microsoftteams/privacy/intelligent-recap) | Give your users a more personalized rundown of their meetings with intelligent meeting recap.|No control| +|[Join verification check](join-verification-check.md) | Can require human verification checks for anonymous users to join meetings in your org.|No control| +|[Language interpretation](https://support.microsoft.com/office/use-language-interpretation-in-microsoft-teams-meetings-b9fdde0f-1896-48ba-8540-efc99f5f4b2e) |No control |Can enable language interpretation settings for a meeting, add interpreters before the meeting, and designate interpreters during the meeting.| +|[Limit presenter role permissions](presenter-role-reduction.md) |Can limit presenter role permissions for the tenant. |No control| |[Live translated transcription (Teams Premium)](meeting-transcription-captions.md) |Can control whether organizers with a Premium license can have live translated transcription for their meetings. |Can enable live translated transcription for themselves; attendees can always turn on live translated transcription. | -|[Manage what attendees see (Teams Premium)](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)|No control.|Can decide whose avatars or video feeds to spotlight during the town hall.| +|[Manage what attendees see (Teams Premium)](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)|No control|Can decide whose avatars or video feeds to spotlight during the town hall.| +|[Manage who can present and request control](meeting-who-present-request-control.md) |Control who can present in meetings and whether participants and external participants can request control of the presentation.|Can manage who can present in their meeting options.| |[Meeting join and lobby](who-can-bypass-meeting-lobby.md)|Can set the defaults for new meetings.|Can choose meeting join and lobby settings for each meeting.| +|[Meeting themes (Teams Premium)](meeting-themes.md)|Can define meeting themes, including colors, images, and logo.|Can turn the admin-defined theme on or off.| |[Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md)|Can control the default values and enforce specific values for Microsoft 365 Copilot in Teams meetings and events in organizers’ meeting options.|Can control whether Microsoft 365 Copilot in Teams meetings and events is used **Only during the meeting**, **During and after the meeting**, or **Off**. Attendees can use Copilot if they have a Copilot Microsoft 365 Copilot license.| -|[Prevent users from joining external meetings](external-meeting-join.md)|Can control which types of Microsoft Teams meetings your users can join.|No control.| -|[Prevent users from sharing content in external meetings (Teams Premium)](block-external-content-share.md)|Can control which types of external Microsoft Teams meetings your users share content in.|No control.| +|[Prevent copying or forwarding of chat (Teams Premium)](manage-chat-sensitive-meetings.md#prevent-copying-or-forwarding-of-chat)|Can prevent copying or forwarding of chat contents by using a meeting template or sensitivity label.|Can manage options if admin doesn't lock label or template settings. | +|[Prevent users from joining external meetings](external-meeting-join.md)|Can control which types of Microsoft Teams meetings your users can join.|No control| +|[Prevent users from sharing content in external meetings (Teams Premium)](block-external-content-share.md)|Can control which types of external Microsoft Teams meetings your users share content in.|No control| |[Q&A](manage-qna-for-teams.md)|Can manage if organizers can use Q&A in meetings.|Can decide if Q&A is available for their meetings if allowed by admins.| +|[Quality of service (QoS)](meetings-real-time-media-traffic.md)|Can prioritize real-time network traffic that's sensitive to network delays over traffic that's less sensitive.|No control| |[Reactions](manage-reactions-meetings.md)| Manage whether reactions can be used in meetings created by organizers with this policy. |Can control whether reactions can be used in their meetings. | -|[Recording](meeting-recording.md)|Can allow or prevent meeting recording and set recording expiration time.|If the admin enables recording, organizers can set who can record (Teams Premium) and automatic recording.| -|[Registration](set-up-meeting-registration.md)|Can allow or prevent meeting registration.|Can require meeting registration if allowed by admin.| +|[Recording storage and permissions](manage-reactions-meetings.md)| Manage recording storage and permissions. |Permissions depend on admin settings. | +|[Real time telemetry](use-real-time-telemetry-to-troubleshoot-poor-meeting-quality.md)|Can look at your users’ scheduled meetings and see audio, video, content sharing, and network-related issues. You can use this telemetry to investigate these issues during meetings and troubleshoot in real time.|No control| +|[Restrict who can record (Teams Premium)](manage-meeting-recording-options.md#manage-who-can-record-and-transcribe-meetings)| Can restrict which users can record by using a meeting template or sensitivity label. |Can manage options if admin doesn't lock label or template settings. | |[RTMP-In (Teams Premium)](meetings-rtmp-in.md)|Can control whether organizers can use RTMP-In for their meetings. |Can produce their Teams meetings directly from an external hardware or software-based encoder to integrate different types of media. To start streaming from the encoder, organizers can choose RTMP-In from their meeting options and then access the RTMP link and key. | |[Scheduling](manage-who-can-schedule-meetings.md)|Can define who can schedule private and channel meetings.|Can schedule meetings if allowed by admin.| -|[Meeting Theme (Teams Premium)](meeting-themes.md)|Can define meeting themes, including colors, images, and logo.|Can turn the admin-defined theme on or off.| +|[Sensitivity labels](manage-who-can-schedule-meetings.md)|Can create sensitivity labels for Teams meetings.|Can apply your sensitivity label to meeting invites from Outlook or Teams. Recipients in your organization see the sensitivity label and all recipients see any headers or footers as configured content markings. Optionally, the meeting invite can be encrypted so only authorized people can see it and access the meeting link. Usage rights can further restrict access, for example, preventing the invite from being forwarded.| +|[Speaker Coach](meeting-speaker-coach.md)|Manage whether users in your organization can use Speaker Coach during meetings and events.|No control- all participants can use Speaker Coach if the admin allows.| |[Transcription and captions](meeting-transcription-captions.md)|Can allow or prevent transcription and closed captions for attendees.|Can enable captions.| -|[View-only](view-only-meeting-experience.md)|Allow organizers to host large meetings where after the meeting reaches capacity at 1,000 users, additional attendees join with a view-only experience.|No control.| +|[View-only](view-only-meeting-experience.md)|Allow organizers to host large meetings where after the meeting reaches around 900 users, additional attendees join with a view-only experience.|No control| |[Voice isolation](voice-isolation.md)|Can control whether users can use voice isolation in meetings and calls.|Can enable voice isolation.| |[Watermarks (Teams Premium)](watermark-meeting-content-video.md)|Can allow or prevent watermarks for attendee video and shared content|Can enforce watermarks if allowed by the admin| diff --git a/Teams/plan-town-halls.md b/Teams/plan-town-halls.md index 9233d8e3f2..35097679c9 100644 --- a/Teams/plan-town-halls.md +++ b/Teams/plan-town-halls.md @@ -27,7 +27,7 @@ description: Learn what is a town hall in Microsoft Teams. Understand how to pla --- # Plan for Teams town halls -**APPLIES TO:** ✖️Meetings ✖️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls Town halls are meant for one-to-many communications where the presenters, organizers, and co-organizers lead the presentation. The audience participation is primarily to view and react to the content being shared. As an admin, this article guides you through how to plan and prepare for town halls in your organization. @@ -105,58 +105,59 @@ If you've been using live events for your organization, you might want to unders |Capability|Live Events|Town halls|Premium town halls| |:------| :---: | :---: | :---: | -|Ability to not send emails and calendar invites to attendees|✔️|*In development*|*In development*| -|AI generated captions|✔️|✔️|✔️| -|Attendee reporting|✔️| ✔️|✔️| +|Ability to not send emails and calendar invites to attendees|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|AI generated captions|![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)| +|Attendee reporting|![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)| |Broadcast capacity|10k|10k|- 20k
*- 100k In development*| +|Chat for attendees|![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)| |Concurrent events|15|15|50| -|Control when event invites are sent|✔️|*In development*|*In development*| +|Control when event invites are sent|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| |Co-organizer capacity|N/A|10|10| -|CVI support|✔️|*In development*|*In development*| -|Default audio and video off|✔️|✔️|✔️| -|Download translated transcripts|✔️|*In development*|*In development*| +|CVI support|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Default audio and video off|![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)| +|Download translated transcripts|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| |Duration|Four hours|30 hours|30 hours| |eCDN|Microsoft and partner providers|Microsoft and partner providers|Microsoft and partner providers| -|DVR|✔️|*In development*|*In development*| -|Dynamics 365 integration|✔️|*In development*|*In development*| -|Email editing|✖️|✖️|✔️| -|End event for attendees and return presenters to green room|✔️|*In development*|*In development*| -|Essential emails|✖️|✔️|✔️| -|External presenters|✔️|✔️|✔️| -|Green room|✔️|✔️|✔️| -|Join as attendee for presenters and organizers|✔️|*In development*|*In development*| +|DVR|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Dynamics 365 integration|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Email editing|![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)| +|End event for attendees and return presenters to green room|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Essential emails|![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 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)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Green room|![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)| +|Join as attendee for presenters and organizers|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| |Layouts|Single Video, Video + Content​​|Dynamic focused curated view|Dynamic focused curated view| -|Live translated captions|✔️|Six languages|10 languages| -|Manage the types of events your organizers can create|✔️|*In development*|*In development*| -|Manage what attendees see|✖️|✔️|✔️| -|Manage whether events in your org can be recorded|✔️|*In development*|*In development*| -|Manage whether events in your org can be transcribed|✔️|*In development*|*In development*| -|Microsoft town hall insights|✖️|✖️|✔️| -|Modern group support|✔️|✔️|✔️| -|MTR (Windows) support for presenters and attendees|✔️|*In development*|*In development*| -|Nudge attendees to join|✔️|*In development*|*In development*| +|Live translated captions|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|Six languages|10 languages| +|Manage the types of events your organizers can create|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Manage what attendees see|![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 checkmark for yes](/office/media/icons/success-teams.png)| +|Manage whether events in your org can be recorded|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Manage whether events in your org can be transcribed|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Microsoft town hall insights|![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)| +|Modern group support|![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)| +|MTR (Windows) support for presenters and attendees|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Nudge attendees to join|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| |Presenter capacity (including external presenters)|100|100|100| -|Presenters can dial in|✔️|*In development*|*In development*| -|Preview shared content in managed mode|✔️|*In development*|*In development*| -|Producer role|✔️|*In development*|*In development*| -|Producer UX|✔️ |Manage what attendees see|Manage what attendees see| -|Q&A: attendees can filter questions|✔️|✔️|✔️| +|Presenters can dial in|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Preview shared content in managed mode|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Producer role|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Producer UX|![Image of a checkmark for yes](/office/media/icons/success-teams.png) |Manage what attendees see|Manage what attendees see| +|Q&A: attendees can filter questions|![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)| |Q&A capacity|10k|10k|20k| -|Q&A: delete and archive questions|✔️|✔️|✔️| -|Q&A: moderator default and hide real names|✔️|*In development*|*In development*| -|Q&A: organizers can make presenters moderators|✔️|*In development*|*In development*| -|Q&A: organizers can privately reply to a question|✔️|*In development*|*In development*| -|Q&A: question export to CSV|✔️|✔️|✔️| -|Q&A: vote on and sort questions|✔️|*In development*|*In development*| -|Queue and preview content and presenters|✔️|*In development*|*In development*| -|RTMP-In|✔️|✔️|✔️| -|RTMP-In Transcription|✔️|*In development*|*In development*| -|Separate invites for presenters and attendees|✔️|*In development*|*In development*| -|Sharepoint embedded scheduling|✔️|*In development*|*In development*| -|Usage reports|✔️|✔️|✔️| -|VDI support|✔️|*In development*|*In development*| -|Viva Engage integration|✔️|*In development*|*In development*| -|VOD|✔️|✔️|✔️| +|Q&A: delete and archive questions|![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)| +|Q&A: moderator default and hide real names|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Q&A: organizers can make presenters moderators|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Q&A: organizers can privately reply to a question|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Q&A: question export to CSV|![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)| +|Q&A: vote on and sort questions|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Queue and preview content and presenters|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|RTMP-In|![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)| +|RTMP-In Transcription|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Separate invites for presenters and attendees|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Sharepoint embedded scheduling|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Usage 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)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|VDI support|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|Viva Engage integration|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|*In development*|*In development*| +|VOD|![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)| For more information on Teams Premium, see [Teams Premium licensing](/microsoftteams/teams-add-on-licensing/licensing-enhance-teams). @@ -168,11 +169,12 @@ Teams admins and organizers have different policies and settings to control the |:------|:-----|:---------| |[Attendance and engagement reports](/microsoftteams/teams-analytics-and-reports/meeting-attendance-report)|Can enforce on or off or allow organizer to choose.|Can turn on or off if allowed by admin.| |[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 chat during town halls.| +|[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.| -|[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|Can manage and configure the availability of eCDN for organizers. Admins can also disable the Microsoft eCDN for town hall organizers with a Premium license and switch to a partner eCDN provider.| No control.| +|[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.| +|[Event chat (Teams Premium)](town-hall-chat.md)|Can manage whether town hall organizers with a Teams Premium license can turn on event chat for their attendees.|Can use chat during town halls if the organizer's settings and admin's policy allows it.| |[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 town hall.| |[Limit presenter role permissions](presenter-role-reduction.md) |Can limit presenter role permissions for the tenant. |No control.| |[Live translated captions](meeting-transcription-captions.md) |Can control whether organizers with a Premium license can have live translated captions for their town halls. |Organizers can select six languages, or ten if they have a Premium license for attendees to use when translating captions during the town hall.| diff --git a/Teams/plan-webinars.md b/Teams/plan-webinars.md index e30916061c..98747de40d 100644 --- a/Teams/plan-webinars.md +++ b/Teams/plan-webinars.md @@ -28,7 +28,7 @@ description: Learn how to plan for webinars in Microsoft Teams. # Plan for Teams webinars -**APPLIES TO:** ✖️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls A webinar is a two-way interactive virtual event where the presenters deliver information to attendees. This format provides extra control for an organizer over the conversation and participants. Common scenarios for webinars might include trainings, product demos, sales lead generation, customer events, company announcements, and showcasing products. Webinars can accommodate up to 1,000 attendees and allow organizers to gather registration data from attendees before the event. @@ -52,17 +52,17 @@ There are a few key differences between in-org and public webinars. When managin |Capability|In-org webinar|Public webinar| |:----|:-----:|:-------:| -|Includes guests|✖️|✔️| -|Accessible to members of the organization that created the webinar|✔️|✔️| -|Accessible to anyone with a registration link|✖️|✔️| -|Anonymous users can register|✖️|✔️| -|Attendees type their name on the registration form when registering|✖️|✔️| -|Attendees must reenter their information after selecting the join link|✖️|✔️| -|Attendees have unique join links|✔️|✔️| -|Organizers can decide if attendees with a registration link can bypass the lobby|✔️|✔️| -|Organizers can decide if anyone who can't bypass the lobby is automatically rejected|✔️|✔️| -|Attendees can dial in to join|✖️|✖️| -|Includes external presenters|✔️|✔️| +|Includes guests|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Accessible to members of the organization that created the webinar|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Accessible to anyone with a registration link|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Anonymous users can register|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Attendees type their name on the registration form when registering|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Attendees must reenter their information after selecting the join link|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Attendees have unique join links|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Organizers can decide if attendees with a registration link can bypass the lobby|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Organizers can decide if anyone who can't bypass the lobby is automatically rejected|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Attendees can dial in to join|![Image of a x for no](/office/media/icons/cancel-teams.png)|![Image of a x for no](/office/media/icons/cancel-teams.png)| +|Includes 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)| ## Webinar attendee interaction @@ -81,24 +81,24 @@ A Teams Premium subscription includes the following features for webinars: |Feature name | Webinar features | Teams Premium webinar features | |-------------------------------------------------------|:---------------------:|:-------------------------:| -|Allow registered users to bypass the lobby |✔️ |✔️ | -|Assign a co-organizer |✔️ |✔️ | -|Limit the number of people who can register |✔️ |✔️ | -|Require attendees to register|✔️|✔️| -|Set up a green room for webinar presenters |✔️|✔️ | -|Turn on Q&A for webinars with up to 1,000 attendees |✔️ |✔️| -|View attendance reports|✔️|✔️| -|External presenters|✔️|✔️| -|Create a webinar wait list | |✔️ | -|Limit the day and time when people can register | |✔️ | -|Manage attendees’ view | |✔️ | -|Manually approve registrants | |✔️ | -|Send reminder emails to registrants | |✔️ | -|Use RTMP-In for webinars | |✔️ | -|Hide attendee names | |✔️ | -|Manage what attendees see | |✔️ | -|Custom meeting templates | |✔️ | -|Admin created custom meeting backgrounds | |✔️ | +|Allow registered users to bypass the lobby |![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Assign a co-organizer |![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Limit the number of people who can register |![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Require attendees to register|![Image of a checkmark for yes](/office/media/icons/success-teams.png)|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Set up a green room for webinar 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) | +|Turn on Q&A for webinars with up to 1,000 attendees |![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)| +|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) | +|Manually approve registrants | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Send reminder emails to registrants | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Use RTMP-In for webinars | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Hide attendee names | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Manage what attendees see | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Custom meeting templates | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Admin created custom meeting backgrounds | |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ## Webinar control comparison @@ -115,6 +115,7 @@ Teams admins and organizers have different policies and settings to control the |[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.| |[Hide attendee names (Teams Premium)](hide-attendee-names.md) |Can control whether organizers with a Premium license can hide the names and photos of attendees from other attendees in the stage, roster, and chat. | Can hide attendee names during webinars to protect identities and privacy. | +|[Join verification check](join-verification-check.md) | Can require human verification checks for anonymous users to join webinars in your org.|No control| |[Limit presenter role permissions](presenter-role-reduction.md) |Can limit presenter role permissions for the tenant. |No control.| |[Live translated transcription (Teams Premium)](meeting-transcription-captions.md) |Can control whether organizers with a Premium license can have live translated transcription for their webinars. |Can enable live translated transcription for themselves; attendees can always turn on live translated transcription. | |[Manage what attendees see (Teams Premium)](https://support.microsoft.com/office/manage-what-attendees-see-in-teams-meetings-19bfd690-8122-49f4-bc04-c2c5f69b4e16)|No control|Can decide whose avatars or video feeds to spotlight during a Teams meeting. Others are hidden from view.| diff --git a/Teams/predefined-meeting-template-reference.md b/Teams/predefined-meeting-template-reference.md index 1c6e790e2c..d9ed5d91a1 100644 --- a/Teams/predefined-meeting-template-reference.md +++ b/Teams/predefined-meeting-template-reference.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: janineco -ms.date: 12/08/2023 +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -24,9 +24,9 @@ description: See a list of Microsoft Teams meeting templates and their settings. [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The following predefined meeting templates are available in Teams. You can determine which of these templates are available to your users by using [meeting template policies](manage-meeting-templates.md). +The following predefined meeting templates are available in Teams. You can determine which of these templates are available to your users by using [meeting template policies](manage-meeting-templates.md). -If your organization has Teams Premium, you can edit these templates (if noted below) or [create your own meeting templates](create-custom-meeting-template.md). You can also configure Teams Premium settings in editable templates and meeting organizers with a Teams Premium license can use those settings in their meetings. +If your organization has Teams Premium, you can edit these templates (indicated in the Lock status column) or [create your own meeting templates](create-custom-meeting-template.md). You can also configure Teams Premium settings in editable templates and meeting organizers with a Teams Premium license can use those settings in their meetings. ## Virtual appointment @@ -48,13 +48,13 @@ The Virtual appointment meeting template comes with the following options. You c |***Recording and transcription***|||| |Record meetings automatically|Off|Visible|Unlocked| |Who can record meetings|Only organizers and co-organizers|Visible|Unlocked| -|Copilot|On with transcript|Visible|Unlocked| +|Allow Copilot|During and after the meeting|Visible|Unlocked| |***Roles***|||| |Announce when people dialing in join and leave|Off|Visible|Unlocked| |***Meeting engagement***|||| |Allow meeting chat|On during the meeting only|Visible|Unlocked| |Allow reactions|Off|Visible|Unlocked| -|Enable Q&A|Off|Visible|Unlocked| +|Q&A|Off|Visible|Unlocked| |Manage what attendees see|Off|Visible|Unlocked| To learn more, see [Manage the Virtual appointment meeting template in Teams](virtual-appointment-meeting-template.md). @@ -79,19 +79,17 @@ The controlled-content meeting template comes with the following options. You ca |***Recording and transcription***|||| |Record meetings automatically|Off|Visible|Unlocked| |Who can record meetings|Only organizers and co-organizers|Visible|Unlocked| -|Copilot|On with transcript|Visible|Unlocked| +|Allow Copilot|During and after the meeting|Visible|Unlocked| |***Roles***|||| |Announce when people dialing in join and leave|Off|Visible|Unlocked| |***Meeting engagement***|||| |Allow meeting chat|On|Visible|Unlocked| |Allow reactions|Off|Visible|Unlocked| -|Enable Q&A|Off|Visible|Unlocked| +|Q&A|Off|Visible|Unlocked| |Manage what attendees see|Off|Visible|Unlocked| ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) diff --git a/Teams/prepare-my-users-email-templates.md b/Teams/prepare-my-users-email-templates.md index a40c903466..8f3efe21c1 100644 --- a/Teams/prepare-my-users-email-templates.md +++ b/Teams/prepare-my-users-email-templates.md @@ -1,7 +1,7 @@ --- title: User notification email templates for online phone system rollout -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 03/31/2018 ms.topic: article diff --git a/Teams/presence-admins.md b/Teams/presence-admins.md index df38e788c6..dc2144089c 100644 --- a/Teams/presence-admins.md +++ b/Teams/presence-admins.md @@ -65,17 +65,15 @@ The order of statuses, from most available to least available, is: > [!NOTE] > For users that have their mailbox hosted on-prem, presence delays of one hour (maximum) are expected. -## Automatic status settings and user experience +## Automatic status settings + +Normally, a user's status is based on user activity (whether they're **Available** or **Away**); on the state of the Teams app (e.g. whether they're **In a call** or **Presenting**); and on their Outlook calendar (e.g. whether they're **In a meeting**). + +A user who isn't logged in to Teams on any device is **Offline**. Otherwise, their presence depends on whether they're logged in on a computer or on a mobile device: +* On a computer, a user's presence becomes **Away** automatically if they're inactive for a few minutes or if the computer is locked; and it becomes Offline when the computer enters sleep mode. +* On a mobile device, a user's presence becomes Away whenever the Teams app is in the background, and then becomes **Offline** after 24 hours of inactivity. -App-configured presence states are based on user activity (Available, Away), Outlook calendar states (In a meeting), or Teams app states (In a call, Presenting). When you're in focus mode based on your calendar, **Focusing** is the state people see in Teams. Focus mode displays as **Do not disturb** in other products. - -Your current presence state changes to Away when you lock your computer or when your computer enters idle or sleep mode. On a mobile device, your presence status changes to Away whenever the Teams app is in the background. - -Users receive all chat messages sent to them in Teams regardless of their presence state. If a user is offline when someone sends them a message, the chat message appears in Teams the next time the user is online. If a user state is set to Do not disturb, the user still receives chat messages, but banner notifications aren't displayed. - -Users receive calls in all presence states except for Do not disturb, in which incoming calls go to voicemail. If the recipient blocked the caller, the call won't be delivered and the caller sees the recipient's presence as Offline. - -Users can add people to their priority access list by going to **Settings** > **Privacy** in Teams. People who have priority access can contact the user even when the user's status is set to Do not disturb. +If a user is logged in to Teams on two or more devices (e.g. on both a desktop computer and on a phone), then the device where they were active most recently determines their presence. For example, if a user is logged in on both a computer and a mobile device, and they're currently working on the computer, their presence will come from the computer. When they disconnect on the computer, their presence will then come from the status of the mobile device. Call queues can use presence to route calls to agents. For more information, see [Create a Call Queue in Microsoft Teams](create-a-phone-system-call-queue.md). @@ -93,6 +91,14 @@ Users can set a duration for the presence that they set manually. If a user does - For 1 day if it's **Busy** or **Do not disturb** - For 7 days if it's any other status +## Notifications and Do not disturb + +Users receive all chat messages regardless of their presence. If a user is offline when someone sends them a message, the chat message appears in Teams the next time they come online. If a user is in a **Do not disturb** state, they still receive chat messages, but banner notifications aren't displayed. + +Users receive calls in all presence states except for Do not disturb, in which case incoming calls go to voicemail. + +Users can add people to a priority access list by going to **Settings > Privacy** in Teams. If they do, messages from these people will caused banner notifications to be displayed as normal for that user even if the user is in a Do not disturb state, and the user will still receive calls from these people. + ## Admin settings in Teams compared to Skype for Business The following admin settings Skype for Business are different in Teams: diff --git a/Teams/presenter-role-reduction.md b/Teams/presenter-role-reduction.md index 5b3aaa4cb1..a2c58063d2 100644 --- a/Teams/presenter-role-reduction.md +++ b/Teams/presenter-role-reduction.md @@ -26,7 +26,7 @@ description: Learn how to limit presenter role permissions and capabilities in y # Limit presenter role permissions for your org -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls In Microsoft Teams, presenters have responsibilities related to presenting, sharing content and collaborating within the meeting or event. Presenters can mute attendees, change roles within the meeting, manage the lobby, and more. diff --git a/Teams/privacy/teams-privacy-oce-overview.md b/Teams/privacy/teams-privacy-oce-overview.md index 06dc6ed418..701a6fe817 100644 --- a/Teams/privacy/teams-privacy-oce-overview.md +++ b/Teams/privacy/teams-privacy-oce-overview.md @@ -10,54 +10,58 @@ ms.collection: - M365-collaboration - privacy-teams ms.reviewer: -ms.date: 10/04/2023 +ms.date: 10/18/2024 ms.localizationpriority: high search.appverid: MET150 -description: This article outlines the optional connected experiences you'll see in Microsoft Teams. +description: This article outlines the optional connected experiences you see in Microsoft Teams. appliesto: - Microsoft Teams --- # Overview of optional connected experiences in Microsoft Teams -If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as **optional connected experiences**) while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Online Service Terms](https://www.microsoft.com/licensing/product-licensing/products), as described separately for each optional service. This article lists our Teams cloud-backed services. +If you have a work or school account, your organization's admin may have provided you with the ability to use one or more cloud-backed services (also referred to as "optional connected experiences") while using Microsoft Teams, like GIPHY and/or URL Preview service. These cloud-backed services are optional. Whether you use them is up to you. They're offered to you under terms that differ from the [Microsoft Product Terms](https://www.microsoft.com/licensing/docs/view/Product-Terms), as described separately for each optional service. This article lists our Teams cloud-backed services. If your admin has given you the ability to use optional connected experiences in Teams, you can go to **Settings** > **Privacy** in Teams and choose whether you want to use optional connected experiences. > [!NOTE] -> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using the [Office cloud policy service](/deployoffice/overview-office-cloud-policy-service) and configuring the *Allow the use of additional optional connected experiences in Office* policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in the Office apps (such as Word, Excel, and PowerPoint) that come with Microsoft 365 Apps for enterprise. +> If you're an admin, you can give or restrict your users' ability to use optional connected experiences. You can do this by using [Cloud Policy service for Microsoft 365](/microsoft-365-apps/admin-center/overview-cloud-policy) and configuring the **Allow the use of additional optional connected experiences in Office** policy setting. This is the same policy setting that controls whether optional connected experiences are available to your users in Microsoft 365 Apps, such as Word, Excel, and PowerPoint. ## GIPHY -GIPHY is a cloud-backed service that lets you use GIFs in your Teams chats. If you're in **Teams** > **GIF** > **Search**, the search terms are sent to GIPHY. These experiences, if allowed by your admin and after you choose to use them, are subject to the [GIPHY Privacy Policy](https://support.giphy.com/hc/articles/360032872931-GIPHY-Privacy-Policy) and [Terms of Service](https://support.giphy.com/hc/articles/360020027752-GIPHY-User-Terms-of-Service). +GIPHY is a cloud-backed service that lets you use GIFs in your Teams chats. If you're in **Teams** > **GIF** > **Search**, the search terms are sent to GIPHY. These experiences, if allowed by your admin and after you choose to use them, are subject to the [GIPHY Privacy Policy](https://support.giphy.com/hc/articles/360032872931-GIPHY-Privacy-Policy) and the [GIPHY User Terms of Service](https://support.giphy.com/hc/articles/360020027752-GIPHY-User-Terms-of-Service). ## Ratings and reviews for Teams apps -Ratings and reviews allow Teams users to provide feedback about their experience with using a Teams app. Reviews are anonymous unless the user chooses otherwise. All Teams users can view these ratings and reviews on the details page for the app. Users are only allowed to provide ratings and reviews for apps they’ve installed and only for apps that are publicly available from Microsoft or other companies. The ratings are powered by Microsoft AppSource and are shown on the app’s page on the [AppSource website](https://appsource.microsoft.com/). AppSource is provided under the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement) and the [Microsoft Commercial Marketplace Terms of Use](/legal/marketplace/marketplace-terms). +Ratings and reviews allow Teams users to provide feedback about their experience with using a Teams app. Reviews are anonymous unless the user chooses otherwise. All Teams users can view these ratings and reviews on the details page for the app. Users are only allowed to provide ratings and reviews for apps they’ve installed and only for apps that are publicly available from Microsoft or other companies. The ratings are powered by Microsoft AppSource and are shown on the app’s page on the [AppSource website](https://appsource.microsoft.com/). AppSource is provided under the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement) and the [Microsoft Commercial Marketplace Terms of Use](/legal/marketplace/marketplace-terms). ## Search Coach Tab App -The Search Coach Teams tab app available in Microsoft EDU Class Teams makes search requests to Bing search through the Bing API when a user sends a query, returning ad-free SafeSearch results. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [privacy statement](https://privacy.microsoft.com/privacystatement). +The Search Coach Teams tab app available in Microsoft EDU Class Teams makes search requests to Bing search through the Bing API when a user sends a query, returning ad-free SafeSearch results. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). ## Teams apps link previews -The Teams app link previews service generates a preview snippet of the app's adaptive card and attaches it under the URL when a user sends a URL string that maps to the app in the Teams store. If the URLP setting is turned on, this service will make a request to the service URL as the user is typing the message to unfurl a card preview. Tenant admin and user settings for apps would be honored. +The Teams app link previews service generates a preview snippet of the app's adaptive card and attaches it under the URL when a user sends a URL string that maps to the app in the Teams store. If the URLP setting is turned on, this service makes a request to the service URL as the user is typing the message to unfurl a card preview. Tenant admin and user settings for apps would be honored. ## Teams device store checkout -Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the terms of service and privacy statement of UnifiedCommunications.com. +Teams device store is available in the Teams admin center and Teams App. It enables discovery and purchase of Teams certified devices. To enable checkout, the Teams device store shares basic user and company information, including user email address, user GUIDs, and tenant GUIDs, with UnifiedCommunications.com. This experience, if allowed by the **Allow the use of additional optional connected experiences in Office** policy setting, is subject to the [Terms of Service](https://new.unifiedcommunications.com/about/terms-of-service/) and [Privacy Policy](https://new.unifiedcommunications.com/about/privacy-policy/) of UnifiedCommunications.com. -To learn more about Teams device store, see [Purchase devices in the Teams device store](../devices/device-store.md). +To learn more about Teams device store, see [Purchase devices in the Microsoft Teams device store](../devices/device-store.md). ## URL Preview service -The URL Preview service automatically generates a preview snippet and attaches under the snippet the URL when a user sends a URL string. This service will make a request to the service URL as the user is typing the message. If the service URL doesn't have any schema.org data, it will send a request to Bing search to get the data it needs to generate the preview snippet. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [privacy statement](https://privacy.microsoft.com/privacystatement). Any URLs you provide to Microsoft Teams while using these services can be sent to Microsoft Bing, including Bing Content Validation Service for evaluation of harmful content. They aren't linked to you by the Bing organization. +The URL Preview service automatically generates a preview snippet and attaches under the snippet the URL when a user sends a URL string. This service makes a request to the service URL as the user is typing the message. If the service URL doesn't have any schema.org data, it sends a request to Bing search to get the data it needs to generate the preview snippet. Experiences that rely on Bing are licensed to you under the terms of the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement) and covered by the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Any URLs you provide to Microsoft Teams while using these services can be sent to Microsoft Bing, including Bing Content Validation Service for evaluation of harmful content. They aren't linked to you by the Bing organization. :::image type="content" source="../media/url-preview.png" alt-text="A screen showing a sample of a URL preview for the Microsoft home page in a text box."::: +## WebView2 + +WebView2 is a component that developers use to build their applications, and the developers can deploy a self-updating Evergreen WebView2 Runtime onto user devices to power their applications. WebView2 collects its own telemetry to help them maintain and improve the WebView2 component. If the policy turned off, the diagnostic data collection from WebView2 will be disabled. + ## Related articles -- [Overview of policy controls for Teams](policy-control-overview.md) -- [Overview of optional connected experiences in Office](/deployoffice/privacy/optional-connected-experiences) -- [Required service data for Office](/deployoffice/privacy/required-service-data) -- [Account Privacy Settings](https://support.microsoft.com/office/3e7bc183-bf52-4fd0-8e6b-78978f7f121b) +- [Policy control overview for Microsoft Teams](policy-control-overview.md) +- [Overview of optional connected experiences in Office](/microsoft-365-apps/privacy/optional-connected-experiences) +- [Required service data for Office](/microsoft-365-apps/privacy/required-service-data) +- [Access your Account Privacy Settings](https://support.microsoft.com/office/3e7bc183-bf52-4fd0-8e6b-78978f7f121b) diff --git a/Teams/private-channels.md b/Teams/private-channels.md index 6fdd06d3e7..a5639ab6fa 100644 --- a/Teams/private-channels.md +++ b/Teams/private-channels.md @@ -1,10 +1,10 @@ --- title: IT Admins - Private channels in Microsoft Teams -author: MicrosoftHeidi -ms.author: heidip +author: DaniESmith +ms.author: danismith manager: jtremper ms.reviewer: jasonlewis -ms.date: 10/11/2023 +ms.date: 11/04/2024 ms.topic: article ms.service: msteams audience: Admin @@ -30,7 +30,7 @@ You can use a private channel to limit collaboration to specific individuals or For example, a private channel is useful in these scenarios: - A group of people in a team want a focused space to collaborate without having to create a separate team. -- A subset of people in a team wants a private channel to discuss sensitive information, such as budgets, resourcing, strategic positioning, and so on. +- A subset of people in a team wants a private channel to discuss projects and topics, such as budgets, resourcing, strategic positioning, and so on. A lock icon indicates a private channel. Only members of private channels can see and participate in private channels that they're added to. @@ -38,8 +38,6 @@ When a private channel is created, it's linked to the parent team and can't be m [Compare private channels with other types of channels](/microsoftteams/teams-channels-overview#channel-feature-comparison). -![Screenshot of private channels in a team.](media/private-channels-in-teams.png) - ## Private channel creation By default, any team owner or team member can create a private channel. Guests can't create them. The ability to create private channels can be managed at the team level and at the organization level. Use [policies](teams-policies.md) to control which users in your organization are allowed to create private channels. Once you've set the policies, team owners can turn off or turn on the ability for members to create private channels in the **Settings** tab for a team. @@ -64,8 +62,6 @@ Each private channel has its own settings that the channel owner can manage, inc The private channel owner can select **Manage channel**, and then use the **Members** and **Settings** tabs to add or remove members and edit settings. -![Screenshot of private channel settings.](media/private-channels-in-teams-channel-settings.png) - ## Private channel owner and member actions The following table outlines what actions owners, members, and guests can do in private channels. @@ -111,13 +107,13 @@ For more information about performing an eDiscovery search for private channel m [Sharing files and folders](https://support.microsoft.com/office/1fe37332-0f9a-4719-970e-d2578da4941c) in a private channel works the same as with other SharePoint sites. Users can share files and folders using sharable links based on the [sharing settings configured by the SharePoint Administrator](/sharepoint/turn-external-sharing-on-or-off). -Sharing a OneNote notebook in a private channel site is the same as sharing access to any other item. If a user is granted access to a notebook in a private channel through SharePoint, removing the user from the team or private channel doesn't remove the user's access to the notebook. If an existing notebook is added as a tab to a private channel, access to the private channel isn't changed and the notebook retains its existing permissions. +Sharing a OneNote notebook in a private channel site is the same as sharing access to any other item. If a user is granted access to a notebook in a private channel through SharePoint, removing the user from the team or private channel doesn't remove the user's access to the notebook. If an existing notebook is added as a tab to a private channel, access to the private channel isn't changed, and the notebook retains its existing permissions. ## Private channel limitations Private channels don't support connectors and tabs in Stream, Planner, Tasks by Planner and To Do, and Forms. -Each team can have a maximum of 30 private channels and each private channel can have a maximum of 250 members. The 30 private channel limit is in addition to the 200 standard channel limit per team. +Each team can have a maximum of 30 private channels, and each private channel can have a maximum of 250 members. The 30 private channel limit is in addition to the 200 standard channel limit per team. When you create a team from an existing team, any private channels in the existing team don't copy over. @@ -129,12 +125,8 @@ Channel meetings can't be scheduled. Channel calendars aren't available. ## Related articles -[Shared channels in Microsoft Teams](/MicrosoftTeams/shared-channels) - -[Overview of teams and channels in Teams](teams-channels-overview.md) - -[Teams PowerShell overview](teams-powershell-overview.md) - -[Use the Microsoft Graph API to work with Teams](/graph/api/resources/teams-api-overview) - -[Channel resource type](/graph/api/resources/channel) +- [Shared channels in Microsoft Teams](/MicrosoftTeams/shared-channels) +- [Overview of teams and channels in Teams](teams-channels-overview.md) +- [Teams PowerShell overview](teams-powershell-overview.md) +- [Use the Microsoft Graph API to work with Teams](/graph/api/resources/teams-api-overview) +- [Channel resource type](/graph/api/resources/channel) diff --git a/Teams/pstn-connectivity.md b/Teams/pstn-connectivity.md index b07f615e5a..95bc0bd5e8 100644 --- a/Teams/pstn-connectivity.md +++ b/Teams/pstn-connectivity.md @@ -1,7 +1,7 @@ --- title: PSTN connectivity options -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 08/10/2023 ms.topic: article @@ -15,7 +15,7 @@ ms.collection: - m365solution-scenario - highpri - Tier1 -ms.reviewer: crowe +ms.reviewer: scottfrancis f1.keywords: - CSH ms.custom: diff --git a/Teams/quality-of-experience-review-guide.md b/Teams/quality-of-experience-review-guide.md index 5bb9296f0d..3eb9d2afed 100644 --- a/Teams/quality-of-experience-review-guide.md +++ b/Teams/quality-of-experience-review-guide.md @@ -1,7 +1,7 @@ --- title: Use CQD to manage call and meeting quality in Microsoft Teams -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: article ms.service: msteams diff --git a/Teams/remote-learning-edu.md b/Teams/remote-learning-edu.md index f9ed253ef3..8d72741302 100644 --- a/Teams/remote-learning-edu.md +++ b/Teams/remote-learning-edu.md @@ -161,8 +161,8 @@ This approach allows you to either use SDS to create groups for each class (reco After class groups are prepared, educators can convert their groups into teams: -1. Select the Teams tab in Teams. -2. At the top of the client, select the **Suggested classes** icon. +1. Select the **Chat** tab in Teams. +2. At the top of the Teams client, select the **Suggested classes** icon. #### Benefits of educator-led team creation diff --git a/Teams/retention-policies.md b/Teams/retention-policies.md index cf5e59a376..d0c44b4b57 100644 --- a/Teams/retention-policies.md +++ b/Teams/retention-policies.md @@ -82,17 +82,9 @@ Data can be stored in the form of screenshots in an end users's local drive thro ## End-user experience -For private chats (1:1 chats) or group chats, users will see that chats older than the retention policy configuration are deleted and an automatically generated message stating "We've deleted older messages due to your org's retention policy" is shown on top of yet undeleted messages. For example: +For private chats (1:1 chats) or group chats, users will see that chats older than the retention policy configuration are deleted and an automatically generated message stating "We've deleted older messages due to your org's retention policy" is shown on top of yet undeleted messages. -:::image type="content" source="media/retention-policies-image1.png" alt-text="User informed in Teams that chat message are deleted because of a Teams retention policy."::: - -:::image type="content" source="media/retention-policies-image2.png" alt-text="User in Teams explaining messages are deleted as a result of a Teams retention policy."::: - -For Channel messages, users (channel members) will see the deleted messages disappear from view after messages expire. If the deleted message was a parent message of a threaded conversation, then, in place of parent message, a message stating "This message has been deleted because of a Retention Policy" will be displayed. For example: - -:::image type="content" source="media/retention-policies-image3.png" alt-text="Screenshot of channel before retention."::: - -:::image type="content" source="media/retention-policies-image4.png" alt-text="Screenshot of channel after retention."::: +For Channel messages, users (channel members) will see the deleted messages disappear from view after messages expire. If the deleted message was a parent message of a threaded conversation, then, in place of parent message, a message stating "This message has been deleted because of a Retention Policy" will be displayed. > [!NOTE] > The displayed messages that users see as a result of deleted messages are not configurable at this time. diff --git a/Teams/rooms/admin-center-license-overview.md b/Teams/rooms/admin-center-license-overview.md deleted file mode 100644 index fa89ad81ae..0000000000 --- a/Teams/rooms/admin-center-license-overview.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Microsoft Teams Rooms license overview in Teams admin center -author: mstonysmith -ms.author: tonysmit -manager: pamgreen -ms.reviewer: ayerragangu -ms.date: 09/13/2024 -ms.topic: article -ms.service: msteams -ms.subservice: itpro-rooms -audience: Admin -appliesto: - - Microsoft Teams -ms.collection: - - teams-rooms-devices - - Teams_ITAdmin_Devices - - Tier1 -search.appverid: MET150 -ms.localizationpriority: medium -f1.keywords: - - NOCSH -ms.custom: - - Licensing - - LIL_Placement - - seo-marvel-apr2020 -description: Learn about and compare Teams Rooms licensing and feature availability in Teams admin center. ---- - -# Microsoft Teams Rooms license overview in Teams admin center - -The Teams admin center lets you view and manage Teams Rooms devices and their peripherals from a central location. This article shows you [what management capabilities](#comparison-of-teams-rooms-feature-availability-by-license) you have, depending on whether a Teams Rooms device is assigned a Microsoft Teams Rooms Basic or Microsoft Teams Rooms Pro license. - -For more information about Microsoft Teams Rooms licenses, see [Microsoft Teams Rooms licenses](rooms-licensing.md). - -> [!NOTE] -> If you have existing Teams Rooms Standard or Teams Rooms Premium legacy licenses, you'll need to switch to Teams Rooms Pro when your legacy licenses expire. If you have an Enterprise Agreement, you'll need to switch to Teams Rooms Pro licenses at your next renewal period. For more information, see [Switching from Teams Rooms Standard and Teams Rooms Premium](rooms-licensing.md#switching-from-teams-rooms-standard-and-teams-rooms-premium). - -[!INCLUDE [mtr-user-licensing](../includes/mtr-user-licensing.md)] - -## See which licenses are assigned to Teams Rooms devices - -You can see what license your devices have by going to Teams devices in the Teams admin center, and then selecting the device category (Teams Rooms on Windows, Teams Rooms on Android, and Surface Hubs) you want to see. For example, if you select **Teams devices** > **Teams Rooms on Windows**, you'll see something similar to the following image. The **License** column shows the Teams Rooms license assigned to each device. - -:::image type="content" source="../media/mtr-device-inventory-license-focus.png" alt-text="Teams Rooms inventory list with focus on Standard, Pro, and Pro (Trial) licenses."::: - -To quickly filter the device inventory for one or more licenses, you can use the filter tool on each device category page. Using the **Filter** drop down menu (highlighted in yellow in the following image), select **License**, and then select the appropriate operator and license values to create the filtered inventory list. - -:::image type="content" source="../media/mtr-device-inventory-license-filter.png" alt-text="Teams Rooms inventory list with focus the filter menu option."::: - -Devices that have the **Pro** license can access all the features of the Teams admin center. Devices with other licenses can access a subset of those features. You can see which features are available to each license in [Comparison of Teams Rooms feature availability by license](#comparison-of-teams-rooms-feature-availability-by-license). - -> [!IMPORTANT] -> If you select multiple devices that include both Microsoft Teams Rooms Basic and Microsoft Teams Rooms Pro licenses, actions that require a Microsoft Teams Rooms Pro license will be performed only on devices that have been assigned that license. The action won't be performed on devices assigned the Microsoft Teams Rooms Basic license. - -## See which features require a Microsoft Teams Rooms Pro license - -Features that require a Microsoft Teams Rooms Pro license can be identified by looking for the :::image type="icon" source="../media/mtr-pro-icon.png" border="false"::: icon on a device's details page. If the device that's currently selected isn't assigned a Microsoft Teams Rooms Pro license, you won't be able to perform the action and will see a prompt to upgrade. - -:::image type="content" source="../media/mtr-restart-device-dialog.png" alt-text="Teams Rooms device restart dialog showing Pro icon."::: - -## Comparison of Teams Rooms feature availability by license - -The following table shows the management capabilities available in the Teams admin center for each Microsoft Teams Rooms license. - -| | Microsoft Teams Rooms Basic | Microsoft Teams Rooms Pro | -|:----------------------------------------------|:---------------------------:|:-------------------------:| -| **Automatic device updates** | ✔ | ✔ | -| **Basic device analytics** | ✔ | ✔ | -| **Basic device health** | ✔ | ✔ | -| **Call quality dashboard** | ✔ | ✔ | -| **Create and view workspaces** | ✔ | ✔ | -| **Real-time telemetry** | ✔ | ✔ | -| **Regular feature updates** | ✔ | ✔ | -| **Remote sign-in and sign-out** | ✔ | ✔ | -| **Android device configurations** | | ✔ | -| **Device alerts** | | ✔ | -| **Device analytics - health and utilization** | | ✔ | -| **Device detail view** | | ✔ | -| **Device health details** | | ✔ | -| **Device tags** | | ✔ | -| **Graph APIs** | | ✔ | -| **Remote restart** | | ✔ | -| **Windows device peripherals management** | | ✔ | -| **Windows device settings** | | ✔ | diff --git a/Teams/rooms/bring-your-own-device.md b/Teams/rooms/bring-your-own-device.md index 0727effcf4..67e8b4aa8b 100644 --- a/Teams/rooms/bring-your-own-device.md +++ b/Teams/rooms/bring-your-own-device.md @@ -40,6 +40,7 @@ There are two main tabs under **Inventory**: **Rooms** and **Devices**. ### Rooms view :::image type="content" source="../media/byod/inventory-rooms-tab.png" alt-text="Screenshot of Inventory rooms tab." lightbox="../media/byod/inventory-rooms-tab.png"::: + This page provides a comprehensive summary of your rooms, featuring the following key insights: - The total number of rooms in your tenant categorized by type (Microsoft Teams Rooms, Bring Your Own Device). @@ -51,7 +52,7 @@ This page provides a comprehensive summary of your rooms, featuring the followin The following table describes the columns in the **Rooms** view of Inventory. - | **Column** | **Description** | + | Column | Description | | --- | --- | | Display name | Name of the room | | Capacity | Illustrate the room's capacity number | @@ -75,7 +76,7 @@ When you select a specific room, you'll see a new pane with two different pages, - **The Inventory page** displays detailed information about the room's devices: - | **Column** | **Description** | + | Column | Description | | --- | --- | | Name | Name of the device | | Type | Type of device (for example, Microsoft Teams Rooms, TeamsPanel, camera.) | @@ -94,7 +95,7 @@ Select the device to view more details.
In the **Device group details** panel that opens up, a table displays all the devices in the group, allowing you to associate them with the specific room at once. -| **Column** | **Description** | +| Column | Description | | --- | --- | | Device display name | Name of the device | | Device type | The category of the device (for example, panel, speaker) | @@ -116,27 +117,35 @@ To associate a device with a room, the following two methods are available: - **Use Import/Export function:** You can use this function to export the inventory list via an Excel file and construct Bring Your Own Device rooms. - 1. In the **Devices** page, click **Export** to download the device inventory. - 2. Open the Excel file and verify that it contains all the devices and room information. - 3. In the Excel file, select the **PERIPHERALS** tab and fill out the Account or Display Name column for the devices listed. - 4. Save the file after associating the device with the specific room information. - 5. Go back to the Inventory Devices page and click **Import** to upload the modified file. - 6. Verify that the device-room association is updated successfully. + 1. In the **Devices** page, click **Export** to download the device inventory. + 2. Open the Excel file and verify that it contains all the devices and room information. + 3. In the Excel file, select the **PERIPHERALS** tab and fill out the Account or Display Name column for the devices listed. + 4. Save the file after associating the device with the specific room information. + 5. Go back to the Inventory Devices page and click **Import** to upload the modified file. + 6. Verify that the device-room association is updated successfully. - > [!NOTE] - > In cases where the devices were not discovered or reported by Pro Management portal, admins can add those new devices using the import function. Device information such as the Product ID, Vendor ID, Serial Number, and Account information are required for the association to be done. + > [!NOTE] + > In cases where the devices were not discovered or reported by Pro Management portal, admins can add those new devices using the import function. Device information such as the Product ID, Vendor ID, Serial Number, and Account information are required for the association to be done. - **Manually associate discovered devices using Pro Management UI:** - 1. Go to the device table. - 1. Select the specific device group with the **Need Action** banner. - 1. Click **Add a room to this device**. - 1. Select the desired room from the list to associate the devices with. - 1. Click **Save**. + 1. Go to the device table. + 1. Select the specific device group with the **Need Action** banner. + 1. Click **Add a room to this device**. + 1. Select the desired room from the list to associate the devices with. + 1. Click **Save**. :::image type="content" source="../media/byod/device-discovery.png" alt-text="Screenshot of device room association." lightbox="../media/byod/device-discovery.png"::: -## Devices automatically discovered by the Pro Management Portal +### Using the PowerShell script to collect peripheral information + +To ensure seamless end-to-end user experience, peripherals such as audio-video bars located in rooms need to be associated or linked to a room account. To do this, you need to identify peripherals based on unique information such as product ID, vendor ID, and serial number. + +You can use a custom script to get peripheral details from rooms to locate peripherals correctly and ensure they're mapped to the corresponding room resource account. The PowerShell script located [here](https://www.microsoft.com/en-us/download/details.aspx?id=106063) must be run with administrator permissions. + +For detailed step-by-step instructions, see [Get information for connected peripherals](../rooms/get-peripheral-information.md). After uploading information on peripherals, use the Teams Pro Management portal to confirm if they are associated to the correct rooms. + +## Peripherals automatically discovered by the Pro Management Portal Devices are automatically discovered using your users' Teams client to send device data to Pro Management Portal. When a user enters the prejoin screen of a meeting, any connected displays and USB audio/video peripherals are scanned and transmitted to the cloud. These devices populate your Devices tab within the Inventory navigation. @@ -144,12 +153,17 @@ At launch, only displays are supported, but USB audio/video peripherals will fol Be aware that Microsoft can't guarantee that devices provide unique data like serial numbers, and this may cause errors or overcounting of usage. We recommend working with your OEM partners to ensure that their devices are providing unique serial numbers to the operating system via the USB descriptor or EDID. -## Bring Your Own Device Usage Report +### Enabling automatic work location updates + +You have the option to [enable the automatic work location update policy](/powershell/module/teams/new-csteamsworklocationdetectionpolicy) for your organization or for a group of users. Automatic work location updates are designed to enhance the end user experience by making it easier to keep their work location up-to-date and connect with others when they are in the office. With the policy enabled, users will have the option to enable automatic work location updates. They can do so in Teams desktop client under **Settings** > **Privacy** > **Sharing your work location**. After users have opted-in, their work location will automatically update to **In the office** when they connect to a BYOD room, provided their work location was previously set to unknown or remote. The detected location will last until the end of their working hours. If they plug in after work hours, the location will be set until 11:59pm that day. This feature allows for a seamless transition between remote and in-office work, which enhances collaboration and communication within your team and other users. + +## Bring Your Own Device Usage Report > [!IMPORTANT] > A Teams Shared Device license is required to unlock the Bring Your Own Device room usage report. For more information about the Teams Shared Device, see [Microsoft Teams Shared Devices licensing - Microsoft Teams | Microsoft Learn](../teams-add-on-licensing/teams-shared-device-license.md). To view the Usage report for your Bring Your Own Device rooms: + 1. In the left navigation menu, select **Reports**. 1. In the Reports page, select the **BYOD Usage** tab. @@ -169,7 +183,7 @@ To view the Usage report for your Bring Your Own Device rooms: Below the headline metrics, there's a table that provides a granular breakdown of individual Bring Your Own Device rooms, accompanied by specific metrics that illuminate each room’s usage and performance during the period selected. - | **Column** | **Description** | + | Column | Description | |---|---| | **Display room name** | The designated name of the Bring Your Own Device room | | **Room Type** | Will show as “Bring Your Own Device Room” as room type | @@ -183,7 +197,8 @@ To see the call utilization view for each room, select the specific Bring Your O > [!NOTE] > Only rooms with Teams Shared Devices or Pro licenses and which are associated with their peripherals are shown in the Bring Your Own Device usage report. -> > Great news! for this first release, customers can utilize the Bring Your Own Device usage data without an additional Teams shared device license until April 8th, 2024. +> +> Great news! for this first release, customers can utilize the Bring Your Own Device usage data without an additional Teams shared device license until April 8th, 2024. ## Settings @@ -196,7 +211,7 @@ The Teams BYOD solution uses peripheral data crowdsourced from the Teams client > [!WARNING] > Disabling this policy setting for certain users will cause BYOD and desk usage information to cease flowing to the service. The Teams BYOD and Desk solution requires peripheral data sent from users to calculate usage reports for peripherals, BYOD rooms, and desks. -``` +```powershell Get-CsTeamsBYODAndDesksPolicy New-CsTeamsBYODAndDesksPolicy -Identity "Test" Set-CsTeamsBYODAndDesksPolicy -Identity "Test" -DeviceDataCollection Disabled diff --git a/Teams/rooms/certified-hardware.md b/Teams/rooms/certified-hardware.md index 032de4cae3..a214392536 100644 --- a/Teams/rooms/certified-hardware.md +++ b/Teams/rooms/certified-hardware.md @@ -95,7 +95,7 @@ The following devices are Certified under the Microsoft Teams Rooms on Windows C | [Dell OptiPlex 7000 with Logitech TAP](https://www.dell.com/en-us/lp/logitechvideoconferencing?ref=cptl_logitech-store-at-dell---4_cta_primary_shopgoogleteamsorzoombundles#All-in-one-Room-Solutions) | Core i7 | 16 GB | 256 GB | | [HP Elite Slice for Meeting Rooms G2](https://www.hp.com/us-en/desktops/business/elite-slice.html) | Core i5 | 8 GB | 128 GB | | [HP Elite Slice G2 Audio Ready with Microsoft Teams Rooms](https://www.hp.com/us-en/desktops/business/elite-slice/microsoft-teams-rooms.html) | Core i5 | 8 GB | 128 GB | -| [HP Slice Partner Ready with Logitech TAP]( https://www.logitech.com/video-collaboration/partners/hp.html) | Core i5 | 8 GB | 128 GB | +| [HP Slice Partner Ready with Logitech TAP](https://www.logitech.com/video-collaboration/partners/hp.html) | Core i5 | 8 GB | 128 GB | | [HP Presence Small Space Solution with Microsoft Teams Rooms](https://www.hp.com/us-en/solutions/presence.html) | Core i5/i7 | 8 GB/16 GB | 256 GB | | [HP Presence Small Space Solution Plus AI Camera with Microsoft Teams Rooms](https://www.hp.com/us-en/solutions/presence.html) | Core i5/i7 | 8 GB/16 GB | 256 GB | | [Lenovo ThinkSmart Hub Gen 2](https://www.lenovo.com/us/en/p/smart-devices/smart-office/thinksmart/thinksmart-hub-60/11sp1tshb60) | Core i5 | 16 GB | 128 GB | @@ -103,6 +103,7 @@ The following devices are Certified under the Microsoft Teams Rooms on Windows C | [Lenovo ThinkSmart One + Controller](https://www.lenovo.com/us/en/p/smart-devices/smart-office/thinksmart/thinksmart-one-plus-controller-for-teams/len102e0006) | Core i5 | 16 GB | 256 GB | | [Lenovo ThinkSmart Core + IP Controller](https://www.lenovo.com/us/en/p/smart-devices/smart-office/thinksmart/lenovo-thinksmart-core-plus-ip-controller-for-microsoft-teams-rooms/len102e0015) | Core i5 | 16 GB | 256 GB | | [Lenovo ThinkSmart One + IP Controller](https://www.lenovo.com/us/en/p/smart-devices/smart-office/thinksmart/lenovo-thinksmart-one-plus-ip-controller-for-teams/12bw0002us) | Core i5 | 16 GB | 256 GB | +|[Lenovo Telluride/ThinkSmart Tiny Kit](https://psref.lenovo.com/Product/ThinkSmart/ThinkSmart_Tiny_Kit)| Core i3|16 GB|256 GB| | [Logitech Tap with Intel NUC](https://www.logitech.com/product/microsoft-rooms) | Core i5 | 8 GB | 128 GB | | Logitech Tap and Intel Tiger Canyon NUC PC | Core i5 | 8 GB | 128 GB | | Logitech TAP Console with Lenovo Core Compute | Core i5 | 8 GB | 128 GB | @@ -140,6 +141,7 @@ The following devices are Certified under the Microsoft Teams Rooms on Windows C | Yealink MVC320 | Core i5 | 8 GB | 128 GB | | Yealink MVC340 | Core i5 | 8 GB | 128 GB | | [Yealink MCore 3 Kit](https://www.yealink.com/en/product-detail/microsoft-teams-rooms-mvc640) | Core i5 | 8 GB | 128 GB | +| Yealink MCore Kit Lite | Core i3 | 8 GB | 128 GB | | Yealink MVC S40 | Core i5 | 8 GB | 128 GB | | [Yealink MVC S60](https://www.yealink.com/en/product-detail/microsoft-teams-rooms-mvcs60) | Core i5 | 8 GB | 128 GB | | [Yealink MVC S90](https://www.yealink.com/en/product-detail/microsoft-teams-rooms-mvcs90) | Core i5 | 8 GB | 128 GB | @@ -151,146 +153,149 @@ The following devices are certified under the Microsoft Teams Rooms peripherals | Microsoft Teams Rooms peripheral | Certified firmware version | Supports content camera | Intelligent camera | Spatial audio | Intelligent speaker | |:-|:-|:-|:-|:-|:-| -| [Aver VC520 Pro Camera + Speakerphone](https://www.averusa.com/products/conference-camera/vc520pro) | 1004.35 | | | -| [Aver VC520 PRO2 Conferencing System](https://www.averusa.com/products/conference-camera/vc520pro2) | 00.0.7200.79 | | | -| [Aver VC520 PRO3 Conferencing System](https://www.averusa.com/products/conference-camera/VC520pro3) | 0.0.9803.08 | | | -| Aver VB342+ Camera Soundbar | Soundbar: 0.0.0000.97 | | | -| [Aver VB342 pro Video bar](https://www.averusa.com/products/video-collaboration-bar/vb342pro) | 0.0.7800.61 | | | -| [Aver VB350 Video bar](https://communication.aver.com/model/vb350) | 0.0.8200.91 | | | -| [Aver CAM 540](https://www.averusa.com/products/conference-camera/cam540) | 0.0.6002.83 | | | -| [Aver CAM 550](https://www.averusa.com/products/conference-camera/cam550) | 0.0.8000.51 | | | -| [Aver CAM 570](https://www.averusa.com/products/conference-camera/cam570) | 0.0.8100.98 | | | -| [Aver CAM 520 Pro](https://www.averusa.com/products/conference-camera/cam520pro) | 0.0.1000.73 | | | -| [Aver CAM 520 Pro 2](https://www.averusa.com/products/conference-camera/cam520pro2) | 0.0.7200.3 | | | -| [Aver CAM 520 Pro 3](https://www.averusa.com/products/conference-camera/cam520pro3) | 0.0.9601.09 | | | -| [Aver CAM 130](https://www.averusa.com/products/conference-camera/cam130) | 0.0.7450.02 | ✔ | | -| [Aver Fone540](https://www.averusa.com/products/vc-accessories/fone540) | 0.0.7002.17 | | | -| Aver VB130 Camera Soundbar | 0.0.7300.71 | | | -| [Aver TR313V2 Camera](https://www.averusa.com/products/ptz-camera/tr313v2) | 0.3.0011.38 | | | -| [Audiocodes RXVCAM50L](https://www.audiocodes.com/solutions-products/products/room-experience-rx-suite/rxvcam50lm-video-camera) | 1.0.5 | | | -| [AudioCodes RXVCam10](https://www.audiocodes.com/solutions-products/products/room-experience-rx-suite/rxvcam10-cc-content-camera) | 1.0.6 | ✔ | | -| [Bose Video Bar VB1](https://pro.bose.com/en_us/products/conferencing/videobars/bose-videobar-vb1.html?mc=25_PS_VB_BO_00_BI_&&msclkid=fc99b79880f714727a63e86ea0e5642a&utm_source=bing&utm_medium=cpc&utm_campaign=US%20-%20Brand_Videobar%20VB1_Exact&utm_term=bose%20videobar%20vb1&utm_content=Bose%20Videobar%20VB1&gclid=fc99b79880f714727a63e86ea0e5642a&gclsrc=3p.ds) | 19.2 | | | -| [Bose VB-S AV Bar](https://pro.bose.com/en_us/products/conferencing/videobars/bose-videobar-vb-s.html) | 1.1.2 | | | -| [Biamp Vidi 250 camera](https://support.biamp.com/Vidi/Cameras/Vidi_250_overview) | 1.1.1 | | | -| [Biamp :::no-loc text="Devio"::: SCR-20CX Web-Based Conferencing Hub with Ceiling Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) | 2.2.0.9 | | | -| [Biamp :::no-loc text="Devio"::: SCR-20TX Web-Based Conferencing Hub with Tabletop Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) | 2.2.0.9 | | | -| [Biamp Parlé VBC 2500 & Parlé VBC 2500a Conferencing Video Bars](https://www.biamp.com/products/product-families/parle/conferencing-bars) | 1.3.0 | | | -| [Biamp Parlé ABC 2500 & Parlé ABC 2500a Conferencing Audio Bars](https://www.biamp.com/products/product-families/parle/conferencing-bars) | 1.3.0 | | | -| [:::no-loc text="Crestron Huddly"::: IQ](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Accessories/CCS-CAM-USB-F-400) | 1.02.09.33901 | | | -| Crestron 1Beyond- Crestron Automate VX Plus: [Automate VX Plus (IV-SAM-VXN-1B)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-SAM-VXN-1B), [INOGENI (SDI2USB3) converter](https://inogeni.com/product/sdi2usb3/), [AutoTracker (IV-CAMA3-20) presenter tracking camera](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAMA3-20-N-W-1B), [Optical PTZ (IV-CAMPTZ) camera](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAMPTZ-12-W-1B) | Automate VX Plus: Version 5.11.8580.20169
INOGENI SDI2USB3: Version 8.39
IV-CAMA30: Version 5.1.82
IV-CAMPTZ: Version 3.1.20 | | | -| [Crestron 1 Beyond p20 PTZ camera (IV-CAM-P20)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-P20-B) | 1.0.19 | | | -| [Crestron 1 Beyond p12 PTZ camera (IV-CAM-P12)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-P12-B) | 1.0.19 | | | -| [Crestron 1 Beyond i20 PTZ camera (IV-CAM-I20)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-I20-B) | 1.0.22 | | | -| [Crestron 1 Beyond i12 PTZ camera (IV-CAM-I12)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-I12-B) | 1.0.22 | | | -| [Crestron Flex Hub](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Conferencing-Audio/UC-AUDIO-HUB-DR1) + [Crestron Flex Pods](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Conferencing-Audio/UC-AUDIO-POD-B-DR1) | 1.13.0113 | | | -| HP Presence See Camera | 1.0.23.0 | | | -| [:::no-loc text="Huddly"::: Canvas](https://www.huddly.com/conference-cameras/canvas/) | 1.3.25 | ✔ | | -| [Huddly Crew AI-directed multi-camera system](https://www.huddly.com/conference-cameras/crew/) | 1.5.19 | | | -| [:::no-loc text="Huddly"::: IQ](https://www.huddly.com/conference-cameras/iq/) | 1.3.22 | | | -| [:::no-loc text="Huddly"::: IQ Lite](https://www.huddly.com/conference-cameras/iq/) | 1.3.29 | | | -| [:::no-loc text="Huddly"::: IQ Camera](https://www.huddly.com/conference-cameras/iq/) | 1.3.27 | | | -| [:::no-loc text="Huddly"::: L1](https://www.huddly.com/conference-cameras/l1/) | 1.2.9 | | | -| :::no-loc text="Huddly"::: L1 Camera with [Crestron UC-C100-T MTR](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Integrator-Kits/UC-C100-T) kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-C100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | | -| :::no-loc text="Huddly"::: L1 Camera with [Crestron UC-CX100-T](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Integrator-Kits/UC-CX100-T) MTR-W Kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.9
Crestron UC-CX100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 1.00.20.246 or above | | | -| :::no-loc text="Huddly"::: L1 Camera with Crestron UC-M70-T MTR kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-M70-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | | -| :::no-loc text="Huddly"::: L1 Camera with Crestron UC-MX70-T MTR kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-MX70-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | | -| [:::no-loc text="Huddly"::: S1 camera](https://www.huddly.com/conference-cameras/s1/) | 1.4.0 | | | -| [:::no-loc text="Jabra Panacast3"::: Camera](https://www.jabra.com/business/video-conferencing/jabra-panacast) | 1.3.9.12 | | | +| [Aver VC520 Pro Camera + Speakerphone](https://www.averusa.com/products/conference-camera/vc520pro) | 1004.35 | | ||| +| [Aver VC520 PRO2 Conferencing System](https://www.averusa.com/products/conference-camera/vc520pro2) | 00.0.7200.79 | | ||| +| [Aver VC520 PRO3 Conferencing System](https://www.averusa.com/products/conference-camera/VC520pro3) | 0.0.9803.08 | | ||| +| Aver VB342+ Camera Soundbar | Soundbar: 0.0.0000.97 | | ||| +| [Aver VB342 pro Video bar](https://www.averusa.com/products/video-collaboration-bar/vb342pro) | 0.0.7800.61 | | ||| +| [Aver VB350 Video bar](https://communication.aver.com/model/vb350) | 0.0.8200.91 | | ||| +| [Aver CAM 540](https://www.averusa.com/products/conference-camera/cam540) | 0.0.6002.83 | | ||| +| [Aver CAM 550](https://www.averusa.com/products/conference-camera/cam550) | 0.0.8000.51 | | ||| +| [Aver CAM 570](https://www.averusa.com/products/conference-camera/cam570) | 0.0.8100.98 | | ||| +| [Aver CAM 520 Pro](https://www.averusa.com/products/conference-camera/cam520pro) | 0.0.1000.73 | | ||| +| [Aver CAM 520 Pro 2](https://www.averusa.com/products/conference-camera/cam520pro2) | 0.0.7200.3 | | ||| +| [Aver CAM 520 Pro 3](https://www.averusa.com/products/conference-camera/cam520pro3) | 0.0.9601.09 | | ||| +| [Aver CAM 130](https://www.averusa.com/products/conference-camera/cam130) | 0.0.7450.02 | ✔ | ||| +| [Aver Fone540](https://www.averusa.com/products/vc-accessories/fone540) | 0.0.7002.17 | | ||| +| Aver VB130 Camera Soundbar | 0.0.7300.71 | | ||| +| [Aver TR313V2 Camera](https://www.averusa.com/products/ptz-camera/tr313v2) | 0.3.0011.38 | | ||| +| [Audiocodes RXVCAM50L](https://www.audiocodes.com/solutions-products/products/room-experience-rx-suite/rxvcam50lm-video-camera) | 1.0.5 | | ||| +| [AudioCodes RXVCam10](https://www.audiocodes.com/solutions-products/products/room-experience-rx-suite/rxvcam10-cc-content-camera) | 1.0.6 | ✔ | ||| +| [Bose Video Bar VB1](https://pro.bose.com/en_us/products/conferencing/videobars/bose-videobar-vb1.html?mc=25_PS_VB_BO_00_BI_&&msclkid=fc99b79880f714727a63e86ea0e5642a&utm_source=bing&utm_medium=cpc&utm_campaign=US%20-%20Brand_Videobar%20VB1_Exact&utm_term=bose%20videobar%20vb1&utm_content=Bose%20Videobar%20VB1&gclid=fc99b79880f714727a63e86ea0e5642a&gclsrc=3p.ds) | 19.2 | | ||| +| [Bose VB-S AV Bar](https://pro.bose.com/en_us/products/conferencing/videobars/bose-videobar-vb-s.html) | 1.1.2 | | ||| +| [Biamp Vidi 250 camera](https://support.biamp.com/Vidi/Cameras/Vidi_250_overview) | 1.1.1 | | ||| +| [:::no-loc text="Devio"::: SCR-20CX Web-Based Conferencing Hub with Ceiling Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) [Biamp :::no-loc text="Devio"::: SCR-20CX Web-Based Conferencing Hub with Ceiling Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) | 2.2.0.9 | | ||| +| [:::no-loc text="Devio"::: SCR-20TX Web-Based Conferencing Hub with Tabletop Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) [Biamp :::no-loc text="Devio"::: SCR-20TX Web-Based Conferencing Hub with Tabletop Microphone](https://www.biamp.com/products/product-families/devio/huddle-room-solutions) | 2.2.0.9 | | ||| +| [Biamp Parlé VBC 2500 & Parlé VBC 2500a Conferencing Video Bars](https://www.biamp.com/products/product-families/parle/conferencing-bars) | 1.3.0 | | ||| +| [Biamp Parlé ABC 2500 & Parlé ABC 2500a Conferencing Audio Bars](https://www.biamp.com/products/product-families/parle/conferencing-bars) | 1.3.0 | | ||| +| [:::no-loc text="Crestron Huddly"::: IQ](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Accessories/CCS-CAM-USB-F-400) | 1.02.09.33901 | | ||| +| Crestron 1Beyond- Crestron Automate VX Plus: [Automate VX Plus (IV-SAM-VXN-1B)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-SAM-VXN-1B), [INOGENI (SDI2USB3) converter](https://inogeni.com/product/sdi2usb3/), [AutoTracker (IV-CAMA3-20) presenter tracking camera](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAMA3-20-N-W-1B), [Optical PTZ (IV-CAMPTZ) camera](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAMPTZ-12-W-1B) | Automate VX Plus: Version 5.11.8580.20169
INOGENI SDI2USB3: Version 8.39
IV-CAMA30: Version 5.1.82
IV-CAMPTZ: Version 3.1.20 | | ||| +| [Crestron 1 Beyond p20 PTZ camera (IV-CAM-P20)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-P20-B) | 1.0.19 | | ||| +| [Crestron 1 Beyond p12 PTZ camera (IV-CAM-P12)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-P12-B) | 1.0.19 | | ||| +| [Crestron 1 Beyond i20 PTZ camera (IV-CAM-I20)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-I20-B) | 1.0.22 | | ||| +| [Crestron 1 Beyond i12 PTZ camera (IV-CAM-I12)](https://www.crestron.com/Products/Workspace-Solutions/Intelligent-Video/1-Beyond-Intelligent-Video/IV-CAM-I12-B) | 1.0.22 | | ||| +| [Crestron Flex Hub](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Conferencing-Audio/UC-AUDIO-HUB-DR1) + [Crestron Flex Pods](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Conferencing-Audio/UC-AUDIO-POD-B-DR1) | 1.13.0113 | | ||| +| HP Presence See Camera | 1.0.23.0 | | ||| +| [:::no-loc text="Huddly"::: Canvas](https://www.huddly.com/conference-cameras/canvas/) | 1.3.25 | ✔ | ||| +| [Huddly Crew AI-directed multi-camera system](https://www.huddly.com/conference-cameras/crew/) | 1.5.19 | | ||| +| [:::no-loc text="Huddly"::: IQ](https://www.huddly.com/conference-cameras/iq/) | 1.3.22 | | ||| +| [:::no-loc text="Huddly"::: IQ Lite](https://www.huddly.com/conference-cameras/iq/) | 1.3.29 | | ||| +| [:::no-loc text="Huddly"::: IQ Camera](https://www.huddly.com/conference-cameras/iq/) | 1.3.27 | | ||| +| [:::no-loc text="Huddly"::: L1](https://www.huddly.com/conference-cameras/l1/) | 1.2.9 | | ||| +| :::no-loc text="Huddly"::: L1 Camera with [Crestron UC-C100-T MTR](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Integrator-Kits/UC-C100-T) kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-C100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | ||| +| :::no-loc text="Huddly"::: L1 Camera with [Crestron UC-CX100-T](https://www.crestron.com/Products/Workspace-Solutions/Unified-Communications/Crestron-Flex-Integrator-Kits/UC-CX100-T) MTR-W Kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.9
Crestron UC-CX100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 1.00.20.246 or above | | ||| +| :::no-loc text="Huddly"::: L1 Camera with Crestron UC-M70-T MTR kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-M70-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | ||| +| :::no-loc text="Huddly"::: L1 Camera with Crestron UC-MX70-T MTR kit | :::no-loc text="Huddly"::: L1 Camera: 1.2.1
Crestron UC-MX70-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 compute 1.0.20.246 or above | | ||| +| [:::no-loc text="Huddly"::: S1 camera](https://www.huddly.com/conference-cameras/s1/) | 1.4.0 | | ||| +| [:::no-loc text="Jabra Panacast3"::: Camera](https://www.jabra.com/business/video-conferencing/jabra-panacast) | 1.3.9.12 | | ||| | [:::no-loc text="Jabra Panacast"::: 50 Video Bar](https://www.jabra.com/business/video-conferencing/jabra-panacast-50) | 8.0.7 | ✔ | ✔ | | ✔ | -| [:::no-loc text="Jabra Speak2"::: 75](https://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak2-75) | 1.2.3 | | | -| [Lenovo ThinkSmart Cam Camera](https://www.lenovo.com/us/en/p/accessories-and-software/webcams-and-video/webcams-&-video_webcams/40cltscam1?orgRef=https%253A%252F%252Fwww.bing.com%252F) | 1.0.111.4 | | | -| [Lenovo ThinkSmart Bar](https://www.lenovo.com/us/en/virtual-reality-and-smart-devices/smart-collaboration/thinksmart/ThinkSmart-Bar/p/11SP1TSSDBR) | 0.9.3 | | | -| Lenovo ThinkSmart Bar Expand XL | 5.9.5 | | | -| Lenovo Thinksmart Bar 180 | 6.5.1 | ✔ | | | ✔ | -| [Logitech Brio](https://www.logitech.com/product/brio) | V2.2.50 | ✔ | | -| [Logitech 930e](https://www.logitech.com/product/c930e-webcam) | 8.0.914 | ✔ | | -| [Logitech Rally](https://www.logitech.com/product/rally-ultra-hd-conferencecam) | 1.2.4 | | | -| [Logitech Rally Bar](https://www.logitech.com/products/video-conferencing/room-solutions/rallybar.960-001308.html) | 10.3.82 | | | -| [Logitech Rally Bar](https://www.logitech.com/products/video-conferencing/room-solutions/rallybar.html) with [Mic Pods](https://www.logitech.com/products/video-conferencing/accessories/mic-pod-for-rally.html) | Logi CollabOS: 1.10.425
Mic pods: 2.1.4 | | | -| [Logitech Sight](https://www.logitech.com/products/video-conferencing/room-solutions/sight.960-001510.html) + [Rally Bar](https://www.logitech.com/en-us/products/video-conferencing/room-solutions/rallybar.960-001308.html) | Sight:
Logi CollabOS: 1.10.208 | | ✔ | -| [Logitech Rally Bar Mini](https://www.logitech.com/products/video-conferencing/room-solutions/rallybarmini.960-001336.html) | 10.5.880 | | | -| [Logitech Sight](https://www.logitech.com/products/video-conferencing/room-solutions/sight.960-001510.html) + [Rally Bar Mini](https://www.logitech.com/products/video-conferencing/room-solutions/rallybarmini.960-001336.html) | Sight:
Logi CollabOS: 1.10.208 | | ✔ | -| [Logitech Rally Bar Huddle](https://www.logitech.com/business/solutions/huddle-space.html) | Logi CollabOS: 1.10.277
System Image: 0.903.271
Audio: 0.2.67 | | | -| [Logitech MeetUp](https://www.logitech.com/product/meetup-conferencecam) | Audio — 1.0.172
Video — 1.0.156 | | | -| [Logitech MeetUp 2](https://www.logitech.com/products/video-conferencing/conference-cameras/meetup2.html) | Logi CollabOS: 1.13.77 | | | -| [Logitech ConferenceCam Connect](https://www.logitech.com/product/conferencecam-connect) | 1.1.248.0
1.1.684 | | | -| [Logitech Group](https://www.logitech.com/product/conferencecam-group) | 8.5.778 | | | -| Logitech PTZ Pro | 1.1.219 | | | -| [Logitech PTZ Pro 2](https://www.logitech.com/products/video-conferencing/conference-cameras/ptz-pro2-conferencecam.960-001184.html) | | | | -| [Logitech Scribe](https://www.logitech.com/products/video-conferencing/room-solutions/scribe.960-001332.html) | 1.1.1 | ✔ | | -| [MAXHUB UC S07 Videoconferencing Camera](https://www.maxhub.com/en/s07/) | Audio firmware version: V0.0.0.5476
Video firmware version: V100-20230726-175602 | | | -| MAXHUB UC W31 4K USB Camera | Video firmware version: 100-20230731-104934 | | | -| MAXHUB UC BM35 | 0.0.02457 | | | -| [Microsoft Surface Hub Smart Camera](https://www.microsoft.com/d/surface-hub-smart-camera/8n983ctks176) | FW: 1.8.1 | | | -| [Microsoft Surface Hub 2 Camera](https://www.microsoft.com/d/surface-hub-2-camera/8tzgfl7z18ph) | FW: 24.712.159 | | | -| [Nureva HDL300](https://www.nureva.com/audio-conferencing/hdl300) | 2.3.6 | | | -| [Nureva HDL310](https://www.nureva.com/audio-conferencing/hdl310) | 1.5.0.0 | | | -| [Nureva HDL410](https://www.nureva.com/audio-conferencing/hdl410) | 1.5.243554 | | | -| [Owl Labs Meeting Owl 3](https://owllabs.com/products/meeting-owl-3) | 6.4.10.42 | | | -| [Panasonic 360 degree camera speakerphone PressIT360](https://panasonic.net/cns/prodisplays/products/ty-csp1/) | 0.0.7904.54 | | | -| [Pansonic AW-UE4 camera](https://pro-av.panasonic.net/products/aw-ue4/) | 02.03 | | | -| [Poly Eagle Eye Cube Camera](https://www.polycom.com/products-services/hd-telepresence-video-conferencing/realpresence-accessories/eagleeye-cameras.html) | 1.2.0 | | | -| [Polycom EagleEye IV](https://www.poly.com/us/en/products/video-conferencing/eagleeye/eagleeye-iv) | 1.0.0 | | | -| [Polycom CX5100](https://www.polycom.com/products-services/products-for-microsoft/lync-optimized/cx5100-unified-conference-station.md) | 1.2.0.70232 | | | -| [Polycom Eagle Eye Director II](https://www.poly.com/us/en/products/video-conferencing/eagleeye/eagleeye-director-ii) | 2.1.0.10 | | | -| [Polycom Studio Soundbar](https://www.polycom.com/hd-video-conferencing/room-video-systems/polycom-studio.html) | 1.1.2.000570 | | | -| [Poly Sync 40](https://www.poly.com/us/en/products/phones/sync/sync-40) | 0.0.94.1461 | | | -| [Poly Sync 60](https://www.poly.com/us/en/products/phones/sync/sync-60) | 0.0.150.1671 | | | -| [Polycom Trio 8500 / 8800](https://www.polycom.com/voice-conferencing-solutions/conference-phones/trio.html) | 5.7.2.3205 | | | -| [Poly Trio C60](https://www.poly.com/us/en/products/phones/trio/trio-c60) | 5.9.5.3066 | | | -| [Poly Studio P15 Video Bar](https://www.poly.com/us/en/products/video-conferencing/studio-p/studio-p15) | 1.2.0.000287 | | | -| [Poly Studio E70 Camera](https://www.poly.com/us/en/products/video-conferencing/studio/studio-e70) | 1.1 | | | -| Poly Studio E60 Camera | 1.0.4.0 | | | -| [Poly Studio R30](https://www.poly.com/us/en/products/video-conferencing/studio/studio-r30) | 2.0.0.001096 | | | -| Poly Studio V52 | 1.0.1-400045 | | | -| [EPOS SP 220 MS](http://no-no.sennheiser.com/dual-speakerphones-sp-220-ms-uc) | 2.0.12.0 | | | -| [EPOS SP20](https://www.eposaudio.com/en/us/enterprise/products/sp-20-ml-142ee5ca-speakerphone-1000226) | 1.2.15 | | | -| [EPOS SP30](https://www.eposaudio.com/en/us/enterprise/products/sp-30-78c0cecc-bluetooth-speakerphone-1000223) | 2.1.52 | | | -| [EPOS SP30T](https://www.eposaudio.com/en/us/enterprise/products/sp-30t-b949fe9a-bluetooth-speakerphone-1000225) | 3.2.63 | | | -| [EPOS Expand 80T + 2 Extension Mics](https://www.eposaudio.com/en/us/enterprise/products/expand-80t-bluetooth-speakerphone-1000203) | Speakerphone — 4.6.55
Extension Mic — 0.2.314 | | | +| [:::no-loc text="Jabra Speak2"::: 75](https://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak2-75) | 1.3.4 | | ||| +| [Lenovo ThinkSmart Cam Camera](https://www.lenovo.com/us/en/p/accessories-and-software/webcams-and-video/webcams-&-video_webcams/40cltscam1?orgRef=https%253A%252F%252Fwww.bing.com%252F) | 1.0.111.4 | | ||| +| [Lenovo ThinkSmart Bar](https://www.lenovo.com/us/en/virtual-reality-and-smart-devices/smart-collaboration/thinksmart/ThinkSmart-Bar/p/11SP1TSSDBR) | 0.9.3 | | ||| +| Lenovo ThinkSmart Bar Expand XL | 5.9.5 | | ||| +| Lenovo Thinksmart Bar 180 | 8.1.0 | ✔ | ✔ | | ✔ | +| [Logitech Brio](https://www.logitech.com/product/brio) | V2.2.50 | ✔ | ||| +| [Logitech 930e](https://www.logitech.com/product/c930e-webcam) | 8.0.914 | ✔ | ||| +| [Logitech Rally](https://www.logitech.com/product/rally-ultra-hd-conferencecam) | 1.2.4 | | ||| +| [Logitech Rally Bar](https://www.logitech.com/products/video-conferencing/room-solutions/rallybar.960-001308.html) | 10.3.82 | | ||| +| [Logitech Rally Bar](https://www.logitech.com/products/video-conferencing/room-solutions/rallybar.html) with [Mic Pods](https://www.logitech.com/products/video-conferencing/accessories/mic-pod-for-rally.html) | Logi CollabOS: 1.10.425
Mic pods: 2.1.4 | | ||| +| [Logitech Sight](https://www.logitech.com/products/video-conferencing/room-solutions/sight.960-001510.html) + [Rally Bar](https://www.logitech.com/en-us/products/video-conferencing/room-solutions/rallybar.960-001308.html) | Sight:
Logi CollabOS: 1.10.208 | | ✔ ||| +| [Logitech Rally Bar Mini](https://www.logitech.com/products/video-conferencing/room-solutions/rallybarmini.960-001336.html) | 10.5.880 | | ||| +| [Logitech Sight](https://www.logitech.com/products/video-conferencing/room-solutions/sight.960-001510.html) + [Rally Bar Mini](https://www.logitech.com/products/video-conferencing/room-solutions/rallybarmini.960-001336.html) | Sight:
Logi CollabOS: 1.10.208 | | ✔ ||| +| [Logitech Rally Bar Huddle](https://www.logitech.com/business/solutions/huddle-space.html) | Logi CollabOS: 1.10.277
System Image: 0.903.271
Audio: 0.2.67 | | ||| +| [Logitech MeetUp](https://www.logitech.com/product/meetup-conferencecam) | Audio — 1.0.172
Video — 1.0.156 | | ||| +| [Logitech MeetUp 2](https://www.logitech.com/products/video-conferencing/conference-cameras/meetup2.html) | Logi CollabOS: 1.13.77 | | ||| +| [Logitech ConferenceCam Connect](https://www.logitech.com/product/conferencecam-connect) | 1.1.248.0
1.1.684 | | ||| +| [Logitech Group](https://www.logitech.com/product/conferencecam-group) | 8.5.778 | | ||| +| Logitech PTZ Pro | 1.1.219 | | ||| +| [Logitech PTZ Pro 2](https://www.logitech.com/products/video-conferencing/conference-cameras/ptz-pro2-conferencecam.960-001184.html) | | | ||| +| [Logitech Scribe](https://www.logitech.com/products/video-conferencing/room-solutions/scribe.960-001332.html) | 1.1.1 | ✔ | ||| +| [MAXHUB UC S07 Videoconferencing Camera](https://www.maxhub.com/en/s07/) | Audio firmware version: V0.0.0.5476
Video firmware version: V100-20230726-175602 | | ||| +| MAXHUB UC W31 4K USB Camera | Video firmware version: 100-20230731-104934 | | ||| +| MAXHUB UC BM35 | 0.0.02457 | | ||| +| [Microsoft Surface Hub Smart Camera](https://www.microsoft.com/d/surface-hub-smart-camera/8n983ctks176) | FW: 1.8.1 | | ||| +| [Microsoft Surface Hub 2 Camera](https://www.microsoft.com/d/surface-hub-2-camera/8tzgfl7z18ph) | FW: 24.712.159 | | ||| +| [Nureva HDL300](https://www.nureva.com/audio-conferencing/hdl300) | 2.3.6 | | ||| +| [Nureva HDL310](https://www.nureva.com/audio-conferencing/hdl310) | 1.8.269710 | | | ✔ | | +| [Nureva HDL410](https://www.nureva.com/audio-conferencing/hdl410) | 1.5.243554 | | ||| +| [Owl Labs Meeting Owl 3](https://owllabs.com/products/meeting-owl-3) | 6.4.10.42 | | ||| +| [Panasonic 360 degree camera speakerphone PressIT360](https://panasonic.net/cns/prodisplays/products/ty-csp1/) | 0.0.7904.54 | | ||| +| [Pansonic AW-UE4 camera](https://pro-av.panasonic.net/products/aw-ue4/) | 02.03 | | ||| +| [Poly Eagle Eye Cube Camera](https://www.polycom.com/products-services/hd-telepresence-video-conferencing/realpresence-accessories/eagleeye-cameras.html) | 1.2.0 | | ||| +| [Polycom EagleEye IV](https://www.poly.com/us/en/products/video-conferencing/eagleeye/eagleeye-iv) | 1.0.0 | | ||| +| [Polycom CX5100](https://www.polycom.com/products-services/products-for-microsoft/lync-optimized/cx5100-unified-conference-station.md) | 1.2.0.70232 | | ||| +| [Polycom Eagle Eye Director II](https://www.poly.com/us/en/products/video-conferencing/eagleeye/eagleeye-director-ii) | 2.1.0.10 | | ||| +| [Polycom Studio Soundbar](https://www.polycom.com/hd-video-conferencing/room-video-systems/polycom-studio.html) | 1.1.2.000570 | | ||| +| [Poly Sync 40](https://www.poly.com/us/en/products/phones/sync/sync-40) | 0.0.94.1461 | | ||| +| [Poly Sync 60](https://www.poly.com/us/en/products/phones/sync/sync-60) | 0.0.150.1671 | | ||| +| [Polycom Trio 8500 / 8800](https://www.polycom.com/voice-conferencing-solutions/conference-phones/trio.html) | 5.7.2.3205 | | ||| +| [Poly Trio C60](https://www.poly.com/us/en/products/phones/trio/trio-c60) | 5.9.5.3066 | | ||| +| [Poly Studio P15 Video Bar](https://www.poly.com/us/en/products/video-conferencing/studio-p/studio-p15) | 1.2.0.000287 | | ||| +| [Poly Studio E70 Camera](https://www.poly.com/us/en/products/video-conferencing/studio/studio-e70) | 1.1 | | ||| +| Poly Studio E60 Camera | 1.0.4.0 | | ||| +| [Poly Studio R30](https://www.poly.com/us/en/products/video-conferencing/studio/studio-r30) | 2.0.0.001096 | | ||| +| Poly Studio V52 | 1.0.1-400045 | | ||| +| Poly Studio V72 | 1.4.5-424011 | | ||| +| [EPOS SP 220 MS](http://no-no.sennheiser.com/dual-speakerphones-sp-220-ms-uc) | 2.0.12.0 | | ||| +| [EPOS SP20](https://www.eposaudio.com/en/us/enterprise/products/sp-20-ml-142ee5ca-speakerphone-1000226) | 1.2.15 | | ||| +| [EPOS SP30](https://www.eposaudio.com/en/us/enterprise/products/sp-30-78c0cecc-bluetooth-speakerphone-1000223) | 2.1.52 | | ||| +| [EPOS SP30T](https://www.eposaudio.com/en/us/enterprise/products/sp-30t-b949fe9a-bluetooth-speakerphone-1000225) | 3.2.63 | | ||| +| [EPOS Expand 80T + 2 Extension Mics](https://www.eposaudio.com/en/us/enterprise/products/expand-80t-bluetooth-speakerphone-1000203) | Speakerphone — 4.6.55
Extension Mic — 0.2.314 | | ||| | [EPOS Expand Capture 5](https://www.eposaudio.com/en/us/enterprise/products/expand-capture-5-speakerphone-1000895) | 1.0.1 | | | | ✔ | -| [EPOS EXPAND VISION 1M camera](https://www.eposaudio.com/en/us/enterprise/products/expand-vision-1m-usb-meeting-room-video-camera-1001197) | 9.24.0 | | | -| [Extron DMP128 PLUS C V AT DSP System (DMP 128 Plus C V AT, DMP 128 Plus C AT, DMP 128 Plus C V, DMP 128 Plus C, DMP 128 Plus AT, DMP 128 Plus, DMP 128 FlexPlus C AT, DMP 128 FlexPlus C V AT)](https://www.extron.com/product/dmp128plus) | 1.08 | | | -| [Extron DMP 64 PLUS C V AT DSP System (DMP 64 Plus C V AT, DMP 64 Plus C AT, DMP 64 Plus C V, DMP 64 Plus C)](https://www.extron.com/product/dmp64plus) | 1.08 | | | -| [:::no-loc text="Jabra"::: 510](https://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak-510##7510-209) | 2.10.0 | | | -| [:::no-loc text="Jabra"::: 710](http://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak-710) | 1.8.0 | | | -| [:::no-loc text="Jabra"::: 810](http://www.jabra.com/supportpages/jabra-speak-810) | 1.2.23 | | | -| [Yealink CP900](https://www.yealink.com/products_150.html) | 100.20.0.29 | | | -| Yealink Smartvision 40 | 286.410.0.20 | | | +| [EPOS EXPAND VISION 1M camera](https://www.eposaudio.com/en/us/enterprise/products/expand-vision-1m-usb-meeting-room-video-camera-1001197) | 9.24.0 | | ||| +| [Extron DMP128 PLUS C V AT DSP System (DMP 128 Plus C V AT, DMP 128 Plus C AT, DMP 128 Plus C V, DMP 128 Plus C, DMP 128 Plus AT, DMP 128 Plus, DMP 128 FlexPlus C AT, DMP 128 FlexPlus C V AT)](https://www.extron.com/product/dmp128plus) | 1.08 | | ||| +| [Extron DMP 64 PLUS C V AT DSP System (DMP 64 Plus C V AT, DMP 64 Plus C AT, DMP 64 Plus C V, DMP 64 Plus C)](https://www.extron.com/product/dmp64plus) | 1.08 | | ||| +| [:::no-loc text="Jabra"::: 510](https://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak-510##7510-209) | 2.10.0 | | ||| +| [:::no-loc text="Jabra"::: 710](http://www.jabra.com/business/speakerphones/jabra-speak-series/jabra-speak-710) | 1.8.0 | | ||| +| [:::no-loc text="Jabra"::: 810](http://www.jabra.com/supportpages/jabra-speak-810) | 1.2.23 | | ||| +| [Yealink CP900](https://www.yealink.com/products_150.html) | 100.20.0.29 | | ||| +| Yealink Smartvision 40 | 286.412.0.20 | | ✔ ||| | [Yealink SmartVision 60](https://www.yealink.com/en/product-detail/smartvision60) | 279.410.0.74 | | ✔ | | ✔ | -| [Yealink UVC30](https://www.yealink.com/product/microsoft-teams-room-system-uvc30) | 105.420.0.11 | ✔ | | -| [Yealink UVC34 All-in-one video bar](https://www.yealink.com/product/usb-videobar-uvc34) | 265.410.0.9 | | | -| [Yealink UVC40 All-in-one Video bar](https://www.yealink.com/product/usb-videobar-uvc40) | 128.410.0.10 | | | -| [Yealink UVC84](https://www.yealink.com/product/camera-uvc84) | 262.410.0.10 | | | -| [Yealink UVC86]( https://www.yealink.com/product/camera-uvc86) | 151.410.0.5 | | | +| [Yealink UVC30](https://www.yealink.com/product/microsoft-teams-room-system-uvc30) | 105.420.0.11 | ✔ | ||| +| [Yealink UVC34 All-in-one video bar](https://www.yealink.com/product/usb-videobar-uvc34) | 265.410.0.9 | | ||| +| [Yealink UVC40 All-in-one Video bar](https://www.yealink.com/product/usb-videobar-uvc40) | 128.410.0.10 | | ||| +| [Yealink UVC84](https://www.yealink.com/product/camera-uvc84) | 262.410.0.10 | | ||| +| [Yealink UVC86](https://www.yealink.com/product/camera-uvc86) | 151.410.0.5 | | ||| | Yealink MSpeech | 136.410.0.19 | | | | ✔ | -| Shure Microflex Ecosystem1: [MXA910 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa910?variant=MXA910AL-60CM) or [MXA920 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa920?variant=MXA920W-S) or [MXA901 Conferencing Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa901?variant=MXA901W-R) or [MXA902 Integrated Conferencing Ceiling Array](https://www.shure.com/products/microphones/mxa902?variant=MXA902W-S) or [MXA710 Linear Array Microphone](https://www.shure.com/products/microphones/mxa710?variant=MXA710AL-2FT%2520) or [MXA310 Table Array Microphone](https://www.shure.com/products/microphones/mxa310?variant=MXA310AL) +
Shure [IntelliMix P300 Audio Conferencing Processor](https://www.shure.com/products/mixers/p300?variant=P300-IMX) or [ANIUSB-MATRIX Network Interface](https://www.shure.com/products/mixers/aniusb-matrix?variant=ANIUSB-MATRIX) +
Shure [MXN5W-C Ceiling Speaker](https://www.shure.com/products/loudspeakers/mxn5?variant=MXN5W-C) | MXA910: FW 4.1, MXA920: FW 1.1.56, MXA901: FW 6.0.15.0, MXA902: FW 5.0.115, MXA710: FW 1.2.0, MXA310: FW 4.1,
P300: FW 4.1, ANIUSB-MATRIX: FW 4.7.21,
MXN5W-C: FW 1.0.4 | | | -|Shure Microflex Ecosystem1: [MXA910 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa910?variant=MXA910AL-60CM) or [MXA920 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa920?variant=MXA920W-S) or [MXA901 Conferencing Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa901?variant=MXA901W-R) or [MXA902 Integrated Conferencing Ceiling Array](https://www.shure.com/products/microphones/mxa902?variant=MXA902W-S) or [MXA710 Linear Array Microphone](https://www.shure.com/products/microphones/mxa710?variant=MXA710AL-2FT%2520) or [MXA310 Table Array Microphone](https://www.shure.com/products/microphones/mxa310?variant=MXA310AL) +
[Shure IntelliMix Room Software DSP](https://www.shure.com/products/software/intellimix_room) on Crestron UC-C100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 Compute or Dell OptiPlex7080XE or on Lenovo ThinkSmart Core +
[Shure MXN5W-C Ceiling Speaker](https://www.shure.com/products/loudspeakers/mxn5?variant=MXN5W-C) | MXA910: FW 4.1, MXA920: FW 1.1.56, MXA901: FW 6.0.15.0, MXA902: FW 5.0.115, MXA710: FW 1.2.0, MXA310: FW 4.1,
MXN5W-C: FW 1.0.4 | | | -| Shure MXW6X/C Cardioid Boundary Transmitter +
Shure MXWAPXD2 Access Point Transceiver +
Shure MXN5W-C Ceiling Speaker | MXW6X/C Transmitter: 1.1.0.236
MXWAPXD2: 1.1.0.236
MXN5W-C: 1.5.21.0 | | | +| Yealink CM20 Ceiling Audio Kit | Yealink RoomConnect Software: 2.33.43.0
AVHub: 153.433.0.15
CM20: 294.410.0.35
CS10: 298.410.0.40 | | ||| +| Shure Microflex Ecosystem1: [MXA910 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa910?variant=MXA910AL-60CM) or [MXA920 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa920?variant=MXA920W-S) or [MXA901 Conferencing Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa901?variant=MXA901W-R) or [MXA902 Integrated Conferencing Ceiling Array](https://www.shure.com/products/microphones/mxa902?variant=MXA902W-S) or [MXA710 Linear Array Microphone](https://www.shure.com/products/microphones/mxa710?variant=MXA710AL-2FT%2520) or [MXA310 Table Array Microphone](https://www.shure.com/products/microphones/mxa310?variant=MXA310AL) +
Shure [IntelliMix P300 Audio Conferencing Processor](https://www.shure.com/products/mixers/p300?variant=P300-IMX) or [ANIUSB-MATRIX Network Interface](https://www.shure.com/products/mixers/aniusb-matrix?variant=ANIUSB-MATRIX) +
Shure [MXN5W-C Ceiling Speaker](https://www.shure.com/products/loudspeakers/mxn5?variant=MXN5W-C) | MXA910: FW 4.1, MXA920: FW 1.1.56, MXA901: FW 6.0.15.0, MXA902: FW 5.0.115, MXA710: FW 1.2.0, MXA310: FW 4.1,
P300: FW 4.1, ANIUSB-MATRIX: FW 4.7.21,
MXN5W-C: FW 1.0.4 | | ||| +|Shure Microflex Ecosystem1: [MXA910 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa910?variant=MXA910AL-60CM) or [MXA920 Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa920?variant=MXA920W-S) or [MXA901 Conferencing Ceiling Array Microphone](https://www.shure.com/products/microphones/mxa901?variant=MXA901W-R) or [MXA902 Integrated Conferencing Ceiling Array](https://www.shure.com/products/microphones/mxa902?variant=MXA902W-S) or [MXA710 Linear Array Microphone](https://www.shure.com/products/microphones/mxa710?variant=MXA710AL-2FT%2520) or [MXA310 Table Array Microphone](https://www.shure.com/products/microphones/mxa310?variant=MXA310AL) +
[Shure IntelliMix Room Software DSP](https://www.shure.com/products/software/intellimix_room) on Crestron UC-C100-T with :::no-loc text="ASUSTeK"::: Computer INC 9934 Compute or Dell OptiPlex7080XE or on Lenovo ThinkSmart Core +
[Shure MXN5W-C Ceiling Speaker](https://www.shure.com/products/loudspeakers/mxn5?variant=MXN5W-C) | MXA910: FW 4.1, MXA920: FW 1.1.56, MXA901: FW 6.0.15.0, MXA902: FW 5.0.115, MXA710: FW 1.2.0, MXA310: FW 4.1,
MXN5W-C: FW 1.0.4 | | ||| +| Shure MXW6X/C Cardioid Boundary Transmitter +
Shure MXWAPXD2 Access Point Transceiver +
Shure MXN5W-C Ceiling Speaker | MXW6X/C Transmitter: 1.1.0.236
MXWAPXD2: 1.1.0.236
MXN5W-C: 1.5.21.0 | | ||| | [Sennheiser TeamConnect Intelligent Speaker/TC ISP (T-Rock)](https://en-us.sennheiser.com/tcisp) | 1.0.6 | | | | ✔ | -| [Sennheiser TC Bar M](https://www.sennheiser.com/tcbar-medium) | 0.9.17 | | | -| [Sennheiser TC Bar S](https://www.sennheiser.com/tcbar-small) | 0.9.17 | | | -| [Biamp Tesira Fore AVB VT4 Fixed audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+ ‡
[Sennheiser TeamConnect Ceiling 2 Microphone](https://sennheiser.com/tcc2)+ ‡
[Tesira EX-UBT](https://www.biamp.com/products/tesira/tesira-expanders) ‡ | Biamp DSP: 3.12.0.15
TCC2: 1.3.3
EX-UBT: 3.12.0.15 | | | -| [Biamp Tesira FORTÉ AVB VT4 Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones)+
[Biamp Desono C-IC6 ceiling mounted loudspeaker](https://www.biamp.com/products/tesira-speakers) | Audio FW version: 3.15 | | | -| [Biamp TesiraFORTE AVB VT4](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Parle TTM-X(Table Mic)](https://www.biamp.com/products/product-families/parle/parle-microphones)+
[Ex-UBT]() | Audio FW version: 3.15 | | | -| [Biamp :::no-loc text="Devio"::: SCX Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones) +
[Biamp Desono C-IC6 ceiling mounted loudspeaker](https://www.biamp.com/products/tesira-speakers) | :::no-loc text="Devio"::: SCX Series: 4.2.5 | | | -| [Biamp Tesira Forte X Series Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones) +
[Biamp Desono C-IC6 ceiling mounted loudspeaker](https://www.biamp.com/products/tesira-speakers) | Tesira FORTE X Series: 4.2.5 | | | -| [Bose ControlSpace EX-440C DSP +
Bose P2600A AmpLink Amplifier +
Sennheiser TCC2 Ceiling Microphone +
Bose EdgeMax EM180 Ceiling Speaker](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | | -| [Bose ControlSpace EX-440C DSP +
Bose P2600A AmpLink Amplifier + Sennheiser TCC2 Ceiling Microphone +
Bose DesignMax DM2C-P Ceiling Speaker](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | | -| [Bose ControlSpace EX-1280C DSP](https://pro.bose.com/en_us/products/signal_processing_and_networking/controlspace_ex/cs_ex_1280c.html#v=cs_ex_1280c_black) +
Bose P2600A AmpLink Amplifier +
[Sennheiser TCC2 Ceiling Microphone](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) +
[DesignMax DM2C -LP Ceiling Speaker](https://pro.bose.com/en_us/products/loudspeakers/background_foreground/designmax/designmax_dm2c_lp.html#v=designmax_dm2c_lp_black) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | | -| [Bose ControlSpace EX-1280C DSP](https://pro.bose.com/en_us/products/signal_processing_and_networking/controlspace_ex/cs_ex_1280c.html#v=cs_ex_1280c_black) +
Bose P2600A AmpLink Amplifier+
[Sennheiser TCC2 Ceiling Microphone](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) +
[EdgeMax EM180 Ceiling Speaker](https://pro.bose.com/en_us/products/loudspeakers/background_foreground/edgemax/edgemax_em180.html#v=edgemax_em180_white) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | | -| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Network Microphone ([Q-SYS NM-T1](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/nm-t1/), [Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) or [AudioTechnica ATND1061](https://www.qsys.com/alliances-partnerships/audio-technica/?L=0)) +
Q-SYS Amplifier ([SPA series](https://www.qsys.com/products-solutions/power-amplifiers/installed/non-network/low-power-applications/spa-series/) or [CX-Q series](https://www.qsys.com/products-solutions/power-amplifiers/installed/network/cx-q-series/)) +
[AcousticDesign Series Loudspeakers](https://www.qsys.com/products-solutions/loudspeakers/installed/passive/ceiling-mount/acousticdesign-series/) +
Q-SYS Network Camera ([PTZ-IP 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [PTZ-IP 12x72](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) optional +
[Q-SYS I/O USB Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AudioTechnica ATND1061: 1.0.2
Q-SYS Amplifiers: N/A
AcousticDesign Series Loudspeakers: N/A | | | | -| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
[Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) Ceiling Microphone +
Q-SYS [SPA series](https://www.qsys.com/products-solutions/power-amplifiers/installed/non-network/low-power-applications/spa-series/) Amplifier +
[AcousticDesign Wall Mount Series Loudspeakers](https://www.qsys.com/products-solutions/loudspeakers/installed/passive/column-surface-mount/acousticdesign-series/) +
Q-SYS Network Camera ([PTZ-IP 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [PTZ-IP 12x72](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) optional +
[Q-SYS I/O USB Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AcousticDesign Series Loudspeakers: N/A | | | ✔ | -| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Network Microphone ([Q-SYS NM-T1](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/nm-t1/), [Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) or [AudioTechnica ATND1061](https://www.qsys.com/alliances-partnerships/audio-technica/?L=0)) +
Q-SYS [NL Series Loudspeakers](https://www.qsys.com/products-solutions/q-sys/audio-network-loudspeakers/nl-series/) +
Q-SYS Network Camera ([NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/) optional +
[Q-SYS I/O Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AudioTechnica ATND1061: 1.0.2 | | | -|Q-SYS VisionSuite – Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Q-SYS Network Camera ([NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-series-ptz-conference-cameras/), [NC-20x60](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-series-ptz-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) +
Q-SYS Seervision AI Accelerator ([SVS1-2U, SVS4-2U](https://www.qsys.com/products/q-sys/video/seervision/?L=0)) +
Certified for Microsoft Teams Q-SYS Audio Solution with Ceiling Mic | Q-SYS Designer 9.10.1
Seervision v75.0.3
VisionSuite Plugin v75.0.3 | | | -| [Vaddio IntelliSHOT-M](https://www.legrandav.com/products/cameras/hd_fixed_camera/intellishot-m-camera) | 1.0.0 | | | -| [Vaddio RoboSHOT 30E-M HD PTZ Camera](https://www.legrandav.com/products/cameras/hd_ptz_camera/roboshot-30e-m) | 1.0.0 | | | -| [Yamaha CS-500](https://europe.yamaha.com/en/products/unified_communications/video_collaboration/cs-500/index.html) | 1.0.4 | | | -| [Yamaha CS-800](https://europe.yamaha.com/en/products/unified_communications/video_collaboration/cs-800/index.html) | 1.0.4 | | | -| [Yamaha ADECIA Ceiling Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_ceiling/index.html) | 1.2.0 | | | -| [Yamaha ADECIA Tabletop Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_tabletop/index.html) | E1.2.0 for table mic, D1.2.0 for processor | | | -| [Yamaha ADECIA Wireless Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_wireless/index.html) | 1.9.5 for Wireless mic, 2.1.0 for processor | | | -| [Yamaha YVC-1000MS](https://europe.yamaha.com/en/products/unified_communications/speakerphones/yvc-1000ms/index.html) | 1.0.0 | | | +| Sennheiser TC Bar M | 0.9.17 | | ||| +| Sennheiser TC Bar S | 0.9.17 | | ||| +| [Biamp Tesira Fore AVB VT4 Fixed audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+ ‡
[Sennheiser TeamConnect Ceiling 2 Microphone](https://sennheiser.com/tcc2)+ ‡
[Tesira EX-UBT](https://www.biamp.com/products/tesira/tesira-expanders) ‡ | Biamp DSP: 3.12.0.15
TCC2: 1.3.3
EX-UBT: 3.12.0.15 | | ||| +| [Biamp Tesira FORTÉ AVB VT4 Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones)+
Biamp Desono C-IC6 ceiling mounted loudspeaker | Audio FW version: 3.15 | | ||| +| [Biamp TesiraFORTE AVB VT4](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Parle TTM-X(Table Mic)](https://www.biamp.com/products/product-families/parle/parle-microphones)+
[Ex-UBT]() | Audio FW version: 3.15 | | ||| +| [:::no-loc text="Devio"::: SCX Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones) +
Biamp Desono C-IC6 ceiling mounted loudspeaker [Biamp :::no-loc text="Devio"::: SCX Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones) +
Biamp Desono C-IC6 ceiling mounted loudspeaker | :::no-loc text="Devio"::: SCX Series: 4.2.5 | | ||| +| [Biamp Tesira Forte X Series Audio DSP](https://www.biamp.com/products/tesira-fixed-audio-dsp)+
[Biamp Parlé TCM-XA Ceiling Microphone](https://www.biamp.com/products/product-families/parle/parle-microphones) +
Biamp Desono C-IC6 ceiling mounted loudspeaker | Tesira FORTE X Series: 4.2.5 | | ||| +| [Bose ControlSpace EX-440C DSP +
Bose P2600A AmpLink Amplifier +
Sennheiser TCC2 Ceiling Microphone +
Bose EdgeMax EM180 Ceiling Speaker](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | ||| +| [Bose ControlSpace EX-440C DSP +
Bose P2600A AmpLink Amplifier + Sennheiser TCC2 Ceiling Microphone +
Bose DesignMax DM2C-P Ceiling Speaker](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | ||| +| [Bose ControlSpace EX-1280C DSP](https://pro.bose.com/en_us/products/signal_processing_and_networking/controlspace_ex/cs_ex_1280c.html#v=cs_ex_1280c_black) +
Bose P2600A AmpLink Amplifier +
[Sennheiser TCC2 Ceiling Microphone](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) +
[DesignMax DM2C -LP Ceiling Speaker](https://pro.bose.com/en_us/products/loudspeakers/background_foreground/designmax/designmax_dm2c_lp.html#v=designmax_dm2c_lp_black) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | ||| +| [Bose ControlSpace EX-1280C DSP](https://pro.bose.com/en_us/products/signal_processing_and_networking/controlspace_ex/cs_ex_1280c.html#v=cs_ex_1280c_black) +
Bose P2600A AmpLink Amplifier+
[Sennheiser TCC2 Ceiling Microphone](https://www.boseprofessional.com/en_us/solutions/work/es1-ceiling-audio-solution.html) +
[EdgeMax EM180 Ceiling Speaker](https://pro.bose.com/en_us/products/loudspeakers/background_foreground/edgemax/edgemax_em180.html#v=edgemax_em180_white) | Bose DSP: 2.290
P2600A: 1.160
TCC2: 1.4.2 | | ||| +| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Network Microphone ([Q-SYS NM-T1](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/nm-t1/), [Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) or [AudioTechnica ATND1061](https://www.qsys.com/alliances-partnerships/audio-technica/?L=0)) +
Q-SYS Amplifier ([SPA series](https://www.qsys.com/products-solutions/power-amplifiers/installed/non-network/low-power-applications/spa-series/) or [CX-Q series](https://www.qsys.com/products-solutions/power-amplifiers/installed/network/cx-q-series/)) +
[AcousticDesign Series Loudspeakers](https://www.qsys.com/products-solutions/loudspeakers/installed/passive/ceiling-mount/acousticdesign-series/) +
Q-SYS Network Camera ([PTZ-IP 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [PTZ-IP 12x72](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) optional +
[Q-SYS I/O USB Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AudioTechnica ATND1061: 1.0.2
Q-SYS Amplifiers: N/A
AcousticDesign Series Loudspeakers: N/A | | | || +| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
[Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) Ceiling Microphone +
Q-SYS [SPA series](https://www.qsys.com/products-solutions/power-amplifiers/installed/non-network/low-power-applications/spa-series/) Amplifier +
[AcousticDesign Wall Mount Series Loudspeakers](https://www.qsys.com/products-solutions/loudspeakers/installed/passive/column-surface-mount/acousticdesign-series/) +
Q-SYS Network Camera ([PTZ-IP 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [PTZ-IP 12x72](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC 20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) optional +
[Q-SYS I/O USB Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AcousticDesign Series Loudspeakers: N/A | | | ✔ || +| Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Network Microphone ([Q-SYS NM-T1](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/nm-t1/), [Sennheiser TCC2](https://en-us.sennheiser.com/tcc2) or [AudioTechnica ATND1061](https://www.qsys.com/alliances-partnerships/audio-technica/?L=0)) +
Q-SYS [NL Series Loudspeakers](https://www.qsys.com/products-solutions/q-sys/audio-network-loudspeakers/nl-series/) +
Q-SYS Network Camera ([NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-20x60](https://www.qsys.com/products-solutions/q-sys/video/ptz-ip-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/) optional +
[Q-SYS I/O Bridge](https://www.qsys.com/products-solutions/q-sys/audio-io-peripherals/io-usb-bridge/) optional | Q-SYS Designer 9.7.0
Sennheiser TCC2 Ceiling Microphone: TCC2 - 1.5.1
Dante 1.2.0
AudioTechnica ATND1061: 1.0.2 | | ||| +|Q-SYS VisionSuite – Q-SYS Core ([110f](https://www.qsys.com/products-solutions/q-sys/processing/core-110f/), [8 Flex](https://www.qsys.com/products-solutions/q-sys/processing/core-8-flex/), [Nano](https://www.qsys.com/products-solutions/q-sys/processing/core-nano/), or [NV-32-H](https://www.qsys.com/products-solutions/q-sys/processing/nv-32-h-core-capable/)) +
Q-SYS Network Camera ([NC-12x80](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-series-ptz-conference-cameras/), [NC-20x60](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-series-ptz-conference-cameras/), [NC-110](https://www.qsys.com/products-solutions/q-sys/video/nc-series/nc-110-conference-camera/)) +
Q-SYS Seervision AI Accelerator ([SVS1-2U, SVS4-2U](https://www.qsys.com/products/q-sys/video/seervision/?L=0)) +
Certified for Microsoft Teams Q-SYS Audio Solution with Ceiling Mic | Q-SYS Designer 9.10.1
Seervision v75.0.3
VisionSuite Plugin v75.0.3 | | ||| +| [Vaddio IntelliSHOT-M](https://www.legrandav.com/products/cameras/hd_fixed_camera/intellishot-m-camera) | 1.0.0 | | ||| +| [Vaddio RoboSHOT 30E-M HD PTZ Camera](https://www.legrandav.com/products/cameras/hd_ptz_camera/roboshot-30e-m) | 1.0.0 | | ||| +| [Yamaha CS-500](https://europe.yamaha.com/en/products/unified_communications/video_collaboration/cs-500/index.html) | 1.0.4 | | ||| +| [Yamaha CS-800](https://europe.yamaha.com/en/products/unified_communications/video_collaboration/cs-800/index.html) | 1.0.4 | | ||| +| [Yamaha ADECIA Ceiling Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_ceiling/index.html) | 1.2.0 | | ||| +| [Yamaha ADECIA Tabletop Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_tabletop/index.html) | E1.2.0 for table mic, D1.2.0 for processor | | ||| +| [Yamaha ADECIA Wireless Solution](https://europe.yamaha.com/en/products/contents/unified_communications/adecia_wireless/index.html) | 1.9.5 for Wireless mic, 2.1.0 for processor | | ||| +| Yamaha ADECIA Ceiling Solution using Ceiling Speakers | RM-CR (DSP): 2.7
RM-CG (Microphone): 2.7.1
VXC2P (Speaker): 1.0.0 | | ||| +| [Yamaha YVC-1000MS](https://europe.yamaha.com/en/products/unified_communications/speakerphones/yvc-1000ms/index.html) | 1.0.0 | | ||| ‡ Customers may choose either the Dante interface or the network switch recommended by Biamp/Sennheiser for this bundle. 1 On a Teams Rooms device that is paired with a Shure microphone, the audio setting displayed on the device doesn't sync with the setting on the microphone in meetings that don't use Microsoft Teams. diff --git a/Teams/rooms/conditional-access-and-compliance-for-devices.md b/Teams/rooms/conditional-access-and-compliance-for-devices.md index 03251c8d59..6eb45dc9cb 100644 --- a/Teams/rooms/conditional-access-and-compliance-for-devices.md +++ b/Teams/rooms/conditional-access-and-compliance-for-devices.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: dimehta -ms.date: 08/22/2024 +ms.date: 10/21/2024 ms.topic: article audience: Admin ms.service: msteams @@ -20,59 +20,61 @@ f1.keywords: description: Learn about recommended Conditional Access and Intune device compliance policies and best practices for Microsoft Teams Rooms. --- -# Conditional Access and Intune compliance for Microsoft Teams Rooms +# Conditional Access and Intune compliance for Microsoft Teams Rooms and panels -This article provides requirements and best practices for Conditional Access and Intune device compliance policies for Microsoft Teams Rooms that are used in shared spaces. +This article provides requirements and best practices for Conditional Access and Intune device compliance policies for Microsoft Teams Rooms on Windows, Teams Rooms on Android, and Teams panel devices. [!INCLUDE [teams-pro-license-requirement](../includes/teams-pro-license-requirement.md)] ## Requirements -Teams Rooms must already be deployed on the devices you want to assign Conditional Access policies to. If you haven't deployed Teams Rooms yet, see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md) and [Deploy Microsoft Teams Rooms on Android](../devices/collab-bar-deploy.md) for more information. - -A Microsoft Entra ID P1 Service Plan is required to use Conditional Access. Its included in the Microsoft Teams Rooms license. +- Teams Rooms resource accounts created, for more information, see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md). +- A Microsoft Entra ID P1 Service Plan is required to use Conditional Access. It's included in the Microsoft Teams Rooms license or Shared Device license. ## Teams Rooms Conditional Access best practices -Conditional Access policies can secure the sign in process on devices that are in shared spaces and used by multiple people. For an overview of Conditional Access in Microsoft Entra ID, see [What is Conditional Access in Microsoft Entra ID?](/azure/active-directory/conditional-access/overview). +Conditional Access policies can secure the sign in process on devices that are in shared spaces. For an overview of Conditional Access in Microsoft Entra ID, see [What is Conditional Access in Microsoft Entra ID?](/azure/active-directory/conditional-access/overview). -When using Conditional Access to secure Teams Rooms, consider the -following best practices: +When using Conditional Access to secure Teams Rooms, consider the following best practices: -- To simplify deployment and management, include all Microsoft 365 room resources accounts associated with Teams Rooms in one user group. -- Have a naming standard for all Teams Rooms resource accounts. For - example, the account names 'mtr-room1@contoso.com' and - 'mtr-room2@contoso.com' both start with the prefix 'mtr-'. - When account names are standardized, you can use dynamic groups in Microsoft Entra ID - to automatically apply Conditional Access policies to all of these - accounts at once. For more information on dynamic groups, see [Rules for dynamically populated groups membership](/azure/active-directory/enterprise-users/groups-dynamic-membership). +- Include all Microsoft 365 room resources accounts associated with Teams Rooms in one Microsoft Entra ID user group. +- Use a naming standard for all Teams Rooms resource accounts. For example, the account names 'mtr-room1@contoso.com' and 'mtr-room2@contoso.com' both start with the prefix 'mtr-'. When account names are standardized, you can use dynamic groups in Microsoft Entra ID to automatically apply Conditional Access policies to all of these accounts at once. For more information on dynamic groups, see [Rules for dynamically populated groups membership](/azure/active-directory/enterprise-users/groups-dynamic-membership). +- Exclude your Teams Rooms resource accounts from all existing Conditional Access policies and create a new policy specific to the resource accounts. +- Do not require user interactive multifactor authentication (MFA). User interactive MFA isn't supported for Teams Rooms resource accounts since the resource accounts don't have a second device to approve the MFA request. For a list of supported Conditional Access assignments for Teams Rooms, see [Supported Conditional Access policies](supported-ca-and-compliance-policies.md#supported-conditional-access-policies). -## Example Conditional Access policy +### Example Conditional Access policy In this example, the Conditional Access policy works as follows: 1. The account signing in must be a member of a specific user group, in this example, the "Shared devices" group. -2. The account signing in must only be trying to access Office 365, Office 365 Exchange Online, Microsoft Teams Services, and Office 365 SharePoint Online. Attempts to sign into any other client app are rejected. -3. The resource account must be signing in on the Windows device platform. -4. The resource account must also sign in from a known, trusted location. +2. The account signing in must only be trying to access Office 365, Office 365 Exchange Online, Microsoft Teams Services, and Microsoft 365 SharePoint Online. Attempts to sign into any other client app are rejected. +3. The authentication method must be modern authentication. Legacy authentication mechanisms should be blocked. +4. The resource account must be signing in on the Windows or Android device platform. +5. The resource account must also sign in from a known, trusted location. +6. The resource account must be signing in from a compliant device. -If these conditions are met successfully, and the user enters the correct username and password, then the resource account signs into Teams. +If these conditions are met successfully, and the device has the correct username and password, then the resource account signs into Teams. -## Conditional Access with Microsoft Intune compliance for Teams Rooms +## Intune compliance for Teams Rooms -Compliance requirements are defined rules that devices must meet to be marked as compliant, such as minimum operating system version. Devices must be considered compliant before they can be used to sign into a resource account. +Compliance requirements are defined rules that devices must meet to be marked as compliant, such as minimum operating system version. Device compliance can be used as a condition in conditional access before the resource account can sign in. For a list of supported Intune compliance policies for Teams Rooms, see [Supported device compliance policies](supported-ca-and-compliance-policies.md#supported-device-compliance-policies). -For more information on setting up Intune with Teams Android devices, see [Configure Intune to enroll Teams Android-based devices](../devices/phones-panels-deploy.md#configure-intune-to-enroll-teams-android-based-devices). +### Example Intune compliance policy for Teams Rooms on Windows -## Example (Windows only): Conditional Access with Intune device compliance +1. Require that a firewall is running on Teams Rooms on Windows. +2. Require a minimum operating system version. +3. Require that Microsoft Defender is running on Teams Rooms. -In this example for Teams Rooms on Windows +This compliance policy should be assigned to the Teams Rooms devices and the Teams Rooms resource accounts. If the device doesn't meet these requirements, it won't be marked as compliant. -1. Require that a firewall is running on Teams Rooms on Windows. -2. Require that Microsoft Defender is running on Teams Rooms. -3. If Teams Rooms doesn't meet either of these requirements, it won't be marked as compliant, and the devices won't sign in. -This compliance policy applies to all users, not just Teams resource accounts. \ No newline at end of file +### Example Intune compliance policy for Teams Rooms on Android and Teams panels + +1. Minimum operating system version is greater than Android 10. +2. Block rooted devices. +3. Require encryption of data storage on device + +This compliance policy should be assigned to the Teams Rooms devices and the Teams Rooms resource accounts. If the device doesn't meet these requirements, it won't be marked as compliant. diff --git a/Teams/rooms/content-camera.md b/Teams/rooms/content-camera.md index 6e3f24cc1b..684b2645fe 100644 --- a/Teams/rooms/content-camera.md +++ b/Teams/rooms/content-camera.md @@ -1,5 +1,5 @@ --- -title: Learn how to setup content cameras - Microsoft Teams +title: Learn how to set up content cameras - Microsoft Teams author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -27,9 +27,6 @@ description: Use a content camera in Microsoft Teams Rooms that interacts with i You can now use a content camera with a Microsoft Teams Rooms system. A content camera interacts with special image-processing software and a whiteboard to allow a presenter to draw on an analog whiteboard and share the content with remote participants. -> [!NOTE] -> Special image-processing software to enhance the whiteboard's content is available on all Teams Rooms on Windows, and select Teams Rooms on Android. - [!INCLUDE [teams-pro-license-requirement](../includes/teams-pro-license-requirement.md)] See the following video for examples of content camera functionality. @@ -88,7 +85,7 @@ If you have whiteboards larger than 12 ft. (3.65 m) or with no corners (like ful ## [Teams Rooms for Windows](#tab/Windows) ### Supported Windows cameras -To determine whether you can use a camera as a content camera, refer to [Teams Rooms certified systems and peripherals](/microsoftteams/rooms/certified-hardware?tabs=Peripherals). +Any certified Teams Rooms on Windows camera can be used as a content camera. However, we recommend using a camera which has been specifically certified as a content camera for the best experience. Refer to [Teams Rooms certified systems and peripherals](/microsoftteams/rooms/certified-hardware?tabs=Peripherals) for certified cameras. Or, refer to the Microsoft Teams devices marketplace for supported Content Camera Kits at [aka.ms/teamsdevices](https://aka.ms/teamsdevices). @@ -114,7 +111,7 @@ To determine whether your Teams Rooms on Android supports the addition of a cont Once the camera is installed in the room, set it up on that room's Microsoft Teams Rooms console: 1. Navigate to the Teams Admin Settings page on your Microsoft Teams Rooms on Android device. The steps for this will differ depending on the device. -1. Select Devices, then Content Camera. Select the content camera using the drop down menu. +1. Select Devices, then Content Camera. Select the content camera using the drop-down menu. 1. (Optional) If the camera was installed upside down because the camera was mounted from the ceiling, check the **Rotate 180°** option. 1. Tap away from the dialog to save the settings. diff --git a/Teams/rooms/copilot-admin-mtr.md b/Teams/rooms/copilot-admin-mtr.md new file mode 100644 index 0000000000..7a3f3cc546 --- /dev/null +++ b/Teams/rooms/copilot-admin-mtr.md @@ -0,0 +1,385 @@ +--- +title: Admin guide to Copilot in Teams +author: mstonysmith +ms.author: tonysmit +manager: pamgreen +ms.reviewer: elaineho +ms.date: 10/23/2024 +ms.topic: article +audience: admin +appliesto: + - Microsoft Teams +ms.service: msteams +ms.subservice: itpro-rooms +ms.collection: + - M365-collaboration + - teams-rooms-consoles + - Tier1 +f1.keywords: + - NOCSH +search.appverid: MET150 +ms.localizationpriority: medium +description: Learn more about how to set up Copilot and AI-based features in Microsoft Teams Rooms. +--- + +# Teams Rooms and Copilot overview + +When you're considering deploying Copilot and AI-based features for your Teams users, there are many things to consider. The number and type of AI-based features is dependent on the type of license you assign to your Teams users, the devices you're using for Teams Rooms, and the type of license assigned to your Microsoft Teams Rooms resource account. + +There are four separate sets of AI-based features that can be deployed to your users when you assign a specific license for those users and Teams Rooms. + +- **Copilot** - Copilot bot integration. Adding it to all the apps including Teams. Ask questions to resolve issues, catch up during meetings (meeting recap), organize meeting points. +- **Teams Rooms** - Live transcripts and captions. Intelligent Speaker - identify in-room participants. +- **Meetings and collaboration** - Policy changes for transcription, captions, and recording. +- **Microsoft Teams** - AI-based noise suppression and video optimization. Cameo overlay. Voice isolation. Speaker attribution, face, and voice enrollment. + +To see more about these features, see [Get more out of hybrid meetings with Teams Rooms and Copilot](https://techcommunity.microsoft.com/t5/microsoft-teams-blog/get-more-out-of-hybrid-meetings-with-teams-rooms-and-copilot/ba-p/4057302). + +## Getting started with Copilot + +[Microsoft 365 Copilot](https://www.microsoft.com/microsoft-365/blog/2023/03/16/introducing-microsoft-365-copilot-a-whole-new-way-to-work) is an AI-powered productivity tool that uses large language models (LLMs) and integrates your data with the Microsoft Graph and Microsoft 365 Apps. + +Microsoft 365 provides the ability for users to find and access their content through natural language prompting. Copilot ensures data security and privacy by adhering to existing obligations and integrating with your organization's policies. To get the most out of Copilot, you should consider optimizing data and content for Search, to ensure optimal secure access. To learn more about privacy with Microsoft 365 Copilot, see [Data, Privacy, and Security for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-privacy). + +To get started with Microsoft 365 Copilot, see [Get started with Microsoft 365 Copilot - admin guide](/copilot/microsoft-365/microsoft-365-copilot-setup). + +## Requirements for Microsoft 365 Copilot + +The integration of Microsoft 365 Copilot and Microsoft 365 Apps enables Copilot experiences to take place inside individual apps, such as Word, PowerPoint, Teams, Excel, Outlook, and more. As a result of this integration, the requirements for using Microsoft 365 Copilot are nearly identical to the requirements for using Microsoft 365 Apps. + +To see more videos on [Copilot, see Microsoft Mechanics--Podcast](). + +Learn more: [Service Descriptions for Copilot](/copilot/microsoft-365/microsoft-365-copilot-requirements). + +## Admin set up for Teams Rooms + +Within your organization, there are several settings that you'll either need to turn on (they're off by default) or verify that they're turned on to let end users get the full advantages of Copilot in Microsoft Teams Rooms specifically. Settings like transcriptions, captioning, recording, voice isolation, voice enrollment are a few of the settings that you want to set up or turn on for your end users in your organization in order for users to benefit from Copilot and Microsoft Teams Rooms. + +### Assign your licenses + +After you've prepared your organization for Copilot, you can manage your Microsoft 365 licenses from the Microsoft 365 admin center. You can assign licenses to individual users or to groups of users and reassign licenses to other users depending on the level of AI support that would be needed. + +#### Feature vs license comparison + +| Feature | Microsoft Teams | Microsoft Teams Premium | Copilot for M365 | +|:-----|:-----|:-----|:-----| +|AI-based noise suppression|Yes||| +|AI-based video optimization (brightness and backgrounds)|Yes||| +|Suggested replies|Yes||| +|Live meeting captions and transcript|Yes||| +|Cameo video overlay on screen share and PowerPoint Live|Yes||| +|Real-time translation of meeting captions and transcripts||Yes|| +|Intelligent recap (after recording) - standardized AI notes and AI tasks||Yes|Yes| +|Intelligent recap (after recording) - video, speaker, chapter markers||Yes|Yes| +|Ask any question during meeting?|||Yes| +|How did the team react to proposal?|||Yes| +|Does this plan's timeline have any conflicts?|||Yes| +|Create a table with pros and cons|||Yes| +|Microsoft Copilot UX|||Yes| +|Other: AI-powered web grounding and Microsoft 365 Graph grounding|||Yes| +|Other: Microsoft Copilot and Copilot Studio|||Yes| +|Other: Copilot in core Microsoft 365 apps|||Yes| + +Learn more: [Set up Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-setup). + +In Teams, there are different types of user licenses that you must assign. First, you must assign at least one user license to your users depending on what features you want available to your Teams users. Second, to take advantage of all of the AI-based features you must then assign a Microsoft Teams Pro license to each Teams Rooms console in your organization. + +Learn more: [Understand licensing requirements for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-licensing) + +#### Assign user licenses + +For business users, a user must have a Microsoft 365 Business Basic, Business Standard, Business Premium, E3, E5, F1, or F3 and Microsoft 365 Copilot subscriptions. + +To assign and manage licenses, you can use the Microsoft 365 admin center. + +1. Sign in to the Microsoft 365 admin center, go to Marketplace and purchase Microsoft 365 Copilot from the list. = + +1. After you purchase the subscription, go to **Billing** > **Licenses** > select **Microsoft 365 Copilot.** + +1. In the product details page, assign the licenses to users and manage their access to Microsoft 365 Copilot and other apps and services. + +Learn more: [Assign licenses for Copilot](/copilot/microsoft-365/microsoft-365-copilot-enable-users) + +### Assign a Teams Room Pro license + +To assign a Microsoft Teams Rooms Pro license, you can use the Microsoft 365 admin center. + +1. Sign in to the Microsoft 365 admin center and go to **Users** > **Active users** > Select the **resource account** you created earlier. +1. In the right pane, select **Licenses and Apps**. + +1. Assign a Teams Room Pro license. + +1. To assign a Microsoft Teams Rooms Pro license, you can use the Microsoft 365 admin center. + + 1. Sign in to the Microsoft 365 admin center and go to **Users** > **Active users** > Select the **resource account** you created earlier. + 1. In the right pane, select **Licenses and Apps**. + +Learn more: [Enable users for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-enable-users). + +### Update your Teams Rooms devices + +Microsoft Teams Rooms on Windows supports Intelligent Speaker. Intelligent Speaker (speaker recognition or speaker attribution) is used in live meetings and in meeting transcripts to identify each the speaker. With Copilot, Teams Rooms not only enhance the overall meeting experience with Intelligent Speaker, it enables better support for collaboration and works together by adding meeting summaries and Intelligent Recap. + +To support these features, you want to verify that all Teams Rooms on Windows devices are updated and have the hardware to support Intelligent Speaker or speaker recognition. + +To update Teams Rooms running Windows, see [Teams Rooms app and Windows versioning support](rooms-lifecycle-support.md). Verify that all of your Teams Rooms are running the latest Windows updates. + +> [!CAUTION] +> Intelligent Speaker isn't yet available for Teams Rooms on Android. It's only supported on Teams Rooms on Windows. + +Although you don't get Intelligent Speaker as a features on Teams Rooms on Android yet, it's important that if you have Teams Rooms on Android devices you still will get other AI-based features like noise suppression. To see what features are available, see [Teams Rooms and panels feature comparison](teams-devices-feature-comparison.md?tabs=Commercial). + +To support those features, make sure you have updated the firmware on all of your Teams Rooms on Android devices. See [Teams Rooms on Android supported firmware](../devices/certified-hardware-android.md?tabs=Android). + +### Voice and face enrollment + +#### Turn on voice and face enrollment + +You can turn on or off voice and face enrollment for specific users, or groups using the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) policy. You can see the meeting settings, [Get-CsTeamsMeetingPolicy](/powershell/module/teams/get-csteamsmeetingpolicy). + +You can use a new meeting policy you create or use the Global (Org-wide default) policy to turn on voice and face enrollment using the Teams admin center or PowerShell. + +By default, voice and face enrollment is disabled for all users in the organization, but admins can change this setting using PowerShell. + +To use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity Global -EnrollUserOverride Enabled +``` + +Learn more: [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) + +To turn on or off voice and face enrollment for specific users, you can either assign a custom meeting policy to the users. + +You can use PowerShell to apply the setting to a custom policy: + +```PowerShell +Grant-CsTeamsMeetingPolicy -Identity -EnrollUserOverride Enabled + +``` +Learn more: [Grant-CsTeamsMeetingPolicy](/powershell/module/teams/grant-csteamsmeetingpolicy) + +> [!NOTE] +> There isn't a way to set this in Teams admin center. You must use PowerShell. + +Learn more: [Voice recognition](/microsoftteams/rooms/voice-recognition) + +> [!NOTE] +> Voice and face enrollment settings will be moving over to **TeamsAIPolicy** cmdlet. + +#### Set up voice and face recognition profiles + +Tell your users to set up a voice and face profile in the Teams app. Each person who is attending in the meeting room (as opposed to remotely) sets up their digital voice profile in the system so that they'll be identified in the transcription. + +1. Go to your profile picture select **More options** > **Settings** and look under **Language** and make sure that your Teams language is set to **English**. To see the languages that are supported, see [Supported languages](voice-and-face-recognition.md#supported-languages-for-enrollment). +2. Under **Settings** again, select **Recognition** and then **Create voice profile.** +3. On the next screen, select the microphone, then select **Create voice profile** and read the text that is in the box. + +Learn more: [Identify in-room meeting participants](https://support.microsoft.com/office/use-microsoft-teams-intelligent-speakers-to-identify-in-room-participants-in-a-meeting-transcription-a075d6c0-30b3-44b9-b218-556a87fadc00#bkmk_setupvoiceprofile) + +### Setting up noise suppression and isolation + +#### Noise suppression + +Noise suppression is identifying non human voices or noise in an environment and then minimizing or completely eliminating them from an audio stream. Part of the AI process for voice isolation is telling the difference between background chatter in a café and a user is simply listening in and if they also want to be heard clearly if they're speaking in the meeting from their device. + +Noise suppression of background noise is turned on by default (and can be turned off) when you install the Microsoft Teams app but their microphone must also support it. If it does, noise suppression of background noise will significantly reduce the amount of background noise from a meeting participant, and it greatly enhances the microphone's audio quality. + +:::image type="content" source="../media/mtr-devices/noise-suppression.png" alt-text="Screenshot of the noise suppression setting that is turned on." lightbox="../media/mtr-devices/noise-suppression.png"::: + +However, if you want to also isolate or have Teams be able to tell the difference between background nose and a human's voice, each user will then set up a voice profile and enable voice isolation in the Teams app. + +#### Turn on voice isolation + +You can manage how voice and face profiles are used to turn off Voice Isolation for users to enhance noise and voice background reduction admins can switch off voice isolation with PowerShell in the meeting policy or users can turn it on themselves in the Teams app. + +:::image type="content" source="../media/mtr-devices/voice-isolation.png" alt-text="Screenshot showing the setting for voice isolation in the Teams app." lightbox="../media/mtr-devices/voice-isolation.png"::: + +> [!TIP] +> If you are using Bring Your Own Device (BYOD) meeting rooms and rooms audio we will turn on voice isolation automatically. + +Learn more: **[Manage voice isolation for your users](/microsoftteams/voice-isolation)** + +Voice Isolation is on by default in an organization. Check to make sure that it's on and if it isn't, you can use PowerShell to turn it on for all of your users. + +```Powershell +Set-CsTeamsMeetingPolicy -Identity Global -VoiceIsolation Enabled +``` + +Each user must set up a voice profile to turn it on in their Teams app. This can be turned off or on either before or during a meeting. + +If you have turned on Face profiles in your organization, the **Create face profile** button is available to end users. When they select the button, they can then set up their face profile that is used in meetings. + +### Turn on Copilot for your Teams users + +When you want to add Copilot to Teams, you'll need to turn it on, enable transcriptions, and meeting recordings for your end users. After you turn it on, users will see the Copilot icon and options but transcription for meetings will also need to be turned on as well. + +To pin a Copilot icon to the Teams app, see [Pin Microsoft Copilot to the navigation bar](/copilot/microsoft-365/pin-copilot). + +To turn on Copilot for your Teams users. + +1. In the [Teams admin center](https://admin.teams.microsoft.com/), go to **Meetings** from the navigation pane > **Meeting Policies**. +2. Either select an existing policy or create a new one. Select **On** or **On only with retained transcript** from the dropdown for the **Copilot** setting. + +You can use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -Copilot Enabled +``` + +Learn more: [Meeting transcription](/microsoftteams/copilot-teams-transcription) + +### Set up meeting transcription, captions, and recording + +Transcription allows users to play back meeting recordings with closed captions and review important discussion items in the transcript. Transcription and captions along with the meeting's recording help create inclusive content for viewers. It also helps Copilot to create meeting summaries, recaps, action items, and other features. + +:::image type="content" source="../media/mtr-devices/captions-and-transcripts.png" alt-text="Screenshot with captions and transcriptions settings in the Teams app." lightbox="../media/mtr-devices/captions-and-transcripts.png"::: + +#### Turn on meeting transcriptions + +To turn on meeting transcription. + +1. In the [Teams admin center](https://admin.teams.microsoft.com/), go to **Meetings** > select **Meeting Policies**. +2. Either select an existing policy or create a new one. +3. On the meeting policy page, under **Recording & transcription**, turn on **Meeting recording**. This setting is off by default. + +> [!NOTE] +> Under **Recording & transcription**, there are several other recording options that are available for you to set. Review all of the settings to ensure that they meet the needs of your organization. + +You can use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -AllowTranscription $true +``` + +Learn more: [Meeting transcription](/microsoftteams/meeting-transcription-captions) + +#### Turn on meeting recording + +Recording meetings is optional, however, there are many cases that you want to allow meetings to be recorded. Meeting recordings as you imagine is recording a stream of audio and video for a meeting, but in +the case with Copilot, it's used to help generate meeting summaries, recaps, and other information after the meeting has ended. When a meeting is recorded: + +- It gets uploaded to OneDrive (private meetings) or SharePoint (channel meetings). +- People invited to the meeting have permissions to the recording (guests and external attendees can view the recording only if the recording is explicitly shared with them). +- Microsoft Purview compliance features 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 added to various file lists across Microsoft 365: Shared with me, office.com, Recommended, Recent, etc. +- Microsoft 365 Search indexes it. + +There's also an option for recordings to have automatic transcription, so that users can play back meeting recordings with closed captions and review important discussion items in the transcript. + +You can use a new meeting policy you create or use the Global (Org-wide default) policy to turn this on using the Teams admin center or PowerShell. + +1. In the [Teams admin center](https://admin.teams.microsoft.com/), under **Meetings** > **Meeting policies**. +1. Select the policy that you want to edit. Turn **Meeting recording** On or Off. + +You can use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity \ -AllowCloudRecording Enabled +``` + +Learn more: [Meeting recording](/microsoftteams/meeting-recording?tabs=meeting-policy) + +#### Turn on Live captioning + +Teams has built-in closed captioning you can turn on from the meeting controls. Live captions can make your meeting more productive and inclusive for participants who are deaf or hard-of-hearing, have different levels of language proficiency, or the meeting participant is in a noisy place during a meeting will all benefit from live captions. + +Live captions and transcriptions can show you the text of a conversation in a Teams meeting. They can help you keep records or better understand what others are saying during a meeting. + +It's available in the desktop version of the Teams app but users can set transcription and captioning options under **Settings** > **Captions and transcripts** in the Teams app. + +:::image type="content" source="../media/mtr-devices/captions-and-transcripts.png" alt-text="Screenshot with the captions and transcriptions settings." lightbox="../media/mtr-devices/captions-and-transcripts.png"::: + +Learn more: [Live transcriptions]() + +If your organization is using OneDrive for Business and SharePoint for meeting recordings, you should turn on **Allow transcription** in the Teams meeting policy and turn on the **Always show live captions in meeting** in the Teams app and encourage your users to start transcription in every meeting. This will make captions available in the post-meeting recording when it's generated by Copilot as well. + +1. In the [Teams admin center](https://admin.teams.microsoft.com/). +2. Under **Meetings**, select **Meeting Policies**. Either select an +existing policy or create a new one. +3. On the meeting policy page, under **Recording & transcription**, set **Live captions** to **Off, but +organizers and co-organizers can turn them on. + +You can use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -AllowTranscription $true +``` + +#### Turn on Live transcriptions + +By default, transcripts are shown in the language spoken during a meeting or event. Live translated transcription allows your users to translate the meeting or event transcript into the language they're most comfortable with. + +You can use a new meeting policy you create or use the Global (Org-wide default) policy to turn this on using the Teams admin center or PowerShell. + +To turn on Live transcription, **Transcription** but be set to **On** +first. + +1. In the [Teams admin center](https://admin.teams.microsoft.com/). +2. Under **Meetings**, select **Meeting Policies**. Either select an existing +policy or create a new one. +3. On the meeting policy page, under **Recording & transcription**, turn on **Meeting recording**. This +setting is off by default. + +You can use PowerShell to turn this on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -Copilot Enabled -AllowTranscription $true +``` + +Learn more: [Meeting transcription and captions](/microsoftteams/meeting-transcription-captions) + +### Turn it on so speakers will be identified in meetings + +In meeting transcripts, live transcripts, captions and in meeting recaps using Copilot, you want users to be able to identify the person that is talking during the meeting or attribution. By default, this is turned on at the organization level (Global (Org-wide default) policy), but in the case you want to turn this off for another part of your organization, you can create a new meeting policy. + +You can optionally tell users to go verify that it's turned on by going to in the Teams app to **Settings** > **Captions and transcripts** > **Automatically identify me in meeting captions and transcripts** and make sure it's turned on. + +:::image type="content" source="../media/mtr-devices/auto-id.png" alt-text="Screenshot with the 'automatically ID me in meetings' setting." lightbox="../media/mtr-devices/auto-id.png"::: + +**Speaker Attribution Modes**: + +- **Enabled**: Speakers are identified in transcription. +- **EnabledUserOverride**: Speakers are identified in transcription if enabled, however, users can change this setting and choose not to be identified in the Teams profile settings. +- **DisabledUserOverride:** Speakers are not identified in the transcription. If enabled, users can change this setting and choose to be identified in their Teams profile settings. +- **Disabled**: Teams won't identify and display speaker names next to audio streams in meetings. + +You can use PowerShell to set this: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity Global -SpeakerAttributionMode Enabled +``` + +### To identify in-room participants in a meeting transcription + +Using [Microsoft Teams Rooms](https://rooms.microsoft.com/) on Windows you can hold meetings where in-room participants can be identified in live transcription and in meeting transcripts. When you enable Intelligent Speaker, during the meeting all participants can then easily see who's saying what, and the post-meeting transcript identifies both remote and in-room attendees. + +Learn more: [Identify in-room meeting participants](https://support.microsoft.com/office/use-microsoft-teams-intelligent-speakers-to-identify-in-room-participants-in-a-meeting-transcription-a075d6c0-30b3-44b9-b218-556a87fadc00#bkmk_setupvoiceprofile) + +#### Enable Intelligent Speaker + +Voice profile data is used in any meeting with an Intelligent Speaker. However, each user must set up a voice and face profile in the Teams app. See, [Voice and face recognition](voice-and-face-recognition.md) or [Set up voice and face profiles](copilot-admin-mtr.md#set-up-voice-and-face-recognition-profiles). + +> [!NOTE] +> Intelligent Speaker is only available on Microsoft Teams Rooms for Windows. + +Enabling people recognition or Intelligent Speaker requires you to set the CsTeamsMeetingPolicy to let individual voice and face profiles to be used for recognition in meetings. + +Use PowerShell to turn it on: + +```PowerShell +Set-CsTeamsMeetingPolicy -Identity -RoomAttributeUserOverride Attribute +``` + +Learn more: [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) + +> [!NOTE] +> No special microphones are needed to use this feature. Microphones that are included in Teams Rooms for Windows devices all support Intelligent Speaker. However, there are also addtional hardware devices that can be used along side of Teams Rooms that support Intelligent Speaker. To see which devices are certified and can be used, see [Certified Intelligent Speakers](certified-hardware.md?tabs=Devices). + +## Related articles + +- [Manage Microsoft 365 Copilot settings in the Microsoft 365 admin center](/copilot/microsoft-365/microsoft-365-copilot-page) +- [Manage Microsoft 365 Copilot in Teams meetings and events](/microsoftteams/copilot-teams-transcription) +- [Microsoft 365 reports in the admin center – Microsoft 365 Copilot usage](/microsoft-365/admin/activity-reports/microsoft-365-copilot-usage) \ No newline at end of file diff --git a/Teams/rooms/create-resource-account.md b/Teams/rooms/create-resource-account.md index 0eb38a495b..572d7e4cbc 100644 --- a/Teams/rooms/create-resource-account.md +++ b/Teams/rooms/create-resource-account.md @@ -1,5 +1,5 @@ --- -title: Create resource accounts for rooms and shared Teams devices +title: How to create and configure resource accounts for Teams Rooms and panels author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -20,50 +20,52 @@ f1.keywords: ms.localizationpriority: medium ms.custom: seo-marvel-apr2020 ms.assetid: f09f4c2a-2608-473a-9a27-f94017d6e9dd -description: Read this article for information on how to create resource accounts for rooms and shared devices, including Microsoft Teams Rooms, Teams Rooms on Surface Hub, and hot-desking on Teams displays. +description: Read this article for information on how to create resource accounts for Teams rooms and shared devices. These devices include Microsoft Teams Rooms, Teams panels, and Surface Hub. --- -# Create and configure resource accounts for rooms and shared Teams devices +# How to create and configure resource accounts for Teams Rooms and panels -This article provides steps to create resource accounts for shared spaces and devices, and it includes steps to configure resource accounts for Microsoft Teams Rooms on Windows, Teams Rooms on Android, Teams Rooms on Surface Hub, and hot-desking on Teams displays. +This article provides steps to create resource accounts for shared spaces and devices, and it includes steps to configure resource accounts for Microsoft Teams Rooms on Windows, Teams Rooms on Android, & Teams panels. -Microsoft 365 resource accounts are mailbox and Teams accounts that are dedicated to specific resources, such as a room or projector. These resource accounts can automatically respond to meeting invites using rules you define when they're created. For example, if you have a common resource such as a conference room, you can set up a resource account for that conference room that will automatically accept or decline meeting invites depending on its calendar availability. +Microsoft 365 resource accounts are mailbox and Teams accounts that are dedicated to specific resources, such as a room or projector. These resource accounts can automatically respond to meeting invites using rules you define when they're created. For example, if you have a common resource such as a conference room, you can set up a resource account for that conference room which automatically accepts or declines meeting invites depending on its calendar availability. -Every resource account is unique to a single Microsoft Teams Rooms installation or Teams display hot-desking implementation. +Every resource account is unique to a single Microsoft Teams Rooms installation or Teams device implementation. -[!INCLUDE [m365-teams-resource-account-difference](../includes/m365-teams-resource-account-difference.md)] +[!INCLUDE [mtr-device-config-account-include](../includes/m365-teams-resource-account-difference.md)] > [!NOTE] -> If using Microsoft Teams panels, the Teams Rooms resource account signs in to both Teams Rooms and associated Teams panels. +> If using Microsoft Teams panels, the same Teams Rooms resource account signs in to the Teams Rooms device and any associated Teams panels. ## Before you begin ### Requirements -Depending on your environment, you need one or more roles to create resource accounts. +You may need one or more roles to create, license, and configure resource accounts. | Environment | Required Roles | |-----|-----| -|Microsoft Entra ID |Global Administrator or User Administrator | -|Active Directory |Active Directory Enterprise Admins, Domain Admins, or have delegated rights to create users. Microsoft Entra Connect Sync rights. | +|Microsoft Entra ID |Global admin or User admin | +|On-premises Active Directory |Active Directory Enterprise Admins, Domain Admins, or have delegated rights to create users | |Exchange Online |Global Administrator or Exchange Administrator | |Exchange Server |Exchange Organization Management or Recipient Management | - -> [IMPORTANT] -> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. +|Licensing |Global admin or Billing admin | +|Teams |Global admin or Teams admin | > [!IMPORTANT] -> If you're creating resource accounts for Teams Rooms, the resource account's UPN must match the SMTP address of the resource account. +> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. -### What license do you need? +## Get the right license [!INCLUDE [mtr-device-config-license-include](../includes/mtr-device-config-license-include.md)] -## Create a resource account +## Create resource account & assign the license [!INCLUDE [mtr-device-config-account-include](../includes/mtr-device-config-account-include.md)] -## Configure mailbox properties +> [!IMPORTANT] +> If you're creating resource accounts for Teams Rooms, the resource account's UPN must match the SMTP address of the resource account. + +## Configure Exchange mailbox properties [!INCLUDE [mtr-device-config-mailbox-include](../includes/mtr-device-config-mailbox-include.md)] @@ -71,29 +73,33 @@ Depending on your environment, you need one or more roles to create resource acc [!INCLUDE [mtr-device-config-password-include](../includes/mtr-device-config-password-include.md)] -## Assign a meeting room license - -[!INCLUDE [mtr-device-config-assign-include](../includes/mtr-device-config-assign-include.md)] - ## Next steps -### Meeting policies +### Teams policies [!INCLUDE [mtr-device-config-policies-include](../includes/mtr-device-config-policies-include.md)] ### Calling -There are no unique requirements to enable calling with resource accounts. You enable the resource account for calling in the same way you enable a regular user. +Resource accounts can be enabled for public switched telephone network (PSTN) the same way you enable a regular user. For more information, see [Calling in Microsoft Teams](/microsoftteams/cloud-voice-landing-page). We also recommend disabling voicemail for shared devices with a calling policy. For more information, see [Calling policies in Teams](../teams-calling-policy.md). + +### Conditional Access + +Conditional access controls resource accounts for Teams devices. You may need to make modifications to your existing policies to ensure your resource accounts are secure and functional. For more information on supported configurations and changes you may need to make, see [Conditional access for Teams devices](/microsoftteams/rooms/conditional-access-and-compliance-for-devices). > [!NOTE] -> We recommend turning off voice mail for shared devices by assigning a calling policy to the device resource accounts. See [Calling and call-forwarding in Teams](../teams-calling-policy.md) for more information. +> Teams shared devices do not support Security defaults in Microsoft Entra ID. Use conditional access to secure your environment and Teams shared devices. + +### Resource Account Sign in Test + +Use this tool: [Teams Rooms sign in test](https://testconnectivity.microsoft.com/tests/TeamsMTRDeviceSignIn/input) to test that your Teams Rooms resource account is configured for successful sign on. + +### Exchange Room Finder & Microsoft Places [!INCLUDE [mtr-device-config-calendar-include](../includes/mtr-device-config-calendar-include.md)] ## Related articles -[Configure accounts for Microsoft Teams Rooms](rooms-configure-accounts.md) - [Plan for Microsoft Teams Rooms](rooms-plan.md) [Deploy Microsoft Teams Rooms](rooms-deploy.md) diff --git a/Teams/rooms/digital-signage.md b/Teams/rooms/digital-signage.md index b3dbc922a0..89ac780e5b 100644 --- a/Teams/rooms/digital-signage.md +++ b/Teams/rooms/digital-signage.md @@ -23,9 +23,7 @@ description: Learn more about how --- # Configure digital signage on Teams Rooms -This feature is only available for Technology Adoption Program (TAP) Preview and early adopter customers. - -Digital signage on Microsoft Teams Rooms expands organizational communications into your meeting spaces, enabling you to inform, connect, and engage your teams. When your Teams Rooms devices are not used for meetings or presentations, they can be configured to display dynamic content and relevant information like how to guides, company or organizational news, upcoming events, and more in signage mode. You can adjust when signage mode is activated and deactivated, including whether signage mode will adhere to the operating system's screen time-out setting. When your Teams Rooms devices are in signage mode, signage content appears in full screen on the front-of-room displays. You have the option to show the Teams Rooms banner so that users can see the room information and calendar preview alongside the signage content on the front-of-room displays. Tapping the touch console during signage mode seamlessly returns the user to the home screen. +Digital signage on Microsoft Teams Rooms expands organizational communications into your meeting spaces, enabling you to inform, connect, and engage your teams. When your Teams Rooms devices aren't used for meetings or presentations, they can be configured to display dynamic content and relevant information like how to guides, company or organizational news, upcoming events, and more in signage mode. You can adjust when signage mode is activated and deactivated, including whether signage mode will adhere to the operating system's screen time-out setting. When your Teams Rooms devices are in signage mode, signage content appears in full screen on the front-of-room displays. You have the option to show the Teams Rooms banner so that users can see the room information and calendar preview alongside the signage content on the front-of-room displays. Tapping the touch console during signage mode seamlessly returns the user to the home screen. :::image type="content" source="media/digital-signage/ds-meeting-enlarged-console.jpg" alt-text="Teasms Rooms homescreen." lightbox="media/digital-signage/ds-meeting-enlarged-console.jpg"::: @@ -42,7 +40,7 @@ Configuring digital signage for your tenant requires the following: Currently, digital signage isn't yet available on the following clients and environments: - Teams Rooms on Android (MTR-A) -- Multi-tenant Management portal (MTMA) +- Multitenant Management portal (MTMA) - Government Community Cloud (GCC) - Government Community Cloud High (GCC-H) - Department of Defense (DoD) @@ -54,7 +52,7 @@ To enable digital signage for your Teams Rooms devices, you need to follow these 1. Manage permissions for digital signage. 1. Enable digital signage for the tenant. 1. Add signage sources for the tenant, including enabling native third-party integrations as desired. -1. Assign a source and settings to rooms which will register rooms onto supported third-party content management systems (if applicable). +1. Assign a source and settings to rooms which register rooms onto supported third-party content management systems (if applicable). > [!IMPORTANT] > Before you enable and set up digital signage, consider your privacy and compliance requirements. See [Adding an external signage source](#step-3---adding-an-external-signage-source) for more information. @@ -62,7 +60,7 @@ The following sections show you how to complete each step. ## Step 1 - Managing permissions for digital signage -By default, Microsoft 365 Global Admins and Teams Rooms Pro Managers have the digital signage *tenant* management and digital signage *room* management permissions which grants the ability to perform the following actions respectively: +By default, Microsoft 365 Global Admins and Teams Rooms Pro Managers have the digital signage *tenant* management and digital signage *room* management permissions which grant the ability to perform the following actions respectively: > [!IMPORTANT] > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. @@ -74,7 +72,7 @@ By default, Microsoft 365 Global Admins and Teams Rooms Pro Managers have the di - Set default signage source and settings for the tenant. - Digital signage *room* management permission - - Enable and disable digital signage for a room. + - Enable, disable, and reset digital signage for a room. - Select an existing signage source from the list of sources that has been added to the tenant for a room. - Modify signage settings for a room. @@ -83,7 +81,7 @@ Microsoft 365 Global Admins and Teams Rooms Pro Managers can assign additional u > [!IMPORTANT] > Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. -1. Log in to **Teams Rooms Pro Management** portal > go to **Settings** > **Roles** > select **Create** **role** > enter a unique name and description for the role > select **Next**. +1. Sign in to **Teams Rooms Pro Management** portal > go to **Settings** > **Roles** > select **Create** **role** > enter a unique name and description for the role > select **Next**. 1. Under **Role permissions**, select **Digital signage tenant management: View, Modify** and/or **Digital signage room management: Modify** as desired > select **Next** > enter a name and description for the assignment > select **Next**. 1. Under **Assign members**, search and/or select user(s) and/or security group(s) that will be part of this role with the selected permissions > select **Next**. 1. Under **Assign scope**, search and/or select room(s) and/or room group(s) that this role can manage > select **Next** > **Add new role**. @@ -93,9 +91,9 @@ Microsoft 365 Global Admins and Teams Rooms Pro Managers can assign additional u ## Step 2 - Enabling digital signage -To enable digital signage for your tenant, log in to **Teams Rooms Pro Management** portal > go to **Settings** > **Digital signage** > toggle On **Digital signage** on the digital signage tenant management page. +To enable digital signage for your tenant, sign in to **Teams Rooms Pro Management** portal > go to **Settings** > **Digital signage** > toggle On **Digital signage** on the digital signage tenant management page. -Next, you'll need to add a signage source. You can add multiple signage sources for your tenant and assign a different source per room or room group. Supported signage sources include third-party digital signage providers and web URLs. Native integrations with the following trusted third-party digital signage providers are available: +Next, you need to add a signage source. You can add multiple signage sources for your tenant and assign a different source per room or room group. Supported signage sources include third-party digital signage providers and web URLs. Native integrations with the following trusted third-party digital signage providers are available: - [Appspace](https://www.appspace.com/microsoft-teams-rooms/) @@ -106,7 +104,11 @@ Next, you'll need to add a signage source. You can add multiple signage sources ## Step 3 - Adding an external signage source -To enable a third party integration, from the digital signage tenant management page, select **Add source** > enter a unique name and description for this source > select **Next** > choose the third party system of your choice > enter a valid integration ID that you must obtain from the third-party system > select **Validate** > **Next** > acknowledge terms of use > select **Next** > review and finish > select **Submit**. +To enable a third party integration, from the digital signage tenant management page, select **Add source** > enter a unique name and description for this source > select **Next** > choose the third party system of your choice > enter a valid integration ID that you must obtain from the third-party system > select **Validate** > **Next** > acknowledge terms of use > select **Next** > review and finish > select **Submit**. You can find the setup instructions for the following supported third party providers below: + +- [Appspace](https://docs.appspace.com/latest/devices-app/advanced-registration-microsoft-meeting-room-devices/) + +- [XOGO](https://www.xogo.io/microsoft-teams-rooms-setup) If you don’t use any of the supported third party providers, you can set web URLs as a signage source. To ensure the web application loads successfully on your Teams Rooms device, the URL must meet the following requirements: @@ -124,15 +126,18 @@ To add a web URL as signage source, from the digital signage tenant management p > By adding a signage source to your tenant, you accept full responsibility for all signage content that is displayed in your rooms and acknowledge that Microsoft isn't responsible for the signage content that is displayed nor the data that may be transferred out of our system to the external signage source. > Supported third party providers will receive the name and email of the specific rooms where they have been assigned as the signage source, allowing seamless integration. -## Step 4 - Assigning a signage source and settings +## Step 4 - Assigning signage source and settings Once you've added signage source(s) for your tenant, you can now assign a signage source and settings to your rooms. If you're assigning one of the trusted third party providers as a signage source to a room, this step automatically registers that specific room onto the third-party content management system. You can assign a signage source and settings for multiple rooms or room groups at the tenant level or for individual rooms at a room level: -- Tenant-level - from the digital signage tenant management page, choose a signage source > select **Assign to rooms** > confirm the pre-selected source that you intend to assign > select **Next** > review or modify signage settings > select **Next** > search or select room(s) and/or room group(s) where you'd like to assign your chosen source and settings > select **Next** > review and finish > select **Submit**. -- Room-level - navigate to the specific room's settings. Go to **Rooms** > choose a specific room > select **Settings** > **Digital signage** > toggle ON **Digital signage** > modify signage settings as desired > choose a signage source from any of the sources added to the tenant > select **Apply**. +- Tenant-level - from the digital signage tenant management page, choose a signage source > select **Assign to rooms** > confirm the preselected source that you intend to assign > select **Next** > review or modify signage settings > select **Next** > search or select room(s) and/or room group(s) where you'd like to assign your chosen source and settings > select **Next** > choose when the configuration will be applied > review and finish > select **Submit**. +- Room-level - navigate to the specific room's settings. Go to **Rooms** > choose a specific room > select **Settings** > **Digital signage** > toggle ON **Digital signage** > modify signage settings as desired > choose a signage source from any of the sources added to the tenant > select **Apply** > choose when the configuration will be applied > select **Submit**. + +> [!IMPORTANT] +> Whether you choose to apply the settings now or during the maintenance window, the room must be online, connected, and signed into the Teams Rooms app for settings to be applied. Note that after a room restarts, it takes about 10-15 minutes for the Teams Rooms Pro Management agent to be connected. > [!NOTE] -> Settings will only be applied during the maintenance window. To find the setting application results, go to **Rooms** > select **Export** **all** and filter through the rooms and settings in the CSV file. +> To find the setting application results, go to **Rooms** > select **Export** **all** and filter through the rooms and settings in the CSV file. Once settings have been applied, rooms are now registered with the third party provider. You can manage and update the content that plays in the room directly from the third party content management system. > [!TIP] @@ -150,7 +155,7 @@ While each room or room group can be assigned with a unique configuration, you c - **Display period** - from the digital signage tenant management page, select **Preferences** > - **Activation timer** - enter the number of minutes (between 1 to 100) that a device has been idle before signage mode activates. - **Deactivation** **timer** - enter the number of minutes (between 0 to 100) before a scheduled meeting starts when signage mode deactivates and returns to the home screen. - - **Screen timeout** - toggle On or Off **Allow screen timeout when device is idle** as desired. Turn On to adhere to the operating system's screen timeout settings (i.e., the screen light goes out regardless of when signage mode is activated). Turn Off to bypass the operating system's screen timeout settings (i.e., the screen remains lit up on idle devices when signage mode is activated). + - **Screen timeout** - toggle On or Off **Allow screen timeout when device is idle** as desired. Turn On to adhere to the operating system's screen timeout settings (that is, the screen light goes out regardless of when signage mode is activated). Turn Off to bypass the operating system's screen timeout settings (that is, the screen remains lit up on idle devices when signage mode is activated). > [!NOTE] > If you add video content in your signage playlist, the screen timeout setting might not consistently honored due to underlying operating system behavior for video playback. @@ -162,22 +167,24 @@ While each room or room group can be assigned with a unique configuration, you c When using a supported third party digital signage provider as the signage source of a room, you can proactively monitor the health of digital signage in the room using the new digital signage health signal when you expand the display signal. To view the digital signage health signal: go to **Rooms** > choose the specific room > select **Status** > toggle On **Show all signals** > expand **Display** > select **Digital signage**. Alternatively, go to **Incidents** > expand **Display** > select **Digital** **signage**. -When there is an issue with the third party player or signage content, the issue description, and actions you can take to resolve the issue (if applicable) will be visible in the messages. Depending on the nature of the issue, the Teams Rooms experience will vary: +When there's an issue with the third party player or signage content, the issue description, and actions you can take to resolve the issue (if applicable) will be visible in the messages. Depending on the nature of the issue, the Teams Rooms experience varies: -- If there is no signage content available to play in a room whether caused by a system error (i.e., server error, offline) or human error (i.e., no content assigned to the room, no cached content), signage mode will remain deactivated until the issue is resolved at the next device restart. The room will remain on the home screen to avoid showing error messages or empty screens on front-of-room displays. Alerts will be provided on the Teams Rooms Pro Management portal and the third party content management system as appropriate. -- If there is signage content available to play in a room (i.e., cached content) despite an error, signage mode will continue to activate per the activation timer. Any applicable alerts will still be provided on the Teams Rooms Pro Management portal and/or the third party content management system. +- If there's no signage content available to play in a room whether caused by a system error (that is, server error, offline) or human error (that is, no content assigned to the room, no cached content), signage mode will remain deactivated until the issue is resolved at the next device restart. The room remains on the home screen to avoid showing error messages or empty screens on front-of-room displays. Alerts are provided on the Teams Rooms Pro Management portal and the third party content management system as appropriate. +- If there's signage content available to play in a room (i.e., cached content) despite an error, signage mode continues to activate per the activation timer. Any applicable alerts will still be provided on the Teams Rooms Pro Management portal and/or the third party content management system. > [!NOTE] > The digital signage health signal is not available for rooms with a web URL (custom option) signage source. ### Help and support -If you have issues with configuring signage settings on your Teams Rooms device using the Teams Rooms Pro Management portal, you can contact Microsoft support. For issues specific to the signage content displayed in your rooms, supported third party providers must be contacted first for assistance. If your digital signage provider determines that the underlying issue requires Microsoft's attention, they can route the issue to Microsoft on your behalf or advise you to open a ticket directly with Microsoft. +For issues with getting a valid integration ID, how your Teams Rooms devices appear on the third party content management system, or specific problems with the signage content displayed in your rooms, you must contact your third party provider for assistance. If your digital signage provider determines that the underlying issue requires Microsoft's attention, they can route the issue to Microsoft on your behalf or advise you to open a ticket directly with Microsoft. For other issues with configuring digital signage settings using the Teams Rooms Pro Management portal, you may contact Microsoft support. ## Known issues and limitations |Issue or limitation|Workaround| | -------- | -------- | -|Settings are only applied during the maintenance window.|There is no way to immediately apply the settings.| -|Regardless of the signage source, the digital signage health signal isn't available.|If digital signage has been enabled but signage mode isn't activated after the maintenance window, submit an issue using **Report a problem**.| - +|Regardless of the signage source, the digital signage health signal isn't available on the Teams Rooms Pro Management portal.|There's no workaround. Users must report issues for you to be alerted of digital signage issues in the room.| +|When the **Apply now** option for applying settings is selected and the room is in use, the settings won't be applied immediately to avoid disruption in the room. Rather, we'll retry to apply the settings during the maintenance window.|When settings fail to apply immediately, you can either wait for the maintenance window or push another update when the room is no longer in use to override the settings scheduled to be applied during the maintenance window.| +|There's a 2-hour delay before changes to digital signage settings appear in the **Export all** report.|Navigate to the room's digital signage settings page to view the latest settings of the room.| +|In some instances, assigning an Appspace channel to a room results in a failure to load signage mode in the room.|To troubleshoot, run the **Restart device-Clear cache** action with the **Delete Teams cache** option selected on the Teams Rooms Pro Management portal for the impacted room. If the issue persists, contact Appspace.| +|Rooms with dual displays that use Appspace may see a black screen on one of the displays when the Appspace player loads for the first time.|When a black screen is showing on of one of the dual displays, tap the touch console to exit signage mode. When the room goes back to the home screen, the next time signage mode loads, both screens will properly show signage mode.| diff --git a/Teams/rooms/managed-meeting-rooms-portal.md b/Teams/rooms/managed-meeting-rooms-portal.md index 9a4d8dec2f..316aead4dd 100644 --- a/Teams/rooms/managed-meeting-rooms-portal.md +++ b/Teams/rooms/managed-meeting-rooms-portal.md @@ -25,7 +25,7 @@ f1keywords: ## Overview -The Teams Rooms Pro Management portal provides a view of the health of your meeting rooms and helps to facilitate your existing monitoring tools and practices. This feature is only available in public or commercial cloud. It's not available in GCC, GCC-H, or DoD government clouds. +The Teams Rooms Pro Management portal provides a view of the health of your meeting rooms and helps to facilitate your existing monitoring tools and practices. This feature is only available in the commercial & GCC clouds. It's not available in GCC-H or DoD clouds. The scope of the monitoring is: diff --git a/Teams/rooms/meetings-with-SIP-H323-devices.md b/Teams/rooms/meetings-with-sip-h323-devices.md similarity index 66% rename from Teams/rooms/meetings-with-SIP-H323-devices.md rename to Teams/rooms/meetings-with-sip-h323-devices.md index 0ef3719f0a..b2877f4784 100644 --- a/Teams/rooms/meetings-with-SIP-H323-devices.md +++ b/Teams/rooms/meetings-with-sip-h323-devices.md @@ -1,10 +1,10 @@ --- -title: SIP and H.323 calling with Teams Rooms +title: SIP and H.323 dialing with Teams Rooms author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: naforer -ms.date: 09/06/2024 +ms.date: 10/30/2024 ms.topic: article audience: Admin ms.service: msteams @@ -21,28 +21,28 @@ ms.localizationpriority: medium description: Learn about how to set up Teams Rooms to receive and place calls using SIP and H.323. --- -# SIP and H.323 Calling with Teams Rooms +# SIP and H.323 Dialing with Teams Rooms -SIP and H.323 calling is available on Microsoft Teams Rooms on Windows devices licensed with a Microsoft Teams Rooms Pro license. This functionality uses a Cloud Video Interop provider which you can enable in your tenant. +SIP and H.323 dialing is available on Microsoft Teams Rooms on Windows devices licensed with a Microsoft Teams Rooms Pro license. This functionality uses a specific SIP-supporting plan from a Cloud Video Interop provider which you can enable in your tenant. -This feature enables calls with audio, video, and screen sharing between Teams Rooms devices and other conferencing endpoints that support either the SIP or the H.323 protocol. The SIP and H.323 endpoints can be either internal or external to your organization. SIP and H.323 dialing is disabled by default in your organization. You must follow the steps in this document to enable this functionality using Microsoft Teams PowerShell. SIP & H.323 calls from your Teams Rooms device are Teams calls to the Microsoft 365 cloud, which then communicates with your provider. No other network or firewall rules are required to enable this functionality if you already have working Teams Rooms devices deployed. +This feature allows Teams Rooms devices to make audio, video, and screen sharing calls with other conferencing endpoints that support SIP or H.323 protocols, whether internal or external to your organization. By default, SIP and H.323 dialing is disabled. To enable it, follow the steps in this document using Microsoft Teams PowerShell. SIP and H.323 calls from Teams Rooms devices are routed through the Microsoft 365 cloud to your plan provider, requiring no additional network or firewall rules if you already have working Teams Rooms devices. -If you have multiple Teams Rooms all with a Pro licenses deployed in your organization, you can configure SIP and H.323 dialing for one or all of your Teams Rooms. +If you have multiple Teams Rooms all with Pro licenses deployed in your organization, you can configure SIP and H.323 dialing for one or all of those Teams Rooms. > [!IMPORTANT] > -> This feature is only available for Microsoft Teams Rooms devices licensed with a Teams Rooms Pro license and is only availble for Teams Rooms on Windows device. This won't work with Teams Rooms on Android devices. +> This feature is exclusive to Microsoft Teams Rooms devices with a Teams Rooms Pro license and is only compatible with Teams Rooms on Windows devices. It does not support Teams Rooms on Android devices. ## Implementation Requirements -To enable your Teams Rooms device to use SIP and H.323 calling: +To enable your Teams Rooms device to use SIP and H.323 dialing: 1. The Teams Rooms resource account must have a Teams Rooms Pro license assigned. -2. You must have an agreement with one of the certified [Cloud Video Interop providers](../cloud-video-interop.md) (CVI) which offer SIP & H.323 calling capabilities, reference that link for which providers enable calling from Teams Rooms. -3. Information from your CVI provider on the "AreaCode" to use when configuring SIP & H.323 calling in Microsoft Teams. The "AreaCode" may match the "TenantKey" used when you configured CVI. -4. You must create and assign a Teams Room Video Teleconferencing Policy your Teams Rooms resource accounts. +2. You need an agreement with one of the certified [Cloud Video Interop providers](../cloud-video-interop.md) (CVI) which offer SIP & H.323 dialing capabilities. Refer to that link for a list of providers that enable SIP & H.323 dialing from Teams Rooms. +3. You need information from your SIP-supporting provider about the "AreaCode" to use when configuring SIP & H.323 dialing in Microsoft Teams Rooms. If you have CVI enabled, the "AreaCode" may match the "TenantKey" used when you configured it. +4. You must create and assign a SIP & H.323 Video Teleconferencing Policy to your Teams Rooms resource accounts. -## How to configure a SIP & H.323 Video Teleconferencing Policy +## How to configure a SIP / H.323 Video Teleconferencing Policy The Teams Room Video Teleconference Policy enables SIP & H.323 calling on Teams Rooms devices. You must first create a new Teams Room Video Teleconferencing policy and set the parameters to enable SIP and H.323 dialing. If you have multiple CVI providers in your tenant, you can configure multiple Video Teleconferencing policies, and assign different policies to different Teams Room resource accounts. Although you can only have one Global policy, individual policies take precedence if directly assigned to an account. diff --git a/Teams/rooms/proximity-join.md b/Teams/rooms/proximity-join.md index e2657f1640..5d6310bb5a 100644 --- a/Teams/rooms/proximity-join.md +++ b/Teams/rooms/proximity-join.md @@ -18,20 +18,22 @@ appliesto: - Microsoft Teams ms.localizationpriority: medium search.appverid: MET150 -description: Learn how to use the Proximity Join feature using Bluetooth and Ultrasound connnectivity to nudge a Microsoft Teams Room console into a meeting you are having for an optimum meeting room experience. +description: Learn how to use the Proximity Join feature using Bluetooth and Ultrasound connectivity to nudge a Microsoft Teams Room console into a meeting you're having for an optimum meeting room experience. f1keywords: NOCSH --- # Proximity Join using Bluetooth and ultrasound -Proximity Join is a feature that lets you use your Teams app on a desktop or mobile device to invite or nudge a Microsoft Teams Rooms console into a Teams meeting. Before you nudge the Teams Rooms console into the meeting, the room doesn't have to be already invited or added to the meeting. This feature uses wireless technologies that can be individually turned on or off depending on the requirements of the environment including: +Proximity Join is a feature that lets you use your Teams app on a desktop or mobile device to invite or nudge a Microsoft Teams Room into a Teams meeting. The Teams Room doesn't need to be invited to the meeting to be joined using proximity join. This feature uses wireless technologies that can be individually turned on or off depending on the requirements of the environment including: - [Bluetooth](#bluetooth) -- [Ultrasonic sound (Ultrasound)](#ultrasound) +- [Ultrasound (Ultrasonic)](#ultrasound) -The end user experience is the same if Bluetooth or ultrasound are used for Proximity Join to join a meeting. If they're both turned on, they operate together and in parallel. A Teams Room that is found with ultrasound turned on is always put in the meeting's prejoin screen at the top of the list of nearby rooms. You can see it's available in the room audio option. Teams Rooms that are found using Bluetooth are listed after the room that have ultrasound turned on in that list. +The end user experience is the same if Bluetooth or ultrasound are used for Proximity Join. If they're both turned on, they operate together to provide the most accuracy. A Teams Room that is found with ultrasound turned on is always put in the meeting's prejoin screen at the top of the list of nearby rooms (under the room audio option). Teams Rooms that are found using Bluetooth are listed after the room that have ultrasound turned on in that list. -Once a connection is established between a personal laptop or mobile device with the Teams app and a Teams Room console, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. +When a user's laptop or mobile device brings a Teams Rooms in using Proximity Join or if Proximity Join detects a user is joining while in a Teams Room already in the meeting, the user's video won't appear in the room's display, and the room's video stream is hidden on the personal device's meeting stage. Users can override the automatic hiding behavior by using the pin or spotlight functionality of Teams Meetings. + +Proximity join doesn't require a direct network connection between a user personal devices and the Teams Rooms device, all communication takes place through Microsoft Teams. ## Bluetooth @@ -46,22 +48,20 @@ Ultrasound signaling is available on Microsoft Teams Rooms on Windows, beacons f > [!NOTE] > Proximity Join using ultrasound isn't currently available for Teams Rooms on Android. -The Proximity Join via ultrasound works by emitting an ultrasonic (19.5 kHz - 21.5 kHz) signal from the Teams Room console that isn't audible to humans. It's more accurate than Bluetooth because at reasonable volume, it won't penetrate through walls. Plus, the signal is paused when the Microsoft Teams Room is either in a meeting or HDMI ingest is active. For example, you walk into a conference room with ultrasound turned on the Teams Rooms console, and you want to join your meeting to the Teams Room, you see it in the meeting's prejoin screen in the list of available rooms because those rooms are sorted and listed at the top of the screen. This lets someone select the exact Teams Rooms console and conference room they want to use for their meeting. +The Proximity Join using ultrasound works by emitting an ultrasonic (19.5 kHz - 21.5 kHz) signal from the Teams Room console that isn't audible to humans. It's more accurate than Bluetooth because at reasonable volume, it won't penetrate through walls. Plus, the signal is paused when the Microsoft Teams Room is either in a meeting or HDMI ingest is active. For example, you walk into a conference room with ultrasound turned on the Teams Rooms console, and you want to join your meeting to the Teams Room, you see it in the meeting's prejoin screen in the list of available rooms because those rooms are sorted and listed at the top of the screen. This lets someone select the exact Teams Rooms console and conference room they want to use for their meeting. > [!NOTE] > Room Remote can't be used with ultrasound only because the ultrasound beacon is paused while the Teams Room is in a call. Room Remote can't use ultrasound to verify that the personal device is in proximity with the room, so Room Remote won't work if only ultrasound is turned on. > [!CAUTION] -> Some younger people and animals with sensitive hearing may be able to hear it. In our testing, this sound hasn't been distressing, but take note if young people or animals are in your meeting room environment. We recommend that younger people and animals aren't present in the meeting room environments. If the beacon can be heard outside of the space for which it is intended to represent, speak with your admin. While Microsoft works with partners to ensure volume levels are adequately capped, your admin may have overridden the volume for ultrasound emission on a console or audio peripheral that will in turn may have unintended consequences. +> People or animals with sensitive hearing may be able to hear the ultrasound tones. In our testing, this sound hasn't been distressing, and is only output prior to a call being initiated but take note if those who may hear the ultrasound tones are present in your environment to decide if this feature should be enabled or not. ### Ultrasound supported devices |Sender (Consoles for Teams Rooms on Windows)|Receiver| | -------- | -------- | |Crestron UC-2 |Teams on Windows (minimum version 24193.1805.3040.8975)| -|Crestron MercuryX |Teams on MacOS (minimum version 24193.1707.3028.4282) | -|Lenovo Hub 500|| -|Lenovo ThinkSmart Audio G2|| +|Crestron MercuryX |Teams on macOS (minimum version 24193.1707.3028.4282) | |Logi Tap|| @@ -73,7 +73,7 @@ There are multiple ways and tools you can use to manage Proximity Join settings > [!NOTE] > The settings for ultrasound don't apply to Teams Room on Android but the Bluetooth settings are available for those devices. -### [Teams Rooms Pro portal](#tab/portal) +### [Pro Management Portal](#tab/portal) Management of proximity features is available in the Teams Rooms Pro Management portal: @@ -83,9 +83,8 @@ Management of proximity features is available in the Teams Rooms Pro Management - Automatically accept proximity-based meeting invitations -- Enable ultrasound beaconing - - - Remote control from personal devices +> [!NOTE] +> Ultrasound controls aren't available yet within the Pro Management Portal. ### [Teams Rooms app settings](#tab/app-settings) @@ -97,15 +96,14 @@ Management of proximity features is available on Microsoft Teams Rooms admin set - Automatically accept proximity-based meeting invitations -- Enable ultrasound beaconing - - - Remote control from personal devices +> [!NOTE] +> Ultrasound controls aren't available yet within the device settings. -### [XML configuration file](#tab/xml) +### [XML (Teams Rooms on Windows)](#tab/xml) -Like most Teams Rooms on Windows features, you can update the settings of your device with the Teams Rooms XML configuration file. The XML configuration file lets you remotely deploy configuration changes to one or more Teams Rooms on Windows devices in your organization. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). +You can update the settings of your device with an XML configuration file. For more information, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](/microsoftteams/rooms/xml-config-file). -|**Paramater**|**Type**|**Level**|**Usage**| +|**Parameter**|**Type**|**Level**|**Usage**| |:-------- |:-------- |:-------- |:-------- | |BluetoothAdvertisementEnabled|Boolean ❷|First ❶|Enabled by default.| |AutoAcceptProximateMeetingInvitations|Boolean ❷|First ❶|If true, proximity based meeting invitations using Bluetooth are automatically accepted. Enabled by default.| diff --git a/Teams/rooms/rooms-authentication.md b/Teams/rooms/rooms-authentication.md index 069109f504..73ca087acb 100644 --- a/Teams/rooms/rooms-authentication.md +++ b/Teams/rooms/rooms-authentication.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: dimehta -ms.date: 09/17/2024 +ms.date: 10/21/2024 ms.topic: article audience: Admin ms.service: msteams @@ -25,19 +25,25 @@ description: Learn how to configure modern authentication for Microsoft Teams Ro Microsoft Teams Rooms on Windows shares authentication component with Teams desktop client and uses the same underlying authentication libraries to connect to Teams and other Microsoft 365 services. As such, Teams rooms requirements for authentication are based on Microsoft Teams requirements. Learn more about [Identity models and authentication for Microsoft Teams](/microsoftteams/identify-models-authentication). -However, Teams rooms on Windows have some key differences compared to an end user personal computer where Teams desktop runs. These differences may impact authentication configurations for Teams rooms. +However, Teams Rooms on Windows have some key differences compared to an end user personal computer where Teams desktop runs. These differences may impact authentication configurations for Teams rooms. -The key differences are as below:   +## Key differences from the Teams Desktop application  -1. Microsoft Teams rooms accounts are centrally managed by IT administrators in an organization. End users don't have ability to sign in/ out of Teams Rooms devices. -1. Microsoft Teams rooms use Microsoft Entra user accounts that are configured with resources mailbox in Microsoft Exchange. Learn more about [Manage resource mailboxes in Exchange Online](/exchange/recipients-in-exchange-online/manage-resource-mailboxes) -1. Microsoft Teams rooms on Windows application run under least privileged local user that has been further locked down using Windows [Shell Launcher V2](/windows/iot/iot-enterprise/customize/shell-launcher) to remove Windows shell components (Start menu, taskbar, settings etc.), such that only Teams Rooms application is aware of resource account used to sign in to Microsoft Teams. This mechanism also prevents other applications to get account information from Windows Account Manager as Windows has no information about resource account used by Teams rooms application. -1. Authentication in Microsoft Teams Rooms on Windows doesn’t require any user intervention and doesn’t support second-factor authentication. The modern authentication mechanism uses the [resource owner password credentials](/azure/active-directory/develop/v2-oauth-ropc) authorization grant type in OAuth 2.0. +1. Microsoft Teams Rooms resource accounts are centrally managed by IT administrators in an organization. End users don't have ability to sign in / out of Teams Rooms devices. +1. Microsoft Teams Rooms use Microsoft Entra accounts that are configured with resources mailbox in Microsoft Exchange. +1. Microsoft Teams Rooms on Windows application run under least privileged local user that has been further locked down using Windows [Shell Launcher V2](/windows/iot/iot-enterprise/customize/shell-launcher) to remove Windows shell components (Start menu, taskbar, settings etc.), such that only Teams Rooms application is aware of resource account used to sign in to Microsoft Teams. This mechanism also prevents other applications to get account information from Windows Account Manager as Windows has no information about resource account used by Teams rooms application. +1. Authentication in Microsoft Teams Rooms on Windows doesn’t require any user intervention and doesn’t support second-factor authentication. The modern authentication mechanism uses the [resource owner password credentials](/azure/active-directory/develop/v2-oauth-ropc) (ROPC) authorization grant type in OAuth 2.0. -It’s important to note that Microsoft Teams Rooms resource accounts shouldn't be configured to use multifactor authentication (MFA), smart card authentication, or client certificate-based authentication (which are all available for end users). +It’s important to note that Microsoft Teams Rooms resource accounts shouldn't be configured to use user interactive multifactor authentication (MFA), smart card authentication, or client certificate-based authentication. -Teams rooms resource account access to Microsoft 365 service can be set up using Conditional Access policies.  Since Windows has no knowledge of resource account that is used by Teams room application, to apply device-level conditional access policies, you must enroll Teams Rooms on Windows devices with Microsoft Endpoint Manager. Learn more about [Enrolling Microsoft Teams Rooms on Windows devices with Microsoft Endpoint Manager](https://techcommunity.microsoft.com/t5/intune-customer-success/enrolling-microsoft-teams-rooms-on-windows-devices-with/ba-p/3246986). When device is enrolled in Endpoint Manager, Teams Room application uses Windows enrolled account using Web access management (WAM) to send device compliance status for conditional access evaluation. To learn more about Conditional access and End Manager device compliance policies, see [Conditional Access and Intune compliance for Microsoft Teams Rooms](/microsoftteams/rooms/conditional-access-and-compliance-for-devices) and [Supported Conditional Access and Intune device compliance policies for Microsoft Teams Rooms](/microsoftteams/rooms/supported-ca-and-compliance-policies?tabs=mtr-w) +## Conditional Access Considerations -You can configure a resource account used with Microsoft Teams Rooms for IP/location-based access. To learn more, see [Conditional Access: Block access by location](/azure/active-directory/conditional-access/howto-conditional-access-policy-location). +Teams Rooms resource account access to Microsoft 365 service can be limited using Conditional Access policies. Since Windows has no knowledge of resource account that is used by Teams room application, to apply device-level conditional access policies, you must enroll Teams Rooms on Windows devices with Microsoft Intune. Learn more about [Enrolling Microsoft Teams Rooms on Windows devices with Intune](https://techcommunity.microsoft.com/t5/intune-customer-success/enrolling-microsoft-teams-rooms-on-windows-devices-with/ba-p/3246986). When the device is enrolled in Intune, the Teams Rooms application uses Windows enrolled account using Web access management (WAM) to send device compliance status for conditional access evaluation. To learn more about Conditional Access and Intune compliance policies, see [Conditional Access and Intune compliance for Microsoft Teams Rooms](/microsoftteams/rooms/conditional-access-and-compliance-for-devices) and [Supported Conditional Access and Intune device compliance policies for Microsoft Teams Rooms](/microsoftteams/rooms/supported-ca-and-compliance-policies?tabs=mtr-w) -For more information about device compliance, see [Supported Conditional Access and Intune compliance policies for Microsoft Teams Rooms](supported-ca-and-compliance-policies.md). +## Teams Legacy Authorization + +Teams upgrade configuration policies offer a setting called **BlockLegacyAuthorization** which when enabled prevents Teams Rooms on Windows from connecting to Teams services. To learn more about this policy see, [Set-CsTeamsUpgradeConfiguration](/powershell/module/skype/set-csteamsupgradeconfiguration) or run Get-CsTeamsUpgradeConfiguration to check if **BlockLegacyAuthorization** is enabled in your tenant. + + ``` Powershell + Get-CsTeamsUpgradeConfiguration | fl BlockLegacyAuthorization + ``` diff --git a/Teams/rooms/rooms-deploy.md b/Teams/rooms/rooms-deploy.md index f9fce32199..7f72a31cb6 100644 --- a/Teams/rooms/rooms-deploy.md +++ b/Teams/rooms/rooms-deploy.md @@ -1,10 +1,10 @@ --- -title: Deploy Microsoft Teams Rooms +title: Microsoft Teams Rooms Deployment Overview author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: altsou -ms.date: 08/29/2024 +ms.date: 10/11/2024 ms.topic: article audience: Admin ms.service: msteams @@ -20,130 +20,95 @@ f1.keywords: ms.localizationpriority: medium ms.custom: seo-marvel-apr2020 ms.assetid: 678689e4-d547-499b-be64-7d8f16dd8668 -description: Read this article to learn about how to deploy Microsoft Teams Rooms, including the deployment phases. +description: Read this article to learn about how to deploy Microsoft Teams Rooms and Teams panels, including the deployment phases. --- # Deployment overview -Deployment of Microsoft Teams Rooms essentially breaks down into phases: +After completing planning for Teams Rooms (see [Planning for Teams Rooms](rooms-plan.md)), the next phase is deployment. Deploying Teams Rooms is broken down into a few phases: -- Confirming that your deployment locations (spaces) meet the deployment dependencies -- Creating Microsoft Teams or Skype for Business and Exchange accounts and assigning them to Teams Rooms (see [Configure accounts for Microsoft Teams Rooms](rooms-configure-accounts.md)) -- Setting up Teams Rooms Pro Management for your systems see [Enrolling a device into Pro Management](enrolling-mtrp-managed-service.md) -- Setting up Teams Rooms in meeting spaces and connecting the peripheral devices you need (see the OEM documentation for your set of devices) +1. Ordering equipment and confirming that your deployment locations (spaces) meet the deployment dependencies +2. Preparing your network environment and configuration steps to ensure your devices work on your corporate network +3. Creating resource accounts for your Microsoft Teams devices (see [Create and configure resource accounts for Teams devices](rooms-configure-accounts.md)) +4. Enabling the Teams Rooms Pro Management Portal and assigning administrative roles (see [Accessing the Pro Management Portal](enrolling-mtrp-managed-service.md)) +5. Configuring Intune for your Teams Rooms +6. Physically deploying your Teams Rooms devices and completing the initial setup steps > [!TIP] > As a companion to this article, we recommend using the [Microsoft Teams Rooms automated setup guide](https://go.microsoft.com/fwlink/?linkid=2224463) when signed in to the Microsoft 365 admin center. This guide will customize your experience based on your environment. To review best practices without signing in and activating automated setup features, go to the [Microsoft 365 setup portal](https://go.microsoft.com/fwlink/?linkid=2222974). -## Site readiness +## Ordering equipment and site readiness for a Teams Rooms deployment -While the ordered devices are being delivered to your organization, work with your networking, facilities, and AV teams to make sure that deployment dependencies are met and each site and space is ready in terms of power, networking, and display. In addition, make sure the physical installation requirements are met. For physical installation considerations, consult with your vendor and leverage the experience of your AV team when installing and mounting screens and running cabling. +Before ordering Teams Rooms equipment, review your physical meeting room spaces to determine the style of meetings that occur in the space and the equipment that fits the need. For more information, see [meeting room guidance](room-planning-guidance.md). Then, order your desired equipment from the [Teams devices store](/microsoftteams/devices/device-store) or from your reseller partner. -You can find out more about these dependencies in the planning guidance links below: - -- [Check network availability](rooms-prep.md#confirm-network-configuration) -- [Certificates](rooms-prep.md#certificates) -- [Proxy](rooms-prep.md#proxy) - -> [!TIP] -> If you must use proxy servers to provide access to Teams, first review [Proxy servers for Teams and Skype for Business Online](../proxy-servers-for-skype-for-business-online.md). When it comes to Microsoft Teams real-time media traffic over proxy servers, we recommend bypassing proxy servers altogether. Microsoft Teams traffic is already encrypted, so proxy servers don't make it more secure and they add latency to real-time traffic. As part of your wider deployment, we recommend that you follow the guidance in [Prepare your network for Teams](../prepare-network.md) for bandwidth planning and assessing your network's suitability for real-time traffic. +Work with your network, facilities, and audio-video (AV) teams to make sure that deployment dependencies are met. Ensure each site and space is ready in terms of power, networking, and furniture. In addition, make sure the physical installation requirements are met. For physical installation considerations, consult with your vendor and use the experience of your AV team when installing and mounting screens and running cabling. |   |   | |-----------|------------| -| ![confirm sites.](../media/audio_conferencing_image7.png)
Decision points|
  • Confirm that your sites meet the key requirements for Microsoft Teams Rooms.
  • Confirm that you've provided sufficient bandwidth for each site.
| -| ![plan device deployment.](../media/audio_conferencing_image9.png)
Next steps|
  • Start to plan your device deployment and configuration.
| +| ![confirm sites.](../media/audio_conferencing_image7.png)
Decision points|
  • Select and order your Microsoft Teams Rooms equipment.
  • Confirm that your sites meet the physical installation requirements for Microsoft Teams Rooms.
| +| ![plan device deployment.](../media/audio_conferencing_image9.png)
Next steps|
  • Prepare your network for Teams Rooms.
| + -## Service readiness +## Preparing your corporate network for Teams Rooms -To prepare for your Microsoft Teams Rooms deployment, do the following key, central tasks: +Teams Rooms devices have specific network requirements which may require adjustments to your corporate network from bandwidth, firewall & proxy, or installing certificates. All of these requirements are things you want to consider as you deploy Teams Rooms. For more information on the networking requirements, see these links: -- Define Microsoft Teams Rooms resource accounts. -- If joining Teams Rooms to Microsoft Entra ID, prepare a Microsoft Entra group with dynamic membership to hold all of the Teams Rooms resource accounts. This will simplify future management, such as applying Conditional Access policies. In order to most easily leverage Microsoft Entra dynamic groups, determine a naming convention that will uniquely identify your Teams Rooms resource accounts. -- If joining Teams Rooms to Active Directory, prepare an organizational unit and Active Directory group to hold your Microsoft Teams Rooms machine and resource accounts, and—optionally—prepare Group Policy objects (GPOs) to enable PowerShell remoting. +- [Prepare your network](rooms-prep.md) +- [Enable Teams Rooms QoS](/microsoftteams/devices/qos-on-teams-devices) +- [Review Teams Rooms IPs and URLs](security.md?tabs=Windows#network-security) +- [Enable 802.1x for Teams Rooms](security.md?tabs=Windows#network-security) -### Define Microsoft Teams Rooms resource account features +## Creating resource accounts for your Microsoft Teams Rooms -Depending on the collaboration scenarios that you've decided to enable with your Microsoft Teams Rooms deployment, you'll need to determine the features and capabilities that you assign to each Microsoft Teams Rooms that you enable. +Teams Rooms devices need resource accounts to be able to successfully sign into Teams and allow end users to book and ensure join buttons appear on the rooms calendar. Each physical meeting room needs its own Teams Rooms resource account. Teams devices dedicated for that space can share the same resource account, meaning a Teams Room with two Teams panels at different doors can all share the same Teams Rooms resource account. This sharing ensures they're all in sync from a calendar perspective and automatic check-in/booking for meetings works correctly. + +For each resource account, there are features an IT admin can enable for different business needs. You want to consider the features outlined here as you create your Teams Rooms resource accounts following this guide: [How to create and configure resource accounts for Teams devices](create-resource-account.md). | Scenario | Description | Microsoft Teams Rooms service account feature | |---------- |------------- | --- | -| Interactive meetings | Using voice, video, and screen sharing; making the Microsoft Teams Rooms a bookable resource | Enabled for Microsoft Teams; enabled for Exchange (Resource Mailbox) | -| Dial-in conferencing | Have an audio conferencing phone number when tapping "New meeting" on the console | Enabled for Audio Conferencing | -| Outbound/inbound PSTN Calling | Enable the Microsoft Teams Rooms console to make and receive PSTN calls | Enabled for Phone System | - -For more information about Microsoft Teams Rooms accounts, see [Configure accounts for Microsoft Teams Rooms](rooms-configure-accounts.md). +| Bookable for meetings | Using voice, video, and screen sharing; making the Microsoft Teams Rooms a bookable resource | Enabled for Microsoft Teams; enabled for Exchange calendaring | +| Meet Now | Allowing a "Meet Now" from the Teams Rooms device | Configure a Teams Meeting policy allowing Meet Now | +| Outbound/inbound Calling | Enable the Microsoft Teams Rooms console to make and receive Public Switched Telephone Network (PSTN) calls | Enabled for Phone System | |   |   | |-----------|------------| -| ![scenario support.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide which scenarios you'll support, and identify licensing requirements for your Microsoft Teams Rooms resource accounts.
| -| ![prepare host machine.](../media/audio_conferencing_image9.png)
Next steps|
  • Prepare to host machine and resource accounts.
| - -_Sample Microsoft Teams Rooms resource account planning table_ - -| Site | Room name | Room type | Future room capabilities | Microsoft Teams Rooms account features | -|-----------|---------------|---------------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| London HQ | Curie | Medium | 1 screen, audio and video plus presentation
Dial-in conferencing access
PSTN access | Enabled for Exchange (Resource Mailbox)
Enabled for Audio Conferencing
Enabled for Phone System | -| Sydney HQ | Hill | Large | 2 Screens, audio and video plus presentation
Dial-in conferencing access
PSTN access | Enabled for Skype for Business
Enabled for Exchange (Resource Mailbox)
Enabled for Audio Conferencing
Enabled for Phone System | - -### Prepare to host Microsoft Teams Rooms and resource accounts (optional) - -To enable you to manage and report on your Microsoft Teams Rooms and resource accounts, prepare your on-premises Active Directory or Microsoft Entra ID. - -Define an on-premises Active Directory or Microsoft Entra group to add all Microsoft Teams Rooms resource accounts to. If using Microsoft Entra ID, consider using a dynamic group to automatically add and remove resource accounts from the group. - -Define one organizational unit in your on-premises Active Directory hierarchy to hold all Microsoft Teams Rooms machine accounts (if they're joined to the domain) and one organizational unit to hold all the Microsoft Teams Rooms user accounts. Disable Group Policy inheritance to ensure that you apply only the policies you intended to apply to the domain-joined Microsoft Teams Rooms. - -Create a Group Policy object assigned to the organization unit that contains your Microsoft Teams Rooms computer accounts. Use this to: +| ![scenario support.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide which Teams Rooms scenarios you support.
  • Identify licensing requirements for your Microsoft Teams Rooms resource accounts.
| +| ![prepare host machine.](../media/audio_conferencing_image9.png)
Next steps|
  • Prepare the Pro Management Portal.
| -- [Set power and local account settings](rooms-operations.md#configuring-group-policy-for-microsoft-teams-rooms). -- Enable Windows Update. -- Enable PowerShell remoting. You can configure a start-up script to run a script: Enable-PSRemoting -Force +## Enabling the Pro Management Portal -You can use PowerShell to perform several remote management activities, including getting and setting configuration information. PowerShell remoting must be enabled *before* any PowerShell remote management can take place and should be considered as part of your deployment processes or configured via Group Policy. For more information about these capabilities and enabling them, see [Maintenance and operations](rooms-operations.md#remote-management-using-powershell). +Teams Rooms devices are best managed in the Teams Rooms Pro Management Portal. Once you have a Teams Rooms Pro license available in your Microsoft 365 tenant, you can enable the Teams Rooms Pro Management Portal following the guidance here: [Accessing the Pro Management Portal](enrolling-mtrp-managed-service.md). -## Configuration and deployment +While in the Pro Management Portal it's important to define various administrative roles for your meeting room admins. The Pro Management Portal supports granular role-based access control (RBAC), you can follow the steps here for how to configure RBAC: [Role-based access control in the Microsoft Teams Rooms Pro Management Portal](rooms-pro-rbac.md). -Planning for configuration and deployment covers the following key areas: -- Resource account provisioning -- Device software installation -- Device deployment -- Microsoft Teams Rooms application and peripheral device configuration -- Testing -- Asset management - -### Resource account provisioning - -Each Microsoft Teams Rooms device requires a dedicated and unique resource account that must be enabled for both Microsoft Teams and Exchange. This account must have a room mailbox hosted on Exchange. Calendar processing must be configured so that the device can automatically accept incoming meeting requests. For more information about creating these accounts, see [Configure accounts for Microsoft Teams Rooms](rooms-configure-accounts.md). - -> [!TIP] -> Each Microsoft Teams Rooms must have a valid and unique machine name on your network. Many monitoring and alerting systems display the machine name as a key identifier, so it's important to develop a naming convention for Microsoft Teams Rooms deployments that allows support personnel to easily locate the Microsoft Teams Rooms that has been flagged as requiring an action. An example might be using a pattern of MTR-*Site*-*Room Name* (MTR-LON-CURIE). - -|   |   | +|   |   | |-----------|------------| -| ![decide naming convention.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide the naming convention for your Microsoft Teams Rooms resource accounts.
  • Decide whether you'll create individual accounts or use bulk-provisioning scripts.
| -| ![next steps.](../media/audio_conferencing_image9.png)
Next steps|
  • Start to plan your device deployment.
| +| ![scenario support.](../media/audio_conferencing_image7.png)
Decision points|
  • Activate the Pro Management Portal.
  • Define RBAC inside of the Pro Management Portal
| +| ![prepare host machine.](../media/audio_conferencing_image9.png)
Next steps|
  • Configuring Intune for your Teams Devices.
| -### Device software installation +## Configuring Intune for your Teams Devices -Teams Rooms comes pre-installed by the original equipment manufacturer (OEM). +Teams Rooms on Windows devices can be managed in Intune to expand device management capabilities and for Intune compliance checks to ensure Teams Rooms on Windows devices are compliant with organizational requirements. Teams Rooms on Android and Teams panels devices automatically enroll into Intune when they're logged in for the first time providing more controls and Intune compliance checks as well. -We provide guidance on how to use [Microsoft Teams Rooms Pro Management Portal](managed-meeting-rooms-portal.md) to monitor the Microsoft Teams Rooms deployment and report on availability, hardware/software errors, and Microsoft Teams Rooms application version. +For Teams Rooms on Windows devices, Intune enrollment can be completed using [AutoPilot + AutoLogin](autopilot-autologin.md) or in one of several other manually [enrollment methods offered by Intune](/mem/intune/fundamentals/deployment-guide-enrollment-windows). -An additional consideration is whether the Microsoft Teams Rooms will be domain-joined. Information about the benefits of domain joining can be found in [Configuring Group Policy for Microsoft Teams Rooms](rooms-operations.md#configuring-group-policy-for-microsoft-teams-rooms). +For Teams Rooms on Android and Teams panel devices, Intune enrollment is requirement for a successful sign in. Teams Android devices use Android Device Administrator today as their enrollment method, for information on enabling Intune enrollment see these instructions: [Configure Intune to enroll Teams Android-based devices](/microsoftteams/devices/phones-panels-deploy#configure-intune-to-enroll-teams-android-based-devices). -|   |   | +|   |   | |-----------|------------| -| ![decision points device naming.](../media/audio_conferencing_image7.png)
Decision points|
  • Decide the Microsoft Teams Rooms resource account naming convention to be used during your deployment.
  • Decide whether you'll join Microsoft Teams Rooms devices to your domain.
  • Decide whether you'll use Azure Monitor to monitor the Microsoft Teams Rooms deployment.
  • -| ![next steps plan device.](../media/audio_conferencing_image9.png)
    Next steps|
    • Start to plan your device deployment approach.
    | +| ![scenario support.](../media/audio_conferencing_image7.png)
    Decision points|
    • Enabling Teams Rooms on Windows devices to enroll in Intune
    • Enabling Teams Rooms on Android and Teams panels to enroll in Intune
    | +| ![prepare host machine.](../media/audio_conferencing_image9.png)
    Next steps|
    • Physically deploying your Teams Rooms devices and completing the initial setup
    | + +## Physically deploying and configuring your Teams Rooms devices ### Device deployment -After you've decided how to create and manage your Microsoft Teams Rooms resource accounts, create your plan to ship the devices and their assigned peripherals to your rooms, and then proceed to installation and configuration. +After creating your resource accounts and enabling the management portal, it's time to ship devices. Create your plan to ship the devices and their assigned peripherals to your rooms, and then proceed to installation and configuration. |   |   | |-----------|------------| -| ![manage site-by-site deployment.](../media/audio_conferencing_image7.png)
    Decision points|
    • Decide who will manage the site-by-site deployment.
    • Identify the resources who will install Microsoft Teams Rooms on site and undertake the configuration and testing.
    | +| ![manage site-by-site deployment.](../media/audio_conferencing_image7.png)
    Decision points|
    • Decide who manages the site-by-site deployment.
    • Identify the resources to install Microsoft Teams Rooms on site and undertake the configuration and testing.
    | | ![start device testing.](../media/audio_conferencing_image9.png)
    Next steps|
    • Start device testing.
    | _Sample deployment table_ @@ -155,28 +120,22 @@ _Sample deployment table_ ### Microsoft Teams Rooms application and peripheral device configuration -After each Microsoft Teams Rooms system has been physically deployed and the supported peripheral devices connected, you'll need to configure the Microsoft Teams Rooms application to assign the Microsoft Teams Rooms resource account and password to enable Teams Rooms to sign in to Microsoft Teams and Exchange. +At initial power on of your Teams Rooms device, you need to configure the Microsoft Teams Rooms application to use the matching Microsoft Teams Rooms resource account and password to sign in to Microsoft Teams. -You can manually configure each Microsoft Teams Rooms system. Alternatively, you can use a centrally stored, per–Teams Rooms XML configuration file to manage the application settings. - -For more information about how to use the XML configuration file, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](xml-config-file.md). - -You can use [remote PowerShell](rooms-operations.md#remote-management-using-powershell) to pull the Microsoft Teams Rooms configuration for reporting needs. +Once signed in, you can configure settings each Microsoft Teams Rooms system. For a Teams Rooms on Windows device, you can use a centrally stored, XML configuration file to manage the application settings. For more information about how to use the XML configuration file, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](xml-config-file.md). |   |   | |-----------|------------| -| ![decision point configure.](../media/audio_conferencing_image7.png)
    Decision points|
    • Decide whether you'll manually configure each Microsoft Teams Rooms system or use a central XML file (one per Microsoft Teams Rooms device).
    | -| ![next steps remote approach.](../media/audio_conferencing_image9.png)
    Next steps|
    • Define your remote management approach.
    | +| ![decision point configure.](../media/audio_conferencing_image7.png)
    Decision points|
    • Decide whether to manually configure each Microsoft Teams Rooms system or use a central XML file.
    | +| ![next steps remote approach.](../media/audio_conferencing_image9.png)
    Next steps|
    • Test your new Teams Rooms devices.
    | ### Testing -After Teams Rooms has been deployed, you should test it. Check that the capabilities listed in [Microsoft Teams Rooms help](https://support.microsoft.com/office/microsoft-teams-rooms-help-e667f40e-5aab-40c1-bd68-611fe0002ba2?ui=en-us&rs=en-us&ad=us) are working on the deployed device. We highly recommend that the deployment team verify that Microsoft Teams Rooms is appearing in Teams admin center and in Teams Rooms Pro Management. It's also important that you make a number of test calls and meetings to check quality. - -We recommend that as part of the general Teams, you configure building files for Call Quality Dashboard (CQD), monitor quality trends, and engage in the Quality of Experience Review process. For more information, see [Improve and monitor call quality for Teams](../monitor-call-quality-qos.md). +After Teams Rooms is deployed, you should test it. Check that the capabilities listed in [Microsoft Teams Rooms help](https://support.microsoft.com/office/microsoft-teams-rooms-help-e667f40e-5aab-40c1-bd68-611fe0002ba2?ui=en-us&rs=en-us&ad=us) are working on the deployed device. We recommend that the deployment team check that Microsoft Teams Rooms is appearing in Teams Admin Center and in Teams Rooms Pro Management Portal. It's also important that you make several test calls and meetings to check quality. ### Asset management -As part of the deployment, you'll want to update your asset register with the room name, Microsoft Teams Rooms name, Microsoft Teams Rooms resource account, and assigned peripheral devices. +As part of the deployment, you may want to update your asset register with the room name, Microsoft Teams Rooms name, Microsoft Teams Rooms resource account, and assigned peripheral devices. _Sample asset table_ diff --git a/Teams/rooms/rooms-operations.md b/Teams/rooms/rooms-operations.md index abec2a66cf..7eb2c5a604 100644 --- a/Teams/rooms/rooms-operations.md +++ b/Teams/rooms/rooms-operations.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: kramachandra -ms.date: 09/30/2024 +ms.date: 11/18/2024 ms.topic: article audience: Admin ms.service: msteams @@ -45,12 +45,12 @@ The logs are output as a ZIP file in c:\rigel. ### Display Sleep/Wake Behavior -Teams Rooms on Windows devices are configured out of the box to send no video signal after 10 minutes of inactivity, at which time the Windows PC will stop sending video from its video outputs. You need to configure front of room displays in PC mode if available or set displays to automatically sleep/wake on an inactive/active HDMI video signal, consult your display OEM documentation for guidance. If the display doesn't support any of the mentioned functionalities, you may be able to use a display controller to enable the desired behavior over CEC or RS-232 control: +Teams Rooms on Windows devices are configured out of the box to send no video signal after 10 minutes of inactivity, at which time the Windows PC will stop sending video from its video outputs. You need to configure front of room displays in PC mode if available or set displays to automatically sleep/wake on an inactive/active HDMI video signal, consult your display OEM documentation for guidance. If the display doesn't support any of the mentioned functionalities, you may be able to use a display controller to enable the desired behavior over CEC or RS-232 control. We do not certify displays or display controllers due to the abundance of offerings in the market, this list offers a few options for display controls that have worked in the past: - [Crestron HD-CTL-101](https://www.crestron.com/Products/Control-Hardware-Software/Hardware/Control-Modules/HD-CTL-101) - [Liberty DL-UHDILC](https://secure.libertycable.com/product_details.php?pitem=DL-UHDILC) - [Extron HD CTL 100](https://www.extron.com/article/hdctl100ad) -If the displays aren't visible to the Windows PC when in their sleep state, Teams Rooms may report display disconnected alerts messages in Teams Admin Center and the Pro Management Portal and you may experience instability with your Teams Rooms devices. Windows believes the displays are physically disconnected. Consult your display manufacturer documentation for how to configure your displays in a way that keeps the HDMI sync with the Windows PC. If unsuccessful, powered Extended Display Identification Data (EDID) emulators/minders can be used to mitigate the instability and prevent monitoring alerts, several options are listed: +If the displays aren't visible to the Windows PC when in their sleep state, Teams Rooms may report display disconnected alerts messages in Teams Admin Center and the Pro Management Portal and you may experience instability with your Teams Rooms devices. Windows believes the displays are physically disconnected. Consult your display manufacturer documentation for how to configure your displays in a way that keeps the HDMI sync with the Windows PC. If unsuccessful, powered Extended Display Identification Data (EDID) emulators/minders can be used to mitigate the instability and prevent monitoring alerts. We do not certify or offer support for EDID minders but several options are listed which have worked for other customers: - [Extron EDID 101H 4K PLUS](https://www.extron.com/product/edid101h4kplus) - [StarTech EDID Emulator](https://www.startech.com/en-us/audio-video-products/vsedidhd) @@ -129,11 +129,8 @@ You can also perform this task directly on the device with these steps: 1. Switch to Admin mode 2. Open Windows Explorer and follow the instructions for your app version: -3. If running Teams Rooms on Windows 4.19.82.0 or earlier: -4. Navigate to: `C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalCache\Roaming\Microsoft\` -5. Delete the **Teams** folder -6. If running Teams Rooms 5.0.0 or newer: -7. Navigate to: `C:\Users\Skype\AppData\Local\Packages\MSTeamsRooms_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams` +1. Navigate to: `C:\Users\Skype\AppData\Local\Packages\MSTeamsRooms_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams` + 8. Delete everything inside the MSTeams folder 9. Restart the Teams Rooms device and allow it to return to the Teams Rooms interface diff --git a/Teams/rooms/rooms-plan.md b/Teams/rooms/rooms-plan.md index 5978ef1213..19ef40925b 100644 --- a/Teams/rooms/rooms-plan.md +++ b/Teams/rooms/rooms-plan.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: sohailta -ms.date: 03/01/2024 +ms.date: 10/21/2024 ms.topic: article audience: Admin ms.service: msteams @@ -26,7 +26,7 @@ description: This article explains the relevant planning considerations for depl This article introduces an end-to-end approach to planning, delivering, and operating Microsoft Teams Rooms as part of your overall meeting and conference room strategy. -You'll find planning information below covering the recommended approach and key decisions that you need to make, with links to supporting technical information. We recommend that you review the Plan, Deploy, and Manage sections even if you're already fully deployed. +The planning information covers the recommended approach and key decisions that you need to make, with links to supporting technical information. We recommend that you review the Plan, Deploy, and Manage sections even if you're already fully deployed. ## Overview of Microsoft Teams Rooms @@ -44,32 +44,33 @@ Microsoft Teams Rooms includes the following key components to deliver a great u - Compute module - Microsoft Teams Rooms application - Peripheral devices (camera, microphone, speaker) -- External screens (maximum of two) +- Front of room screens (maximum of two) - HDMI input Check out the certified Teams Rooms systems and peripherals in [Teams Rooms certified systems and peripherals](certified-hardware.md). ## Teams Rooms licensing -Each meeting room device, such as a Teams Rooms console, Surface Hub, and Teams panel, needs a Teams Rooms license. Teams provides two licenses for Teams Rooms: Microsoft Teams Rooms Pro and Microsoft Teams Rooms Basic. +Each meeting room needs a Teams Rooms license, such as a Teams Rooms console, Surface Hub, or Teams panel. Teams provides two licenses for Teams Rooms: Microsoft Teams Rooms Pro and Microsoft Teams Rooms Basic. -Microsoft Teams Rooms Pro is great for organizations that have 25 or more meeting room devices or who want the most comprehensive meeting and device management experiences. Hybrid Teams meetings become more immersive with features like Front row, Content camera, AI-powered noise suppression, and other features available with Microsoft Teams Rooms Pro. Teams Rooms admins can centrally manage all their certified Teams Rooms devices from the Teams admin center from configuring conditional access policies to analyzing rich telemetry about device health and meeting quality. +Microsoft Teams Rooms Pro is great for organizations that have 25 or more meeting room devices or who want the most comprehensive meeting and device management experiences. Hybrid Teams meetings become more immersive with features like Front row, Content camera, AI-powered noise suppression, and other features available with Microsoft Teams Rooms Pro. Teams Rooms admins can centrally manage all their certified Teams Rooms devices from the Pro Management Portal. -Microsoft Teams Rooms Basic is available for organizations that only have a few meeting room devices and who only need basic meeting and management functionality. Microsoft Teams Rooms Basic lets you join meetings, share content and live video, join Zoom and Webex meetings with Direct Guest Join, and perform basic device inventory and monitoring in the Teams admin center. +Microsoft Teams Rooms Basic is available for organizations that only have a few meeting room devices and who only need basic meeting and management functionality. Microsoft Teams Rooms Basic lets you join meetings, share content and live video, join Zoom and Webex meetings with Direct Guest Join, and perform basic device inventory and monitoring in the Teams Admin Center. Before you can use a meeting room device, you need to assign a license to it. For more information, see [Microsoft Teams Rooms licenses](rooms-licensing.md). +> [!TIP] +> If your meeting room only has a Teams panel, you can use a Teams Shared Device license for the Teams panel resource account. If you add a Teams Rooms device to the space later, you can upgrade to a Teams Rooms Pro license. + [!INCLUDE [mtr-user-licensing](../includes/mtr-user-licensing.md)] |   |   | |-----------|------------| -|![decide deployment.](../media/audio_conferencing_image7.png)
    Decision points|
    • Will you deploy Microsoft Teams Rooms in your organization?
    • How will you procure your Microsoft Teams Rooms systems?
    | -| ![identify activities.](../media/audio_conferencing_image9.png)
    Next steps |
    • Identify who will undertake the key activities throughout your deployment.
    • Review the meeting rooms you have (and plan to set up) to understand where you want to deploy Microsoft Teams Rooms and the peripheral devices that would be appropriate for the room size.
    | +|![decide deployment.](../media/audio_conferencing_image7.png)
    Decision points|
    • Are you deploying Microsoft Teams Rooms in your organization?
    • How do you plan you procure your Microsoft Teams Rooms systems?
    | +| ![identify activities.](../media/audio_conferencing_image9.png)
    Next steps |
    • Identify who performs the key activities throughout your deployment.
    • Understand where you want to deploy Microsoft Teams Rooms and the peripheral devices that would be appropriate for the room size.
    | | | | -## Identify who will undertake the key activities throughout your deployment - -Use the approach illustrated below to guide you through your deployment, and customize the sample outputs provided as needed for your organization. +## Identify who performs the key activities throughout your deployment Begin with understanding what conference rooms you have and envisioning what would work best for you in the future, then move through selecting and procuring the equipment you need, readying your sites, configuring and deploying your service, managing change and user adoption, and developing operations and maintenance procedures. @@ -83,9 +84,9 @@ You might need to coordinate these activities across several teams. We provide a | Plan capabilities | IT Project Team | | [Room inventory and capability planning](#room-inventory-and-capability-planning) | | Device selection | IT Project Team / AV Team | | [Device selection](#device-selection) | | Procurement | IT Project Team / AV Team | | [Procurement](#procurement) | -| Site readiness | Facilities / AV team / IT Project Team | | [Site readiness](rooms-deploy.md#site-readiness) | -| Service readiness | IT Project Team | | [Service readiness](rooms-deploy.md#service-readiness) | -| Configuration | IT Project Team | | [Configuration and deployment](rooms-deploy.md#configuration-and-deployment) | +| Site readiness | Facilities / AV team / IT Project Team | | [Site readiness](rooms-deploy.md#ordering-equipment-and-site-readiness-for-a-teams-rooms-deployment) | +| Network readiness | IT Project Team | | [Network readiness](rooms-deploy.md#preparing-your-corporate-network-for-teams-rooms) | +| Resource accounts | IT Project Team | | [Creating resource accounts](rooms-deploy.md#creating-resource-accounts-for-your-microsoft-teams-rooms) | | Deployment | Facilities / AV team / IT Project Team | | [Deployment checklist](console.md) | | Adoption | Facilities / AV team / IT Project Team | | [Adoption](#plan-for-adoption-and-change-management) | | Maintenance and operations | AV team / IT Project Team | | [Management overview](rooms-manage.md) | @@ -96,7 +97,7 @@ The first step is to inventory your organization's existing meeting spaces and c After you create an inventory of the equipment and capabilities in each existing room, your requirements for that room feed into your device selection planning to create a rich conferencing solution. The modalities (audio, video) needed for each room—in addition to room size and purpose—all play an important role in deciding which solution is most appropriate for each room. -As part of your discovery, it's key to consider room acoustics and layout. For example, check that the chairs in the room won't block the camera view. Verify that the room doesn't have excessive echo or noisy air conditioning, and that it does have sufficient power for the screens and Microsoft Teams Rooms. There are many factors to consider that your audio-visual (AV) team or partner will be able to advise on. +As part of your discovery, it's key to consider room acoustics and layout. For example, check that the chairs in the room can't block the camera view. Verify that the room doesn't have excessive echo or noisy air conditioning, and that it does have sufficient power for the screens and Microsoft Teams Rooms. There are many factors to consider that your audio-visual (AV) team or partner can advise on. |   |   | |-----------|------------| @@ -106,8 +107,8 @@ _Sample meeting/conference room inventory_ | Site | Room name | Room type | Number of people | In scope? | Current room capabilities | Future room capabilities | |-----------|-----------|-----------|------------------|-----------|-------------------------------------|--------------------------| -| London HQ | Curie | Medium | 6–12 | Yes | Speakerphone | 1 screen, audio and video plus presentation
    PSTN Access | -| Sydney HQ | Hill | Large | 12–16 | Yes | Legacy AV unit, 1 screen and camera | 2 screens, audio and video plus presentation
    PSTN Access | +| London HQ | Curie | Medium | 6–12 | Yes | Speakerphone | Single screen, audio, and video plus presentation | +| Sydney HQ | Hill | Large | 12–16 | Yes | Legacy AV unit, single screen, and camera | Dual screens, audio, and video plus presentation | ## Device selection @@ -122,12 +123,12 @@ Based on the vendor you prefer, use the information provided in the requirements |   |   | |---|---| -| ![rooms in scope.](../media/audio_conferencing_image7.png)
    Decision points |
    • From your inventory, which types of rooms are in scope for your deployment?
    • Which systems will you deploy for each room type?
    | +| ![rooms in scope.](../media/audio_conferencing_image7.png)
    Decision points |
    • Which types of rooms are in scope for your deployment?
    • Which systems will you deploy for each room type?
    | | ![gather material.](../media/audio_conferencing_image9.png)
    Next steps |
    • Start to gather key operational material for your chosen systems, and engage your procurement team.
    | _Sample Microsoft Teams Rooms deployment template for your organization_ -| Room type/size | Number of people | Microsoft Teams Rooms system | Peripheral devices | Display(s) | +| Room type/size | Number of people | Microsoft Teams Rooms system | Peripheral devices | Displays | |--------------------|------------------|------------------------------|--------------------|-----------------| | Focus 10' by 9' | 2–4 | | | | | Small 16' by 16' | 4–6 | | | | @@ -137,51 +138,26 @@ _Sample Microsoft Teams Rooms deployment template for your organization_ > [!TIP] > Now is a great time to start gathering information about the Microsoft Teams Rooms solution you've chosen. -### Wireless network considerations - -We strongly recommend that you connect your Teams Rooms devices to a wired network for greater stability and performance, ensuring a seamless meeting experience. If using a wired connection is not available, you may opt to use a wireless connection. - -> [!IMPORTANT] -> Wireless networks can be prone to network interference leading to quality degradation. We strongly recommend that you follow your wireless equipment provider's best practices when configuring a wireless connection to improve video and audio quality. - -Here are some examples of wireless network configuration best practices recommended by various manufacturers: - -- Deploy wireless equipment, such as access points and routers, that can handle and distribute the bandwidth load across all connected devices in the network. -- As much as possible, use access points and routers from a single manufacturer to avoid further congesting the radio-spectrum. -- Ensure wireless equipment is installed in a way that reduces or eliminates interference from objects and other equipment. -- Ensure the wireless network shows strong signal strength (Wi-Fi signal showing full bars is preferred) on Teams Rooms and other device screens. -- Default to prioritizing 5 GHz coverage for devices to optimize for higher bandwidth. -- Enable band steering to ensure that 5 GHz is always given more priority when sharing the same network name (SSID) as 2.4 GHz. -- Keep wireless channel utilization below 50%. -- Keep access point and router firmware up to date with the latest firmware versions and hot fixes. -- Verify that Teams Rooms devices and at least one access point see each other with a signal strength of -60 dBm or better. A dBm value closer to zero is preferred. Follow your equipment manufacturer's recommendations. -- Implement QoS whenever possible to allow monitoring and resolution of issues in real time. - -For additional best practices specific to your wireless network hardware, check your manufacturer's documentation. - -You can also troubleshoot wireless network issues using the wireless network report built into Windows 10. For more information, see [Analyze the wireless network report - Microsoft Support](https://support.microsoft.com/windows/analyze-the-wireless-network-report-76da0daa-1db2-6049-d154-7bb679eb03ed). - - ## Procurement You can procure your chosen system as a bundle or an integrated solution via device partners. -You can acquire Microsoft Teams Rooms from a number of partners who are listed in [Teams Rooms certified systems and peripherals](certified-hardware.md). Please visit the partners' websites to learn more about these solutions and procurement options. +You can acquire Microsoft Teams Rooms from one of the partners are listed in [Teams Rooms certified systems and peripherals](certified-hardware.md). Visit the partners' websites to learn more about these solutions and procurement options. -Depending on your deployment scale and approach, you might decide to have the Microsoft Teams Rooms and supported peripheral devices shipped to a central location for initial configuration and assignment. This might be a good approach for a staged rollout across many sites. Or, you might choose to ship the bundles directly to your sites. +Depending on your deployment scale and approach, you might decide to have the Microsoft Teams Rooms and supported peripheral devices shipped to a central location for initial configuration and assignment. A central location might be a good approach for a staged rollout across many sites. Or, you might choose to ship the bundles directly to your sites. |   |   | |---|---| -| ![ship components.](../media/audio_conferencing_image7.png)
    Decision points|
    • Will you ship the components directly to a site or to a staging facility?
    • Who will manage the staging facility (if you decide to use one)?
    | +| ![ship components.](../media/audio_conferencing_image7.png)
    Decision points|
    • Do you ship the components directly to a site or to a staging facility?
    • Do you know who manages the staging facility (if you decide to use one)?
    | | ![plan operations.](../media/audio_conferencing_image9.png)
    Next steps|
    • Plan for operations.
    • Plan for adoption and change management.
    | ## Plan for operations Your organization must execute monitoring, administration, and management tasks on an ongoing basis, and it's key to agree who will undertake these tasks early in your deployment. -Many organizations have an AV team or partner who manages their conference rooms and devices. Or you can have Microsoft help manage Teams Rooms by leveraging Microsoft Teams Rooms Pro. Decide who will manage the Microsoft Teams Rooms devices going forward to monitor performance as well as deploy software updates and hotfixes. +Many organizations have an AV team or partner who manages their conference rooms and devices. It's important to decide who manages the Microsoft Teams Rooms devices going forward to monitor performance and deploy software updates and hotfixes. -Consider which helpdesk queue you'll route Microsoft Teams Rooms-related calls to, and provide an FAQ to the helpdesk team so they can better understand how to use Microsoft Teams Rooms and the key troubleshooting steps they can take. A good starting point for this FAQ is the [user help](https://support.microsoft.com/office/microsoft-teams-rooms-help-e667f40e-5aab-40c1-bd68-611fe0002ba2) and [Known issues](known-issues.md). +Consider which helpdesk queue you route Microsoft Teams Rooms-related calls to, and provide an FAQ to the helpdesk team so they can better understand how to use Microsoft Teams Rooms and the key troubleshooting steps they can take. A good starting point for this FAQ is the [user help](https://support.microsoft.com/office/microsoft-teams-rooms-help-e667f40e-5aab-40c1-bd68-611fe0002ba2) and [Known issues](known-issues.md). > [!NOTE] > Microsoft Teams Rooms sign in to Microsoft Teams and allows joining meetings hosted by Microsoft Teams services. Microsoft Teams rooms may also connect to third party meeting services anonymously as guest, depending on your configuration of the device. @@ -197,7 +173,7 @@ Consider which helpdesk queue you'll route Microsoft Teams Rooms-related calls t ## Plan for adoption and change management -Microsoft Teams Rooms systems introduce new capabilities to your users. It's important that you recognize that this will be a change for your users, and you should ensure your internal marketing campaign identifies the benefits the new system will have for your users and the key talking points leads can use to discuss with their teams. +Microsoft Teams Rooms systems introduce new capabilities to your users. It's important that you recognize that Teams Rooms will be a change for your users, and you should ensure your internal marketing campaign identifies the benefits the new system will have for your users and the key talking points leads can use to discuss with their teams. -Consider scheduling show-and-tell events and poster drops at each site to inform your users of the new capabilities. You might also create in-room "quick start guides." Consider finding a meetings champion at each site who can help others get up to speed and start using the devices. +To inform your users of the new capabilities, consider scheduling show-and-tell events and poster drops at each site. You might also create in-room "quick start guides." Consider finding a meeting champion at each site who can help others get up to speed and start using the devices. diff --git a/Teams/rooms/rooms-prep.md b/Teams/rooms/rooms-prep.md index 8f377fe081..50231c66b0 100644 --- a/Teams/rooms/rooms-prep.md +++ b/Teams/rooms/rooms-prep.md @@ -1,5 +1,5 @@ --- -title: Prepare your Environment +title: Prepare your environment for Teams Rooms author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -23,35 +23,21 @@ description: Learn about how to prepare your infrastructure for deploying Micros ms.custom: seo-marvel-apr2020 --- -# Prepare your environment +# Prepare your environment for Teams Rooms -This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Microsoft Teams Rooms. - -1. Prepare a resource account for each Microsoft Teams Rooms device. See [Deploy Microsoft Teams Rooms](rooms-deploy.md) for details - -2. Ensure that there's a working network/Internet connection for the device to use with access to all required URLs and IPs, further guidance can be found here: [Network Security](security.md#network-security) - -3. In order to improve your experience, Microsoft collects data. To allow Microsoft to collect data, allow these sites: - - - Telemetry client endpoint: `https://vortex.data.microsoft.com/` - - Telemetry settings endpoint:` https://settings.data.microsoft.com/` - -## Create and test a resource account - -A *resource account* is an account that the Microsoft Teams Rooms device uses to access features such as: Teams for Calling and Meetings and SharePoint for Whiteboards and PowerPoint files. See [Deploy Microsoft Teams Rooms](rooms-deploy.md) for details. +This section contains an overview of the steps required to prepare your network environment so that you can use all of the features of Microsoft Teams Rooms. This section also includes information on configuring local administive access to your Teams Rooms devices. ## Confirm network configuration In order to function properly, Microsoft Teams Rooms devices must have access to a network that meets these requirements: -- Access to: Microsoft Teams, SharePoint/OneDrive, Pro Management Portal, Microsoft Store, Windows Update, Intune, Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Windows#network-security) +- Review access to: Microsoft Teams, SharePoint/OneDrive, Pro Management Portal, Microsoft Store, Windows Update, Intune, Microsoft Entra ID, & Microsoft Common destinations. Open required ports to the required destinations documented in [Teams Rooms Network Security](/microsoftteams/rooms/security?tabs=Windows#network-security) - Review network bandwidth and quality of service (QoS) requirements: [QoS on Teams Devices](/microsoftteams/devices/qos-on-teams-devices) -- If your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url - -- If your organization utilizes certificates for network access, you need the certificates for a successful setup +- Review if your organization utilizes a proxy, you need the proxy address or proxy autoconfiguration (PAC) file url +- Review if your organization utilizes certificates for network access, you need the certificates for a successful setup > [!IMPORTANT] > Be sure to use a network connection with enough bandwidth (we recommend 10 mbps up/down per Teams Room) to ensure your meetings perform well. @@ -69,17 +55,19 @@ Your Microsoft Teams Rooms device uses certificates for Microsoft Teams, network #### Proxy for Teams Rooms on Windows -This guidance is for manual configuration. This can also be automated using Intune configurations on your devices ensure these configurations are consistent across a large scale deployment. +This guidance is for manual configuration. This configuration can also be automated using Intune configurations on your devices ensure these configurations are consistent across a large scale deployment. ##### Skype User Registry Hive -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you'll be prompted for the local Administrator password on the device (the default password is **sfb**) -2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Entra ID joined choose **Other User,** then use .\admin as the user name) -3. In the **Search Windows** box bottom left type in regedit (either long press the screen or right select and choose **Run as administrator**) -4. Select on the HKEY_USERS folder (you'll see a list of machine user SIDs) ensure the root folder HKEY_USERS is selected +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you're prompted for the local Administrator password on the device (the default password is **sfb**) +1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) +1. In the **Search** box, in the bottom left type in regedit (either long press the screen or right select and choose **Run as administrator**) +1. Select on the HKEY_USERS folder ensure the root folder HKEY_USERS is selected + 5. Select on File and then choose **Load Hive** 6. Browse to the **C:\Users\Skype** folder and type in the File name box NTUSER.dat and press the open button -7. You'll be prompted for a Key Name for your newly loaded Hive; type in Skype (you should now see the registry settings for the Skype User) +1. You're prompted for a Key Name for your newly loaded Hive; type in Skype (you should now see the registry settings for the Skype User) + 8. Open the Skype key and browse to HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings then ensure these settings are entered: ```console @@ -100,14 +88,14 @@ This guidance is for manual configuration. This can also be automated using Intu "AutoConfigURL"=http://contosoproxy.corp.net/proxy.pac ``` -9. Once you're finished making your changes highlight the Skype User key (root folder for Skype) and choose unload Hive from the Registry file menu (you'll be prompted for confirmation - select **Yes**) +9. When finished making changes, highlight the Skype User key (root folder for Skype) and choose unload Hive from the Registry file menu (which prompts for confirmation - select **Yes**) 10. You can now close the registry editor and reboot your Teams Room ##### Windows System Proxy -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you'll be prompted for the local Administrator password on the device (the default password is **sfb**) -2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Entra ID joined choose **Other User,** then use .\admin as the user name) -3. In the **Search Windows** box bottom left type in 'Settings' +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) +1. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) +3. In the **Search Windows** box, type in 'Settings' 4. Select 'Network & internet' 5. Select 'Proxy' 6. Configure your proxy IP or proxy PAC file @@ -115,8 +103,8 @@ This guidance is for manual configuration. This can also be automated using Intu ##### Pro Management Agent Proxy -1. In the Microsoft Teams Rooms UI, select on the Settings gear icon where you'll be prompted for the local Administrator password on the device (the default password is **sfb**) -2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Entra ID joined choose **Other User,** then use .\admin as the user name) +1. In the Microsoft Teams Rooms UI, select on the Settings gear icon which prompts for the local Administrator password on the device (the default password is `sfb`) +2. Tap on **Settings** followed by tapping on the **Go to Windows** button and then tapping on the **go to Admin Sign In** button and then clicking the **Administrator** button (if the computer is Microsoft Entra ID joined choose **Other User,** then use .\admin as the user name) 3. In the Windows ***Search*** field (bottom-left section of the screen), enter **cmd** (either long press the screen or right select, and choose ***Run as administrator***). 4. Run the following command (double quotes at end of command are important): @@ -140,38 +128,81 @@ This guidance is for manual configuration. This can also be automated using Intu Proxy settings on Teams Rooms on Android vary by device manufacturer. Consult OEM documentation for how to best configure Teams Rooms on Android devices for a network with a proxy. -## Admin group management +## Wireless network considerations + +We strongly recommend that you connect your Teams Rooms devices to a wired network for greater stability and performance, ensuring a seamless meeting experience. If using a wired connection isn't available, you may opt to use a wireless connection. + +> [!IMPORTANT] +> Wireless networks can be prone to network interference leading to quality degradation. We strongly recommend that you follow your wireless equipment provider's best practices when configuring a wireless connection to improve video and audio quality. + +Here are some examples of wireless network configuration best practices recommended by various manufacturers: + +- Deploy wireless equipment, such as access points and routers, that can handle and distribute the bandwidth load across all connected devices in the network. +- As much as possible, use access points and routers from a single manufacturer to avoid further congesting the radio-spectrum. +- Ensure wireless equipment is installed in a way that reduces or eliminates interference from objects and other equipment. +- Ensure the wireless network shows strong signal strength (Wi-Fi signal showing full bars is preferred) on Teams Rooms and other device screens. +- Default to prioritizing 5-GHz coverage for devices to optimize for higher bandwidth. +- Enable band steering to ensure that 5 GHz is always given more priority when sharing the same network name as 2.4 GHz. +- Keep wireless channel utilization below 50%. +- Keep access point and router firmware up to date with the latest firmware versions and hot fixes. +- Verify that Teams Rooms devices and at least one access point see each other with a signal strength of -60 dBm or better. A dBm value closer to zero is preferred. Follow your equipment manufacturer's recommendations. +- Implement QoS whenever possible to allow monitoring and resolution of issues in real time. + +For more best practices specific to your wireless network hardware, check your manufacturer's documentation. + +You can also troubleshoot wireless network issues using the wireless network report built into Windows 10. For more information, see [Analyze the wireless network report - Microsoft Support](https://support.microsoft.com/windows/analyze-the-wireless-network-report-76da0daa-1db2-6049-d154-7bb679eb03ed). + +## Tenant Restrictions + +For organizations which utilize [tenant restrictions](/entra/identity/enterprise-apps/tenant-restrictions) features of Microsoft Entra ID, this is supported on some Teams Devices if your organization utilizes the proxy deployment variant with header injection. + +#### Teams Rooms on Windows + +To support tenant restrictions, ensure you have your proxy configuration on your Teams Rooms device completed per this Learn document and ensure the Teams Rooms on Windows device has the replacement SSL certificates installed on it to trust the header injected web traffic. + +#### Teams Rooms on Android + +Tenant restrictions aren't supported today on Teams Rooms on Android devices. Consult with your Android device OEM for potential workarounds. + +## Teams Rooms on Windows administrative access + +### Using an admin group If you choose to join a Teams Rooms on Windows device to a domain (Microsoft Entra ID or Active Directory), you can use Microsoft Intune, Group Policy, or Local Computer Management to set a Security Group as local administrator just like you would for a Windows PC in your domain. Anyone who is a member of that security group can enter their credentials and unlock Settings. > [!NOTE] > If your Microsoft Teams Rooms device loses trust with the domain (for example, if you remove the Microsoft Teams Rooms from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. The workaround is to log in with the local Admin account. - -## Local accounts for Teams Rooms on Windows - -### Local 'Skype' User Account - -Teams Rooms includes a passwordless local account named "Skype". This account is used to sign in to Windows to launch the Teams Rooms app. It isn't supported to apply a password to this account. See [Microsoft Teams Rooms security](security.md) for more information. ### Local "Admin" User Account > [!CAUTION] > Be sure to change the Microsoft Teams Rooms password as soon as possible. -Microsoft Teams Rooms default password is set to "sfb". The password can be changed in several ways: +Microsoft Teams Rooms default password is set to `sfb`. The password can be changed in several ways: - Recommended: [Configuring LAPS on Teams Rooms on Windows](/microsoftteams/rooms/laps-authentication) - Intune: [Set-LocalUser](/powershell/module/microsoft.powershell.localaccounts/set-localuser) - Locally: [Change or reset your Windows password](https://support.microsoft.com/windows/change-or-reset-your-windows-password-8271d17c-9f9e-443f-835a-8318c8f68b9c) You can read more about the Admin account in the [Microsoft Teams Rooms security](security.md) article. - + +### Local 'Skype' User Account + +> [!CAUTION] +> Any modifications to the "Skype" user account are not supported by Microsoft and will prevent your Teams Rooms on Windows device from functioning correctly. + +Teams Rooms on Windows include a local account named "Skype" which is passwordless. This account is used to sign in to Windows to launch the Teams Rooms app. For more information on how the "Skype" user is security, review [Microsoft Teams Rooms security](security.md). + ### Machine Account Much like any Windows device, the machine name can be renamed by right-clicking in **Settings** \> **About** \> **Rename PC**. If you would like to rename the computer after joining it to a domain, use [Rename-Computer](/powershell/module/microsoft.powershell.management/rename-computer), a PowerShell command, followed by the computer's new name. - + +## Teams Rooms on Android administrative access + +Local administrative access to Teams Rooms on Android devices is controlled by the Teams device equipment manufacturer. Consult the device documentation for default accounts and passwords and instructions for how to change those passwords. + ## Related articles [Plan Microsoft Teams Rooms](rooms-plan.md) diff --git a/Teams/rooms/rooms-release-note.md b/Teams/rooms/rooms-release-note.md index 769f268b9f..fc9daf1eb2 100644 --- a/Teams/rooms/rooms-release-note.md +++ b/Teams/rooms/rooms-release-note.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: henrikalim -ms.date: 09/30/2024 +ms.date: 10/29/2024 ms.topic: article audience: Admin ms.service: msteams @@ -65,16 +65,30 @@ Teams Rooms app updates happen either using the Microsoft Store or using [manual Features with the :::image type="icon" source="../media/mtr-pro-icon.png"::: icon are available only with Teams Rooms Pro license. ### 5.2.115.0 (9/26/2024) + + >[!NOTE] + >The following two features were added to the 5.2.115.0 release with a service side change on October 31, 2024. + +- **Digital signage** :::image type="icon" source="../media/mtr-pro-icon.png"::: : Inform, connect, and engage your employees with digital signage. Users can view dynamic content and relevant information on front-of-room displays when devices aren't in use. Admins can configure tenant-wide and room-specific settings from the Teams Rooms Pro Management portal. Native integrations with selected third-party digital signage providers ([Appspace](https://docs.appspace.com/latest/devices-app/advanced-registration-microsoft-meeting-room-devices/), [XOGO](https://www.xogo.io/xogo-for-microsoft-teams-rooms)) are available, along with the use of web URLs as signage sources. [Learn more](digital-signage.md). + +- **Enhanced cross-platform meetings using SIP join**:::image type="icon" source="../media/mtr-pro-icon.png"::: **:** Collaboration is seamless and intuitive across all meeting platforms, providing a native Teams Room experience when joining SIP-based conferencing services like Google Meet, Zoom, Cisco Webex, Amazon Chime, RingCentral, and others. Users enjoy the familiar Teams Rooms interface with access to certain third-party in-meeting controls, depending on the platform. Features include up to 1080p video quality, dual screen support, various meeting layouts, and HDMI ingest. This capability requires a SIP calling plan from a Cloud Video Interop (CVI) partner, currently available through Pexip. [Learn more](third-party-join.md). + Introduced in this update: -- **Proximity based join experience improvements**: Proximity based join experience is updated to disable auto accepting all nudges from external or federated tenants. Room admins can allow this depending on the location of the room. In addition, granular controls for ultrasound are added that allow IT admins to select speaker to use to omit ultrasound beacon as well as volume output percentage to fine tune room experience. -- **Dynamic video tile resizing based on people count** :::image type="icon" source="../media/mtr-pro-icon.png"::: **:** The room video tile on Teams desktop client dynamically adjusts size based on the number of people in the room. When one person is in the room, the tile matches the remote participant's size. With two or more people, the room tile expands to be four times larger. Room admins can enable or disable the people count. -- **Microsoft Teams Rooms on Windows room preview shows Cloud IntelliFrame** :::image type="icon" source="../media/mtr-pro-icon.png"::: **:** The Preview video of room will show IntelliFrame when Cloud IntelliFrame is enabled for the room, to let in room participants be aware of how they appear to those online. [Learn more](/microsoftteams/devices/cloud-intelliframe). -- **Roster grouping for in-room participants through proximity join** :::image type="icon" source="../media/mtr-pro-icon.png"::: **:** When joining a meeting in a Microsoft Teams Room on Windows with a companion device, in-room participants will be grouped under the room node. Participants must join through Proximity Join with Microsoft Teams Rooms. -- **Native controls for Group Framing, Active Speaker and Edge-composed IntelliFrame:** Allow users to natively toggle certain camera features provided by OEMs, including group framing, active speaker framing, and edge-composed IntelliFrame. -- **Breakout rooms support:** With breakout room support, Teams Rooms on Windows can be added to a breakout room as an attendee and moved in and out of the main room making it easy for breakout session coordination. -Resolved issues: -- Fixed a known issue where content and gallery were swapped, after reconnecting a screen on dual display setups. +- **Proximity based join experience improvements**: Proximity based join experience is updated to disable auto accepting all nudges from external or federated tenants. In addition, Teams Rooms on Windows with compatible consoles supports proximity join using ultrasound, providing an alternative to Bluetooth. [Learn more](/microsoftteams/rooms/proximity-join?tabs=portal). +- **Dynamic video tile resizing based on people count** :::image type="icon" source="../media/mtr-pro-icon.png"::: **:** The room video tile on Teams desktop client dynamically adjusts size based on the number of people in the room. When one person is in the room, the tile matches the remote participant's size. With two or more people, the room tile expands to be four times larger. Room admins can enable or disable the people count. [Learn more](/microsoftteams/rooms/xml-config-file). +- **Microsoft Teams Rooms on Windows room preview shows Cloud IntelliFrame** :::image type="icon" source="../media/mtr-pro-icon.png"::: **:** The Preview video of room shows IntelliFrame when Cloud IntelliFrame is enabled for the room, to let in room participants be aware of how they appear to those online. [Learn more](/microsoftteams/devices/cloud-intelliframe). +- **Roster grouping for in-room participants through proximity join:** When joining a meeting in a Microsoft Teams Room with a companion device, in-room participants are grouped under the room node. Participants must join through Proximity Join with Microsoft Teams Rooms. [Learn more](https://support.microsoft.com/en-us/office/microsoft-teams-rooms-windows-e667f40e-5aab-40c1-bd68-611fe0002ba2). +- **Native controls for Group Framing, Active Speaker and Edge-composed IntelliFrame:** Allow users to natively toggle certain camera features provided by OEMs, including group framing, active speaker framing, and edge-composed IntelliFrame. [Learn more](https://support.microsoft.com/en-us/office/enhance-hybrid-meetings-with-microsoft-intelliframe-for-teams-rooms-97161377-b746-49dc-992f-97bbf0d590f7). + + > [!NOTE] + > The camera's OEM firmware is required. + +- **Breakout rooms support:** With breakout room support, Teams Rooms on Windows can be added to a breakout room as an attendee and moved in and out of the main room making it easy for breakout session coordination. [Learn more](https://support.microsoft.com/en-us/office/use-breakout-rooms-in-microsoft-teams-meetings-7de1f48a-da07-466c-a5ab-4ebace28e461). + +Resolved issues: + +- Fixed a known issue where content and gallery were swapped, after reconnecting a screen on dual display will set up. - Fixed a known issue where the chat panel is empty after a reboot. - Fixed an issue where sometimes, the on-screen keyboard failed to appear on the console. - Fixed an issue where the app would restart after the device wakes up or while using meet now. @@ -100,12 +114,12 @@ Introduced in this update: **This release is available for all Teams environments, however, GCC-High customers with this version installed won't see new features released from the previous update 5.0.111.0.** This update contains essential bug fixes and performance improvements: -- Fixed an issue where Webview 2 runtime was failing to install after updating to app 5.0.111.0, thereby not getting the new features released in that update. -- Fixed an issue where Teams Rooms app might not fill the display when the display was reconnected and the scaling settings with Console was not synced. +- Fixed an issue where WebView 2 runtime was failing to install after updating to app 5.0.111.0, blocking the new features released in that update. +- Fixed an issue where Teams Rooms app might not fill the display when the display was reconnected and the scaling settings with Console wasn't synced. - Fixed an issue where a blank screen was displayed upon applying a custom theme. - Fixed an issue where Screen sharing from a video teleconferencing device to a Teams Rooms for Windows device doesn't work. - Fixed an issue where some devices failed to setup after a reset by using Zero touch Deployment with Windows Autopilot. -- The ability to change language is now enabled by default. Admins can turn off this feature by setting the Room language setting to 'False'. [Please visit](/microsoftteams/rooms/xml-config-file) to learn more. +- The ability to change language is now enabled by default. Admins can turn off this feature by setting the Room language setting to 'False'. To learn more, see [Teams Rooms XML configuration](/microsoftteams/rooms/xml-config-file). ### 5.0.111.0 (4/24/2024) @@ -116,12 +130,12 @@ Introduced in this update: - **New Teams on Teams Rooms** - This update brings the New Teams available on Teams Desktop to Microsoft Teams Rooms on Windows. With the new Teams app now a part of Teams Rooms on Windows, all Teams Rooms devices can now utilize available resources to optimize room experience and rendering intelligent audio and video more reliably. The New Teams app has parity of experiences, and in addition all new Teams rooms experiences are built on new Teams app. - **Zero Touch Deployment with Windows Autopilot and Pro Management Portal** :::image type="icon" source="../media/mtr-pro-icon.png":::. This update includes app support to enable the end-to-end deployment experience. -- **Ability to change language on Microsoft Teams Rooms on Windows**. With this new feature, end users can change the language of the Microsoft Teams Rooms on the Microsoft Windows app. The language choices offered are the same as those that are offered in the Microsoft Teams desktop app. The language is reverted to the default language when it restarts. To enable this, you will need to set the Room language setting to 'True'. [Please visit](/microsoftteams/rooms/xml-config-file) to learn more. -- **Skype for business deprecation**. Back with the release of app 4.19.57.0, we had announced the end of support for Skype for Business (Server and Online) on Microsoft Teams Rooms. With this update, we have retired the XML settings for SfB as well as ability to sign in or support to Skype for Business meetings. +- **Ability to change language on Microsoft Teams Rooms on Windows**. With this new feature, end users can change the language of the Microsoft Teams Rooms on the Microsoft Windows app. The language choices offered are the same as those that are offered in the Microsoft Teams desktop app. The language is reverted to the default language when it restarts. To enable this, you need to set the Room language setting to 'True'. To learn more, see [Teams Rooms XML configuration](/microsoftteams/rooms/xml-config-file). +- **Skype for business deprecation**. With the release of app 4.19.57.0, we announced the end of support for Skype for Business (Server and Online) on Microsoft Teams Rooms. With this update, we have retired the XML settings for SfB and ability to sign in or support to Skype for Business meetings. - **Meeting Chat shown by default in Gallery View for Teams Rooms on Windows**. Meeting Chat is now shown by default when joining a Teams meeting with Teams Rooms on Windows in Gallery View, making it easier to see incoming chat messages on the front of room display. Admins can configure the default chat experience for a room, and users can make in-meeting changes to show or hide the chat using the touch console. -- **Join meetings with a QR code**. Users can quickly join upcoming meetings by scanning a QR code on the Teams Room home screen using a mobile camera. Users will then enter the room companion mode experience on Teams mobile and the full meeting experience on Teams Rooms. Users can also scan the QR code to start an ad-hoc meeting or cast content from mobile to the front-of-room display. If the user does not have the Teams mobile app, they will be directed to download it after scanning the QR code. Cross-tenant meetings are supported when the organization setting and user policies allow it. IT admins can control the feature from the XML settings or the Teams admin center. [Learn more](/microsoftteams/rooms/teams-rooms-qr-codes). +- **Join meetings with a QR code**. Users can quickly join upcoming meetings by scanning a QR code on the Teams Room home screen using a mobile camera. Users will then enter the room companion mode experience on Teams mobile and the full meeting experience on Teams Rooms. Users can also scan the QR code to start an ad-hoc meeting or cast content from mobile to the front-of-room display. If the user doesn't have the Teams mobile app, they'll be directed to download it after scanning the QR code. Cross-tenant meetings are supported when the organization setting and user policies allow it. IT admins can control the feature from the XML settings or the Teams admin center. [Learn more](/microsoftteams/rooms/teams-rooms-qr-codes). - **4K display UI scaling for Teams Rooms on Windows**. 4K-enabled displays, including front of room displays and touch boards, are natively supported on the Teams Rooms experience. Note: 4K video isn't supported. -- **Improvements to Join with an ID**. Teams meetings continues to be the default option while the option to select joining Zoom meetings with an ID, and others to come, is visually clearer. +- **Improvements to Join with an ID**. Teams meetings continue to be the default option while the option to select joining Zoom meetings with an ID, and others to come, is visually clearer. - **Meeting ID and passcode to join on Teams Rooms on Windows**. Admins can configure and require a meeting ID and passcode to join a meeting on Teams Rooms on Windows to ensure one more level of security and privacy. This feature is available with Teams Rooms Pro license. - **End users can switch IntelliFrame on or off using Stage roster**. @@ -129,8 +143,8 @@ Introduced in this update: - **Integration between Report a Problem and Pro Portal Management:** Admins can configure for easier tracking, via SendFeedbackToPMP XML setting, that when a user sends feedback through Report a Problem from a room with a Microsoft Teams Pro license, each feedback creates an event in the Teams Rooms Pro Management portal. -> [!IMPORTANT] -> Please note that some systems maybe missing the minimum version of the Edge WebView2 runtime. Until Edge Webview2 runtimeversion 110.0.1587.63 or higher is installed, these devices will be missing some features. + > [!IMPORTANT] + > Note that some systems maybe missing the minimum version of the Edge WebView2 runtime. Until Edge Webview2 runtimeversion 110.0.1587.63 or higher is installed, these devices will be missing some features. ### 4.19.82.0 (1/31/2024) @@ -148,9 +162,9 @@ Introduced in this update: - **End of support for Skype for Business server and legacy home screen UI**. Support for Skype for Business and Skype for Business + Microsoft Teams as meeting modes are no longer available, and settings that were required for this set up are removed. The legacy home screen experience is also no longer officially supported. Learn more at [End of support for connecting to Skype for Business server in Microsoft Teams Rooms on Windows](https://techcommunity.microsoft.com/t5/skype-for-business-blog/end-of-support-for-connecting-to-skype-for-business-server-in/ba-p/3915956). - **Touch board form factor support**. Teams Rooms on Windows now support certified Touch board form factors like Surface Hub 3. Touch boards run Teams rooms touch experience on single screen.  Portrait mode/Rotation on Surface Hub 3 is in preview with more optimizations to follow. - **One time passcode (OTP) based setup**:::image type="icon" source="../media/mtr-pro-icon.png":::. One-time passcode (OTP) provides a new and simplified way to set up Teams Room on Windows. During the first-time setup experience, the installer is presented with an option to enter a One-time passcode instead of resource account credentials, eliminating the need to share room account passwords. OTP is then used to automatically fetch the resource account credentials and sign into Teams Rooms. Teams room admins can provision the OTP from the Teams Rooms Pro Management Portal. -- **Front Row Enhancement - Active video speaker promotion**. Front Row now promotes pinned or spotlighted participants to the center stage when there's no shared content in the single and dual display mode to make the most of empty space. For single display mode, when no one is pinned, spotlighted, or sharing content, the most recent active speaker video will be promoted to the center. In dual display mode, when no one is pinned, spotlighted, or sharing content, the two most recent active speaker videos will be promoted to the center on each screen. If someone is sharing content, the most recent active video speaker will be promoted on the right screen. +- **Front Row Enhancement - Active video speaker promotion**. Front Row now promotes pinned or spotlighted participants to the center stage when there's no shared content in the single and dual display mode to make the most of empty space. For single display mode, when no one is pinned, spotlighted, or sharing content, the most recent active speaker video is promoted to the center. In dual display mode, when no one is pinned, spotlighted, or sharing content, the two most recent active speaker videos are promoted to the center on each screen. If someone is sharing content, the most recent active video speaker is promoted on the right screen. - **Support Joining a Teams Live Event as an Attendee**. To join a live event as an attendee and watch the streaming experience, follow the instructions on [Attend a live event in Microsoft Teams](https://support.microsoft.com/office/attend-a-live-event-in-microsoft-teams-a1c7b989-ebb1-4479-b750-c86c9bc98d84). -- **Teams Room on Windows content camera enhancements**. Teams rooms on Windows support content cameras that are [certified by Microsoft](content-camera.md?tabs=Windows#supported-cameras-and-settings) to share analog Whiteboard in rooms. Customers now have the additional choice to connect any Teams certified or any other camera as a content camera on Teams Rooms on Windows to allow ease of use. +- **Teams Room on Windows content camera enhancements**. Teams rooms on Windows support content cameras that are [certified by Microsoft](content-camera.md?tabs=Windows#supported-cameras-and-settings) to share analog Whiteboard in rooms. Customers now have the choice to connect any Teams certified or any other camera as a content camera on Teams Rooms on Windows to allow ease of use. - **Responsive calendar sizing**. The calendar size changes dynamically based on screen width and height to adapt to various front-of-room display sizes. Learn more at [Set up and manage Teams Rooms on Windows custom backgrounds](/microsoftteams/rooms/custom-backgrounds). > [!NOTE] @@ -277,11 +291,11 @@ Introduced in this update: - IT admin can disable Microsoft noise suppression through XML setting3 - IT admin can override download folder cleanup on the device through registry key setting4 - Enabling users to join Teams meeting hosted on another cloud (that is, GCCH customer can join Teams meetings hosted on commercial cloud and vice versa) -- Teams Rooms now blocks launching Microsoft Edge from URLs in PowerPoint Live as an added security measure for Teams rooms with touch displays +- Teams Rooms now block launching Microsoft Edge from URLs in PowerPoint Live as an added security measure for Teams rooms with touch displays - Meet now experience is improved to add instructions for users to invite users to the room - Support for Windows 10 21H2 feature release for Teams rooms -1 Instructions for enrolling public preview MTR Windows devices can be found [here](../public-preview-doc-updates.md#enable-public-preview). +1 Instructions for enrolling Teams Rooms in public preview can be found [here](../public-preview-doc-updates.md#enable-public-preview). 2 For information about setting Front of Room display resolution and scaling remotely through XML, see [Remotely configure layout, scale, and resolution on Teams Rooms displays](manage-front-room-scale-res.md). @@ -304,7 +318,7 @@ Introduced in this update: Introduced in this update: -- Front Row layout (Preview) for MTR on Windows1 +- Front Row layout (Preview) for Teams Rooms on Windows1 - Admin setting to set Front row layout as default - Meet Now and call app update for Teams only, Teams default client modes1,2 - Switch between multiple video cameras in Teams meetings1 @@ -356,7 +370,7 @@ Introduced in this update: > > \*These features are rolled out using Teams service and will work with all application versions greater than 4.9. > -> To join the scheduled meeting both from Teams Mobile app and MTR-W find the room account in roster on the Teams Mobile app and press "Control this room" menu and you can control Call controls from the app. +> To join the scheduled meeting both from Teams Mobile app and Teams Rooms on Windows find the room account in roster on the Teams Mobile app and press "Control this room" menu and you can control Call controls from the app. ### 4.9.12.0 (7/28/2021) @@ -422,7 +436,7 @@ Introduced in this update: Introduced in this update: - See more videos with 3x3 video gallery on front of room displays -- Start local live closed captions from MTR +- Start local live closed captions - Join Zoom meetings from Teams Rooms with Direct Guest Join (Preview) > [!NOTE] @@ -511,7 +525,7 @@ Introduced in this update: - A new content camera feature that enables users to intelligently include a traditional whiteboard into their Teams meeting - Additional improvements to the Console UI to reduce clutter and moved **Settings** into a new side bar that is accessed via More on the console - Disabled share tray button if local content cable isn't connected or a content camera isn't connected -- Fixed an issue with the touch keyboard where it failed to appear the first time only after an MTR system restart +- Fixed an issue with the touch keyboard where it failed to appear the first time only after a system restart - Quality and reliability fixes ### 4.0.105.0 (07/10/2019) @@ -524,7 +538,7 @@ Introduced in this update: - Universal bar for in-meeting call controls for Teams calls/ meetings to provide consistent experience with Microsoft Teams PC/ Web/ Mobile clients1 - Call quality feedback rating after Teams calls/ meetings1 - Receive/render Microsoft Whiteboard on Microsoft Teams Rooms front of room display when shared from PC/ Web/ Mobile Teams client1 2 -- Removed support for Windows 10 Version 1809 upgrades due to compatibility issues with Microsoft Teams Rooms client. Windows 10 Version 19H1 support will be added in future releases +- Removed support for Windows 10 Version 1,809 upgrades due to compatibility issues with Microsoft Teams Rooms client. Windows 10 Version 19H1 support will be added in future releases 1 Microsoft Teams service rollout using Teams rings. This feature might be available earlier or later than 4.0.105.0 client update. @@ -737,6 +751,8 @@ Introduced in this update: |Release |Release date | |---------|---------| +|[1449/1.0.96.2024110701](#144910962024110701-november-2024) | November 2024 | +|[1449/1.0.96.2024101004](#144910962024101004-october-2024) | October 2024 | |[1449/1.0.96.2024091202](#144910962024091202-september-2024) | September 2024 | |[1449/1.0.96.2024080804](#144910962024080804-august-2024) | August 2024 | |[1449/1.0.96.2024061103](#144910962024061103-june-2024) | June 2024 | @@ -768,6 +784,45 @@ Introduced in this update: Features with :::image type="icon" source="../media/mtr-pro-icon.png"::: are only available with Teams Rooms Pro license. +### 1449/1.0.96.2024110701 (November 2024) + +Introduced in this update: + + +- **Dual display mode and swap screens admin controls1**:::image type="icon" source="../media/mtr-pro-icon.png":::. IT admins can deliberately configure Teams Rooms on Android devices to run in dual display mode. Admins can also switch the screens of dual display rooms using the swap screens setting, easily correcting front-of-room displays that were set up invertedly. Both controls are accessible from the device settings and the Teams admin center. This feature requires a Teams Rooms Pro license. + + +- **3x3 video gallery on dual displays2**:::image type="icon" source="../media/mtr-pro-icon.png":::. Dual display rooms can now show up to 18 participant videos (3x3 on each screen) when no content is being shared during meetings. + + + +- **Cloud Intelliframe**:::image type="icon" source="../media/mtr-pro-icon.png":::. Cloud IntelliFrame enhances non-AI cameras, showing in-room participants in individual frames like remote attendees for a more natural, engaging experience. Now, Teams Rooms on Android receive Cloud IntelliFrame video feeds, bringing uniformity across Windows and Android devices. Roadmap ID: 415250. Learn more. + + + +- **Whiteboard enhancements**. When using the whiteboard outside of meetings, your content is retained even when a meeting begins. The whiteboard's contents are preserved and shared with remote participants instantly. You can also use the ‘Follow me’ function to guide participants as you navigate, and collaborative cursors let you see everyone working in real-time. + + + +- **Net Promoter Score (NPS) survey**. Users can rate how likely they are to recommend Microsoft Teams Rooms from 1 to 5 and provide additional comments on NPS surveys delivered on Teams Rooms on Android devices. NPS surveys will show up periodically after meetings end. IT admins can manage policies and allow or prevent room accounts from getting NPS surveys using PowerShell. Learn more. + + + +- **Admin email support for Report a problem**. IT admins can designate an email address for receiving ‘Report a problem’ submissions from Teams Rooms on Android devices. The email address can be set from the device settings and the Teams admin center. + + +1The swap screens setting will only be available on devices with the proper firmware support. If you don’t see the setting on your device, contact the device manufacturer for firmware support timelines. + +2Due to device capability requirements and performance implications, 3x3 video gallery support for dual displays will only be available on the following Teams Rooms on Android devices: Yealink MeetingBar A40, Poly Studio X52, and Poly Studio G62. + +### 1449/1.0.96.2024101004 (October 2024) + +Resolved issues: + +- Resolved a bug to ensure smooth migration to AOSP Device Management in a future release. +- Improved diagnosability for proximity-based meeting join. +- Fixed app crashes and performance issues. + ### 1449/1.0.96.2024091202 (September 2024) Resolved issues: @@ -775,7 +830,7 @@ Resolved issues: - When a secondary external camera is attached, users are unable to switch the room camera in meetings. - Local HDMI content that is projected outside of a meeting gets automatically shared into a meeting. - Incorrect Korean translation of calendar time slots. -- The Join button is not showing up correctly on the calendar for Direct Guest Join meetings. +- The Join button isn't showing up correctly on the calendar for Direct Guest Join meetings. - Various issues causing meetings to crash. - Minor improvements and bug fixes. @@ -789,14 +844,14 @@ Introduced in this update: Resolved issues: - Joining meetings on Cisco devices results in meeting drops and returning to the home screen. -- Built-in Teams backgrounds are not downloading successfully. -- Tapping Meet now on Logitech TAP devices shows a notification that the app does not support launching on secondary displays. +- Built-in Teams backgrounds aren't downloading successfully. +- Tapping Meet now on Logitech TAP devices shows a notification that the app doesn't support launching on secondary displays. - When joining Direct Guest Join meetings while the HDMI ingest cable is connected, the HDMI ingest feed is shown as the room video instead of the local room camera feed. - Volume is increased and decreased by increments of 30 instead of 10 on Logitech devices. -- Participant video gets re-framed from fit-to-frame to fill-frame intermittently on Cisco devices. +- Participant video gets reframed from fit-to-frame to fill-frame intermittently on Cisco devices. - Various meeting and call reliability issues. -1Neat devices are excluded from this rollout of custom backgrounds due to an issue that is unique to Neat devices. Once the issue is resolved, custom backgrounds will be enabled for Neat devices in a later release. +1Custom backgrounds support on Neat Teams rooms devices require firmware version NFC1.20240924.0005 or greater for the compute and NFA1.20240924.0507 or greater for touch controller. ### 1449/1.0.96.2024061103 (June 2024) @@ -809,7 +864,7 @@ Introduced in this update: Introduced in this update: - **Home screen refresh**. The Teams Rooms on Android home screen matches the look and feel of Teams Rooms on Windows, enabling users to engage with a consistent Teams Rooms interface. The touch console features six action buttons and shows the room calendar on the right side of the home screen. If the Bluetooth beaconing setting is enabled, a room tip appears at the bottom left corner of the front-of-room display and touch console for user education. -- **Join meetings with a QR code**. Users can quickly join upcoming meetings by scanning a QR code on the Teams Room home screen using a mobile camera. Users will then enter the room companion mode experience on Teams mobile and the full meeting experience on Teams Rooms. Users can also scan the QR code to start an ad-hoc meeting or cast content from mobile to the front-of-room display. If the user does not have the Teams mobile app, they will be directed to download it after scanning the QR code. Cross-tenant meetings are supported when the organization setting and user policies allow it. IT admins can control the feature from the device settings or the Teams admin center. [Learn more](/microsoftteams/rooms/teams-rooms-qr-codes). +- **Join meetings with a QR code**. Users can quickly join upcoming meetings by scanning a QR code on the Teams Room home screen using a mobile camera. Users will then enter the room companion mode experience on Teams mobile and the full meeting experience on Teams Rooms. Users can also scan the QR code to start an ad-hoc meeting or cast content from mobile to the front-of-room display. If the user doesn't have the Teams mobile app, they'll be directed to download it after scanning the QR code. Cross-tenant meetings are supported when the organization setting and user policies allow it. IT admins can control the feature from the device settings or the Teams admin center. [Learn more](/microsoftteams/rooms/teams-rooms-qr-codes). - **4K local HDMI content sharing**. Users can consume HDMI content in 4K quality on Teams Rooms on Android devices that support 4K HDMI input when users project content to the front-of-room display without joining an online Teams meeting. - **Give feedback support**. The Help button includes a Give feedback option that lets users share their opinions and ideas about Teams Rooms on Android with Microsoft, just like users can do so on Teams desktop, web, mobile, and Teams Rooms on Window clients. This feedback is used to improve the Teams experience. IT admins can enable or disable this feature for users and manage other feedback policies using PowerShell. [Learn more](/microsoftteams/manage-feedback-policies-in-teams). - Performance improvements in meetings including when users share HDMI content. @@ -824,7 +879,7 @@ Introduced in this update: Introduced in this update: -- Bug fixes for app crashes and an issue with the device restart banner that does not auto dismiss. +- Bug fixes for app crashes and an issue with the device restart banner that doesn't auto dismiss. ### 1449/1.0.96.2024020802 (February 2024) @@ -832,7 +887,7 @@ Introduced in this update: - **Meeting ID and passcode**1 :::image type="icon" source="../media/mtr-pro-icon.png":::. IT admins can configure and require users to enter a meeting ID and passcode for joining meetings to ensure a level of security and privacy. - **New calendar views**. A new look with expanded functionalities. Users can view the calendar for the current day and the next day. Any available time slots for 11 minutes or more are shown. A visual indicator (green/purple vertical bar) is added to each time slot for users to easily see whether a room is booked or available. -- **Improved view switcher for Front of Room display controls**. The updated interface for the view switcher menu provides users with more control of the front of room display(s) during a meeting. Users can customize the views to show or hide the meeting chat. For Front Row, users can select which meeting component is displayed on the left and right panel. IT admins can configure the default number of panels and the default component showing on the panel(s) using the local device setting. +- **Improved view switcher for Front of Room display controls**. The updated interface for the view switcher menu provides users with more control of the front of room displays during a meeting. Users can customize the views to show or hide the meeting chat. For Front Row, users can select which meeting component is displayed on the left and right panel. IT admins can configure the default number of panels and the default component showing on the panel(s) using the local device setting. - Support for Teams Premium security features including end-to-end encryption for meetings and sensitivity labels. - Fix for an experience regression in the Call app including support for P2P call and group call. - Reliability and other improvements. @@ -917,11 +972,11 @@ Introduced in this update: Introduced in this update: -- Whenever you want to brainstorm in the office, simply walk up and start whiteboarding using the new whiteboard button on the home screen. With just one touch, you can quickly launch Microsoft Whiteboard and start collaborating outside of a Teams meeting. Admins can enable and control this feature with the **Allow initiate Whiteboard** setting on the device. +- Whenever you want to brainstorm in the office, just walk up and start whiteboarding using the new whiteboard button on the home screen. With just one touch, you can quickly launch Microsoft Whiteboard and start collaborating outside of a Teams meeting. Admins can enable and control this feature with the **Allow initiate Whiteboard** setting on the device. - Seamlessly switch from local to online collaboration by selecting Start meeting on the local whiteboarding screen. This action kicks off an ad-hoc meeting and automatically presents the existing whiteboard. From there, you can add participants into the meeting and contribute across the same whiteboard in real-time. - Microsoft Whiteboard can now be viewed side by side with remote meeting participants using the Content + Gallery layout. Whenever content sharing starts, Content + Gallery will now be the default layout regardless of the content type. - Content sharing in a meeting is more accessible with the redesigned share menu. When you select **Share** in the meeting control bar, you can find all content options that can be shared in one place, including Microsoft Whiteboard. Sharing Microsoft Whiteboard in a meeting is also now supported on resource accounts. [Admins, see instructions on how to manage Microsoft Whiteboard sharing in Teams](/microsoft-365/whiteboard/manage-sharing-organizations) -- We're also introducing a new touch screen support that allows you to control the room system from both the touch display at the front of the room and the touch console, whichever is more convenient. Admins can enable this feature with the **Enable touch screen controls** setting on the device. To further enhance the meeting experience on large screen devices, 4K display is also now supported. +- We're also introducing a new touch screen support that allows you to control the room system from both the touch display at the front of the room and the touch console, whichever is more convenient. Admins can enable this feature with the **Enabled touch screen controls** setting on the device. To further enhance the meeting experience on large screen devices, 4K display is also now supported. - Aside from optimizing touch experiences for local meetings, we're also enriching hybrid meetings through remote camera pan, tilt, and zoom controls support. Remote meeting participants can now control the zoom and orientation of a Teams Rooms camera directly from their desktop during a meeting. [Admins, follow these instructions for enabling this setting](/microsoftteams/meeting-policies-audio-and-video) - Joining a meeting on a room device has also become more inclusive. With chat notifications, you can see incoming chat messages on the front-of-room display and participate in the meeting on equal grounds. Admins can enable this setting in the device settings, and you can temporarily disable this setting using the meeting control bar. @@ -938,7 +993,7 @@ Introduced in this update: ### 1449/1.0.96.2022072103 (August 2022) -In partnership with Cisco, you'll be able to join Cisco WebEx meetings through Microsoft Teams. After you enable **Direct guest** **join** through settings, schedule a new Cisco WebEx meeting or forward an existing meeting to the Teams Room on Android. The meeting will appear on the calendar and will be available to join. +In partnership with Cisco, you're able to join Cisco WebEx meetings through Microsoft Teams. After you enable **Direct guest** **join** through settings, schedule a new Cisco WebEx meeting or forward an existing meeting to the Teams Room on Android. The meeting appears on the calendar and will be available to join. > [!NOTE] > Direct guest join Cisco WebEx will be initially available on Poly. Other manufacturers will receive it shortly after. @@ -947,7 +1002,7 @@ For IT admins who want to learn more about known issues and troubleshooting Team ### 1449/1.0.96.2022051102 (May 2022) -In partnership with Zoom, we're releasing an ability to join Zoom meetings through Microsoft Teams. After you enable **Direct guest** **join** through settings, schedule a new Zoom meeting or forward to an existing Zoom meeting to the Teams Room on Android. The meeting will appear on the calendar and will be available to join. +In partnership with Zoom, we're releasing an ability to join Zoom meetings through Microsoft Teams. After you enable **Direct guest** **join** through settings, schedule a new Zoom meeting or forward to an existing Zoom meeting to the Teams Room on Android. The meeting appears on the calendar and will be available to join. > [!NOTE] > Direct guest join will be initially available on Logitech, Poly, and some Yealink devices. Other manufacturers will receive it shortly after. @@ -967,14 +1022,14 @@ Introduced in this update: - New reactions. - You can view content in the room or share it into the meeting by plugging in an HDMI cable. Available for all certified devices with HDMI capability. - Presenters and organizers are able to control camera and microphone access for all attendees. -- Five new wallpapers to choose from to customize your Teams Rooms on Android devices. These wallpapers will apply to the front-of-room displays in a single and dual screen configuration. +- Five new wallpapers to choose from to customize your Teams Rooms on Android devices. These wallpapers apply to the front-of-room displays in a single and dual screen configuration. - Webinar presenters can now join and participate from the Teams Room on Android devices. - To provide a more cohesive experience, all IT admin settings are combined into one group under device settings for easier room configuration. - These settings are available only on shared room accounts and require a password to access. -- This functionality will be available on a select set of devices. +- This functionality is available on a select set of devices. - A warning message will appear on the front-of-room display when the room is over capacity. - This will initially be available only on these select devices: EPOS EXPAND Vision 3T, Yealink MeetingBar A20, Yealink MeetingBar A30. -- When someone checks in on a Teams panel devices and the previous meeting is running over, a notification will appear on the front-of-room display to inform those people in the room that their meeting is over, and that people are waiting for the room. (Must have a Teams panel device paired with the Teams Room device). +- When someone checks in on a Teams panel devices and the previous meeting is running over, a notification appears on the front-of-room display to inform those people in the room that their meeting is over, and that people are waiting for the room. (Must have a Teams panel device paired with the Teams Room device). ### 1449/1.0.96.2021070803 (July 2021) @@ -991,7 +1046,7 @@ Introduced in this update: - Simplified sign-in screen - IT Admins can do remote provisioning and sign-in of Teams Rooms from the Teams Admin Center -- Use your phone or a secondary Teams device as a remote for the Teams Room. Control mic, camera, volume, live captions, and layout settings via the secondary device +- Use your phone or a secondary Teams device as a remote for the Teams Room. Control mic, camera, volume, live captions, and lay out settings via the secondary device - Select Teams Rooms devices now support projecting your screen via HDMI cable - Live captions now available for one-on-one calls - Presenters and organizers can select to lock a meeting to prevent anyone else from joining the meeting. Go to **More** > **Lock** **meeting** @@ -1001,14 +1056,14 @@ Introduced in this update: ### 1449/1.0.96.2021032002 (April 2021) -Most Teams Rooms on Android devices are compatible with a touch console (for example Poly TC8). When paired with a Teams Rooms system, the console allows you to see the room calendar, join meetings, and place calls directly from the console. During meetings or calls, you'll be able to see current meeting participants, add new ones, switch content layouts, raise hands, and more +Most Teams Rooms on Android devices are compatible with a touch console (for example Poly TC8). When paired with a Teams Rooms system, the console allows you to see the room calendar, join meetings, and place calls directly from the console. During meetings or calls, you're able to see current meeting participants, add new ones, switch content layouts, raise hands, and more -A full-day calendar view will show all scheduled meetings on the system and permit you to join meetings directly from the device. All existing calling and meeting functionality will move to the console and will be arranged along side the calendar. +A full-day calendar view shows all scheduled meetings on the system and permit you to join meetings directly from the device. All existing calling and meeting functionality will move to the console and will be arranged along side the calendar. > [!NOTE] > If the touch console is connected, all actionable functionality will move to the console, but the calendar will remain visible on the connected display for quick reference. -The following features will be available to you when you sign in with your account (e.g. E5 licenses) into the Teams Rooms on Android systems: +The following features are available to you when you sign in with your account (for example, E5 licenses) into the Teams Rooms on Android systems: - Start Microsoft Whiteboard and share the whiteboard in the meeting from the Teams Rooms device. - Start recording during meeting or call. @@ -1018,7 +1073,7 @@ The following features will be available to you when you sign in with your accou Introduced in this update: -- Dual screen support. Some select hardware (e.g., Poly Studio X50) that supports dual display configuration can now have a dual display experience with Teams. It's particularly useful in meetings, where meeting participants will be presented on one display and content on the other +- Dual screen support. Some select hardware (for example, Poly Studio X50) that supports dual display configuration can now have a dual display experience with Teams. It's useful in meetings, where meeting participants are presented on one display and content on the other - Meeting gallery supports 9 participants. Now Teams Rooms on Android will show up to 9 participants on the meeting stage - New layouts. Together mode and Large gallery layouts are now available under the existing Layout button during meetings. These additional layouts are made to highlight video participants better - Spotlight. Teams Rooms on Android will present spotlighted participants as large tiles on the meeting stage similar to content. Only desktop Teams clients are capable of selecting spotlighted participants at this time diff --git a/Teams/rooms/security.md b/Teams/rooms/security.md index 800838677d..ee4c3b8c04 100644 --- a/Teams/rooms/security.md +++ b/Teams/rooms/security.md @@ -1,5 +1,5 @@ --- -title: Microsoft Teams Rooms security +title: Microsoft Teams Rooms on Windows and Teams Android device security author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -18,14 +18,14 @@ ms.collection: f1.keywords: - NOCSH ms.localizationpriority: medium -description: Learn how to secure your Microsoft Teams Rooms on Windows and Android devices. +description: Learn how to your Microsoft Teams Rooms on Windows and Teams Android devices are secure by default. --- -# Microsoft Teams Rooms security +# Microsoft Teams Rooms on Windows and Teams Android device security -This article provides security guidance for Microsoft Teams Rooms devices on both Windows and Android devices. This guidance includes information on hardware, software, network, and account security. +This article provides security guidance for Microsoft Teams Rooms devices on both Windows and Android as well as Teams panels, Teams Phone, and Teams Displays. This guidance includes information on hardware, software, network, and account security. -Select the **Teams Rooms on Windows** or **Teams Rooms for Android** tab for more information on Teams Room security on your device. +Select the **Teams Rooms on Windows** or **Teams Android devices** tab for more information on security for your device. ## [Teams Rooms on Windows](#tab/Windows) @@ -51,19 +51,15 @@ Secure boot is enabled by default. Secure boot is a security standard developed Access to UEFI settings is only possible by attaching a physical keyboard and mouse, which prevents being able to access UEFI via the Teams Rooms touch-enabled console or any other touch-enabled displays attached to Teams Rooms. -Kernel Direct Memory Access (DMA) Protection is a Windows setting that is enabled on Teams Rooms. With this feature, the OS and the system firmware protect the system against malicious and unintended DMA attacks for all DMA-capable devices: +Kernel Direct Memory Access (DMA) Protection is a Windows setting that is enabled on Teams Rooms. With this feature, the OS and the system firmware protect the system against malicious and unintended DMA attacks for all DMA-capable devices: during the boot process and against malicious DMA by devices connected to easily accessible internal/external DMA-capable ports, such as M.2 PCIe slots and Thunderbolt 3, during OS runtime. -- During the boot process. - -- Against malicious DMA by devices connected to easily accessible internal/external DMA-capable ports, such as M.2 PCIe slots and Thunderbolt 3, during OS runtime. - -Teams Rooms also enables Hypervisor-protected code integrity (HVCI). One of the features provided by HVCI is Credential Guard. Credential Guard provides the following benefits: +Teams Rooms also enable Hypervisor-protected code integrity (HVCI). One of the features provided by HVCI is Credential Guard. Credential Guard provides the following benefits: - **Hardware security** NTLM, Kerberos, and Credential Manager take advantage of platform security features, including Secure Boot and virtualization, to protect credentials. - **Virtualization-based security** Windows NTLM and Kerberos derived credentials and other secrets run in a protected environment that is isolated from the running operating system. -- **Better protection against advanced persistent threats** When Credential Manager domain credentials, NTLM, and Kerberos derived credentials are protected using virtualization-based security, the credential theft attack techniques, and tools used in many targeted attacks are blocked. Malware running in the operating system with administrative privileges can't extract secrets that are protected by virtualization-based security. +- **Better protection against advanced persistent threats** When Credential Manager domain credentials, NTLM, and Kerberos derived credentials are protected using Virtualization-based security, the credential theft attack techniques, and tools used in many targeted attacks are blocked. Malware running in the operating system with administrative privileges can't extract secrets that are protected by Virtualization-based security. ## Software Security @@ -74,17 +70,17 @@ After Microsoft Windows boots, Teams Rooms automatically signs into a local Wind The Microsoft Teams Rooms app runs using the Assigned Access feature found in Windows 10 1903 and later. Assigned Access is a feature in Windows that limits the application entry points exposed to the user and enables single-app kiosk mode. Using Shell Launcher, Teams Rooms is configured as a kiosk device that runs a Windows desktop application as the user interface. The Microsoft Teams Rooms app replaces the default shell (explorer.exe) that usually runs when a user logs on. In other words, the traditional Explorer shell doesn't get launched at all which greatly reduces the Microsoft Teams Rooms vulnerability surface within Windows. For more information, see [Configure kiosks and digital signs on Windows desktop editions](/windows/configuration/kiosk-methods). -If you decide to run a security scan or a Center for Internet Security (CIS) benchmark on Teams Rooms, the scan can only run under the context of a local administrator account as the Skype user account doesn't support running applications other than the Teams Rooms app. Many of the security features applied to the Skype user context don't apply to other local users and, as a result, these security scans don't surface the full security lockdown applied to the Skype account. Therefore, we don't recommend to running a local scan on Teams Rooms. However, you can run external penetration tests if so desired. Because of this, we recommend that you run external penetration tests against Teams Rooms devices instead of running local scans. +If you decide to run a security scan or a Center for Internet Security (CIS) benchmark on Teams Rooms, the scan can only run under the context of a local administrator account as the Skype user account doesn't support running applications other than the Teams Rooms app. Many of the security features applied to the Skype user context don't apply to other local users and, as a result, these security scans don't surface the full security lockdown applied to the Skype account. Therefore, we don't recommend to running a local scan on Teams Rooms. However, you can run external penetration tests if so desired. Because of this configuration, we recommend that you run external penetration tests against Teams Rooms devices instead of running local scans. Additionally, lock down policies are applied to limit nonadministrative features from being used. A keyboard filter is enabled to intercept and block potentially insecure keyboard combinations that aren't covered by Assigned Access policies. Only users with local or domain administrative rights are permitted to sign into Windows to manage Teams Rooms. These and other policies applied to Windows on Microsoft Teams Rooms devices are continually assessed and tested during the product lifecycle. -Microsoft Defender is enabled out of the box, the Teams Rooms Pro license also includes Defender for Endpoint, which allows customers to enroll their Teams Rooms into Defender for Endpoint to provide security teams visibility into the security posture of Teams Room on Windows devices from the Defender portal. Teams Rooms on Windows can be enrolled following the steps for [Windows devices](/microsoft-365/security/defender-endpoint/onboarding-endpoint-manager). We don't recommend modifying Teams Rooms using protection rules (or other Defender policies that make configuration changes) as these policies can impact Teams Rooms functionality; however, reporting functionality into the portal is supported. +Microsoft Defender is enabled out of the box. The Teams Rooms Pro license also includes Defender for Endpoint, which allows customers to enroll their Teams Rooms into Defender for Endpoint. This enrollment can provide security teams visibility into the security posture of Teams Room on Windows devices from the Defender portal. Teams Rooms on Windows can be enrolled following the steps for [Windows devices](/microsoft-365/security/defender-endpoint/onboarding-endpoint-manager). We don't recommend modifying Teams Rooms using protection rules (or other Defender policies that make configuration changes) as these policies can impact Teams Rooms functionality; however, reporting functionality into the portal is supported. ## Account Security Teams Rooms devices include an administrative account named "Admin" with a default password. We strongly recommend that you change the default password as soon as possible after you complete setup. -The Admin account isn't required for proper operation of Teams Rooms devices and can be renamed or even deleted. However, before you delete the Admin account, make sure that you set up an alternate local administrator account configured before removing the one that ships with Teams Rooms devices. For more information on how to change a password for a local Windows account using built-in Windows tools or PowerShell, see the following: +The Admin account isn't required for proper operation of Teams Rooms devices and can be renamed or even deleted. However, before you delete the Admin account, make sure that you set up an alternate local administrator account configured before removing the one that ships with Teams Rooms devices. For more information on how to change a password for a local Windows account using built-in Windows tools or PowerShell, see these guides: - [Configuring LAPS on Teams Rooms on Windows](/microsoftteams/rooms/laps-authentication) - [Change or reset your Windows password](https://support.microsoft.com/windows/change-or-reset-your-windows-password-8271d17c-9f9e-443f-835a-8318c8f68b9c) @@ -102,20 +98,22 @@ Don't grant local Administrator permissions to the Skype user account. Windows Configuration Designer can be used to create Windows provisioning packages. Along with changing the local Admin password, you can also do things like changing the machine name and enrolling into Microsoft Entra ID. For more information on creating a Windows Configuration Designer provisioning package, see [Provisioning packages for Windows 10](/windows/configuration/provisioning-packages/provisioning-packages). -You need to create a resource account for each Teams Rooms device so that it can sign into Teams. You can't use user interactive two-factor or multi-factor authentication with this account. Requiring a second factor would prevent the account from being able to automatically sign into the Teams Rooms app after a reboot. In addition, Microsoft Entra Conditional Access policies and Intune Compliance Policies can be deployed to secure the resource account. For more information, see [Supported Conditional Access and Intune device compliance policies for Microsoft Teams Rooms](supported-ca-and-compliance-policies.md) and [Conditional Access and Intune compliance for Microsoft Teams Rooms](conditional-access-and-compliance-for-devices.md). +You need to create a resource account for each Teams Rooms device so that it can sign into Teams. You can't use user interactive two-factor or multifactor authentication with this account. Requiring a user interactive second factor would prevent the account from being able to automatically sign into the Teams Rooms app after a reboot. In addition, Microsoft Entra Conditional Access policies and Intune Compliance Policies can be deployed to secure the resource account and achieve multifactor authentication through other means. For more information, see [Supported Conditional Access and Intune device compliance policies for Microsoft Teams Rooms](supported-ca-and-compliance-policies.md) and [Conditional Access and Intune compliance for Microsoft Teams Rooms](conditional-access-and-compliance-for-devices.md). We recommend that you create the resource account in Microsoft Entra ID, if possible as a cloud-only account. While a synced account can work with Teams Rooms in hybrid deployments, these synced accounts often have difficulty signing into Teams Rooms and can be difficult to troubleshoot. If you choose to use a third-party federation service to authenticate the credentials for the resource account, ensure the third-party IDP responds with the `wsTrustResponse` attribute set to `urn:oasis:names:tc:SAML:1.0:assertion`. If your organization doesn't want to use WS-Trust, use cloud-only accounts instead. ## Network Security -Generally, Teams Rooms has the same network requirements as any Microsoft Teams client. Access through firewalls and other security devices is the same for Teams Rooms as for any other Microsoft Teams client. Specific to Teams Rooms, the categories listed as "required" for Teams must be open on your firewall. Teams Rooms also needs access to Windows Update, Microsoft Store, and Microsoft Intune (if you use Microsoft Intune to manage your devices). For the full list of IPs and URLs required for Microsoft Teams Rooms, see: +Generally, Teams Rooms has the same network requirements as any Microsoft Teams client. Access through firewalls and other security devices is the same for Teams Rooms as for any other Microsoft Teams client. Specific to Teams Rooms, the categories listed as "required" for Teams must be open on your firewall. Teams Rooms also need access to Windows Update, Microsoft Store, and Microsoft Intune (if you use Microsoft Intune to manage your devices). For the full list of IPs and URLs required for Microsoft Teams Rooms, see: -- **Microsoft Teams, Exchange Online, SharePoint Online, Microsoft 365 Common, and Office Online** [Office 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams) +- **Microsoft Teams, Exchange Online, SharePoint, Microsoft 365 Common, and Office Online** [Office 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams) - **Windows Update** [Configure WSUS](/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus#211-connection-from-the-wsus-server-to-the-internet) -- **Microsoft Store** [Prerequisites for Microsoft Store for Business and Education](/microsoft-store/prerequisites-microsoft-store-for-business#proxy-configuration) +- **Microsoft Store** [Microsoft Store endpoints](/mem/intune/fundamentals/intune-endpoints#microsoft-store) - **Microsoft Intune** [Network Endpoints for Microsoft Intune](/mem/intune/fundamentals/intune-endpoints) +- **Telemetry client endpoint**: vortex.data.microsoft.com +- **Telemetry settings endpoint**: settings.data.microsoft.com -If you're using the Microsoft Teams Rooms managed services component of Microsoft Teams Rooms Pro, you also need to make sure that Teams Rooms can access the following URLs: +For Microsoft Teams Rooms Pro Management Portal, you also need to make sure that Teams Rooms can access the following URLs: - agent.rooms.microsoft.com - global.azure-devices-provisioning.net @@ -128,32 +126,32 @@ If you're using the Microsoft Teams Rooms managed services component of Microsof - mmrprodemeastor.blob.core.windows.net - mmrprodnoamiot.azure-devices.net - mmrprodnoamstor.blob.core.windows.net +- mmrprodnoampubsub.webpubsub.azure.com +- mmrprodemeapubsub.webpubsub.azure.com +- mmrprodapacpubsub.webpubsub.azure.com **GCC customers will also need to enable the following URLs:** - mmrprodgcciot.azure-devices.net - mmrprodgccstor.blob.core.windows.net -Teams Rooms is configured to automatically keep itself patched with the latest Windows updates, including security updates. Teams Rooms installs any pending updates every day beginning at 2:00am using a preset local policy. There's no need to use other tools to deploy and apply Windows Updates. Using other tools to deploy and apply updates can delay the installation of Windows patches and thus lead to a less secure deployment. The Teams Rooms app is deployed using the Microsoft Store. +Teams Rooms is configured to automatically keep itself patched with the latest Windows updates, including security updates. Teams Rooms installs any pending updates every day beginning between 2:00 - 3:00 am local device time using a preset local policy. There's no need to use other tools to deploy and apply Windows Updates. Using other tools to deploy and apply updates can delay the installation of Windows patches and thus lead to a less secure deployment. The Teams Rooms app is deployed using the Microsoft Store. Teams Rooms devices work with most 802.1X or other network-based security protocols. However, we're not able to test Teams Rooms against all possible network security configurations. Therefore, if performance issues arise that can be traced to network performance issues, you may need to disable these protocols. -For optimum performance of real time media, we strongly recommend that you configure Teams media traffic to bypass proxy servers and other network security devices. Real time media is very latency sensitive and proxy servers and network security devices can significantly degrade users' video and audio quality. Also, because Teams media is already encrypted, there's no tangible benefit from passing the traffic through a proxy server. For more information, see [Networking up (to the cloud)—One architect’s viewpoint](/microsoft-365/solutions/networking-design-principles), which discusses network recommendations to improve the performance of media with Microsoft Teams and Microsoft Teams Rooms. - -> [!IMPORTANT] -> Teams Rooms doesn't support authenticated proxy servers. +For optimum performance of real time media, we strongly recommend that you configure Teams media traffic to bypass proxy servers and other network security devices. Real time media is very latency sensitive and proxy servers and network security devices can significantly degrade users' video and audio quality. Also, because Teams media is already encrypted, there's no tangible benefit from passing the traffic through a proxy server. For more information, see [Networking up (to the cloud)—One architect’s viewpoint](/microsoft-365/solutions/networking-design-principles), which discusses network recommendations to improve the performance of media with Microsoft Teams and Microsoft Teams Rooms. If your organization utilizes tenant restrictions, it's supported for Teams Rooms on Windows devices following the configuration guidance in the [prepare your environment](/microsoftteams/rooms/rooms-prep#tenant-restrictions) document. Teams Rooms devices don't need to connect to an internal LAN. Consider placing Teams Rooms in a secure isolated network segment with direct Internet access. If your internal LAN becomes compromised, the attack vector opportunities towards Teams Rooms is reduced. -We strongly recommend that you connect your Teams Rooms devices to a wired network. The use of wireless networks requires careful planning and assessment for the best experience. For more information, see [Wireless network considerations](rooms-plan.md#wireless-network-considerations). +We strongly recommend that you connect your Teams Rooms devices to a wired network. The use of wireless networks requires careful planning and assessment for the best experience. For more information, see [Wireless network considerations](rooms-prep.md#wireless-network-considerations). -Proximity Join and other Teams Rooms features rely on Bluetooth. However, the Bluetooth implementation on Teams Rooms devices doesn't allow for an external device connection to a Teams Rooms device. Bluetooth technology use on Teams Rooms devices is currently limited to advertising beacons and prompted proximal connections. The `ADV_NONCONN_INT` protocol data unit (PDU) type is used in the advertising beacon. This PDU type is for nonconnectable devices advertising information to the listening device. There's no Bluetooth device pairing as part of these features. Additional details on Bluetooth protocols can be found on the [Bluetooth SIG website](https://www.bluetooth.com/blog/bluetooth-low-energy-it-starts-with-advertising/). +Proximity Join and other Teams Rooms features rely on Bluetooth. However, the Bluetooth implementation on Teams Rooms devices doesn't allow for an external device connection to a Teams Rooms device. Bluetooth technology use on Teams Rooms devices is currently limited to advertising beacons and prompted proximal connections. The `ADV_NONCONN_INT` protocol data unit (PDU) type is used in the advertising beacon. This PDU type is for nonconnectable devices advertising information to the listening device. There's no Bluetooth device pairing as part of these features. More details on Bluetooth protocols can be found on the [Bluetooth SIG website](https://www.bluetooth.com/blog/bluetooth-low-energy-it-starts-with-advertising/). -## [Teams Rooms on Android](#tab/Android) +## [Teams Android devices](#tab/Android) -This article doesn't cover Android devices configured for dedicated device mode by Microsoft Endpoint Manager. Teams Android devices run in Kiosk mode by design. For information about Android Kiosk, see [Android Enterprise dedicated device enrollment](/mem/intune/enrollment/android-kiosk-enroll). +This article is specific to Teams Android devices (Teams Rooms on Android, Teams panels, Teams Phone, & Teams Displays). This article doesn't cover Android devices configured for dedicated device mode by Microsoft Endpoint Manager. -Microsoft works with our OEM partners to deliver a solution that is secure by design, and customizable to meet customer needs. This article discusses many of the security features found in Teams Android devices and our approach. It's split into four key sections for ease of navigation. +Microsoft works with our OEM partners to deliver a solution that is secure by design, and customizable to meet customer needs. This article discusses many of the security features found in Teams Android devices and our approach. > [!NOTE] > Microsoft Teams Android devices shouldn't be treated as a typical Android device. Teams Android devices are purpose-built appliances designed for use with Teams and their respective use cases. This article applies to certified and dedicated Microsoft Teams devices running the Android operating system only. Teams certified devices can only be purchased from certified OEM vendors. For information about Microsoft Teams certified Android devices, see [Teams Rooms certified systems and peripherals](certified-hardware.md). @@ -181,11 +179,11 @@ All Microsoft and OEM applications are code signed. Code signing helps validatin ### Third party applications -Teams certified devices don't have the Google Play Store, Amazon App Store, or Google Play Services, installed by design. This helps to ensure that no third-party applications can be installed from the store onto a device. +To ensure that no third-party applications can be installed, Teams certified devices don't have the Google Play Store, Amazon Appstore, or Google Play Services, installed by design. ### Android debug bridge -Android debug bridge (ADB) is disabled by design on all Teams Android devices running release software. ADB is a command line tool that enables administrators to perform functions on Android-based devices and enables installation of apps, access to the device shell, and other admin functions. +Android debug bridge (ADB) is disabled on all Teams Android devices running release software. ADB is a command line tool that enables administrators to perform functions on Android-based devices and enables installation of apps, access to the device shell, and other admin functions. ### File system encryption @@ -211,7 +209,7 @@ Teams Android devices are also compatible with some conditional access policies, ### Local device administrator account -Teams Android devices include an administrative account to access device settings, the local web server if one's installed, and any OEM specific settings. +Teams Android devices include an administrative account to access device settings, the local web server (if installed), and any OEM specific settings. Initial device setup and configuration items such as the default username and password for this account can be obtained from the device manufacturer. @@ -219,7 +217,7 @@ Initial device setup and configuration items such as the default username and pa > Be sure to change the local device administrator password as soon as possible. > [!TIP] -> The Teams admin center can be used to change the local device administrator password of a signed-in Teams Android device by applying a configuration profile. We recommend this approach after initial device sign-in to protect elevated features of an Android device. Elevated features can include device settings and web admin portals if they're supported. +> Teams Admin Center can be used to change the local device administrator password of a signed-in Teams Android device by applying a configuration profile. We recommend this approach after initial device sign-in to protect elevated features of an Android device. Elevated features can include device settings and web admin portals if they're supported. ### User or resource account @@ -227,7 +225,7 @@ Teams Android devices require the use of a user, or dedicated resource account, ### Device updates -Teams Android devices are configured to download Microsoft-certified updates from the Teams admin center when they become available. These updates can be pushed automatically or manually invoked by an Administrator. Third-party tools from our OEM partners is also available to perform this function if necessary. Teams Android devices can install updates after hours to avoid impact to users. After hours schedules can be configured in the Teams admin center or using third-party tools from OEM partners. +Teams Android devices are configured to download Microsoft-certified updates from Teams Admin Center when they become available. These updates can be pushed automatically or manually invoked by an Administrator. Third-party tools from our OEM partners are also available to perform this function if necessary. Teams Android devices can install updates after hours to avoid impact to users. After-hours schedules can be configured in the Teams admin center or using third-party tools from OEM partners. > [!IMPORTANT] > Microsoft recommends the management of firmware for all Teams Android devices is done via the Teams admin center. @@ -236,11 +234,11 @@ Teams Android devices are configured to download Microsoft-certified updates fro Teams Android devices have the same network requirements as any Microsoft Teams client, including access through firewalls and other security devices. Specifically, the categories listed as **required** for Teams must be open on your firewall along with other supporting services as listed below. For the full list of IPs and URLs required for Teams Android devices, see: -- Microsoft Teams, Exchange Online, SharePoint Online, Microsoft 365 Common, and Office Online [Office 365 URLs and IP address range](/microsoft-365/enterprise/urls-and-ip-address-ranges) +- Microsoft Teams, Exchange Online, SharePoint, Microsoft 365 Common, and Office Online [Office 365 URLs and IP address range](/microsoft-365/enterprise/urls-and-ip-address-ranges) - Microsoft Intune [Network Endpoints for Microsoft Intune](/mem/intune/fundamentals/intune-endpoints) -Teams Android devices work with most 802.1X and other network-based security protocols. However, we can't test Teams Android devices against all network security configurations. Therefore, if performance issues arise that can be traced to network performance issues, you may need to disable these protocols if they're configured in your organization, or contact your OEM partner for assistance. +Teams Android devices work with most 802.1X and other network-based security protocols. However, we can't test Teams Android devices against all network security configurations. Therefore, if performance issues arise that due to network performance issues, you may need to disable these protocols, or contact your OEM partner for assistance. For optimum performance of real time media, we strongly recommend that you configure Teams media traffic to bypass proxy servers and other network security devices. Real time media is sensitive to network latency, which can be caused by proxy servers and other network security devices. Network latency can significantly degrade users' video and audio quality. For more information, see [Networking up (to the cloud)—One architect’s viewpoint](/microsoft-365/solutions/networking-design-principles), which discusses network recommendations to improve the performance of media with Microsoft Teams. @@ -251,7 +249,7 @@ Teams Android devices use encrypted communications and endpoint authentication o Teams Android devices don't need to connect to an internal LAN. Consider placing Teams Android devices in a secure network segment with direct Internet access. For example, Teams Phones could be deployed on a voice VLAN. If your internal LAN becomes compromised, the attack vector opportunities towards Teams Android devices is reduced by implementing this network segregation. -We strongly recommend that you connect your Teams Rooms devices to a wired network. The use of wireless networks requires careful planning and assessment for the best experience. For more information, see [Wireless network considerations](rooms-plan.md#wireless-network-considerations). +We strongly recommend that you connect your Teams Rooms devices to a wired network. The use of wireless networks requires careful planning and assessment for the best experience. For more information, see [Wireless network considerations](rooms-prep.md#wireless-network-considerations). Proximity Join, Better Together, Teams Cast, and pairing of Teams panels rely on Bluetooth. Bluetooth technology use on Teams Rooms on Android devices is currently limited to advertising beacons and prompted proximal connections. The `ADV_NONCONN_INT` protocol data unit (PDU) type is used in the advertising beacon. This PDU type is for nonconnectable devices advertising information to the listening device. There's no Bluetooth device pairing as part of these features. More details on Bluetooth protocols can be found on the Bluetooth SIG website. diff --git a/Teams/rooms/supported-ca-and-compliance-policies.md b/Teams/rooms/supported-ca-and-compliance-policies.md index ddf55fccce..e34afe4a82 100644 --- a/Teams/rooms/supported-ca-and-compliance-policies.md +++ b/Teams/rooms/supported-ca-and-compliance-policies.md @@ -27,71 +27,66 @@ This article provides supported Conditional Access and Intune device compliance [!INCLUDE [teams-pro-license-requirement](../includes/teams-pro-license-requirement.md)] > [!NOTE] -> Teams Rooms must already be deployed on the devices you want to assign -Conditional Access policies to. If you haven't deployed Teams Rooms yet, -see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md) -and [Deploy Microsoft Teams Rooms on Android](../devices/collab-bar-deploy.md) +> Teams Rooms must be already deployed on the devices if you want to assign Conditional Access policies. If you haven't deployed Teams Rooms yet, see [Create resource accounts for rooms and shared Teams devices](create-resource-account.md) and [Deploy Microsoft Teams Rooms on Android](../devices/collab-bar-deploy.md) for more information. ## Supported Conditional Access policies The following list includes the supported Conditional Access policies for Teams Rooms on Windows and Android, and for policies on Teams panels, phones, and displays. -| Assignment | Teams Rooms on Windows | Teams Rooms on Android and panels | Teams phones and displays | -|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| User or workload identities | Supported | Supported | Supported | -| Cloud apps or actions | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | -| **Conditions** | --- | --- | --- | -| User risk | Supported | Supported | Supported | -| Sign-in risk | Supported | Supported | Supported | -| Device platforms | Supported | Supported | Supported | -| Locations | Supported | Supported | Supported | -| Client apps | Not supported | Not supported | Not supported | -| Filter for devices | Supported | Supported | Supported | -| **Grant** | --- | --- | --- | +| Assignment | Teams Rooms on Windows | Teams Rooms on Android and panels | Teams phones and displays | +|:-----|:-----|:-----|:-----| +| User or workload identities | Supported | Supported | Supported | +| Cloud apps or actions | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | Supported

    Teams Rooms needs to access the following Cloud apps: Office 365, Office 365 Exchange Online, Office 365 SharePoint Online, and Microsoft Teams Services | +| **Conditions** |---|---|---| +| User risk | Supported | Supported | Supported | +| Sign-in risk | Supported | Supported | Supported | +| Device platforms | Supported | Supported | Supported | +| Locations | Supported | Supported | Supported | +| Client apps | Not supported | Not supported| Not supported | +| Filter for devices | Supported | Supported | Supported | +| Authentication flows | Supported | Not supported

    Device code flow is required for sign in. | Not supported

    Device code flow is required for sign in. | +| **Grant** | --- |--- | --- | | Block access | Supported | Supported | Supported | | Grant access | Supported | Supported | Supported | | Require multi-factor authentication | Not supported | Not supported | Supported | -| Require authentication strength | Not supported | Not Supported | Not supported +| Require authentication strength | Not supported | Not Supported | Not supported | Require device to be marked as compliant | Supported | Supported | Supported | | Require Microsoft Entra hybrid joined device | Not supported | Not supported | Not supported | | Require approved client app | Not supported | Not supported | Not supported | | Require app protection policy | Not supported | Not supported | Not supported | -| Require password change | Not supported | Not supported | Not supported -| **Sessions** | --- | --- | --- +| Require password change | Not supported | Not supported | Not supported | +| **Sessions** | --- | --- | --- | | Use app enforced restrictions | Not supported | Not supported | Not Supported | -| Use Conditional Access App Control | Not supported | Not Supported | Not supported -| Sign-in frequency | Supported | Supported | Supported | -| Persistent browser session | Not supported | Not supported | Not supported | -| Customize conditional access evaluation | Not supported | Not supported | Not supported | -| Disable resiliency defaults | Not supported | Not supported | Not supported -| Require token protection for sign-in sessions (Preview) | Not supported | Not supported | Not supported +| Use Conditional Access App Control | Not supported | Not Supported | Not supported +| Sign-in frequency | Supported| Supported | Supported | +| Persistent browser session | Not supported | Not supported | Not supported | +| Customize conditional access evaluation | Not supported | Not supported | Not supported | +| Disable resiliency defaults | Not supported | Not supported | Not supported +| Require token protection for sign-in sessions (Preview) | Not supported | Not supported | Not supported > [!NOTE] > Using Conditional Access policies with Sign-in frequency configured, will make all Teams Android devices periodicly sign out. This is expected behavior. -> + > [!NOTE] > Authentication Strength including but not limited to, FIDO2 Security keys, is not supported for use with Conditional Access policys that will affect all Teams Devices. - ## Supported device compliance policies -Microsoft Teams Rooms on Windows and Teams Rooms on Android support -different device compliance policies. +Microsoft Teams Rooms on Windows and Teams Rooms on Android support different device compliance policies. #### [Teams Rooms on Windows](#tab/mtr-w) -Below is a table of device compliance settings and recommendations for -their use with Teams Rooms. +Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Policy | Availability | Notes | +|--------------|---------------|----------------| | [**Device health**](/mem/intune/protect/compliance-policy-create-windows#device-health) | -- | -- | -| Require BitLocker | Supported | Only use if you have first enabled BitLocker on Teams Rooms. | +| Require BitLocker | Supported | Only use if you have enabled BitLocker first on Teams Rooms. | | Require Secure Boot to be enabled on the device | Supported | Secure Boot is a requirement for Teams Rooms. | | Require code integrity | Supported | Code integrity is already a requirement for Teams Rooms. | -| [**Device Properties**](/mem/intune/protect/compliance-policy-create-windows#device-properties) | -- | -- | -| Operating System Version (minimum, maximum) | Not supported | Teams Rooms automatically updates to newer versions of Windows and setting values here could prevent successful sign-in after an OS update. | +| [**Device Properties**](/mem/intune/protect/compliance-policy-create-windows#device-properties) -- | | +| Operating System Version (minimum, maximum) | Not supported | Teams Rooms automatically will update to newer versions of Windows and setting values here could prevent successful sign-in after an OS update. | | OS version for mobile devices (minimum, maximum) | Not supported. | | | Valid operating system builds | Not supported | | | [**Configuration Manager Compliance**](/mem/intune/protect/compliance-policy-create-windows#device-properties) | -- | -- | @@ -104,7 +99,7 @@ their use with Teams Rooms. | Antivirus | Supported | Antivirus (Windows Defender) is already a requirement for Teams Rooms. | | Antispyware | Supported | Antispyware (Windows Defender) is already a requirement for Teams Rooms. | | Microsoft Defender Antimalware | Supported | Microsoft Defender Antimalware is already a requirement for Teams Rooms. | -| Microsoft Defender Antimalware minimum version | Not supported. | Teams Rooms automatically updates this component so there's no need to set compliance policies. | +| Microsoft Defender Antimalware minimum version | Not supported. | Teams Rooms will automatically update this component so there's no need to set compliance policies. | | Microsoft Defender Antimalware security intelligence up-to-date | Supported | Validate that Microsoft Defender Antimalware is already a requirement for Teams Rooms. | | Real-time protection | Supported | Real-time protections are already a requirement for Teams Rooms. | | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-windows#microsoft-defender-for-endpoint) | -- | -- | @@ -112,11 +107,10 @@ their use with Teams Rooms. #### [Teams Rooms on Android](#tab/mtr-a) -Below is a table of device compliance settings and recommendations for -their use with Teams Rooms. +Below is a table of device compliance settings and recommendations for their use with Teams Rooms. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| Policy | Availability | Notes | +|--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | @@ -136,10 +130,9 @@ their use with Teams Rooms. | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | -| Maximum minutes of inactivity before password are required | Not supported | - | +| Maximum minutes of inactivity before password are required | Not supported | | Require a password to unlock mobile devices | Not supported | | | [**Android 10 and later**](/mem/intune/protect/compliance-policy-create-android#android-10-and-later) | -- | -- | | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | @@ -149,8 +142,8 @@ their use with Teams Rooms. Below is a table of device compliance settings and recommendations for their use with Teams phones and displays. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| +| Policy | Availability | Notes | +|--------------|---------------|----------------| | [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | | Require the device to be at or under the machine risk score | Not supported | | | [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | @@ -170,7 +163,7 @@ Below is a table of device compliance settings and recommendations for their use | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | | Maximum minutes of inactivity before password are required | Not supported | | | Require a password to unlock mobile devices | Not supported | | @@ -178,20 +171,18 @@ Below is a table of device compliance settings and recommendations for their use | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | | Required password type | Not supported | | - - #### [Teams panels](#tab/panels) Below is a table of device compliance settings and recommendations for their use with Teams panels. -| Policy | Availability | Notes | -|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------| -| [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | -| Require the device to be at or under the machine risk score | Not supported | | -| [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | -| Device managed with device administrator | Required | Teams Android devices management requires device administrator to be enabled. | -| Rooted devices | Supported | | -| Require the device to be at or under the device threat level | Not supported | | +| Policy | Availability | Notes | +|--------------|---------------|----------------| +| [**Microsoft Defender for Endpoint**](/mem/intune/protect/compliance-policy-create-android#microsoft-defender-for-endpoint) | -- | -- | +| Require the device to be at or under the machine risk score | Not supported | | +| [**Device Health**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | +| Device managed with device administrator | Required | Teams Android devices management requires device administrator to be enabled. | +| Rooted devices | Supported | | +| Require the device to be at or under the device threat level | Not supported | | | [**Google Play Protect**](/mem/intune/protect/compliance-policy-create-android#device-health) | -- | -- | | Google Play Services is configured | Not supported | Google play isn't installed on Teams Android devices. | | Up-to-date security provider | Not supported | Google play isn't installed on Teams Android devices. | @@ -205,7 +196,7 @@ Below is a table of device compliance settings and recommendations for their use | Block apps from unknown sources | Not supported | Only Teams admins install apps or OEM tools | | Company Portal app runtime integrity | Supported | | | Restricted apps | Not supported | | -| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement is not allowed on production devices. | +| Block USB debugging on device | Not Supported | Not Applicable. ADB enablement isn't allowed on production devices. | | [**All Android devices*](/mem/intune/protect/compliance-policy-create-android#all-android-devices) | -- | -- | | Maximum minutes of inactivity before password are required | Not supported | | | Require a password to unlock mobile devices | Not supported | | @@ -213,4 +204,3 @@ Below is a table of device compliance settings and recommendations for their use | [**Android 9 and earlier or Samsung Knox**](/mem/intune/protect/compliance-policy-create-android#android-9-and-earlier-or-samsung-knox) | -- | -- | | Required password type | Not supported | | ---- diff --git a/Teams/rooms/teams-devices-feature-comparison.md b/Teams/rooms/teams-devices-feature-comparison.md index 0652c7c76f..f340d91834 100644 --- a/Teams/rooms/teams-devices-feature-comparison.md +++ b/Teams/rooms/teams-devices-feature-comparison.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: mattslomka -ms.date: 4/24/2024 +ms.date: 10/31/2024 ms.topic: article audience: Admin ms.service: msteams @@ -24,13 +24,13 @@ description: A guide comparing the Teams devices for shared spaces features betw # Teams Device feature comparison (Windows, Android, & Panels) -Microsoft Teams Rooms experiences are designed with customers in mind. Every customer has unique needs, which is why Microsoft offers a breadth of options, including Teams Rooms on Windows and on Android as well as Teams panels mounted outside of the conference room. +Microsoft Teams Rooms experiences are designed with customers in mind. Microsoft offers a breadth of options: Teams Rooms on Windows, Teams Rooms on Android, and Teams panels mounted outside of the conference room. Core functionality is available on all platforms so end users can always have great audio and video experiences, use one-touch join to join meetings, and access inclusive features. -As Microsoft brings new features to Teams and to Teams Rooms, we strive to bring them to all platforms, but features may roll out at different times due to many factors, including things like technical feasibility and customer feedback for each platform. This means you may see some features rolling out on Windows before they come to the Android platform. Items listed here are supported in the Teams application, confirm supportability with the hardware vendor you select. +As Microsoft brings new features to Teams and to Teams Rooms, we strive to bring them to all platforms, but features may roll out at different times due to many factors, including things like technical feasibility and customer feedback for each platform. This means you may see some features rolling out on Windows before they come to the Android platform. Items listed here are supported in the Teams application. Confirm supportability with the hardware vendor you select. -To help guide you as to what features are available on different platforms, you can refer to the chart (government tenants can refer to the respective tabs), which is updated periodically. Not all Teams Rooms features will be included on this list, continue to consult the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap) and Microsoft sales representatives for more information. +To help guide you as to what features are available on different platforms, you can refer to the chart including tabs for Government Commercial Cloud (GCC) and Government Commercial Cloud High (GCC-H). Not all Teams Rooms features are included on this list. For roadmap items, continue to consult the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap) and Microsoft sales representatives. ## [Commercial](#tab/Commercial) @@ -46,8 +46,9 @@ To help guide you as to what features are available on different platforms, you | | Teams Meeting with ID | Available | Available | | | Direct guest join | BlueJeans: Available
    Webex: Available
    Zoom: Available| BlueJeans: Not available
    Webex: Available
    Zoom: Available | | | Direct guest join with ID | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | -| | SIP/H.323 calling | Available | Not available | -| | PSTN calling | Available | Available| +| | Enhanced cross-platform meetings using SIP join | Available | Not available | +| | SIP/H.323 dialing | Available | Not available | +| | Telephone calling | Available | Available| | | Admins can require meeting ID and passcode on meeting join | Available | Available | | | Cross cloud meeting join (for example, Commercial > GCC or GCC High > GCC) | Available | Not available | | **Meeting engagement and collaboration** | Intuitive, purpose-built app experience| Available | Available | @@ -62,13 +63,15 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | | | Teams Town Hall (Attendee role) | Not available | Not available | | | Teams Live Event (Presenter role) | Available | Not available | | | Teams Live Event (Attendee role) | Available | Not available | +| | Teams Webinar (Presenter role) | Available | Available | +| | Teams Webinar (Attendee role) | Not available | Not available | | | Overflow Meeting Join (1k+ meeting participants) | Available | Not available | | | Microsoft Whiteboard - Initiate during a Teams Meeting | Available | Available | | | Microsoft Whiteboard - Initiate without a Teams Meeting (from a console) | Not available | Available | @@ -86,7 +89,7 @@ To help guide you as to what features are available on different platforms, you | | Rate my call report | Available | Not available | | | Net promoter score (NPS) at meeting end| Available | Not available | | | Meeting controls on touch enabled front of room displays | Not available | Available | -| | Smart Camera Controls | Available | Available| +| | Smart Camera Controls | Available | Available | | | Local pan tilt zoom (PTZ) controls | Not available | Not available | | | Remote Pan tilt zoom (PTZ) control | Available | Available | | | Switch between multiple in-room cameras | Available | Available| @@ -107,8 +110,10 @@ To help guide you as to what features are available on different platforms, you | | Microsoft Defender for Endpoint | Available | Not available | | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | Available | Available | +| | Digital signage | Available | Not available | | | Unauthenticated proxy support | Available | Available | -| | Authenticated proxy support | Not available | Not available | +| | Authenticated proxy support | Available | Not available | +| | Tenant restrictions | Available | Not available | | **Teams Admin Center** | Automatic onboarding | Available | Available | | | Device inventory views | Available | Available | | | Overall device health monitoring | Available | Available | @@ -152,8 +157,13 @@ To help guide you as to what features are available on different platforms, you | | Room capacity notifications | Available | | **Customization** | View room equipment| Available | | | Built-in backgrounds | Available | +| | Custom background | Available | | | Line of business apps | Available | | | Change color of LED lights | Available | +| **Device Management** | Unauthenticated proxy support | Available | +| | Authenticated proxy support | Not available | +| | Tenant restrictions | Not available | + ## [GCC](#tab/GCC) @@ -169,8 +179,9 @@ To help guide you as to what features are available on different platforms, you | | Teams Meeting with ID | Available | Available | | | Direct guest join | BlueJeans: Available
    Webex: Available
    Zoom: Available| BlueJeans: Not available
    Webex: Available
    Zoom: Available | | | Direct guest join with ID | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | -| | SIP/H.323 calling | Available | Not available | -| | PSTN calling | Available | Available | +| | Enhanced cross-platform meetings using SIP join | Available | Not available | +| | SIP/H.323 dialing | Available | Not available | +| | Telephone calling | Available | Available | | | Admins can require meeting ID and passcode on meeting join | Available | Available | | | Cross cloud meeting join (for example, Commercial > GCC or GCC High > GCC) | Available | Not available | | **Meeting engagement and collaboration** | Intuitive, purpose-built app experience| Available | Available | @@ -185,13 +196,15 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Not available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | | | Teams Town Hall (Attendee role) | Not available | Not available | | | Teams Live Event (Presenter role) | Available | Not available | | | Teams Live Event (Attendee role) | Available | Not available | +| | Teams Webinar (Presenter role) | Available | Available | +| | Teams Webinar (Attendee role) | Not available | Not available | | | Overflow Meeting Join (1k+ meeting participants) | Available | Not available | | | Microsoft Whiteboard - Initiate during a Teams Meeting | Available | Available | | | Microsoft Whiteboard - Initiate without a Teams Meeting (from a console) | Not available | Not available | @@ -230,8 +243,10 @@ To help guide you as to what features are available on different platforms, you | | Microsoft Defender for Endpoint | Available | Not available | | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | Available | Not available | +| | Digital signage | Available | Not available | | | Unauthenticated proxy support | Available | Available | -| | Authenticated proxy support | Not available | Not available | +| | Authenticated proxy support | Available | Not available | +| | Tenant restrictions | Available | Not available | | **Teams Admin Center** | Automatic onboarding | Available | Available | | | Device inventory views | Available | Available | | | Overall device health monitoring | Available | Available | @@ -274,8 +289,12 @@ To help guide you as to what features are available on different platforms, you | | Room capacity notifications | Available | | **Customization** | View room equipment| Available | | | Built-in backgrounds | Available | +| | Custom background | Available | | | Line of business apps | Available | | | Change color of LED lights | Available | +| **Device Management** | Unauthenticated proxy support | Available | +| | Authenticated proxy support | Not available | +| | Tenant restrictions | Not available | ## [GCC-High](#tab/GCCHigh) @@ -291,8 +310,9 @@ To help guide you as to what features are available on different platforms, you | | Teams Meeting with ID | Available | Available | | | Direct guest join | BlueJeans: Available
    Webex: Available
    Zoom: Available| BlueJeans: Not available
    Webex: Available
    Zoom: Available | | | Direct guest join with ID | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | BlueJeans: Not available
    Webex: Not available
    Zoom: Available | -| | SIP/H.323 calling | Available | Not available | -| | PSTN calling | Available | Available | +| | Enhanced cross-platform meetings using SIP join | Not available | Not available | +| | SIP/H.323 dialing | Available | Not available | +| | Telephone calling | Available | Available | | | Admins can require meeting ID and passcode on meeting join | Available | Available | | | Cross cloud meeting join (for example, Commercial > GCC or GCC High > GCC) | Available | Not available | | **Meeting engagement and collaboration** | Intuitive, purpose-built app experience| Available | Available | @@ -307,13 +327,15 @@ To help guide you as to what features are available on different platforms, you | | Live reactions | Available | Available | | | PowerPoint Live | Available | Available | | | Live closed captions | Available | Available | -| | Participate in breakout rooms | Not available | Not available | +| | Participate in breakout rooms | Available | Not available | | | Teams Premium meeting protection policies (watermark, E2E encryption for meetings, and sensitivity labels) | Available | Available | | | Start meeting recording and transcription | Not available | Not available | | | Teams Town Hall (Presenter role) | Not available | Not available | | | Teams Town Hall (Attendee role) | Not available | Not available | | | Teams Live Event (Presenter role) | Available | Not available | | | Teams Live Event (Attendee role) | Available | Not available | +| | Teams Webinar (Presenter role) | Available | Available | +| | Teams Webinar (Attendee role) | Not available | Not available | | | Overflow Meeting Join (1k+ meeting participants) | Available | Not available | | | Microsoft Whiteboard - Initiate during a Teams Meeting | Not available | Not available | | | Microsoft Whiteboard - Initiate without a Teams Meeting (from a console) | Not available | Not available | @@ -352,8 +374,10 @@ To help guide you as to what features are available on different platforms, you | | Microsoft Defender for Endpoint | Available | Not available | | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | Available | Not available | +| | Digital signage | Available | Not available | | | Unauthenticated proxy support | Available | Available | -| | Authenticated proxy support | Not available | Not available | +| | Authenticated proxy support | Available | Not available | +| | Tenant restrictions | Available | Not available | | **Teams Admin Center** | Automatic onboarding | Available | Available | | | Device inventory views | Available | Available | | | Overall device health monitoring | Available | Available | @@ -381,5 +405,9 @@ To help guide you as to what features are available on different platforms, you | | Room capacity notifications | Not available | | **Customization** | View room equipment| Not available | | | Built-in backgrounds | Available | +| | Custom background | Not available | | | Line of business apps | Not available | | | Change color of LED lights | Available | +| **Device Management** | Unauthenticated proxy support | Available | +| | Authenticated proxy support | Not available | +| | Tenant restrictions | Not available | diff --git a/Teams/rooms/third-party-join.md b/Teams/rooms/third-party-join.md index ebf4d8d87c..34cf48cb75 100644 --- a/Teams/rooms/third-party-join.md +++ b/Teams/rooms/third-party-join.md @@ -1,5 +1,5 @@ --- -title: Enable Teams Rooms devices to join third-party meetings +title: Third-party meetings on Teams Rooms author: mstonysmith ms.author: tonysmit manager: pamgreen @@ -21,137 +21,153 @@ ms.localizationpriority: medium description: This article discusses how to configure your organization and Teams Rooms devices to support third-party meeting joining to Cisco Webex and Zoom. --- -# Enable Teams Rooms devices to join third-party meetings - -Microsoft Teams Rooms devices support a one-touch experience for joining third-party online meetings, also referred to as Direct Guest Join. When enabled, you can use Teams Rooms to join meetings hosted on Cisco Webex and Zoom just as easily as you can join meetings hosted in Microsoft Teams. Keep in mind that in this case, the experience in Teams Rooms of the third-party online meeting is driven by the third-party online meeting provider. - -Supported devices and services: - -- Teams Rooms on Windows, all certified models – Zoom, Cisco Webex, BlueJeans by Verizon - -- Teams Rooms on Android, all certified models – Zoom, Cisco Webex - - > [!NOTE] - > Microsoft releases new features for Teams Rooms on Android on a regular basis. However, there can be a delay between when features are released and when they become available on a device. If a feature isn't available on your device, check with your device's manufacturer for information on when it might become available. +# Third-party meetings on Teams Rooms + +Microsoft Teams Rooms devices support a one-touch and join by ID experiences for connecting to third-party online meetings. This capability comes in two forms: Direct Guest Join (DGJ) or Cross-Platform meetings via SIP (Session Initiation Protocol) join. When third-party join is enabled, you can use Teams Rooms to join meetings hosted on other meeting platforms as easily as you can join meetings hosted on Microsoft Teams. Third-party meeting providers drive the experience of their platform on the Teams Room device. + +Before you can join third-party meetings from Teams Rooms, you need to do the following steps: +1. Understand which third-party meeting join solution is right for your organization. +2. Configure the Teams Rooms' resource accounts Exchange mailbox to process invites for third-party and externally scheduled meetings. +3. Ensure no tenant policies are blocking devices from connecting to third-party meeting services. +4. Configure Teams Rooms devices to allow third-party meetings. + +## Step 1: Determine which third-party meeting join solution is right for your Teams Rooms + +Teams Rooms offer two ways for connecting to third-party meetings: a SIP video based solution known as cross-platform meeting via SIP join and a WebRTC based solution known as Direct Guest Join. These solutions have different requirements and capabilities which are noted in the table. Review the table and determine which is right for your organization. + +| Supported Functionality | Cross-Platform Meetings via SIP | Direct Guest Join +|--------|----------|---------|---------| +| Join Button           | Amazon Chime
    Cisco Webex
    Google Meet
    GoToMeeting
    RingCentral
    Zoom
    Other SIP services           | Cisco Webex
    Zoom           | +| Join by ID | Amazon Chime
    Cisco Webex
    Google Meet
    GoToMeeting
    RingCentral
    Zoom
    Other SIP services via SIP URI | Zoom | +| Events & Webinars | Cisco Webex*
    Zoom* | Not available | +| Receive video quality | Up to 1080p / 30 fps | Up to 720p / 30 fps | +| Send video quality | Up to 1080p / 30 fps | Up to 720p / 30 fps | +| Receive content | Available | Available | +| Send content with HDMI | Available | Not available | +| Send content with [content camera](content-camera.md) | Available | Not available | +| Maximum front of room displays | Two displays | One display | +| Layout controls | Available* | Available* | +| List participant | Available* | Available* | +| View chat | Available* | Available* | +| Breakout rooms | Available* | Available* | +| View reactions | Available* | Available* | +| Send reactions | Not available | Not available | +| View content annotations | Not available | Not available | +| View transcript | Not available | Not available | +| Recording notification | Available | Available | +| Whiteboard view | Available* | Available* | +| Whiteboard interaction | Not available | Not available | +| Lobby control | Available* | Not available | +| Lobby authentication / bypass | Not available | Not available | +| Microphone mute sync | Not available | Not available | +| Teams Rooms coordinated join | Not available | Not available | +| SIP paid dialing plan required | Yes | No | +| Direct internet access required | No | Yes | +| Teams Rooms license | Teams Rooms Pro | Teams Rooms Basic
    Teams Rooms Pro | +| Teams Rooms platform | Teams Rooms on Windows | Teams Rooms on Windows
    Teams Rooms on Android | > [!NOTE] -> To join a Cisco Webex meeting from a Teams Rooms device, the Cisco meeting needs to be hosted in Webex Meetings Pro using Cisco Webex web application version WBS 40.7 or later. +> *Third party platform features listed were available at the time this article was last updated and may vary from platform to platform. Microsoft periodically reviews these features to keep this document current but other platforms may make changes which can impact these features.
    > [!NOTE] -> Joining a Zoom meeting from a Teams Rooms console is supported. However, you can't join Zoom Webinars and Zoom Events from a Teams Rooms console. Those aren't supported at this time. - -Before you can join third-party meetings from Teams Rooms, you need to do the following: +> To join a Cisco Webex meeting from a Teams Rooms device using Direct Guest Join, the Cisco meeting needs to be hosted in Webex Meetings Pro using Cisco Webex web application version WBS 40.7 or later. -1. Configure the Teams Rooms' Exchange mailbox to process invites for third-party meetings. -2. Make sure your organization doesn't have any policies that would prevent you from connecting to third-party meeting services. -3. Configure Teams Rooms to allow third-party meetings. +## Step 2: Allow Exchange to process third-party meetings and externally created invites -The following sections show you how to complete each of these steps. +When a Teams Room joins a Teams Meeting, it utilizes hidden properties in the Outlook meeting invite to know the meeting link to join. But when joining third-party meetings, Teams Rooms read the calendar invite message body so you need to retain the meeting invite body to ensure a join button can be generated for third-party meeting platforms. Similarly, a typical use case for third-party meeting join is for meetings created outside of your organization, in which case, you want users to be able to forward the externally scheduled meeting invite to their preferred meeting space and have the room accept the invite. -## Step 1: Allow calendar invite processing for third-party meetings - -The first thing you need to do to enable a one-touch join experience from Team Rooms is set the calendar processing rules for the device's Exchange Online room mailbox. The room mailbox needs to allow external meetings and keep the message body and subject so it can see the URL needed to join the third-party meeting. To set these room mailbox options using the [Set-CalendarProcessing](/powershell/module/exchange/set-calendarprocessing) cmdlet, do the following: - -1. Connect to Exchange Online PowerShell. For more information, see [Connect to Exchange Online PowerShell with Basic authentication](/powershell/exchange/connect-to-exchange-online-powershell) or [Connect to Exchange Online PowerShell using multi-factor authentication](/powershell/exchange/mfa-connect-to-exchange-online-powershell), depending on your authentication method. - -2. Get the User Principal Name (UPN) of the room mailbox if you don't know it by running the following command: - - ```powershell - Get-Mailbox | Where {$_.RoomMailboxAccountEnabled -eq $True} | Format-Table Name, UserPrincipalName - ``` +To enable these scenarios, you need to modify the Exchange calendar processing rules on the room resource account. To set these room mailbox options using the [Set-CalendarProcessing](/powershell/module/exchange/set-calendarprocessing) cmdlet, do the following steps: -3. Find the name of the room mailbox associated with your Teams Rooms device and make note of its UPN. +1. Connect to Exchange Online PowerShell. For more information, [Connect to Exchange Online PowerShell](/powershell/exchange/mfa-connect-to-exchange-online-powershell). -4. After you find the room mailbox's UPN, run the following command. Replace `` with the room mailbox's UPN: +2. Using the resource account mailbox's user principal name (UPN), run the following command. Replace `` with the room mailbox's UPN: ```powershell - Set-CalendarProcessing -ProcessExternalMeetingMessages $True -DeleteComments $False -DeleteSubject $False + Set-CalendarProcessing -ProcessExternalMeetingMessages $True -DeleteComments $False ``` -Learn more about [Exchange Online PowerShell](/powershell/exchange/exchange-online-powershell). - -## Step 2: Configure Office 365 Threat Protection and link rewrite - -To enable the one-touch join experience, meeting join link information from the third-party meeting needs to be present and readable in the meeting invite. If your organization uses the [Microsoft Defender for Office 365](/microsoft-365/security/office-365-security/safe-links) safe links feature, or if you use a third-party solution that scans all incoming and outgoing URLs for threats, it may change the meeting join URLs and make the meeting unrecognizable by the Teams Rooms device. To make sure this doesn't happen, you need to add the third-party meeting service's URLs to the Defender for [Office 365 Safe Links **Do not rewrite** list](/microsoft-365/security/office-365-security/safe-links) or the third-party URL rewrite exception list. +## Step 3A: Configure URL rewrite policies to not modify third party meeting links - If you use a third-party solution, refer to the instructions for that solution to add URLs to its URL rewrite exception list. +To enable the one-touch join experience, meeting join link information from the third-party meeting needs to be present and readable in the meeting invite by the Teams Room device. If your organization uses [Microsoft Defender for Office 365](/microsoft-365/security/office-365-security/safe-links) safe links, or if you use a third-party solution that scans all URLs for threats, it may change the meeting join URLs and make the meeting unrecognizable by the Teams Rooms device. To ensure invites work, you need to add the third-party meeting service's URLs to the [Defender for Office 365 Safe Links **Don't rewrite** list](/microsoft-365/security/office-365-security/safe-links), or the third-party URL rewrite exception list. If you use a third-party solution, refer to the instructions for that solution to add URLs to its URL rewrite exception list. -Here are some example entries that you may need to add to your Defender for Office 365 Safe Links *Do not rewrite* list or third-party URL rewrite exception list: +Here are some example entries that you may need to add to a rewrite exception list: - **Cisco Webex** `*.webex.com/*` - **Zoom** `*.zoom.us/*`, `*.zoom.com/*`, `*.zoomgov.com/*` -- **BlueJeans** `*.bluejeans.com/*` - -For a complete list of URLs to add to your Defender for Office 365 Safe Links *Do not rewrite* list or third-party URL rewrite exception list, contact the third-party meeting service provider you want to accept meeting invites from. > [!CAUTION] -> Only add URLs that you trust to your Microsoft Defender for Office 365 Safe Links *Do not rewrite* list or third-party URL rewrite exception list. +> Only add URLs that you trust to your *don't rewrite* exception list. -## Step 3a: Enable third-party meetings on Teams Rooms on Windows +## Step 3B: If you're utilizing Direct Guest Join, ensure your network connections are optimized to connect to your desired platform -The last step you need to do is allow Teams Rooms to join third-party meetings. Third-party meetings require a username and email address to join them. If the username and email address that you need to use is different than the device's room mailbox, you need to add them to your device. You can do this in the Teams Rooms settings or in the XML config file. You can do this in the Teams Rooms settings on any capable Teams Rooms or in the XML config file for Teams Rooms on Windows. +When using Direct Guest Join, Teams Rooms devices connect directly to the website of that third-party platform. Because of this direct connection, your Teams Rooms devices need to be able to connect to that third party website. Ensure your organization’s firewalls or web filters allow the traffic without authentication and that the web traffic is in an appropriate QoS class (if applicable). Refer to the third-party meeting platforms documentation for the correct URLs and IPs to allow. -### Use device settings +## Step 4: Enable third-party meetings on your Teams Rooms devices -To configure Teams Rooms on Windows using the touchscreen console, do the following: +The last step you need to take is to allow Teams Rooms to join third-party meetings with Teams Rooms device settings. If the username and email address that you wish to use to join meetings is different than the device's resource account, you can configure that while enabling third-party meeting join. -1. On the Microsoft Teams Rooms console, select **More**. -2. Select **Settings**, and then enter the device administrator username and password. -3. Go to the **Meetings** tab and select a third-party meeting provider you wish to enable (e.g., **Webex**, **Zoom**, etc.). +## [Teams Rooms on Windows](#tab/MTRW) -:::image type="content" source="../media/use-device-settings.png" alt-text="Turning on and off third party providers."::: +If you wish to utilize the cross-platform SIP join capability, you need to enable SIP video calling on your Teams Rooms following these instructions: [SIP and H.323 Dilaing](meetings-with-sip-h323-devices.md). Once SIP calling is enabled, the Teams Room automatically uses SIP instead of WebRTC to join the enabled third-party meetings. To ensure SIP calling enabled Teams Rooms can always join a meeting, Teams Rooms will automatically use Direct Guest Join over WebRTC if the third party meeting invite doesn't contain a SIP dial string. Lastly, if SIP calling isn't enabled, Teams Rooms on Windows devices will only utilize Direct Guest Join over WebRTC for third-party meetings. -1. If you want to join meetings with the username and email address associated with the room mailbox, select **Join with room info**. -1. If you want to join meetings with an alternate username and email address, select **Join with custom info** and enter username and email address you'd like to use. -1. Select **Save and exit**. Your device will restart. +> [!NOTE] +> Automatic fallback to WebRTC DGJ works for meetings using the calendar join button. If users attempt to use join by ID and the meeting does not have SIP capabilities, the call will fail. Only enable SIP dialing in your organization if third-party meetings you join have SIP capabilities or educate your users on the fall back options with the calendar join buttons. - ![Meetings](https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/assets/63427703/6503b72c-4482-4ec4-9492-610503d02c36) +#### Using the Pro Management Portal -### Use the SkypeSettings.xml configuration file +1. Log in to the [Teams Pro Management Portal](enrolling-mtrp-managed-service.md) +2. Select **Rooms** +3. Select your desired room +4. Select **Settings** +5. Select **Meetings** +6. Toggle your desired meeting platforms +7. Select **Apply** -The following settings can be added to the `SkypeSettings.xml` file located in `C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState`. For more information about the `SkypeSettings.xml` file, see [Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file](xml-config-file.md). +#### Using the local device settings -To enable Zoom meetings, set the `ZoomMeetingsEnabled` XML element to **True**, as follows. +To configure Teams Rooms on Windows using the touchscreen console, do the following steps: -```xml -True -``` +1. On the Microsoft Teams Rooms console, select **More**. +2. Select **Settings**, and then enter the device administrator username and password. +3. Go to the **Meetings** tab and select a third-party meeting provider you wish to enable (for example, **Cisco Webex**, **Zoom**, etc.). -To enable Cisco Webex meetings, set the `WebexMeetingsEnabled` XML element to **True**, as follows. + :::image type="content" source="../media/use-device-settings.png" alt-text="Turning on and off third party providers."::: -```xml -True -``` +4. If you want to join meetings with the username and email address associated with the room mailbox, select **Join with room info**. +5. If you want to join meetings with an alternate username and email address, select **Join with custom info** and enter username and email address you'd like to use. +6. Select **Save and exit**. Your device restarts. -To enable BlueJeans meetings, set the `BlueJeansMeetingsEnabled` XML element to **True**, as follows. + ![Meetings](https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/assets/63427703/6503b72c-4482-4ec4-9492-610503d02c36) -```xml -True -``` +#### Use the SkypeSettings.xml configuration file -You can optionally specify a custom username and email address to join third-party meetings using the following XML elements. If the values you provide aren't valid, the Teams Rooms device will default to use room mailbox username and email address. +For more information about the `SkypeSettings.xml` file, see [Manage Microsoft Teams Rooms settings with an XML configuration file](xml-config-file.md). -```xml -true +To enable the various platforms, set the XML element to **True**, as follows. -guestname + ```xml + True + True + ``` -guest@contoso.com -``` +You can optionally specify a custom username and email address to join third-party meetings using the following XML elements. If the values you provide aren't valid, the Teams Rooms device defaults to use room mailbox username and email address. -## Step 3b: Enable third-party meetings on Teams Rooms on Android + ```xml + true + guestname + guest@contoso.com + ``` -To configure Teams Rooms on Android using the touchscreen console or front-of-room display, do the following: +## [Teams Rooms on Android](#tab/MTRA) -1. On the Microsoft Teams Rooms console or front-of-room display, select **More**. -2. Select **Settings**, and: - - If using a personal account (for example, an account with an E5 license), choose **Meetings** option. - - If using a shared account (for example, a resource account with a Teams Rooms license), choose **Device settings**, locate **Teams Admin settings**, enter an admin password, and choose a **Meetings** option. +To configure Teams Rooms on Android locally on the device, do the following steps: - > [!NOTE] - > Some device manufacturers require an admin password before **Device settings** can be accessed. +1. On the Microsoft Teams Rooms device, select **More**. +2. Select **Settings**. +3. Open **Teams admin settings**. Enter the device administrative credentials +4. Select **Meetings**. ![Meetings settings for MTR on Android](..\media\step-3b-enable-third-party-meetings-on-teams-rooms-on-android.png) -3. Select the third-party meeting provider you want to enable. -4. If you want to join meetings with a custom username and email address, select **Join with custom name and email**. To update custom personal info, press **Edit custom info** and input your preferred name and email address. +5. Select the toggle next to the third-party meeting providers you want to enable. +6. If you want to join meetings with a custom username and email address, select **Join with custom name and email**. To update custom personal info, press **Edit custom info** and input your preferred name and email address. diff --git a/Teams/rooms/voice-and-face-recognition.md b/Teams/rooms/voice-and-face-recognition.md index 2a9d294445..b79450a5ba 100644 --- a/Teams/rooms/voice-and-face-recognition.md +++ b/Teams/rooms/voice-and-face-recognition.md @@ -27,7 +27,7 @@ description: Learn how admins can manage and control voice and face enrollment i Voice and face enrollment is a feature in Microsoft Teams that allows users to create a voice and face profile. Voice and face enrollment is used to improve the audio quality and user experience of Teams meetings and calls. This feature helps to reduce background noise and secondary speakers and provides speaker attribution and Microsoft CoPilot accuracy in meeting rooms equipped with Microsoft Teams Rooms devices. Admins and security teams can manage and control this feature and ensure for which user the enrollment and usage of the profile are turned on. -Users can unenroll their profile, even if the admin disables enrollment for them. Users can save their information by staying enrolled so they are in full control of their voice and face data. See [Create Recognition profiles for Microsoft IntelliFrame](https://support.microsoft.com/office/create-recognition-profiles-for-microsoft-intelliframe-f0084478-52a7-4c52-bcdc-9063ed0e0bc0). +Users have full control over their voice and face data and can choose to stay enrolled or unenroll their profiles at any time through their desktop client, even if admins have disabled enrollment after the user has enrolled. See [Create Recognition profiles for Microsoft IntelliFrame](https://support.microsoft.com/office/create-recognition-profiles-for-microsoft-intelliframe-f0084478-52a7-4c52-bcdc-9063ed0e0bc0). This article covers: @@ -139,6 +139,10 @@ Set-CsTeamsMeetingPolicy -Identity -PolicyName -EnrollUserOverride Disabled +> [!NOTE] +> A new `csTeamsAIPolicy` for Microsoft Teams, now available via Microsoft PowerShell, will take effect in mid-January 2025. This policy will replace the existing enrollment setting in `csTeamsMeetingPolicy` and includes two settings: `EnrollFace` and `EnrollVoice`. +> To help you get started, review: +> - [Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn](/powershell/module/teams/set-csteamsaipolicy) Admins can manage how voice and face profiles are used to turn off Voice Isolation for users to enhance noise and voice background reduction admins can switch off voice isolation with PowerShell in the meeting policy. ```powershell @@ -179,3 +183,17 @@ To export the voice and face profiles of users using the Teams Admin Center, adm **Answer:** We don't support getting data cross-tenant. We only retrieve data for their tenant only. +**Question:** Are voice and face enrollments available in GCCH and DOD? + +**Answer:** No, voice and face enrollments are currently available only up to GCC and are not available in GCCH or DOD environments. + +## Related topics + +- [Manage voice isolation for your users' Microsoft Teams calls and meetings](/microsoftteams/voice-isolation) + +- [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) + +- [Microsoft 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges) + +- [Manage voice recognition technology controls for an Intelligent Speaker](/microsoftteams/rooms/voice-recognition) + diff --git a/Teams/routing-calls-to-unassigned-numbers.md b/Teams/routing-calls-to-unassigned-numbers.md index 83dab55cee..f328985501 100644 --- a/Teams/routing-calls-to-unassigned-numbers.md +++ b/Teams/routing-calls-to-unassigned-numbers.md @@ -1,7 +1,7 @@ --- title: Routing calls to unassigned numbers -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 11/17/2023 diff --git a/Teams/search-for-phone-numbers-for-users.md b/Teams/search-for-phone-numbers-for-users.md index c2e18c62a7..3fe8c41346 100644 --- a/Teams/search-for-phone-numbers-for-users.md +++ b/Teams/search-for-phone-numbers-for-users.md @@ -1,7 +1,7 @@ --- title: "Search for telephone numbers for users" -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: davlick, roykuntz, jastark ms.date: 11/28/2017 diff --git a/Teams/see-a-list-of-audio-conferencing-numbers-in-teams.md b/Teams/see-a-list-of-audio-conferencing-numbers-in-teams.md index 11556738f4..7e76fb14fe 100644 --- a/Teams/see-a-list-of-audio-conferencing-numbers-in-teams.md +++ b/Teams/see-a-list-of-audio-conferencing-numbers-in-teams.md @@ -4,7 +4,7 @@ ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/14/2023 +ms.date: 10/16/2024 ms.topic: article ms.assetid: 2d6b4ed4-e12b-4691-8405-fae720d69425 ms.tgt.pltfrm: cloud @@ -49,6 +49,18 @@ Using the Microsoft Teams admin center: - You can also see the location and primary language that the audio conferencing auto attendant uses. +## See your audio conferencing phone numbers using PowerShell + +To see your audio conferencing phone numbers with PowerShell, use the PowerShell [Get-CsOnlineDialInConferencingServiceNumber](/powershell/module/teams/get-csonlinedialinconferencingservicenumber) cmdlet. + +To see all the audio conferencing phone numbers in your organization, use the following script: + +```powershell +Get-CsOnlineDialInConferencingServiceNumber | fl +``` + +For more examples, see [Get-CsOnlineDialInConferencingServiceNumber](/powershell/module/teams/get-csonlinedialinconferencingservicenumber). + ## Related topics - [Change the settings for an audio conferencing bridge](change-the-settings-for-an-audio-conferencing-bridge.md) diff --git a/Teams/see-a-list-of-phone-numbers-in-your-organization.md b/Teams/see-a-list-of-phone-numbers-in-your-organization.md index ddca4cb1e0..839e1ab420 100644 --- a/Teams/see-a-list-of-phone-numbers-in-your-organization.md +++ b/Teams/see-a-list-of-phone-numbers-in-your-organization.md @@ -1,7 +1,7 @@ --- title: "See a list of telephone numbers in your organization" -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: davlick, roykuntz, jastark ms.date: 10/09/2023 diff --git a/Teams/set-auto-attendant-languages-for-audio-conferencing-in-teams.md b/Teams/set-auto-attendant-languages-for-audio-conferencing-in-teams.md index ca902377b5..28e492a5d6 100644 --- a/Teams/set-auto-attendant-languages-for-audio-conferencing-in-teams.md +++ b/Teams/set-auto-attendant-languages-for-audio-conferencing-in-teams.md @@ -4,7 +4,7 @@ ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/14/2023 +ms.date: 10/16/2024 ms.topic: article ms.assetid: 26d73dda-ab26-4af4-8aec-d17f3479ae50 ms.tgt.pltfrm: cloud @@ -61,6 +61,12 @@ Using the Microsoft Teams admin center: - Languages can be set for dedicated but not for shared phone numbers. - To see a list of countries/regions in which Audio Conferencing in Microsoft 365 or Office 365 using Microsoft as the provider is available, see [Phone numbers for Audio Conferencing](phone-numbers-for-audio-conferencing-in-teams.md). + +## Manage auto attendant languages using PowerShell + +To manage auto attendant languages with PowerShell, use the PowerShell [CsOnlineDialInConferencingServiceNumber](/powershell/module/teams/set-csonlinedialinconferencingtenantsettings) cmdlet. + +For examples, see [CsOnlineDialInConferencingServiceNumber](/powershell/module/teams/set-csonlinedialinconferencingtenantsettings). ## Related topics diff --git a/Teams/set-up-calling-plans.md b/Teams/set-up-calling-plans.md index b8fa6b80a4..112fd18675 100644 --- a/Teams/set-up-calling-plans.md +++ b/Teams/set-up-calling-plans.md @@ -1,7 +1,7 @@ --- title: Set up Microsoft Calling Plans -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz, jastark ms.date: 09/24/2024 diff --git a/Teams/set-up-meeting-dial-out-confirmation.md b/Teams/set-up-meeting-dial-out-confirmation.md index 0bf3111aec..96ea64a5b6 100644 --- a/Teams/set-up-meeting-dial-out-confirmation.md +++ b/Teams/set-up-meeting-dial-out-confirmation.md @@ -4,7 +4,7 @@ ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/14/2023 +ms.date: 10/16/2024 ms.topic: article ms.service: msteams ms.subservice: teams-audio-conferencing @@ -21,11 +21,11 @@ appliesto: # Set up meeting dial-out confirmation for your users in Microsoft Teams -Sending meeting invitations through dial outs and Call me calls are useful ways to invite participants to join a meeting, allowing both new and existing participants to join using either a traditional or a mobile phone. However, when the person who is called doesn't pick up and a voicemail system answers the call instead, the voicemail system joins the meeting. In this scenario, the participants listen to the voicemail until it's removed from the meeting. +Sending meeting invitations through dial outs and Call me calls is an effective way to invite participants to join a meeting, whether they're new or existing participants, using either a traditional or mobile phone. However, if the person being called doesn't pick up and a voicemail system answers instead, the voicemail system joins the meeting. This results in participants having to listen to the voicemail until someone removes it from the meeting. -You can configure Teams to request a confirmation from the called person to join the meeting when a meeting dial out goes to a phone number and the person who is called can't answer the call. This way, you can prevent voicemail systems from connecting to meetings. When the voicemail system answers a call, the voicemail system doesn't connect to the meeting because it can't provide a confirmation to join. +To prevent this, you can configure Teams to request a confirmation from the called person before they join the meeting. When a meeting dial out goes to a phone number and the person can't answer, the voicemail system can't connect because it can't provide the required confirmation. -This policy requires anyone who gets dial outs or Call me calls to accept the meeting invitation by pressing 1 on their phone keypad or saying "Okay." The confirmation prevents the user's voicemail message from joining the meeting. +This policy requires anyone receiving dial outs or Call me calls to accept the meeting invitation by pressing 1 on their phone keypad or saying "Okay." This confirmation step ensures that voicemail systems don't join the meeting. ## Set up meeting dial-out confirmation for your users with PowerShell diff --git a/Teams/set-up-meeting-registration.md b/Teams/set-up-meeting-registration.md index 0c7f3f2a59..c12d58c1d2 100644 --- a/Teams/set-up-meeting-registration.md +++ b/Teams/set-up-meeting-registration.md @@ -26,7 +26,7 @@ description: Learn how to set up and manage meeting registration policies in Tea # Manage registration for Microsoft Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] diff --git a/Teams/set-up-town-halls.md b/Teams/set-up-town-halls.md index 0724c99607..46ee7394fe 100644 --- a/Teams/set-up-town-halls.md +++ b/Teams/set-up-town-halls.md @@ -1,10 +1,10 @@ --- -title: Manage who can schedule town halls in Microsoft Teams +title: Manage who can schedule and attend town halls in Microsoft Teams ms.author: wlibebe author: wlibebe manager: pamgreen -ms.reviewer: sachung -ms.date: 9/18/2024 +ms.reviewer: chbalaki +ms.date: 11/7/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -21,12 +21,12 @@ ms.collection: - m365initiative-meetings - highpri - Tier1 -description: Learn how to set up and manage town hall policies for IT Admins in Microsoft Teams. Learn how to manage who can schedule town halls in your organization. +description: Learn how to set up and manage town hall policies for IT Admins in Microsoft Teams. Learn how to manage who can schedule and attend town halls in your organization. --- -# Manage who can schedule town halls in Microsoft Teams +# Manage who can schedule and attend town halls in Microsoft Teams -**APPLIES TO:** ✖️Meetings ✖️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls ## Overview @@ -34,13 +34,13 @@ Town halls in Microsoft Teams are a one-to-many interactive virtual event. This For details on how your organizers can create town halls, see [Schedule a town hall in Microsoft Teams](https://support.microsoft.com/office/schedule-a-town-hall-in-microsoft-teams-d493b5cc-9f61-4dac-8027-d837dafb7a4c). -### Manage who can schedule town halls +## Manage who can schedule town halls You can use the Teams admin center or PowerShell to manage who can schedule town halls in your organization. |Teams admin center value| PowerShell value|Behavior| |---------|---------------|---------------| -|On|Enabled| **This is the default.** Users with this policy can create town halls. | +|On|Enabled| **This is the default value.** Users with this policy can create town halls. | |Off|Disabled| Users with this policy can't create town halls.| ### Manage who can schedule town halls using the Teams admin center @@ -51,16 +51,16 @@ To manage who can schedule town halls through the Teams admin center, use the fo 2. Expand **Meetings** from the navigation pane. 3. Under **Meetings**, select **Events Policies**. 4. Either select an existing policy or create a new one. -5. Toggle the **Allow town halls** setting **On** or **Off**. -6. Select **Save** +5. Toggle the **Town halls** setting **On** or **Off**. +6. Select **Save**. -## Manage who can schedule town halls through PowerShell +### Manage who can schedule town halls through PowerShell You can use PowerShell to manage who can schedule town halls in your organization. To manage who can schedule town halls, use the **`-AllowTownhalls`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. -### Turn off town halls +#### Turn off town halls To prevent organizers with this policy from creating town halls, use the following script: @@ -68,17 +68,59 @@ To prevent organizers with this policy from creating town halls, use the followi Set-CsTeamsEventsPolicy -Identity -AllowTownhalls Disabled ``` -### Turn off public town halls +#### Turn on town halls + +To allow organizers with this policy to create town halls, use the following script: -To prevent organizers with this policy from scheduling public town halls, use the following script: +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowTownhalls Enabled +``` + +## Manage who can attend town halls > [!NOTE] > The EveryoneInCompanyExcludingGuests value allows only in org attendees to join town halls created by organizers with this policy. For town halls, in org attendees include guests. However, for webinars, guests aren't considered in org. +You can use the Teams admin center or PowerShell to manage who can attend town halls in your organization. + +|Teams admin center value| PowerShell value|Behavior| +|---------|---------------|---------------| +|Everyone|Everyone| **This is the default value.** When organizers with his policy create town halls, any user can attend. | +|Everyone in my organization excluding guests|EveryoneInCompanyExcludingGuests| When organizers with his policy create town halls, only users in your org and guests defined in external access can attend.| + +### Manage who can attend town halls using the Teams admin center + +To manage who can attend town halls through the Teams admin center, use the following steps: + +1. Open the Teams admin center. +2. Expand **Meetings** from the navigation pane. +3. Under **Meetings**, select **Events Policies**. +4. Either select an existing policy or create a new one. +5. From the dropdown for the **Who can attend webinars** setting select either **Everyone** or **EveryoneInCompanyExcludingGuests**. +6. Select **Save** + +### Manage who can attend town halls through PowerShell + +You can use PowerShell to manage who can attend town halls in your organization. + +To manage who can attend town halls, use the **`-EventAccessType`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. + +#### Turn off public town halls + +To only allow users in your organization and guests to attend town halls created by users with this policy, use this script: + ```powershell Set-CsTeamsEventsPolicy -Identity -EventAccessType EveryoneInCompanyExcludingGuests ``` +#### Turn on public town halls + +To allow any user to attend town halls created by users with this policy, use this script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -EventAccessType Everyone +``` + ## Related topics - [Plan for town halls](plan-town-halls.md) diff --git a/Teams/set-up-webinars.md b/Teams/set-up-webinars.md index c368de4381..e434d7881b 100644 --- a/Teams/set-up-webinars.md +++ b/Teams/set-up-webinars.md @@ -1,11 +1,10 @@ --- -title: Manage who can schedule webinars in Microsoft Teams - +title: Manage who can schedule and attend webinars in Microsoft Teams ms.author: wlibebe author: wlibebe manager: pamgreen -ms.reviewer: justle -ms.date: 12/6/2023 +ms.reviewer: sherimehmood +ms.date: 11/7/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -22,15 +21,17 @@ ms.collection: - m365initiative-meetings - highpri - Tier1 -description: Learn how to set up webinars and manage who can schedule webinars for IT Admins in Teams. +description: Learn how to set up webinars and manage who can schedule and attend webinars for IT Admins in Teams. --- -# Manage who can schedule webinars in Microsoft Teams +# Manage who can schedule and attend webinars in Microsoft Teams -**APPLIES TO:** ✖️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] +## Overview + Microsoft Teams offers webinars, a two-way interactive virtual event. As an admin, you can set up and manage who can schedule webinars in your organization. For more information on how to plan for webinars in your org, see [Plan for Teams webinars](plan-webinars.md). @@ -40,65 +41,85 @@ To learn more about the webinar experience for your users, see [Get Started with > [!NOTE] > The webinar experience isn't available for Microsoft 365 GCC High or Microsoft 365 DoD. -## Manage webinars using the Teams admin center +## Manage who can schedule webinars + +You can use the Teams admin center or PowerShell to manage who can schedule webinars in your organization. -You can use the Teams admin center to set up and manage the webinar experience for your organization. +|Teams admin center value| PowerShell value|Behavior| +|---------|---------------|---------------| +|On|Enabled| **This is the default value.** Users with this policy can create webinars. | +|Off|Disabled| Users with this policy can't create webinars.| -### Turn webinars on or off +### Manage who can schedule webinars using the Teams admin center -Follow these steps in the Teams admin center to turn webinars on or off: +To manage who can schedule webinars through the Teams admin center, use the following steps: 1. Open the Teams admin center. -2. Select **Meetings** from the navigation pane. +2. Expand **Meetings** from the navigation pane. 3. Under **Meetings**, select **Events Policies**. 4. Either select an existing policy or create a new one. -5. Toggle the **Allow webinars** setting **On** or **Off**. -6. Select **Save**. +5. Toggle the **Webinars** setting **On** or **Off**. +6. Select **Save** -## Manage webinars using PowerShell +### Manage who can schedule webinars using PowerShell -You can use PowerShell to set up and manage the webinar experience for your organization. +You can use PowerShell to manage who can schedule webinars in your organization. -To set up webinars, use the **`-AllowWebinars`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. +To manage who can schedule webinars, use the **`-AllowWebinars`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. -The following table shows the behaviors of the settings for the **`-AllowWebinars`** parameter: +#### Turn off webinars -|Setting value| Behavior| -|---------|---------------| -|Enabled| Users with this policy can create webinars. | -|Disabled| Users with this policy can't create webinars.| +To prevent organizers with this policy from creating webinars, use the following script: -Before you can run these cmdlets, you must be connected to Microsoft Teams PowerShell. For more information, see [Manage Teams with Microsoft Teams PowerShell](/microsoftteams/teams-powershell-managing-teams). - -For more information on PowerShell cmdlets for Teams webinars, see [Related articles](#related-articles). +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowWebinars Disabled +``` -### Turn on webinars +#### Turn on webinars -To turn on webinars, use the following script: +To allow organizers with this policy to create webinars, use the following script: ```powershell Set-CsTeamsEventsPolicy -Identity -AllowWebinars Enabled ``` -### Turn off webinars +## Manage who can attend webinars -To turn off webinars, use the following script: +You can use the Teams admin center or PowerShell to manage who can attend webinars in your organization. -```powershell -Set-CsTeamsEventsPolicy -Identity -AllowWebinars Disabled -``` +|Teams admin center value| PowerShell value|Behavior| +|---------|---------------|---------------| +|Everyone|Everyone| **This is the default value.** When organizers with his policy create webinars, any user can attend. | +|Everyone in my organization excluding guests|EveryoneInCompanyExcludingGuests| When organizers with his policy create webinars, only users in your org can attend.| -## Manage whether organizers can schedule public or private webinars +### Manage who can attend webinars using the Teams admin center -You can use PowerShell to manage whether organizers can [create public or private webinars](https://support.microsoft.com/office/0719a9bd-07a0-47fd-8415-6c576860f36a): +To manage who can attend webinars through the Teams admin center, use the following steps: -To allow organizers to only create private webinars, use the following script: +1. Open the Teams admin center. +2. Expand **Meetings** from the navigation pane. +3. Under **Meetings**, select **Events Policies**. +4. Either select an existing policy or create a new one. +5. From the dropdown for the **Who can attend webinars** setting select either **Everyone** or **EveryoneInCompanyExcludingGuests**. +6. Select **Save** + +### Manage who can attend webinars using PowerShell + +You can use PowerShell to manage who can attend webinars in your organization. + +To manage who can attend webinars, use the **`-EventAccessType`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. + +#### Turn off public webinars + +To only allow users in your organization to attend webinars created by users with this policy, use this script: ```powershell Set-CsTeamsEventsPolicy -Identity -EventAccessType EveryoneInCompanyExcludingGuests ``` -To allow organizers to create public or private webinars, use the following script. Public webinars may include anonymous users: +#### Turn on public webinars + +To allow any user to attend webinars created by users with this policy, use this script: ```powershell Set-CsTeamsEventsPolicy -Identity -EventAccessType Everyone @@ -112,8 +133,4 @@ Set-CsTeamsEventsPolicy -Identity -EventAccessType Everyone - [Manage email communications for webinars](manage-email-communications.md) - [Meetings, webinars, and live events](quick-start-meetings-live-events.md) - [Attendance report for meetings and webinars in Microsoft Teams](teams-analytics-and-reports/meeting-attendance-report.md) -- [New-CsTeamsEventsPolicy](/powershell/module/teams/new-csteamseventspolicy) -- [Set-CsTeamsEventsPolicy](/powershell/module/teams/set-csteamseventspolicy) -- [Grant-CsTeamsEventsPolicy](/powershell/module/teams/grant-csteamseventspolicy) -- [Get-CsTeamsEventsPolicy](/powershell/module/teams/get-csteamseventspolicy) -- [Remove-CsTeamsEventsPolicy](/powershell/module/teams/remove-csteamseventspolicy) +- [Set-CsTeamsEventsPolicy](/powershell/module/teams/set-csteamseventspolicy) \ No newline at end of file diff --git a/Teams/setting-up-your-phone-system.md b/Teams/setting-up-your-phone-system.md index d902df6049..233fa14cad 100644 --- a/Teams/setting-up-your-phone-system.md +++ b/Teams/setting-up-your-phone-system.md @@ -1,7 +1,7 @@ --- title: "Set up Teams Phone in your organization" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 03/07/2024 diff --git a/Teams/shared-calling-scenario.md b/Teams/shared-calling-scenario.md index 583db8d585..3888f685b3 100644 --- a/Teams/shared-calling-scenario.md +++ b/Teams/shared-calling-scenario.md @@ -1,7 +1,7 @@ --- title: "Shared Calling scenario" ms.reviewer: roykuntz -ms.date: 09/20/2023 +ms.date: 10/31/2024 author: mkbond007 ms.author: mabond manager: pamgreen diff --git a/Teams/shared-channels-errors.md b/Teams/shared-channels-errors.md index ff465bb29b..1f69f4ecc1 100644 --- a/Teams/shared-channels-errors.md +++ b/Teams/shared-channels-errors.md @@ -1,7 +1,7 @@ --- title: Shared channels errors in Microsoft Teams -author: jacktremper -ms.author: jtremper +author: DaniESmith +ms.author: danismith manager: pamgreen ms.reviewer: jasonlewis ms.date: 06/28/2024 @@ -23,13 +23,14 @@ description: Learn how to use fix errors in shared channels in Microsoft Teams. # Shared channels errors in Microsoft Teams -If your users see error messages when trying to add people from outside your organization to shared channels, check the settings in this article. +If your users see error messages when trying to add people from outside your organization to shared channels, check the settings in this article. ## Due to admin policy, you can't add external people to the channel. For more info, talk to your admin. Teams uses Microsoft 365 Groups for team membership. The Microsoft 365 Groups guest settings must be turned on in order for people outside the organization to be added to a shared channel. If your users see this error, check the Microsoft 365 Groups settings for people outside the organization. -To set Microsoft 365 Groups settings for people outside the organization +To set Microsoft 365 Groups settings for people outside the organization: + 1. In the Microsoft 365 admin center, in the left navigation pane, expand **Settings**. 1. Click **Org settings**. 1. In the list, click **Microsoft 365 Groups**. @@ -40,8 +41,9 @@ To set Microsoft 365 Groups settings for people outside the organization Teams channel policies determine how users can interact with shared channels. If users see this error message, check the channel policy for that user. -To set the policy for inviting people outside the organization to shared channels -1. In the left navigation of the Microsoft Teams admin center, go to Teams > Teams policies. +To set the policy for inviting people outside the organization to shared channels: + +1. In the left navigation of the Microsoft Teams admin center, go to **Teams** > **Teams policies**. 1. Select the policy that your user is assigned to. 1. Ensure that **Invite external users to shared channels** is **On**. 1. If you made changes, select **Apply**. @@ -52,7 +54,8 @@ For more information about Teams channel policies, see [Manage channel policies If your users see this error, then they're prevented from sharing the channel with people in the other organization by the Microsoft Entra cross-tenant access settings. This may be due to the inbound settings in your organization or the outbound settings in the other organization. -To check the inbound settings for your organization +To check the inbound settings for your organization: + 1. In [Microsoft Entra ID](https://aad.portal.azure.com), select **External Identities**, and then select **Cross-tenant access settings**. 1. Select the inbound access link for the organization that you want to check. 1. On the **B2B direct connect** tab, choose **Customize settings**. diff --git a/Teams/shared-device-security-for-microsoft-teams.md b/Teams/shared-device-security-for-microsoft-teams.md index a7e30b65b3..acf89e4c57 100644 --- a/Teams/shared-device-security-for-microsoft-teams.md +++ b/Teams/shared-device-security-for-microsoft-teams.md @@ -7,7 +7,7 @@ ms.topic: reference ms.service: msteams audience: admin ms.reviewer: pawa -ms.date: 08/21/2020 +ms.date: 10/30/2024 description: Zero Trust guidance for using Microsoft Teams securely from a shared computer in the workplace. ms.localizationpriority: high search.appverid: MET150 @@ -39,18 +39,18 @@ Recognizing that this might not be possible or practical in all scenarios, it's Plans should be developed to adhere to guidelines as promptly as is possible. -1. Make use of Operating System platform security capabilities. +1. Use Operating System platform security capabilities. 1. Ensure that the operating system is configured to install automatic updates from the Operating System provider (for Microsoft systems, this can be accomplished via [**Windows Update**](https://support.microsoft.com/help/12373/windows-update-faq)). 1. Ensure that any device encryption capabilities such as [**bitlocker**](/windows/security/information-protection/bitlocker/bitlocker-overview) are enabled, and the key used to access the device is secured. Note that most modern [**Windows 10 devices support bitlocker**](/windows/security/information-protection/bitlocker/bitlocker-device-encryption-overview-windows-10). 1. Use anti-virus capabilities such as those offered by [**Windows Defender**](/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-in-windows-10) on your devices. 1. Use of [separate user accounts](https://support.microsoft.com/help/4026923/windows-10-create-a-local-user-or-administrator-account) for each user of the system is highly recommended. 1. *Don't* grant, or use, administrator privileges for nonadministrative functions (such as browsing the web, running Teams, et cetera). -If the above guidance can't be met, we recommend making use of other browser security best practices: +If the guidance above can't be met, we recommend using other browser security best practices: -1. Apply browser security capabilities. - 1. Use private browsing sessions to minimize data and history that persists to disk. For example, use [inPrivate browsing in Microsoft Edge](https://support.microsoft.com/help/4533513/microsoft-edge-browse-inprivate), [Incognito browsing in Google Chrome](https://support.google.com/chrome/answer/95464?co=GENIE.Platform%3DDesktop&hl=en), or the capabilities your specific browser for browsing privately. - 1. Changing the system behavior to engage private browsing *by default* is recommended. +1. Automatically delete browser data. + 1. Configure your browser to automatically delete the browser history and data regularly, or whenever the browser is closed. This protects privacy without affecting how Microsoft Teams works. You can find instructions on how to set this up in the documentation for [Google Chrome](https://support.google.com/chrome/community-guide/245444314/how-to-automatically-clear-browsing-data-when-closing-google-chrome-window-a-step-by-step-guide), [Microsoft Edge](https://support.microsoft.com/windows/microsoft-edge-browsing-data-and-privacy-bb8174ba-9d73-dcf2-9b4a-c582b4e640dd), [Mozilla Firefox](https://support.mozilla.org/en-US/kb/delete-browsing-search-download-history-firefox), and [Apple Safari](https://support.apple.com/guide/safari/clear-your-browsing-history-sfri47acf5d6/mac). + 1. Private browsing sessions, such as inPrivate browsing in Microsoft Edge or Incognito Mode in Google Chrome, can help minimize the data and history that's saved to your device. However, using Microsoft Teams on the web in private browsing sessions may lead to performance issues if cookies or services used by Microsoft or third-party apps in Teams are blocked. 2. Browse to and use the [Teams web app](https://teams.microsoft.com) (sometimes called the *web* client) not the downloadable Teams client. diff --git a/Teams/shared-line-appearance.md b/Teams/shared-line-appearance.md index 3880241aa8..c6c90de138 100644 --- a/Teams/shared-line-appearance.md +++ b/Teams/shared-line-appearance.md @@ -3,8 +3,8 @@ title: "Shared line appearance in Microsoft Teams" author: mkbond007 ms.author: mabond manager: pamgreen -ms.date: 02/19/2019 -ms.reviewer: roykuntz +ms.date: 10/15/2024 +ms.reviewer: ashgupt ms.topic: conceptual ms.tgt.pltfrm: cloud ms.service: msteams diff --git a/Teams/sign-in-teams.md b/Teams/sign-in-teams.md index bced751720..3ededdcc2f 100644 --- a/Teams/sign-in-teams.md +++ b/Teams/sign-in-teams.md @@ -9,7 +9,7 @@ ms.service: msteams search.appverid: MET150 ms.reviewer: ms.date: 03/26/2018 -description: Learn how technologies like single sign-on, and Modern Authentication affects your sign-in behavior on iOS, Android, macOS, and PC. How to use Teams with many accounts, and restrict sign in. Includes how to tell Teams to ignore the pre-fill of the user's name (UPN) at sign-in. +description: Learn how technologies like single sign-on, and Modern Authentication affects your sign-in behavior on iOS, Android, macOS, and PC, how to use Teams with many accounts, and restrict sign in. Includes how to tell Teams to ignore the prefill of the user's name (UPN) at sign-in. ms.custom: seo-marvel-apr2020 ms.localizationpriority: high ms.collection: @@ -22,7 +22,7 @@ appliesto: # How different technologies affect Microsoft Teams sign-in -If you need to understand how technologies like single sign-on (SSO), modern authentication (MS), and multifactor authentication (MA) affect users' experience of sign-in, this article helps clarify what users and admins can expect to see. It also outlines the sign-in behavior for macOS, Android, and iOS devices, how sign-in works using multiple accounts, how to remove automatically filled credentials or "pre-fill" at the sign-in screen, how to restrict sign-in, and how to simplify the sign-in experience with domain-less sign-in on shared and managed mobile devices. +If you need to understand how technologies like single sign-on (SSO), modern authentication (MS), and multifactor authentication (MA) affect users' experience of sign-in, this article helps clarify what users and admins can expect to see. It also outlines the sign-in behavior for macOS, Android, and iOS devices, how sign-in works using multiple accounts, how to remove automatically filled credentials or "prefill" at the sign-in screen, how to restrict sign-in, and how to simplify the sign-in experience with domain-less sign-in on shared and managed mobile devices. Bookmark this article if your role involves knowing Microsoft Team's expected behaviors during sign-in. @@ -50,14 +50,14 @@ Here's a rundown of the behavior users can expect with each modern authenticatio - If users are signed in to a domain-joined computer, when they start Teams, they might be asked to go through one more authentication step, depending on whether your organization opted to require MFA or if their computer already requires MFA to sign in. If their computer already requires MFA to sign in, when they open up Teams, the app automatically starts. -- On domain-joined PCs, when SSO isn't possible, Teams may pre-fill its sign-in screen with the user principal name (UPN). There are cases where you may not want this, especially if your organization uses different UPNs on-premises and in Microsoft Entra ID. If that's the case, **you can use the following Windows registry key to turn off pre-population of the UPN**: +- On domain-joined PCs, when SSO isn't possible, Teams may prefill its sign-in screen with the user principal name (UPN). There are cases where you might not want this, especially if your organization uses different UPNs on-premises and in Microsoft Entra ID. If that's the case, **you can use the following Windows registry key to turn off pre-population of the UPN**: Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\Teams
    SkipUpnPrefill(REG_DWORD)
    0x00000001 (1) > [!NOTE] - > Skipping or ignoring user name pre-fill for user names that end in ".local" or ".corp" is on by default, so you don't need to set a registry key to turn these off. + > Skipping or ignoring user name prefill for user names that end in ".local" or ".corp" is on by default, so you don't need to set a registry key to turn these off. ### Microsoft Teams sign-in to another account on a domain-joined computer @@ -65,7 +65,7 @@ Users on domain-joined computer may not be able to sign in to Teams with another ## macOS users and Microsoft Teams sign-in prompts -On macOS, Teams will prompt users to enter their username and credentials and may prompt for multifactor authentication depending on your organization's settings. Once users enter their credentials, they won't be required to provide them again. From that point on, Teams automatically starts whenever they're working on the same computer. +On macOS, Teams will prompt users to enter their username and credentials and might prompt for multifactor authentication depending on your organization's settings. Once users enter their credentials, they won't be required to provide them again. From that point on, Teams automatically starts whenever they're working on the same computer. ## Microsoft Teams sign-in for iOS and Android users @@ -88,7 +88,7 @@ The following images show how users can add multiple accounts in Teams mobile ap ## Restrict sign-in to Microsoft Teams -Organization may want to restrict how corporate-approved apps are used on managed devices, for example to restrict students' or employees' ability to access data from other organizations or use corporate-approved apps for personal scenarios. These restrictions can be enforced by setting Devices Policies that Teams applications recognize. +Organization might want to restrict how corporate-approved apps are used on managed devices, for example to restrict students' or employees' ability to access data from other organizations or use corporate-approved apps for personal scenarios. These restrictions can be enforced by setting Devices Policies that Teams applications recognize. ### How to restrict Microsoft Teams sign-in on mobile devices @@ -116,12 +116,12 @@ To create an app configuration policy for managed Android devices, see [Add app Microsoft Teams apps on Windows and macOS are gaining support for device policies that restrict sign in to your organization. The policies can be set via usual Device Management solutions such as MDM (Mobile Device Management) or GPO (Group Policy Object). -When this policy is configured on a device, users can only sign in with accounts homed in a Microsoft Entra tenant that is included in the "Tenant Allow List" defined in the policy. The policy applies to all sign-ins, including first and additional accounts. If your organization spans multiple Microsoft Entra tenants, you can include multiple Tenant IDs in the Allow List. Links to add another account may continue to be visible in the Teams app, but they won't be operable. +When this policy is configured on a device, users can only sign in with accounts homed in a Microsoft Entra tenant that's included in the "Tenant Allow List" defined in the policy. The policy applies to all sign-ins, including first and additional accounts. If your organization spans multiple Microsoft Entra tenants, you can include multiple Tenant IDs in the Allow List. Links to add another account might continue to be visible in the Teams app, but they won't be operable. > [!NOTE] > ->1. The policy only restricts sign-ins. It does not restrict the ability for users to be invited as a guest in other Microsoft Entra tenants, or switch to those other tenants (where users have been invited as a guest). ->2. The policy requires Teams for Windows version 1.3.00.30866 or higher, and Teams for macOS version 1.3.00.30882 (released mid-November 2020). +>- The policy only restricts sign-ins. It does not restrict the ability for users to be invited as a guest in other Microsoft Entra tenants, or switch to those other tenants (where users have been invited as a guest). +>- The policy requires Teams for Windows version 1.3.00.30866 or higher, and Teams for macOS version 1.3.00.30882 (released mid-November 2020). **Policies for Windows** Administrative Template files (ADMX/ADML) are available from the [Download center](https://www.microsoft.com/download/details.aspx?id=49030) (the policy setting descriptive name in the administrative template file is "Restrict sign in to Teams to accounts in specific tenants"). Additionally, you can manually set keys in Windows Registry: @@ -162,14 +162,14 @@ The sign-in experience looks similar to our standard Teams sign-in experience. ## Simplify the sign-in experience with domain-less sign-in -You can simplify the sign-in experience on Teams for iOS and Android by pre-filling the domain name on the sign-in screen for users on shared and managed devices. Users sign in by entering the first part of their UPN (without the domain name). For example, if the username is 123456@contoso.com or adelev@contoso.com, users can sign in by using only "123456" or "adelev", respectively, and their password. +You can simplify the sign-in experience on Teams for iOS and Android by prefilling the domain name on the sign-in screen for users on shared and managed devices. Users sign in by entering the first part of their UPN (without the domain name). For example, if the username is 123456@contoso.com or adelev@contoso.com, users can sign in by using only "123456" or "adelev", respectively, and their password. Signing in to Teams is faster and easier, especially for employees such as frontline workers on shared devices, who sign in and out regularly. > [!NOTE] > For users to experience the sign-in experience described in this section, their devices must be running Teams for iOS version 6.6.0 or later, or Teams for Android version 1416/1.0.0.2024053003 or later. -:::image type="content" source="media/teams-mobile-domainless-sign-in.png" alt-text="Screenshot of the sign-in screen showing the pre-filled domain name on Teams for iOS and Android." lightbox="media/teams-mobile-domainless-sign-in.png"::: +:::image type="content" source="media/teams-mobile-domainless-sign-in.png" alt-text="Screenshot of the sign-in screen showing the prefilled domain name on Teams for iOS and Android." lightbox="media/teams-mobile-domainless-sign-in.png"::: | Name | Value | |---|---| @@ -196,15 +196,21 @@ Follow these steps to implement domain-less sign-in in your app: Learn more about how to [read and apply managed configurations](https://developer.android.com/work/managed-configurations#read-configurations) and [configure and test setup using TestDPC](https://github.com/android/enterprise-samples/tree/main/ManagedConfigurations#testing). -1. Customize your sign-in experience to collect the username and pre-fill the acquired domain_name on the screen. If you're using the Microsoft Authentication Library (MSAL), you can make the following call to acquire a token post collecting the username on your screen. +1. Customize your sign-in experience to collect the username and prefill the acquired domain_name on the screen. If you're using the Microsoft Authentication Library (MSAL), you can make the following call to acquire a token post collecting the username on your screen. - iOS: [Microsoft Authentication Library for iOS and macOS](https://github.com/AzureAD/microsoft-authentication-library-for-objc?tab=readme-ov-file#quick-sample) - Android: [Microsoft Authentication Library (MSAL) for Android](https://github.com/AzureAD/microsoft-authentication-library-for-android/?tab=readme-ov-file#step-4-create-an-msal-publicclientapplication) +## SMS sign in + +SMS-based authentication lets users sign in without providing, or even knowing, their user name and password. Users enter their phone number at the sign-in prompt and receive an SMS authentication code that they use to complete sign in. This authentication method simplifies access to apps and services, especially for frontline workers. + +To learn more, see [Configure and enable users for SMS-based authentication using Microsoft Entra ID](/entra/identity/authentication/howto-authentication-sms-signin#enable-the-sms-based-authentication-method). + ## URLs and IP address ranges for Microsoft Teams Teams requires connectivity to the Internet. To understand endpoints that should be reachable for customers using Teams in Office 365 plans, Government, and other clouds, read [Office 365 URLs and IP address ranges](/office365/enterprise/urls-and-ip-address-ranges). ## Related articles -[Teams Troubleshooting](/MicrosoftTeams/troubleshoot/teams) +[Teams troubleshooting](/MicrosoftTeams/troubleshoot/teams) diff --git a/Teams/sip-tester-powershell-script.md b/Teams/sip-tester-powershell-script.md index fa720cc06e..481e1f635b 100644 --- a/Teams/sip-tester-powershell-script.md +++ b/Teams/sip-tester-powershell-script.md @@ -1,7 +1,7 @@ --- title: PowerShell script to test Direct Routing Session Border Controller connections -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: article ms.reviewer: filippse diff --git a/Teams/special-character-restrictions-in-policy-names.md b/Teams/special-character-restrictions-in-policy-names.md index d50f82fde5..99d63d7327 100644 --- a/Teams/special-character-restrictions-in-policy-names.md +++ b/Teams/special-character-restrictions-in-policy-names.md @@ -1,7 +1,7 @@ --- title: Special character restrictions in Teams policies -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: serdars ms.reviewer: jastark ms.date: 07/03/2018 diff --git a/Teams/stream-classification-in-call-quality-dashboard.md b/Teams/stream-classification-in-call-quality-dashboard.md index 6dda03a42d..ab8798c960 100644 --- a/Teams/stream-classification-in-call-quality-dashboard.md +++ b/Teams/stream-classification-in-call-quality-dashboard.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: jamp -ms.date: 05/22/2018 +ms.date: 10/22/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -15,8 +15,8 @@ ms.collection: search.appverid: MET150 audience: Admin appliesto: - - Skype for Business - Microsoft Teams + - Skype for Business ms.localizationpriority: medium f1.keywords: - CSH @@ -47,7 +47,7 @@ If one or more of the following conditions are met and Packet Utilization is > 5 |||| > [!NOTE] -> The Audio Classifier uses basic network performance telemetry to assess if the optimal conditions for good quality audio were present. If any one of the thresholds are broken then the audio will be marked _Poor_, but this does not mean the audio stream was actually of poor quality, nor does it mean the user perceived a quality issue. The Teams media stack is built to withstand and correct for poor network conditions, and can mitigate considerable network performance degradation in excess of the thresholds above before a drop in quality is perceived by users. We recommend admins make every effort to build and configure their networks and Teams deployments for the best possible quality, and the above metrics are a useful guideline to assess performance of those networks. +> The Audio Classifier uses basic network performance telemetry to assess if the optimal conditions for good quality audio were present. If any one of the thresholds are broken then the audio will be marked _Poor_, but this doesn't mean the audio stream was actually of poor quality, nor does it mean the user perceived a quality issue. The Teams media stack is built to withstand and correct for poor network conditions, and can mitigate considerable network performance degradation in excess of the thresholds above before a drop in quality is perceived by users. We recommend admins make every effort to build and configure their networks and Teams deployments for the best possible quality, and the above metrics are a useful guideline to assess performance of those networks. ### Video Classifier due to Freeze @@ -98,20 +98,20 @@ In CQD, a stream is marked _Unclassified_ when Interactive Connectivity Establis To check for ICE connectivity failures, examine the dimensions "First Connectivity Ice" and "Second Connectivity Ice" for a "FAILED" value. If either value indicates a failure, the stream is marked as _Unclassified_. -If ICE connectivity succeeded for an _Unclassified_ stream, the stream is likely considered _Unclassified_ because key stream metrics weren't reported. There are a few reasons these metrics may not be reported: +If ICE connectivity succeeded for an _Unclassified_ stream, the stream is likely considered _Unclassified_ because key stream metrics weren't reported. There are a few reasons these metrics might not be reported: -- **QoE reports weren't received** — The metrics used for classification are reported in a QoE report sent at the end of a call. If this report isn't produced (for example, because some third-party endpoints may not send QoE) or could not be sent (for example, because of a network outage), CQD is unable to classify the stream. +- **QoE reports weren't received** — The metrics used for classification are reported in a QoE report sent at the end of a call. If this report isn't produced (for example, because some third-party endpoints might not send QoE) or couldn't be sent (for example, because of a network outage), CQD is unable to classify the stream. > [!TIP] > The "QoE Record Available" dimension can be used to determine whether a QoE report was received for a stream. Note that this dimension will have a value of "True" if a QoE report was received from either endpoint. A QoE report from both endpoints is required for the most accurate reporting of metrics. -- **Short calls** — Short calls may not have enough media activity to compute key stream metrics. Without these metrics, CQD is unable to classify the stream. +- **Short calls** — Short calls might not have enough media activity to compute key stream metrics. Without these metrics, CQD is unable to classify the stream. > [!TIP] > The dimensions "Duration (Seconds)", "Duration (Minutes)", "Duration 5 seconds or less", and "Duration 60 seconds or more" can be used to determine the duration of a stream. The measurement "Avg Call Duration" can also be used to compute the average duration for a set of streams. - **Low packet utilization** — Like the "short call" scenario, sufficient packet utilization is required for computation of key stream metrics. Without these metrics, CQD is unable to classify the stream. - - A common low packet utilization scenario occurs when an attendee joins a meeting to listen to the presenter, but never speaks (the microphone is muted for most of the call). Here, the audio stream inbound to the client has high packet utilization while the audio stream outbound from the client has little to no packet utilization. The duration of the stream may be an hour or longer but the packet utilization on the stream from the client to the server is low since the microphone was muted, and an _Unclassified_ stream results. + - A common low packet utilization scenario occurs when an attendee joins a meeting to listen to the presenter, but never speaks (the microphone is muted for most of the call). Here, the audio stream inbound to the client has high packet utilization while the audio stream outbound from the client has little to no packet utilization. The duration of the stream might be an hour or longer but the packet utilization on the stream from the client to the server is low since the microphone was muted, and an _Unclassified_ stream results. > [!TIP] > The "Packet Utilization" dimension and "Avg Packet Utilization" measurement can be used to determine the packet activity of a stream. diff --git a/Teams/stream-teams-meetings.md b/Teams/stream-teams-meetings.md index 83da2a2ee5..c09cf02ae1 100644 --- a/Teams/stream-teams-meetings.md +++ b/Teams/stream-teams-meetings.md @@ -25,7 +25,7 @@ description: Learn how to set up and manage streaming for your Teams meetings. # Manage live streaming for Teams meetings and webinars -**APPLIES TO:** ✔️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls Live streaming allows organizers in your org to expand their reach and provide a unique experience for meeting and webinar attendees. As an admin, when you enable live streaming, your organizers can stream meetings and webinars to external endpoints by providing a Real-Time Messaging Protocol (RTMP) URL and key to the built-in Custom Streaming app in Teams. diff --git a/Teams/streaming-ecdn-enterprise-content-delivery-network.md b/Teams/streaming-ecdn-enterprise-content-delivery-network.md index 9e95791e38..02db2195b5 100644 --- a/Teams/streaming-ecdn-enterprise-content-delivery-network.md +++ b/Teams/streaming-ecdn-enterprise-content-delivery-network.md @@ -22,27 +22,39 @@ description: Learn about scale video delivery and enterprise content delivery ne --- # Enterprise content delivery networks for streaming Microsoft Teams events -**APPLIES TO:** ✔️Meetings ✖️Webinars ✔️Town halls ✔️Live events +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)View only-meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Live events Teams streaming events can use enterprise content delivery networks (eCDNs), including the Microsoft eCDN and eCDNs from Microsoft partners. Teams streaming events include: - Town halls - Live events -- Meetings with more than 1,000 participants +- [View-only](view-only-meeting-experience.md) meetings -Playback of videos from Microsoft Teams events uses adaptive bitrate streaming (ABR) delivered as a unicast stream. Every viewer gets their own video stream from the internet. For events or videos sent out to large portions of your organization, there could be a significant amount of network and internet bandwidth consumed by viewers. +Video playback from Microsoft Teams events utilizes adaptive bitrate streaming (ABR), which is delivered as a unicast stream. Every viewer gets their own video stream from the internet. For events or videos sent out to large portions of your organization, there could be a significant amount of network and internet bandwidth consumed by viewers. -Organizations might want to understand and reduce the network traffic for events and popular videos. If so, you can enable Teams to integrate with Microsoft’s enterprise content delivery network (eCDN) or trusted Microsoft partners that offer eCDN solutions. The eCDN solutions from our trusted partners include capabilities like real-time monitoring, and in-depth network analytics. These eCDN platforms let organizations monitor, scale, and optimize the distribution of video streams (and sometimes other content types) across your enterprise network. +Video playback from Microsoft Teams events uses adaptive bitrate streaming (ABR) delivered as a unicast stream. This means that each viewer gets their own video stream from the internet. For events or videos sent out to a large portion of your organization, this can result in viewers consuming significant network and internet bandwidth. + +As an admin, you might want to understand and reduce the network traffic for events and popular videos. If so, you can enable Teams to integrate with Microsoft’s enterprise content delivery network (eCDN) or trusted Microsoft partners that offer eCDN solutions. The eCDN solutions from our trusted partners include capabilities like real-time monitoring, and in-depth network analytics. These eCDN platforms let you monitor, scale, and optimize the distribution of video streams (and sometimes other content types) across your enterprise network. + +## Town halls and view-only meetings + +Here's the eCDN setup for town halls and view-only meetings: + +- If an organizer has a Teams Premium license, Microsoft eCDN is the default for view-only meetings and town halls. +- If the organizer doesn't have a Teams Premium license, your chosen eCDN provider is the default for view-only meetings and town halls. +- If the organizer doesn’t have a Teams Premium license and you haven’t set up eCDN in the Teams admin center, town halls and view-only meetings don’t have an eCDN. + +Without Microsoft eCDN, town hall organizers with a Premium license might not be able to access some future features that require this eCDN solution. + +If you want your town hall and view-only meeting organizers with a Teams Premium license to use your chosen eCDN provider, see the [Manage the eCDN solution for Premium town halls and view-only meetings](#manage-the-ecdn-solution-for-premium-town-halls-and-view-only-meetings) section in this article. ## Microsoft eCDN -**Microsoft eCDN** solves the network congestion problem that occurs during large corporate virtual events such as all-hands meetings. Microsoft eCDN forms a mesh network over the LAN, which reduces the load by up to 98%. With WebRTC as its foundation, Microsoft eCDN eliminates the need for any software or hardware installations. Microsoft eCDN is included with a Teams Premium license, but you can also purchase this solution for organizers who don't have a Teams Premium license. +**Microsoft eCDN** solves the network congestion problem that occurs during large corporate virtual events such as all-hands meetings. Microsoft eCDN forms a mesh network over the LAN, reducing the load by up to 98%. With WebRTC as its foundation, Microsoft eCDN eliminates the need for any software or hardware installations. Microsoft eCDN is included with a Teams Premium license, but you can also purchase this solution for organizers who don't have a Teams Premium license. - Microsoft eCDN works out of the box without any configuration. The network configuration for Microsoft eCDN ensures that remote workers and/or heavy video traffic doesn't strain your network nor oblige you to invest in costly infrastructure. It includes automatic site detection, automatic VPN detection, and automatic NAT/firewall traversal. To learn more, see [How to enable Microsoft eCDN](/ecdn/how-to/enable-microsoft-ecdn-for-your-tenant). - Silent Testing with Microsoft eCDN allows admins to simulate large events on their corporate network, allowing thorough and non-disruptive testing and troubleshooting before a real event. To learn more, see [Perform a silent test](/ecdn/how-to/perform-silent-test). - Industry-leading analytics from Microsoft eCDN provide granular analyses and allow admins to quickly find the root cause for any streaming issue. Your toolkit includes delivery and UX metrics, advanced drill downs, and per-user analytics. Learn more at [Analytics](/ecdn/technical-documentation/analytics). -Town hall organizers with a Teams Premium license have Microsoft eCDN on by default, but you can select a different eCDN solution for these organizers. Without Microsoft eCDN, town hall organizers with a Premium license might not be able to access some future features that require this eCDN solution. -To change the eCDN solution your Premium town hall organizers use, see the [Manage the eCDN solution for Premium town halls](#manage-the-ecdn-solution-for-premium-town-halls) section in this article. ## Acquire and set up your eCDN solution outside of Teams @@ -92,15 +104,15 @@ Follow these steps to configure your eCDN solution: 1. Toggle the **Video distribution provider** to **On**. 1. Choose an **eCDN/SDN provider** from the **Video distribution provider** dropdown list. 1. Fill out the other fields as directed by your solution provider (some solution providers don't use all the fields). -1. Select **Save**. +1. Select **Save**. It might take up to 24 hours to see your changes. 1. To check if your setup is correct, select **Verify setup**. - Search for any video in your organization to validate with. - If your eCDN provider is set up correctly, you see a **Success** message on the verify setup tool. - If you aren't set up correctly, you see a **Failure** message. Copy the event message to share with your provider for troubleshooting. -## Manage the eCDN solution for Premium town halls +## Manage the eCDN solution for Premium town halls and view-only meetings -Microsoft eCDN solution is the default for town hall organizers with a Teams Premium license. You can manage whether your Premium organizers use the Microsoft eCDN or one of our partner eCDN solutions. +Microsoft eCDN solution is the default for town hall and view-only meeting organizers with a Teams Premium license. You can manage whether your Premium organizers use the Microsoft eCDN or one of our partner eCDN solutions. |Teams admin center policy option|Parameter value in PowerShell| Behavior| |---------|---------|---------------| diff --git a/Teams/support-pin.md b/Teams/support-pin.md index 22623f0365..fdfd8f13ee 100644 --- a/Teams/support-pin.md +++ b/Teams/support-pin.md @@ -1,7 +1,7 @@ --- title: How do I look up my support PIN? -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: article ms.service: msteams diff --git a/Teams/team-templates-nonprofit.md b/Teams/team-templates-nonprofit.md index 42b724600a..7f6b0814c6 100644 --- a/Teams/team-templates-nonprofit.md +++ b/Teams/team-templates-nonprofit.md @@ -54,7 +54,7 @@ Here's the channels and apps that come with the Manage Volunteers team template. It takes only a few quick steps to create a team from the Manage volunteers template. -1. In Teams, go to **Teams** > **Join or create a team** > **Create team**. +1. In Teams, go to **Chat** > **New team** > **Create**. 2. Choose the **Manage volunteers** team template. 3. Choose a privacy level: - **Private**: People need permission from the team owner to join the team. diff --git a/Teams/teams-add-on-licensing/licensing-enhance-teams.md b/Teams/teams-add-on-licensing/licensing-enhance-teams.md index 7a9f4fe20f..c5e80a9c9a 100644 --- a/Teams/teams-add-on-licensing/licensing-enhance-teams.md +++ b/Teams/teams-add-on-licensing/licensing-enhance-teams.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams Premium licensing -author: wlibebe -ms.author: wlibebe +ms.author: danismith +author: DaniEASmith manager: pamgreen ms.reviewer: margidesai, spraveen ms.date: 03/26/2024 @@ -39,14 +39,33 @@ Microsoft Teams Premium is a Teams add-on license that allows organizations with This article is for IT admins who wish to understand Teams Premium licensing and purchase Teams Premium licenses for their users. This article provides answers to questions like: -- [How does Teams Premium compare to Teams?](#how-does-teams-premium-compare-to-teams) -- [Are there previous Teams features that moved to Teams Premium?](#are-there-previous-teams-features-that-moved-to-teams-premium) -- [What are the requirements to purchase Teams Premium?](#what-are-the-requirements-to-purchase-teams-premium) -- [Which users should be assigned Teams Premium licenses?](#which-users-should-be-assigned-teams-premium-licenses) -- [How does Teams Premium differ from Teams Rooms Pro?](#how-does-teams-premium-differ-from-teams-rooms-pro) -- [Can I experience Teams Premium before buying licenses?](#can-i-experience-teams-premium-before-buying-licenses) -- [How do I purchase Teams Premium licenses?](#how-do-i-purchase-teams-premium-licenses) -- [Is admin configuration required after assigning users licenses?](#is-admin-configuration-required-after-assigning-users-licenses) +- [Microsoft Teams Premium licensing](#microsoft-teams-premium-licensing) + - [How does Teams Premium compare to Teams?](#how-does-teams-premium-compare-to-teams) + - [Meetings](#meetings) + - [Webinars](#webinars) + - [Town halls](#town-halls) + - [Advanced Collaboration Tools](#advanced-collaboration-tools) + - [Meetings protection](#meetings-protection) + - [Intelligent recap](#intelligent-recap) + - [Intelligent meeting recap](#intelligent-meeting-recap) + - [Virtual Appointments](#virtual-appointments) + - [Meet app](#meet-app) + - [Places Workplace Collaboration](#places-workplace-collaboration) + - [Queues app](#queues-app) + - [Immersive Mesh Experiences](#immersive-mesh-experiences) + - [Are there previous Teams features that moved to Teams Premium?](#are-there-previous-teams-features-that-moved-to-teams-premium) + - [What are the requirements to purchase Teams Premium?](#what-are-the-requirements-to-purchase-teams-premium) + - [Can I acquire Teams Premium features without the Teams Premium license?](#can-i-acquire-teams-premium-features-without-the-teams-premium-license) + - [Which users should be assigned Teams Premium licenses?](#which-users-should-be-assigned-teams-premium-licenses) + - [Which features are applied to organizers, attendees/users, or admins?](#which-features-are-applied-to-organizers-attendeesusers-or-admins) + - [How does Teams Premium differ from Teams Rooms Pro?](#how-does-teams-premium-differ-from-teams-rooms-pro) + - [Can I experience Teams Premium before buying licenses?](#can-i-experience-teams-premium-before-buying-licenses) + - [How does the Teams Premium self-service trial license work?](#how-does-the-teams-premium-self-service-trial-license-work) + - [Can I manage my users' self-service trial licenses?](#can-i-manage-my-users-self-service-trial-licenses) + - [What are the terms and conditions of the Teams Premium self-service trial?](#what-are-the-terms-and-conditions-of-the-teams-premium-self-service-trial) + - [What happens if my users' trial licenses expire?](#what-happens-if-my-users-trial-licenses-expire) + - [How do I purchase Teams Premium licenses?](#how-do-i-purchase-teams-premium-licenses) + - [Is admin configuration required after assigning users licenses?](#is-admin-configuration-required-after-assigning-users-licenses) To learn how to set up and configure Teams Premium features, see [Microsoft Teams Premium - Overview for administrators](/microsoftteams/enhanced-teams-experience), which also includes links to end-user documentation. @@ -63,33 +82,32 @@ The following tables compare key features between Teams and Teams Premium. Becau | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Host and attend Teams Meetings | ✔️ | | -| Experience Teams' standard look and feel | ✔️ | | -| Use standard and custom meeting backgrounds at the user level| ✔️ | | -| Read live captions during meetings and live events | ✔️ | | -| Set up a green room for meeting presenters and organizers| ✔️ | | -| View attendance reports | ✔️ | | -| In-progress meeting real time telemetry with 24 hour retention | ✔️ | | -| Customize meeting templates for your organization | | ✔️ | -| Add organization branding to meeting lobbies | | ✔️ | -| Customize meeting backgrounds for your organization | | ✔️ | -| Customize Together mode scenes for your organization | | ✔️ | -| Add branding to meeting invites and meeting join launch pages | | ✔️ | -| Read live translated captions during meetings | | ✔️ | -| Manage what attendees see | | ✔️ | -| Use RTMP-In for meetings | | ✔️ | -| Hide attendee names | | ✔️ | -| View engagement reports | | ✔️ | -| Translate post-meeting transcriptions (*coming soon*) | | ✔️ | -| Turn on eCDN Meetings\* | | ✔️ | -| Audio quality alerts | | ✔️ | -| Video quality alerts | | ✔️ | -| Screen sharing quality alerts | | ✔️ | -| Automatic real time telemetry with 7 day retention | | ✔️ | -| Prevent users from sharing content when attending external Teams meetings | | ✔️ | -| View how many users attended meetings that used a Teams Premium feature | | ✔️ | -| View the number of meetings used a Teams Premium feature| | ✔️ | -| View the number of meetings each user attended that used a Teams Premium feature| | ✔️ | +| Host and attend Teams Meetings | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Experience Teams' standard look and feel | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +| Use standard and custom meeting backgrounds at the user level| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Read live captions during meetings and live events | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Set up a green room for meeting presenters and organizers| ![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) | +| In-progress meeting real time telemetry with 24 hour retention | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Customize meeting templates for your organization | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Add organization branding to meeting lobbies | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Customize meeting backgrounds for your organization | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Customize Together mode scenes for your organization | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Add branding to meeting invites and meeting join launch pages | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Read live translated captions during meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Manage what attendees see | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Use RTMP-In for meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Hide attendee names | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View engagement reports | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Turn on eCDN for view-only meetings\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Audio quality alerts | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Video quality alerts | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Screen sharing quality alerts | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Automatic real time telemetry with 7 day retention | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Prevent users from sharing content when attending external Teams meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View how many users attended meetings that used a Teams Premium feature | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of meetings used a Teams Premium feature| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of meetings each user attended that used a Teams Premium feature| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *To take advantage of eCDN for all attendees, either a Teams Premium or standalone eCDN license is required. eCDN can be acquired as a standalone license, and more licenses can be purchased outside of Teams Premium, if needed. To learn about eCDN licensing, see [Microsoft eCDN](https://www.microsoft.com/en-us/microsoft-teams/ecdn).* @@ -97,54 +115,55 @@ The following tables compare key features between Teams and Teams Premium. Becau | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Require attendees to register | ✔️ | | -| Assign a co-organizer | ✔️ | | -| Limit the number of people who can register | ✔️ | | -| Allow registered users to bypass the lobby | ✔️ | | -| Turn on Q&A for webinars with up to 1,000 attendees | ✔️ | | -| View attendance reports | ✔️ | | -| Set up a green room for webinar presenters and organizers| ✔️ | | -| Manage what attendees see | | ✔️ | -| Send custom and reminder emails to registrants | | ✔️ | -| Create a webinar wait list | | ✔️ | -| Webinar organizers can view engagement reports | | ✔️ | -| Manually approve registrants | | ✔️ | -| View engagement reports | | ✔️ | -| Limit the day and time when people can register | | ✔️ | -| Use RTMP-In for webinars | | ✔️ | -| View how many users attended webinars that used a Teams Premium feature | | ✔️ | -| View the number of webinars used a Teams Premium feature| | ✔️ | -| View the number of webinars each user attended that used a Teams Premium feature.| | ✔️ | +| Require attendees to register | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Assign a co-organizer | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Limit the number of people who can register | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Allow registered users to bypass the lobby | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Turn on Q&A for webinars with up to 1,000 attendees | ![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) | +| Set up a green room for webinar presenters and organizers| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Manage what attendees see | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Send custom and reminder emails to registrants | | ![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) | +| Webinar organizers can view engagement reports | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Manually approve registrants | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View engagement reports | | ![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) | +| Use RTMP-In for webinars | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View how many users attended webinars that used a Teams Premium feature | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of webinars used a Teams Premium feature| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of webinars each user attended that used a Teams Premium feature.| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ### Town halls | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Broadcast town halls to 10k attendees | ✔️ | | -| Host up to 15 town halls simultaneously | ✔️ | | -| View attendance reports | ✔️ | | -| Manage what attendees see | ✔️ | | -| Provide town hall video on demand | ✔️ | | -| Provide a unique join link for presenters | ✔️ | | -| Set up a green room for presenters and organizers | ✔️ | | -| Turn on third party or Microsoft eCDN for town halls | ✔️ | | -| Use RTMP-In for town halls 1 | ✔️ | | -| Town hall Q&A capacity of 10k attendees | ✔️ | | -| Organizers can pre-select six languages for live translated captions | ✔️ | | -| Broadcast town halls to 20k attendees | | ✔️ | -| Host up to 50 town halls simultaneously | | ✔️ | -| Town hall Q&A capacity of 20k attendees | | ✔️ | -| Use Microsoft eCDN for Premium town halls 2 | | ✔️ | -| Choose an eCDN provider for town halls 2 | | ✔️ | -| View Microsoft Town hall insights | | ✔️ | -| Town hall organizers can view engagement reports | | ✔️ | -| Edit town hall emails | | ✔️ | -| Town hall attendee reactions | | ✔️ | -| Organizers can pre-select 10 languages for live translated captions | | ✔️ | -| Real time monitoring of the attendee experience | | ✔️ | -| View how many users attended town halls that used a Teams Premium feature | | ✔️ | -| View the number of town halls used a Teams Premium feature| | ✔️ | -| View the number of town halls each user attended that used a Teams Premium feature.| | ✔️ | +| Broadcast town halls to 10k attendees | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Host up to 15 town halls simultaneously | ![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) | +| Manage what attendees see | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Provide town hall video on demand | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Provide a unique join link for 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) | +| Set up a green room for presenters and organizers | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Turn on third party or Microsoft eCDN for town halls | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Use RTMP-In for town halls 1 | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Town hall Q&A capacity of 10k attendees | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Organizers can pre-select six languages for live translated captions | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Broadcast town halls to 20k attendees | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Host up to 50 town halls simultaneously | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Town hall Q&A capacity of 20k attendees | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Use Microsoft eCDN for Premium town halls 2 | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Choose an eCDN provider for town halls 2 | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View Microsoft Town hall insights | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Town hall organizers can view engagement reports | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Edit town hall emails | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Town hall attendee reactions | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Organizers can pre-select 10 languages for live translated captions | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Real time monitoring of the attendee experience | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View how many users attended town halls that used a Teams Premium feature | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of town halls used a Teams Premium feature| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View the number of town halls each user attended that used a Teams Premium feature.| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Event chat for attendees| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | 1 If RTMP-In is enabled for a town hall, live translated captions aren't available to the attendees even if the organizer selects the languages before the town hall starts. 2 To take advantage of eCDN for all attendees, either a Teams Premium or standalone eCDN license is required. eCDN can be acquired as a standalone license, and more licenses can be purchased outside of Teams Premium, if needed. To learn about eCDN licensing, see [Microsoft eCDN](https://www.microsoft.com/en-us/microsoft-teams/ecdn).* @@ -153,12 +172,12 @@ The following tables compare key features between Teams and Teams Premium. Becau | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Admin can view insights on inactive external domains\* | | ✔️ | -| Admin can view insights on inactive teams\* | | ✔️ | -| Admin can view insights on external collaboration by user\* | | ✔️ | -| Admin can view insights on external collaboration by team\* | | ✔️ | -| Admin can view insights on external collaboration by guest\* | | ✔️ | -| Users can block incoming chats from people in your organization | | ✔️ | +| Admin can view insights on inactive external domains\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Admin can view insights on inactive teams\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Admin can view insights on external collaboration by user\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Admin can view insights on external collaboration by team\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Admin can view insights on external collaboration by guest\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Users can block incoming chats from people in your organization | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *Customers must acquire and assign Teams Premium licenses to each user in their tenant for its use of Advanced collaboration analytics.* @@ -166,17 +185,17 @@ The following tables compare key features between Teams and Teams Premium. Becau | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Manage meeting lobbies | ✔️ | | -| End-to-end encryption for one-to-one calls | ✔️ | | -| Moderate meeting chats | ✔️ | | -| Control who can present | ✔️ | | -| Add watermarks to meetings | | ✔️ | -| End-to-end encryption for meetings | | ✔️ | -| Control who can record | | ✔️ | -| Prevent copy/paste in meeting chats | | ✔️ | -| Assign Microsoft Purview Information Protection sensitivity labels for meetings\* | | ✔️ | -| Custom user policy packages | | ✔️ | -| Prevent users from sharing content in external Teams meetings | | ✔️ | +| Manage meeting lobbies | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| End-to-end encryption for one-to-one calls | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Moderate meeting chats | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Control who can present | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Add watermarks to meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| End-to-end encryption for meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Control who can record | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Prevent copy/paste in meeting chats | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Assign Microsoft Purview Information Protection sensitivity labels for meetings\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Custom user policy packages | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Prevent users from sharing content in external Teams meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *This feature is only available to Teams Premium users with a Microsoft 365 E5, E5 Compliance, F5 Compliance, or F5 Security + Compliance subscription. For more information on licensing requirements, see [What are the requirements to purchase Teams Premium?](#what-are-the-requirements-to-purchase-teams-premium)* @@ -188,16 +207,16 @@ In the meeting recap, your users can find the most important parts of a meeting, | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| View recordings of meetings | ✔️ | | -| View meeting transcripts | ✔️ | | -| View and use files added to meetings | ✔️ | | -| View and use apps added to meetings | ✔️ | | -| Navigate meeting recordings with autogenerated chapters (*coming soon*) | | ✔️ | -| View when a screen was shared in the meeting transcript | | ✔️ | -| View time markers in meeting recordings when you joined or left a meeting | | ✔️ | -| Jump to different speakers with speaker timeline markers | | ✔️ | -| View AI-generated notes and tasks from meetings | | ✔️ | -| View when you were mentioned in a meeting\* | | ✔️ | +| View recordings of meetings | ![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 meeting 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) | +| View and use files added to meetings | ![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 and use apps added to meetings | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Navigate meeting recordings with autogenerated chapters (*coming soon*) | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View when a screen was shared in the meeting transcript | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View time markers in meeting recordings when you joined or left a meeting | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Jump to different speakers with speaker timeline markers | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View AI-generated notes and tasks from meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View when you were mentioned in a meeting\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *Mentions of a user's name is pulled from the meeting transcript, not from an @mention tag in the meeting chat.* @@ -208,18 +227,18 @@ In the meeting recap, your users can find the most important parts of a meeting, | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Access Virtual Appointments with the Bookings app for scheduling, appointment management, and email notifications | ✔️ | | -| Integrate Virtual Appointments using APIs | ✔️ | | -| Join appointments from a browser | ✔️ | | -| Join appointments in Teams | ✔️ | | -| Allow users to join a virtual lobby waiting room | ✔️ | | -| Integrate with Microsoft Forms | ✔️ | | -| Customize the lobby waiting room with themes and logos | | ✔️ | -| Send SMS notifications\* | | ✔️ | -| Organizational and departmental analytics | | ✔️ | -| View and manage scheduled appointments in the queue | | ✔️ | -| View and manage on-demand appointments in the queue | | ✔️ | -| Send post-appointment follow-ups (*coming soon*) | | ✔️ | +| Access Virtual Appointments with the Bookings app for scheduling, appointment management, and email notifications | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +| Integrate Virtual Appointments using APIs | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +| Join appointments from a browser | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Join appointments in Teams | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Allow users to join a virtual lobby waiting room | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Integrate with Microsoft Forms | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Customize the lobby waiting room with themes and logos | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Send SMS notifications\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Organizational and departmental analytics | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View and manage scheduled appointments in the queue | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View and manage on-demand appointments in the queue | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Send post-appointment follow-ups (*coming soon*) | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *SMS notifications for Virtual Appointments are currently available in the US, Canada, and UK.* @@ -229,29 +248,50 @@ The Meet app in Teams allows users to view important details of their meetings i | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| View and prepare upcoming meetings | ✔️ | | -| Join ongoing meetings | ✔️ | | -| View and recap meetings you attended | ✔️ | | -| Filter meetings by All, with Content, and Recorded | ✔️ | | -| View and recap meetings that you missed | | ✔️ | -| View and recap meetings that mention you\* | | ✔️ | -| View when you were mentioned in a meeting\* | | ✔️ | -| View AI-generated tasks from meetings | | ✔️ | +| View and prepare upcoming meetings | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Join ongoing meetings | ![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 and recap meetings you attended | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Filter meetings by All, with Content, and Recorded | ![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 and recap meetings that you missed | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View and recap meetings that mention you\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View when you were mentioned in a meeting\* | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| View AI-generated tasks from meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | \* *Mentions of a user's name is pulled from the meeting transcript, not from an @mention tag in the meeting chat.* +### Places workplace collaboration + +Microsoft Places allows you and your organization to build a smart workplace. With a Teams Premium license, your users can experience upgraded features that support advanced booking and space analytics. As an admin, you have access to advanced management capabilities. To learn more about Places, see [Microsoft Places overview](/microsoft-365/places/places-overview). + +| Feature | Teams | Teams Premium | +|---------|:-----:|:-------------:| +|In-person events| ![Image of a checkmark for yes](/office/media/icons/success-teams.png)| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Hybrid RSVP| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Places card| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Work plans| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Workplace presence| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Individual desk booking| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Intelligent suggestions| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Places explorer| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Places finder| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Quick book| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Room check-in and auto release| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Space analytics| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Team guidance| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | + ### Queues app The Queues app is a Teams-native solution designed to empower organizations to manage customer engagements efficiently, unlocking a set of advanced call functionalities for Teams Phone Call queues and Auto attendants. To learn more about the Queues app, see [Use the Queues app for Microsoft Teams](https://support.microsoft.com/office/370ad83e-c2c1-4a9f-8a59-16c98be102e9) and [Manage the Queues app](/microsoftteams/manage-queues-app). | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -|Call queue and Auto attendant management directly within Teams| | ✔️ | -|Real-time metrics for Call queues and Auto attendants within Queues app| | ✔️ | -|Historical reporting for Call queues and Auto attendants within Queues app| | ✔️ | +|Call queue and Auto attendant management directly within Teams| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Real-time metrics for Call queues and Auto attendants within Queues app| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +|Historical reporting for Call queues and Auto attendants within Queues app| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | For a complete list of features available in the Queues app, see [Manage voice applications policies](/microsoftteams/manage-voice-applications-policies). + ### Immersive Mesh Experiences With Immersive spaces in Teams, your users can join a 3D immersive meeting experience for up-to 16 people right from any Teams meeting.
    @@ -259,10 +299,10 @@ With a Teams Premium license, your distributed workforce can connect in 3D immer | Feature | Teams | Teams Premium | |---------|:-----:|:-------------:| -| Avatars in Teams | ✔️ | | -| 3D immersive meetings in Teams | ✔️ | | -| Custom immersive spaces in Microsoft Mesh | | ✔️ | -| Larger capacity immersive meetings | | ✔️ | +| Avatars in Teams | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) |![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| 3D immersive meetings in Teams | ![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 immersive spaces in Microsoft Mesh | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | +| Larger capacity immersive meetings | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) | ## Are there previous Teams features that moved to Teams Premium? @@ -308,8 +348,8 @@ For example, in a Teams meeting, Teams checks each users’ type of Teams licens - **Organizer-based features:** Some Teams Premium features are applied at the organizer level. If an event organizer has a Teams Premium license, the organizer-based features are shared and made accessible to the attendees only during the event. -> [!NOTE] -> If an organizer with a Teams Premium license appoints a delegate to create their meetings, the delegate doesn't need a Teams Premium license for organizer-based features to work. + > [!NOTE] + > If an organizer with a Teams Premium license appoints a delegate to create their meetings, the delegate doesn't need a Teams Premium license for organizer-based features to work. - **Attendee-based features:** Some Teams Premium features are applied at the attendee/user level. These Teams Premium features aren't shared or made accessible to other attendees during the event and only benefit the Teams Premium licensed users. - **Admin-based features:** Some Teams Premium features primarily benefit an organization's IT admins. These features are only accessible to Teams admins with a Teams Premium license. @@ -318,13 +358,13 @@ The following table shows which Teams Premium features provide primary value to | Premium Value | Features Applied at Organizer Level | Features Applied at Attendee/User Level | Features Applied at the IT Admin Level | | ------------- | :---------------------------------- | :--------------------------------- | :------------------------------------- | -| **More intelligence** | ✔️ Live translation for captions (40 languages) | ✔️ AI-generated chapters for intelligent meeting recap recordings
    ✔️ Personalized timeline markers in meeting recordings
    ✔️ Speaker timeline markers
    ✔️ Intelligent speaker search in the transcript
    ✔️ AI-generated notes and tasks | ✔️ Advanced collaboration analytics | -| **More personalized** | ✔️ Meeting templates (configured by IT admin)
    ✔️ Custom meeting branding ✔️ Custom immersive spaces in Microsoft Mesh| ✔️ Custom organization backgrounds
    ✔️ Organization together mode scenes
    ✔️ Custom user policy packages
    ✔️ View aggregated usage of Teams Premium features by users in your org| | -| **More protected** | ✔️ Watermarking
    ✔️ Who can record
    ✔️ End-to-end encryption for online meetings (up to 200)
    ✔️ Hide attendees' names
    ✔️ E5 customers: Microsoft Purview Information Protection sensitivity labels for Meetings | ✔️ Block incoming chats from people in the organization
    ✔️ Prevent users from sharing content in external Teams meetings
    ✔️ Audio quality alerts
    ✔️ Video quality alerts
    ✔️Screen sharing quality alerts
    ✔️Automatic real time telemetry with 7 day retention
    ✔️Prevent users from sharing content when attending external Teams meetings | | -| **Advanced Virtual Appointments** | ✔️ Custom lobby room with branding, logos, and more
    ✔️ SMS notifications | ✔️ On-demand and scheduled appointment functionality and queue views
    ✔️ Analytics at departmental and organizational level
    SMS notifications

    *At the user level, these features apply to any user in the tenant who wants access to pre and post-appointment actions and data, like a meeting scheduler, supervisor, or admin.* | | -| **Advanced Webinars** | ✔️ Manage attendee view
    ✔️ Reminder emails
    ✔️ Wait lists and manual approval
    ✔️ Limit registration date and time
    ✔️ RTMP-In | | -| **Advanced Town halls** | ✔️ Scale up to 20,000 attendees
    ✔️ Concurrency limit of 50 meetings
    ✔️ Email customization
    ✔️ Microsoft eCDN support
    ✔️Real-time organizer analytics ✔️Pre-select 10 languages for attendee captions
    ✔️Town hall attendee reactions | | ✔️Real time monitoring of the attendee experience | -| **Microsoft eCDN** | | ✔️ Works with Teams Meetings and Town halls
    ✔️ Microsoft eCDN included as a part of the Teams Premium bundle | | +| **More intelligence** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Live translation for captions (40 languages) | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) AI-generated chapters for intelligent meeting recap recordings
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Personalized timeline markers in meeting recordings
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Speaker timeline markers
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Intelligent speaker search in the transcript
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) AI-generated notes and tasks | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Advanced collaboration analytics | +| **More personalized** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meeting templates (configured by IT admin)
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Custom meeting branding
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)
    Custom immersive spaces in Microsoft Mesh| ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Custom organization backgrounds
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Organization together mode scenes
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Custom user policy packages
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) View aggregated usage of Teams Premium features by users in your org| | +| **More protected** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Watermarking
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Who can record
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) End-to-end encryption for online meetings (up to 200)
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Hide attendees' names
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) E5 customers: Microsoft Purview Information Protection sensitivity labels for Meetings | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Block incoming chats from people in the organization
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Prevent users from sharing content in external Teams meetings
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Audio quality alerts
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Video quality alerts
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Screen sharing quality alerts
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Automatic real time telemetry with 7 day retention
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Prevent users from sharing content when attending external Teams meetings | | +| **Advanced Virtual Appointments** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Custom lobby room with branding, logos, and more
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) SMS notifications | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) On-demand and scheduled appointment functionality and queue views
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Analytics at departmental and organizational level
    SMS notifications

    *At the user level, these features apply to any user in the tenant who wants access to pre and post-appointment actions and data, like a meeting scheduler, supervisor, or admin.* | | +| **Advanced Webinars** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Manage attendee view
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Reminder emails
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Wait lists and manual approval
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Limit registration date and time
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) RTMP-In | | +| **Advanced Town halls** | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Scale up to 20,000 attendees
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Concurrency limit of 50 meetings
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Email customization
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Microsoft eCDN support
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Real-time organizer analytics
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Pre-select 10 languages for attendee captions
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town hall attendee reactions
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Event chat| | ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Real time monitoring of the attendee experience | +| **Microsoft eCDN** | | ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Works with Teams view-only meetings, live events, and town halls
    ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Microsoft eCDN included as a part of the Teams Premium bundle | | ## How does Teams Premium differ from Teams Rooms Pro? @@ -394,7 +434,7 @@ The following list indicates Teams Premium features that require admin configura - Being assigned a custom policy package. - Using organization customized meeting templates. - Seeing organization customized branding. -- Using eCDN for town halls. +- Using eCDN for town halls, view-only meetings, and live events. - Using RTMP-In. - Customizing Virtual Appointment lobby rooms with branding. - Hiding attendees names from meetings and webinars. diff --git a/Teams/teams-administrative-units.md b/Teams/teams-administrative-units.md new file mode 100644 index 0000000000..5b9410223e --- /dev/null +++ b/Teams/teams-administrative-units.md @@ -0,0 +1,144 @@ +--- +title: Using administrative units in Microsoft Teams +author: MicrosoftHeidi +ms.author: heidip +manager: jtremper +ms.reviewer: andrewklutz +ms.date: 10/16/2024 +ms.topic: article +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +ms.collection: + - M365-collaboration +f1.keywords: +- NOCSH +appliesto: + - Microsoft Teams +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn how to use administrative units to manage groups of users or other entities in Microsoft Teams. +--- + +# Administrative units for Microsoft Teams + +This article describes the highlights of Administrative Units for Teams administration using the Teams admin center and the Teams PowerShell module. Administrative Units are a way to delegate administrative tasks to a subset of users, groups, or devices using the Microsoft Entra Admin Portal. + +You could previously manage Devices via Administrative Units, but only for the Teams Administrator role, as outlined in this article: [Manage devices with administrative units](administrative-unit.md). + +With more capabilities enabled to be managed via Administrative Units, there's a need to cover the following usages: + +## Set up Administrative Units + +### Scenario One: Creation of Administrative Units in the Microsoft Entra admin center (AAD) + +Full details on how to create Administrative Units can be found here (Administrative Unit administrators need a Microsoft Entra ID P1 or P2 license): [Create or delete Administrative Units - Entra ID](/entra/identity/role-based-access-control/admin-units-manage?tabs=ms-powershell). + +### Scenario Two: Assignment and unassignment of RBAC roles to Administrative Units in the Microsoft Entra admin center (AAD) + +Global Administrators can assign any of the following RBAC roles using the method in the adjacent column: + +|RBAC Role |Assignment method |Documentation | +|---------------------------------------|------------------------------------------------------------|--------------| +|Teams administrator |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs |[Learn more](/graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope) | +|Teams device administrator |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs |[Learn more](/graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope) | +|Teams communication administrator |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs |[Learn more](/graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope) | +|Teams communication support engineer |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs |[Learn more](/graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope) | +|Teams communication support specialist |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs |[Learn more](/graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope) | +|Teams telephony administrator |Microsoft Entra admin center (UI)
    Teams PowerShell
    Teams Graph APIs | | + +The role assignments listed in the table can also be applied directly to the intended users or groups. Learn more at [Use Microsoft Entra groups to manage role assignments - Microsoft Entra ID](/entra/identity/role-based-access-control/groups-concept). + +## Roles and capabilities + +|Management types |Admin |Device admin |Communication admin |Telephony admin |Communication support engineer |Communication support specialist | +|-----------------|------|-------------|--------------------|----------------|-------------------------------|---------------------| +|Teams management |NA |NA |NA |NA |NA |NA | +|User management |-Manage users list page
    -User details page
    --Account tab
    --Meetings and calls
    --Policies
    --Devices tab |NA |-Manage users list page
    -User details page
    --Account tab
    --Meetings and calls
    --Policies
    --Voice
    --Voicemail |-Manage users list page
    -User details page
    --Account tab
    --Meetings and calls
    -Policies
    -Voice
    Voicemail |-Manage users list page
    -User details page
    --Meetings and calls |-Manage users list page
    -User details page
    --Meetings and calls | +|Devices management |The entire devices section (seven options) |The entire devices section (seven options) |NA |NA |NA |NA | +|Policy management |Option to only perform user or group policy assignments for the following policies:
    -Audio conferencing
    -Meeting
    -Customization
    -Live events
    -Events
    -Messaging
    -Calling
    -Call hold
    -Call park
    -Caller ID
    -Emergency
    -Mobility
    -Voice routing
    -Voicemail
    -Voice applications |NA |Option to only perform user or group policy assignments for the following policies:
    -Audio conferencing
    -Meeting
    -Customization
    -Live events
    -Events
    -Calling
    -Call hold
    -Call park
    -Caller ID
    -Emergency
    -Mobility
    -Voice routing
    -Voicemail
    -Voice applications |NA |NA |NA | +|Voice management |Phone Number assignment – From User Details Page (Only Direct Routing numbers) |NA |Phone Number assignment – From User Details Page (Only Direct Routing numbers) |NA |NA |NA | +|Analytics and reporting management |-Usage reports (only PSTN reports
    )-Call quality dashboard (UII info redacted) |NA |-Usage reports (only PSTN reports
    )-Call quality dashboard (UII info redacted) |NA |Call quality dashboard (UII info redacted) |Call quality dashboard (UII info redacted) | +|Apps management |NA |NA |NA |NA |NA |NA | + +## Individual feature areas + +### Device management + +As a scoped administrator with the Teams device admin or Teams administrator role, you can: + +- Access the Devices section in Teams admin center and view the list of devices assigned to the users in the Administrative unit +- Filter, sort, and search the devices by various criteria. +- Select a device and view its details, configuration, and status. +- Perform actions on the device, such as restart, reset, update, or assign to a user. + +> [!NOTE] +> Export of devices isn’t available for scoped admin roles, you need to have tenant-wide permissions to export devices. + +To learn more, see [Manage devices with administrative units](administrative-unit.md). + +### User management + +As a scoped administrator with the Teams administrator role or any of the Teams communication roles, you can: + +- Filter, sort, and search the users by various criteria. +- Select a user and view their details, meetings, policies, and devices. +- Assign or unassign a Direct Routing phone number to a user in your Administrative Unit. +- Assign or unassign policies to a user in your Administrative Unit. +- Perform real-time or past meetings troubleshooting for a user in your Administrative Unit. + +> [!NOTE] +> Export of users isn’t available for scoped admin roles, you need to have tenant-wide permissions to export users. + +### Policy management + +As a scoped administrator with the Teams administrator role or any of the Teams communication roles, you can: + +- Access the Policy sections in the Teams admin center and view the list of policies available in the tenant. +- Assign or unassign policies to a user or a group in your Administrative Unit. +- View the policy assignments and the effective policy for a user or a group in your Administrative Unit. Batch policy assignments are also enabled. + +### Phone number management + +As a scoped administrator with the Teams administrator role or any of the Teams communication roles, you can: + +- Assign or unassign Direct Routing phone numbers to users in your Administrative Unit from the User Details page in the Teams admin center. + +### Analytics and reporting management + +As a scoped administrator with the Teams administrator role or any of the Teams communication roles, you can: + +- Access the Usage reports section in the Teams admin center and view the reports (Only PSTN) scoped to the users in your Administrative Unit. +- Filter, sort, and export the reports by various criteria. +- Access the Call Quality Dashboard section in the Teams admin center and view the call quality data for the users in your Administrative Unit. + +## Limitations for Administrative Units + +Tasks that aren't available in this phase for a scoped administrator (regardless of the RBAC role), in either the Teams admin center or through the Teams PowerShell module: + +- Teams and channel settings +- Audio conferencing, voice, and voicemail settings +- Guest access +- External access +- Calling plan and Operator Connect numbers +- Emergency addresses +- Teams apps +- Tenant level settings and conference bridges +- Policy packages +- Emergency addresses, network topology, networks, and locations +- Frontline teams and apps +- Teams advisor and network planner +- Rules + +## Teams PowerShell and Administrative Units + +The functionality outlined in this article is available for the RBAC roles using Teams PowerShell. The differences in PowerShell are: + +- An admin assigned with multiple Admin units is able to manage all the users across each admin unit simultaneously. +- In the Teams admin center, the scoped admin would have to select the particular Administrative Unit and manage those users within the Administrative Unit at any given time. + +An example of using Teams PowerShell and Administrative Units is: + +- An organization has three branches: North, South, and East. North and South branches are assigned to a single admin, and East is assigned to another admin. +- The scoped admin assigned with North and South branches is able to manage all the users across both North and South simultaneously using Teams PowerShell. +- In the Teams admin center, the scoped admin can either manage the North or South branch in turn, but not both at the same time. diff --git a/Teams/teams-adoption-understand-teams-and-channels.md b/Teams/teams-adoption-understand-teams-and-channels.md index 77430e572e..65384f05a7 100644 --- a/Teams/teams-adoption-understand-teams-and-channels.md +++ b/Teams/teams-adoption-understand-teams-and-channels.md @@ -1,9 +1,9 @@ --- title: Understand teams and channels in Microsoft Teams -author: MicrosoftHeidi -ms.author: heidip +author: DaniESmith +ms.author: danismith manager: jtremper -ms.date: 09/12/2024 +ms.date: 11/04/2024 audience: Admin ms.topic: conceptual ms.service: msteams @@ -23,24 +23,16 @@ appliesto: - Microsoft Teams --- - # Understand teams and channels in Microsoft Teams -The concepts of teams and channels are fundamental to a healthy, productive implementation of Microsoft Teams. +The concepts of teams and channels are fundamental to a healthy, productive implementation of Microsoft Teams. - A team is a collection of people, content, and tools that work together to produce a business outcome for your company. Teams is built on Microsoft 365 Groups, and changes to Microsoft 365 group membership sync to the team. -- Channels are the collaboration spaces within a team in which the actual work is done. +- Channels are the collaboration spaces within a team in which the actual work is done. To read more about teams and channels, see the [Overview of teams and channels in Microsoft Teams](teams-channels-overview.md). For comprehensive Teams adoption guidance, get the [Teams Adoption Guide](https://aka.ms/teamstoolkit). To learn more about Teams and Microsoft 365 Groups, see [Microsoft 365 Groups and Microsoft Teams](office-365-groups.md) and [Learn more about Microsoft 365 Groups](https://support.office.com/article/Learn-about-Office-365-groups-b565caa1-5c40-40ef-9915-60fdb2d97fa2). - -**View this short video** -
    -> [!VIDEO https://www.youtube.com/embed/WkAVgNKn0hs] - - - Team access types determine who can join a team: - *Private* teams are restricted to team members approved by the team owner(s). This is a typical setting for project teams and virtual teams in a large organization. diff --git a/Teams/teams-analytics-and-reports/external-domain-activity-report.md b/Teams/teams-analytics-and-reports/external-domain-activity-report.md index d6422f09d8..139d36be41 100644 --- a/Teams/teams-analytics-and-reports/external-domain-activity-report.md +++ b/Teams/teams-analytics-and-reports/external-domain-activity-report.md @@ -7,7 +7,7 @@ audience: Admin ms.topic: article ms.service: msteams ms.reviewer: izzychun -ms.date: 09/09/2024 +ms.date: 10/14/2024 ms.localizationpriority: medium ms.collection: - M365-collaboration @@ -18,7 +18,12 @@ appliesto: --- # Microsoft Teams external domain activity report -The external domain activity report in the Microsoft Teams admin center shows you how you communicate with [trusted external organizations](/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#specify-trusted-microsoft-365-organizations) over chat. This report includes information for 1:1 chats, group chats, and meeting chats, but not for calls or meetings themselves. This report includes both a base and Teams Premium version, where the base version tells you which domains you communicate with and the premium version exposes more detailed information about your communication with each domain. +The external domain activity report in the Microsoft Teams admin center shows you how you communicate with managed external organizations over chat. This report includes information for 1:1 chats, group chats, and meeting chats. + +> [!NOTE] +> We count the following events as meeting chats: When a user is invited to a meeting, when a meeting ends, and when a user leaves a meeting chat. + +This report includes both a base and Teams Premium version, where the base version tells you which domains you communicate with and the premium version exposes more detailed information about your communication with each domain. > [!NOTE] > If you have an explicit allowed domains list, this report may include domains not on your allow list. It's possible for users from an allowed organization to start a group chat with users from your organization and users from other organizations allowed by them, but not allowed by you. These domains will show up in your external domain activity report. @@ -35,22 +40,23 @@ The external domain activity report in the Microsoft Teams admin center shows yo |Item |Description | |-------------------------------|------------| -|Domain name |The domain of the trusted organization. **Premium:** Each domain can be clicked on to see domain-specific insights. | +|Domain name |The domain name. **Premium:** Each domain can be clicked on to see domain-specific insights. | |People in my org |The number of users that have communicated with the organization through chat during the selected time range. | |**Premium:** Total messages | The number of messages that have been exchanged between your organization and the external domain during the selected time range. | |**Premium:** Messages sent | The number of messages that have been sent to your organization by the external domain during the selected time range. | |**Premium:** Messages received | The number of messages that have been sent by your organization to the external domain during the selected time range. | -> [!NOTE] -> -> It's possible to have 0 **people in my org**. If an external domain reaches out to your organization and receives no response, we will display 0 **people in my org**. +- It's possible to have 0 **people in my org**. If an external domain reaches out to your organization and receives no response, we will display 0 **people in my org**. +- In addition to managed communication, we look at when anonymous users join meetings. If you have **Anonymous user join** turned on, you might have unexpected domains appear on your list. Our reports show the names of the domains of the users who joined meetings, rather than marking them as anonymous. +- Premium columns shouldn't be considered accurate until 7 days, 30 days, and 60 days, respectively, after a premium license was assigned. You may notice 0 in some rows or message counts and user counts not making sense. +- Even if a domain has activity in just one or two, but not all three of the potential date ranges (7 days, 30 days, and 60 days), the domain still surfaces the reports of all three date ranges. It shows total internal users as 0 and all premium columns as 0, if applicable. If it's been over 60 days since a premium license was assigned, you can assume a row of all 0s in the 7d or 30d reports means that there was no communication with the domain during that date range, despite the domain surfacing on the list. There should not be all 0s in a 60d report unless it's been less than 60 days since a premium license was assigned. ## Interpret the domain-specific report -|Item |Description | -|--------|-------------| -|**Premium:** Username|The UPN of the user in your org who communicates with the external domain. | -|**Premium:** Messages sent| The number of messages that have been sent to each user by the external domain during the selected time range.| +|Item |Description | +|---------------------------|---------------------------------------------------------------------------| +|**Premium:** Username |The UPN of the user in your org who communicates with the external domain. | +|**Premium:** Messages sent |The number of messages that have been sent to each user by the external domain during the selected time range.| > [!NOTE] > diff --git a/Teams/teams-analytics-and-reports/meeting-attendance-report.md b/Teams/teams-analytics-and-reports/meeting-attendance-report.md index 67d99f0ab6..52e157e2a0 100644 --- a/Teams/teams-analytics-and-reports/meeting-attendance-report.md +++ b/Teams/teams-analytics-and-reports/meeting-attendance-report.md @@ -7,7 +7,7 @@ audience: Admin ms.topic: article ms.service: msteams ms.reviewer: richardzhang -ms.date: 11/27/2023 +ms.date: 10/14/2024 f1.keywords: - NOCSH ms.localizationpriority: high @@ -23,11 +23,11 @@ appliesto: # Manage the attendance and engagement report for meetings and events in Microsoft Teams -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls [!INCLUDE[Teams Premium](../includes/teams-premium-ecm.md)] -The attendance and engagement report for Teams meetings and events shows organizers who attended a meeting, webinar, or town hall, what time each attendee joined, left, and more. +The attendance and engagement report for Teams meetings and events provides detailed information about organizers and attendees. The report shows who attended a meeting, webinar, or town hall, along with the exact times each attendee joined and left, and other engagement metrics. Organizers with a Teams Premium license can see engagement information that captures how attendees reacted and interacted during the meeting or event. The engagement data shows the total count of attendees that performed the following actions: @@ -64,12 +64,14 @@ As an admin, you control whether organizers can view and download the attendance |No, but attendees can opt in|The attendance and engagement report initially excludes all attendees with this policy. To opt in, attendees can set the **Identify me in attendance reports** toggle to **On** or **Off** in their Teams privacy settings.| |Always|The attendance and engagement report includes all attendees with this policy, and attendees can't opt out.| |Never|The attendance and engagement report excludes all attendees with this policy, and attendees can't opt in.| + 1. For **Attendee information**, choose one of the following options: |Option|Behavior| |:------|:-----| |Show everything|**This is the default.** Include attendees' join times, leave times, and in-meeting duration.| - |Only show who attended|Excludes attendees' join times, leave times, and in-meeting duration. + |Only show who attended|Excludes attendees' join times, leave times, and in-meeting duration.| + 1. Select **Save** > [!NOTE] @@ -77,7 +79,7 @@ As an admin, you control whether organizers can view and download the attendance ## Manage attendance report policies with PowerShell -In PowerShell, you can use the **`-AllowEngagementReport`** parameter and [Set-CsTeamsMeetingPolicy cmdlet](/powershell/module/teams/set-csteamsmeetingpolicy) to turn on attendance and engagement reports. This policy is on by default. +To manage attendance and engagement reports, you can use the **`-AllowEngagementReport`** parameter in the PowerShell [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet. To turn off attendance and engagement reports, use the following script: diff --git a/Teams/teams-analytics-and-reports/pstn-minute-pools-report.md b/Teams/teams-analytics-and-reports/pstn-minute-pools-report.md index 1a6b9f5e69..e6f6b3cf2d 100644 --- a/Teams/teams-analytics-and-reports/pstn-minute-pools-report.md +++ b/Teams/teams-analytics-and-reports/pstn-minute-pools-report.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams PSTN minute pools report -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen audience: Admin ms.topic: article diff --git a/Teams/teams-analytics-and-reports/pstn-usage-report.md b/Teams/teams-analytics-and-reports/pstn-usage-report.md index 27e200a1c3..b4d3a90590 100644 --- a/Teams/teams-analytics-and-reports/pstn-usage-report.md +++ b/Teams/teams-analytics-and-reports/pstn-usage-report.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams PSTN usage report -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen audience: Admin ms.topic: article diff --git a/Teams/teams-analytics-and-reports/teams-town-hall-usage-report.md b/Teams/teams-analytics-and-reports/teams-town-hall-usage-report.md index 0c97f92856..af9d72565e 100644 --- a/Teams/teams-analytics-and-reports/teams-town-hall-usage-report.md +++ b/Teams/teams-analytics-and-reports/teams-town-hall-usage-report.md @@ -18,7 +18,7 @@ appliesto: --- # Microsoft Teams town hall usage report -**APPLIES TO:** ✖️Meetings ✖️Webinars ✔️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls The Teams town hall usage report in the Microsoft Teams admin center shows you the activity overview for town hall created in your organization. As an admin, you can view usage information, including the event title, event ID, start time, end time, event access type, and the names of the organizers, presenters, and co-organizers for each event. You can gain insight into usage trends and see who in your organization schedules and produces town halls. diff --git a/Teams/teams-analytics-and-reports/teams-webinar-usage-report.md b/Teams/teams-analytics-and-reports/teams-webinar-usage-report.md index 827093bfd2..aa93877a3c 100644 --- a/Teams/teams-analytics-and-reports/teams-webinar-usage-report.md +++ b/Teams/teams-analytics-and-reports/teams-webinar-usage-report.md @@ -18,7 +18,7 @@ appliesto: --- # Microsoft Teams webinar usage report -**APPLIES TO:** ✖️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls The Teams webinar usage report in the Microsoft Teams admin center shows you the activity overview for webinars created in your organization. As an admin, you can view usage information, including the event title, event ID, start time, end time, event access type, and the names of the organizers, presenters, and co-organizers for each event. You can also gain insight into usage trends and see who in your organization schedules and produces webinars. diff --git a/Teams/teams-analytics-and-reports/walkie-talkie-usage-report.md b/Teams/teams-analytics-and-reports/walkie-talkie-usage-report.md index b86d650151..aa03cd3975 100644 --- a/Teams/teams-analytics-and-reports/walkie-talkie-usage-report.md +++ b/Teams/teams-analytics-and-reports/walkie-talkie-usage-report.md @@ -7,7 +7,7 @@ audience: admin ms.topic: conceptual ms.service: microsoft-365-frontline ms.reviewer: yinchang -ms.date: 10/13/2023 +ms.date: 10/07/2024 f1.keywords: - NOCSH ms.localizationpriority: high @@ -57,9 +57,9 @@ The report gives you a breakdown of each transmission made during the date range |NotifiedParticipants|The participants to which a push notification is sent when a transmission starts. In scenarios where the connection between the device and service is lost, a notification is sent to the device to re-establish the connection as soon as possible because a transmission is coming.| |AudioDurationMilliseconds|Duration of the transmission in milliseconds.| |ConnectionId|ID of each connection to a Walkie Talkie channel established by the device.| -|TransmissionStartTime |Date and time when the first audio packet is received by the service.| -|TransmissionEndTime|Date and time when the last audio packet is received by the service.| -|ParticipantList|A semi-colon delimited list of IDs of the devices connected to the channel at the time the transmission is sent.| +|TransmissionStartTime |Date and time, in Coordinated Universal Time (UTC), when the first audio packet is received by the service. The format is YYYY-MM-DDTHH:MM:SS. For example, 2024-10-08T20:49:03.| +|TransmissionEndTime|Date and time, in Coordinated Universal Time (UTC), when the last audio packet is received by the service. The format is YYYY-MM-DDTHH:MM:SS. For example, 2024-10-08T20:49:05.| +|ParticipantList|A semi-colon delimited list of IDs of the devices connected to the channel at the time the transmission ends.| |CallTimedOut|Whether the transmission exceeded the duration limit. This is a Boolean value.| |Platform|Device operating system.| |ParticipantType|Whether the participant was the transmitter or a receiver of the transmission.| @@ -67,6 +67,24 @@ The report gives you a breakdown of each transmission made during the date range |AppVersion|Version of the Teams app installed on the device.| |ClientCallStatus |Indicates if the device was able to receive the transmission without any issue.| +### Use the report to identify and investigate issues + +#### Missing audio transmissions + +1. **Locate the ParticipantList column**. Go to the **ParticipantList** column in the report, which lists the participants for each conversation ID. This list contains the device ID for each participant of the conversation. +1. **Count the participants**. Make sure the number of participants in the participant list matches the number of rows for that conversation ID. +1. **Check for mismatches**. If the numbers don’t match, it indicates missing transmissions. +1. **Identify the missing participants**. To find out which participants missed the transmission, compare the participant IDs in the list with the rows present. +1. **Backtrack to the user ID**. Use the participant ID to backtrack and identify the specific user who missed the transmission. + +#### Audio quality issues + +1. **Identify client call status**. Go to the **ClientCallStatus** column in the report and check the client call status. + - A status of FAILURE indicates an issue with the transmission. The issue could be due to network glitches, degraded audio quality, or other technical problems. + - A status of ABANDONED means that the device received the transmission but didn’t reproduce it. This could be because the device was in Do Not Disturb mode or already engaged in another call. +1. **Analyze failure reasons**. Understand that a FAILURE status means the service was able to ping the device, but the device didn’t respond correctly. This could be due to network issues or device problems. +1. **Review specific failures**. Investigate specific failure cases such as network issues, incoming call in progress errors, or mismatched channel IDs. These can provide insights into the nature of the audio quality issues. + ## Related articles - [Manage the Walkie Talkie app in Teams](../walkie-talkie.md) diff --git a/Teams/teams-app-permission-policies.md b/Teams/teams-app-permission-policies.md index 8a47ebcc63..d60e0d917b 100644 --- a/Teams/teams-app-permission-policies.md +++ b/Teams/teams-app-permission-policies.md @@ -8,7 +8,7 @@ ms.tgt.pltfrm: cloud ms.service: msteams ms.subservice: teams-apps audience: Admin -ms.date: 09/03/2024 +ms.date: 11/13/2024 ms.reviewer: mhayrapetyan ms.collection: - M365-collaboration @@ -35,18 +35,25 @@ ms.custom: As an admin, you can use app permission policies to control the apps that are available to each user in your organization. The permissions you set to allow or block all apps or specific apps are applicable to all [types of apps in Teams](apps-in-teams.md). To understand policies, see [app permission policies](app-policies.md). You must be a Teams Administrator or have a higher role to manage these policies. -To allow an app, you must allow it in [Org-wide app settings](manage-apps.md#manage-org-wide-app-settings), [individual app's setting](manage-apps.md#allow-or-block-apps), and app permission policy. While the first two settings just allow an app for use in your organization, the permission policies allow you to control which users can use a specific app. You control the access on a per-user and per-app basis by creating and applying the policy to specific users. +To let your org users use a Teams app or a copilot agent, you must allow it in: + +* [Org-wide app settings](manage-apps.md#manage-org-wide-app-settings). +* [Individual app's setting](manage-apps.md#allow-or-block-apps). +* In app permission policy. +* In Teams admin center and Microsoft 365 admin center. + +The first two settings just allow an app for use in your organization, the permission policies lets you to control which users can use a specific app. You control the access on a per-user and per-app basis by creating and applying the policy to specific users. To make any apps or copilot agents available in your organization, ensure that the settings to allow these are the same in Teams admin center and in [Microsoft 365 admin center](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps) in the Integrated Apps page. Teams admin center lets you create two types of permissions policies: -* **Global (Org-wide default)** policy exists by default and applies to all users. Any changes made to this policy affect all users as this policy is applied to all users by default. -* An admin-created policy applies only to the users that it's applied to. Create a new policy to allow apps for specific users. +* **Global (Org-wide default)** policy exists by default and applies to all users. Any changes made to this policy affect all users. +* **Custom policy** apply only to those users that you apply it to. You create and use custom policies to allow apps to specific users. - :::image type="content" source="media/app-permission-policy-trimmed.png" alt-text="Screenshot showing a new app permission policy being created."::: + :::image type="content" source="media/app-permission-policy-trimmed.png" alt-text="Screenshot showing custom and default app permission policies."::: If your organization is already on Teams, the app settings you configured in **Tenant-wide settings** in the Microsoft 365 admin center are reflected in **Org-wide app settings** on the [Manage apps](https://admin.teams.microsoft.com/policies/manage-apps) page in Teams admin center. If you're new to Teams and just getting started, by default, all apps are allowed in the org-wide global setting. It includes apps published by Microsoft, third-party software providers, and your organization. -Alternately, you can use [app centric management](app-centric-management.md) to configure the access to apps on a per-app basis. It offers an easier method to configure access to apps. The app centric management functionality replaces app permissions policies by making it easier for admins to specify the users and group in their organization who can add or install Teams apps on a per-app basis. You can use only one method to define access to apps in your organization. If you choose to, you can migrate from app permission policies to app centric management using our migration UI. +Alternately, you can use [app centric management](app-centric-management.md) to configure the access to apps on a per-app basis. It offers an easier method to configure access to apps. The app centric management functionality replaces app permissions policies. The feature makes it easier for you to specify the users in their organization who can add or install Teams apps on a per-app basis. You can use only one method to define access to apps in your organization. If you choose to, you can migrate from app permission policies to app centric management using our migration UI. > [!NOTE] > To know about third-party app settings in Microsoft 365 Government Community Cloud High (GCCH) and Department of Defense (DoD) environment, see [Manage org-wide app settings for Microsoft 365 Government](manage-apps.md#manage-org-wide-app-settings-for-microsoft-365-government). @@ -60,10 +67,10 @@ Use one or more custom app permission policies, if you want to control the apps 1. Provide a name and description for the policy. 1. Under **Microsoft apps**, **Third-party apps**, and **Custom apps**, select one of the following options: - * Allow all apps - * Allow specific apps and block all others - * Block specific apps and allow all others - * Block all apps + * Allow all apps or copilot agents + * Allow specific apps or copilot agents and block all others + * Block specific apps or copilot agents and allow all others + * Block all apps or copilot agents 1. If you selected **Allow specific apps and block all others**, add the apps that you want to allow: diff --git a/Teams/teams-app-setup-policies.md b/Teams/teams-app-setup-policies.md index b9b12cb64e..d64bfc1a92 100644 --- a/Teams/teams-app-setup-policies.md +++ b/Teams/teams-app-setup-policies.md @@ -8,7 +8,7 @@ ms.tgt.pltfrm: cloud ms.subservice: teams-apps ms.service: msteams audience: Admin -ms.date: 07/31/2024 +ms.date: 11/05/2024 ms.reviewer: mhayrapetyan ms.collection: - M365-collaboration @@ -39,6 +39,9 @@ The following built-in app setup policies are available in the Microsoft Teams a * **FirstlineWorker**: This policy is for Frontline Worker. The policy can't be customized. You can assign it to Frontline Workers in your organization. +> [!NOTE] +> The user pinning setting is available in the Teams admin center in Microsoft 365 Commercial, GCC, GCC High, and DoD environments. + ## Pin apps Using app pinning functionality, you can highlight apps that users need the most; make such apps available for users instantly; and make it available in the use's context. App pinning promotes ease of access and improves app adoption in your organization. Admins can pin apps and they can allow users to pin apps. If an admin pins an app, the app is added and pinned in the Teams client of the allowed users only. Pinning respects other governance controls and apps aren't available to users who aren't allowed to use the app. @@ -189,8 +192,6 @@ When you unassign policies in bulk, you're removing policy assignments that were * Admin pins always take precedence. If the user pinning option is turned on, then apps pinned by the users display below the apps pinned by the admins. If the user pinning option is turned off, then the users lose existing pins and only the apps pinned by the admins are available in the app bar. -* The user pinning setting is available in the Teams admin center in Microsoft 365 Government Community Cloud (GCC) environments (GCC, GCC High, and DoD), but it has no effect. - * There's no limit on the maximum number of pinned apps that you can add to a policy. However, at least two apps must be pinned to the Teams mobile client (iOS and Android). If a policy has fewer than two apps, the mobile client doesn't reflect the policy settings. Instead, the mobile client continues to use the existing configuration. * After you edit or assign a policy, it can take a few hours for changes to take effect. Also, the rollback takes a few hours to take effect if you choose to roll back the policy application. diff --git a/Teams/teams-classic-client-end-of-availability.md b/Teams/teams-classic-client-end-of-availability.md index c90017c2e9..f10a5d82cb 100644 --- a/Teams/teams-classic-client-end-of-availability.md +++ b/Teams/teams-classic-client-end-of-availability.md @@ -164,6 +164,4 @@ In the Teams admin center: - In mid-May, any users remaining on classic Teams will be switched to new Teams, and the toggle to return to classic Teams won't be available. We'll attempt to uninstall classic Teams after a period of time. > [!IMPORTANT] -> A rare issue with the uninstall of classic Teams has been detected and to be cautious Microsoft has paused the automatic uninstallation of classic Teams for customers who haven't already completed this step. This issue could result in the Teams Meeting Addin in Outlook failing to schedule or join Teams meetings. We are actively investigating this issue and will update once it's resolved. If your users are experiencing this issue, a workaround is to use Teams to schedule or join meetings. -> -> For customers who are experiencing this issue or who wish to perform the uninstall of classic Teams themselves and experience this issue, there are troubleshooting steps available here: [Teams meeting add-in missing from Outlook and new Teams](/microsoftteams/troubleshoot/meetings/teams-meeting-add-in-missing). +> For customers who uninstall classic Teams themselves and experience a Teams meeting add-on issue, there are troubleshooting steps available here: [Teams meeting add-in missing from Outlook and new Teams](/microsoftteams/troubleshoot/meetings/teams-meeting-add-in-missing). diff --git a/Teams/teams-client-uninstall-script.md b/Teams/teams-client-uninstall-script.md new file mode 100644 index 0000000000..4752962e30 --- /dev/null +++ b/Teams/teams-client-uninstall-script.md @@ -0,0 +1,50 @@ +--- +title: Uninstallation script for the classic Teams client +ms.author: heidip +author: MicrosoftHeidi +manager: jtremper +ms.topic: article +ms.date: 11/12/2024 +ms.service: msteams +audience: admin +ms.collection: +- M365-collaboration +- m365initiative-deployteams +ms.reviewer: asgupta +search.appverid: MET150 +f1.keywords: +- NOCSH +description: Documenting for a downloadable uninstall script for the classic Teams client which allows you to manually shut off and remove the classic Teams client after moving to the new Teams client on non-VDI devices. +appliesto: +- Microsoft Teams +ms.localizationpriority: medium +--- + +# Uninstall the classic Teams client using a script + +Microsoft has an [uninstallation script](https://download.microsoft.com/download/d/f/c/dfc1a7ce-e3da-4e12-94fc-bea60ba3d9ba/UninstallClassicTeams.ps1) designed to uninstall the classic Teams client from all user profiles found on devices in your organization. This script can be run on all devices apart from Virtualized Desktop Infrastructure (VDI). If the classic Teams client is running for any user on the machine at the time the script is run, this script also ends the existing classic Teams running instance. + +## Using the script + +### Running the script on a single device + +If you want to have the uninstallation script run for a single device, run it on that device [in administrative mode](/powershell/scripting/learn/ps101/01-getting-started#how-to-launch-powershell). After you run the script, the classic Teams client is uninstalled from all user profiles of the specified device. + +## Running the script with device management software + +If you need to have this uninstallation script run across all devices in your organization, run this script using device management software, like Intune. We have [sample instructions](https://github.com/microsoft/MDE-PowerBI-Templates/blob/master/ASR_scripts/AddShortcuts_with_Intune.md) for running the script in Intune. + +If the script is run in Intune or other device management software: + +- Admins get results in the form of .JSON that indicates different parameters, like how many instances of classic Teams there are, how many have been uninstalled from devices, and so on. +- Admins can download these results as a .CSV file. + +> [!NOTE] +> After the uninstallation of classic Teams, new Teams and Teams meeting add-in (TMA) might not work together. See [this article](/microsoftteams/troubleshoot/meetings/teams-meeting-add-in-missing#cause) for more information. + +### Teams meeting add-in issue resolution + +To address the TMA issue when it does occur, Microsoft has [an additional script](https://download.microsoft.com/download/d/f/c/dfc1a7ce-e3da-4e12-94fc-bea60ba3d9ba/DetectAndUninstallTMA.ps1) to resolve the issue. + +> [!NOTE] +> If the new Teams client is running and the TMA issue is detected by this script, it can't fix the issue. diff --git a/Teams/teams-client-update.md b/Teams/teams-client-update.md index 7f7d80ab3b..13831d20dd 100644 --- a/Teams/teams-client-update.md +++ b/Teams/teams-client-update.md @@ -9,59 +9,155 @@ audience: admin ms.collection: - M365-collaboration ms.reviewer: -ms.date: 06/28/2024 +ms.date: 10/14/2024 search.appverid: MET150 f1.keywords: - NOCSH -description: This article outlines the process behind updating the classic Microsoft Teams desktop client. +description: This article outlines the process behind updating the Microsoft Teams desktop client. ms.localizationpriority: Medium appliesto: - Microsoft Teams ms.custom: seo-marvel-apr2020 --- -# Classic Teams update process +# Why it's important to keep Teams updated. -Teams web app updates are typically released on the fourth Monday of each month. +> [!IMPORTANT] +> This article contains information for the new Teams client. The classic Teams client has ended support, and is no longer receiving updates. -Teams desktop client updates are released monthly after rigorous internal testing and validation through our Technology Adoption Program (TAP). Desktop client updates typically start on the fourth Monday of the month and are rolled out gradually to customers throughout the remainder of the week. If a critical update is required, Teams bypasses this schedule and releases the update as soon as it’s available. - -The desktop client updates itself automatically. Teams checks for updates every few hours behind the scenes, downloads it, and then waits for the computer to be idle before silently installing the update. - -Users can also manually download updates by selecting **Check for updates** in the **...** drop-down menu next to your **Profile** icon in the top right of the app. If an update is available, it's downloaded and silently installed when the computer is idle. - -## What can I do if classic Teams desktop client remains outdated? - -These are a few reasons your classic Teams client remain outdated (major version below 1.7): - - The update packages can't be downloaded. To address this, make sure the following domains can be accessed from the user's machine: - - statics.teams.microsoft.com - - statics.teams.cdn.office.net - - Multiple users are sharing the machine and new users are logging in frequently (eg., a Kiosk machine) - - Classic Teams is installed into a non-updatable location such as ProgramData or Program Files - -If you're an admin and multiple users in your organization have remained on an older version of classic Teams client, your users aren't able to automatically move to new Teams. To resolve this, you can use the admin-provision tool TeamsBootstrapper.exe to remove classic Teams as well as to provision the new client. Please see next section to learn more. - -## Can admins deploy updates instead of Teams auto-updating? - -Admins can quickly move users to new Teams via the provision tool TeamsBootstrapper.exe with the -u argument. To learn more, please see the following article: [Bulk upgrade to the new Microsoft Teams client](new-teams-bulk-install-client.md). - -You can use the [Microsoft Teams new client usage report](new-teams-usage-report.md) to find out if the users in your organization are using an outdated classic Teams client. - -## What about updates to Microsoft 365 Apps for enterprise? -Teams can be installed with new installations of Microsoft 365 Apps for enterprise as described in [Deploy Microsoft Teams with Microsoft 365 Apps for enterprise](/DeployOffice/teams-install). - -Teams follows its own update process as outlined earlier in this article. Teams doesn't follow the update process for the other Offices apps, such as Word and Excel. +Keeping Microsoft Teams up-to-date is crucial for maximizing productivity and staying connected. Regular updates mean you have access to the latest features, security enhancements, and bug fixes. Updating not only improves the overall performance and reliability of the application, it also helps you and your team collaborate more efficiently. By staying current with updates, you reduce the risk of having issues and ensure compatibility with other tools, making it easier to focus on your work without interruptions. ## Servicing agreement -As part of a modern online service, the Teams client is updated once per month. The client automatically installs updates when they become available to that client. Because we stagger the availability of updates worldwide, some clients in your organization might receive new updates before others. Because Teams is governed by the Modern Lifecycle Policy, it's expected that users remain on the most up-to-date version of the desktop client. Auto-updates ensure that users have the latest capabilities, performance enhancements, security, and service reliability. - -To identify when desktop clients fall out of date, an in-app alert is displayed if the user’s current version is between one and three months old, and if there's a new version available. This in-app messaging encourages users to update to the latest version of Teams or, if necessary, to reach out to their IT admin to do so. Users on Teams desktop clients that are more than three months old will see a blocking page. This page gives the options to update now, reach out to their IT admin, or continue to Teams on the web. - -Teams desktop clients on Government Clouds currently have an exception to this servicing agreement until further notice. - -For information on new version releases, check [Message Center](https://admin.microsoft.com/AdminPortal/Home#/MessageCenter) or go to **Help** > **What’s new** in the client. - -## What about updates to Teams on VDI? - -Teams clients on Virtual Desktop Infrastructure (VDI) aren't automatically updated the way that non-VDI Teams clients are. You have to update the VM image by installing a new MSI as described in the instructions to [Install Teams on VDI](teams-for-vdi.md). You must uninstall the current version to update to a newer version. +As part of a modern online service, the Teams client is updated twice a month. The client automatically installs updates when they become available to that client. Because we stagger the availability of updates worldwide, some clients in your organization might receive new updates before others. Because Teams is governed by the Modern Lifecycle Policy, it's expected that users remain on the most up-to-date version of the desktop client. Auto-updates ensure that users have the latest capabilities, performance enhancements, security, and service reliability. + +To identify when desktop clients fall out of date, an in-app alert is displayed if the user's current version is between one and three months old, and if there's a new version available. This in-app messaging encourages users to update to the latest version of Teams or, if necessary, to reach out to their IT admin to do so. Users on Teams desktop clients that are more than three months old will see a blocking page. This page gives the options to update now, reach out to their IT admin, or continue to Teams on the web. + +For information on new version releases, check [Message Center](https://admin.microsoft.com/AdminPortal/Home#/MessageCenter) or go to **Help** > **What's new** in the client. + +## Teams client updates timeline + +New updates for the Teams desktop client are released twice a month after thorough internal testing and validation through our Technology Adoption Program (TAP). The desktop client is rolled out to customers gradually. + +> [!IMPORTANT] +> When there's a critical update, Teams bypasses the regular schedule and releases the update immediately. + +Other factors that help your client to stay up-to-date: + +- Operating System (OS): + - Meets the minimum OS requirements for Teams. + - Your OS version is up-to-date (non-LTSC update channel) and still under support. + - Your OS has the latest patches installed. +- Webview2: + - Webview2 updates automatically on Windows, you should make sure it isn't blocked. Webview2 is updated by Teams on macOS. + - Webview2 must be a supported version (latest version). + +For more information, see [Teams client system requirements](teams-client-system-requirements.md). + +## Updating Teams on Windows devices + +- **Update checks**: Teams applications on both Windows and Mac devices check for updates when the application starts up and every few hours in the background, whether the application is running or not. A user must be signed into the machine for updates to happen. +- **Download**: Updates are downloaded based on availability and staged to the user session. By using Windows Delivery Optimization, only the delta that's different from the current installed version (the differential update) is downloaded. +- **Restart**: Restarting the application is required for the update to take effect. +- **Manual**: The update starts automatically when the application is idle on Windows clients. A user can choose to restart sooner by selecting the **Restart** button next to the ellipsis (...) button in the client. + +### Issues with Teams client updates in Windows and best practices + +- Windows delivery optimization service is disabled or configured with unsupported mode (100). This blocks the updater's ability to download the update payload. + - There's a Windows Delivery Optimization service configuration requirement: [Upgrade to the new Teams client using policies](new-teams-deploy-using-policies.md). + - Enabling the Peer to Peer capability isn't required. +- Team's app package is modified by a user. The MSIX packages are installed machine-wide under the Program Files directory. The file ACLs are tightly controlled and monitored by the Windows OS. If the file ACLs are modified or changed by a user, the system deems the application to be in a corrupted state. This leads to unexpected behaviors such as crashing, unexpected app termination, and a failure to update. + - It's essential to make sure the files under the installation directory (%programfiles%\windowsapps) aren't altered in any way. +- Network settings that block Team's CDN endpoints cause delivery optimization service failures and a failure to update the app. + - You must allow Microsoft M365 endpoints in network configuration. For more information, see [Microsoft 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges). + - Avoid SSL inspection on M365 endpoints. SSL inspection is known to cause high update download failure rate and retries. +- Running on an out of support OS, or a Windows version that doesn't have the latest updates and patches can lower the success of Teams updates. + - Windows 11 improves the Teams application update success rate and reliability as it has the most current installer. + - Make sure you install all OS patches before deploying Teams on Windows 10 or Windows 11. + +## Updating Teams on Mac devices + +- The Teams desktop client updates itself using Microsoft AutoUpdate (MAU), similar to other Microsoft applications. Learn more about MAU at [Configuring Microsoft AutoUpdate (MAU) for Organization Specific Updates](/microsoft-365-apps/mac/mau-configure-organization-specific-updates). +- Teams uses default MAU Office channels for updates and a custom channel for Teams-specific scenarios. The post-installation script registers the app with MAU's default Office channel (Current, Preview, or Beta) to ensure the app can be updated by MAU without running itself. +- When the update is downloaded while Teams is running, we leverage MAU's **Install On Clone** feature, to prepare the installation. Once a user quits the application, MAU finishes updates by moving the clone to the /Applications folder. Teams for Mac doesn't automatically restart to apply updates. It always waits for user to take the action. +- Users can also manually check for updates by selecting **Check for updates** from the Help menu bar item. This action opens Microsoft AutoUpdate (MAU). + +### How to configure MAU + +- No special configuration is required if the MAU preferences are left at default values. +- If your organization employs managed MAU preferences, the Teams app preferences should look like this: + +```xml +/Applications/Microsoft Teams.app +     +      Application ID +      TEAMS21 +     +``` + +> [!NOTE] +> Your configuration may contain an LCID key with a value set to 1033. This value isn't used any longer, and you can delete it. + +### Issues with Mac update and best practices + +- Microsoft AutoUpdate (MAU) not being installed or being blocked on your device. + - Since MAU is an integral part of New Teams, it's included with the Teams installer. When Teams is first installed, MAU is also installed unless it's already present on the device. However, there have been instances where MAU has been deliberately removed or blocked by firewalls. + - To see if you have MAU installed, select **Check for Updates** from the Help menu bar item. This should open the MAU user interface, but if MAU isn't installed, nothing happens. + - To make sure that MAU is allowed to function correctly, we need to first [check the MAU configuration](#how-to-troubleshoot-a-mau-configuration). If the configuration is correct and [MAU is installed](#how-to-configure-mau), and it still doesn't work, it's likely being blocked. In that case, the user should contact their administrator. +- MAU is outdated. + - Microsoft Teams needs MAU version 4.52.22101101 at a minimum, but it's strongly recommended to use version 4.73.24071426 or higher for crucial security updates. MAU self-updates, and a manual update should not be required under the default settings. +- Your organization uses a custom MAU profile and the Teams portion isn't configured correctly. + - As previously mentioned, Teams handles MAU registration autonomously within user preferences. There are instances when an organization deploys custom MAU preferences using an MDM management system. In such cases, the managed preferences take precedence. Occasionally, these settings might be incorrectly configured. Common issues include a complete lack of Teams configuration, outdated configurations for Classic Teams, or configurations that reference the old name **Microsoft Teams (work or school).app**. + +### How to troubleshoot a MAU configuration + +- To troubleshoot MAU configuration issues, you first need to open the Terminal app and execute the following commands: + + - ` defaults read /Library/Managed\ Preferences/com.microsoft.autoupdate2` + - ` defaults read com.microsoft.autoupdate2 ` + +- In the output, locate the "/Applications/Microsoft Teams.app". It should look like: + - Basic: +```xml +Applications= { + ... + "/Applications/Microsoft Teams.app" = { + "Application ID" = TEAMS21; + }; + ... + } +``` + - Custom channel: +```xml +Applications= { + ... + "/Applications/Microsoft Teams.app" = { + "Application ID" = TEAMS21; + ChannelName = Custom; + ManifestServer = "https://statics.teams.cdn.office.net/production-osx/24199.1700.3003.1785/"; + ManifestServerExpiryTime = "2024-08-02T08:40:06Z"; + }; + ... + } +``` + +> [!NOTE] +> Preferences in /Library/Managed\ Preferences/ take precedence. If you see an "Applications" entry there, focus solely on that output. + +- If the "/Application/Microsoft Teams.app" path is absent, it indicates that the Teams registration is missing, and you need to reach out to your administrator to add the basic registration to the managed preferences profile. + +- If the "/Application/Microsoft Teams.app" entry appears but is different from the examples, contact your administrator to resolve the managed preferences profile. + +#### Common misconfigurations + +|Issue |Example | +|--------------------------------------|---------| +|Classic Teams configuration |"/Applications/Microsoft Teams.app" = {
    "Application ID" = **TEAMS10;**
    } | +|New Teams configuration with old name |"/Applications/Microsoft Teams **(work or school).app**"
    = {
    "Application ID" = **TEAMS21**;
    } | +|Serving multiple configurations |"/Applications/**Microsoft Teams.app**" = {
    "Application ID" = **TEAMS10**;;
    }
    "/Applications/**Microsoft Teams.app**" = {
    "Application ID" = **TEAMS21**;
    } | + +- A special case might happen when the registration is correct, but your application is still called **Microsoft Teams (work or school).app**. When this case happens, you need to manually download and install the [latest version of Teams](https://aka.ms/getteams). If someone don't have permission to install software, contact an administrator to perform the installation. After the installation is done, you'll continue to receive updates automatically. + +## Updates to Teams on VDI + +See [Install Teams on VDI](teams-for-vdi.md). diff --git a/Teams/teams-contact-center.md b/Teams/teams-contact-center.md index aea85063f8..6440098f3e 100644 --- a/Teams/teams-contact-center.md +++ b/Teams/teams-contact-center.md @@ -62,6 +62,7 @@ The following providers offer contact center solutions that are integrated into | `Avaya` | https://www.avaya.com/en/enterprise-cloud/ | | `Bright Pattern` | https://www.brightpattern.com/ | | `CentrePal` | https://www.centrepal.com/ | +| `Cirrus` | https://www.cirrusresponse.com/cloud-contact-centre/microsoft-teams/ | | `Cisco` | https://www.cisco.com/c/en/us/products/contact-center/webex-contact-center/index.html | | `Competella` | https://www.competella.com/microsoft-teams-skype-for-business | | `ComputerTalk` | https://www.computer-talk.com/product/enterprise-contact-center/ice-contact-center-for-teams | @@ -93,7 +94,6 @@ The following providers offer contact center solutions that are integrated into | Solution Provider | Solution website | | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Cirrus` | https://www.cirrusresponse.com/cloud-contact-centre/microsoft-teams/ | | `Evolve IP` | https://www.evolveip.net/contact-center | | `FrontStage` | https://www.frontstage.cc | | `Geomant` | https://www.geomant.com/buzzeasy-contact-centre-for-microsoft-teams | diff --git a/Teams/teams-encoder-setup.md b/Teams/teams-encoder-setup.md index 4905439b6d..b44769b515 100644 --- a/Teams/teams-encoder-setup.md +++ b/Teams/teams-encoder-setup.md @@ -27,7 +27,7 @@ ms.custom: > [!NOTE] > We're currently still supporting live events. While we still recommend you to upgrade to [Teams town halls](plan-town-halls.md) to take advantage of new features and experiences, your users can continue to schedule events. For more information, see [Updates for Town Hall in Microsoft Teams and Teams Live Events](https://techcommunity.microsoft.com/t5/microsoft-teams-blog/extension-for-teams-live-events-retirement/ba-p/4148352). -**APPLIES TO:** ✔️Meetings ✖️Webinars ✔️Town halls ✔️Live events +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Live events Video encoders allow users to produce Microsoft Teams live events via external hardware or software-based solutions. @@ -49,23 +49,23 @@ Microsoft validated the video encoders for live streaming with Teams in the foll |Encoder |Website |Encoder Type|Native Caption Support| |---------------------------------------|---------|---------|---------| -|AJA HELO Plus |[AJA HELO Plus](https://www.aja.com/products/helo-plus) |Hardware|✔️| -|AWS Elemental Live |[AWS Elemental Live](https://aws.amazon.com/elemental-live/) |Hardware|✔️| -|Blackmagic Web Presenter HD |[Blackmagic Web Presenter](https://www.blackmagicdesign.com/products/blackmagicwebpresenter) |Hardware|✔️| +|AJA HELO Plus |[AJA HELO Plus](https://www.aja.com/products/helo-plus) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|AWS Elemental Live |[AWS Elemental Live](https://aws.amazon.com/elemental-live/) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Blackmagic Web Presenter HD |[Blackmagic Web Presenter](https://www.blackmagicdesign.com/products/blackmagicwebpresenter) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |Blackmagic ATEM Mini with streaming engine |[Blackmagic ATEM Mini with streaming engine](https://www.blackmagicdesign.com/products/atemmini) |Hardware|| |BrandLive |[BrandLive](https://www.brandlive.com/) |Service|| |Epiphan video Pearl Nano |[Epiphan video Pearl Nano](https://www.epiphan.com/products/pearl-nano/) |Hardware|| -|FFmpeg |[FFmpeg](https://ffmpeg.org/) |Software|✔️| -|Haivision |[Haivision Makito X4](https://www.haivision.com/microsoft/stream) |Hardware|✔️| +|FFmpeg |[FFmpeg](https://ffmpeg.org/) |Software|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Haivision |[Haivision Makito X4](https://www.haivision.com/microsoft/stream) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |Live Arena AI Producer |[Live Arena AI Producer](https://www.livearena.com/) |Service|| -|Magewell Ultra Encode AIO |[Magewell Ultra Encode AIO](https://www.magewell.com/ultra-encode-aio) |Hardware|✔️| -|Matrox Monarch EDGE Series |[Matrox Monarch EDGE Series](https://video.matrox.com/en/products/encoders-decoders/monarch-edge-series) |Hardware|✔️*| +|Magewell Ultra Encode AIO |[Magewell Ultra Encode AIO](https://www.magewell.com/ultra-encode-aio) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| +|Matrox Monarch EDGE Series |[Matrox Monarch EDGE Series](https://video.matrox.com/en/products/encoders-decoders/monarch-edge-series) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)*| |Newtek TriCaster 2 Elite |[Newtek TriCaster 2 Elite](https://www.vizrt.com/products/tricaster/tricaster-2-elite/) |Hardware|| |Open Broadcaster Software (OBS Studio) |[Open Broadcaster Software](https://obsproject.com/) |Software|| |Socialive |[Socialive](https://socialive.us/) |Service|| |StreamYard |[StreamYard](https://streamyard.com/) |Service|| |Telestream Wirecast |[Telestream Wirecast](https://www.telestream.net/wirecast/overview.htm) |Software|| -|Teradek Prism Flex |[Teradek Prism Flex](https://teradek.com/pages/prism) |Hardware|✔️| +|Teradek Prism Flex |[Teradek Prism Flex](https://teradek.com/pages/prism) |Hardware|![Image of a checkmark for yes](/office/media/icons/success-teams.png)| |vMix |[vMix](https://www.vmix.com/) |Software|| |XSplit Broadcaster |[XSplit Broadcaster](https://www.xsplit.com/) |Software|| diff --git a/Teams/teams-for-vdi.md b/Teams/teams-for-vdi.md index 624ce5338b..b030e87c0a 100644 --- a/Teams/teams-for-vdi.md +++ b/Teams/teams-for-vdi.md @@ -6,7 +6,7 @@ manager: jtremper ms.topic: article ms.service: msteams ms.reviewer: amitsri -ms.date: 10/13/2023 +ms.date: 10/30/2024 audience: admin description: Learn how to run classic Microsoft Teams in a Virtualized Desktop Infrastructure (VDI) environment. ms.localizationpriority: medium @@ -23,6 +23,9 @@ appliesto: # Classic Teams for Virtualized Desktop Infrastructure +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + >[!Important] >This article describes the requirements and limitations of using classic Microsoft Teams in a virtualized environment. > @@ -30,7 +33,7 @@ appliesto: ## What is VDI? -Virtual Desktop Infrastructure (VDI) is virtualization technology that hosts a desktop operating system and applications on a centralized server in a data center. This enables a complete, and personalized, desktop experience for users with a fully secured and compliant centralized source. +Virtual Desktop Infrastructure (VDI) is virtualization technology that hosts a desktop operating system and applications on a centralized server in a data center. VDI enables a complete, and personalized, desktop experience for users with a fully secured and compliant centralized source. Teams in a virtualized environment supports chat and collaboration. And with the Azure Virtual Desktop, Citrix, and VMware platforms, calling and meeting functionality is also supported. @@ -50,7 +53,7 @@ Using Teams in a virtualized environment requires the following components. - **Virtualization broker**: The resource and connection manager to the virtualization provider, such as Azure. - **Virtual desktop**: The Virtual Machine (VM) stack that runs Teams. - **Thin client**: The device that the user physically interfaces with. -- **Teams desktop app**: The Teams desktop client app in the VM. This can be divided into three major sub-components: +- **Teams desktop app**: The Teams desktop client app in the VM. This component can be divided into three major sub-components: - Desktop client: Win32 native app, installed via .exe (auto update enabled) or .msi (auto update disabled). *Version Example: 1.6.00.18681* - Web client: a common component for both Teams native desktop app and web (browser) app, it auto updates every time the app starts (even in non-persistent environments). *Version Example: 1.0.0.2023052414.* - Shim: a VDI and VDI partner specific component that is bundled with the Web client, hence it auto updates. *Version Example: 1.14.0.1 (Citrix), 21494295 (VMware), 1.1.2206.13001 (Azure Virtual Desktop/W365)* @@ -112,7 +115,7 @@ You can deploy the Teams desktop app for VDI using a per-machine installation or For a dedicated persistent setup, both per-machine and per-user installation will work. However, for a non-persistent setup, Teams requires a per-machine installation in order to work efficiently. See the [Non-persistent setup](#non-persistent-setup) section. -With per-machine installation, automatic updates are disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates are enabled. +With per-machine installation, automatic updates are disabled. To update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates are enabled. > [!IMPORTANT] > Keep the Teams desktop app in your VDI environment up to date. Teams desktop app versions with release dates that are more than 90 days older than the [current version's release date](/officeupdates/teams-app-versioning) aren't supported. Unsupported Teams desktop app versions show a blocking page to users and request that they update their app. @@ -140,7 +143,7 @@ The following is the recommended minimum VM configuration. In a non-persistent setup, users' local operating system changes are not retained after users log off. Such setups are commonly shared multi-user sessions. VM configuration varies based on the number of users and available physical server resources. -For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image. This ensures an efficient launch of the Teams app during a user session. To learn more, see the [Install or update the Teams desktop app on VDI](#install-or-update-the-teams-desktop-app-on-vdi) section. +For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image, which ensures an efficient launch of the Teams app during a user session. To learn more, see the [Install or update the Teams desktop app on VDI](#install-or-update-the-teams-desktop-app-on-vdi) section. Using Teams in a non-persistent setup also requires a profile-caching manager for efficient Teams runtime data synchronization. Efficient data synchronization ensures that the appropriate user-specific information (such as a user's data, profile, or settings) is cached during the user's session. Make sure data in these two folders are synced: @@ -148,7 +151,7 @@ Using Teams in a non-persistent setup also requires a profile-caching manager fo - `C:\Users\username\AppData\Roaming\Microsoft\Teams (%AppData%\Microsoft\Teams)` > [!NOTE] -> A roaming folder (or, if you are using folder redirection, a caching manager) is required to ensure that the Teams app has the runtime data and files required to run the application. This is necessary to mitigate network latency issues or network glitches, which would otherwise cause application errors and a slow experience due to unavailable data and files. +> A roaming folder (or, if you are using folder redirection, a caching manager) is required to ensure that the Teams app has the runtime data and files required to run the application. This folder is necessary to mitigate network latency issues or network glitches, which would otherwise cause application errors and a slow experience due to unavailable data and files. There are a variety of caching manager solutions available, such as [FSLogix](/fslogix/overview). Consult your caching manager provider for specific configuration instructions. @@ -252,7 +255,7 @@ In addition to chat and collaboration, Teams on VDI with calling and meetings is ![Diagram showing Teams on VDI architecture.](media/teams-on-vdi-architecture.png) > [!IMPORTANT] -> If you currently run Teams without AV optimization in VDI and you use features that are not supported yet for optimization (such as Give and take control when app sharing), you have to set virtualization provider policies to turn off Teams redirection. This means that Teams media sessions won't be optimized. For steps on how to set policies to turn off Teams redirection, contact your virtualization provider. +> If you currently run Teams without AV optimization in VDI and you use features that are not supported yet for optimization (such as Give and take control when app sharing), you have to set virtualization provider policies to turn off Teams redirection. Which means that Teams media sessions won't be optimized. For steps on how to set policies to turn off Teams redirection, contact your virtualization provider. ### Network requirements @@ -421,7 +424,7 @@ Teams VDI policies are available in the Teams module. These policies are active - `Set-CsTeamsVdiPolicy` > [!NOTE] -> This is only for non-optimized environments. +> This policy is only for non-optimized environments. ### Connect to Microsoft Teams PowerShell @@ -442,7 +445,7 @@ When users whose VDI `DisableCallsAndMeetings` policy is set to `$true` sign int All types of calling should be disabled. > [!NOTE] -> This is only for non-optimized environments. +> This policy is only for non-optimized environments. ```PowerShell New-CsTeamsVdiPolicy -Identity DisableCallsAndMeetingsTrue -DisableCallsAndMeetings $true -DisableAudioVideoInCallsAndMeetings $false @@ -465,7 +468,7 @@ When users whose VDI `DisableAudioVideoInCallsAndMeetings` policy is set to `$tr - Can't hold person-to-person audio and video calls from VDI. > [!NOTE] -> This is only for non-optimized environments. +> This policy is only for non-optimized environments. ```powershell $PolName = "DisableCallsAndMeetingsAV" @@ -499,7 +502,7 @@ if($cleanup){ - In Citrix persistent VDI environments where Teams was installed using the .exe, if the user disconnects from the Virtual Machine while Teams is running, Teams auto-updates can result in the user being in a non-optimized state for Audio/Video when they reconnect to their sessions. We recommend that users quit Teams before they disconnect from Citrix Virtual Desktops to avoid this scenario. This behavior is fixed in Teams 1.6.00.12455. - Teams should be deployed either per user or per machine. Deployment of Teams for concurrent per user and per machine is not supported. To migrate from either per machine or per user to one of these modes, follow the uninstall procedure and redeploy to either mode. - In Citrix Remote PC environments users might not be optimized if they roam between the office and home. -For example, a user launching Microsoft Teams from the office (i.e. connected to the device locally via console) that later locks the device and reconnects to the Windows session via HDX will not be optimized. This requires a Microsoft Teams restart to properly detect the new state. This can be prevented by deploying the following registry key on the Remote PC: +For example, a user launching Microsoft Teams from the office (i.e. connected to the device locally via console) that later locks the device and reconnects to the Windows session via HDX will not be optimized. This circumstance requires a Microsoft Teams restart to properly detect the new state. This circumstance can be prevented by deploying the following registry key on the Remote PC: HKLM/Software/Microsoft/Teams Name: VDIOptimizationMode @@ -553,7 +556,7 @@ The following are known issues and limitations for calling and meetings: #### Teams crashes or the Teams sign in screen is blank -This is a known issue with Citrix VDA versions 1906 and 1909. To work around this issue, add the following registry `DWORD` value, and set it to `204` (hexadecimal): +This issue is a known issue with Citrix VDA versions 1906 and 1909. To work around this issue, add the following registry `DWORD` value, and set it to `204` (hexadecimal): HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\SfrHook\Teams.exe diff --git a/Teams/teams-memory-usage-perf.md b/Teams/teams-memory-usage-perf.md index 7c1985a6af..7e5e80f983 100644 --- a/Teams/teams-memory-usage-perf.md +++ b/Teams/teams-memory-usage-perf.md @@ -22,6 +22,9 @@ ms.custom: seo-marvel-jun2020 # How Microsoft Teams uses memory +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + Some Microsoft Teams users have questions about how Teams uses memory. This article describes how memory is used by Teams, and why the Teams desktop application (app) and the Teams web app do not prevent other apps and workloads on the same computer from having enough memory to run optimally. Teams is designed to use modern web technology. To achieve this, the Teams desktop client was developed on Electron, which uses Chromium for rendering. This is the same rendering engine behind many of today's most popular browsers, including Edge and Chrome. ## How Teams works diff --git a/Teams/teams-powershell-application-authentication.md b/Teams/teams-powershell-application-authentication.md index 63a164978e..6664827232 100644 --- a/Teams/teams-powershell-application-authentication.md +++ b/Teams/teams-powershell-application-authentication.md @@ -55,7 +55,7 @@ The following examples show how to use Teams PowerShell Module with the Microsof - Connect using Access Tokens: - Access Tokens can be retrieved via the login.microsoftonline.com endpoint. It requires two Access Tokens – “MS Graph” and “Skype and Teams Tenant Admin API” resources. + Access Tokens can be retrieved via the login.microsoftonline.com endpoint. It requires two Access Tokens – "MS Graph" and "Skype and Teams Tenant Admin API" resources. ```powershell $ClientSecret = "…" @@ -96,8 +96,9 @@ Sample steps for creating applications in Microsoft Entra ID are mentioned below 1. Register the application in Microsoft Entra ID. 2. Assign API permissions to the application. - - For \*-Cs cmdlets - the Microsoft Graph API permission needed is `Organization.Read.All`. - - For Non \*-Cs cmdlets - the Microsoft Graph API permissions needed are `Organization.Read.All`, `User.Read.All`, `Group.ReadWrite.All`, `AppCatalog.ReadWrite.All`, `TeamSettings.ReadWrite.All`, `Channel.Delete.All`, `ChannelSettings.ReadWrite.All`, `ChannelMember.ReadWrite.All`. + - For \*-Cs cmdlets - The Microsoft Graph API permission needed is `Organization.Read.All`. + - For Non \*-Cs cmdlets - The Microsoft Graph API permissions needed are `Organization.Read.All`, `User.Read.All`, `Group.ReadWrite.All`, `AppCatalog.ReadWrite.All`, `TeamSettings.ReadWrite.All`, `Channel.Delete.All`, `ChannelSettings.ReadWrite.All`, `ChannelMember.ReadWrite.All`. + - Note - There's no need to configure any API permission for "Skype and Teams Tenant Admin API". Configuring this permission might result in failures. 3. Generate a self-signed certificate. 4. Attach the certificate to the Microsoft Entra application. 5. Assign [Microsoft Entra roles](/microsoftteams/using-admin-roles#teams-roles-and-capabilities) to the application. Refer to this [Assign a role](/azure/active-directory/roles/manage-roles-portal#assign-a-role) procedure, but search for the application instead of a user. diff --git a/Teams/teams-powershell-release-notes.md b/Teams/teams-powershell-release-notes.md index 69b64ac836..e6e6509c6f 100644 --- a/Teams/teams-powershell-release-notes.md +++ b/Teams/teams-powershell-release-notes.md @@ -26,7 +26,10 @@ This page provides the latest Teams PowerShell change log for both General Avail | Date | Version | Updates | |------- | -------------------- | ------------------------------ | -| August 2024 | [6.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.5.1-preview) |
  • Releases Export-CsAcquiredPhoneNumber cmdlet.
  • Releases Get-CsExportAcquiredPhoneNumberStatus cmdlet.
  • +| November 2024 | [6.7.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.7.0)|
  • Adds LobbyChats, NoiseSuppressionForDialInParticipants parameters to [New\|Set]-CsTeamsMeetingPolicy.
  • Adds AIInterpreter, VoiceSimulationInInterpretation parameters to [New\|Set]-CsTeamsCallingPolicy.
  • Adds RecordingForTownhall, RecordingForWebinar, TranscriptionForTownhall, TranscriptionForWebinar parameters to [New\|Set]-CsTeamsEventsPolicy.
  • Adds FileTypeCheck, UrlReputationCheck parameters to [New\|Set]-CsTeamsMessagingConfiguration.
  • Adds AllowedTrialTenantDomains parameter to [New\|Set]-CsTenantFederationSettings.
  • Adds UserNameExtension parameter to [New\|Set]-CsAutoAttendant cmdlets.
  • +| October 2024 | [6.6.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.6.1-preview) |
  • Adds AllowExtendedWorkInfoInSearch parameters to [New\|Set]-CsTeamsMessagingPolicy.
  • Adds FederatedBilateralChats parameter to [New\|Set]-CsExternalAccessPolicy.
  • Adds PinnedCallingBarApps parameter to [New\|Set]-CsTeamsAppSetupPolicy.
  • Adds MessagingNotes parameter to Set-CsTeamsMessagingConfiguration.
  • Contains a new implementation of [Get\|Set]-CsPrivacyConfiguration, [Get\|Set\|Remove\|New]-CsTeamsNotificationAndFeedsPolicy. Functionality remains the same as previous implementation.
  • Releases [Get\|Update]-M365UnifiedTenantSettings to get or update tenant level settings like DefaultApp, GlobalApp, PrivateApp and EnableCopilotExtensibility.
  • Adds AppInstallType, InstallForOperationType, InstallForUsers, InstallForGroups and InstallVersion parameters to Update-M365TeamsApp.
  • Adds InstalledFor output attribute to Get-M365TeamsApp & Get-AllM365TeamsApps.
  • Adds ApiVersion parameter to [Set\|Remove]-TeamTargetingHierarchy and [Get]-TeamTargetingHierarchyStatus.
  • +| October 2024 | [6.6.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.6.0) |
  • Releases Export-CsAcquiredPhoneNumber cmdlet.
  • Releases Get-CsExportAcquiredPhoneNumberStatus cmdlet.
  • Releases [Get\|Set\|Remove\|Grant\|New]-CsTeamsAIPolicy cmdlets.
  • Releases [Get\|Set]-CsTeamsEducationAssignmentsAppPolicy cmdlets.
  • Adds EnablePayAsYouGoSpendingLimits and PayAsYouGoSpendingUserLimit parameters to [New\|Set]-CsTeamsCallingPolicy cmdlets.
  • Removes CreateBy attribute, updates datetime format for CreateAt and DownloadLinkExpiry attributes to UTC in Get-CsExportAcquiredPhoneNumberStatus cmdlet output.
  • + | August 2024 | [6.5.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.5.1-preview) |
  • Releases Export-CsAcquiredPhoneNumber cmdlet.
  • Releases Get-CsExportAcquiredPhoneNumberStatus cmdlet.
  • | August 2024 | [6.5.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.5.0) |
  • [BREAKING CHANGE] Deprecates Set-CsOnlineDialInConferencingUserDefaultNumber cmdlet. More details in [Set-CsOnlineDialInConferencingUserDefaultNumber](/powershell/module/teams/set-csonlinedialinconferencinguserdefaultnumber).
  • Fixes mapping for postal code in Set-CsOnlineLisCivicAddress.
  • Releases [Get\|Set]-CsTeamsExternalAccessConfiguration cmdlets.
  • Adds CaptchaVerificationForMeetingJoin parameter to the [New\|Set]-CsTeamsMeetingPolicy cmdlets.
  • | July 2024 | [6.4.1-preview](https://www.powershellgallery.com/packages/MicrosoftTeams/6.4.1-preview) |
  • [BREAKING CHANGE] Deprecates Set-CsOnlineDialInConferencingUserDefaultNumber cmdlet. More details in [Set-CsOnlineDialInConferencingUserDefaultNumber](/powershell/module/teams/set-csonlinedialinconferencinguserdefaultnumber).
  • Fixes mapping for postal code in Set-CsOnlineLisCivicAddress.
  • | June 2024 | [6.4.0](https://www.powershellgallery.com/packages/MicrosoftTeams/6.4.0) |
  • Adds ExternalAccessWithTrialTenants parameter to the Set-CsTenantFederationConfiguration cmdlet.
  • diff --git a/Teams/teams-progressive-web-apps.md b/Teams/teams-progressive-web-apps.md new file mode 100644 index 0000000000..da9ec1c2b2 --- /dev/null +++ b/Teams/teams-progressive-web-apps.md @@ -0,0 +1,66 @@ +--- +title: Teams Progressive Web Apps (PWAs) +description: Progressive Web Apps (PWAs) allow sites like Teams on the web to offer more desktop capabilities that are typically unavailable to websites. +author: MicrosoftHeidi +ms.author: heidip +manager: jacktremper +audience: admin +displayType: one-column +ms.date: 10/18/2024 +ms.reviewer: +ms.service: msteams +ms.topic: tutorial +ms.localizationpriority: medium +search.appverid: MET150 +ms.collection: + - M365-collaboration + - tier2 +f1.keywords: + - CSH +ms.custom: + - NewAdminCenter_Update + - seo-marvel-mar2020 +appliesto: + - Microsoft Teams +--- + +# What is a Progressive Web App (PWA)? + +A Progressive Web App (PWA) is a type of web application that can be installed on a device and provides a user experience similar to a native desktop app. PWAs allow sites like Teams on the web to offer more desktop capabilities that are typically unavailable to websites. + +PWAs are hosted by Microsoft Edge and Chrome browsers but look and feel like a native app. At their core, PWAs are still websites and operate within the same browser sandbox environment, offering the security and control many administrators require for their users. + +## Microsoft Teams on the web as a PWA + +Microsoft Teams on the web can be installed as a PWA on Edge or Chrome browsers. This allows users who can't install the Microsoft Teams desktop client or prefer using web apps to still have a seamless Teams desktop experience. + +## Benefits of using Teams PWA + +- **Automatic start**: Can automatically start on login for quick access. +- **Easy access**: Can be pinned to the taskbar or dock for easy access. +- **Consistent experience**: Provides a more consistent experience for web users who also use Teams desktop clients on other devices. + +## Deploying Teams PWA using group policies + +Administrators can deploy Microsoft Teams on the web PWA using group policies in Edge and Chrome browsers. There are two relevant policies: + +- **WebAppInstallForceList**: This policy allows administrators to force-install specific web apps, including PWAs. Users are unable to uninstall PWAs in this policy, and removing the policy causes the PWA to be uninstalled. +- **WebAppSettings**: This policy provides more settings for managing web apps. + +For detailed instructions on configuring these policies, see the following documentation: + +- [Edge group policy documentation](/deployedge/microsoft-edge-policies) +- [Chrome group policy documentation](https://support.google.com/chrome/a/answer/187202) + +## Recommended group policies for PWA users + +To ensure a smooth experience for PWA users and to avoid common permission issues, it's also recommended that administrators set the following group policies: + +- **SleepingTabsBlockedForUrls**: Prevents tabs with Teams on the web from going to sleep. +- **NotificationsAllowedForURLs**: Automatically allows notifications for Teams on the web. +- **ScreenCaptureAllowedByOrigins**: Allows screen capture for Teams on the web. +- **AudioCaptureAllowedUrls**: Allows audio capture for Teams on the web. +- **VideoCaptureAllowedUrls**: Allows video capture for specified URLs. +- **CookiesAllowedForUrls**: Unblocks specific cookies for Teams on the web, including third-party cookies used in line-of-business (LOB) apps. + +Setting these policies helps users avoid repeatedly approving common permissions or accidentally blocking functionalities needed for Teams on the web. diff --git a/Teams/teams-recording-compliance.md b/Teams/teams-recording-compliance.md new file mode 100644 index 0000000000..707f532bc1 --- /dev/null +++ b/Teams/teams-recording-compliance.md @@ -0,0 +1,229 @@ +--- +title: Introduction to Microsoft Teams third-party compliance recording +ms.author: scottfrancis +author: sfrancis206 +manager: pamgreen +ms.date: 11/11/2024 +audience: Admin +ms.topic: conceptual +ms.service: msteams +ms.reviewer: kiran.kodali +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn about Teams third-party compliance recording for calling, meetings, town halls, webinars, and live events. +f1.keywords: +- CSH +ms.custom: + - Adopt + - seo-marvel-mar2020 +ms.collection: +- Teams_ITAdmin_Adopt +- M365-collaboration +- tier3 +- m365initiative-meetings +- m365initiative-voice +- purview-compliance +appliesto: +- Microsoft Teams +--- + +# Third-party compliance recording for Microsoft Teams calls and meetings + +**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Calls + +## Compliance recording overview + +Compliance recording is the process of recording and storing communications in a way that follows local, national, and global regulatory requirements. + +Microsoft Teams is enhanced to offer compliance recording of call and meeting communications by supporting integrations with certified, third-party, compliance recording solutions. + +Using a partner solution to record Teams calls, meetings, and events allows corporate compliance officers to securely collect necessary communications in the manner required to meet regulated compliance and legal obligations (such as MiFID II, Dodd-Frank, FDCPA, HIPAA, GDPR, etc.). + +Compliance recording partner solutions are integrated with Teams as shown in the following diagram: + +:::image type="content" source="media/compliance-recorder-small.png" alt-text="Diagram of the flow for when a Teams meeting or call is sent and received." lightbox="media/compliance-recorder-expandable.png"::: + +The Graph API supporting the third-party application’s recording status is available in the following national cloud deployments: + +|Global Service |US Government L4 |US Government L5 (DOD) |China operated by 21Vianet | +|----------------------|------------------|---------------|-----------------| +|Yes |Yes |Yes |No | + +This solution is designed specifically to turn on policy-based compliance recording with Teams. Any other use of this solution isn't supported. + +## Supported compliance recording capabilities + +As a Teams communications admin, with a third-party compliance recording solution, you can specify when to capture calls, meetings, and events for subsequent processing and retention, in accordance with relevant corporate or regulatory policies. +From the available APIs and third-party compliance recording solutions, the following capabilities are supported. + + + + + + + + + + + + + + + + + + + + + + +
    PersonaCapabilities
    Recorded users
      +
    • Be notified when recording is in progress.

    • +
    • Be informed when policy and/or recorder error is causing changes in calling behavior.

    • +
    Communications admin
      +
    • Understand why and how to apply / enforce recording policies to Teams users / endpoints.

    • +
    • Configure and maintain Teams recording policies for the organization.

    • +
    • Monitor and troubleshoot recording-related issues with Teams calls and meetings.

    • +
    • Support internal compliance officer with operational analytics on usage, quality, and reliability.

    • +
    Compliance officer
      +
    • Collect all Teams communications in the manner required to meet compliance obligations in appropriate regional boundaries.

    • +
    • Search for interactions based on communication-related metadata or interaction content. Common examples include:

      +
        +
      • Metadata - Participants, time, direction, dialed number, origin number, Custom business data.

      • +
      • Content – Transcription, sentiment, phonetics, related interactions.

      • +
    • +
    • Analyze and interact with collected communications, including the ability to monitor interactions as they're being collected.

    • +
    • Ensure security of collected communications and prevent tampering at all stages.

    • +
    + +For general Teams recording capabilities, see [Teams recordings](./teams-recording-policy.md) + +#### Considerations + +Compliance recording isn't supported for: + +- E911 emergency calling services +- Users operating in Survivable Branch Appliance mode +- PSTN Calls for India users + +**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. + +**Call queues** + +Inbound call queue calls are recorded where users have an assigned compliance recording policy. Some routing methods might involve usability concerns with multiple announcements. + +## Supported notification methods + +Users with an assigned compliance recording policy know that their digital interactions with Teams are being recorded. Depending on the third-party recording solution and how it's configured, users may not be able to disable the recording and may not have access to the recording. + +Compliance recording notifications are supported for the Teams client experiences. The experiences can be both visual and audio. + +### Teams clients - visual notice + +- Desktop/web +- Mobile (iOS/Android) +- Teams Phones +- Teams rooms + +### Other endpoints - audio notice + +- SIP phones +- Skype for Business +- Audio conferencing (audio notice in dial-in number's default or user-selected language) +- PSTN callers (audio notice in Teams user's default language) + +## Recorder development + +The solution for Teams compliance recording is achieved through Microsoft’s third-party partners who develop compliance recording bots, and pair the bot with their recording solution. Each partner solution varies, but each partner uses the same key Graph APIs, an application instance, and a compliance recording policy. + +For a sample of developing a compliance recording bot, see [deploying and testing a sample bot](https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot#bot-registration). + +## Third-party compliance recording partners + +Microsoft created a compliance recording for Microsoft Teams certification program while making Teams APIs available for partners to develop and integrate compliance recording solutions. This program provides customers with the assurance that each participating partner's solution is tested and verified to provide the quality, compatibility, and reliability expected from a Microsoft solution. + +The following site lists current partners with certified their compliance recording solution for Microsoft Teams: +[Modern Work for Partners - Compliance Recording Solutions](https://cloudpartners.transform.microsoft.com/compliance-recording-solutions) + +Microsoft only supports compliance recording solutions from the listed certified partners. If there are enablement or operational issues, you must contact your compliance recording partner first. If the partner determines the issue is with Microsoft, they might ask you to raise a case with Microsoft, providing context of the investigation completed by the partner. If needed, the partner can bring the issue to Microsoft through their Microsoft support channel. Microsoft might reject support cases where a non-certified Compliance Recording solution is used, or if investigation shows that the issue is one the partner can address. + +If you're a vendor seeking to join the certification program, fill out the calling platform intake as the next step. +[Calling Platform Intake](https://aka.ms/CallingPlatformIntake) + +## Create and manage your compliance recording policy + +Once a compliance recording solution is in place, a Teams admin can create and assign recording policies to control which users are recorded and which recorder is used for each user. Recorders are automatically invited to participate in conversations based on the configuration of these policies when a communication interaction takes place. +Compliance +recording policies are managed using [Microsoft +PowerShell](./teams-powershell-overview.md) +and can be applied at the tenant, per-user, and security group level for each +organization. You can find more information on Microsoft Learn for +[Meeting +policies](./meeting-policies-overview.md), + [calling +policies](./teams-calling-policy.md) and [group +policies](./assign-policies-users-and-groups.md#assign-a-policy-to-a-group). + +1. Create an application instance in your tenant. + + ```powershell + New-CsOnlineApplicationInstance -UserPrincipalName cr.instance@contoso.onmicrosoft.com -DisplayName ComplianceRecordingBotInstance -ApplicationId fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 + ``` + + Example results + - RunspaceId : 4c13efa6-77bc-42db-b5bf-bdd62cdfc5df + - ObjectId : 5069aae5-c451-4983-9e57-9455ced220b7 + - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 + - UserPrincipalName : cr.instance@contoso.onmicrosoft.com + - ApplicationId : fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 + - DisplayName : ComplianceRecordingBotInstance + - PhoneNumber : + + ```powershell + Sync-CsOnlineApplicationInstance -ObjectId 5069aae5-c451-4983-9e57-9455ced220b7 + ``` + +2. Create a Compliance Recording policy. + + ```powershell + New-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy -Enabled $true -Description "Test policy created by tenant admin" + ``` + + Example results + - Identity : Global + - ComplianceRecordingApplications : {} + - Enabled : True + - WarnUserOnRemoval : True + - Description : Test policy created by tenant admin + + ```powershell + Set-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy ` + -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Id 5069aae5-c451-4983-9e57-9455ced220b7 -Parent TestComplianceRecordingPolicy) + ``` + + See [Set-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/set-csteamscompliancerecordingpolicy). + +3. Assign the Compliance Recording policy to a user. + + ```powershell + Grant-CsTeamsComplianceRecordingPolicy -Identity testuser@contoso.onmicrosoft.com -PolicyName TestComplianceRecordingPolicy + ``` + + See [Grant-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/grant-csteamscompliancerecordingpolicy). + + ```powershell + Get-CsOnlineUser testuser@contoso.onmicrosoft.com | select SipAddress, TenantId, TeamsComplianceRecordingPolicy | fl + ``` + + Example + - UserPrincipalName : testuser@contoso.onmicrosoft.com + - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 + - TeamsComplianceRecordingPolicy : TestComplianceRecordingPolicy + +### Related topics  + +- [Teams Recordings - Microsoft Teams | Microsoft Learn](./teams-recording-policy.md) +- diff --git a/Teams/teams-recording-policy.md b/Teams/teams-recording-policy.md index c2c092b02e..ae9c43faef 100644 --- a/Teams/teams-recording-policy.md +++ b/Teams/teams-recording-policy.md @@ -1,16 +1,16 @@ --- -title: Introduction to Microsoft Teams third party compliance recording -ms.author: wlibebe -author: wlibebe +title: Introduction to recording Microsoft Teams calls and meetings +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen -ms.date: 06/27/2024 +ms.date: 11/11/2024 audience: Admin ms.topic: conceptual ms.service: msteams -ms.reviewer: ritikag,lisma +ms.reviewer: ritikag ms.localizationpriority: medium search.appverid: MET150 -description: Learn about Teams third party compliance recording for calling, meetings, town halls, webinars, and live events. +description: Learn about Teams recordings for calling, meetings, town halls, webinars, and live events. f1.keywords: - CSH ms.custom: @@ -20,294 +20,69 @@ ms.collection: - Teams_ITAdmin_Adopt - M365-collaboration - tier3 +- m365initiative-meetings +- m365initiative-voice - purview-compliance appliesto: - Microsoft Teams --- -# Introduction to Microsoft Teams third party compliance recording +# Introduction to Teams recording -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls ✔️ Calls ✔️ Live events +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Calls ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Live events ## Overview -Third-party compliance recording allows orgs using Microsoft Teams for calls, meetings, and events to implement an admin policy for automatic recording. For your users to make calls, they must have an assigned Teams Phone license. As an admin, you can also choose when to capture calls, meetings, and events for subsequent processing and retention, in accordance with relevant corporate or regulatory policies. +In Microsoft Teams, your users can record calls and meetings to reference later and share with others. Communications can also be automatically preserved for industry compliance reasons. Call and meeting recordings capture media shared during the session (audio, video, and screen sharing activity), and are stored according to your policies. -Teams is enhanced to support the integration of partner recording solutions. These enhancements provide a complete solution for configuring, managing, recording, storing, and analyzing Teams communications. The enhancements include communications platform APIs and events for recording, which provide: +There are two recording features that can be enabled with policy: -- Seamless, high-quality media capture across devices. Compliance recording captures the same screenshare activity as convenience recording. To learn which screenshare activities are captured, see [Record a meeting in Microsoft Teams](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24). +- **Convenience recording**- an ad-hoc recording of a call or meeting that a user starts and manages. -- Support for interaction capture between Teams users and supported calling, meeting, and endpoints (Teams, Teams Mobile, Skype for Business, PSTN). +- **Compliance recording**-calls and meetings that are automatically recorded without user intervention and owned by the company, using a third-party solution. -Compliance recording can be enabled on Microsoft 365 A3/A5/E3/E5/Business Premium, Office 365 A3/A5/E3/E5 users, Teams Rooms license, or Microsoft Teams Shared Devices license. +The following table compares convenience and compliance recording. -> [!NOTE] -> Compliance recording isn't currently supported for E911 emergency calling services. +| Property | Convenience Recording | Compliance Recording | +| ---------------------- | :------------------: | :---------------: | +| Recording initiator | Licensed Teams user, enabled with meeting / calling policy | Admin (system) | +| Storage and access owner | [Meeting storage and permissions](tmr-meeting-recording-change.md) | Admin / compliance officer | +| Participant notification enforced | Yes | Yes | +| Participant consent supported | Yes | No | +| Media recorded | Voice, video, screen share, PPT Live | Voice, video, screen share | +| Retention policy | [Meeting storage and permissions](tmr-meeting-recording-change.md) | Configurable with partner solution | +| Recording policy | Configurable with Teams Admin Center (Meeting policy + Calling policy) | Configurable with user policy | -The compliance recording solution integration capabilities were also -reviewed at Ignite 2019 in the [Compliance -Recording and Microsoft Teams -session](https://myignite.microsoft.com/archives/IG19-VCE40). +- Guests can't initiate convenience recordings. -### Compliance vs convenience recording +- Users in trusted organizations can’t initiate convenience recordings when they join meetings in your organization. -In Microsoft Teams, there are two types of recordings: +- Users in trusted organizations can initiate convenience recordings of unscheduled, 1:1 calls originated by either party. If they initiate, the recording adheres to the calling policy defined in the trusted organization's tenant. -- **Convenience recording-** an ad-hoc recording of a call or meeting that a user starts. To learn more about convenience recording, see [Teams meeting recording](meeting-recording.md). -- **Compliance recording-** using an admin policy to automatically record calls and meetings. +- Users assigned with Edu A1 license only, can record manually but can't use meeting options to auto-record. -The following table details differences between convenience and compliance recording. +Meeting recordings don't capture: -| Type | Convenience Recording | Compliance Recording | -| ---------------------- | ------------------ | --------------- | -| Initiator | User | Admin (system) | -| Target | Per-call / meeting / event | Per-user | -| Storage owner | Organizer | Admin or compliance officer | -| Participant notification required? | Yes | Yes | -| Retention Policy | Organizer's SharePoint Online policy enforced | Yes | +- More than four peoples' video streams at once +- Whiteboards and annotations +- Shared notes +- Content shared by apps +- Videos or animations embedded in PowerPoint Live presentations +- Multi-screen share -Users with an assigned compliance recording policy know that their digital -interactions with Teams are being recorded. They also know that they can't -disable the recording and don't have access to the recording once the interaction is complete. The recording becomes part of the organizational archive. This archive is available to compliance and legal personnel for eDiscovery, legal hold, and other corporate retention uses. +Calls in Teams are unscheduled, peer-to-peer Teams client sessions (encompassing internal and external Teams users). In convenience and compliance recording, policy scope for calls includes Teams PSTN calls, if the user has one of the following licenses: Microsoft 365 E5, Office 365 E5, or Microsoft/Office 365 E3 with Teams Phone Add-on license. -## Solution architecture overview +> [!TIP] +> To learn and share more about recording options that you may allow your users to control, refer to [Record a meeting in Microsoft Teams](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24).  -Compliance recording solutions are integrated with Teams as -shown in the following diagram: +## Managing recording policies -:::image type="content" source="media/compliance-recording-diagram-small.png" alt-text="Diagram of the flow for when a Teams meeting or call is sent and received." lightbox="media/compliance-recording-diagram-expand.png"::: +Navigate to these sections for more specific details on convenience and compliance recording: -> [!NOTE] -> This solution is designed specifically to enable policy-based compliance recording with Teams. Any other use of this solution isn't supported. +| Meeting convenience recording | Call convenience recording | Meeting and call compliance recording | +| :------------------: | :---------------: | :---------------: | +| [Manage Teams recording policies for meetings](./meeting-recording.md)| [Manage Teams recording policies for calls](./call-recording-transcription-captions.md) | [Teams compliance recording for meetings and calls](./teams-recording-compliance.md) | -## Example user needs +### Related topics - - - - - - - - - - - - - - - - - - - - - -
    PersonaNeeds
    Recorded users
      -
    • Be notified when recording is in progress.

    • -
    • Be informed when policy and/or recorder error is causing changes in calling behavior.

    • -
    Communications admin
      -
    • Understand why and how to apply / enforce recording policies to Teams users / endpoints.

    • -
    • Configure and maintain Teams recording policies for the organization.

    • -
    • Monitor and troubleshoot recording-related issues with Teams calls and meetings.

    • -
    • Support internal compliance officer with operational analytics on usage, quality, and reliability.

    • -
    Compliance officer
      -
    • Collect all Teams communications in the manner required to meet compliance obligations in appropriate regional boundaries.

    • -
    • Search for interactions based on communication-related metadata or interaction content. Common examples include:

      -
        -
      • Metadata - Participants, time, direction, dialed number, origin number, Custom business data.

      • -
      • Content – Transcription, sentiment, phonetics, related interactions.

      • -
    • -
    • Analyze and interact with collected communications, including the ability to monitor interactions as they're being collected.

    • -
    • Ensure security of collected communications and prevent tampering at all stages.

    • -
    - -## Recorders - -The core component of the compliance recording solution is the recorder. -Recorders are built as scalable Azure-based services (bots) that -[use Microsoft's communications -platform](/graph/cloud-communications-concept-overview) -and register as applications with Microsoft Graph. The recorder provides -the direct interaction with the Teams calls and meetings -[communications platform -APIs](/graph/api/resources/communications-api-overview) -and provides the endpoint for media ingestion. - -A [sample compliance recorder application is -available](https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot) -that shows how to configure the bot, create the app instance and assign -the compliance policies. The sample also has examples on API usage for -recording specific interactions such as handling -[incoming -call](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Http/Controllers/PlatformCallController.cs#L199-L244) routing, -[changing recording -states](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Bot/CallHandler.cs#L135-L138), -and [removing the user who is being -recorded](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Bot/CallHandler.cs#L121-L126). -Graph documentation on the specific APIs can be found here for -[updateRecordingStatus](/graph/api/call-updaterecordingstatus?tabs=http) -and -[incomingContext](/graph/api/resources/incomingcontext). - -The exact implementation of the recorder service varies by partner, but must be designed to support multiple recorders. This requirement ensures high availability and geographical distribution, reducing latency between Teams and the recorder. Recorders should be designed with resiliency and redundancy in mind. - -Partners must confirm the minimum required release version of the -Microsoft Graph communications APIs and SDKs with Microsoft before -submitting their solution for certification. This requirement ensures that all -requirements of compliance recording integration are supported. - -Requirements that are fundamental for compliance recording -scenario: - -- Recorder bot must be deployed in Azure. - -- Recorder bot must run on a Windows VM in Azure. - -- Recorder bot outbound firewall destination IP address must be open to the Azure public IP range. - -- Recorder bot inbound firewall source IP address must be open to the [Teams IP range](/microsoft-365/enterprise/urls-and-ip-address-ranges#microsoft-teams). - -The Azure and Windows VM requirements only apply to the Teams Bot -component, which means that a partner might implement the rest of the -platform of their choice provided they can meet the relevant performance -and functional requirements for compliance recording. - -## Create and manage your compliance recording policy - -Through creating and assigning compliance recording policies, as an admin, you can determine which users are to be recorded and which recorder is used for each user. Recorders are automatically invited to participate in conversations based on the configuration of these policies when a communication interaction takes place. -Compliance -recording policies are managed using [Microsoft -PowerShell](./teams-powershell-overview.md) -and can be applied at the tenant, per-user, and security group level for each -organization. You can find more information on Microsoft Learn for -[Meeting -policies](./meeting-policies-overview.md), - [calling -policies](./teams-calling-policy.md) and [group -policies](./assign-policies-users-and-groups.md#assign-a-policy-to-a-group). - -1. Create an application instance in your tenant. - - ```powershell - PS C:\> New-CsOnlineApplicationInstance -UserPrincipalName cr.instance@contoso.onmicrosoft.com -DisplayName ComplianceRecordingBotInstance -ApplicationId fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 - - RunspaceId : 4c13efa6-77bc-42db-b5bf-bdd62cdfc5df - ObjectId : 5069aae5-c451-4983-9e57-9455ced220b7 - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 - UserPrincipalName : cr.instance@contoso.onmicrosoft.com - ApplicationId : fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 - DisplayName : ComplianceRecordingBotInstance - PhoneNumber : - ``` - - ```powershell - PS C:\> Sync-CsOnlineApplicationInstance -ObjectId 5069aae5-c451-4983-9e57-9455ced220b7 - ``` - -2. Create a Compliance Recording policy. - - ```powershell - PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy -Enabled $true -Description "Test policy created by tenant admin" - - Identity : Global - ComplianceRecordingApplications : {} - Enabled : True - WarnUserOnRemoval : True - Description : Test policy created by tenant admin - ``` - - ```powershell - PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy ` - -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Id 5069aae5-c451-4983-9e57-9455ced220b7 -Parent TestComplianceRecordingPolicy) - ``` - - See [Set-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/set-csteamscompliancerecordingpolicy). - -3. Assign the Compliance Recording policy to a user. - - ```powershell - PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity testuser@contoso.onmicrosoft.com -PolicyName TestComplianceRecordingPolicy - ``` - - See [Grant-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/grant-csteamscompliancerecordingpolicy). - - ```powershell - PS C:\> Get-CsOnlineUser testuser@contoso.onmicrosoft.com | select SipAddress, TenantId, TeamsComplianceRecordingPolicy | fl - - UserPrincipalName : testuser@contoso.onmicrosoft.com - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 - TeamsComplianceRecordingPolicy : TestComplianceRecordingPolicy - ``` - -## User experiences - -### PSTN calls - -Inbound call queue (CQ) calls are recorded for users who have an assigned compliance recording (CR) policy. Some routing methods might involve usability concerns with multiple announcements. We recommend appropriately configuring your call queues to align with your organization's intended user experience. - -Compliance recording doesn't work if users have an Internet outage, and make or receive PSTN calls using an SBA. - -### Notifications - -Support for notifications is enabled using the Teams client experiences. The experiences can be either visual or audio. - -#### Teams clients - visual notice - -- Desktop/web -- Mobile (iOS/Android) -- Teams Phones -- Teams rooms - -#### Other endpoints - audio notice - -- SIP phones -- Skype for Business -- Audio conferencing (audio notice in dial-in number's default or user-selected language) -- PSTN callers (audio notice in Teams user's default language) - -## Compliance recording for Teams certification programs - -In addition to publishing publicly available APIs allowing partners to develop and integrate CCaaS solutions with Teams, we developed the compliance recording for Microsoft Teams certification program. This program provides customers with the assurance that each participating partner's solution is tested and verified. Customers can be assured that partners provide the quality, compatibility, and reliability they expect from Microsoft solutions. - -The following partners certify their solution for Microsoft Teams.

    - -|Partner|Solution website | -|:--|:--| -|ASC Technologies |[https://www.asctechnologies.com/english/ASC_Recording_Insights_Compliance_Recording_for_Microsoft_Teams.html](https://www.asctechnologies.com/english/ASC_Recording_Insights_Compliance_Recording_for_Microsoft_Teams.html) | -|AudioCodes |[https://online.audiocodes.com/smarttap-360-live-for-microsoft-teams](https://online.audiocodes.com/smarttap-360-live-for-microsoft-teams) | -|CallCabinet |[https://www.callcabinet.com/compliance-microsoft-teams-call-recording](https://www.callcabinet.com/compliance-microsoft-teams-call-recording ) | -|Dubber |[https://www.dubber.net/call-recording/](https://www.dubber.net/call-recording/) | -|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) | -|Insightful Technology |[https://insightfultechnology.com/teams/](https://insightfultechnology.com/teams/) | -|Luware |[https://luware.com/en/solution/microsoft-teams-recording/](https://luware.com/en/solution/microsoft-teams-recording/) | -|Mida Solutions |[https://www.midasolutions.com/recorder-for-teams/](https://www.midasolutions.com/recorder-for-teams/) | -|NICE Engage |[https://www.nice.com/products/workforce-engagement/call-recording/air-and-engage](https://www.nice.com/products/workforce-engagement/call-recording/air-and-engage) | -|NICE NTR-X |[https://www.niceactimize.com/compliance/ms-teams-recording.html](https://www.niceactimize.com/compliance/ms-teams-recording.html) | -|Numonix |[https://numonix.cloud](https://numonix.cloud) | -|Oak Innovation |[https://www.oakinnovate.com/clarify](https://www.oakinnovate.com/clarify) | -|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/) | -|Verint |[https://www.verba.com/solutions/microsoft-teams-recording](https://www.verba.com/solutions/microsoft-teams-recording) | - -
    -The following partners are in the process of certifying their solution for Microsoft Teams.

    - -|Partner|Solution website | -|:--|:--| -|Cloud World Wide Services |[https://recordia.net/microsoft-teams-call-recording/](https://recordia.net/microsoft-teams-call-recording/) | -|CreaLog |[https://www.crealog.com/en/products-solutions/recording/](https://www.crealog.com/en/products-solutions/recording/) | -|Landis Technologies |[https://landistechnologies.com/](https://landistechnologies.com/) | -|Redwood Technologies |[https://www.contentguru.com/en-us/solutions/needs/compliance-recording-ms-teams/](https://www.contentguru.com/en-us/solutions/needs/compliance-recording-ms-teams/) | - -This list gets updated as more partners join and meet the certification criteria. - -## Support boundaries - -Microsoft only supports compliance recording solutions from the listed certified partners. If there are issues, you must contact your compliance recording partner first. If needed, the partner can bring the issue to Microsoft through internal channels. Microsoft might reject support cases where a non-certified Compliance Recording solution is used, or if investigation shows the issue is one that the partner can address. - -## Next steps - -If you're a vendor seeking to join the certification program, fill out the calling platform intake as the next step. -> [!div class="nextstepaction"] -> [Calling Platform Intake](https://aka.ms/CallingPlatformIntake) +- [Teams settings and policies reference - Microsoft Teams | Microsoft Learn](settings-policies-reference.md) diff --git a/Teams/tmr-meeting-recording-change.md b/Teams/tmr-meeting-recording-change.md index a38c1917e3..42b0d7bc6a 100644 --- a/Teams/tmr-meeting-recording-change.md +++ b/Teams/tmr-meeting-recording-change.md @@ -23,6 +23,9 @@ appliesto: # Teams meeting recording storage and permissions in OneDrive and SharePoint +> [!NOTE] +> When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off. To learn more about Copilot, see [Manage Microsoft 365 Copilot in Teams meetings and events](copilot-teams-transcription.md). + When users in your org record Teams meetings, the recording is stored in either OneDrive and SharePoint. Depending on where your users access the file, the recording plays on the video player in OneDrive or SharePoint. This article helps you, as an admin, understand recording storage and permissions for OneDrive and Sharepoint. To learn about your recording policies, see [Teams meeting recording](meeting-recording.md). To learn how to block the download of Teams meeting recording files from SharePoint or OneDrive, see [Block the download of Teams meeting recording files from SharePoint or OneDrive](block-download-meeting-recording.md). @@ -31,7 +34,7 @@ To learn about your recording policies, see [Teams meeting recording](meeting-re ### Meetings and events -For **meetings and events**, use the per-organizer **`-MeetingRecordingOwnership`** parameter within the PowerShell [**CsTeamsRecordingRolloutPolicy**](/powershell/module/teams/set-csteamsrecordingrolloutpolicy) cmdlet to decide if the recording is saved to the organizer's or recording initiator's OneDrive. This policy applies to the following meeting and event types: +For **meetings and events**, you can use the per-organizer **`-MeetingRecordingOwnership`** parameter within the PowerShell [**CsTeamsRecordingRolloutPolicy**](/powershell/module/teams/set-csteamsrecordingrolloutpolicy) cmdlet to decide if the recording is saved to the organizer's or recording initiator's OneDrive. This policy applies to the following meeting and event types: - Automatically recorded meetings - Delegate-created meetings @@ -114,8 +117,7 @@ For **non-Channel meetings**: - If the meeting is forwarded, only participants who are automatically added to the meeting chat thread receive the recording link. - For optimal performance, the total number of users in a chat shouldn't exceed 1,000. - If a meeting is forwarded to a group, only some users are added to the chat. If forwarded to an individual user, they're added to the meeting chat unless there are more than 1,000 users in the chat. - -For **large meetings**, if a meeting has more than 250 participants, some particpants don't automatically have file permissions. Excluded participants should ask the recording owner to add them to the shared list. +- For **large meetings**, if a meeting has more than 250 participants, some particpants don't automatically have file permissions. Excluded participants should ask the recording owner to add them to the shared list. For **Channel meetings**, permissions are inherited from the owners and members list in the channel. diff --git a/Teams/toc.yml b/Teams/toc.yml index a374c7e658..877e0b9540 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -3,6 +3,8 @@ items: href: teams-overview.md - name: Teams Premium overview href: enhanced-teams-experience.md +- name: Set up Facilitator for AI notes + href: facilitator-teams.md - name: Get started items: - name: Deployment overview @@ -103,8 +105,12 @@ items: href: new-teams-education.md - name: Update to the new Teams for Web href: new-teams-web.md + - name: Teams Progressive Web Apps (PWAs) + href: teams-progressive-web-apps.md - name: New teams pre-installation script href: new-teams-preinstallation-script.md + - name: Teams client updates + href: teams-client-update.md - name: Troubleshooting installation issues href: /microsoftteams/troubleshoot/teams-administration/fix-new-teams-installation-issues - name: Troubleshooting launch issues @@ -117,6 +123,8 @@ items: href: teams-classic-client-end-of-availability.md - name: Manually uninstall classic Teams client href: teams-classic-client-uninstall.md + - name: Classic Teams uninstillation script + href: teams-client-uninstall-script.md - name: Feature differences between desktop and Teams for Web href: new-teams-desktop-client-features.md - name: Usage report for new Teams client @@ -125,8 +133,6 @@ items: items: - name: Get the classic Teams clients href: get-clients.md - - name: Classic Teams client updates - href: teams-client-update.md - name: Bulk install classic Teams using Windows Installer href: msi-deployment.md - name: Classic Teams for Virtualized Desktop Infrastructure (VDI) @@ -331,8 +337,12 @@ items: href: /microsoft-365/compliance/information-barriers-teams-shared-channels?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json - name: Legal hold href: /microsoft-365/compliance/ediscovery-teams-legal-hold?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json - - name: Third party compliance recording - href: teams-recording-policy.md + - name: Recording + items: + - name: Introduction to Teams recording + href: teams-recording-policy.md + - name: Third party compliance recording + href: teams-recording-compliance.md - name: Retention policies href: retention-policies.md - name: Sensitivity labels @@ -358,7 +368,6 @@ items: - name: Intelligent recap href: privacy/intelligent-recap.md - - name: Manage and monitor Teams items: - name: Overview @@ -367,6 +376,8 @@ items: href: using-admin-roles.md - name: Manage teams in Teams admin center href: manage-teams-in-modern-portal.md + - name: Teams Administrative Units + href: teams-administrative-units.md - name: Manage policies items: @@ -669,12 +680,16 @@ items: href: meeting-webinar-town-hall-feature-comparison.md - name: Presenter & organizer experience items: - - name: Manage who can schedule town halls + - name: Manage who can schedule and attend town halls href: set-up-town-halls.md + - name: Manage who can schedule and attend webinars + href: set-up-webinars.md - name: Manage who can start and schedule meetings href: manage-who-can-schedule-meetings.md - - name: Manage who can schedule webinars - href: set-up-webinars.md + - name: Manage event chat for town halls + href: town-hall-chat.md + - name: Require verification checks + href: join-verification-check.md - name: Limit presenter role permissions href: presenter-role-reduction.md - name: Manage VOD publishing permissions for webinars and town halls @@ -687,7 +702,7 @@ items: href: hide-attendee-names.md - name: Manage the attendance report href: teams-analytics-and-reports/meeting-attendance-report.md - - name: Who can bypass the lobby + - name: Manage lobby options in Microsoft Teams href: who-can-bypass-meeting-lobby.md - name: Content sharing href: meeting-policies-content-sharing.md @@ -1301,10 +1316,12 @@ items: - name: Contact Center integrations href: teams-contact-center.md -- name: Teams Rooms and devices +- name: Teams Rooms and devices items: - name: Teams device store href: devices/device-store.md + - name: Copilot and Teams Rooms + href: rooms/copilot-admin-mtr.md - name: Teams device certification items: - name: Certification overview @@ -1315,7 +1332,7 @@ items: href: devices/certification-partners.md - name: How to join the program href: devices/certification-join.md - - name: Teams device specifications + - name: Teams specifications href: devices/certification-specifications.md - name: IT admins and decision makers href: devices/certification-it-admins.md @@ -1326,8 +1343,8 @@ items: - name: Windows version support href: rooms/rooms-lifecycle-support.md - name: Android version support - href: devices/android-version-support.md - - name: Teams Certified Devices + href: devices/android-version-support.md + - name: Teams certified devices items: - name: Overview of certified devices href: devices/certified-devices-overview.md @@ -1343,245 +1360,323 @@ items: href: devices/teams-displays-certified-hardware.md - name: Personal peripherals href: devices/usb-devices.md - - name: Microsoft Teams Rooms + items: + - name: Troubleshooting and known issues + href: /microsoftteams/troubleshoot/meetings/known-issues-teams-certified-peripherals + - name: Teams Rooms and panels items: - - name: Overview - href: rooms/index.md - name: Plan - items: - - name: Teams Rooms planning - href: rooms/rooms-plan.md - - name: Security - href: rooms/security.md - - name: Meeting room guidance for Teams + items: + - name: Teams Rooms + items: + - name: Overview of Teams Rooms + href: rooms/index.md + - name: Planning for Teams Rooms + href: rooms/rooms-plan.md + - name: Features + items: + - name: Teams Room Home Screen and admin controls + href: rooms/mtr-home-refresh.md + - name: Join a meeting using Proximity Join + href: rooms/proximity-join.md + - name: Join meetings with QR codes + href: rooms/teams-rooms-qr-codes.md + - name: SIP and H.323 dialing with Teams Rooms + href: rooms/meetings-with-sip-h323-devices.md + - name: Join third-party meetings + href: rooms/third-party-join.md + - name: Digital signage + href: rooms/digital-signage.md + - name: Custom backgrounds on Android + href: rooms/custom-backgrounds-android.md + - name: Custom backgrounds on Windows + href: rooms/custom-backgrounds.md + - name: Content camera + href: rooms/content-camera.md + - name: Coordinated meetings + href: rooms/coordinated-meetings.md + - name: Intelligent speaker + items: + - name: Voice and face recognition + href: rooms/voice-and-face-recognition.md + - name: Voice recognition controls + href: rooms/voice-recognition.md + - name: IntelliFrame + items: + - name: Multi-Stream IntelliFrame + href: devices/smartvision-admin.md + - name: Cloud IntelliFrame + href: devices/cloud-intelliframe.md + - name: Teams panels + items: + - name: Overview of Teams panels + href: devices/overview-teams-panels.md + - name: Planning for Teams panels + href: devices/teams-panels.md + - name: Features + items: + - name: Use Teams panels + href: devices/use-teams-panels.md + - name: App support + href: app-support-on-Teams-panels.md + - name: Check-in and auto release + href: devices/check-in-and-auto-release.md + - name: Reserve rooms with a QR code + href: devices/reserving-rooms-with-a-qr-code.md + - name: Custom backgrounds on Teams panels + href: devices/custom-background-panels.md + - name: Surface Hub (legacy) + items: + - name: Manage Microsoft Teams settings + href: rooms/surface-hub-manage-config.md + - name: Surface Hub Help + href: /surface-hub/first-run-program-surface-hub + - name: Teams Rooms and panels feature comparison + href: rooms/teams-devices-feature-comparison.md + - name: Meeting room design guidance href: rooms/room-planning-guidance.md - name: Licensing items: - name: Overview of Teams Rooms licensing href: rooms/rooms-licensing.md - - name: Teams Rooms admin center licensing - href: rooms/admin-center-license-overview.md - name: Teams Rooms legacy licensing href: rooms/rooms-legacy-licensing.md - - name: Release notes - href: rooms/rooms-release-note.md - - name: Deploy - items: - - name: Deployment overview - href: rooms/rooms-deploy.md - - name: Prepare your environment - href: rooms/rooms-prep.md - - name: Create resource accounts - href: rooms/create-resource-account.md - - name: Authentication + - name: Security + href: rooms/security.md + - name: Conditional Access and Intune compliance items: - - name: Deploy LAPs - href: rooms/laps-authentication.md - - name: Configure authentication - href: rooms/rooms-authentication.md - name: Best practices for Conditional Access and Intune compliance href: rooms/conditional-access-and-compliance-for-devices.md - name: Supported Conditional Access and Intune compliance policies href: rooms/supported-ca-and-compliance-policies.md - - name: Surface Hub - items: - - name: Set up Coordinated Meetings - href: rooms/coordinated-meetings.md - - name: Manage Microsoft Teams settings - href: rooms/surface-hub-manage-config.md - - name: Teams Rooms for Windows deployment tools + - name: Authentication for Teams Rooms on Windows devices + href: rooms/rooms-authentication.md + - name: Authentication for Teams Android devices + href: devices/authentication-best-practices-for-android-devices.md + - name: Conditional Access-related known issues + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-android-devices-conditional-access-issues + - name: Release notes items: - - name: Create a Teams Room for Windows image - href: rooms/console.md - - name: Update a Teams Room for Windows - href: rooms/manual-update.md - - name: Peripherals + - name: Teams Rooms release notes + href: rooms/rooms-release-note.md + - name: Teams panels release notes + href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Teams_panels + - name: Management apps + href: devices/certified-device-apps.md + - name: Troubleshooting and known issues items: - - name: Content cameras - href: rooms/content-camera.md - - name: Manage + - name: Teams Rooms on Windows + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-windows + - name: Teams Rooms on Android + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android + - name: Deploy items: - - name: Management overview + - name: Overview + href: rooms/rooms-deploy.md + - name: Step 1 - Plan your rooms + href: rooms/rooms-plan.md + - name: Step 2 - Prepare your environment + items: + - name: Preparing your network + href: rooms/rooms-prep.md + - name: Quality of Service (QoS) for Teams Rooms + href: devices/qos-on-teams-devices.md + - name: Intune Enrollment for Windows + items: + - name: Autopilot and Autologin + href: rooms/autopilot-autologin.md + - name: Deploy LAPS + href: rooms/laps-authentication.md + - name: Intune Enrollment for Android + items: + - name: Device administrator + href: devices/mtra-panels-deploy.md + - name: AOSP device management + href: rooms/android-migration-guide.md + - name: Step 3 - Create room accounts + href: rooms/create-resource-account.md + - name: Step 4 - Setting up Teams Rooms + items: + - name: Teams Rooms on Windows + items: + - name: Use AutoPilot and AutoLogin for Teams Rooms on Windows + href: rooms/autopilot-autologin.md + - name: Create a one-time password + href: rooms/create-otp.md + - name: Set up using one-time passwords + href: rooms/first-time-setup.md + - name: Teams Rooms on Android and Teams panels + items: + - name: Remote provisioning and sign-in + href: devices/remote-provision-remote-login.md + - name: Manage + items: + - name: Overview href: rooms/rooms-manage.md - - name: Maintenance and operations - href: rooms/rooms-operations.md - - name: Remotely configure layout, scale, and resolution - href: rooms/manage-front-room-scale-res.md - - name: Manage settings with an XML file - href: rooms/xml-config-file.md - - name: Feature management + - name: Keep up to date + items: + - name: Teams Rooms on Windows + href: rooms/rooms-lifecycle-support.md + - name: Teams Rooms on Android + href: devices/certified-hardware-android.md + - name: Management apps + href: devices/certified-device-apps.md + - name: Operations and configuration items: - - name: Teams Rooms Home screen - href: rooms/mtr-home-refresh.md + - name: Teams Rooms operations + href: rooms/rooms-operations.md + - name: Reset Teams Rooms on Windows + href: rooms/recovery-tool.md + - name: OEM Image creation for Teams Rooms on Windows + href: rooms/console.md + - name: Manually update Teams Rooms on Windows + href: rooms/manual-update.md + - name: Manage settings with an XML file + href: rooms/xml-config-file.md + - name: Remotely configure layout, scale, and resolution + href: rooms/manage-front-room-scale-res.md - name: Remotely configure front row layout href: rooms/manage-front-row.md - - name: Proximity join - href: rooms/proximity-join.md - - name: Join third-party meetings - href: rooms/third-party-join.md - - name: SIP and H.323 calling with Teams Rooms - href: rooms/meetings-with-SIP-H323-devices.md - - name: Manage custom backgrounds on Android - href: rooms/custom-backgrounds-android.md - - name: Manage custom backgrounds on Windows - href: rooms/custom-backgrounds.md - - name: Digital signage - href: rooms/digital-signage.md - - name: Join meetings with QR codes - href: rooms/teams-rooms-qr-codes.md - - name: Multi-Stream IntelliFrame - href: devices/smartvision-admin.md - - name: Cloud IntelliFrame - href: devices/cloud-intelliframe.md - - name: Identification and enrollment + - name: Teams Admin Center items: - - name: Voice and face recognition - href: rooms/voice-and-face-recognition.md - - name: Voice recognition controls for Intelligent speakers - href: rooms/voice-recognition.md - - name: Use the recovery tool - href: rooms/recovery-tool.md - - name: Known issues - href: /microsoftteams/troubleshoot/teams-devices-and-rooms/rooms-known-issues - - name: Microsoft Teams Rooms Pro Management - items: - - name: Getting started - items: - - name: Overview - href: rooms/rooms-pro-management.md - - name: Accessing the Pro Management portal - href: rooms/enrolling-mtrp-managed-service.md - - name: Enroll a device into Pro management - href: rooms/enroll-a-device.md - - name: Role-based access control - href: rooms/rooms-pro-rbac.md - - name: Resource accounts - href: rooms/resource-accounts.md - - name: Bring your own device (BYOD) spaces - items: - - name: Bring Your Own Device (BYOD) - href: rooms/bring-your-own-device.md - - name: Bookable Desks - href: rooms/bookable-desks.md - - name: Add peripherals to inventory - href: rooms/get-peripheral-information.md - - name: Planning and deployment - items: - - name: Standards and Rooms Planner - href: rooms/standards-and-room-planner.md - - name: Create a one-time password - href: rooms/create-otp.md - - name: Set up using one-time passwords - href: rooms/first-time-setup.md - - name: AutoPilot and Autologin - href: rooms/autopilot-autologin.md - - name: Monitoring and maintenance - items: - - name: Managing your inventory - href: rooms/inventory.md - - name: Monitoring and maintaining Teams Rooms - href: rooms/managed-meeting-rooms-portal.md - - name: Signal settings - href: rooms/signal-settings.md - - name: Remotely access a Teams Room console - href: rooms/remotely-access-teams-rooms.md - - name: Managed updates - href: rooms/update-management.md - - name: Configure ServiceNow - href: rooms/microsoft-teams-rooms-configure-servicenow.md - - name: Audit logs for activities - href: rooms/multi-tenant-auditing.md - - name: Viewing events - href: rooms/view-events.md - - name: Record an issue - href: rooms/customer-reported-incidents.md - - name: Multi-tenant management for partners - href: rooms/multi-tenant-management-partner.md - - name: Multi-tenant management for customers - href: rooms/multi-tenant-management-customer.md - - name: Analytics, reports, and insights - items: - - name: Health and usage reports - href: rooms/health-and-usage-reports.md - - name: Data and privacy information - href: rooms/data-and-privacy-info.md - - name: Devices - items: - - name: Phones for Teams - href: devices/phones-for-teams.md - - name: Teams panels - items: - - name: Overview - href: devices/overview-teams-panels.md - - name: Plan - href: devices/teams-panels.md - - name: Manage + - name: Overview + href: rooms/rooms-manage.md + - name: Manage your devices + href: devices/device-management.md + - name: Manage Teams device tags + href: devices/manage-device-tags.md + - name: Update your devices remotely + href: devices/remote-update.md + - name: RBAC using administrative units + href: administrative-unit.md + - name: Teams device health + href: teams-device-health.md + - name: Teams device health monitoring + href: alerts/device-health-status.md + - name: Health and usage reports + href: rooms/health-and-usage-reports.md + - name: Teams Rooms Pro Management items: - - name: Feature management - items: - - name: Use Teams panels - href: devices/use-teams-panels.md - - name: App support on Teams panels - href: app-support-on-Teams-panels.md - - name: Check-in and auto release - href: devices/check-in-and-room-release.md - - name: Reserve rooms with a QR code - href: devices/reserving-rooms-with-a-qr-code.md - - name: Manage custom backgrounds - href: devices/custom-background-panels.md - - name: SIP gateways + - name: Getting started + items: + - name: Overview + href: rooms/rooms-pro-management.md + - name: Accessing the Pro Management portal + href: rooms/enrolling-mtrp-managed-service.md + - name: Enroll a device into Pro management + href: rooms/enroll-a-device.md + - name: Resource accounts + href: rooms/resource-accounts.md + - name: Manage + items: + - name: Managing your inventory + href: rooms/inventory.md + - name: Standards and Rooms Planner + href: rooms/standards-and-room-planner.md + - name: Remotely access a Teams Room console + href: rooms/remotely-access-teams-rooms.md + - name: Managed updates + href: rooms/update-management.md + - name: Role-based access control + href: rooms/rooms-pro-rbac.md + - name: Multi-tenant management for partners + href: rooms/multi-tenant-management-partner.md + - name: Multi-tenant management for customers + href: rooms/multi-tenant-management-customer.md + - name: Alerting + items: + - name: Signal settings + href: rooms/signal-settings.md + - name: Configure ServiceNow + href: rooms/microsoft-teams-rooms-configure-servicenow.md + - name: Viewing events + href: rooms/view-events.md + - name: Record an issue + href: rooms/customer-reported-incidents.md + - name: Analytics, reports, and insights + items: + - name: Monitor and maintain Teams Rooms + href: rooms/managed-meeting-rooms-portal.md + - name: Audit logs for activities + href: rooms/multi-tenant-auditing.md + - name: Data and privacy information + href: rooms/data-and-privacy-info.md + - name: Troubleshooting and known issues + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/get-support-teams-rooms-pro-management + - name: Teams phones + items: + - name: Plan items: - - name: Plan for SIP Gateway - href: sip-gateway-plan.md - - name: Configure SIP Gateway - href: sip-gateway-configure.md - - name: Dynamic filters - href: sip-gateway-dynamic-filters.md + - name: Overview of Teams phones + href: phones/phones-for-teams.md + - name: What's new in Teams phones + href: https://support.microsoft.com/office/what-s-new-in-microsoft-teams-devices-eabf4d81-acdd-4b23-afa1-9ee47bb7c5e2#ID0EBD=Desk_phones - name: Deploy items: - - name: Plan phones and displays deployment - href: devices/plan-device-deployment.md - - name: Set up common area phones - href: set-up-common-area-phones.md - - name: Set up a common area mobile phones - href: devices/common-area-mobile-phones.md - - name: Remote provisioning and sign-in - href: devices/remote-provision-remote-login.md - - name: Remote sign in and sign out - href: devices/remote-sign-in-and-sign-out.md - - name: Deploy Teams phones and Teams panels using Intune - href: devices/phones-panels-deploy.md - - name: Authentication best practices for Android devices - href: devices/authentication-best-practices-for-android-devices.md - - name: AOSP device management - href: rooms/android-migration-guide.md + - name: Step 1 - Overview + href: phones/plan-device-deployment.md + - name: Step 2 - Prepare your environment + items: + - name: Prepare your network + href: phones/prepare-network-teams-phones.md + - name: Quality of Service (QoS) for Teams phone + href: phones/qos-on-teams-phones.md + - name: Intune Enrollment for Teams phones + items: + - name: Device administration + href: phones/phones-deploy.md + - name: AOSP device management + href: rooms/android-migration-guide.md + - name: Authentication best practices for Teams phone + href: phones/authentication-best-practices-phones.md + - name: Step 3 - Set up and configure + items: + - name: Set up common area phones + href: phones/set-up-common-area-phones.md + - name: Set up a common area mobile phones + href: phones/common-area-mobile-phones.md + - name: Step 4 - Set up Teams phones + items: + - name: Remote provisioning + href: phones/remote-provision-remote-login-phones.md + - name: Remote sign in and sign out + href: phones/remote-sign-in-and-sign-out-phones.md - name: Manage items: - - name: Manage your devices in Teams - href: devices/device-management.md - - name: Use administrative units to manage devices - href: administrative-unit.md - - name: Manage Teams device tags - href: devices/manage-device-tags.md - - name: Update your devices remotely - href: devices/remote-update.md - - name: Feature management - items: - - name: QoS on Teams devices - href: devices/qos-on-teams-devices.md - - name: RealWear for Teams - href: flw-realwear.md - - name: Monitor - items: - - name: Teams device health monitoring - href: alerts/device-health-status.md - - name: Teams devices and peripherals - href: teams-device-health.md + - name: Set the Teams phone interface + href: phones/teams-android-devices-user-interface.md + - name: Line keys for speed dialing + href: phones/line-keys.md + - name: Manage Teams phones + href: phones/manage-teams-phones.md + - name: Update management + href: phones/remote-update-teams-phones.md + - name: Troubleshooting and known issues + href: /microsoftteams/troubleshoot/teams-rooms-and-devices/teams-rooms-known-issues-android.md#issues-with-teams-phones + + - name: Bring your own device (BYOD) spaces + items: + - name: BYOD rooms + href: rooms/bring-your-own-device.md + - name: Bookable desks + href: rooms/bookable-desks.md + - name: Set up your BYOD inventory + href: rooms/get-peripheral-information.md + - name: SIP Gateway + items: + - name: Plan for SIP Gateway + href: devices/sip-gateway-plan.md + - name: Configure SIP Gateway + href: devices/sip-gateway-configure.md + - name: Dynamic filters + href: devices/sip-gateway-dynamic-filters.md + - name: Known issues + href: /microsoftteams/troubleshoot/phone-system/sip-gateway-issues - name: Reference items: - name: Teams displays overview href: devices/teams-displays.md - - name: Hot desking Teams Displays + - name: Hot desking Teams displays href: devices/hot-desking-teams-displays.md - name: Manage apps in Teams @@ -1602,6 +1697,8 @@ items: href: manage-lists-app.md - name: Manage the Planner app href: manage-planner-app.md + - name: Manage app-powered tasks in the Planner app + href: app-powered-tasks-in-planner.md - name: Manage the Praise app href: manage-praise-app.md - name: Manage the Approvals app @@ -1650,15 +1747,15 @@ items: items: - name: Overview of app management href: manage-apps.md - - name: Policies for app access and rollout - items: + - name: Policies to access and install apps + items: - name: Understand app policies href: app-policies.md - - name: Manage app permission policies + - name: Manage permission policies for availability href: teams-app-permission-policies.md - - name: Manage app setup policies + - name: Manage setup policies for installation href: teams-app-setup-policies.md - - name: Use or migrate to app centric management + - name: Use app centric management href: app-centric-management.md - name: Preinstall apps for users href: install-teams-apps.md @@ -1680,6 +1777,8 @@ items: href: audit-app-management-activities.md - name: View app usage report and analytics href: teams-analytics-and-reports/app-usage-report.md + - name: Take ownership of your org's apps + href: app-ownership-developer-portal.md - name: Industries and government guidance items: diff --git a/Teams/toll-free-dialing-limitations-and-restrictions.md b/Teams/toll-free-dialing-limitations-and-restrictions.md index 22abbd12c2..4b48b31377 100644 --- a/Teams/toll-free-dialing-limitations-and-restrictions.md +++ b/Teams/toll-free-dialing-limitations-and-restrictions.md @@ -1,7 +1,7 @@ --- title: "Toll-free dialing limitations and restrictions" -ms.author: crowe -author: CarolynRowe +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen ms.reviewer: mikedav, roykuntz, jastark, oscarr ms.date: 11/28/2017 diff --git a/Teams/town-hall-chat.md b/Teams/town-hall-chat.md new file mode 100644 index 0000000000..0cdc99998b --- /dev/null +++ b/Teams/town-hall-chat.md @@ -0,0 +1,101 @@ +--- +title: Manage event chat for Microsoft Teams town halls +ms.author: wlibebe +author: wlibebe +manager: pamgreen +ms.reviewer: chbalaki +ms.date: 11/11/2024 +ms.topic: article +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +appliesto: + - Microsoft Teams +ms.localizationpriority: medium +search.appverid: MET150 +f1.keywords: +- CSH +ms.custom: +ms.collection: + - M365-collaboration + - m365initiative-meetings + - highpri + - Tier1 +description: Learn how to manage which organizers can use event chat for their Microsoft Teams town halls. +--- + +# Manage event chat for Microsoft Teams town halls + +**APPLIES TO:** ![Image of a x for no](/office/media/icons/cancel-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Town halls + +[!INCLUDE[Teams Premium](includes/teams-premium-ecm.md)] + +> [!NOTE] +> This feature is currently in Public Preview. + +In Microsoft Teams town halls, only presenters, organizers, and co-organizers can use chat. If town hall organizers have a Teams Premium license, they can turn on **Event chat** in their **Meeting options** to allow attendees to a chat and interact with each other. Event chat is only available during the town hall. Organizers, presenters, and co-organizers can still chat separately. + +As an admin, you can manage whether town hall organizers with a Teams Premium license can turn on event chat for their attendees. + +For details on how your users use event chat for town halls, see [Chat in a town hall in Microsoft Teams](https://support.microsoft.com/office/chat-in-a-town-hall-in-microsoft-teams-a4a0e102-ca45-4605-a0a8-83a884547338). + +## Manage event chat for your organizers + +To manage whether town hall organizers with a Teams Premium license can turn on event chat for their attendees, use the **`-TownhallChatExperience`** parameter within the PowerShell [**CsTeamsEventsPolicy**](/powershell/module/teams/set-csteamseventspolicy) cmdlet. + +The following table shows the behaviors of the settings for the **`-TownhallChatExperience`** parameter: + +|Setting value| Behavior| +|---------|---------------| +|Optimized| **This is the default value.** Town hall organizers with this policy can turn on event chat for their attendees. | +|None| Town hall organizers with this policy can't turn on event chat for their attendees.| + +### Turn off event chat + +To turn off event chat, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -TownhallChatExperience None +``` + +### Turn on event chat + +To turn on event chat, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -TownhallChatExperience Optimized +``` + +## Event chat eDiscovery and storage + +Messages for event chat in town halls are only stored in the organizer's mailbox for up to 30 days. During this time, if you do a content search for the organizer, you can see all the messages that were sent in that event chat. +However, if you place the organizer’s mailbox on legal hold, the mailbox continues to keep the event chat messages for longer. + +When the organizer leaves the company anytime from when the event is scheduled to 30 days after the town hall ends, the following details apply: + +- Event chat might be unavailable during the town hall. +- Chat might be available during the event, but might not get sent to the organizer’s mailbox. +- Some messages aren't e-Discoverable in the organizer’s mailbox depending on when the organizer leaves the company. + +If a town hall organizer leaves the company, you should reschedule the town hall. + +You can't see which users viewed specific messages during the event. You also can't search for event chat messages in an attendee's mailbox. + +Learn more, see [Get started with Content search](/purview/ediscovery-content-search). + +## Limitations + +- If a town hall restarts, event chat isn't available in the new town hall. +- Attendees can only send up to 200 characters of text and emojis into the Event Chat. +- All other message composition options that are available in a [Teams Meeting chat](manage-meeting-chat.md) like sending pictures, sending GIFs, attaching files, or formatting text aren't supported. Hyperlinks are only supported if they're fewer than 200 characters. +- Attendees can't use `@` to mention others, reply to other chat messages using the 'Reply' function, or 'React' to messages. +- Event Chat is only available for attendees, presenters, and organizers during the town hall. Event chat isn't available before or after the town hall. +- During the town hall, attendees can only see the last 200 messages. +- Attendees sending chat messages might experience a 15-30 second latency from the presenters and organizers. + +## Related articles + +- [Plan for town halls](plan-town-halls.md) +- [Manage meetings chat](manage-meeting-chat.md) +- [Attendance report for meetings and webinars in Microsoft Teams](teams-analytics-and-reports/meeting-attendance-report.md) +- [Set-CsTeamsEventsPolicy](/powershell/module/teams/set-csteamseventspolicy) diff --git a/Teams/troubleshoot-installation.md b/Teams/troubleshoot-installation.md index 3948211863..2a1bb8e1ea 100644 --- a/Teams/troubleshoot-installation.md +++ b/Teams/troubleshoot-installation.md @@ -21,6 +21,9 @@ description: Learn how to troubleshoot installation and update issues for the Te # Troubleshoot classic Microsoft Teams installation and update issues on Windows +> [!IMPORTANT] +> The classic Team client is no longer supported. This client is not receiving further updates, including security updates. The classic Teams client will not work after June 30, 2025. You must upgrade to the new Teams client before that time. See [The new Microsoft Teams](new-teams-desktop-admin.md) for more information. + This article provides guidance for how to diagnose and troubleshoot installation and update issues for the Teams desktop client app running on Windows. For additional troubleshooting information, see [Teams troubleshooting](/MicrosoftTeams/troubleshoot/teams). [!Important] diff --git a/Teams/turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md b/Teams/turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md index 584047f84b..cbee10c7b4 100644 --- a/Teams/turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md +++ b/Teams/turn-on-or-off-entry-and-exit-announcements-for-meetings-in-teams.md @@ -4,7 +4,7 @@ ms.author: jenz author: jenzamora manager: pamgreen ms.reviewer: oscarr -ms.date: 12/14/2023 +ms.date: 10/16/2024 ms.topic: article ms.assetid: f2c7b5ea-07b6-4b77-8023-bec9596fcc32 ms.tgt.pltfrm: cloud @@ -28,18 +28,16 @@ description: Admin can learn about how to turn entry and exit announcements on o # Turn on or off entry and exit announcements for meetings in Microsoft Teams -When you set up Audio Conferencing in Microsoft 365 or Office 365, you get phone numbers for your users through an audio conferencing bridge. A conferencing bridge can have one or more phone numbers that are included at the bottom of the meeting invite. These phone numbers allow users to join Microsoft Teams meetings by dialing in. +When you set up Audio Conferencing in Microsoft 365 or Office 365, you provide users with phone numbers through an audio conferencing bridge. This bridge can have one or more phone numbers, which are included at the bottom of the meeting invite. These numbers allow users to join Microsoft Teams meetings by dialing in. -As an admin, you can manage whether an entry and exist announcement is played when participants who dialed into the meeting join or exit. +As an admin, you can control whether an entry and exit announcement is played when participants who dialed into the meeting join or leave. > [!NOTE] > [!INCLUDE [updating-admin-interfaces](includes/updating-admin-interfaces.md)] ## Setting meeting join options using the Microsoft Teams admin center -You must be a Teams service admin to make these changes. See [Use Teams administrator roles to manage Teams](./using-admin-roles.md) to read about getting admin roles and permissions. - -1. Navigate to **Meetings** > **Conference Bridges**. +1. Expand **Meetings** > **Conference Bridges**. 2. At the top of the **Conference Bridges** page, select **Bridge Settings**. @@ -56,9 +54,23 @@ You must be a Teams service admin to make these changes. See [Use Teams administ ## Turn on or off entry and exit announcements with PowerShell -To turn entry and exit announcements on or off with PowerShell, use the **`-EnableEntryExitNotifications`** parameter within the PowerShell CsOnlineDialInConferencingTenantSettings cmdlet. +To turn entry and exit announcements on or off with PowerShell, use the **`-EnableEntryExitNotifications`** parameter within the PowerShell [CsOnlineDialInConferencingTenantSettings](/powershell/module/teams/set-csonlinedialinconferencingtenantsettings) cmdlet. + +### Turn off entry and exit announcements + +To turn off entry and exit announcements, use the following script: + +```powershell +Set-CsOnlineDialInConferencingTenantSettings -EnableEntryExitNotifications $false +``` + +### Turn on entry and exit announcements + +To turn on entry and exit announcements, use the following script: -For CsOnlineDialInConferencingBridge script examples, see [Set-CsOnlineDialInConferencingBridge](/powershell/module/teams/Set-csonlinedialinconferencingtenantsettings). +```powershell +Set-CsOnlineDialInConferencingTenantSettings -EnableEntryExitNotifications $true +``` ## Related topics diff --git a/Teams/user-call-settings.md b/Teams/user-call-settings.md index 515e1dd413..4081bf6032 100644 --- a/Teams/user-call-settings.md +++ b/Teams/user-call-settings.md @@ -1,7 +1,7 @@ --- title: Configure call forwarding and delegation settings -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: jenstr ms.date: 11/17/2023 diff --git a/Teams/vdi-2.md b/Teams/vdi-2.md index 7623e745c2..8ed5315f43 100644 --- a/Teams/vdi-2.md +++ b/Teams/vdi-2.md @@ -40,9 +40,9 @@ New VDI solution for Teams is a new architecture for optimizing the delivery of |Requirement |Minimum version | |----------------------------------|----------------| -|New Teams |24193.1805.3040.8975 (for Azure Virtual Desktop/Windows 365)
    24165.1410.2974.6689 (for Citrix single session VDAs)
    24243.1309.3132.617 (for Citrix multi-session VDAs) | +|New Teams |24193.1805.3040.8975 (for Azure Virtual Desktop/Windows 365)
    24295.605.3225.8804 (for Citrix) | |Azure Virtual Desktop/Windows 365 |Windows App: 1.3.252
    Remote Desktop Client: 1.2.5405.0 | -|Citrix |VDA: 2203 LTSR CU3 or 2305 CR
    Citrix Workspace app: 2203 LTSR (any CU), 2402 LTSR, or 2302 CR | +|Citrix |VDA: 2203 LTSR CU3 or 2305 CR
    Citrix Workspace app: 2203 LTSR (any CU), 2402 LTSR, or 2302 CR
    MsTeamsPluginCitrix: 2024.41.1.1 | |Endpoint |Windows 10 1809 (SlimCore minimum requirement)
    GPOs must not block MSIX installations (see [Step 3: SlimCore MSIX staging and registration on the endpoint](#step-3-slimcore-msix-staging-and-registration-on-the-endpoint))
    Minimum CPU: Intel Celeron (or equivalent) @ 1.10 GHz, 4 Cores, Minimum RAM: 4 GB | ## Optimizing with new VDI solution for Teams @@ -385,11 +385,13 @@ The new Teams client requires three custom virtual channels to function: MSTEAMS 2. The VDA machines must be rebooted for the policy to take effect. -#### Citrix App Protection and Microsoft Teams compatibility +#### Screen sharing + +##### Citrix App Protection and Microsoft Teams compatibility Users who have App Protection enabled can still share their screen and apps while using the new optimization. Sharing requires VDA version 2402 or higher, and CWA for Windows 2309.1 or higher. Users on lower versions end up sharing a black screen instead when the App Protection module is installed and enabled. -#### AVD Screen Capture Protection and Microsoft Teams compatibility +##### AVD Screen Capture Protection and Microsoft Teams compatibility Users who have [Screen Capture Protection](/azure/virtual-desktop/screen-capture-protection?tabs=intune) (SCP) enabled can't share their screens or apps. Other people on the call can only see a black screen. If you want to allow users to share their screen even with SCP enabled, you need to disable SlimCore optimization in the Teams Admin Center policy (so the user is optimized with WebRTC), and set the SCP policy to **Block screen capture on client**. @@ -399,6 +401,9 @@ Call Quality Dashboard (CQD) allows IT Pros to use aggregate data to identify pr VDI user information is now exposed through numerous dimensions and filters. Check [this page](dimensions-and-measures-available-in-call-quality-dashboard.md) for more information about each dimension. +> [!NOTE] +> The new Quality of Experience (QER) template is available in the Power BI query templates for CQD download. Version 8 now includes templates for reviewing VDI client-focused metrics. + ##### Query fundamentals A well-formed CQD query/report contains all three of these parameters: @@ -498,6 +503,8 @@ The code logged here needs to be mapped using this table: |1722 | |RPC_S_SERVER_UNAVAILABLE |'The RPC server is unavailable' MsTeamsVdi.exe related error. | |2000 |16002 |No Plugin |Endpoint doesn't have the MsTeamsPlugin, or if it has it, it didn't load (check with Process Explorer). | |2001 | |Virtual Channel Not Available |Error on Citrix VDA WFAPI. | +|2003 |16026 |Custom Virtual Channels (MSTEAMS, MSTEAM1 and MSTEAM2) are blocked due to a Citrix Studio policy |Review the [Citrix virtual channel allow list](#citrix-virtual-channel-allow-list) section of this article. | +|2005 |16043 |Teams is running as a Published App (Citrix) or RemoteApp (AVD/Windows 365) |This mode is currently not supported - Teams will not load SlimCore in this case, and users will always be optimized with WebRTC. | |3000 |24002 |SlimCore Deployment not needed |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | |3001 |24010 |SlimCore already loaded |This code isn't really an error. It's a good indicator that the user is on the new optimization architecture with SlimCore. | |3004 |24035 |Plugin irresponsive |Try restarting RDP or ICA session. | diff --git a/Teams/view-only-meeting-experience.md b/Teams/view-only-meeting-experience.md index 22e6e647ad..284f9e0619 100644 --- a/Teams/view-only-meeting-experience.md +++ b/Teams/view-only-meeting-experience.md @@ -3,7 +3,7 @@ title: View-only meeting experience ms.author: wlibebe author: wlibebe ms.reviewer: christi.balaki -ms.date: 3/4/2024 +ms.date: 9/26/2024 manager: pamgreen ms.topic: article audience: admin @@ -22,15 +22,17 @@ appliesto: # Teams view-only meeting experience -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls -Microsoft Teams supports up to 10,000 attendees in a meeting. Once the main meeting reaches capacity at 1,000 users, additional attendees join with a view-only experience. Attendees in the view-only experience can view the meeting, but have limited access to meeting features. Meeting organizers see notifications for the view-only experience when around 500 users are in the meeting. +Microsoft Teams supports up to 10,000 attendees in a meeting. Once the main meeting reaches capacity at around 900 users, additional attendees join with a view-only experience. Attendees in the view-only experience can view the meeting, but have limited access to meeting features. Meeting organizers see notifications for the view-only experience when around 500 users are in the meeting. -Initial attendees who join before the meeting capacity enjoy full meeting experience. These attendees can share audio/video, see shared content, and participate in chat. +Initial attendees who join before the meeting capacity enjoy the full meeting experience. These attendees can share audio/video, see shared content, and participate in chat. Attendees who join after the main meeting capacity is reached have a view-only experience. These attendees can join the view-only experience through desktop, web, and Teams mobile (Android and iOS). -As an admin, you can decide if organizers with this policy have the view-only experience attendees join after the 1,000 user capacity. If you disable the view-only experience, meeting attendance is limited to the first 1,000 attendees. +As an admin, you can assign this policy to your organizers. This policy allows attendees who join the meeting after the 900-user capacity is reached to have a view-only experience. If you turn off the view-only experience, the meeting is limited to the first 1,000 attendees. + +To learn how to monitor, scale, and optimize the distribution of video during view-only meetings, see [Enterprise content delivery networks for streaming Microsoft Teams events](streaming-ecdn-enterprise-content-delivery-network.md). ## Teams view-only experience controls @@ -65,7 +67,7 @@ When the capacity of the main meeting is reached, meeting attendees are informed ![the Teams pre-join screen and the message for participants telling them that they will join in view-only mode.](media/view-only-pre-join-screen.png) -Before the meeting reaches capacity, attendees always join the main meeting. If the main meeting reaches capacity and attendees leave, new space becomes available, allowing new attendees to join the main meeting until it fills up again. View-only attendees can't be promoted to the main meeting. +Before the meeting reaches capacity, attendees always join the main meeting. Once the meeting reaches capacity, view-only attendees can't be promoted to the main meeting. If presenter and attendee roles are set, presenters who join after capacity is reached in the main meeting become view-only attendees. These presenters have the same limitations as other view-only attendees. Organizers are always guaranteed space in the main meeting. diff --git a/Teams/virtual-appointment-meeting-template.md b/Teams/virtual-appointment-meeting-template.md index c0dc2ed4ae..9baea6570a 100644 --- a/Teams/virtual-appointment-meeting-template.md +++ b/Teams/virtual-appointment-meeting-template.md @@ -6,7 +6,7 @@ manager: jtremper ms.topic: conceptual ms.service: msteams ms.reviewer: jewilcze -ms.date: 09/13/2024 +ms.date: 11/11/2024 search.appverid: MET150 searchScope: - Microsoft Teams @@ -24,7 +24,7 @@ appliesto: # Manage the Virtual appointment meeting template in Microsoft Teams -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a x for no](/office/media/icons/cancel-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls ![Information icon](media/info.png) **Some features described in this article require [Teams Premium](teams-add-on-licensing/licensing-enhance-teams.md)**. @@ -51,9 +51,9 @@ To learn more, see [Manage meeting templates in Teams](manage-meeting-templates. ![Information icon](media/info.png) **This is a [Teams Premium](teams-add-on-licensing/licensing-enhance-teams.md) feature. Meeting organizers must have a Teams Premium license to use this feature.**. > [!NOTE] -> This feature is currently available in Canada, the United Kingdom, and the United States. Your users can only send SMS text notifications to people who have a valid Canada phone number (+1 country code), United Kingdom phone number (+44 country code), or United States phone number (+1 country code). SMS text notifications are sent in English. +> This feature is currently available in Canada, the Netherlands, New Zealand, Norway, the United Kingdom, and the United States. Your users can send SMS text notifications to people who have a valid Canada (+1 country code), Netherlands (+31 country code), New Zealand (+64 country code), Norway (+47 country code), United Kingdom (+44 country code), or United States phone number (+1 country code). The text notifications are sent in the language of the meeting organizer. -You can control whether your users can choose to send SMS text notifications to external guests in appointments that they schedule using the template. When this feature is enabled for a user, they'll see the SMS notifications option in the template. +You can control whether your users can choose to send SMS text notifications to external guests in appointments that they schedule using the template. When this feature is enabled for a user, they see the SMS notifications option in the template. - If the user chooses **Send text notifications** (the default setting), external guests will receive appointment confirmation, update, and reminder text messages that include the Teams meeting join link and appointment details. - If the user chooses **Don't send text notifications**, external guests won't receive text messages about their appointment. @@ -94,6 +94,8 @@ You can assign the policy directly to users, either individually or at scale thr - If a user who has access to this feature chose **Send text notifications** when they scheduled an appointment, and then their access is turned off, no additional text messages are sent to the external guest. +- For the Netherlands, the **Phone number** field on the form might require an 11-digit number to successfully send SMS notifications. If you experience issues, add zeros (0) to the beginning of the phone number to reach an 11-digit value. + ### SMS notifications usage report To get an overview of SMS notifications usage across your organization, view the [SMS notifications usage report](/microsoft-365/frontline/sms-notifications-usage-report) in the Teams admin center. diff --git a/Teams/voice-case-study-audio-conferencing.md b/Teams/voice-case-study-audio-conferencing.md index d4b661b7e2..bd8863e98b 100644 --- a/Teams/voice-case-study-audio-conferencing.md +++ b/Teams/voice-case-study-audio-conferencing.md @@ -1,7 +1,7 @@ --- title: 'Teams voice Contoso case study: Audio Conferencing' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-case-study-call-queues.md b/Teams/voice-case-study-call-queues.md index 2af1be71f3..a51a19e83b 100644 --- a/Teams/voice-case-study-call-queues.md +++ b/Teams/voice-case-study-call-queues.md @@ -1,7 +1,7 @@ --- title: 'Teams voice Contoso case study: Auto attendants and call queues' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article @@ -34,7 +34,7 @@ Depending on the site type, Contoso had the following needs: - Site Type B: Skype for Business Enterprise Voice - Site Type B had existing auto attendants and call queues that needed to migrate to Teams. Contoso needed to keep the phone numbers associated with the auto attendants. Contoso moved the majority of these sites to Phone System with Calling Plans. However, in the few locations where Calling Plans was not available, Contoso moved these sites to a Direct Routing configuration. + Site Type B had existing auto attendants and call queues that needed to migrate to Teams. Contoso needed to keep the phone numbers associated with the auto attendants. Contoso moved most these sites to Phone System with Calling Plans. However, in the few locations where Calling Plans wasn't available, Contoso moved these sites to a Direct Routing configuration. - Site Type C: Skype for Business Enterprise Voice & traditional legacy telephony system @@ -51,7 +51,7 @@ Depending on the site type, Contoso had the following needs: - Q: How will the calls be routed to members in a call queue: attendant, serial, or round robin routing? A: Contoso decided to use Attendant routing, - - Q: How will we determine when a user should or should not get a call? + - Q: How will we determine when a user should or shouldn't get a call? A: Contoso decided to use call handling options to determine if the agent is available: presence-based routing. ## Configuration @@ -76,7 +76,7 @@ The steps to set up an auto attendant and a call queue include the following out Contoso had to set up the phone number provided by the local carrier as the service number in Office 365. -- To set up a phone number available through Direct Routing, Contoso followed the instructions located in [Manage Resource Accounts](manage-resource-accounts.md). Because Office 365 is not aware of the on-premises phone numbers, Contoso used PowerShell to complete the setup. +- To set up a phone number available through Direct Routing, Contoso followed the instructions located in [Manage Resource Accounts](manage-resource-accounts.md). Because Office 365 isn't aware of the on-premises phone numbers, Contoso used PowerShell to complete the setup. - To configure the Cloud auto attendant, Contoso followed the steps outlined in [Set up a Cloud auto attendant](create-a-phone-system-auto-attendant.md). diff --git a/Teams/voice-case-study-emergency-calling.md b/Teams/voice-case-study-emergency-calling.md index ceafb65730..d0901d616f 100644 --- a/Teams/voice-case-study-emergency-calling.md +++ b/Teams/voice-case-study-emergency-calling.md @@ -1,7 +1,7 @@ --- title: 'Teams voice Contoso case study: Emergency calling' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-case-study-location-based-routing.md b/Teams/voice-case-study-location-based-routing.md index 621203cdb4..22687024b3 100644 --- a/Teams/voice-case-study-location-based-routing.md +++ b/Teams/voice-case-study-location-based-routing.md @@ -1,7 +1,7 @@ --- title: 'Teams voice Contoso case study: Location-based routing' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-case-study-migration-plan.md b/Teams/voice-case-study-migration-plan.md index 97a2cca5fb..5c3a947d30 100644 --- a/Teams/voice-case-study-migration-plan.md +++ b/Teams/voice-case-study-migration-plan.md @@ -1,7 +1,7 @@ --- title: Teams voice Contoso case study upgrade plan -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-case-study-overview.md b/Teams/voice-case-study-overview.md index 955bfd2e24..ca4fccf7a3 100644 --- a/Teams/voice-case-study-overview.md +++ b/Teams/voice-case-study-overview.md @@ -1,7 +1,7 @@ --- title: Teams voice Contoso case study overview -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-case-study-phone-system.md b/Teams/voice-case-study-phone-system.md index c58a167b4f..187ad4338a 100644 --- a/Teams/voice-case-study-phone-system.md +++ b/Teams/voice-case-study-phone-system.md @@ -1,7 +1,7 @@ --- title: 'Contoso case study: Phone System for a multi-national corporation' -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.date: 06/17/2020 ms.topic: article diff --git a/Teams/voice-isolation.md b/Teams/voice-isolation.md index 4b8cffed6f..eefa4bb708 100644 --- a/Teams/voice-isolation.md +++ b/Teams/voice-isolation.md @@ -26,7 +26,7 @@ description: Learn how to manage whether users can use voice isolation for IT Ad # Manage voice isolation for your users' Microsoft Teams calls and meetings -**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Town halls ✔️Calls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Calls Voice isolation reduces noise and uses the personalized deep voice quality enhancement artificial intelligence (AI) model to separate the user's voice from other sounds and voices in Microsoft Teams calls and meetings. As an admin, you can control whether your users can use voice isolation in calls and meetings. @@ -34,13 +34,7 @@ The voice isolation feature relies on the voice profile, stored on the user's lo To learn about enrollment, see [Overview of voice and face enrollment](/microsoftteams/rooms/voice-and-face-recognition). -To learn more about voice isolation troubleshooting, setup, and the experience for your users, see [Voice isolation in Microsoft Teams calls and meetings](https://prod.support.services.microsoft.com/office/voice-isolation-in-microsoft-teams-calls-and-meetings-a9756ea9-4cec-44c4-aefb-6f5d17c89427). - -## Prerequisites - -Verify that the following URL is included in your allowlist: - -- https://aiinfrastructure.static.microsoft/public/aiinfrastructure/tsg_model_file/d1579e8339689379a218e26beea3825b68b9e75ec9dbb41aeb2be78510fead3c/model.gz +To learn more about voice isolation troubleshooting, setup, and the experience for your users, see [Voice isolation in Microsoft Teams calls and meetings](https://support.microsoft.com/office/voice-isolation-in-microsoft-teams-calls-and-meetings-a9756ea9-4cec-44c4-aefb-6f5d17c89427). ## Manage whether your users can use voice isolation @@ -82,12 +76,9 @@ Set-CsTeamsMeetingPolicy -Identity -VoiceIsolation Disabled ## Related topics +- [Overview of voice and face enrollment](/microsoftteams/rooms/voice-and-face-recognition) - [Plan for meetings with external participants in Microsoft Teams](plan-meetings-external-participants.md) - [Plan for meetings](plan-meetings.md) - [Meetings, webinars, and live events overview](quick-start-meetings-live-events.md) - [Feature comparison](meeting-webinar-town-hall-feature-comparison.md) -- [New-CsTeamsMeetingPolicy](/powershell/module/teams/new-csteamsmeetingpolicy) - [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) -- [Grant-CsTeamsMeetingPolicy](/powershell/module/teams/grant-csteamsmeetingpolicy) -- [Get-CsTeamsMeetingPolicy](/powershell/module/teams/get-csteamsmeetingpolicy) -- [Remove-CsTeamsMeetingPolicy](/powershell/module/teams/remove-csteamsmeetingpolicy) diff --git a/Teams/walkie-talkie.md b/Teams/walkie-talkie.md index 04ae542f00..eeeb265410 100644 --- a/Teams/walkie-talkie.md +++ b/Teams/walkie-talkie.md @@ -19,7 +19,7 @@ ms.collection: appliesto: - Microsoft Teams - Microsoft 365 for frontline workers -ms.date: 02/27/2024 +ms.date: 10/09/2024 --- # Manage the Walkie Talkie app in Microsoft Teams @@ -84,12 +84,18 @@ Pin Walkie Talkie to Teams for easy access. This step depends on which license y #### E license: Use an app setup policy to pin Walkie Talkie to Teams +> [!NOTE] +> If your users have an E licence and [Public preview is enabled in Teams](public-preview-doc-updates.md), Walkie Talkie is pre-pinned to the app bar. + App setup policies let you customize Teams to pin apps that are most important for your users in your users. To pin the Walkie Talkie app for your users, you can edit the global (Org-wide default) policy or create and assign a custom policy in app setup policy. To learn more, see [Use app setup policies to pin and auto-install apps for users](teams-app-setup-policies.md). :::image type="content" source="media/deploy-walkie-talkie-2.png" alt-text="Screenshot showing adding Walkie Talkie to the pinned apps list in the Add pinned apps pane." lightbox="media/deploy-walkie-talkie-2.png"::: +> [!NOTE] +> If you're pinning more than 10 apps, Walkie Talkie must be added to one of the first 10 slots in the list. + #### F license: Use the Tailored frontline app experience to pin Walkie Talkie and other apps to Teams The tailored frontline app experience in Teams pins the most relevant apps in Teams for users who have an [F license](https://www.microsoft.com/microsoft-365/enterprise/frontline#office-SKUChooser-0dbn8nt). Pinned apps include Walkie Talkie, Shifts, Tasks, and Approvals. By default, this feature is on, giving your frontline workers an out-of-the-box experience tailored to their needs. diff --git a/Teams/watermark-meeting-content-video.md b/Teams/watermark-meeting-content-video.md index fd18ac08ab..a929410f3c 100644 --- a/Teams/watermark-meeting-content-video.md +++ b/Teams/watermark-meeting-content-video.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: mudrapatel -ms.date: 12/14/2023 +ms.reviewer: maahma +ms.date: 11/12/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -23,13 +23,13 @@ description: Learn how to enable or require watermarks on attendee video and sha # Require a watermark for sensitive Teams meetings -**APPLIES TO:** ✔️Meetings ✖️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -You can enable a watermark to be displayed in Teams meetings both for content shared on screen and for attendee video. The watermark displays the email address of the meeting participant. Each participant will see their own email address overlaid on the meeting video or shared content. This deters participants from taking unauthorized screenshots of the meeting content. +As an admin, can allow organizers with a Teams Premium license to turn on watermarks in Teams meetings both for content shared on screen and for participant's video. The watermark displays the email address of the meeting participant. Each participant sees their own email address overlaid on the meeting video or shared content. Watermarks deter participants from taking unauthorized screenshots of the meeting content. To understand how your organizers use watermarks, see [Watermark for Teams meetings](https://support.microsoft.com/office/watermark-for-teams-meetings-a9166432-f429-4a19-9a72-c9e8fdf4f589). -Watermarks are supported on Teams desktop, mobile, and Microsoft Teams Rooms. People joining meetings from unsupported platforms will have an audio-only experience. +Watermarks are supported on Teams desktop, mobile, and Microsoft Teams Rooms. Users joining meetings from unsupported platforms have an audio-only experience. The following participants have an audio-only experience when a watermark is in use: @@ -39,10 +39,12 @@ The following participants have an audio-only experience when a watermark is in - Older Teams clients - [Direct Guest Join on Microsoft Teams Rooms devices](/microsoftteams/rooms/third-party-join) +:::image type="content" source="media/watermark-small.png" alt-text="Screenshot of Contoso Education's meeting theme featuring their brand logo, image, and colors." lightbox="media/watermark-expand.png"::: + > [!NOTE] -> Meeting settings in sensitivity labels, custom meeting templates, and watermarks require Teams Premium. +> Meeting settings in sensitivity labels and custom meeting templates require a Teams Premium license. -Meeting watermarks are enabled in the Teams admin center. They can then be added by the meeting organizer (the organizer must have a Teams Premium license) or enforced by a template or sensitivity label. +Meeting watermarks are managed in the Teams admin center. After you turn on watermarks, organizers with a Teams Premium license can add them to their meetings, or you can enforce watermarks with a template or sensitivity label. The following table shows where watermarks are configured: @@ -54,44 +56,38 @@ The following table shows where watermarks are configured: When a watermark is being used in a meeting, the following features are turned off: - Large gallery - - Together mode - - Content from camera ## Watermarks for sensitive and highly sensitive meetings -Watermarks can be useful for protecting confidential information shared in meetings. This is most useful when sharing information with people who don't normally have access to the information. For example, a member of the finance organization might use watermarks when sharing quarterly estimates with managers from different divisions. +Watermarks can be useful for protecting confidential information shared in meetings. This is most useful when sharing information with users who don't normally have access to the information. For example, a member in the finance organization might use watermarks when sharing quarterly estimates with managers from different divisions. -Since watermarks are designed to reduce the chances that confidential information will be exfiltrated, using them in meetings where all the participants have direct access to the content being shared may not add to security. +Watermarks are designed to reduce the chances that confidential information being transferred out. Using watermarks in meetings where all the participants have direct access to the content being shared might not add to security. For information about using watermarks with other meeting features to help protect confidential information in meetings, see [Configure Teams meetings with protection for highly sensitive data](/microsoftteams/configure-meetings-highly-sensitive-protection). ## Meeting recordings -If a meeting with a watermark is recorded, the watermark is applied at playback time by Microsoft Stream. Viewers of the recording see their own email address as a watermark on the video. If the recording file is edited or moved, the watermark won't be available at playback time. - -By default, download of the meeting recording (.mp4) file is disabled for recordings of meetings with a watermark. However, the person who recorded the meeting can change that permission. Downloaded .mp4 files don't contain a watermark. - -## Configure watermarks +If a meeting with a watermark is recorded, Microsoft Stream applies the watermark at playback time. Viewers of the recording see their own email address as a watermark on the video. If the recording file is edited or moved, the watermark isn't available at playback time. -For watermarks to be available to the meeting organizer, they must be enabled in the Teams admin center. (Watermarks are enabled by default.) Note that sensitivity labels can enforce watermarks even if they're turned off for the meeting organizer in the Teams admin meeting policy. +By default, download of the meeting recording (.mp4) file is turned off for watermarked meeting recordings. However, the user who recorded the meeting can change that permission. Downloaded .mp4 files don't contain a watermark. -To configure watermarking for meetings +## Manage watermarks -1. In the Teams admin center, expand **Meetings** and select **Meeting policies** > **Content Protection**. +You can turn on watermarks for your organizers in the Teams admin center. You can use sensitivity labels to enforce watermarks even if you turn them off for the meeting organizer in this meeting policy. -1. Select the policy you want to update. +To manage watermarks for meetings, follow these steps: -1. To configure watermark on attendee video, set **Watermark videos** to **On** or **Off**. +1. In the Teams admin center, expand **Meetings** and select **Meeting policies**. +2. Either select an existing policy or create a new one. +3. Within your chosen policy, navigate to the **Content Protection** section. +4. For watermarks on attendee video, toggle **Watermark videos** to **On** (default) or **Off**. +5. For watermarks on content shared on screen in a meeting, toggle **Watermark shared content** to **On** or **Off**. +6. To set the watermark pattern or transparency, or see a preview, select **Edit settings**. Select **Apply** if you make changes. +7. Select **Save**. -1. To configure watermark on content shared on screen in a meeting, set **Watermark shared content** to **On** or **Off**. - -1. To set the watermark pattern or transparency, or see a preview, select **Edit settings**. Select **Apply** if you make changes. - -1. Select **Save**. - -You can also enable or disable watermarks by using PowerShell. Use the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet with the `-AllowWatermarkForCameraVideo` and `-AllowWatermarkForScreenSharing` parameters. +You can also turn watermarks on or off by using PowerShell. Use the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) cmdlet with the **`-AllowWatermarkForCameraVideo`** and **`-AllowWatermarkForScreenSharing`** parameters. For example: @@ -104,7 +100,5 @@ Set-CsTeamsMeetingPolicy -Identity Global -AllowWatermarkForScreenSharing $True ## Related topics - [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - - [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) - - [Teams policies reference - Watermark](settings-policies-reference.md#content-protection) diff --git a/Teams/what-are-dial-plans.md b/Teams/what-are-dial-plans.md index 4699b8c568..ab8719753f 100644 --- a/Teams/what-are-dial-plans.md +++ b/Teams/what-are-dial-plans.md @@ -1,7 +1,7 @@ --- title: "What are dial plans?" -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: mikedav, roykuntz ms.date: 09/27/2023 diff --git a/Teams/what-are-emergency-locations-addresses-and-call-routing.md b/Teams/what-are-emergency-locations-addresses-and-call-routing.md index d61054ed83..acab91dda7 100644 --- a/Teams/what-are-emergency-locations-addresses-and-call-routing.md +++ b/Teams/what-are-emergency-locations-addresses-and-call-routing.md @@ -1,7 +1,7 @@ --- title: Plan and manage emergency calling -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.reviewer: roykuntz ms.date: 01/22/2024 diff --git a/Teams/what-is-phone-system-in-office-365.md b/Teams/what-is-phone-system-in-office-365.md index 9dad1aa12b..38f34d70ac 100644 --- a/Teams/what-is-phone-system-in-office-365.md +++ b/Teams/what-is-phone-system-in-office-365.md @@ -2,8 +2,8 @@ title: "What is Teams Phone" ms.reviewer: roykuntz ms.date: 03/07/2024 -author: CarolynRowe -ms.author: crowe +author: sfrancis206 +ms.author: scottfrancis manager: pamgreen ms.topic: conceptual ms.tgt.pltfrm: cloud diff --git a/Teams/who-can-bypass-meeting-lobby.md b/Teams/who-can-bypass-meeting-lobby.md index acd3c616d0..a084446023 100644 --- a/Teams/who-can-bypass-meeting-lobby.md +++ b/Teams/who-can-bypass-meeting-lobby.md @@ -1,8 +1,8 @@ --- -title: IT Admins - Control who can bypass the meeting lobby in Microsoft Teams +title: IT Admins - Manage lobby options in Microsoft Teams ms.author: wlibebe author: wlibebe -ms.reviewer: vivekmo +ms.reviewer: vivek.mohan ms.date: 6/6/2024 manager: pamgreen ms.topic: article @@ -20,9 +20,9 @@ f1.keywords: description: Learn how admins can configure the meeting lobby in Microsoft Teams to allow only certain meeting participants to join the meeting directly. --- -# IT Admins - Control who can bypass the meeting lobby in Microsoft Teams +# IT Admins - Manage lobby options in Microsoft Teams -**APPLIES TO:** ✔️Meetings ✔️Webinars ✖️Town halls +**APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Webinars ![Image of a x for no](/office/media/icons/cancel-teams.png)Town halls The Teams meeting lobby prevents certain types of participants from joining a meeting until a meeting organizer, co-organizer, or presenter admits them. When a participant goes to the lobby, organizers, co-organizers, and presenters are notified and can choose to admit them to the meeting or not. @@ -52,8 +52,9 @@ The following table shows the Teams meeting policies that affect how meeting par |Setting|Description| |:------|:----------| |**Anonymous users and dial-in callers can start a meeting**|This per-organizer policy allows for leaderless meetings. This setting controls whether anonymous participants and dial-in users can join the meeting without a verified participant in attendance. This setting only applies when **Who can bypass the lobby** is set to **Everyone**. If the **Anonymous users can join a meeting** organization-level setting or meeting policy is **Off**, this setting only applies to dial-in callers. By default, this setting is turned off to prevent anonymous users from misusing your meeting links.

    While **Off**, anonymous participants and dial-in users wait in the lobby until a verified participant (including a dial-in organizer) joins the meeting, at which point they're automatically admitted. Once the meeting starts, anonymous participants and dial-in users join the call automatically, even if the organizer leaves.

    If this setting is **On**, anonymous and dial-in participants can start and join the meeting without a verified participant present.| -|**People dialing in can bypass the lobby**|This is a per-organizer policy. This setting controls whether people who dial in by phone join the meeting directly or wait in the lobby. When this setting is **Off**, dial-in users wait in the lobby until an organizer, co-organizer, or presenter joins the meeting and admits them. When this setting is **On**, dial-in users automatically join the meeting without going through the lobby. (If **Anonymous users and dial-in callers can start a meeting** is **Off**, they wait in the lobby until the meeting starts.)| -|**Who can bypass the lobby**|This is a per-organizer policy. This setting controls which types of participants (except participants dialing in by phone) join a meeting directly. This policy also controls which types of participants wait in the lobby until an organizer, co-organizer, or presenter admits them.| +|**People dialing in can bypass the lobby**|This is a per-organizer policy. This setting controls whether people who dial in by phone join the meeting directly or wait in the lobby. When this setting is **Off**, dial-in users wait in the lobby until an organizer, co-organizer, or presenter joins the meeting and admits them. When this setting is **On**, dial-in users automatically join the meeting without going through the lobby. (If **Anonymous users and dial-in callers can start a meeting** is **Off**, they wait in the lobby until the meeting starts.) This policy sets a default that your organizers can change through their **Meeting options**.| +|**Who can admit from lobby**| This per-organizer policy controls who can bring participants from the lobby into the meeting or webinar. When set to its default value of **Organizers and presenters**, only organizers and presenters can admit participants into the meeting from the lobby. This policy sets a default that your organizers can change through their **Meeting options**.| +|**Who can bypass the lobby**|This is a per-organizer policy. This setting controls which types of participants (except participants dialing in by phone) join a meeting directly. This policy also controls which types of participants wait in the lobby until an organizer, co-organizer, or presenter admits them. This policy sets a default that your organizers can change through their **Meeting options**.| The following table shows how each option for the **Who can bypass the lobby** policy affects each *type of meeting participant*. @@ -67,12 +68,16 @@ The following table shows how each option for the **Who can bypass the lobby** p **Only people who were invited** applies only to participants who were sent an invite directly, who are part of an invited distribution list (of up to 10,000 users), or to whom an invite was forwarded. Users added via *Invite members* in a channel meeting wait in the lobby. -## Choose who can bypass the lobby in meetings hosted by your organization +To manage who can bypass the lobby using PowerShell, see the [Control who can bypass the lobby](#control-who-can-bypass-the-lobby) section in this article. + +## Use the Teams admin center to manage lobby options in meetings hosted by your organization You can manage lobby settings and policies in the Teams admin center. See the following sections for guidance on which setting to choose for different circumstances. For information about how meeting policies work, see [Manage meeting policies in Microsoft Teams](/microsoftteams/meeting-policies-overview). > [!IMPORTANT] -> Meeting organizers can change the default values that you choose for the **People dialing in can bypass the lobby** and **Who can bypass the lobby** settings via Meeting Options. If you need to enforce these settings to a particular value, you can use a meeting template or sensitivity label (Teams Premium required). For more information, see [Configure the Microsoft Teams meeting lobby for sensitive meetings](configure-lobby-sensitive-meetings.md). +> Meeting organizers can change the default values that you choose for the **People dialing in can bypass the lobby**, **Who can admit from lobby** and **Who can bypass the lobby** settings through their **Meeting options**. If you need to enforce these settings to a particular value, you can use a meeting template or sensitivity label (Teams Premium license required). For more information, see [Configure the Microsoft Teams meeting lobby for sensitive meetings](configure-lobby-sensitive-meetings.md). +> +> Meeting templates and sensitivity labels don't support the **Who can admit from lobby** setting. To manage meeting join and lobby policies, follow these steps: @@ -83,15 +88,15 @@ To manage meeting join and lobby policies, follow these steps: - **Anonymous users and dial-in callers can start a meeting** - **Who can bypass the lobby** (Who can bypass the lobby) - **People dialing in can bypass the lobby** - - ![Screenshot showing the meeting join and lobby policy in the Teams admin center.](media/meeting-join-and-lobby-tac-settings.png) + - **Who can admit from lobby** 1. Select **Save**. Changes can take up to 24 hours to take effect. If you want to allow anonymous meeting access, be sure the **Anonymous users can join a meeting** meeting setting is also turned on. -To set the organization-wide meeting setting for anonymous meeting join +To set the organization-wide meeting setting for anonymous meeting join: + 1. In the Teams admin center, expand **Meetings** and then select **Meeting settings**. 1. In the **Participants** section, set **Anonymous users can join a meeting** to **On** or **Off**. ![Screenshot showing the meeting join and lobby settings in the Teams admin center.](media/anonymous-users-can-join-meetings-org-setting.png) @@ -111,6 +116,8 @@ If you want people joining anonymously to wait in the lobby, you can set the **W By default, the **Anonymous users and dial-in callers can start a meeting** policy is **Off**. This means that anonymous participants and people calling in by phone always wait in the lobby until a verified participant starts the meeting. +To manage this setting using PowerShell, see the [Control whether anonymous users can join meetings](#control-whether-anonymous-users-can-join-meetings) section in this article. + > [!IMPORTANT] > We recommend that you leave this setting off. When the setting is on, people with unverified accounts can start meetings, including using the meeting link to have meetings at unscheduled times. @@ -118,6 +125,14 @@ By default, the **Anonymous users and dial-in callers can start a meeting** poli By default, the **People dialing in can bypass the lobby** policy is **Off**, but meeting organizers can change this in Meeting Options when they set up a meeting. You can change the default by updating the **People dialing in can bypass the lobby** policy or you can enforce a particular value by using a meeting template. +To manage this setting using PowerShell, see the [Control whether users dialing in by phone can bypass the lobby](#control-whether-users-dialing-in-by-phone-can-bypass-the-lobby) section in this article. + +## Control who can admit participants from the lobby + +By default, the **Who can admit from lobby** policy is set to **Organizers and presenters**, but meeting organizers can change this in their **Meeting options** when they set up a meeting or webinar. You can change the default by updating the **Who can admit from lobby** policy. + +To manage this setting using PowerShell, see the [Control who can admit users from the lobby](#control-who-can-admit-users-from-the-lobby) section in this article. + ## Control access to meetings by guests and people from trusted organizations There are two types of people outside your organization who can join meetings as verified participants: @@ -150,13 +165,126 @@ While there isn't a specific control that turns off the meeting lobby completely With these settings, anonymous users and dial-in callers still wait in the lobby if the meeting hasn't started. While you can set **Anonymous users and dial-in callers can start a meeting** to **On** to avoid this, we don't recommend it. -## Set meeting policies by using PowerShell +## Use PowerShell to manage lobby policies + +You can use the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) PowerShell cmdlet to manage the following lobby options: + +- Anonymous users can join meetings +- Users dialing in by phone can bypass the lobby +- Who can bypass the lobby +- Who can admit users from the lobby + +### Control whether anonymous users can join meetings + +To control whether anonymous users can join meetings, use the [**`-AllowAnonymousUsersToJoinMeeting`**](/powershell/module/teams/set-csteamsmeetingpolicy?#-allowanonymoususerstojoinmeeting) parameter. + +#### Prevent anonymous participants from joining meetings + +To prevent anonymous participants from joining meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowAnonymousUsersToJoinMeeting $false +``` + +#### Allow anonymous participants to join meetings + +**This is the default setting.** To allow anonymous participants to join meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowAnonymousUsersToJoinMeeting $true +``` + +### Control whether users dialing in by phone can bypass the lobby + +To control whether users dialing in by phone can bypass the lobby, use the [**`-AllowPSTNUsersToBypassLobby`**](/powershell/module/teams/set-csteamsmeetingpolicy#-allowpstnuserstobypasslobby) parameter. + +#### Prevent users dialing in by phone from bypassing the lobby + +To prevent users dialing in by phone from bypassing the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowPSTNUsersToBypassLobby $false +``` + +#### Allow users dialing in by phone to bypass the lobby + +To allow users dialing in by phone to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AllowPSTNUsersToBypassLobby $true +``` + +### Control who can bypass the lobby -You can set the meeting policies described in this article by using the [Set-CsTeamsMeetingPolicy](/powershell/module/teams/set-csteamsmeetingpolicy) PowerShell cmdlet with the following parameters: +To control who can bypass the lobby, use the [**`-AutoAdmittedUsers`**](/powershell/module/teams/set-csteamsmeetingpolicy?#-autoadmittedusers) parameter. -- [-AllowAnonymousUsersToJoinMeeting](/powershell/module/teams/set-csteamsmeetingpolicy?#-allowanonymoususerstojoinmeeting) to control if anonymous users can join meetings -- [-AllowPSTNUsersToBypassLobby](/powershell/module/teams/set-csteamsmeetingpolicy#-allowpstnuserstobypasslobby) to control if people dialing in by phone can bypass the lobby -- [-AutoAdmittedUsers](/powershell/module/teams/set-csteamsmeetingpolicy?#-autoadmittedusers) to control who can bypass the lobby +#### Allow everyone to bypass the lobby + +To allow everyone to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers Everyone +``` + +#### Only allow people in my org, trusted orgs, and guests to bypass the lobby + +To only allow people in your org, trusted orgs, and guests to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers EveryoneInSameAndFederatedCompany +``` + +#### Only allow people in my org and guests to bypass the lobby + +To only allow people in your org and guests to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers EveryoneInCompany +``` + +#### Only allow people in my org to bypass the lobby + +To only allow people in your org to bypass to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers EveryoneInCompany +``` + +#### Only allow people who were invited to bypass the lobby + +To only allow people who were invited to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers InvitedUsers +``` + +#### Only allow organizers and co-organizers to bypass the lobby + +To only allow organizers and co-organizers to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers OrganizerOnly +``` + +### Control who can admit users from the lobby + +To control who can admit users from the lobby, use the [**`-UsersCanAdmitFromLobby`**](/powershell/module/teams/set-csteamsmeetingpolicy?#-userscanadmitfromlobby) parameter. + +#### Only allow organizers and presenters to admit participants from the lobby + +**This is the default value.** To only allow organizers and presenters to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers OrganizersAndPresentersOnly +``` + +#### Only allow organizers and co-organizers to admit participants from the lobby + +To only allow organizers and co-organizers to bypass the lobby in meetings and webinars created by organizers with this policy, use the following script: + +```powershell +Set-CsTeamsEventsPolicy -Identity -AutoAdmittedUsers OrganizerAndCoOrganizersOnly +``` ## Run the lobby diagnostic tool @@ -167,8 +295,7 @@ If a user recently had an undesired lobby experience in a meeting hosted by your ## Related topics +- [Who can admit from lobby](https://support.microsoft.com/office/using-the-lobby-in-microsoft-teams-meetings-eaf70322-d771-4043-b595-b40794bac057) - [Join a meeting without a Teams account](https://support.microsoft.com/office/c6efc38f-4e03-4e79-b28f-e65a4c039508) - - [Using the Microsoft Teams admin center to configure organization-wide policy](meeting-settings-in-teams.md#allow-anonymous-users-to-join-meetings) - - [External participants receive "Sign in to Teams to join, or contact the meeting organizer"](/microsoftteams/troubleshoot/meetings/external-participants-join-meeting-blocked)