Microsoft Teams Support articles

Spend less time hunting for meeting issues with the Best Practice Configurations dashboard in Teams

DJ1298 — Thu, 30 Apr 2026 16:26:02 GMT

https://learn.microsoft.com/microsoftteams/best-practice-dashboard

The dashboard is built to help admins monitor meeting-related best practices across the environment. It highlights common causes of meeting quality, such as correct ports and protocols being used, outdated Teams clients, DNS resolution failures, local and cloud proxy bypass configuration, and VDI optimization. This helps you see patterns to allow you can focus on broad issues affecting many users, not just one report at a time.

Why should you start using this today?

- You don’t just see that something is wrong—you see the issue paired with recommendations to resolve.

- Issues are grouped by location and network segment, which makes it easier to spot systemic problems.

- It reduces manual investigation, as issue details are shown based on location and IP.

- It helps track improvement over time. As you address recommendations, the dashboard shows trends so you can monitor progress.

- It helps admins keep an eye on their tenant ecosystem proactively. If the configurations are correct, it reduces the chances of users facing meeting quality issues.

A few examples of when to use it:

1. When users start mentioning Teams meeting quality issues

If users in a specific city are reporting poor Teams meeting experiences, the dashboard can help you quickly see whether that location has a high percentage of traffic using TCP instead of UDP, outdated clients, proxy routing, or DNS resolution failures. Instead of investigating each complaint separately, you can identify whether the issue is tied to a shared network path, public IP range, or regional setup and work the root cause first.

2. When you want to clean up outdated Teams clients

The dashboard shows locations with a high percentage of streams coming from Teams desktop clients more than three months old. Rather than manually gathering version data across the environment, you can immediately see the most affected locations and target update efforts where they will have the biggest impact.

3. When network or security changes may be affecting Teams traffic

If your organization uses VPN split tunneling, proxies, DNS controls, or VDI, the dashboard helps surface where those configurations may be hurting Teams media performance. You can move from “something changed and meetings feel worse” to a focused remediation plan based on the locations and traffic patterns flagged in the dashboard.

4. When you need to show progress

The dashboard includes trend views and CSV export, it can support conversations with networking, endpoint management, and security teams. You spend less effort building reports by hand and more time aligning the right teams on the next action.

If your team supports Microsoft Teams meetings, this dashboard is a good feature to start using now. It gives you a more structured way to find high-impact issues, follow Microsoft recommendations, and spend less time chasing symptoms.

New MRCA Diagnostic: Teams Meeting Add-in For Classic Outlook

Carlos Farrica — Thu, 23 Apr 2026 09:50:23 GMT

Hi Teams Community,

We're back with another great addition from Christopher Tart to Support Diagnostics for Microsoft Teams. We're excited to share that the

Teams Support team has added a new diagnostic to the Microsoft Remote Connectivity Analyzer — the Teams Meeting Add-in For Classic Outlook diagnostic.

If you manage Teams in your organization, you've likely seen this scenario come through your support queue more than once: a user opens classic Outlook to schedule a meeting and the Teams Meeting button is simply nowhere to be found.

This new diagnostic is here to help you quickly pinpoint what's blocking the add-in — whether it's a policy misconfiguration, a licensing gap, or a coexistence mode that's incompatible with the Teams add-in.

Some common symptoms this diagnostic helps you troubleshoot:

The Teams Meeting button is missing from the Outlook ribbon
The Teams add-in doesn't appear in Outlook's list of COM add-ins
Users are unable to schedule a Teams meeting directly from Outlook
Only the Skype Meeting option appears in Outlook, with no Teams option in sight

To access the new diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on Teams Meeting Add-in For Classic Outlook.

You'll need to sign in with a Teams account to run the test. Once authenticated — the diagnostic will then validate that user's configuration end to end.

At a high level, the test checks a couple of things:

The user is licensed for Microsoft Teams
The Teams Outlook add-in policy is enabled (TeamsUpgradePolicy / Teams meeting policies)
The user's coexistence and upgrade mode is compatible with the Teams Meeting add-in — users set to Skype for Business Only mode will not see the Teams add-in in Outlook
The Teams desktop client is installed and signed in on the user's machine
Exchange Online or on-premises connectivity is verified to confirm Outlook can reach Teams for meeting scheduling
Admin policies that may be suppressing the add-in are flagged (e.g., Outlook add-in management policies)

For more information, check out these resources:

Please give the new diagnostic a try — and let us know if it helped!

Thanks! Microsoft Teams Support

New MRCA Diagnostic: Guest Invite to Teams

Carlos Farrica — Fri, 24 Apr 2026 06:40:37 GMT

Hi Teams Community,

We're back with another great addition from RuiTabaresMsft to Support Diagnostics for Microsoft Teams. We're excited to share a new test now available in the Microsoft Remote Connectivity Analyzer — the Guest Invite to Team diagnostic.

Getting guest access working properly in Teams requires several settings across Microsoft 365 to all line up correctly, and when one of them is misconfigured it can be frustratingly difficult to pinpoint. This new diagnostic is designed to help admins quickly identify exactly where the configuration has gone wrong.

If you're experiencing any of the following symptoms, you should give this diagnostic a try:

A team owner is unable to add or invite a guest user to a Microsoft Team.
You receive an error such as "You don't have permission to add guests" when attempting to invite an external user.
Guest access appears to be enabled in the Teams admin center, but external users still can't join a team.
Guest users were previously able to be invited to teams, but invitations have stopped working after a recent configuration change.

To access the new diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on Guest Invite to Team.

We recommend signing in with a Teams or Microsoft 365 Administrator account. Because this diagnostic validates tenant-wide settings and Microsoft 365 group configuration, admin-level credentials are needed to return complete and accurate results.

At a high level, the test checks a couple of things:

Tenant guest access setting — Validates that "Allow guest access in Teams" is enabled in the Teams admin center.
Microsoft Entra ID external collaboration settings — Confirms B2B external collaboration is not blocked at the Entra ID level.
Microsoft 365 Groups guest settings — Checks that group owners are permitted to add external people as guests.
Team ownership — Verifies the team has at least one owner, as required to invite guests.

For background reading:

Please give the new diagnostic a try — and let us know if it helped!

Thanks! Microsoft Teams Support

Learn to deploy Teams Rooms on Windows in minutes with Autopilot + Autologin!

MattSlomka — Thu, 11 Dec 2025 18:03:36 GMT

It’s never been easier to deploy Teams Rooms on Windows devices at scale than with Autopilot and Autologin, you or your Microsoft Teams Rooms partner can securely deploy Teams Rooms in minutes. Simply take a Teams Rooms device out of the box, plug it in, and with no further interaction the device will:

Start up
Update to the latest Teams Rooms and Windows versions
Sign into Teams
Enroll into the Pro Management Portal for remote management

To make the magic happen, the device hardware identity must be uploaded into Intune as Autopilot device and an Intune administrator must configure Intune to automatically provision the devices for Autopilot. Then, to complete the Autologin portion, the meeting room admin within the Teams Rooms Pro Management Portal will match the Autopilot device with the resource account and either upload existing resource account passwords or automatically generate new passwords. With this process, we’ve heard feedback from customers and partners that one of the most challenging things is how to best get the device Autopilot information into Intune. There are various ways to collect and upload the Autopilot hardware identity:

OEMs can handle the entire process and upload it directly into Intune on your behalf
OEMs can provide the hardware identity information for upload by the IT admin or a Cloud Solution Provider
Some devices require hardware identity collection manually to then be uploaded by the IT admin or Cloud Solution Provider

Since each Teams Room device is a bit different, we’ve partnered with each Teams Rooms manufacturer to create instructional videos with their best practice recommendations for how to use Autopilot + Autologin to deploy their Teams Rooms on Windows devices including how they recommend uploading the device Autopilot information.

Additional Microsoft Resources:

Step by Step Documentation: Use Windows Autopilot and Autologin to easily deploy Microsoft Teams Rooms consoles - Microsoft Teams | Microsoft Learn
Step by Step YouTube video: Autopilot for Teams Rooms Windows Step-by-Step Tutorial
Teams Rooms Autopilot Registration Step by Step for Partners: Teams Rooms Autopilot Registration for Partners - Microsoft Teams | Microsoft Learn

Manufacturer	Video	Documentation
		Autopilot Landing Page Autopilot Registration
		Coming Soon!
		Autopilot Landing Page
		Autopilot Landing Page
	Coming Soon!
	Coming Soon!
	Coming Soon!
		Autopilot Landing Page Support Documentation

New Diagnostic: Copilot Agent Functionality in Microsoft Teams.

mofazil88 — Thu, 04 Sep 2025 18:19:38 GMT

As Microsoft Copilot for Microsoft 365 continues to evolve, ensuring reliable agent performance within Microsoft Teams is critical to delivering a seamless user experience. To support this, we’re introducing the Copilot Agent Functionality Diagnostic—a powerful tool designed to identify and resolve issues that may prevent Copilot agents from operating in Teams. This includes validating eligibility, confirming service availability, and checking for configuration compliance. With this test, organizations can quickly verify that their environment is optimized for Copilot agents, helping users fully leverage the capabilities of Copilot within Teams.

Why This Matters

For Copilot agents to function seamlessly in Microsoft Teams, several dependencies must be in place—including user authentication, valid license assignment, tenant app settings, and the ability to run required custom apps in preview. If any of these prerequisites are misconfigured, users may face errors, limited functionality, or even lose access to Copilot features altogether.

That’s where our Diagnostics comes in -The Copilot Agent Functionality Test helps eliminate these risks by proactively checking authentication, confirming license validity, validating Teams app configurations, and identifying settings that could block Copilot agents. By addressing these issues early, organizations can ensure users experience the full value of Copilot in Teams without disruption.

What the Diagnostic Does

The Copilot Agent Functionality Diagnostic is designed to help both customers and support engineers validate the critical requirements that enable Copilot agents to work seamlessly in Microsoft Teams. It performs a series of checks to confirm:

Successful retrieval of Teams user authentication information
Verification that users hold a valid Microsoft 365 Copilot license for Teams
Confirmation that custom apps in preview are enabled to support Copilot agents
Validation of Teams tenant app settings for proper permissions and availability
Identification of configuration gaps that may block agent functionality

By running these validations, the diagnostic ensures that the Teams environment is properly configured, reducing the likelihood of errors and empowering organizations to deliver a consistent Copilot experience in Microsoft Teams.

Who Should Use It?

Note: A Global Administrator account is required to run this diagnostic.

IT Admins validating Teams settings, app configurations, and license prerequisites to ensure Copilot agents function correctly.
Support Engineers troubleshooting Copilot agent issues related to authentication, configuration, or feature availability.
Adoption & Change Management Leads confirming the Teams environment is properly prepared for users to engage with Copilot agents during rollout.

Get Started

To run the diagnostic, you’ll need a Global Administrator account.

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select COPILOT, then click on the “Copilot Agent Functionality in Microsoft Teams”.

A Big Thank you to Rui Andre Tabares.

New Diagnostic: Copilot License Details check

mofazil88 — Mon, 25 Aug 2025 11:55:07 GMT

As Microsoft Copilot for Microsoft 365 continues to expand its capabilities, so must the tools that ensure a seamless user experience. One of the most important steps in enabling Copilot features is validating license assignments. To support this, we’re excited to introduce the Copilot License Check Diagnostic—a powerful tool designed to streamline and validate your license readiness by confirming whether Copilot for Microsoft 365 licenses are properly assigned to users, ensuring that features dependent on Copilot function as expected. Diagnostics makes it easy to validate license assignments, ensuring users are set to unlock the full power of Copilot.

Why This Matters

The ability to leverage Copilot for Microsoft 365 is directly tied to proper license assignment—a critical step in unlocking AI-powered productivity. Without the right license, users may be unable to access key Copilot features, leading to confusion or reduced value from your Microsoft 365 investment.

That’s where our Diagnostics comes in—helping you quickly validate license readiness, ensure feature availability, and streamline the path to a seamless Copilot experience.

What the Diagnostic Does

The Copilot License Check Diagnostic is built to empower both customers and support engineers. It validates whether users are properly licensed to access Copilot for Microsoft 365 by checking:

Assignment and validity of Copilot for Microsoft 365 licenses
User eligibility across Microsoft 365 services that integrate with Copilot
Dependency on prerequisite licenses (e.g., Microsoft 365 E3/E5, Office apps)
Checks all the service plans enabled within Copilot license.
Potential gaps that could block access to Copilot-powered capabilities

This diagnostic ensures that license readiness is confirmed in advance, reducing the risk of feature unavailability and helping organizations maximize the value of Copilot.

Who Should Use It?

Note: We can run the diagnostic either with Global admin or normal account.

IT Admins validating that users have the correct Copilot for Microsoft 365 licenses assigned
Support Engineers troubleshooting Copilot feature availability issues
Adoption & Change Management Leads ensuring users are ready to access Copilot as part of rollout plans

Get Started

We can run the diagnostic either with Global admin or normal account.

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select COPILOT, then click on the “Copilot License Details”.

A Big Thank you to Rui Andre Tabares.

(Updated!!) New Diagnostic: Microsoft Teams - Teams AOSP Migration Readiness

Carlos Farrica — Tue, 30 Sep 2025 12:10:09 GMT

As Microsoft Teams continues to evolve, so must the infrastructure that supports it. One of the most significant shifts in device management is the migration from Android Device Administrator (ADA) to Android Open Source Project (AOSP) for Teams devices. To support this transition, we’re excited to introduce the AOSP Migration Readiness MRCA Diagnostic—a powerful tool designed to streamline and validate your migration journey.

We have updated this Diagnostic with new firmware validation checkers!!

Why This Matters

The move to AOSP is more than a technical upgrade—it’s a strategic shift toward modern, secure, and scalable device management. With AOSP, organizations gain enhanced control, better compliance alignment, and a more unified experience across Teams-certified Android devices.

But migrations can be complex. That’s where our diagnostic comes in.

For detailed information, please consult Moving Teams Android Devices to AOSP Device Management.

What the Diagnostic Does

The AOSP Migration Readiness Diagnostic is built to empower both customers and support engineers. It checks whether your environment is ready for migration by validating:

The existence and validity of AOSP enrollment profiles
Intune tenant settings and compliance policies
Conditional Access configurations (e.g., MFA, Device Code Flow)
Firmware readiness and device association
End-of-life status for Teams-certified hardware

This diagnostic ensures that all prerequisites are met before initiating the migration, reducing the risk of disruption and improving the success rate of deployments.

Who Should Use It?

Note: you’ll need a Global Administrator account.

IT Admins preparing for large-scale Teams device migrations
Support Engineers troubleshooting enrollment or compliance issues
OEM Partners validating firmware readiness
Security Teams ensuring Conditional Access policies align with AOSP requirements

Get Started

To run the diagnostic, you’ll need a Global Administrator account.

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Teams AOSP Migration Readiness”.

A Big Thank you to Christopher Tart, Traci Herr, David Paulino and Gonçalo Sepulveda.

Microsoft Teams Devices - Device Code Flow Sign-In Issue – Remediation Guidance

MattSlomka — Wed, 06 Aug 2025 17:56:35 GMT

We're publishing additional guidance about a potential sign-in issue impacting Microsoft Teams-certified Android devices (e.g., Teams Rooms on Android, Teams Phones, Teams Panels, and Teams Displays). This issue stems from a new Entra ID Conditional Access policy targeting Device Code Flow (DCF) authentication. This new policy has been deployed to tenants as part of a Microsoft-wide Secure Future Initiative. While there are no additional deployments scheduled at this time, any future rollout plans will be communicated through official channels, including email and Microsoft 365 Message Center posts.

Although previously shared guidance here: Policy changes for Microsoft Teams devices using device code flow authentication | Microsoft Community Hub included steps to exclude Teams Android devices from this policy, we've observed devices which were not excluded and have been signed out.

How to restore full sign-in and remote login functionality on Teams Android devices

If you have Teams Android devices which were signed out, preferably log into the device manually. However, in the likely scenario these devices are in remote locations, complete the following steps to restore the remote login functionality:

Login to the Entra ID portal (https://www.entra.microsoft.com), navigate to your conditional access policies and edit the Microsoft-managed Conditional Access policy called "Block device code flow", exclude your Teams Android device resource accounts from the policy. You can also change the state from "On" to "Report-Only" or "Off" however, Microsoft recommends blocking device code flow in any scenario it's not explicitly required (Block Authentication Flows | Microsoft Learn). Once you've modified this policy, it will not activate again in your tenant.

Screenshot of the "block device code flow" policy in Entra ID.

Once the policy has been modified, reboot your Teams Android devices to force them to sign-in (you may need to reboot up to 3 times)
If rebooting the device fails, attempt to manually sign the device back in using valid Teams resource account credentials. If that also fails, you will need to factory reset the device to clear the invalid authentication state.
After restoring functionality, please ensure your devices are running the latest Teams application:

- - Teams Rooms on Android (both the compute and the console): 1449/1.0.96.2025205603
  - Teams Panel: 1449/1.0.97.2025086303
  - Teams Phone: 1449/1.0.94.2025168802
  - Teams Display: 1449/1.0.95.2024062804

SIP Gateway

If your organization uses Teams SIP devices, you do not need to create exclusion lists for them in case they get signed out. You can sign back in to SIP devices with the help of the SIP Gateway app. To prevent or mitigate impact for Teams SIP devices associated accounts, keep the policy in "Report Only" mode for those user or shared accounts.

Additional Resources

If you need help completing these steps or have questions, please contact your Microsoft account team or support representative.

New Diagnostic: Microsoft Teams Shared Channels now available in MRCA

SreejithSreedharan — Thu, 03 Apr 2025 20:22:08 GMT

We're excited to release another new diagnostic to the MRCA for troubleshooting issues related to Teams Shared channels. Thanks to RuiTabaresMsft who has done it again this time bringing you a comprehensive Microsoft Remote Connectivity Analyzer diagnostic for Shared channels.

To access the customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Teams Shared Channel Add Member”.

Since the release of Shared channels on Teams, one of the common trends reported is the issue related to adding internal and external users to channels. This involves configurations on Teams policies, O365 groups, and Entra B2B Direct Connect, along with additional prerequisites. We discuss the configuration and troubleshooting options in the following article: Collaborate with external participants in a shared channel

This new diagnostic will help you troubleshoot and test if you meet requirements for an internal or external user from outside tenant could be added to a shared channel including Share a channel with People and Collaborate with external participants in a channel.

At a high level the test checks a few things:

Checking the prerequisites for user to be add a member into a shared channel.
Validates that the user can generate an authentication token in Microsoft Teams.
Verifies that the specified mailbox is supported for the intended operation.
Retrieves the user's backend settings which includes configuration settings and preferences associated with the user in Microsoft Teams.
Validates the Teams and channel policies related to shared channels.
Validates the shared channel URI, retrieves the channel thread, and checks connectivity to chat services.
Validates that the group has the AllowToAddGuests setting enabled.
Validates that the tenant group settings for the AllowToAddGuests setting is enabled.
Retrieves the tenant ID associated with the external user.
Validates the cross-tenant access policies (XTAP) to ensure that they permit B2B direct collaboration.
Performs a cross-tenant access policy (XTAP) search.

Please try the new diagnostic if you're having trouble adding members or sharing a shared channel and let us know if it helped.

As always, we welcome your comments, feedback, and questions. Got an idea for a new diagnostic? Issues with this one? Let us know!

Thanks!
Microsoft Teams Support

Right Clicking Teams Taskbar Icon opens "Open With" Dialogue on Windows 10

Corbin_Meek — Tue, 25 Jun 2024 23:26:20 GMT

25 June, 2024 Update: This is now fixed in June 25, 2024—KB5039299 (OS Build 19045.4598) Preview - Microsoft Support - if you're still experiencing this issue update your Windows 10 OS to at least this Kb.

We recently identified a Windows known issue with custom Jump Lists that shipped in Windows 10 22H2. New Teams is one of several apps known to be impacted. When you right click on the New Teams icon in the taskbar on Win10 you might see an "Open With" dialogue instead of the expected Teams custom options (Status, Quit, etc).

Looks like:

Instead of:

You can work around this issue by setting Status via your Profile in the main Teams client window:

The good news is that the necessary fix has already been identified and prepared and will ship in a future update for Windows 10 22H2 soon.

To follow along monitor the Windows 10 update history page here:

Windows 10 update history - Microsoft Support

For more information about the JumpList known issue:

Windows 10, version 22H2 | Microsoft Learn

We apologize for the inconvenience.

Diagnostic: Teams Sign in Diagnostic (Updated) in MRCA

Carlos Farrica — Tue, 04 Jun 2024 11:23:15 GMT

Hi Teams Community,

We're back with an update to Support Diagnostics for Microsoft Teams. RuiTabaresMsft updated the Teams Sign in Diagnostic in Microsoft Remote Connectivity Analyzer.

This diagnostic will help you troubleshoot and test if you meet requirements for a Microsoft Teams user to be able to sign in.

To access the customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Teams Sign in”.

Sign in by using the credentials of the user account that you want to test.
Enter the provided verification code.
Select Verify.

This Diagnostic is a comprehensive check of all account requirements that a Microsoft Teams User needs to successfully sign in.

At a high level the test checks a few things:

Validates that a user can sign into Microsoft Teams.
Validates that a user isn´t disable.
Validates that conditional access is enabled. 
Validates that a user isn´t a B2B member. 
Validates the user sign-in events within the last 7 days in Microsoft Teams.

We welcome your comments, feedback and questions.

Thanks!
Microsoft Teams Support

Moving Teams Android Devices to AOSP Device Management

TabishJ — Fri, 17 Apr 2026 20:02:14 GMT

Update for GCC-High and DOD Customers

AOSP Device Management firmware builds are available for GCC-H and DOD tenants for all devices. Please note that devices in GCC-H and DOD tenants will need to be manually updated, there are no auto updates available.

Update for Commercial and GCC Customers

The migration to AOSP DM has been completed, please ensure all devices are running a firmware with AOSP Device Management included OR for devices which will not move to AOSP DM (see list further down in this blog post) please ensure they've been updated to run Company Portal version 5.0.6423.0 to ensure stability. Microsoft Learn documentation has been updated to support customers new to Teams Android devices, you can follow the guidance here for setting up a new environment.

We will retain the remaining content from the blog for historical reference.

------------------------------------------------------------------

Microsoft Teams Android devices will be commencing auto updates for firmware in order to migrate to Intune AOSP device management starting on May 15th. Please see the table for specific dates per device make and model.

These firmware updates will eventually not be pauseable.

Devices will simply take them following the phases set in Teams Admin Center:

Validation: 0-15 days
General: 16-45 days (default)
Final: 45-60 days

Thus if a device has an auto update start date of May 15th, for the first 15 days only devices in the Validation phase will be updated. Then from May 30th, devices in the General phase will start updating. Finally starting June 28th, devices in the Final phase will start updating. Please note that ring assignments will be assigned and executed on from the firmware (manual) availability date and not the auto update start date.

Please ensure that all prerequisites for AOSP device management migration are completed for your organization to ensure a smooth migration. Your devices may sign out during migration if the prerequisites are not carried out properly. You can use this tool to test for migration readiness: Microsoft Remote Connectivity Analyzer: Test Input

Please see the table below for the schedule of auto updates for your devices.

OEM	Device Type	Models	Firmware (manual) availability	Auto update start
AudioCodes	Phones	C455HD C470HD	Available	Complete
AudioCodes	Phones	C430HD C435HD	Available	Complete
AudioCodes	Rooms	RXV81 RXV200 RXPad	Available	Complete
AudioCodes	Panels	RX Panel	Available	Complete
Crestron	Panels	TSS-770 TSS-1070	Available	Complete
Crestron	Rooms	Crestron AIO Video Bar 70 Crestron Touch Panel TS-1070	Available	Complete
Cisco	Rooms	Cisco Room Bar Cisco Room Bar Pro Cisco Room Kit EQ Cisco Room Kit Pro Cisco Desk Pro Cisco Room Kit EQX Cisco Board Pro G2 75 Cisco Board Pro 55 Cisco Board Pro 75 Cisco Board Pro G2 55 Cisco Navigator	Available	Complete
Cisco	Panels	Cisco Navigator Panel	Available	Complete
DTEN	Rooms	DTEN D7X 75" DTEN D7X 55" DTEN Bar DTEN Mate TC	Available	Complete
Jabra	Rooms	Jabra Panacast 50 VBS Jabra Panacast 50 TC	Available	Complete
Logitech	Rooms	RallyBar [VR0019] RallyBar mini [VR0020] TAP IP [VR0029] RoomMate [VR0030] Logi Rallybar Huddle [VR0034]	Available	Complete
Logitech	Panels	Tap Scheduler [VR0028] DockFlex [VR0035]	Available	Complete
Neat	Rooms	Neat Pad [NF19A1] Neat Bar [NF19B1] Neat Board [NF19C1] Neat Bar Pro [NF21D1] Neat Bar Gen2 [NF22E1] Neat Board 50 [NF22H1] Neat Board Pro 65 [NF23K1]	Available	Complete
Neat	Displays	NeatFrame	Available	Complete
Neat	Panels	Neat Pad [NF19A1]	Available	Complete
Poly	Phones	CCX350	Available Note: Manual firmware availability requires updating to Teams app version 1449/1.0.94.2025084203 as a prerequisite	Complete
Poly	Phones	CCX400 CCX500 CCX505 CCX600 TrioC60	Available Note: Manual firmware availability requires updating to Teams app version 1449/1.0.94.2025084203 as a prerequisite	Complete
Poly	Rooms	Poly Studio X30 Poly Studio X50 Poly Studio X52 Poly Studio X70 Poly Studio X72 Poly Studio G7500 Poly Studio G62 Poly TC8 Poly TC10	Available	Complete
Poly	Panels	TC10 - Panel	Available	Complete
Yealink	Phones [MP5X]	MP54 MP56 MP58 CP965	Available Note: Manual firmware availability requires updating to firmware version 122.15.0.166 (for MP54/MP56/MP58) or firmware version 143.15.0.74 (for CP965) as a prerequisite	Complete
Yealink	Phones [MP5X E2]	MP54E2 MP56E2 MP58E2	Available Note: Manual firmware availability requires updating to firmware version 176.15.0.31 as a prerequisite	Complete
Yealink	Phones [MP5X E2]	MP52E2	Available Note: Manual firmware availability requires updating to firmware version 176.15.0.31 as a prerequisite	Complete
Yealink	Rooms	Yealink MeetingBar A10 Yealink MeetingBar A20 Yealink MeetingBar A30 Yealink MeetingBoard 65" Yealink MeetingBoard 86" Yealink Deskvision A24 Yealink CTP18 Yealink CTP25	Available	Complete
Yealink	Rooms	Yealink MeetingBar A40	Available	Complete
Yealink	Panels	Room Panel RoomPanel Plus	Available	Complete
Yealink	Panels	Room Panel E2 RoomPanel Plus E2	Available	Complete

We are pleased to announce that Microsoft Teams Android devices will be moving to Intune Android Open Source Project (AOSP) device management later this year. AOSP device management will be the mobile device management (MDM) platform for Teams devices going forward. This move will bring a more reliable experience, an improved deployment experience for admins, and it will serve as the platform for future innovation and richer management scenarios for Microsoft Teams Android devices (Teams Rooms, Teams panels, Teams phones, and Teams displays).

AOSP Device Management is the replacement for the legacy Android Device Administrator solution used for managing Teams Devices.

This mandatory migration will take place over several months in 2025. We’ve taken great care to minimize the end user and IT admin impact with this migration, but there is action required for you as the IT admin. Following our published guidance for migration will only take a few minutes and will ensure your devices are seamlessly migrated between MDM platforms with a simple firmware upgrade and set you up for success for new device enrollments in the future. End users will notice no difference in device functionality.

There are two parts to a successful migration to AOSP Device Management:

Step 1: Create new enrollment profiles & configuration/compliance policies in Intune. This step can be completed today, even before the firmware updates are available. Performing these steps will have no impact on existing devices but please note that failing to create enrollment profiles before performing step 2 will result in signed out Teams Devices.

Step 2: Once the AOSP Device Management capable firmware is released in Teams Admin Center, you will need to install the firmware updates for each of the supported Teams Devices. This firmware update will automatically unenroll the device from Device Administrator and re-enroll the device with AOSP Device Management using the enrollment profile created in Step 1. This entire process will be done while the device remains signed into Teams. These firmware updates will be made available from Teams Admin Center as a manual update to allow you time to slowly migrate your devices. Updates will switch to automatic for those with large quantities of devices.

Step by step guidance on how to complete steps 1 and 2 (as well as guidance for configuration & compliance policies) can be found in the AOSP Device Management migration admin guide.

For more details on the AOSP Device Management migration, watch the Step-by-Step AOSP Migration video linked below:

FAQ:

How will I know firmware is available for my devices?

When AOSP DM compatible firmware is available for your devices a firmware update will show as available for your Teams Device in Teams Admin Center labeled as AOSP.

Will the firmware update be pushed out automatically? My organization needs time to prepare!

AOSP DM firmware will initially be available as manual updates for a period of time, allowing organizations to prepare the prerequisites and test the new firmware on specifically selected devices. It will become a mandatory auto update only after this manual update period. See the table above.

Your organization can already complete the prerequisites of creating enrollment profiles and AOSP policies today even before the firmware is generally available.

Isn't Device Administrator being deprecated by end of year 2024? What happens if my devices haven't migrated to AOSP by then?

Although Device Administrator will be deprecated by end of year for devices with GMS, Teams Devices are not GMS devices and therefore will remain supported with Device Administrator for Intune enrollment until AOSP migration is completed as Device Administrator is not being deprecated for non-GMS devices. Read more here in the Intune blog on Device Administrator deprecation: Click Here

My organization uses device identifiers today combined with enrollment restrictions to limit Android Device Administrator enrollment, is there something similar with AOSP Device Management?

We've made this easier with AOSP Device Management! Teams Android Devices automatically enroll as corporate with no need to filter because when you set the Teams Devices toggle in the enrollment profile, only Teams Devices can enroll with AOSP DM, end user mobile devices do not have a way to enroll with AOSP DM so there is no need to use enrollment restrictions like before.

My organization does not enroll our Teams Android Devices in Intune today, do we need to do anything?

No, if your organization does not enroll its Teams Devices into Intune today and currently has the Intune license unassigned from accounts signing into Teams Devices, there will be no impact when you install the new device firmware which supports AOSP device management. Your devices will get the new management applications, but no action is required beyond updating the devices to the new firmware once released.

What happens if I don’t do anything?

Devices will initially be offered firmware updates manually through Teams Admin Center, however in H1CY25 this will change to automatic updates regardless of admin action.

If your organization does enroll its Teams devices into Intune, then by not creating an enrollment profile, devices will fail to enroll properly in Intune and will thus not be able to sign in (or sign out if they were already signed in before). Not creating new AOSP policies could lead to unexpected issues in your environment, as Device Administrator policies will not be migrated automatically.

Wait, I don’t have to enroll my devices in Intune at all? Why would I want to use Intune?

Intune provides a security wrapper around your devices allowing you to set security controls as well as detect if the device is compliant with your organization security requirements prior to allowing the device to sign in to your M365 instance.

Does this change mean I will no longer see my Teams Android Devices in Teams admin center or the Pro Management Portal?

No, this migration changes the enrollment method into Microsoft Intune but has no impact on the manageability inside of Teams admin center or the Teams Pro Management Portal.

Are there devices that will not migrate to AOSP Device Management?

All devices currently certified and supported for Microsoft Teams will be migrated, those devices can be found here:

There are some Teams Android Devices that were previously supported, but are now end of life, which you may still have in your environment, those legacy devices specifically not migrating are listed here:

AudioCodes C448HD (Teams Phone)
AudioCodes C450HD (Teams Phone)
AudioCodes RXV80 (Teams Rooms on Android)
Crestron UC-2 (Teams Phone)
Crestron UC-P8 (Teams Phone)
Crestron UC-P8-I (Teams Phone)
Crestron UC-P10 (Teams Phone)
Crestron UC-P10-I (Teams Phone)
Crestron UC-P8-C (Teams Phone)
Crestron UC-P8-C-I (Teams Phone)
Crestron UC-P10-C (Teams Phone)
Crestron UC-P10-C-I (Teams Phone)
Crestron UC-P8-TD (Teams Display)
Crestron UC-P8-TD-I (Teams Display)
Crestron UC-P10-TD (Teams Display)
Crestron UC-P10-TD-I (Teams Display)
EPOS Expand Vision 3T (Teams Rooms on Android)
EPOS Expand Vision 5T (Teams Rooms on Android)
EPOS Expand Control TC (Teams Rooms on Android)
EPOS Expand Control Panel (Teams Panel)
Lenovo ThinkSmart View (Teams Display)
Lenovo ThinkSmart View Plus (Teams Display)
Polycom Trio 8500 (Teams Phone)
Polycom Trio 8800 (Teams Phone)
Yealink T55/55A (Teams Phone)
Yealink T56/56A (Teams Phone)
Yealink T58/58A (Teams Phone)
Yealink CP960 (Teams Phone)
Yealink VP59 (Teams Phone)
Yealink MP52 (Teams Phone)
Yealink VC210 (Teams Rooms on Android)
Yealink DeskVisio 24 (Teams Display)

What happens with those devices that will not migrate?

The devices listed above will remain on Android Device Administrator. These devices can still be used once Android Device Administrator is fully deprecated but will be considered legacy and unsupported where features may be removed at any time. To use the device you will need to unenroll from Intune and then sign the device back in without an Intune license assigned to the account, more information about this can be found here: Manage Intune devices with Android device administrator | Microsoft Learn

Will I notice anything different with the devices after the migration?

No, the devices will not look any different from an end user perspective. As an IT admin you will see two new applications installed on your devices (visible in the software health tab in Teams Admin Center), these two applications are the “Authenticator” app and the “Microsoft Intune” app these applications replace the previous “Company Portal” application.

Does the sign-in process for devices change once this migration has been completed?

With the exception of the case with Device Code Flow documented below, there is no change to the sign-in process or the look and feel of your devices with this migration.

What if once this migration is complete, I take a device out of storage that has not been through the migration? Will I be able to upgrade it?

Yes, there will be out of box updates available to ensure devices are able to receive the latest apps and can be automatically enrolled using AOSP DM.

When creating the enrollment profile, how long should I set the enrollment profile token expiration date?

If you're participating in a private preview of AOSP DM, please ensure your enrollment policy has a 90 day or shorter expiration, at GA you can replace this with an extended enrollment profile. Those waiting for General Availability without having any devices in preview, feel free to utilize the 65 year expiration.

Once AOSP DM is generally available and I have a device I want to setup for the first time, will I need to use the QR code option in the enrollment profile? Or do I need to create another enrollment profile?

No, the QR code you can generate when creating an AOSP DM enrollment profile in Intune is not applicable for Teams Android Devices and will not be available for use if the "Teams Device" toggle is selected when creating the enrollment profile. And no, for brand new devices signing in for the first time after AOSP DM is generally available, they will enroll using the existing enrollment profile you've created in the migration documentation.

What AOSP policies are supported for Teams Devices?

There's currently a limited set of supported compliance policies for Teams Android Devices enrolled with AOSP Management but more are planned for in future releases:

Device Health Rooted devices (Block).
Device Properties Minimum OS version.
Device Properties Maximum OS version.
System Security Require encryption of data storage on device.

I am a new customer to Teams Devices and want to skip Android Device Administrator, can I enroll my devices using AOSP DM now?

First, thank you for purchasing Teams Devices! But to ensure stability, supportability, and a positive customer experience, we've limited AOSP DM to a subset of preview customers with existing Teams Devices. We ask all new customers to please use Android Device Administrator until AOSP DM is generally available.

Why not use Android Enterprise?

Android Enterprise specifically requires Google Mobile Services, and since Teams Devices do not contain Google Mobile Services, AOSP Device Management is our solution.

Why is my device is signing out on migration?

Please ensure the following:

Ensure a AOSP Device Management enrollment profile is created with a enrollment token extended beyond the current date and the Teams Devices option enabled: https://learn.microsoft.com/en-us/MicrosoftTeams/rooms/android-migration-guide#step-1---set-up-new-aosp-management-enrollment-profiles
If Conditional Access policies are configured requiring device compliance: ensure you have created a AOSP DM compliance policy with supported policies: https://learn.microsoft.com/en-us/MicrosoftTeams/rooms/android-migration-guide#creating-a-aosp-management-compliance-policy

Note: If these devices are signed in with user accounts requiring user interactive multi-factor authentication, they may be prompted to sign back in post migration, this is expected.

Note: Blocking Intune is not recommended in CA policy, and can lead to Intune enrollment issues resulting in sign outs during migration. Adding the "Office 365" resource in your CA policy will work around this by having Teams handle the interactive challenge before attempting Intune enrollment."

Why is sign-in failing using microsoft.com/devicelogin (Device Code Flow (DCF))?

Please see: Policy changes for Microsoft Teams devices using device code flow authentication | Microsoft Community Hub

For sign in for shared space devices with Teams resource accounts (Teams Rooms, Teams Panels, Common Area Phones), this sign in failure is typically caused because user interactive multi-factor authentication (MFA) is being enforced on the account. MFA is not supported for shared space devices: https://learn.microsoft.com/en-us/microsoftteams/rooms/supported-ca-and-compliance-policies?tabs=mtr-a#supported-conditional-access-policies (NOTE: other MFA factors: known network location, compliant device, etc are supported for Teams resource accounts)

For sign in with a personal account, if user interactive MFA is enforced via policy, the web sign in using microsoft.com/devicelogin is not supported. This can be mitigated through the following methods:

With Teams app 1449/1.0.94.2025087003 and later you can leverage the on screen keyboard to use DCF with UPN.
Use filters via conditional access to exclude user-interactive MFA policy from sign in (based on known network location or device type filters).
Sign in locally on the Teams device, the user interactive MFA prompt will appear on the Teams Device, users can interact, complete the MFA prompt and sign in successfully.

How can I use a device enrollment manager (DEM) account to enroll my Teams devices?

DEM accounts are not supported for AOSP Device Management. The account being used for enrollment must be removed from the DEM list. Enroll devices using a device enrollment manager account - Microsoft Intune | Microsoft Learn

Why can't I deploy Trusted Root Certificates on my Teams devices?

Trusted Root Certificate deployment through Intune AOSP is not supported on Teams devices.

Can I migrate my devices to AOSP DM while hotdesking?

Migration while a user is hotdesking is not a supported scenario and the migration will fail.

What about my GCC-H devices?

GCC-H devices will have a different migration plan than the details and timelines posted above. We will share more information for GCC-H in August.

Who do I contact if I need more support or information?

Please reach out to your Microsoft account representatives or open a support case for more details.

BEST PRACTICES (Conditional Access policies/rules)

Policies/Rules	Recommendation	Outcomes if recommendation not followed
CA Policy - with device compliance requirement	Ensure enrollment profile is created in Intune.	Devices may sign-out during migration. Further sign-ins will also be blocked with error: AADSTS50002: "deivce is required to be compliant" in AAD signin non-interactive logs.
CA Policy - Multi-factor Authentication (MFA)	Not supported at all for shared devices For personal devices: not supported with DCF for Teams app version 1449/1.0.94.2025084203 (and earlier) You may use per-user MFA to unblock DCF sign-in temporarily on but this is deprecated in September 2025 For personal devices (Teams Phones, Teams Displays: Supported for DCF with on screen keyboard for Teams app version 1449/1.0.94.2025087003 (and later)	DCF sign-in will fail with AADSTS50076/50079: "use/enroll multi-factor authentication" error code.
CA Policy - with App Protection Policies	Not supported	Sign-in will fail with AADSTS53009/53005 error code.
CA Policy - exclude devices	Location filters or Device filters can be used to exclude devices from unsupported policies. Displayname is the recommended Device filter to use (manufacturer and model also work).	If not excluded from unsupported policies, devices may sign-out.
CA Policy - Terms of Use (ToU)	Not supported for shared devices Not supported with DCF for Teams app version 1449/1.0.94.2025084203 (and earlier) Supported for DCF with on screen keyboard for Teams app version 1449/1.0.94.2025087003 (and later)	DCF sign-in will fail with AADSTS50158 error code.
CA Policy - Sign-in Frequency	Not supported for shared devices Sign-in Frequency for "1 hour" and "Every time" should not be used for Teams Devices undergoing AOSP migration	Requires reauthentication if configured (AADSTS70045), including causing sign-outs during migration.
Firewall rules	Teams and Intune URLs need to be allowed in firewalls Allow Teams traffic, Office 365 endpoints Allow Intune traffic, Intune endpoints	Devices may sign-out during migration and further sign-in may fail with error code: 20018 or discovery on login screen UI.
Dynamic Device Groups	Do not use Dynamic Device Groups that require attributes that are populated by Intune (e.g. device.deviceManufacturer -eq "Cisco").	Leads to replication delay on the Manufacturer and Model number attributes which can cause sign-in delays or require multiple sign in attempts.

New Diagnostic: Microsoft Teams Room Diagnostic now available in MRCA

Carlos Farrica — Tue, 27 Feb 2024 14:30:57 GMT

Hi Teams Community,

We're back with another addition to Support Diagnostics for Microsoft Teams. Christopher Tart and a Team of Subject Matter Experts has written another test for Teams Devices in the Microsoft Remote Connectivity Analyzer.

This new diagnostic will help you troubleshoot and test if you meet requirements for a Microsoft Teams user to be able to sign into a

- Microsoft Teams Room Android

- Microsoft Teams Room Windows

- Microsoft Teams Panel

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Microsoft Teams Room Sign in”.

For more advanced tests, you can login with Global Administrator account and then specify the end user.

Use the "Device Selection" to choose which device type you would like to test the account with.

This new Diagnostic is a comprehensive check of all things Microsoft Teams Room or Panel need to successfully sign in.

At a high level the test checks a few things:

Validates that a user can sign into a Microsoft Teams Room. 
Validates that conditional access is enabled. 
Validates the Intune device compliance policies. 
Validates that the device is properly registered. 
Validates the user sign-in events in Microsoft Teams Room.

We welcome your comments, feedback and questions.

Thanks!
Microsoft Teams Support

Cross Cloud Meeting & Cross Cloud Guest Access between WW Teams and 21Vianet Teams

Bill_Yuan — Thu, 23 Nov 2023 21:14:52 GMT

In our previous blog, we introduced the first two Cross-Cloud Collaboration capabilities between Microsoft WW Teams and 21Vianet Teams:

Cross Cloud Interoperability
Cross Cloud Teams anonymous Meeting Join

We hope you found the features useful to facilitate your communication across WW and 21Vianet clouds using Microsoft Teams. As we said in the previous blog, we recently launched the other two features that allow collaboration across WW Teams and 21Vianet Teams:

Cross Cloud Authenticated Meeting (CCM)
Cross Cloud Guest Access (CCGA)

Now, users in different Microsoft clouds can use these features to participate in meetings, chat, call, and share resources with each other. Those features will elevate collaboration by allowing users from different cloud environments to seamlessly join Teams meetings and collaborate, ensuring security through authentication processes. In this blog post, we will describe what these features are, how they function, and how to activate them for your organization.

Cross Cloud Authenticated Meeting

Cross-cloud authenticated meeting join (CCM) delivers the ability for a Teams user to join a meeting hosted in another cloud while signed into their account in their home tenant. This feature provides the meeting host the ability to validate the identities of meeting participants without having to explicitly grant those participants any access to the host tenant.

To use Cross Cloud Meeting, both the meeting organizer and the meeting participants need to have the feature turned on by their admins.

Go to Teams Admin Center (TAC), find Cross-Cloud meetings under Meeting Settings
Add the other tenant IDs and configure the Inbound/Outbound connections to enable and control this functionality for the tenant.

For detailed instructions, please follow this article: Meet with people in other Microsoft 365 cloud environments - Microsoft Teams | Microsoft Learn

When both sides have finished setting up, users can invite and participate in the meeting hosted in the other cloud.

For example, a WW Teams user joining a 21Vianet Teams meeting with fully respecting his home tenant’s authentication.

Cross Cloud Guest Access

Teams Cross Cloud Guest Access (CCGA) extends existing Guest Access functionality allowing a user to participate in rich collaboration experiences in teams, channels, documents and Teams meetings between tenants across Microsoft clouds. Guests are able to participate in a full collaboration experience including audio/video, screen share, Channel file share and both 1:1 and 1: many chats. These features are enabled through the Microsoft Entra ID B2B feature and the newly released Cross Tenant Access Settings, which can enable trust between tenants and between Microsoft clouds.

Just like the Cross Cloud Authenticated Meeting configuration, to enable the Cross Cloud Guest Access capability between WW Teams and 21Vianet Teams, both the tenants in the two different clouds must have the feature turned on by their tenant admins. Below are the highlight steps:

Enable Guest Access
Configure the Cross-tenant connections with another Microsoft cloud
Add the other organizations and configure the inbound/outbound settings

See detailed instructions on this article: Collaborate with guests from other Microsoft 365 cloud environments | Microsoft Learn

It is like the Guest Access feature in the Cloud.

The host team can then add the guest user by using their email address.

The guest user will receive an email invitation with a link to join the team or channel resource. They can join the team or channel by clicking on the link, or by using the Teams app in the other cloud.

The guest user will have a separate identity and profile in the other cloud, and they can switch between their home cloud and the guest cloud in the Teams app.

In conclusion, Cross Cloud Meeting and Cross Cloud Guest Access are two new features that further improve the cross-cloud collaboration between WW Teams and 21Vianet Teams. These features enable users in different clouds to participate in meetings, chat, call, and use shared resources with each other.

Give it a try!

New Diagnostic: Teams Federation and Interoperability Diagnostic now available in MRCA

Carlos Farrica — Thu, 09 Nov 2023 19:10:00 GMT

Hi Teams Community,

We're back with another addition to Support Diagnostics for Microsoft Teams. This time @Chunlong Li has written our Teams Federation and Interoperability Diagnostic in the Microsoft Remote Connectivity Analyzer.

This new diagnostic will help you troubleshoot and test if you meet requirements for a Microsoft Teams user account within your organization can search and engage in a chat with an external account.

Some common symptoms:

A Teams user tries to search for an external user from the Teams powerbar but there are no external contacts popping up.
A Teams user could find the target external user from the Teams powerbar but experiences the error ‘We can't set up the conversation because your organization are not set up to talk to each other’ when trying to chat with that user.
A Teams user tries to send a message to an external Skype for Business user, the following error pops up in the Teams client: ‘We ran into a Problem sending your message. Please share diagnostic code <error code> with your admin to help them troubleshoot the issue’.

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Teams Federation and Interoperability”.

After logged in with and Administrator account you should specify the SIP address of the internal Teams user and the SIP address of the external target.

And then specify the client that the external user is using

At a high level the test checks a couple of things:

Validates if external access policy is not correctly set.
Validates if the SIP address is correct.
Validates the federation with SFB on premise .

We welcome your comments, feedback and questions.

Thanks!
Microsoft Teams Support

New Diagnostic: (Updated) Teams Android Desk Phone Diagnostic now available in MRCA

Carlos Farrica — Tue, 27 Feb 2024 13:12:59 GMT

Hi Teams Community,

We're back with another addition to Support Diagnostics for Microsoft Teams. This time Christopher Tart has written our first test for Teams Devices in the Microsoft Remote Connectivity Analyzer.

This new diagnostic will help you troubleshoot and test if you meet requirements for a Microsoft Teams user to be able to sign into a Teams Android Desk Phone.

To access the new customer facing diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the “Teams Android Desk Phone Sign in”.

For more advanced tests, you can login with Global Administrator account and then specify the end user.

This new Diagnostic is a comprehensive check of all things Teams Android Desk Phone need to successfully sign in.

At a high level the test checks a couple of things:

Validates that a user can sign into a Teams Android Desk Phone. 
Validates that conditional access is enabled. 
Validates the Intune device compliance policies. 
Validates that the device is properly registered. 
Validates the user sign-in events in Teams Android Desk Phone.

Feb 2024 - Diagnostic was updated to validate Device configuration settings.

We welcome your comments, feedback and questions.

Thanks!
Microsoft Teams Support

Rolling Out Changes to Caller ID Policies

Rebecca Valdivia — Thu, 09 Nov 2023 06:18:24 GMT

In January of 2023, Microsoft announced that we will stop supporting the use of Service calling line ID substitution in Caller ID policies in the Teams admin center and in the New-CsCallingLineIdentity cmdlet in the Teams PowerShell Module and we are instead asking customers to use the Resource calling line ID substitution. In this first phase, announced by MC505122 (now archived), we removed the ability to create new Caller ID policies with Service calling line ID substitution.

In April of 2023, Microsoft announced the second phase of the retirement via MC545913 (requires Admin sign-in to view) indicating that we will stop honoring Caller ID policies using Service calling line ID substitution.

We have started to rollout the second phase of this retirement which should be complete by end of October.

When this change has been implemented, Caller ID policies using Service calling line ID substitution will no longer be honored and the outbound call will not have any caller ID substitution. We will still honor other settings on a Caller ID policy using Service calling line ID substitution. We will also remove using Service calling line ID substitution from the Teams admin center and in the New/Set-CsCallingLineIdentity cmdlet in the Teams PowerShell Module.

Tenant administrators will need to use the Resource calling line ID substitution. This type of substitution uses the phone number of a resource account associated to an Auto Attendant or Call Queue and it supports both Calling Plan, Direct Routing and Operator Connect phone numbers.

You should change any existing caller ID policies using Service calling line ID substitution to using Resource calling line ID substitution.

For more information, please review the following resources:

Update! Microsoft Teams Rooms Licensing Policy Enforcement

Carlos Farrica — Fri, 22 Sep 2023 12:55:05 GMT

Back in July 1, 2023, we have released the information about the new Teams Rooms SKUs informing that all Teams Rooms devices, including Microsoft Surface Hubs and Microsoft Teams Panels, using a user license (i.e., A, E, G) will receive an error message and the device will fail to sign-in to the applicable service after the 90-day grace period expires on September 30, 2023.

IMPORTANT! There are less than 10 days remaining before the Microsoft Teams Rooms licensing policy enforcement goes into effect. Please ensure all Microsoft Teams Rooms are properly licensed by September 30, 2023 to prevent any interruption in service.

Microsoft Teams Rooms, including Microsoft Surface Hubs and Microsoft Teams Panels, with a resource account that does NOT have one of the following licenses assigned will fail to sign-in.

Teams Rooms Basic
Teams Rooms Pro
Teams Rooms Standard
Teams Rooms Premium
Teams Shared Device (Team Panels only)

Note: Devices utilizing a resource account without the appropriate licensing will not have the ability to join meetings or access other features of Microsoft Team Rooms or Teams Panels.

Action needed: We recognize that updating licenses can be a time-consuming process for organizations. To help you, we've created a simple step-by-step process for checking small batches of devices, we’ve produced a video on our Microsoft Helps YouTube channel and an automated script for checking licenses in bulk to help update your licenses to Pro or Basic, making the transition as smooth as possible.

More information: Microsoft Teams Rooms licenses

Cortana voice assistance deprecation in Microsoft Teams Rooms and Teams Display solutions

JohnSteckroth — Wed, 20 Sep 2023 16:05:05 GMT

While the Microsoft Teams product team is rapidly releasing new features and capabilities for Microsoft Teams Rooms and Teams Display devices, there is a deprecation we want to make customers and partners aware of – the end of support for Cortana voice assistance integration. While we continue innovating to deliver more intelligent, inclusive, and productive meeting experiences, we must end support for some legacy technologies.

Deprecation details for Cortana in Microsoft Teams Rooms

With the end of support for Microsoft Cortana for Windows and Teams announcement, we must make some changes to Teams Rooms on Windows and Teams Displays, specifically the Lenovo ThinkSmart View, that will impact customers using Cortana voice assistance. On September 15, 2023, we initiated the process to begin deprecation, and will no longer support Cortana voice assistance, both push-to-talk capability and wake word detection, on any Teams Rooms devices or Teams Displays over the course of the coming weeks. Users will no longer be able to invoke Cortana via the push-to-talk button or use the keyword ("Cortana") when this change is implemented.

We realize this change may affect some of the ways you work on Teams devices. We are delivering exciting new AI features to help customers work faster and smarter and are dedicated to helping customers who have adopted Microsoft voice assistance technologies make a smooth transition. Users who leveraged Cortana voice assistance to complete tasks such as joining, starting, or ending a meeting, adding a name or number, and calling can complete these tasks manually via the console or touch screen interface. Rooms equipped with Certified for Teams intelligent speakers can continue to use the device for meeting audio and intelligent voice attributed transcription. For additional information, click here.

Upcoming Certificate Changes Impacting Direct Routing Users

Rebecca Valdivia — Thu, 09 Nov 2023 06:18:46 GMT

On September 5, 2023, Microsoft performed a test where all Microsoft Session Initiation Protocol (SIP) endpoints were switched over to use the new certificate requirements previously announced. The change requirement and test were communicated to Direct Routing customers through Message Center posts as well as Service Health Incidents in the Microsoft Admin Portal (MC540239, TM614271, MC663640 and TM674073). In addition, Microsoft announced the planned test and upcoming changes in: What's New Direct Routing - Microsoft Teams | Microsoft Learn , and posts were made on LinkedIn and in other techcommunity articles such as: TLS certificate changes to Microsoft 365 services including Microsoft Teams - Microsoft Community Hub.

Despite the aforementioned measures, on September 5th, several thousand customers experienced call failures, leading to the premature suspension of the test. Since the prior test was suspended early, on September 19th (starting 9 AM UTC) Microsoft will perform an additional 24h test where all Microsoft SIP endpoints will be switched over to use the new certificates.

If your Session Border Controllers (SBCs) are not properly configured with the new Certificate Authority (CA) your Direct Routing incoming and outgoing calls will fail.

Action needed: Check your SBC(s) or check with your Direct Routing provider to confirm they have added the relevant certificates to your SBC(s) and tested your SBC(s). The New CA must be added in your SBC configuration and old Baltimore CA must be retained; do not replace the old CA.

New Transport Layer Security (TLS) certificates used by Microsoft SIP interfaces will use a different Root Certificate Authority (CA):

Common Name of the CA: DigiCert Global Root G2 Thumbprint (SHA1): df3c24f9bfd666761b268073fe06d1cc8d4f82a4

The new CA certificate can be downloaded directly from DigiCert titled: DigiCert Global Root G2

Following the test scheduled for September 19th, Microsoft will enforce the CA change requirement starting on October 3, 2023.

More information: What's New Direct Routing - Microsoft Teams | Microsoft Learn