What it does

Teams phones, Teams Rooms on Android, Teams panels and SIP devices are managed from the Teams Rooms Pro Management Portal, not the Teams devices pages in the Teams admin center. Inventory, firmware and app updates, configuration (now "settings templates"), remote actions and health monitoring moved across during 2026, with the remaining Teams admin center workflows retiring in October 2026.

Key facts

• In scope: Teams Rooms on Android, Teams phones, Teams panels and SIP devices. Teams displays aren't migrating — they're end of support.
• Timeline: Android capabilities appeared in the portal from end of June 2026; phased deprecation of the Teams admin center workflows ran through September 2026; remaining workflows retire in October 2026. Government clouds follow later (GCC and DoD around October 2026).
• Portal access needs at least one Teams Rooms (Pro, Basic or Standard) or Teams Shared Device licence in the tenant, or a Teams phone already enrolled. No new licence is required for the move.
• Roles: Global Administrator, Teams Administrator, Teams Device Administrator or Global Reader in Entra, or portal roles (Teams Rooms Pro Manager, Site Lead, Site Technician, custom). Administrative-unit-scoped admins can't access the portal.
• Devices need Admin Agent AA 830 or later to be manageable, and AA 856 before Teams admin center deprecation. Microsoft force-deploys the minimum agent version; it can't be paused.
• Devices on AA 794 or later catch up through Zero-Day Update when they come online; older devices need a manual firmware update from the OEM first. Devices signed out for a long time must sign in once after updating.
• Teams admin center configuration profiles import into the portal as settings templates. Tags import as Groups (Settings > Groups > Import from Teams admin center) — but groups attach to devices, whereas tags followed the signed-in account.
• Updates move from phase-based to update rings. Maintenance window is fixed at 12 AM–5 AM device local time; custom windows aren't available yet. Paused or disabled updates stay that way after migration.
• Remote actions in the portal: restart, sign-in/out, remove/unenrol, collect logs; bulk actions and MAC-address provisioning are rolling in.
• Intune enrolment for Teams Android devices uses AOSP Device Management, replacing Device Administrator. One AOSP enrolment profile per tenant can have "For Microsoft Teams devices" enabled.
• Teams Rooms Basic doesn't include Intune, so Basic-licensed Android rooms won't enrol in Intune unless you license it separately.

When to use / skip

There's no opting out — if the client has Teams phones, panels or Android rooms, this is now their management console. The work is getting them ready: right roles, current agent firmware, network allowlisting, and a deliberate decision about update rings rather than accepting the defaults by accident.

If the client used Intune compliance in Conditional Access for these devices, the AOSP move is the bigger risk. Create the AOSP compliance policy before devices migrate, or they'll sign out and stay signed out until someone fixes it.

Configuration decisions

• Who gets portal roles, and whether delegated admins previously relying on administrative units need custom roles instead.
• How to rebuild the Teams admin center tag model as device groups — usually by site or building.
• Update ring design for phones and Android rooms, and whether executive areas get a longer deferment.
• Which configuration profiles to import as settings templates and which to retire.
• Whether to keep Intune enrolment for these devices at all. Removing Intune licences from resource accounts removes the AOSP dependency, at the cost of compliance-based CA.
• The AOSP compliance policy and the dynamic device group (filtering on the AOSP enrolment profile name) it targets.

Gotchas

• Devices sitting in a cupboard on old firmware won't appear. Below AA 794, someone has to update them by hand from the OEM's site.
• Tags that were account-based now become device-based groups. Hot-desk phones and shared accounts may land in groups you didn't expect.
• The fixed overnight maintenance window doesn't suit 24/7 sites like hospitals or control rooms. There's no custom window yet.
• Non-disruptive update settings and maintenance window settings from the Teams admin center aren't migrated.
• An expired AOSP enrolment token blocks sign-in and new enrolments. Use the long default expiry and record it.
• Unsupported Conditional Access policies on resource accounts stop devices connecting to the service. Check against Microsoft's supported CA list.

Consultant notes

• Run an inventory export from the Teams admin center before it goes, so you have a baseline of models, firmware and assigned profiles.
• Chase the lagging devices first — the long-offline ones and those below the minimum agent version.
• Allowlist the Teams devices network security URLs for Android before blaming the portal for missing devices.
• Tell the helpdesk where things moved. Most of the confusion is people still looking in the Teams admin center.
• Note displays end of support in any refresh plan; replace with phones or move users to the desktop client.

---

Recheck once the Teams admin center device pages are fully retired and custom maintenance windows arrive in the portal