In mid-2026, Microsoft began phasing out Android device management from the Teams Admin Center (TAC) and moving it into the Teams Rooms Pro Management Portal (PMP). Starting in August, TAC workflows for Teams Rooms on Android, Teams phones, panels, and SIP devices will redirect to PMP. By September, any remaining overlapping TAC device-management functions will be retired. For IT teams, the crucial work isn’t the migration itself—it’s proving, right now, that every Android endpoint is ready to be managed in the new portal before those redirects become the default.

What’s Actually Changing

The shift, tracked under Microsoft Roadmap ID 555235, affects four device categories: Teams Rooms on Android, Teams phones, Teams panels, and SIP devices. (Teams Displays are excluded and will reach end of support separately.) These devices will no longer appear in the TAC device inventory and will lose access to TAC-based remote actions, configuration profiles, and update controls. All management moves to PMP, accessible at https://portal.rooms.microsoft.com (or the GCC High/DoD equivalents).

Microsoft’s timeline breaks down into four phases:

  • Until May 2026: Preparation and early guidance only.
  • End of June 2026: Transition begins. Android device management capabilities start appearing in PMP, and some TAC workflows begin redirecting.
  • July–August 2026: Full management workflows are available in PMP (July). TAC redirects increase through August.
  • September 2026: Remaining TAC device-management functions are decommissioned. PMP becomes the single management portal.

The good news: Microsoft promises that existing TAC-enrolled devices will appear automatically in PMP—there is no manual migration to perform. However, that automatic appearance depends on two prerequisites: devices must be updated to Admin Agent version AA 830 (specifically, 1.0.0.202606082157.product) and must be able to reach the requisite Microsoft network endpoints. If either condition is unmet, a device may stay invisible in PMP and, once TAC redirects take effect, become effectively unmanageable.

Licensing requirements for PMP access are flexible: any organization with at least one Teams Rooms Pro, Basic, or Standard license qualifies, as does any tenant with a Teams Shared Space license. Even if you have no such license, if you already manage at least one Teams phone in TAC, that device’s auto-enrollment into PMP provisions the tenant for access. For organizations new to PMP entirely, simply signing into one Teams phone triggers automatic enrollment—provided the phone meets the AA 830 requirement.

Who’s Affected and What It Means

For IT admins managing Teams devices: This is not a passive migration. Even though devices are meant to appear automatically, the transition period exposes real risks. If a device doesn’t meet the version requirement or can’t communicate with PMP, it could fall through the cracks. Once TAC management capabilities are turned off in September, recovering such a device might require a firmware update through the OEM’s portal—a far more disruptive process. The August redirects serve as a hard deadline for uncovering these hidden gaps. Admins who rely on automated updates may assume all devices are current, but paused updates, network exceptions, or deliberate baselines can silently leave a device behind.

For end users: The user experience in meeting rooms and on phones shouldn’t change. Teams meetings will still work. But behind the scenes, an admin who can’t restart a room, collect logs, or push a configuration change might leave a problematic device stranded until someone physically intervenes. The impact may be indirect but painful when something goes wrong.

For organizations with restricted networks: The network requirements for PMP management go beyond basic meeting connectivity. A device that can join a call might still be blocked by firewalls, proxies, or allowlists from sending health data or receiving remote commands. If you haven’t already allowed the full list of “Teams Devices - Network Security” URLs, now is the time to audit and update policies. Otherwise, you risk creating a fleet that appears healthy to users but is invisible to administrators.

How We Got Here

The consolidation of Teams device management into a single portal has been a long-term goal for Microsoft. The Teams Rooms Pro Management portal already manages Windows-based Teams Rooms and offers monitoring, automation, and AI-assisted insights. Extending that to Android devices eliminates the operational complexity of juggling two separate admin interfaces and gives IT a consistent view across all shared-space hardware.

Microsoft first signaled this change through its roadmap and message center posts. The general availability of Android device management in PMP, which began rolling out in June 2026, marks the culmination of that plan. For many admins, this means finally being able to use the same portal for all Teams devices—a welcome simplification. But the phased approach also means that, for a few months, administrators will need to straddle both worlds while verifying that the transition worked correctly.

The July Readiness Checklist: What to Do Now

With July 2026 as the first month of full PMP management and August bringing widespread TAC redirects, the window for validation is narrow. The following steps, drawn from Microsoft’s official guidance and practical deployment experience, will ensure you’re ready before those redirects become a daily reality.

1. Confirm You Can Actually Sign In

Before anything else, open the Teams Rooms Pro Management portal and sign in with an account that holds an appropriate role. You’ll need either a suitable Microsoft Entra ID role (Global Administrator, Teams Administrator, Teams Device Administrator, or Global Reader) or a PMP-specific built-in role like Teams Rooms Pro Manager. If your admins are scoped to Administrative Units, verify they aren’t locked out—AUs don’t yet work with PMP, and you may need to create custom roles inside the portal.

2. Reconcile Your Device Inventory

Export or list every Android device you currently manage in TAC: Teams Rooms on Android, phones, panels, and SIP devices. Then compare that list against what appears in PMP’s device inventory. Don’t stop after spotting a few familiar conference rooms—account for every device, including those in branch offices, labs, or shared spaces that might receive less routine attention. A missing device isn’t proof of a manual migration failure; it’s a signal that the device either hasn’t updated to AA 830 or can’t reach the PMP service.

3. Verify Admin Agent AA 830 Everywhere

Check the agent version on every device. Microsoft requires AA 830, version 1.0.0.202606082157.product. If automatic updates are enabled and working, many devices should already be current. But if your organization pauses updates for any device—perhaps to protect a sensitive meeting space or accommodate an OEM firmware hold—those devices may be stranded on an older agent. Once TAC deprecates, updating them may only be possible through an OEM portal firmware flash. Identify and remediate any stragglers now while TAC is still available.

4. Validate Network Routing

Allowlist the full set of “Teams Devices - Network Security” URLs on your firewalls, proxies, and filtering appliances. Test from representative devices to confirm that management traffic flows unimpeded. A device that appears healthy because it can join a meeting may still be blocking the outbound connections PMP requires for health reporting, remote command delivery, and configuration sync. Address any gaps before redirects leave you with management-blind devices.

5. Test Remote Actions on Live Devices

Seeing a device tile in PMP proves enrollment, but not operational readiness. Pick one or more devices from each category (room, phone, panel, SIP) and:

  • Send a remote restart. Confirm it completes and the device returns to a manageable state.
  • Perform a sign-out and sign-in, if safe, and verify the portal reflects the change without getting stuck in a pending state.
  • Request log collection. Download the logs and ensure they’re accessible to the staff who will need them during future troubleshooting.

Do these tests during a maintenance window. If any action fails, investigate immediately—problems here likely point to agent or network issues that will block production management later.

6. Inspect Health Signals

PMP should be receiving current health signals from all Android devices. In the portal, check that you see active, fresh data for temperature, connectivity, peripheral status, or whatever metrics apply to each device type. A stale or blank health view often masks the same network or agent problems that will prevent remote administration.

7. Import Configuration Profiles as Settings Templates

TAC configuration profiles won’t automatically carry over. Microsoft allows you to import them into PMP as Settings Templates. Identify the profiles that matter—those controlling meeting room behavior, phone hotline settings, or panel customizations—and import them now. After importing, associate the templates with the correct devices and validate that the target hardware receives the intended settings. Don’t assume import equals equivalence; test a few devices thoroughly. This is also a good time to retire obsolete profiles rather than copy over years of configuration history.

8. Review Update Controls

Update behavior doesn’t map 1:1 from TAC to PMP. Devices that had updates paused in TAC will remain paused in PMP, but the update rings differ. During the transition period (now through September 30, 2026), auto-updates via PMP will follow the old TAC cadence until you explicitly adopt PMP’s rings. For phones that are not yet on AA 830, they will be placed in a default “General” ring regardless of their previous TAC phase. Once you’ve brought all devices up to the minimum agent version, plan a deliberate transition to PMP update rings and the new nightly maintenance window (midnight to 5 AM device local time).

What to Watch Next

After September 2026, the ecosystem will settle. PMP will be the undisputed control plane for all Teams devices, and Microsoft will likely continue enhancing its capabilities—expect more AI-assisted insights, deeper integration with incident management, and perhaps tighter links with the larger Microsoft 365 admin experience. In the short term, keep an eye on the Message Center and the continuously updated Microsoft Learn article for any timeline shifts or feature-specific updates. The most important metric right now is simple: by the time August arrives, your team should already be treating PMP as the working console, with TAC as a fallback. If the first TAC redirect is the moment you discover a problem, the transition will feel less like an automatic upgrade and more like a preventable outage.