MicrosoftDocs · mashbynz · Oct 18, 2024 · Oct 18, 2024 · Oct 18, 2024 · Oct 18, 2024
diff --git 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
@@ -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
diff --git 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)</br>[Video 2: Plan your upgrade](https://aka.ms/teams-upgrade-plan)</br>[Video 3: Coexistence and Interoperability](https://aka.ms/teams-upgrade-coexistence-interop)</br>[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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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)