This blog post is about the required transition of Teams Android devices to the Android Open Source Project (AOSP) Device Management in Microsoft Intune. This is a new mobile device enrollment method which requires some actions to be completed to keep your Teams Android devices up and running. The current method is the Android Device Administrator for Teams Devices on Android.

1. Device Management Changes for Microsoft Teams Android Devices
2. What is Android Device Administrator?
3. What is AOSP?
4. What steps do I have to configure at least?
   1. Configure new AOSP management enrollment profiles
   2. Configure AOSP Management Configuration Policies
   3. Configure AOSP Management Compliance Policies
   4. Deploy AOSP Management capable device firmware
5. Extended Token Expiration in Intune AOSP Device Enrollment Profile (October 8, 2024)
6. Updating Teams Phone (Yealink MP56, October 8, 2024)
7. 📫 Update December 10, 2024 📫
8. 📫 Update June 22, 2025 📫

Device Management Changes for Microsoft Teams Android Devices

What is Android Device Administrator?

Android Device Administrator in Microsoft Intune is a legacy method for managing Android devices, allowing IT admins to enforce policies and manage apps on enrolled devices. However, this method is being deprecated, with support ending on December 31, 2024, for devices with access to Google Mobile Services (GMS). Admins are encouraged to transition to Android Enterprise for more advanced and secure management options. In case of Teams Android Devices AOSP is the way to go.

What is AOSP?

Android Open Source Project (AOSP) Management in Microsoft Intune is designed for managing corporate-owned Android devices that do not use Google Mobile Services (GMS). It allows IT admins to enforce policies and manage apps on these devices, which are often used for specific tasks or shared among multiple users. Transitioning to AOSP Device Management is recommended if you have been using Android Device Administrator, as it provides a more secure and modern management solution.

What steps do I have to configure at least?

To enable AOSP you must enable and configure it in your Microsoft Intune tenant accordingly. The following steps provide an overview:

1. Configure new AOSP management enrollment profiles
2. Configure AOSP Management Configuration & Compliance Policies
3. Deploy AOSP Management capable device firmware

Configure new AOSP management enrollment profiles

• https://intune.microsoft.com/
• Devices
• Enrollment
• Android

• Corporate-owned, user-associated devices

• Create profile

• Save the profile

Configure AOSP Management Configuration Policies

I’m not walk through these steps because currently only the Device Restrictions profile with “block screen capture” is allowed. Furthermore, this is optional.

Configure AOSP Management Compliance Policies

Also, the supported set for device compliance is limited to:

• rooted devices can be blocked
• minimum OS version
• maximum OS version
• System Security Require encryption of data storage on device

Deploy AOSP Management capable device firmware

This step cannot be carried out currently via the Teams Admin Center (TAC) because the AOSP firmware is not yet there but will probably become available during H2 2024.

If the configuration was successful Microsoft says that it should later on show the Microsoft Intune and Authenticator App on the Teams Android device as the following screenshot by Microsoft shows.

To compare it, currently before AOSP it should look like this:

Extended Token Expiration in Intune AOSP Device Enrollment Profile (October 8, 2024)

Microsoft changed the validation period for AOSP Device Enromment Profile tokens. That’s why I deleted the old AOSP profile and created a new one because the old one blocked me from creating a new, second one. The following screenshot shows the expiration date in the year 2089 not just a few days in the future.

Updating Teams Phone (Yealink MP56, October 8, 2024)

Recently I checked my demo device, a Teams Phone, Yealink MP56 via Teams Admin Center. It displayed available updates, so I initiated the updates as the following screenshots show.

📫 Update December 10, 2024 📫

There is now a list available in the faq section showing a list of devices and when each is probably get its firmware upgrade automatically. https://techcommunity.microsoft.com/blog/microsoftteamssupport/moving-teams-android-devices-to-aosp-device-management/4140893

…

What’s also interesting to read is:

Isn’t Device Administrator being deprecated by end of year 2024? What happens if my devices haven’t migrated to AOSP by then?

Although Device Administrator will be deprecated by end of year for devices with GMS, Teams Devices are not GMS devices and therefore will remain supported with Device Administrator for Intune enrollment until AOSP migration is completed as Device Administrator is not being deprecated for non-GMS devices. 

📫 Update June 22, 2025 📫

After my Yealink MP56 was offline for some time, I reconnected it to bring it back online. I noticed that a firmware upgrade had been carried out. After it finished, I could finally see that it was on AOSP by checking the Software Health via TAC.

Update August 3, 2025

🛠️ New Diagnostic Tool for Microsoft Teams AOSP Migration

Microsoft has introduced a new diagnostic tool called AOSP Migration Readiness MRCA Diagnostic to support organizations transitioning their Teams Android devices from Android Device Administrator (ADA) to Android Open Source Project (AOSP) management.

🚀 Why It Matters

• AOSP offers modern, secure, and scalable device management.
• It improves compliance, control, and provides a unified experience across Teams-certified Android devices.

🔍 What the Diagnostic Checks

• Validity of AOSP enrollment profiles
• Intune tenant settings and compliance policies
• Conditional Access configurations (like MFA and Device Code Flow)
• Firmware readiness and device association
• End-of-life status of Teams-certified hardware

👥 Who Should Use It

• IT Admins preparing for large-scale migrations
• Support Engineers troubleshooting device issues
• OEM Partners checking firmware compatibility
• Security Teams reviewing Conditional Access policies

🧭 How to Access It

You’ll need a Global Administrator account. Go to the Microsoft Remote Connectivity Analyzer, select Microsoft Teams, and run the Teams AOSP Migration Readiness diagnostic.

Resources

• Microsoft 365 message center MC665936 Device Management Changes for Microsoft Teams Android Devices
• Migration guide Android AOSP management for Microsoft Teams Android devices – Microsoft Teams | Microsoft Learn
• What’s new in Microsoft Teams Rooms and Devices at Enterprise Connect – Microsoft Community Hub
• Intune ending support for Android device administrator on devices with GMS in December 2024 – Microsoft Community Hub
• Manage Intune devices with Android device administrator | Microsoft Learn
• Decreasing support for Android device administrator – Microsoft Community Hub
• Set up Android (AOSP) device management in Intune for corporate-owned userless devices – Microsoft Intune | Microsoft Learn
• Set up Android (AOSP) device management in Intune for corporate-owned user-associated devices – Microsoft Intune | Microsoft Learn
• Device restriction settings for Android (AOSP) in Microsoft Intune | Microsoft Learn
• AOSP Migration Readiness MRCA Diagnostic