diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 9ade48af34..7449ef7932 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -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 } ] } 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/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..c68596d856 100644 --- a/Teams/QoS-in-Teams-clients.md +++ b/Teams/QoS-in-Teams-clients.md @@ -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..dd4f8fbb79 100644 --- a/Teams/QoS-in-Teams.md +++ b/Teams/QoS-in-Teams.md @@ -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|Expedited Forwarding (EF)| + +\* 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/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/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/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/cloud-voice-network-settings.md b/Teams/cloud-voice-network-settings.md index 8edbf68310..e95ee3a5e4 100644 --- a/Teams/cloud-voice-network-settings.md +++ b/Teams/cloud-voice-network-settings.md @@ -5,7 +5,7 @@ ms.author: crowe 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-lobby-sensitive-meetings.md b/Teams/configure-lobby-sensitive-meetings.md index 70e0353ffd..ea2534ff98 100644 --- a/Teams/configure-lobby-sensitive-meetings.md +++ b/Teams/configure-lobby-sensitive-meetings.md @@ -5,7 +5,7 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: +ms.reviewer: vivek.mohan ms.date: 12/11/2023 audience: admin ms.localizationpriority: medium @@ -35,19 +35,27 @@ The following table lists features that you can use to help manage the lobby exp |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 +The following settings are available for **Who can admit from lobby**: + +- 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 it's 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**. + The following settings are available for **Who can bypass the lobby**: - Everyone @@ -57,6 +65,8 @@ The following settings are available for **Who can bypass the lobby**: - People who were invited - Only organizers and co-organizers +This per-organizer policy controls who can bring participants from the lobby into the meeting or webinar. When set to it's 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**. + An additional 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. @@ -89,6 +99,6 @@ If your organization doesn't allow anonymous participants to join meetings at al ## 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..8a516a5b18 100644 --- a/Teams/configure-meetings-baseline-protection.md +++ b/Teams/configure-meetings-baseline-protection.md @@ -5,7 +5,7 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: +ms.reviewer: vivek.mohan ms.date: 12/11/2023 audience: admin ms.localizationpriority: medium @@ -27,7 +27,7 @@ description: Learn how to configure Teams meetings for a baseline level of prote 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. -> [!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. @@ -56,12 +56,24 @@ 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**. +## Default values for **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** + ## Watermarks and end-to-end encryption 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. @@ -76,7 +88,8 @@ For the *baseline* level of protection, we use a sensitivity label that you can 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. -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**. diff --git a/Teams/configure-meetings-highly-sensitive-protection.md b/Teams/configure-meetings-highly-sensitive-protection.md index 49994c7614..09a5d11026 100644 --- a/Teams/configure-meetings-highly-sensitive-protection.md +++ b/Teams/configure-meetings-highly-sensitive-protection.md @@ -5,7 +5,7 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: +ms.reviewer: vivek.mohan ms.date: 12/11/2023 audience: admin ms.localizationpriority: medium @@ -26,13 +26,14 @@ 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 -> [!Note] +> [!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. @@ -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. @@ -101,6 +102,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 +130,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 +169,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 +187,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 +209,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-three-tiers-protection.md b/Teams/configure-meetings-three-tiers-protection.md index f38bc20cfe..2045d9c04d 100644 --- a/Teams/configure-meetings-three-tiers-protection.md +++ b/Teams/configure-meetings-three-tiers-protection.md @@ -73,7 +73,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: @@ -145,6 +145,7 @@ For the baseline tier, we allow everyone except anonymous attendees to bypass th 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) @@ -155,6 +156,8 @@ If you're in a highly regulated industry and you need to manually admit each att 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 diff --git a/Teams/copilot-teams-transcription.md b/Teams/copilot-teams-transcription.md index aee0734fee..772abcd3e0 100644 --- a/Teams/copilot-teams-transcription.md +++ b/Teams/copilot-teams-transcription.md @@ -34,6 +34,9 @@ Microsoft 365 Copilot in Teams meetings and events is an artificial intelligence There are two ways for users in your organization to use Copilot in meetings and events: +> [!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. 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/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..ebbd7d7e44 100644 --- a/Teams/delete-exchange-online-transcripts.md +++ b/Teams/delete-exchange-online-transcripts.md @@ -25,6 +25,9 @@ appliesto: **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). + 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. This article describes how to delete the meeting transcript files in Exchange Online and OneDrive. diff --git a/Teams/devices/authentication-best-practices-for-android-devices.md b/Teams/devices/authentication-best-practices-for-android-devices.md index 7e26715039..2dc817fff0 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,65 @@ 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. 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..51a48e541f 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,8 +47,7 @@ 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 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 | @@ -83,6 +64,8 @@ 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 | @@ -90,8 +73,8 @@ The following devices are certified under the Microsoft Teams Rooms on Android C | DTEN D7X 55" | `1.2.2` |August 15, 2027| 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 | @@ -113,6 +96,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 +107,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 +121,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| @@ -241,6 +229,10 @@ 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 | |:-------------------|:----------------------------|:---------------------------------------------|:-------------------------------|:-------------------------------|:--------------------------------|:--------------------------------| +| 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 +288,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| @@ -393,6 +390,14 @@ 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 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 +540,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 +606,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/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|| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|| - -## 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|| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|| - -## 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|| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|| - -### 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|| -| ![An icon depicting next steps.](../media/audio_conferencing_image9.png)
Next steps|| - -### 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/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..9370e6d959 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| @@ -131,6 +131,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 +150,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 +165,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 +176,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..a237b1d225 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 re0certified, 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 folowing 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 | @@ -112,7 +109,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 +128,11 @@ 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| +|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 +169,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 | diff --git a/Teams/devices/usb-devices.md b/Teams/devices/usb-devices.md index 156b390720..26a89d8088 100644 --- a/Teams/devices/usb-devices.md +++ b/Teams/devices/usb-devices.md @@ -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 | 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/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/enhanced-teams-experience.md b/Teams/enhanced-teams-experience.md index cc8aab061d..11eadeba88 100644 --- a/Teams/enhanced-teams-experience.md +++ b/Teams/enhanced-teams-experience.md @@ -49,6 +49,7 @@ The following sections in this article describe the Teams Premium enhancements f - [Virtual Appointments](#advanced-virtual-appointments) - [Intelligent meeting features](#intelligent-meeting-features) - [Custom 3D Immersive Mesh Experiences](#custom-3d-immersive-mesh-experiences) +- [Advanced Places Workplace Collaboration](#advanced-places-workplace-collaboration) - [Intelligent call recap](#intelligent-call-recap) - [Queues app](#queues-app) @@ -72,6 +73,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. @@ -92,24 +95,26 @@ Teams Premium provides more ways to safeguard and monitor users' Teams experienc - **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)| + | 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 @@ -125,13 +130,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 +153,22 @@ 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. +- **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) | + | 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 +183,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 +207,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 +221,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,18 +241,28 @@ 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) | + | 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 + +> [!NOTE] +> This feature is currently in Public Preview. + +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. Check back soon for details. + +To learn more about Places, see [Microsoft Places overview](/microsoft-365/places/places-overview). ## Calls ### Intelligent call recap + **Intelligent call recap** provides AI-powered insights and recaps to Public Switched Telephone Network (PSTN) and 1:1 Teams calls. - To use this feature for PSTN calls, you must assign a Teams Phone license and either Teams Premium license or a Microsoft 365 Copilot license to users. For more information on Teams Phone licensing, see [Microsoft Teams add-on licenses](teams-add-on-licensing/microsoft-teams-add-on-licensing.md). @@ -261,11 +276,11 @@ Teams Premium and Teams Phone provides access to Queues app, a Teams-native solu - **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. 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/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..5c3d9be5be 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 + ``` -#### [**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/itadmin-readiness.md b/Teams/itadmin-readiness.md deleted file mode 100644 index fe1f0f3ed4..0000000000 --- a/Teams/itadmin-readiness.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Admin training resources - Microsoft Teams -ms.reviewer: jhwang -ms.date: 03/27/2024 -author: MicrosoftHeidi -ms.author: heidip -manager: jtremper -ms.topic: article -ms.service: msteams -audience: admin -ms.collection: -- M365-collaboration -search.appverid: MET150 -f1.keywords: -- CSH -ms.custom: -- ms.teamsadmincenter.dashboard.trainingvideos.admintrainingteams -- seo-marvel-mar2020 -description: Training videos, PowerPoint decks, tutorials, and other resources for admins on how to plan, deploy, and run Microsoft Teams. -appliesto: -- Microsoft Teams ---- -# Getting started with admin training for Microsoft Teams - -Use the training resources to educate yourself about Teams, teach others or run workshops. Check back here often for new content. - -| | | | | -| :------------ | :------------ | :------------ | :------------ | -|![a hand and an upward arrow.](/office/media/icons/get-started-teams.png) |[Start your rollout here](./get-started-with-teams-quick-start.md) |![document with a list](/office/media/icons/document-teams.png)|[View Teams features by platform](https://support.microsoft.com/office/teams-features-by-platform-debe7ff4-7db4-4138-b7d0-fcc276f392d3) | -|![a video play button.](/office/media/icons/video-play.png) |[View best practice and how-to videos in the Coffee in the Cloud channel on YouTube](https://www.youtube.com/channel/UCs2IXBqperxWVe2ozrr3Gdg/videos) |![person with a wrench](/office/media/icons/administrator.png) |[Teams Chalk Talks: learn best practices and practical guidance around popular Teams scenarios](./chalk-talks-landing-page.yml) | - - -

Key training offerings and courses

- -|  |  |  | -|---------|---------|---------| -|[**Teams essentials for IT**](https://aka.ms/MicrosoftTeamsforIT) - Microsoft Mechanics "Teams for IT" video series shows you – the admin – how to roll out, configure, and manage Teams. |[**Support remote workers using Microsoft Teams**](support-remote-work-with-teams.md#support-remote-workers-using-microsoft-teams) - Get the guidance you need – including links to training – to support your users who are working from home. |[**Manage Team collaboration for IT**](/training/paths/m365-manage-team-collaboration) - Learn how to use Teams to facilitate teamwork and communication within your org across applications and devices. | -|[**Service Adoption Specialist certification**](/training/paths/m365-service-adoption) - The Microsoft Service Adoption Specialist certification course features Teams. Learn how to drive adoption of Microsoft services in your org. |[**Introduction to teamwork in Microsoft 365**](/training/modules/intro-to-teamwork-in-m365/index) - The Microsoft Service Adoption Specialist Certification course features Teams. Learn how to drive adoption of Microsoft services in your org. |[**Microsoft 365 Certified: Teamwork Administrator Associate**](/certifications/m365-teamwork-administrator) - Microsoft 365 Teamwork Administrators configure, deploy, and manage Microsoft 365 or Office 365 workloads, such as SharePoint (online, on-premises, and hybrid), OneDrive, and Teams. | - -

Technical training

- -| Module | Video | PowerPoint deck | -| ------------ | -------------------- | -------------------- | -| [Microsoft Mechanics - Teams Essentials for IT YouTube channel](https://aka.ms/MicrosoftTeamsforIT) | [Video: Teams Essentials for IT](https://www.youtube.com/watch?v=MfDB7VenWuA&list=PLXtHYVsvn_b_JeDjgD5XdkyHTDXdYgPGn) (10:13 min)
[Video: Deploy & Configure Teams - Intro](https://www.youtube.com/watch?v=o2mlsUubIO4&list=PLXtHYVsvn_b_JeDjgD5XdkyHTDXdYgPGn&index=2) (8:22 min)
[Video: Security and Compliance](https://youtu.be/91lHNKVVvQ4) (12:42 min)
[Video: Teams Controls for Security and Compliance](https://www.youtube.com/watch?v=Km4T4hMM__k) (10:54 min)|| -| Foundations - Core components | [Video](https://aka.ms/teams-foundations) | [Deck](https://aka.ms/teams-foundations-deck) | -| Apps - Managing and deploying | | [Deck](https://aka.ms/managing-deploying-apps-deck) | -| Audio conferencing | | [Deck](https://aka.ms/teams-audio-conferencing-deck) | -| Call quality overview | | [Deck](https://aka.ms/teams-quality-deck) | -| Direct Routing | [Video 1: Planning for Direct Routing in Teams](https://aka.ms/teams-dr-plan)
[Video 2: Configuring and Managing Direct Routing in Teams](https://aka.ms/teams-dr-config)
[Video 3: Migrating to Direct Routing in Teams](https://aka.ms/teams-dr-migrate) | [Deck](https://aka.ms/teams-direct-routing-deck) | -| Dynamic emergency calling | [Video](https://aka.ms/teams-dec) | [Deck](https://aka.ms/teams-dec-deck) | -| Governance, management, and lifecycle | [Video](https://aka.ms/teams-governance) | [Deck](https://aka.ms/teams-governance-deck) | -| Live events | [Video](https://aka.ms/teams-live-events-session) | [Deck](https://aka.ms/teams-live-events-deck) | -| Phone system introduction | [Video](https://aka.ms/teams-phone-system) | [Deck](https://aka.ms/teams-phone-system-deck) | -| PSTN connectivity | | [Deck](https://aka.ms/teams-pstn-connectivity-deck) | -| Media - Why meetings are simple|[Video](https://aka.ms/media-in-teams) | [Deck](https://aka.ms/media-in-teams-deck)| -| Media - Media flow | [Video](https://aka.ms/teams-media-flows) | [Deck](https://aka.ms/teams-media-flows-deck) | -| Meetings introduction | [Video](https://aka.ms/teams-meetings-intro) | [Deck](https://aka.ms/teams-meetings-intro-deck) | -| Security & Compliance | [Video](https://aka.ms/teams-security-compliance) | [Deck](https://aka.ms/teams-security-compliance-deck) | -| SIP gateway enablement and migration | | [Deck](https://aka.ms/SIP-gateway-enablement-migration-playbook) | -| Teams Devices Deployment playbook | | [Deck](https://aka.ms/teams-devices-deployment-playbook) | -| 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 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) | - -

Teams Rooms Foundations for IT & AV Pros

- -

The following table contains links to comprehensive training decks in PowerPoint on Microsoft Teams Rooms. - -| Module | PowerPoint deck | -| ------------ | -------------------- | -| Module 1: Introduction to Microsoft Teams Rooms | [Deck](https://aka.ms/TeamsRoomsModule1) | -| Module 2: Network readiness | [Deck](https://aka.ms/TeamsRoomsModule2) | -| Module 3: Room design and components | [Deck](https://aka.ms/TeamsRoomsModule3) | -| Module 4: The resource account | [Deck](https://aka.ms/TeamsRoomsModule4) | -| Module 5: Starting and configuring Microsoft Teams Rooms | [Deck](https://aka.ms/TeamsRoomsModule5) | -| Module 6: Managing Microsoft Teams Rooms, Part 1 | [Deck](https://aka.ms/TeamsRoomsModule6) | -| Module 7: Managing Microsoft Teams Rooms, Part 2 | [Deck](https://aka.ms/TeamsRoomsModule7) | -| Module 8: Features, adoption, and troubleshooting | [Deck](https://aka.ms/TeamsRoomsModule8)| - -

Teams Android devices

- -

The following table contains links to comprehensive training decks in PowerPoint on Microsoft Teams Android Devices that includes Teams Displays, Teams Phones, Teams Rooms on Android, and Teams Panels. - -| Module | PowerPoint deck | -| ------------| -------------------- | -| Module 1: Introduction to Microsoft Teams Android devices |[Deck](https://aka.ms/TeamsAndroidModule1) | -| Module 2: Planning Microsoft Teams Android devices|[Deck](https://aka.ms/TeamsAndroidModule2) | -| Module 3: Managing Microsoft Teams Android Devices |[Deck](https://aka.ms/TeamsAndroidModule3)| -| Module 4: Microsoft Teams phones and Microsoft Teams displays |[Deck](https://aka.ms/TeamsAndroidModule4)| -| Module 5: Microsoft Teams Rooms and Microsoft Teams Panels |[Deck](https://aka.ms/TeamsAndroidModule5)| -| Module 6: Adoption and troubleshooting |[Deck](https://aka.ms/TeamsAndroidModule6)| - -## Related topics - -[Live and on demand user training](https://adoption.microsoft.com/user-training/?filter=microsoft-teams) - - diff --git a/Teams/limits-specifications-teams.md b/Teams/limits-specifications-teams.md index a710f82f68..570910328c 100644 --- a/Teams/limits-specifications-teams.md +++ b/Teams/limits-specifications-teams.md @@ -149,7 +149,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/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-meeting-recording-options.md b/Teams/manage-meeting-recording-options.md index aa85f2a1a4..fc97c09e1c 100644 --- a/Teams/manage-meeting-recording-options.md +++ b/Teams/manage-meeting-recording-options.md @@ -23,6 +23,9 @@ description: Learn how to manage who can record Teams meetings, automatic record [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] +> [!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). + 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. The following table shows the features available to help you manage meeting recordings and where they're configured. diff --git a/Teams/manage-qna-for-teams.md b/Teams/manage-qna-for-teams.md index f1bdb7f954..9f83d79d85 100644 --- a/Teams/manage-qna-for-teams.md +++ b/Teams/manage-qna-for-teams.md @@ -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-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-your-network-topology.md b/Teams/manage-your-network-topology.md index 1410b4a54b..27b0cb4dde 100644 --- a/Teams/manage-your-network-topology.md +++ b/Teams/manage-your-network-topology.md @@ -4,7 +4,7 @@ author: CarolynRowe ms.author: crowe 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/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/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/meeting-recording.md b/Teams/meeting-recording.md index 7c5d45400f..d16d218e71 100644 --- a/Teams/meeting-recording.md +++ b/Teams/meeting-recording.md @@ -25,6 +25,9 @@ description: Learn how to deploy features in Teams meetings to record audio, vid # Manage Teams recording policies for meetings and events +> [!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:** ✔️Meetings ✔️Webinars ✔️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). diff --git a/Teams/meeting-transcription-captions.md b/Teams/meeting-transcription-captions.md index 034d0c85cb..c7f0ad45bd 100644 --- a/Teams/meeting-transcription-captions.md +++ b/Teams/meeting-transcription-captions.md @@ -28,6 +28,9 @@ appliesto: **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). + 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. As an admin, you can manage transcription and captions for users in your org. diff --git a/Teams/meeting-webinar-town-hall-feature-comparison.md b/Teams/meeting-webinar-town-hall-feature-comparison.md index aaed64bb62..e7b9838405 100644 --- a/Teams/meeting-webinar-town-hall-feature-comparison.md +++ b/Teams/meeting-webinar-town-hall-feature-comparison.md @@ -38,13 +38,13 @@ The following table shows which features are available in meetings, webinars, an |[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|✖️| +|[Breakout rooms](https://support.microsoft.com/office/use-breakout-rooms-in-microsoft-teams-meetings-7de1f48a-da07-466c-a5ab-4ebace28e461)|✔️|✖️1|✖️| |[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)|✔️|✔️|✔️| |[Custom backgrounds](custom-meeting-backgrounds.md)|Premium|Premium|Premium| -|[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|✔️|✖️|✔️| +|[eCDN](streaming-ecdn-enterprise-content-delivery-network.md)|For view-only meetings only.|✖️|✔️| |[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)|✔️|✔️|✔️| @@ -73,15 +73,15 @@ The following table shows which features are available in meetings, webinars, an |[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|✖️|✖️| +|[View-only attendees](view-only-meeting-experience.md)|10,0002|✖️|✖️| |[VOD](manage-vod-publishing.md)|✖️|✔️|✔️| |[Voice isolation](voice-isolation.md)|✔️|✔️|✔️| |[Watermarks](watermark-meeting-content-video.md)|Premium|✖️|✖️| |[Whiteboard](meeting-policies-content-sharing.md)|✔️|✔️|✖️| -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/meetings-real-time-media-traffic.md b/Teams/meetings-real-time-media-traffic.md index 221e40e22c..34aa42ac3d 100644 --- a/Teams/meetings-real-time-media-traffic.md +++ b/Teams/meetings-real-time-media-traffic.md @@ -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/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..bb9c40b876 100644 --- a/Teams/new-teams-vdi-requirements-deploy.md +++ b/Teams/new-teams-vdi-requirements-deploy.md @@ -581,6 +581,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/overview-meetings-webinars-town-halls.md b/Teams/overview-meetings-webinars-town-halls.md index 7e9931da2f..6c3b8cfbca 100644 --- a/Teams/overview-meetings-webinars-town-halls.md +++ b/Teams/overview-meetings-webinars-town-halls.md @@ -52,11 +52,11 @@ The following table shows the main features that are different between meetings, |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| +|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,0001 (Enterprise plans only)|✖️|✖️| -|Maximum total participants|11,0001 (Enterprise plans only)|1,000|Town halls: 10,000
Premium town halls: 20,000| +|Maximum total participants|10,9001 (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.
+1The 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.
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. @@ -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. diff --git a/Teams/phones/authentication-best-practices-phones.md b/Teams/phones/authentication-best-practices-phones.md new file mode 100644 index 0000000000..aa340a134a --- /dev/null +++ b/Teams/phones/authentication-best-practices-phones.md @@ -0,0 +1,100 @@ +--- +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. 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/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/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 78% rename from Teams/set-up-common-area-phones.md rename to Teams/phones/set-up-common-area-phones.md index 7425fcd79b..a5b067fc54 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,12 +73,15 @@ 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. @@ -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'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). > [!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: @@ -129,11 +124,11 @@ To sign in locally with a username and password: 3. Follow the sign-in directions on the device. Once signed in, the phone will display 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'll 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). @@ -141,7 +136,7 @@ You can also sign into to a common area phone from another device using a code. ### 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 +144,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. @@ -198,10 +193,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-meetings.md b/Teams/plan-meetings.md index 6c120ae9b5..3e713850e4 100644 --- a/Teams/plan-meetings.md +++ b/Teams/plan-meetings.md @@ -46,7 +46,7 @@ This article, designed for admins, introduces types of meetings, features and fu ## 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). @@ -94,9 +94,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). @@ -135,6 +135,7 @@ Teams admins and organizers have different policies and settings to control the |[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.| |[Collaboration features](meeting-policies-content-sharing.md)|Can control the availability of PowerPoint Live, whiteboard, and shared notes.|No control| |[Content sharing](meeting-who-present-request-control.md)|Can control sharing mode and who can request control and can set a default for who can present.|Can control who can present.| +|[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.| @@ -154,7 +155,7 @@ Teams admins and organizers have different policies and settings to control the |[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.| |[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..d627b2dfc6 100644 --- a/Teams/plan-town-halls.md +++ b/Teams/plan-town-halls.md @@ -170,7 +170,7 @@ Teams admins and organizers have different policies and settings to control the |[Audio and video](meeting-policies-audio-and-video.md)|Can manage the availability and use of audio and video for presenters and organizers.| Only presenters and organizers can use their audio and video. Attendees can't share their audio or video, but interact through Q&A.| |[Chat](manage-meeting-chat.md)|Can manage whether organizers, presenters, and co-organizers can read and write messages to each other during town halls.|Can chat with presenters and co-organizers. Attendees don't use chat during town halls.| |[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.| |[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.| 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/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..6f539e9864 100644 --- a/Teams/rooms/bring-your-own-device.md +++ b/Teams/rooms/bring-your-own-device.md @@ -128,7 +128,7 @@ To associate a device with a room, the following two methods are available: - **Manually associate discovered devices using Pro Management UI:** - 1. Go to the device table. +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. @@ -136,7 +136,15 @@ To associate a device with a room, the following two methods are available: :::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. diff --git a/Teams/rooms/certified-hardware.md b/Teams/rooms/certified-hardware.md index 032de4cae3..1883318c9b 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 | @@ -151,146 +152,147 @@ 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 | | | +| [:::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 | 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 | | | +| [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 | | ||| +| [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.410.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](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 | 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 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/create-resource-account.md b/Teams/rooms/create-resource-account.md index 0eb38a495b..95d334b066 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: Create resource accounts for Teams Rooms and shared devices 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 devices -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,29 @@ 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. + +### 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/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/proximity-join.md b/Teams/rooms/proximity-join.md index e2657f1640..60cd863bb5 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,20 +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) | +|Crestron MercuryX |Teams on macOS (minimum version 24193.1707.3028.4282) | |Lenovo Hub 500|| |Lenovo ThinkSmart Audio G2|| |Logi Tap|| @@ -73,7 +75,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 +85,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 +98,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..1fbe235d77 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,15 @@ 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:   -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) - -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). - -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 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) 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..bce20e6ea5 100644 --- a/Teams/rooms/rooms-operations.md +++ b/Teams/rooms/rooms-operations.md @@ -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..510f9bc2ec 100644 --- a/Teams/rooms/rooms-release-note.md +++ b/Teams/rooms/rooms-release-note.md @@ -65,16 +65,23 @@ 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) + 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. @@ -101,7 +108,7 @@ Introduced in this update: 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 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. @@ -116,12 +123,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'll 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 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**. @@ -148,7 +155,7 @@ 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. - **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). @@ -277,7 +284,7 @@ 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 @@ -524,7 +531,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. @@ -789,14 +796,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 +816,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 does not 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 +831,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 +839,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. @@ -921,7 +928,7 @@ Introduced in this update: - 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 +945,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 are 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 +954,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 +974,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 +998,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 +1008,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 are 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 +1025,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..4932844cc9 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/01/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) @@ -47,7 +47,7 @@ To help guide you as to what features are available on different platforms, you | | 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| +| | 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 +62,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 +88,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| @@ -108,7 +110,8 @@ To help guide you as to what features are available on different platforms, you | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | Available | 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 +155,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) @@ -170,7 +178,7 @@ To help guide you as to what features are available on different platforms, you | | 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 | +| | 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 +193,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 | @@ -231,7 +241,8 @@ To help guide you as to what features are available on different platforms, you | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | 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 +285,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) @@ -292,7 +307,7 @@ To help guide you as to what features are available on different platforms, you | | 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 | +| | 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 +322,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 | @@ -353,7 +370,8 @@ To help guide you as to what features are available on different platforms, you | **Device Management** | Built-in backgrounds | Available | Available | | | Custom background | 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 +399,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/voice-and-face-recognition.md b/Teams/rooms/voice-and-face-recognition.md index 2a9d294445..031588a3e4 100644 --- a/Teams/rooms/voice-and-face-recognition.md +++ b/Teams/rooms/voice-and-face-recognition.md @@ -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?view=teams-ps"https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps") 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 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/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-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/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/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/streaming-ecdn-enterprise-content-delivery-network.md b/Teams/streaming-ecdn-enterprise-content-delivery-network.md index 9e95791e38..a3ef8188f4 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:** ✔️View only-meetings ✖️Webinars ✔️Town halls ✔️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/teams-add-on-licensing/licensing-enhance-teams.md b/Teams/teams-add-on-licensing/licensing-enhance-teams.md index 7a9f4fe20f..40de78a02c 100644 --- a/Teams/teams-add-on-licensing/licensing-enhance-teams.md +++ b/Teams/teams-add-on-licensing/licensing-enhance-teams.md @@ -80,8 +80,7 @@ The following tables compare key features between Teams and Teams Premium. Becau | Use RTMP-In for meetings | | ✔️ | | Hide attendee names | | ✔️ | | View engagement reports | | ✔️ | -| Translate post-meeting transcriptions (*coming soon*) | | ✔️ | -| Turn on eCDN Meetings\* | | ✔️ | +| Turn on eCDN for view-only meetings\* | | ✔️ | | Audio quality alerts | | ✔️ | | Video quality alerts | | ✔️ | | Screen sharing quality alerts | | ✔️ | @@ -240,6 +239,15 @@ The Meet app in Teams allows users to view important details of their meetings i \* *Mentions of a user's name is pulled from the meeting transcript, not from an @mention tag in the meeting chat.* +### Places Workplace Collaboration + +> [!NOTE] +> This feature is currently in Public Preview. + +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. Check back soon for details. + +To learn more about Places, see [Microsoft Places overview](/microsoft-365/places/places-overview). + ### 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). @@ -252,6 +260,7 @@ The Queues app is a Teams-native solution designed to empower organizations to m 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.
    @@ -308,8 +317,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. @@ -324,7 +333,7 @@ The following table shows which Teams Premium features provide primary value to | **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 | | +| **Microsoft eCDN** | | ✔️ Works with Teams view-only meetings, live events, and town halls
    ✔️ Microsoft eCDN included as a part of the Teams Premium bundle | | ## How does Teams Premium differ from Teams Rooms Pro? @@ -394,7 +403,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-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..d13f0be50b 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 @@ -27,7 +27,7 @@ appliesto: [!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/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-client-update.md b/Teams/teams-client-update.md index 7f7d80ab3b..021d49848e 100644 --- a/Teams/teams-client-update.md +++ b/Teams/teams-client-update.md @@ -9,59 +9,157 @@ 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. +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. +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. +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-powershell-release-notes.md b/Teams/teams-powershell-release-notes.md index 69b64ac836..7b3394ff6a 100644 --- a/Teams/teams-powershell-release-notes.md +++ b/Teams/teams-powershell-release-notes.md @@ -26,7 +26,8 @@ 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.
    • +| 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/tmr-meeting-recording-change.md b/Teams/tmr-meeting-recording-change.md index 2e5b0ddd9f..de25b82744 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). diff --git a/Teams/toc.yml b/Teams/toc.yml index a374c7e658..74e33a5021 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -103,8 +103,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 @@ -125,8 +129,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) @@ -358,7 +360,6 @@ items: - name: Intelligent recap href: privacy/intelligent-recap.md - - name: Manage and monitor Teams items: - name: Overview @@ -367,6 +368,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: @@ -687,7 +690,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,7 +1304,7 @@ 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 @@ -1315,7 +1318,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 +1329,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 +1346,321 @@ 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 calling 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 Home screen - href: rooms/mtr-home-refresh.md + - 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 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: 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 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..3c3136230b 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,25 @@ 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. + +EnableEntryExitNotifications + +### 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/view-only-meeting-experience.md b/Teams/view-only-meeting-experience.md index 22e6e647ad..cbc90e27c4 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 @@ -24,13 +24,15 @@ appliesto: **APPLIES TO:** ✔️Meetings ✖️Webinars ✖️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/walkie-talkie.md b/Teams/walkie-talkie.md index 04ae542f00..312520b2d9 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,6 +84,9 @@ 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). diff --git a/Teams/who-can-bypass-meeting-lobby.md b/Teams/who-can-bypass-meeting-lobby.md index acd3c616d0..b0f09fc08f 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,7 +20,7 @@ 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 @@ -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 it's 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 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 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)