Microsoft is moving all Android-based Teams device management out of the Teams Admin Center (TAC) and into the Teams Rooms Pro Management portal (PMP). The phased transition starts at the end of June 2026, but the real pressure point arrives in August, when TAC workflows will increasingly redirect to PMP. By September, the old management path retires. For admins, the gatekeeper is Admin Agent version AA 830—devices that don’t have it by the deadline risk becoming unmanageable until they’re updated through OEM tools.

This isn’t a passive portal switch. It demands inventory auditing, role testing, and documentation rewrites. The good news: eligible devices that meet the minimum agent version appear automatically in PMP. The catch: automatic appearance doesn’t guarantee every device is present, reachable, or accessible to the right support staff.

A Staggered Rollout Designed to Give You Time—But Not a Lot

Microsoft’s timeline spans four phases, but the busy months are July and August 2026. Here’s what the company has detailed so far:

  • Through May 2026: Preparation and early guidance. Admin onboarding docs become available, and Microsoft continues rolling out Android-specific features into PMP.
  • End of June 2026: Transition begins. Android device management capabilities start appearing in PMP. Select TAC workflows begin redirecting.
  • July–August 2026: The crunch period. Full management workflows are supposed to be live in PMP by July. In August, TAC redirects become more aggressive, steering admins to PMP for more and more tasks.
  • September 2026: Decommissioning. Remaining overlapping TAC device-management features are retired. PMP becomes the primary portal.

Microsoft warns that these dates could shift as development progresses. Administrators should monitor the main transition article on Microsoft Learn (linked at the end) and Message Center posts for refined milestones.

What the Transition Covers

Four device categories are affected:

  • Teams Rooms on Android (MTR-A)
  • Teams phones
  • Teams panels
  • SIP devices

Teams Displays are excluded—they’re being deprecated and won’t migrate. The capabilities moving to PMP include device inventory, remote actions (restart, log collection, sign-in/sign-out), update management, settings and configuration profiles, health monitoring, incident management, and MAC address-based provisioning. For SIP devices, view and remote actions migrate, with provisioning following in mid-July 2026.

Critically, existing configuration profiles from TAC can be imported as settings templates in PMP, and tags can become groups (once that feature is available). Update behavior will also change: auto-update rings in PMP differ from TAC phases, but during the transition period (through September 30, 2026), devices follow their existing TAC cadence unless admins explicitly adopt PMP rings.

Why AA 830 Is the Dealbreaker

The single most important prerequisite is Admin Agent version AA 830, specifically the build 1.0.0.202606082157.product. Without it, an Android device won’t be manageable in PMP—even if it appears in the device list. Microsoft will accelerate deployment of the minimum agent to devices that have auto-update enabled, but organizations that have paused or disabled auto-update must manually intervene.

After TAC device management is deprecated, updating a device below AA 830 will require going through the OEM portal to install firmware that includes the required agent. That’s a much messier process than updating now via TAC or your existing Mobile Device Management (MDM) flow.

A device showing up in PMP is not proof of readiness. The portal relies on that agent for communication. Admins need independent verification—checking the reported version in PMP or via the device itself—before marking a device as ready.

What This Means for Your Day-to-Day Operations

If your organization manages Teams Android devices, the next few months are about more than just checking a version number. The shift to PMP changes where technicians go to do their jobs. Bookmarks, screenshots, and incident templates that reference TAC will break or mislead staff. The portal itself enforces role-based access control (RBAC) differently, and scoping through Microsoft Entra Administrative Units can block access unless a custom PMP role is created by a Global Administrator or Teams Administrator.

Here’s where early testing pays off. Many organizations discover that a Global Admin account can see and do everything, but the regional technician or outsourced support team—the people who actually triage issues—can’t. Before August’s redirects kick in, sign into PMP with each production role and verify that they can view the right devices, access the information needed for first response, and perform their specific tasks. Map this by device class (room, phone, panel, SIP) and document both expected and observed behavior.

For SIP devices, the AA 830 requirement doesn’t necessarily apply—but that doesn’t mean you skip them. Include SIP devices in inventory reconciliation, access testing, and validation of remote actions.

A Practical Preparation Roadmap

Based on the transition guidance and early adopter experience, here’s a high-level readiness sequence that avoids last-minute panic:

  1. Inventory everything in scope. List every Teams Room on Android, phone, panel, and SIP device. Capture asset ID, location, business owner, support group, and whether auto-update is enabled.
  2. Check Admin Agent versions. For Android devices, record the current Admin Agent build. If it’s below AA 830, flag it immediately. Determine whether auto-update will bring it current or if manual action is needed.
  3. Validate the inventory inside PMP. Once your devices begin appearing automatically (after they meet the agent requirement), compare PMP’s list with your authoritative inventory and the current TAC view. Look for missing, duplicated, stale, offline, or orphaned records.
  4. Test with real roles, not just Global Admin. For each support team, log in with a production account and verify that they can see their assigned devices, review necessary information, and execute their standard tasks. If scoped only via Administrative Units, work with a Global Admin to create suitable custom PMP roles.
  5. Update support documentation. Replace all internal references to TAC with PMP workflows. This includes help desk scripts, escalation paths, role-elevation instructions, and any training materials.
  6. Build an exception list. Track every device that fails any readiness check—missing, offline, outdated, inaccessible, or otherwise unresolved. Assign an owner and deadline for each. For Android devices below AA 830, use your validated update procedure; after remediation, re-verify the agent version before moving the device to “ready.”
  7. Run a pilot with diverse devices. Include at least one production room, a business-critical room, a phone, a panel, a SIP device, and a location on a restricted network. Exercise the tasks your teams will perform regularly, not just a quick login check.
  8. Repeat before August. Re-run the inventory reconciliation, agent checks, and role tests before TAC redirects become aggressive. This second pass catches devices that may have fallen behind or newly surfaced issues.

No, You Don’t Have to Manually Enroll Every Device

Microsoft has confirmed that eligible devices appear in PMP automatically. You don’t need to re-register them one by one. But automatic enrollment is not the same as operational readiness. A device may appear yet be unmanageable because of a missing agent, or visible but not accessible to the technician who needs it. Treat the automatic list as a starting point, not a final validation.

The Risk of Waiting

As of September 2026, the overlapping device management capabilities in TAC will be gone. If you haven’t completed the readiness steps, you’ll lose the ability to update or manage affected devices through Microsoft’s tools until you recover via OEM channels. Support calls that once followed a familiar TAC path will dead-end at a redirect screen. Technicians who haven’t been trained on PMP will waste precious time. The cost isn’t just an inconvenience—it’s potential disruption to meeting rooms, phones, and panels that business users rely on daily.

Looking Ahead

Microsoft’s consolidation of device management into a single portal is a long-term improvement. PMP offers more advanced monitoring, automation, and AI-assisted management. But the transition period demands deliberate preparation. Keep an eye on the official Microsoft Learn article and Message Center for possible timeline tweaks. The company has signaled that dates may be refined; any changes will still orbit the same June–August sequence. Completed inventory, agent, and access checks will remain valuable regardless.

By acting now—well before the August redirects surge—you’ll ensure that when your colleagues search for a device, restart a room system, or troubleshoot a phone, PMP answers instead of a dead end.