diff --git a/Teams/cqd-data-and-reports.md b/Teams/cqd-data-and-reports.md index a583006e8e..3d48f0ebe5 100644 --- a/Teams/cqd-data-and-reports.md +++ b/Teams/cqd-data-and-reports.md @@ -4,7 +4,7 @@ author: mkbond007 ms.author: mabond manager: pamgreen ms.reviewer: jamp, siunies, mikedav, gageames -ms.date: 07/31/2024 +ms.date: 09/25/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -40,7 +40,7 @@ You can access call quality data by several different avenues. Pick the one that |Teams admin center [(https://admin.teams.microsoft.com)](https://admin.teams.microsoft.com)|Call quality data is included on the **Users** page in the Teams admin center, showing the most common data you need in an easy-to-read format. You can't customize the data that you find under **Users**.| |CQD portal [(https://cqd.teams.microsoft.com)](https://cqd.teams.microsoft.com)|Robust summary and detailed reports that meet most needs, with drill-through filtering. You can also customize reports in the CQD portal.

Get two [CQD report templates](#import-the-cqd-report-templates) to help you analyze data in the CQD portal.| |Power BI|Use direct queries to view your CQD data in Power BI using [customizable Power BI templates](CQD-Power-BI-query-templates.md). The CQD Power BI templates are regularly updated to support new Teams features, calling scenarios, and the latest telemetry we have available in CQD.| -|Graph API|Access raw call quality data yourself using the [Graph API](/graph/api/resources/callrecords-api-overview). This is the most complex method, but it gives you the most control and flexibility in analyzing your call quality data. For example, if you need to join it with other data for your organization, you can use the Graph API to create a data model and incorporate call quality data. Please note that CallRecords Graph API may not contain all of the fields that are available in CQD and naming conventions may differ between the two products. | +|Graph API|Access raw call quality data yourself using the [Graph API](/graph/api/resources/callrecords-api-overview). Using Graph API is the most complex method, but it gives you the most control and flexibility in analyzing your call quality data. For example, if you need to join it with other data for your organization, you can use the Graph API to create a data model and incorporate call quality data. Please note that CallRecords Graph API may not contain all of the fields that are available in CQD and naming conventions may differ between the two products. | ## Import the CQD report templates @@ -158,8 +158,7 @@ If you want to use Power BI to analyze your CQD data, read [Use Power BI to anal In the Summary and Location-Enhanced Reports, you can use the **Product Filter** drop-down to show all product data, only Microsoft Teams data, or only Skype for Business data. -> [!div class="mx-imgBorder"] -> ![Screenshot: shows the Product Filter control options.](media/206ad818-0f72-4c8e-b25e-3cc8fcfbef05.png) +![Screenshot: shows the Product Filter control options.](media/cqd-product-filter.png) In Detailed reports, you can use the **Is Teams** dimension to filter the data to Microsoft Teams or Skype for Business data. @@ -169,7 +168,7 @@ These are the reports that you'll see on the CQD Dashboard when you first sign i |Tab|Description| |---|---| -|Overall Call Quality|Aggregate of the other 3 tabs.| +|Overall Call Quality|Aggregate of the other three tabs.| |Server—Client|Details of the streams between server and client endpoints.| |Client—Client|Details of the streams between two client endpoints.| |Voice Quality SLA|Info about calls included in the Skype for Business voice quality [SLA](https://go.microsoft.com/fwlink/p/?linkid=846252).| @@ -222,7 +221,7 @@ Similarly, the Client-Client tab has five collapsible sections: #### Inside versus Outside -CQD classifies a stream as *Inside* or *Outside* using Building information, if it exists. Endpoints of each stream are associated with a subnet address. If the subnet is in the list of the subnets marked InsideCorp in the uploaded Building information, then it is considered *Inside*. If Building information has not yet been uploaded, then Inside Test always classifies the streams as *Outside*. +CQD classifies a stream as *Inside* or *Outside* using Building information, if it exists. Endpoints of each stream are associated with a subnet address. If the subnet is in the list of the subnets marked InsideCorp in the uploaded Building information, then it's considered *Inside*. If Building information hasn't been uploaded yet, then Inside Test always classifies the streams as *Outside*. The Inside Test for a Server-Client scenario only considers the client endpoint. Because servers are always outside from a user's perspective, this isn't accounted for in the test. @@ -231,7 +230,7 @@ The Inside Test for a Server-Client scenario only considers the client endpoint. As the names indicate, the classification criteria is based on the type of client connections. Server is always wired and it isn't included in the calculation. In a given stream, if one of the two endpoints is connected to a WiFi network, then CQD classifies it as WiFi. > [!NOTE] -> Given a stream, if one of the two endpoints is connected to a WiFi network, then it is classified as WiFi in CQD. +> Given a stream, if one of the two endpoints is connected to a WiFi network, then it's classified as WiFi in CQD. ## Tenant Data information @@ -253,25 +252,25 @@ We recommend that you upload your tenant, building, and location data so CQD can |Failure Drill Down Reports|Drill downs: Date by region, locations, subnets, hour, and users.| |Rate My Call Reports|Analyze user call ratings by region, location, or by user. Includes verbatim feedback.| |Help Desk Reports|Help Desk Reports look at call and meeting data for individual users, groups of users, or everyone. Incorporating building and EUII data, these reports help identify possible system issues based on network location, conference details, devices, or firmware.| -|Client Version Reports|Client Version Summary: View the Sessions and Users counts for each client app version

Client Version by User: View user names for each client app version

Pre-built filters for Product and Client Type help focus the versions to specific clients.| +|Client Version Reports|Client Version Summary: View the Sessions and Users counts for each client app version

Client Version by User: View user names for each client app version

Prebuilt filters for Product and Client Type help focus the versions to specific clients.| |Endpoint Reports|Shows call quality by machine endpoints (computer make and model). These reports include building data, if you've uploaded it.| ## Create custom detailed reports If the default CQD reports don't meet your needs, use these instructions to create a custom report. Or [Use Power BI for CQD reports](cqd-power-bi-query-templates.md) instead. -From the pull-down list of reports at the top of the screen displayed at login \(the **Summary Reports** screen\) Select **Detailed Reports** and then **New**. Click **Edit** in a report to see the Query Editor. Each report is backed by a query into the cube. A report is a visualization of the data returned by its query. The Query Editor helps you edit these queries and the display options of the report. +From the pull-down list of reports at the top of the screen displayed at login \(the **Summary Reports** screen\) Select **Detailed Reports** and then **New**. Select **Edit** in a report to see the Query Editor. Each report is backed by a query into the cube. A report is a visualization of the data returned by its query. The Query Editor helps you edit these queries and the display options of the report. > [!IMPORTANT] -> The network range can be used to represent a supernet (combination of several subnets with a single routing prefix). All new building uploads will be checked for any overlapping ranges. If you have previously uploaded a building file, you should download the current file and re-upload it to identify any overlaps and fix the issue before uploading again. Any overlap in previously uploaded files may result in the wrong mappings of subnets to buildings in the reports. Certain VPN implementations do not accurately report the subnet information. It is recommended that when adding a VPN subnet to the building file, instead of one entry for the subnet, separate entries are added for each address in the VPN subnet as a separate 32-bit network. Each row can have the same building metadata. For example, instead of one row for 172.16.18.0/24, you should have 256 rows, with one row for each address between 172.16.18.0/32 and 172.16.18.255/32, inclusive. +> The network range can be used to represent a supernet (combination of several subnets with a single routing prefix). All new building uploads will be checked for any overlapping ranges. If you have previously uploaded a building file, you should download the current file and re-upload it to identify any overlaps and fix the issue before uploading again. Any overlap in previously uploaded files may result in the wrong mappings of subnets to buildings in the reports. Certain VPN implementations do not accurately report the subnet information. It's recommended that when adding a VPN subnet to the building file, instead of one entry for the subnet, separate entries are added for each address in the VPN subnet as a separate 32-bit network. Each row can have the same building metadata. For example, instead of one row for 172.16.18.0/24, you should have 256 rows, with one row for each address between 172.16.18.0/32 and 172.16.18.255/32, inclusive. > > The VPN column is optional and will default to 0. If the VPN column's value is set to 1, the subnet represented by that row will be fully expanded to match all IP addresses within the subnet. Please use this sparingly and only for VPN subnets since fully expanding these subnets will have a negative impact on query times for queries involving building data. -Point to bar charts and trend lines in the report to display detailed values. The report that has focus will show the action menu: **Edit**, **Clone**, **Delete**, **Download**, and **Export Report Tree**. +Point to bar charts and trend lines in the report to display detailed values. The report in focus shows the action menu: **Edit**, **Clone**, **Delete**, **Download**, and **Export Report Tree**. ## Query filters -Query filters are implemented by using the Query Editor in CQD. These filters are used to reduce the number of records returned by CQD, thus minimizing the report's overall size and query times. This is especially useful for filtering out unmanaged networks. The filters listed in the following table use regular expressions (RegEx). +Query filters are implemented by using the Query Editor in CQD. These filters are used to reduce the number of records returned by CQD, thus minimizing the report's overall size and query times. Query filters are especially useful for filtering out unmanaged networks. The filters listed in the following table use regular expressions (RegEx). |Filter|Description|CQD query filter example| |---|---|---| @@ -296,27 +295,15 @@ CQD reports feature several drill-down filters, which are powerful tools for nar ![Diagram illustrating drill-down report flow.](media/qerguide-image-drillthrureportflow.png) -#### Adding and editing drill-down fields - -When editing a report, you have the option to specify drill-down fields of your own using the Query Editor. - -Start by clicking **...** for the report you want to edit, then select **Edit**. - -![Screenshot of editing a drill-down field.](media/qerguide-image-addeditdrilldownfields.png) - -Select a Dimension from the list on the left side of the Query Editor. Then click on the dropdown below the **Navigate To** label and select the tab and expander group that you want that Dimension to drill through to. Note: Presently, drill-down functionality only works by navigating to different tabs. Support for drilling through to a specific expander will be added later. Finally, click **Close** to save your changes to the Dimension, then click **Save** to save and close the Query Editor. - -![Screenshot of selecting a dimension in the Query Editor.](media/qerguide-image-selectquerydimension.png) - ### Multi-select filters In addition to drill-down functionality, CQD also supports specifying Filters with multiple values (OR filters). -In order to select multiple filter values, begin by adding a new filter to the report. Click **+** beside the **Filters** label, enter the name of the Dimension you want to use, and click **Add**. +In order to select multiple filter values, begin by adding a new filter to the report. Select **+** beside the **Filters** label, enter the name of the Dimension you want to use, and select **Add**. -![Screenshot of adding a multi-select filter.](media/qerguide-image-addmultiselectfilter.png) +![Screenshot of adding a multi-select filter.](media/cqd-multi-select-filters.png) -Then, click **Search** (a magnifying glass icon next to the new filter). You'll see a text field, and a number of options, including **Select All** and **Invert**. Enter a value, and click **Search** next to that field to search. Alternatively, leave the text field empty and click **Search** to view up to the first 100 options. +Then, select **Search** (a magnifying glass icon next to the new filter). You'll see a text field, and a number of options, including **Select All** and **Invert**. Enter a value, and select **Search** next to that field to search. Alternatively, leave the text field empty and select **Search** to view up to the first 100 options. ```URL /filter/[AllStreams].[Second Tenant Id]\|[YOUR TENANT ID HERE] @@ -324,13 +311,13 @@ Then, click **Search** (a magnifying glass icon next to the new filter). You'll Example: -![Screenshot of adding a query filter.](media/qerguide-image-addfilter.png) +![Screenshot of adding a query filter.](media/cqd-multi-select-filters-2.png) ### Dashboard level filters Certain CQD reports have dashboard-level filters added to them, making it easy to filter by common parameters. These filters appear outside the regular report tabs and directly beneath the Product filter, and they apply to all filters in the Dashboard. -![Screenshot of a dashboard filter.](media/qerguide-image-dashboardfilters.png) +![Screenshot of a dashboard filter.](media/cqd-dashboard-level-filters.png) ```URL /filter/[AllStreams].[Is Teams]|[TRUE | FALSE] diff --git a/Teams/devices/teams-ip-phones.md b/Teams/devices/teams-ip-phones.md index 9697d524d8..d1a9a6de82 100644 --- a/Teams/devices/teams-ip-phones.md +++ b/Teams/devices/teams-ip-phones.md @@ -270,6 +270,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| |:----------------|:-------------------|:----------------------------|:-------------------------------------------------------------------|:---------------------------| +| 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`| September 24, 2024| | 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 8, 2024| | 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 3, 2023| | TSS-770/TSS-1070 | `2.004.1026` | N/A| Teams client: `1449/1.0.97.2022748302`
Company Portal: `5.0.5484.0`
Admin Agent: `1.0.0.202301162118.product`| June 9, 2023| diff --git a/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md b/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md index 8fbb578c41..96efad74fb 100644 --- a/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md +++ b/Teams/dimensions-and-measures-available-in-call-quality-dashboard.md @@ -456,6 +456,8 @@ Second Media Bypass | Boolean | Indicates if the audio stream was bypassing the | Second Capture Dev Name| String | Name of the audio capture device used by the second endpoint. || | First Render Dev Name| String | Name of the audio playback device used by the first endpoint. || | Second Render Dev Name| String | Name of the audio playback device used by the second endpoint. || +| First Noise Suppression Model Download Failure | Boolean | Indicates if the First endpoint successfully downloaded the noise suppression model prior to outbound audio stream establishment. | • Noise suppression model download is not applicable to or supported by the endpoint or codec.
• Stream is not outbound audio. | +| Second Noise Suppression Model Download Failure | Boolean | Indicates if the Second endpoint successfully downloaded the noise suppression model prior to outbound audio stream establishment. | • Noise suppression model download is not applicable to or supported by the endpoint or codec.
• Stream is not outbound audio. | |**Measure**|||| | ClassifiedPoorCall | Boolean | True if one or more streams in the call were classified as poor based on the metrics listed in [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | • The call didn't have sufficient metrics reported to be classified as good or poor | | Video Poor Due To VideoPostFecplr | Boolean | True if the stream is classified as poor based on the Video Post FEC PLR metric threshold listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). Is always False for non-video streams. | • The endpoint didn't report this data
• The stream wasn't a video stream. | @@ -774,6 +776,10 @@ Many Measurement values can also be used as filters. The following table lists t | Audio Good Call Count |Number of calls|Number of calls involving audio classified as good. There's an up to 0.2% error for this measure. See notes below for details.| | Audio Unclassified Call Count |Number of calls|Number of calls involving audio that couldn't be classified Good or Poor. Unclassified calls are omitted from 'Poor Call Percentage' calculations. There's an up to 0.2% error for this measure. See note below for details.| | Audio Poor Call Percentage |Percentage of calls|Percentage of classified calls involving audio classified as poor. There's an up to 0.2% error for this measure. See note below for details.| +| First Noise Suppression Model Download Failure Count | Number of streams | Number of outbound audio streams where First endpoints failed to download the noise suppression model successfully.| +| Second Noise Suppression Model Download Failure Count | Number of streams | Number of outbound audio streams where Second endpoints failed to download the noise suppression model successfully.| +| First Noise Suppression Model Download Failure Percentage | Percentage of streams (Decimal) | Percentage of outbound audio streams where First endpoints failed to download the noise suppression model successfully.| +| Second Noise Suppression Model Download Failure Percentage | Percentage of streams (Decimal) | Percentage of outbound audio streams where Second endpoints failed to download the noise suppression model successfully.| |AppSharing Stream Count |Number of streams |Number of RDP-based application sharing streams. | |AppSharing Poor Due To SpoiledTilePercentTotal Count |Number of streams |Number of application sharing streams where the spoiled tile percent total metric exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | |AppSharing Poor Due To RelativeOneWayAverage Count |Number of streams |Number of application sharing streams where the relative one-way average metric exceeds thresholds listed here: [Stream Classification in Call Quality Dashboard](stream-classification-in-call-quality-dashboard.md). | diff --git a/Teams/export-teams-content.md b/Teams/export-teams-content.md index 09934710f7..0f8aef4426 100644 --- a/Teams/export-teams-content.md +++ b/Teams/export-teams-content.md @@ -49,7 +49,7 @@ Here are some examples on how you can use these export APIs: - **Deleted Users**: Export API supports capturing messages for deleted users up to 30 days from the time the user was deleted. To find the list of deleted users, see [Deleted Items](/graph/api/directory-deleteditems-list). - **Chat Message Properties:** Refer to the [complete list of properties that Teams Export APIs support](/graph/api/resources/chatmessage#properties). - **Control Messages:** Export API supports capturing control messages in addition to the user generated messages. Control Messages are system generated messages that appear on the Teams client and carry important information such as "User A added User B to the chat and shared all chat history" along with the timestamp. System messages enable the caller to have insights about events that happened in a team, a channel, or a chat. Currently Export API supports the [Add Member and Remove Member event for chats, teams and standard channels](/graph/system-messages#supported-system-message-events). -- **(Beta) Edited History:** Provided that [your tenant is setup with Teams Retention Policy](/purview/create-retention-policies?tabs=teams-retention), Export API supports capturing messages' edited history for [individual & group chat](/graph/api/chat-getallretainedmessages), and [posts, comments in Public & Shared channels](/graph/api/channel-getallretainedmessages). +- **Edited History:** Provided that [your tenant is setup with Teams Retention Policy](/purview/create-retention-policies?tabs=teams-retention), Export API supports capturing messages' edited history for [individual & group chat](/graph/api/chat-getallretainedmessages), and [posts, comments in Public & Shared channels](/graph/api/channel-getallretainedmessages). To learn more about Teams Retention policy, see the [Manage retention policies for Microsoft Teams](/microsoftteams/retention-policies) for further details. diff --git a/Teams/media/cqd-dashboard-level-filters.png b/Teams/media/cqd-dashboard-level-filters.png new file mode 100644 index 0000000000..38432e2589 Binary files /dev/null and b/Teams/media/cqd-dashboard-level-filters.png differ diff --git a/Teams/media/cqd-multi-select-filters-2.png b/Teams/media/cqd-multi-select-filters-2.png new file mode 100644 index 0000000000..6cf406c6a0 Binary files /dev/null and b/Teams/media/cqd-multi-select-filters-2.png differ diff --git a/Teams/media/cqd-multi-select-filters.png b/Teams/media/cqd-multi-select-filters.png new file mode 100644 index 0000000000..af6f411a5b Binary files /dev/null and b/Teams/media/cqd-multi-select-filters.png differ diff --git a/Teams/media/cqd-product-filter.png b/Teams/media/cqd-product-filter.png new file mode 100644 index 0000000000..76c690fcda Binary files /dev/null and b/Teams/media/cqd-product-filter.png differ diff --git a/Teams/rooms/bring-your-own-device.md b/Teams/rooms/bring-your-own-device.md index 96e1addffe..0727effcf4 100644 --- a/Teams/rooms/bring-your-own-device.md +++ b/Teams/rooms/bring-your-own-device.md @@ -4,7 +4,7 @@ author: mstonysmith ms.author: tonysmit manager: pamgreen ms.reviewer: eshanmathur -ms.date: 01/29/2024 +ms.date: 09/26/2024 ms.topic: article ms.tgt.pltfrm: cloud ms.service: msteams @@ -29,10 +29,9 @@ Bring Your Own Device rooms are identified as rooms with no Microsoft Teams Room 1. Open Pro Management Portal on [https://portal.rooms.microsoft.com/](https://portal.rooms.microsoft.com/) and navigate to **Inventory**. 2. In the left navigation menu, select **Planning** and go to **Inventory**. -> [!NOTE] -> For the devices to be captured in Pro Management Portal as Bring Your Own Devices, users need to plug the device into the laptop in the room and join a meeting. We require at least five unique users to report the devices, which will then be displayed in the Pro Management Portal as shared devices. -> -> Devices such as speaker, microphone, camera, display, etc can be plugged into a laptop and captured as shared devices in a BYOD room. ## Inventory page. + > [!NOTE] + > For the devices to be captured in Pro Management Portal as Bring Your Own Devices, users need to plug the device into the laptop in the room and join a meeting. We require at least five unique users to report the devices, which will then be displayed in the Pro Management Portal as shared devices. + > Devices such as speaker, microphone, camera, display, etc can be plugged into a laptop and captured as shared devices in a BYOD room. ## Inventory page. In the **Inventory** page, you'll find an overview of all the rooms within your organization. You can explore your organization's inventory and devices and you can find rooms based on specific groups (country, city, buildings) or by utilizing the search function. @@ -45,19 +44,19 @@ This page provides a comprehensive summary of your rooms, featuring the followin - The total number of rooms in your tenant categorized by type (Microsoft Teams Rooms, Bring Your Own Device). -> [!NOTE] -> The Devices and Rooms association needs to be done in order to view your **Bring Your Own Device** rooms under the **Rooms** page. + > [!NOTE] + > The Devices and Rooms association needs to be done in order to view your **Bring Your Own Device** rooms under the **Rooms** page. - Rooms by capacity: Distribution of rooms by capacity, with a breakdown into small, medium, and large rooms. -The following table describes the columns in the **Rooms** view of Inventory. + The following table describes the columns in the **Rooms** view of Inventory. -| **Column** | **Description** | -| --- | --- | -| Display name | Name of the room | -| Capacity | Illustrate the room's capacity number | -| Room type | Type of the room either Teams Rooms or Bring Your Own Device | -| Licenses Type | Type of license assigned to the room (for example, pro, premium, basic, standard, shared licenses, or unlicensed) | + | **Column** | **Description** | + | --- | --- | + | Display name | Name of the room | + | Capacity | Illustrate the room's capacity number | + | Room type | Type of the room either Teams Rooms or Bring Your Own Device | + | Licenses Type | Type of license assigned to the room (for example, pro, premium, basic, standard, shared licenses, or unlicensed) | Below the headline, you'll find a table with specific information about each room: @@ -67,21 +66,21 @@ When you select a specific room, you'll see a new pane with two different pages, - **The General page:** Provides the following room information: -| Name | The name of the room | -| --- | --- | -| Seating Capacity | The room's capacity | -| OEM name | The manufacturer name | -| Resource account | The account associated with the room | -| Room address | The physical address of the room (street, city, zip code, building, floor) | + | Name | The name of the room | + | --- | --- | + | Seating Capacity | The room's capacity | + | OEM name | The manufacturer name | + | Resource account | The account associated with the room | + | Room address | The physical address of the room (street, city, zip code, building, floor) | - **The Inventory page** displays detailed information about the room's devices: -| **Column** | **Description** | -| --- | --- | -| Name | Name of the device | -| Type | Type of device (for example, Microsoft Teams Rooms, TeamsPanel, camera.) | -| Make | Manufacturer name | -| SerialNumber | The device's serial number | + | **Column** | **Description** | + | --- | --- | + | Name | Name of the device | + | Type | Type of device (for example, Microsoft Teams Rooms, TeamsPanel, camera.) | + | Make | Manufacturer name | + | SerialNumber | The device's serial number | ### Device view @@ -124,19 +123,18 @@ To associate a device with a room, the following two methods are available: 5. Go back to the Inventory Devices page and click **Import** to upload the modified file. 6. Verify that the device-room association is updated successfully. - > [!NOTE] - > In cases where the devices were not discovered or reported by Pro Management portal, admins can add those new devices using the import function. Device information such as the Product ID, Vendor ID, Serial Number, and Account information are required for the association to be done. + > [!NOTE] + > In cases where the devices were not discovered or reported by Pro Management portal, admins can add those new devices using the import function. Device information such as the Product ID, Vendor ID, Serial Number, and Account information are required for the association to be done. - **Manually associate discovered devices using Pro Management UI:** - 1. Go to the device table. - 1. Select the specific device group with the **Need Action** banner. - 1. Click **Add a room to this device**. - 1. Select the desired room from the list to associate the devices with. - 1. Click **Save**. - -:::image type="content" source="../media/byod/device-discovery.png" alt-text="Screenshot of device room association." lightbox="../media/byod/device-discovery.png"::: + 1. Go to the device table. + 1. Select the specific device group with the **Need Action** banner. + 1. Click **Add a room to this device**. + 1. Select the desired room from the list to associate the devices with. + 1. Click **Save**. + :::image type="content" source="../media/byod/device-discovery.png" alt-text="Screenshot of device room association." lightbox="../media/byod/device-discovery.png"::: ## Devices automatically discovered by the Pro Management Portal @@ -155,49 +153,48 @@ To view the Usage report for your Bring Your Own Device rooms: 1. In the left navigation menu, select **Reports**. 1. In the Reports page, select the **BYOD Usage** tab. -:::image type="content" source="../media/byod/usage-report.png" alt-text="Screenshot of Usage Report." lightbox="../media/byod/usage-report.png"::: -The headlines provide few rooms’ insights described in the following table: + :::image type="content" source="../media/byod/usage-report.png" alt-text="Screenshot of Usage Report." lightbox="../media/byod/usage-report.png"::: -| Metrics | Description | -|---|---| -| **Total rooms** | Total number of Bring Your Own Device rooms | -| **Unused rooms** | Number of Bring Your Own Device rooms with no calls | -| **Used rooms** | Number of Bring Your Own Device rooms used based on calls made | -| **Utilization** | Percentage of utilization of all Bring Your Own Device rooms across the tenant.
Utilization = Total call duration (all rooms) / (Workdays * workday hour * Bring Your Own Device rooms)
For example: If the tenant has 15 Bring Your Own Device Rooms, total call duration for all rooms is 300 h, work days = 10, work day hour = 8 h; then Utilization = 300/(10\*8\*15)= 25% | -| **Audio and video calls** | Will generate the duration of the audio call and video camera | -| **Overall call performance** | Overall Percentage of calls rated as “Good” out of the total calls in the room. Each call is evaluated and receives a Good, poor, Unknown rating. | -| **Total calls** | Overall number of calls made in Bring Your Own Device rooms | + The headlines provide few rooms’ insights described in the following table: -Below the headline metrics, there's a table that provides a granular breakdown of individual Bring Your Own Device rooms, accompanied by specific metrics that illuminate each room’s usage and performance during the period selected. + | Metrics | Description | + |---|---| + | **Total rooms** | Total number of Bring Your Own Device rooms | + | **Unused rooms** | Number of Bring Your Own Device rooms with no calls | + | **Used rooms** | Number of Bring Your Own Device rooms used based on calls made | + | **Utilization** | Percentage of utilization of all Bring Your Own Device rooms across the tenant.
Utilization = Total call duration (all rooms) / (Workdays * workday hour * Bring Your Own Device rooms)
For example: If the tenant has 15 Bring Your Own Device Rooms, total call duration for all rooms is 300 h, work days = 10, work day hour = 8 h; then Utilization = 300/(10\*8\*15)= 25% | + | **Audio and video calls** | Will generate the duration of the audio call and video camera | + | **Overall call performance** | Overall Percentage of calls rated as “Good” out of the total calls in the room. Each call is evaluated and receives a Good, poor, Unknown rating. | + | **Total calls** | Overall number of calls made in Bring Your Own Device rooms | -| **Column** | **Description** | -|---|---| -| **Display room name** | The designated name of the Bring Your Own Device room | -| **Room Type** | Will show as “Bring Your Own Device Room” as room type | -| **Utilization** | The percentage of total call duration spent in a Bring Your Own Device room during business hours in the selected period.
For example, for a time period set to 10 Work days for room A, total call duration for room A is 12 h and Work Day Hour = 8 h; then room utilization = Total Call Duration in Room / (Work Days * Work Day Hour) = 12/(10\*8) = 15% | -| **Total calls** | Total count of calls conducted in the room during the specified timeframe | -| **Call performance** | Percentage of calls rated as “Good” out of the total calls in the room. Each call is evaluated and receives a Good, poor, Unknown rating. | + Below the headline metrics, there's a table that provides a granular breakdown of individual Bring Your Own Device rooms, accompanied by specific metrics that illuminate each room’s usage and performance during the period selected. + + | **Column** | **Description** | + |---|---| + | **Display room name** | The designated name of the Bring Your Own Device room | + | **Room Type** | Will show as “Bring Your Own Device Room” as room type | + | **Utilization** | The percentage of total call duration spent in a Bring Your Own Device room during business hours in the selected period.
For example, for a time period set to 10 Work days for room A, total call duration for room A is 12 h and Work Day Hour = 8 h; then room utilization = Total Call Duration in Room / (Work Days * Work Day Hour) = 12/(10\*8) = 15% | + | **Total calls** | Total count of calls conducted in the room during the specified timeframe | + | **Call performance** | Percentage of calls rated as “Good” out of the total calls in the room. Each call is evaluated and receives a Good, poor, Unknown rating. | ### Bring Your Own Device call utilization detailed view To see the call utilization view for each room, select the specific Bring Your Own Device room from the table. There will be a new pane, which gives a detailed view of devices call utilization based on selected period. > [!NOTE] -> Only rooms with Teams Shared Devices or Pro licenses and which are associated with their peripherals are shown in the Bring Your Own Device usage report. -> > Great news! for this first release, customers can utilize the Bring Your Own Device usage data without an additional Teams shared device license until April 8th, 2024. -> ## Settings -#### BYOD Rooms and Desk management -This setting option is located under the "General" tab and controls if peripheral data from BYOD and desk is sent to Microsoft. This feature is currently enabled by default, but admins have the option to disable it with this function. -#### Delete device data. -This setting option enables admins to delete data for a specific user upon request. With the search function, IT Admins can be able to search for the name of the specific user and delete all related data. +> Only rooms with Teams Shared Devices or Pro licenses and which are associated with their peripherals are shown in the Bring Your Own Device usage report. +> > Great news! for this first release, customers can utilize the Bring Your Own Device usage data without an additional Teams shared device license until April 8th, 2024. + +## Settings + ## Access Control & Configuration -### Turning off automatic discovery & usage data collection +### Turning off automatic discovery & usage data collection in the Teams client The Teams BYOD solution uses peripheral data crowdsourced from the Teams client application running on user's computers to discover peripherals as well as understand when those peripherals (and the rooms they are associated to) are used. No personally identifiable data is collected, but should you feel that this data collection is inappropriate for certain users or groups in your organization, you may use the following PowerShell commands to enable or disable BYOD data collection via a Teams policy setting, as well as get the current policy setting status, create a new policy, and remove a policy. > [!WARNING] -> Disabling this policy setting for certain users will cause BYOD usage information to cease flowing to the service. The Teams BYOD solution requires peripheral data sent from users to calculate usage reports for BYOD peripherals and rooms. +> Disabling this policy setting for certain users will cause BYOD and desk usage information to cease flowing to the service. The Teams BYOD and Desk solution requires peripheral data sent from users to calculate usage reports for peripherals, BYOD rooms, and desks. ``` Get-CsTeamsBYODAndDesksPolicy @@ -207,6 +204,16 @@ Set-CsTeamsBYODAndDesksPolicy -Identity "Test" -DeviceDataCollection Enabled Remove-CsTeamsBYODAndDesksPolicy -Identity "Test" ``` +### Configuring Cloud Data + +**BYOD Rooms and Desk management** + +This setting option is located under the **General** tab in Teams Pro Management portal and controls if peripheral data is ingested into the cloud service. This feature is currently enabled by default, but admins have the option to disable it with this function. Disabling this setting will stop showing any usage reports for BYOD rooms or Desks, and also remove the display of any devices in the **Inventory** section, though those devices will continue to exist in the database. + +**Delete Device Data** + +This setting option enables admins to delete all device management data for a specific user. + ### Inventory management permission -This new inventory permission allows other users to view and manage the inventory management. IT Admins can create roles and grant other users' permission to access the inventory management and perform devices association with rooms. +The inventory management permission in Teams Pro Management portal allows other users to view and manage the inventory management. You can create roles and grant other users permission to access inventory management and associate peripherals to rooms or desks. diff --git a/Teams/teams-add-on-licensing/licensing-enhance-teams.md b/Teams/teams-add-on-licensing/licensing-enhance-teams.md index 8a739ad681..7a9f4fe20f 100644 --- a/Teams/teams-add-on-licensing/licensing-enhance-teams.md +++ b/Teams/teams-add-on-licensing/licensing-enhance-teams.md @@ -1,7 +1,7 @@ --- title: Microsoft Teams Premium licensing -author: DaniEASmith -ms.author: danismith +author: wlibebe +ms.author: wlibebe manager: pamgreen ms.reviewer: margidesai, spraveen ms.date: 03/26/2024 @@ -307,6 +307,10 @@ A user's Teams experience depends on their Teams license and their event role. T For example, in a Teams meeting, Teams checks each users’ type of Teams license and whether they're a meeting organizer or attendee. These factors determine a user’s experience and potentially other attendees’ experience during the meeting. - **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. + - **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.