Teams Device Management Moves to PMP: Admin Guide for Dec 15

The biggest risk in this transition is not the new portal itself, it is the devices nobody has looked at in months. Microsoft's own guidance makes three conditions critical.

First, firmware level. Teams phones and other Teams Android devices need Admin Agent version 830 or later to be managed in PMP. Phones below version 830 can only receive Admin Agent updates through TAC, which means they must be updated before TAC management goes away. Devices on Admin Agent 794 or later can pick up the required update automatically once they are powered on and connected, while older devices need an OEM firmware update first.

Second, sign-in state. A device must be signed in to be onboarded into PMP. Phones that have been signed out for a long time, such as spare units in a storeroom or phones at a closed branch, must be signed in at least once.

Third, end-of-life hardware. Microsoft lists device models that have reached end of support and must be updated manually by administrators. SIP phones connected through the Teams SIP Gateway receive no app or firmware updates in either portal, so their lifecycle has to be managed separately.

This change also lands in a busy month for Teams administrators. Other November notices include external chat file sharing being switched on by default for tenants that never set the policy (MC1479514) and the Copilot meeting policy splitting into new MeetingAI and TranscriptionWithMeetingAI settings (MC1532253). Each change is small on its own; together they demand a structured review of your Teams tenant rather than a quick click-through.

A successful move to the Pro Management Portal comes down to inventory, firmware, network and permissions. The steps below follow Microsoft's published guidance and readiness recommendations from the Microsoft Tech Community.

1. Export a full device inventory from TAC now. Record model, firmware, Admin Agent version, location and sign-in status for every phone, room system and panel. Include spare and stored devices.
2. Update every Teams phone to Admin Agent 830 or later. Prioritize devices below version 794, which need OEM firmware first. Do this while TAC still manages phones, before December 15.
3. Sign in idle devices. Power on and sign in phones that have been offline or signed out for a long time so PMP can onboard them.
4. Validate network access. Make sure devices can reach Microsoft's published Teams device endpoints. Test WebSocket traffic, not only HTTPS, and check that proxies, TLS inspection and NAT capacity do not interfere. Teams Rooms devices have limited support for authenticating proxies.
5. Confirm portal roles. Make sure the right administrators, such as Teams administrators and Teams device administrators, can access PMP, and define role-based access for local site technicians if you need it.
6. Plan update rings before confirming them. In PMP, confirming the ring configuration is irreversible. By default all phones map to the General ring, PMP rings roll out updates faster than TAC phases did, and automatic updates run in a nightly window from 12 AM to 5 AM device local time. A tenant-wide pause lasts two weeks before updates resume automatically.

A resilient multi-operator connectivity and SD-WAN design helps with step 4, because consistent firewall and proxy policies across sites mean a device that works in one office will also work in every other.

Handled well, the move to PMP is an opportunity to clean up and standardize your entire Teams device estate. The benefits go beyond simply staying supported.

• One place to manage rooms and phones. Meeting rooms, panels and phones are managed in a single portal, so support teams no longer switch between consoles to troubleshoot a site.
• Faster, more controlled updates. Update rings let you test new firmware on a small group before it reaches executives or contact center agents, reducing the risk of a bad release disrupting calls.
• An accurate asset register. The inventory exercise exposes phones that are unused, end-of-life or assigned to people who have left, which can lower licensing and hardware costs.
• Better call quality. Validating network paths for device management often uncovers proxy and firewall issues that also affect voice and video. Fixing them improves the reliability of voice traffic and SIP trunking across every location.
• Audit-ready change control. A documented transition plan, with firmware levels and ring assignments, gives auditors and management clear evidence of how communication devices are maintained.

A practical checklist for this month: export your TAC inventory, update phones to Admin Agent 830 or later, sign in idle devices, confirm network endpoints and WebSocket access, assign PMP roles and design your update rings before confirming them. Organizations with limited internal resources can rely on IT managed services to run the inventory and updates without pulling engineers away from other projects.

HIT Communications has more than 30 years of experience delivering enterprise voice and connectivity across Latin America, the United States and Europe. Device management is only one part of a reliable Teams calling experience, and we cover the full stack.

Our Microsoft Teams Direct Routing and UCaaS services connect Teams to the public telephone network with local numbers in multiple countries, and our team can manage your Teams phones, room systems and update rings as part of the service. Our voice traffic and SIP trunking offering provides carrier-grade routes for high call volumes, while our multi-operator connectivity design keeps devices and users connected with redundant, policy-consistent networks at every site.

We work with CIOs, IT managers and telephony teams who want one accountable partner instead of several vendors. If you are not sure how many of your phones are below Admin Agent 830, or which devices are offline, that is the right place to start.

The Teams device management transition is a deadline, not just a portal change. SIP devices, Teams Rooms on Android and panels leave the Teams admin center by the end of November 2026, and Teams phones follow by December 15, 2026. Devices that are outdated, offline or signed out are the ones most likely to become unmanageable.

Start with an inventory, update firmware while TAC can still reach your phones, validate network access and plan your PMP update rings carefully. If you would like help reviewing your Teams device estate or managing the transition end to end, contact the HIT Communications team and we will build a plan with you.