MC1227622: Teams Moves Android Device Management from Teams Admin Center to Teams Rooms Pro Management Portal

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
54
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Teams AdminsMicrosoft 365 AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The announcement confirms a delay in rollout for GCC and DoD, with device management moving from Teams admin center to the Pro Management portal and TAC deprecation scheduled by September 2026. Admin impact is high as they must review management workflows, update documentation and adapt to the new portal. User impact is low because changes mainly affect backend device management, not client UX. Urgency is moderate as GA for Public cloud has completed, and TAC deprecation is imminent within two months, requiring timely preparation.
70
🛡️ Admin Impact
15
👥 User Impact
55
Urgency
60
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams Android device management has moved from Teams admin center to Teams Rooms Pro Management portal. TAC deprecation begins soon.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Update internal docs and review migration guidance; PMP is now the primary portal for Teams Android devices.
📅

ROLLOUT TIMELINE

Available:
Now

📢 Official Microsoft Message Center Announcement


(Updated) Transitioning Teams Android Device Management from Teams admin Center to the Teams Rooms Pro Management portal
Message ID: MC1227622 (Updated)

Updated August 5, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP).

This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale.

This message is associated with Roadmap ID 555235.

[When this will happen:]

  • General Availability (Worldwide): Effective July 2, 2026, the rollout is 100% complete across all regions in the Public cloud.
  • General Availability (GCC High and DoD): We expect to complete the rollout by late August 2026 (previously late-July).
  • General Availability (GCC): We expect to complete the rollout by late-August 2026.
  • Device management deprecation in TAC: We will start the deprecation for Public cloud customers in August and expect to complete by end of September 2026 in all the clouds.

[How this affects your organization:]

Who is affected:

Admins who manage Teams Rooms on Android, Teams phones, Teams panels, and SIP Phones.

What will happen:

  • By end of June 2026, Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels and SIP Phones.
  • The following capabilities will be available and enhanced in PMP:
    • Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information
    • Remote device actions (restart, log collection, sign-in/out, provisioning, and more)
    • Update management
    • Device settings management
    • Device health monitoring
    • SIP device management
  • PMP will become the primary portal for all Teams device management. By September 2026, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will be deprecated in TAC.
  • The article below serves as the main information source for this transition. It has been updated with the latest timelines, milestones, migration guidance, and readiness steps. We will keep updating it as the rollout progresses.

[What you need to do to prepare:]

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1227622] Archive
Tooltip: View earlier revisions of this post

Share This Update