Microsoft is transforming device management with Teams Android AOSP Device Management, replacing the legacy Android Device Administrator model with a more secure, scalable, and modern solution for all organisations.
This change is technical and operational for small and medium-sized businesses in London. It affects how devices are updated, signed in, secured, and managed within Microsoft Intune and the Teams Admin Centre.
With automatic firmware updates rolling out in phases, preparing your environment is essential. If the proper steps are not taken in advance, devices could sign out unexpectedly or fail to meet compliance standards.
Learn how your business can adapt to Teams Android AOSP Device Management, avoid migration pitfalls, and benefit from expert guidance through a professional MSP.
What Is Teams Android AOSP Device Management
Teams Android AOSP Device Management is Microsoft’s new mobile device management method for Teams-certified Android hardware, including phones, panels, and meeting room systems. AOSP Device Management delivers enhanced automation, simplified enrollment, and stronger security features by replacing the older Android Device Administrator framework.
Unlike the older system, AOSP Device Management is tightly integrated with Microsoft Intune and the Teams Admin Centre. It allows administrators to control firmware updates, apply compliance policies, and manage devices without relying on third-party enrollment apps like Company Portal.
This migration affects all supported Teams Android devices. London businesses and small and medium-sized organisations are strongly advised to prepare now to avoid sign-in failures or unsupported configurations.
Key features of AOSP Device Management include:
- Seamless device enrollment into Intune via firmware update
- Support for rooted device detection and OS version enforcement
- Automatic assignment of compliance policies based on Intune configuration
- Teams-only enrolment using a dedicated toggle to block personal Android devices
- Long-term support with future-proofed update mechanisms
AOSP vs. Android Device Administrator: A Quick Comparison
| Feature | Android Device Administrator (Legacy) | AOSP Device Management (New) |
| Enrolment method | Manual enrolment via the Company Portal app | Automatic enrolment through firmware update |
| Device scope | Any Android device with an Intune license | Only Teams-certified Android devices |
| App requirement | Requires Company Portal | No additional app needed (uses built-in Intune agent) |
| Security capabilities | Basic compliance policies | Native encryption, rooted device blocking, OS checks |
| Policy targeting | General Android enrolment | Teams-specific targeting using the “Teams Device” toggle |
| Firmware updates | Manual or semi-automated | Phased and automated via Teams Admin Centre |
| Support lifecycle | Deprecated for many Android versions | Long-term support aligned with Microsoft’s strategy |
| Innovation potential | Limited | Built for future Teams device innovation |
Why Microsoft Is Migrating Teams Devices
Device management changes for microsoft are moving all supported Teams Android hardware to AOSP Device Management to ensure long-term security, manageability, and flexibility. The legacy Android Device Administrator model is outdated and does not support the latest compliance frameworks and Conditional Access rules in Microsoft 365.
Reasons for the migration include:
- Improved security: AOSP supports stronger policies, such as device encryption and rooted device detection
- Simplified enrolment: Devices can enrol directly via firmware without manual app installations
- Targeted control: Only Teams-certified devices are eligible, reducing policy complexity
- Regulatory compliance: AOSP allows for more accurate enforcement of access controls and compliance checks
- Support for future innovation: Microsoft can more easily roll out new Teams features using the AOSP platform
This shift enables IT administrators to maintain tighter control over their device estate while reducing the operational burden of managing Teams hardware.
Key Dates and Auto-Update Phases to Know
The rollout for Microsoft Teams Android devices to AOSP device management occurs in structured phases. With minimal disruption, these firmware updates are designed to transition supported hardware to the new management platform. However, to avoid unexpected sign-outs or service issues, IT teams in London SMBS must understand the update schedule and act in advance.
Firmware rollout phases
Microsoft has split the firmware deployment into three key stages. These will be automatically triggered based on each device’s assigned update phase in the Teams Admin Centre:
- Validation phase (0–15 days)
- The initial release window validates firmware updates on a limited set of devices.
- Suitable for IT teams to test the update process on selected hardware.
- General availability phase (16–45 days)
- The standard update window for most devices.
- Recommended period for broader rollout across meeting rooms and desk phones.
- Final rollout phase (45–60 days)
- Applies to any remaining eligible devices that have not yet been updated.
- At this point, the firmware update will become non-deferrable.
During each phase, the firmware updates will become available and apply automatically unless manual updates are performed earlier. Devices not meeting the AOSP Device Management prerequisites may sign out unexpectedly once the update is installed.
Summary of key OEM firmware availability
To help businesses plan, Microsoft has published the following schedule outlining when firmware becomes available for manual or automatic update by the device manufacturer.
| OEM | Device Type | Firmware Available From | Auto-Update Start |
| AudioCodes | Phones, Rooms, Panels | 15 May 2025 – 15 June 2025 | 15 May 2025 – 15 June 2025 |
| Cisco | Rooms, Panels | 15 May 2025 | 15 May 2025 |
| DTEN | Rooms | 15 May 2025 | 15 May 2025 |
| Jabra | Rooms | 15 May 2025 | 15 May 2025 |
| Logitech | Rooms, Panels | May 2025 | 15 June 2025 |
| Neat | Rooms, Displays | May 2025 | 15 June 2025 |
| Poly | Phones, Rooms, Panels | 31 May 2025 – 15 June 2025 | 31 May 2025 – 15 June 2025 |
| Yealink | Phones, Rooms, Panels | 31 May 2025 – 15 June 2025 | 31 May 2025 – 15 June 2025 |
| Crestron | Panels, Rooms | 31 May 2025 – 15 June 2025 | 31 May 2025 – 15 June 2025 |
Note: Availability and start dates vary by model. Refer to Microsoft’s official Teams Admin Centre or support documentation for exact device listings.
By aligning device updates with the outlined phases and preparing properly for AOSP Device Management, London SMBS can maintain service continuity and reduce risk during this required transition.
Migration Prerequisites for IT Admins
To ensure a seamless transition to AOSP Device Management, IT administrators must take a few preparatory steps before firmware updates begin. Without this preparation, Teams Android devices may sign out unexpectedly or fail to re-enrol correctly in Microsoft Intune. These actions are essential for London SMBS, which relies on Teams hardware for day-to-day communication and collaboration.
Step-by-step: Setting up Intune AOSP enrolment profiles
The first requirement is to create a new AOSP Device Management enrolment profile within Microsoft Intune. This profile allows Teams-certified Android devices to enrol once the firmware update is applied automatically.
To configure an enrolment profile:
- Go to Microsoft Intune Admin Centre
- Navigate to Devices > Android > Android (AOSP) > Enrolment profiles
- Select Create profile and choose AOSP as the platform
- Enable the Teams Devices toggle — this ensures only Teams-certified Android devices can use this profile
- Set an appropriate token expiration date
- Use 90 days for preview or test environments
- Use the full 65-year option for general availability environments
- Name the profile clearly (e.g. “Teams Room AOSP Enrolment – May 2025”) and save
Once the profile is created, Intune generates an enrollment token. This is automatically used during firmware migration—no user input or QR code scanning is required for Teams devices.
Required firmware versions and Intune configuration policies
Alongside the enrolment profile, specific policies should be prepared to ensure devices meet compliance and security standards post-migration.
Key requirements include:
- Firmware version compatibility:
- Confirm that your Teams Android devices are running or will update to the AOSP-capable firmware as outlined in Microsoft’s rollout schedule
- Older firmware versions may not support the new enrolment method
- Compliance policies:
- Go to Devices > Compliance policies > Create policy in Intune
- Choose Android (AOSP) as the platform
- Recommended policy settings include:
- Require device encryption
- Block rooted devices
- Set minimum supported OS version (as per your organisation’s standards)
- Conditional Access alignment:
- Review Conditional Access policies to ensure they do not block AOSP-enrolled devices
- Avoid policies requiring user-interactive MFA on shared Teams devices, as these will fail to sign in
These steps ensure that devices migrate automatically to AOSP Device Management without sign-in failures or compliance issues.
Avoid These Common Pitfalls
While AOSP Device Management offers a more secure and streamlined approach to managing Teams’ Android devices, certain misconfigurations or oversights can lead to unnecessary disruption. Many businesses, particularly SMBS in London, could face issues during migration if specific technical details are overlooked.
Below are the most common issues to avoid and how to resolve them.
Conditional Access policies that block sign-ins
One of the most frequent causes of device sign-out or failed re-enrolment during the migration process is restrictive Conditional Access (CA) policies. These policies may have been appropriate under the legacy Android Device Administrator model, but can unintentionally block AOSP-enrolled devices.
To prevent CA policy conflicts:
- Review all policies that require compliant devices — ensure an AOSP-specific compliance policy has been created
- Exclude Teams Android Devices from policies that AOSP Device Management does not support
- Avoid using filters based on attributes only populated after Intune enrolment (e.g. manufacturer or model), as these can delay access
MFA and unsupported features
Multi-factor authentication (MFA) is a core security feature, but is not supported for shared Teams devices using Device Code Flow (DCF). Enforcing user-interactive MFA through Conditional Access will result in failed sign-in attempts during or after the AOSP migration.
To avoid MFA-related issues:
- Do not enforce user-interactive MFA for Teams Rooms, Panels or Common Area Phones
- If MFA is essential, use alternative controls such as a known location or device compliance
- For personal devices (e.g. assigned phones), ensure the latest Teams app version supports on-device interaction for MFA prompts
Device sign-out issues during migration
If the prerequisites for AOSP Device Management are not completed before firmware is applied, devices may sign out automatically. This is especially disruptive in meeting rooms or shared areas where device availability is critical.
To reduce the risk of sign-outs:
- Create the Intune AOSP enrollment profile before applying any firmware update.
- Apply the relevant compliance policy in advance.
- Ensure security system rules allow Teams and Intune traffic — blocked endpoints can prevent enrollment.
- Check for expired enrolment tokens and replace them with new profiles where necessary.
By proactively addressing these areas, London SMBS can avoid unnecessary downtime, failed enrolments, and compliance errors. Ensuring your environment is fully prepared for AOSP Device Management is essential to a smooth, secure migration.
Managing Devices After Migration
Once your Teams Android devices have successfully migrated to AOSP Device Management, it is essential to understand how ongoing management will differ from the legacy system. While the end-user experience remains unchanged, IT administrators will see new behaviours in Microsoft Intune and the Teams Admin Centre.
London SMBS can more effectively maintain compliance, monitor device health, and manage updates by knowing what to expect post-migration.
New Intune and Teams Admin Centre behaviours
With AOSP Device Management enabled, Teams Android devices will no longer rely on the Company Portal app. Instead, they use built-in system apps to communicate directly with Intune.
Key changes include:
- Two new system apps become visible in the Teams Admin Centre:
- Authenticator
- Microsoft Intune
These apps replace the older Company Portal, handling compliance checks and enrolment in the background.
- Devices remain signed in during and after the firmware upgrade, assuming prerequisites were completed.
- Firmware and management status can now be monitored through the Software Health tab in the Teams Admin Centre.
- Devices are automatically tagged as corporate-owned in Intune, removing the need for manual classification.
Monitoring, compliance, and post-migration policy tips
Managing AOSP-enrolled Teams devices requires a slightly different approach in Intune and Conditional Access configurations.
To ensure smooth post-migration operations:
- Regularly review device compliance in Intune > Devices > Monitor > Compliance status.
- Update AOSP compliance policies as new options become available — Microsoft continues to expand supported controls.
- Monitor firmware versions and enrolment health through the Teams Admin Centre to ensure updates are successfully applied.
- Avoid applying user-interactive security policies to shared Teams devices, such as sign-in frequency or Terms of Use.
- Ensure security system rules allow communication with Teams and Intune endpoints for real-time status updates.
By following these steps, IT teams can confidently manage their device estate under AOSP Device Management, ensuring security and service continuity.
What Happens to Legacy or Unsupported Devices?
Not all Teams Android devices are eligible for AOSP Device Management. Some older models, now classed as end-of-life or no longer supported by Microsoft, will not receive the necessary firmware updates for migration. For London SMBS still using these devices, it is essential to understand the implications and available options.
Devices not eligible for AOSP migration
The following Teams devices have been confirmed as unsupported for AOSP Device Management and will remain on the legacy Android Device Administrator model:
- AudioCodes: C448HD, C450HD, RXV80
- Crestron: UC-2, UC-P8 series, UC-P10 series, UC-P8-TD, UC-P10-TD
- EPOS: Expand Vision 3T, 5T, Control TC, Control Panel
- Lenovo: ThinkSmart View, ThinkSmart View Plus
- Polycom: Trio 8500, Trio 8800
- Yealink: T55/T55A, T56/T56A, T58/T58A, CP960, VP59, MP52, VC210, DeskVision 24
These devices will not be enrolled via AOSP Device Management, and new features will not be available in future updates.
How to keep unsupported devices functioning
Although these devices cannot migrate to AOSP Device Management, they can continue operating in a limited capacity if specific steps are followed.
Recommended steps for continued use:
- Remove the Intune license from the account used to sign in to the device: This prevents the device from attempting to re-enrol and failing under AOSP requirements.
- Manually sign back in using the Teams admin credentials: The device will operate without Intune management but can still connect to Microsoft Teams.
- Accept reduced support and feature availability. These devices will not receive future Teams Room updates or security enhancements.
- Plan for phased replacement: Where possible, begin budgeting and planning to upgrade to Teams-certified hardware compatible with AOSP Device Management.
Following this fallback method allows legacy Teams devices to remain in service temporarily. However, it is strongly advised that SMBS transition away from unsupported hardware to ensure continued security, compliance, and functionality in the Microsoft ecosystem.
Why This Matters to London SMBS
For small and medium-sized businesses in London, staying ahead of technological shifts is vital to remaining secure, compliant, and operationally efficient. The move to AOSP Device Management is more than a technical update—it directly impacts how your Teams device functions and how smoothly your business communicates daily.
Without the proper preparation, businesses risk facing sign-in failures, compliance issues, and unsupported hardware. These problems can lead to downtime, lost productivity, and costly IT interventions.
Why AOSP Device Management is important
AOSP Device Management introduces tangible benefits that support modern workplace needs:
- Improved security: Devices enrolled through AOSP gain access to built-in encryption, rooted device detection, and OS version controls
- Enhanced compliance: Integration with Microsoft Intune ensures only compliant devices can access Microsoft 365 services
- Operational simplicity: Enrolment, updates, and policy enforcement are streamlined, reducing manual admin overhead
- Future readiness: Devices managed through AOSP are aligned with Microsoft’s roadmap for Teams Room innovation and long-term support
How Server Consultancy supports a smooth transition
Managing this migration without the proper technical support can be complex. As a London-based Managed Service Provider (MSP), Server Consultancy offers tailored guidance to help SMBS navigate every step of the AOSP Device Management rollout.
With Server Consultancy, your business benefits from:
- Expert policy setup: We configure your Intune enrolment profiles and compliance policies to meet Microsoft’s exact requirements
- Device audit and readiness checks: Our team reviews your Teams estate and identifies unsupported or at-risk devices
- Controlled rollout planning: We help you test and phase firmware updates to minimise disruption
- Conditional Access alignment: We ensure your security policies are compatible with the AOSP framework
- Post-migration monitoring: Continued support to manage updates, compliance, and device health from day one
With Server Consultancy, your business can avoid common pitfalls and confidently adopt AOSP Device Management without affecting productivity or compliance.
Conclusion
The transition to AOSP Device Management marks a notable change in how Microsoft Teams Android devices are enrolled, managed, and secured. While the process introduces a modern, more secure platform, it also requires careful planning to ensure a smooth migration, particularly for small and medium-sized businesses in London that rely heavily on Teams devices for daily operations.
By preparing ahead of Microsoft’s auto-update schedule, businesses can avoid service disruption, maintain compliance, and stay aligned with the latest Microsoft management practices.
Summary of actions for London SMBS:
- Review your current Teams Android devices and identify models eligible for AOSP Device Management
- Create and configure a dedicated AOSP enrolment profile in Microsoft Intune, enabling the Teams Devices toggle.
- Establish compliant device policies that match your organisation’s security standards.
- Check Conditional Access settings to ensure they do not block enrolment or sign-in for shared devices.
- Monitor firmware availability and apply updates during your preferred rollout phase.
- Create a strategy for phasing out legacy devices not supporting AOSP Device Management.
Final advice to prepare ahead of auto-updates:
- Start early. Firmware updates will become automatic and unskippable, so preparing in advance ensures business continuity.
- Test first. During the validation phase, select a small number of devices for early migration to identify any configuration issues.
- Partner with a trusted MSP. Engaging expert support, such as Server Consultancy, helps simplify the migration process, reduce risk, and free up your internal resources.
With the proper preparation and support, your business can confidently adopt AOSP Device Management, ensuring long-term control, security, and compliance for your Microsoft Teams environment.
What is AOSP Management?
AOSP Management, or AOSP Device Management, refers to Microsoft’s new approach to managing Android devices built on the Android Open Source Project (AOSP). This platform is designed explicitly for Teams-certified Android devices, such as meeting room panels, phones, and collaboration bars, that do not include Google Mobile Services (GMS).
AOSP Device Management replaces the legacy Android Device Administrator model, offering a more modern, secure, and streamlined method of enrolling and managing devices via Microsoft Intune.
Key features of AOSP Management include:
-Intune-based enrolment through firmware updates
-No dependency on the Company Portal app
-Support for corporate-only device enrolment, using a Teams-specific toggle
-Built-in security controls like encryption enforcement and rooted device detection
Better alignment with Conditional Access policies in Microsoft 365 environments
This new model simplifies device management for IT administrators, particularly in environments like shared meeting rooms, where personal logins are not used.
What is an AOSP Device?
An AOSP device is an Android-based device that runs on the Android Open Source Project, and does not include Google Mobile Services like Gmail or the Play Store. These devices are designed for business use, particularly in controlled environments like meeting rooms.
In the context of Microsoft Teams, AOSP devices include:
–Teams Phones
-Teams Displays
-Teams Panels
-Meeting room collaboration bars
These devices are certified to work with Microsoft Teams and are managed through AOSP Device Management instead of Android Enterprise. That means they can:
-Enrol in Microsoft Intune automatically using firmware updates
-Be secured with encryption, OS compliance checks, and rooted device blocking
-Function without user-based sign-ins — ideal for shared spaces
If your organisation is unsure which devices qualify or how to manage them, Server Consultancy, the best IT support company for London SMBS, offers expert guidance. We help businesses like yours understand device compatibility, prepare enrollment strategies, and manage the full lifecycle of Teams Android devices using AOSP.
Why is Microsoft using AOSP?
Microsoft uses AOSP, or the Android Open Source Project, as the foundation for managing Teams Android devices because it provides a secure, flexible, and lightweight platform for enterprise environments that do not require Google Mobile Services (GMS).
Many Microsoft Teams-certified devices—such as phones, panels, and collaboration bars—are purpose-built for shared workspaces. These devices do not need consumer apps like Gmail or the Google Play Store, which are typically bundled with GMS. AOSP allows Microsoft to fully control the operating environment, ensuring consistent performance, better security, and deeper integration with Microsoft Intune.
Here’s why AOSP is ideal for Microsoft Teams hardware:
-No dependency on Google services: AOSP supports devices without needing Play Services, making it perfect for Teams hardware.
-Streamlined management: AOSP Device Management works seamlessly with Microsoft Intune to manage firmware, compliance, and enrollment centrally.
-Improved security: The AOSP model supports rooted device detection, device encryption, and controlled access, which are essential for Microsoft 365 environments.
-Scalability: AOSP allows Microsoft to standardise device behaviour across many OEMS while preparing the platform for future innovation in Teams Rooms and shared space technology.
By shifting to AOSP Device Management, Microsoft ensures that Teams Android devices are easier to deploy, more secure to manage, and built for modern business use cases, especially in industries that require strict compliance and simplified workflows.
What is device management on an Android phone?
Device management on an Android phone refers to the tools and processes used by IT administrators to control, monitor, and secure the device in a workplace setting. Whether the phone is used by an individual or shared among employees, mobile device management (MDM) ensures that it complies with company policies, connects securely to business services, and can be supported remotely.
In Microsoft’s ecosystem, AOSP Device Management manages Teams-certified Android devices, such as desk phones or panels, especially those not using Google services.
Key features of Android device management typically include:
-Enrolment into a management system like Microsoft Intune
-Policy enforcement such as password requirements, screen lock, and encryption
-Compliance checks to ensure the device meets minimum security standards
-Remote capabilities, including device wipe, restart, and configuration updates
-Application management, allowing approved business apps and blocking unauthorised ones
For Teams Android devices specifically, AOSP Device Management enables automatic enrolment via firmware, policy enforcement through Intune, and continuous compliance monitoring — all without requiring user sign-in or Google-based apps.
At Server Consultancy, we help London SMBS implement Android device management across various devices, ensuring they stay secure, compliant, and easy to support.