MC1450127 - End-of-support Android devices may not be manageable through the Pro Management Portal

Message Center

Summary

Microsoft is transitioning Teams Android device management from the Teams admin center to the Teams Rooms Pro Management Portal by end of 2026. Supported devices will auto-update to a required Admin Agent version; end-of-support devices may lose manageability. Admins should verify updates and complete the PMP transition steps.

Discussionpowered by zap.ms

Last Updated

Oct 29, 2026

Published Aug 7, 2026

View version history

Service

Microsoft Teams

Tag

Updated message
Admin impact
Retirement

Seen in EDU tenants

We've only seen this message in Education (EDU) tenants. That usually means it's just for education, but it could also come down to licensing, or a rollout that hasn't reached our other tenants yet.

More information

Updated October 29, 2026: We have updated the timeline and content. Thank you for your patience. 

What and Why:

As previously announced in MC1227622, February '26, Microsoft is transitioning management of Teams Android devices from the Teams admin center (TAC) to the Teams Rooms Pro Management Portal (PMP).

To help ensure a smooth transition and reduce administrative effort, Microsoft is automatically updating eligible Teams Android devices to a supported Admin Agent version.

For additional guidance, see the Microsoft Learn article:Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal.

This transition applies to all devices that are currently certified and supported for Microsoft Teams. These devices are listed here:

However, customers may have devices that were previously supported but have now reached end of life. These devices may not be automatically updated to the minimum required Admin Agent version and may not be manageable in the Pro Management Portal.

Rollout Schedule:

  • General Availability (Worldwide): Effective July 2, 2026, the rollout is 100% complete across all regions in the Public cloud. 
  • General Availability (GCC): We expect to start the rollout by Nov 2026 and complete by late-Nov 2026 (previously late-Oct). 
  • General Availability (GCC High and DoD): Effective October 8, 2026, the rollout is 100% complete across GCCH and DoD clouds. 
  • Device management deprecation in TAC: The deprecation of Teams device management capabilities in TAC will begin in November 2026 and will roll out in phases based on device type and feature readiness. 
    • For public clouds - 
      • SIP, MTR-A and Panels devices administration experience in TAC will start deprecating by Mid-November and will complete by end of November. 
      • Phones devices administration experience in TAC will start deprecating by early December and complete by December 15th. 
    • For Gov clouds ( GCC, GCC-H and DoD) 
      • For GCC-H and DoD, device administration experience in TAC will start deprecating by early December and will be completed by December 15th. 
      • For GCC, devices administration experience in TAC will start deprecating by early January and will be completed by January 30th. 
      • Phones devices administration experience for all Sovereign cloud (GCC, GCC-H, DoD) customers will start deprecating by early January and will be completed by January 30th.

Impact on your organization:

Who is affected:

  • Organizations managing Teams Android devices through the Teams admin center.
  • Teams Rooms on Android devices.
  • Teams phones.
  • Teams panels.
  • Other Teams Android-based devices managed through TAC.

What will happen:

  • Microsoft will automatically install the minimum required Teams Admin Agent version on certified and supported Teams Android devices. End-of-support devices may not update automatically and may not be manageable in PMP.
  • Administrators cannot pause or disable automatic Admin Agent updates.
  • Devices may receive Admin Agent updates on a faster cadence than the timing configured throughPMP auto-update rings.
  • The automatic update is intended to prepare devices for management through the Teams Rooms Pro Management Portal.
  • Devices that remain on unsupported Admin Agent versions may lose management functionality after Teams Android device management is retired from TAC at the end of December 2026/January 2027.

Action Required/Recommendations:

Administrators should complete the following actions before the retirement of Teams Android device management in TAC:

  • Verify that Teams Android devices are running a supported Teams Admin Agent version (if available).
  • Ensure devices are visible and manageable in the Teams Rooms Pro Management Portal.
  • Review and complete all steps outlined in thePMP transition guide.
  • Update internal operational documentation and support procedures that reference TAC-based Android device management.

We recommend keeping Teams Android devices up to date with the latest eligible Admin Agent version to ensure uninterrupted device management and a smooth transition to PMP.

Compliance Considerations:

No compliance considerations have been identified. Review this change as appropriate for your organization.

  • No new customer data is stored as part of this change.
  • No changes are being made to customer data processing, storage, or access.
  • No new AI or machine learning capabilities are introduced.
  • No changes are being made to Microsoft Purview, retention, eDiscovery, audit logging, data loss prevention (DLP), sensitivity labels, or compliance reporting capabilities.
  • No third-party integrations are introduced.
  • The change updates the management pathway for Teams Android devices and automatically updates the Teams Admin Agent required for continued device management through the Teams Rooms Pro Management Portal.

Version history

2 versions tracked

Updated 1 time since Oct 22, 2026. Microsoft only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Oct 29, 2026 · 06:49 PMLatest · v2

    Changed: Body, End date

  2. Oct 22, 2026 · 04:33 PMOriginal · v1

    Changed: Initial version