Starting May 15, 2024, Microsoft Teams Android devices will undergo a significant transition to Intune Android Open Source Project (AOSP) device management. This migration involves automatic firmware updates and is designed to enhance mobile device management (MDM) capabilities for Teams devices. Here are the key impacts and considerations:

Affected Devices

The migration will impact a wide range of OEM devices, including but not limited to:

• AudioCodes: Phones (C470HD, C430HD, etc.), Rooms (RXV81, RXV200, etc.), Panels (RX Panel).
• Crestron: Panels (TSS-770, TSS-1070), Rooms (Crestron AIO Video Bar 70, etc.).
• Cisco: Rooms (Cisco Room Bar, Cisco Room Kit EQ, etc.), Panels (Cisco Navigator Panel).
• DTEN: Rooms (DTEN D7X 75", DTEN Bar, etc.).
• Jabra: Rooms (Jabra Panacast 50 VBS, etc.).
• Logitech: Rooms (RallyBar, RallyBar mini, etc.), Panels (Tap Scheduler, DockFlex).
• Neat: Rooms (Neat Pad, Neat Bar, etc.), Displays (NeatFrame), Panels (Neat Pad).
• Poly: Phones (CCX350, CCX400, etc.), Rooms (Poly Studio X30, X50, etc.), Panels (TC10).
• Yealink: Phones (MP54, MP56, etc.), Rooms (Yealink MeetingBar A10, A20).

Migration Phases

The migration will follow a phased schedule:

1. Validation Phase (0-15 days): Initial phase to validate the updates.
2. General Phase (16-45 days): Default phase for broader rollout.
3. Final Phase (45-60 days): Completion phase for final updates.

Prerequisites and Preparation

To ensure a smooth migration, organizations must complete all necessary prerequisites for AOSP device management. Failure to do so may result in devices signing out during the migration process. Key steps include:

• Updating Firmware: Ensure devices are updated to the required firmware versions.
• Compliance Policies: Set up compliance policies for AOSP devices to avoid downtime and ensure devices remain compliant within the tenant.

Potential Issues

Organizations may face several challenges during the migration:

• Device Sign-Out: Devices may sign out if prerequisites are not met.
• Re-Enrollment Issues: Some devices may refuse to re-enroll after signing out, requiring administrator intervention.
• Downtime: Teams Meeting Room Android devices and phones may experience downtime if policies are not set up in advance.

Recommendations

To mitigate these impacts, organizations should:

• Prepare Ahead: Set up enrollment profiles and compliance policies for AOSP devices well in advance.
• Monitor Updates: Keep track of the update schedule and ensure all devices are compliant.
• Admin Support: Provide adequate support to administrators for troubleshooting and re-enrollment issues.

For more detailed guidance on deploying and enrolling Android devices with Intune, please refer to the official Microsoft documentation: Android device enrollment guide for Microsoft Intune | Microsoft Learn.