AOSP Device Management Migration for Teams Rooms on Android

Microsoft announced the transition of Teams Rooms on Android and Teams Panels to a new device management solution leveraging Android Open Source Project Device Management (AOSP DM).

This is a critical update as Google plans to deprecate the Android Device Administrator model in future Android releases. In June, 2025 Logitech released CollabOS 1.14.B AOSP to provide support for Microsoft AOSP DM for most CollabOS devices except Rally Board 65 (see CollabOS Devices: Teams AOSP Device Management Launches June 30th). In August, 2025 Logitech released CollabOS 2.0.B AOSP to provide support for Microsoft AOSP DM for Rally Board 65 (see Rally Board 65 release notes).

Please see Microsoft’s official blog Moving Teams Android Devices to AOSP Device Management for more details. You will find an FAQ on migration, recommendations on CA policies, and more.

The table below lists Logitech CollabOS devices available as of August, 2025, and the minimum CollabOS release that supports Microsoft AOSP DM.

Automatic Updates via TAC

Starting July 21, 2025, Microsoft will begin auto-updating Logitech configured to Teams Rooms on Android and Teams Panels to CollabOS 1.14.B, which support Intune AOSP device management via Teams Admin Center (TAC).

For detailed guidance, see Microsoft’s official blog Moving Teams Android Devices to AOSP Device Management.

IMPORTANT: Devices may sign out during migration if prerequisites aren’t completed.

Overview

This section outlines the mandatory steps to transition Microsoft Teams Rooms for Android and Teams Panel devices to Microsoft AOSP DM if you use Intune device management. It provides a simplified guide based on Microsoft AOSP documentation, but is tailored for Logitech devices.

• Review the guides below 

  • Microsoft’s announcement blog post

  • Microsoft’s Migrating Teams Android Devices to AOSP Device Management from Device Administrator guide

• Update CollabOS devices to CollabOS 1.14.0

  • Except Rally Board 65, which should be updated to CollabOS 2.0.A

• Create a new Intune Enrollment Profile

• Create a new Intune Compliance Policy

• Update CollabOS devices to CollabOS 1.14.B

  • Except Rally Board 65, which should be updated to CollabOS 2.0.B

• Confirm after successful update

Recommended deployment practices:

• Verify that all CollabOS devices are running CollabOS 1.14.0 or higher (or CollabOS 2.0.A in the case of Rally Board 65)

  • You can control CollabOS version deployment using update channels in Sync.

• Keep room displays powered on during the update

• Disable power saving in TAC profiles during the update (see how)

• Validate the update on a small group of devices before wider deployment

• Perform the wider deployment in controlled batches

• Monitor device behavior after each batch update

Prerequisites

Please complete the following important steps before starting the transition to AOSP DM.

• If you're using Intune

  • To prevent Teams Rooms from signing out after the update, you must:

  • Have an active Teams Room license assigned for your devices.

  • Have an active Microsoft Intune tenant

  • Ensure Teams and Intune URLs need to be allowed in firewalls

    • Allow Teams traffic, Office 365 endpoints

    • Allow Intune traffic, Intune endpoints

  • Make sure your devices are updated to the following releases:

    • Rally Bar or Rally Bar Mini: 1.14.180

    • Rally Bar Huddle: 1.14.130

    • Rally Board 65: 2.0.164

    • RoomMate: 1.14.170

    • Tap IP: 1.14.181

    • Tap Scheduler: 1.14.181

    • Dock Flex: 1.14.147

• If you're not using Intune

  • You must make sure Intune is disabled in your Microsoft 365 account.

  • See this guide from Microsoft

• It is recommended to validate the update on a subset of devices before deploying widely.

Update process

The following steps will outline the mandatory steps to transition Teams Android devices to AOSP DM if you use Intune device management.

1. Update to CollabOS 1.14.0

   1. Except Rally Board 65, which should be updated to 2.0.A

2. Create a new Intune Enrollment Profile

3. Create a new Intune Compliance Policy

4. Update to CollabOS 1.14.B

   1. Except Rally Board 65, which should be updated to 2.0.B

5. Confirm after successful update

The guide is based on this AOSP migration guide from Microsoft:

1. Update to CollabOS 1.14.0

Before updating to CollabOS 1.14.B AOSP, make sure your devices are on the following releases:

• Rally Bar/ Rally Bar Mini: 1.14.180

• Rally Bar Huddle: 1.14.130

• Rally Board 65: 2.0.164

• RoomMate: 1.14.170

• Tap IP: 1.14.181

• Tap Scheduler: 1.14.181

• Dock Flex: 1.14.147

If the device is showing a newer update version than this, you can use Logitech Sync to update using a Sync channel.

Option 1: Check CollabOS version In Teams Admin Center (TAC)

Sign into Teams Admin Center (TAC) and check CollabOS versions are the ones mentioned above 

Option 2: Check versions in Logitech device settings

Go to Logitech device settings and check the CollabOS versions are the ones mentioned above

Option 3: Check CollabOS version In Logitech Device Settings

Go to Logitech Logitech Sync and check the CollabOS versions are the ones mentioned above

2. Create a new Intune Enrollment Profile

The first step in preparing devices for AOSP management is setting up enrollment profiles within Microsoft Intune:

• Sign in to the Microsoft Intune admin center using your administrator account 

• Navigate to Devices > Android > Enrollment > Corporate-owned, user-associated devices or go directly to Corporate-owned, user-associated devices

• Click Create Profile 

• Name the Profile appropriately

• Enable “For Microsoft Teams devices”

• Click Next to save the profile

3. Create a new Intune Compliance Policy

• Go to Compliance or go directly to Compliance

• Click Create Policy

• Select Android (AOSP)

• Click Create and name the profile appropriately

• Click Next

• Select “Block” in “Rooted devices”

• Enter “10” in “Minimum OS version”

• Select “Yes” for “Require encryption of data storage on device.”

• Click Next

• Select what is appropriate for your Compliance Policy

• Click Next 

• Add the group you want to associate the Compliance Profile with. (If you don’t see any groups or you need a new one first, then go to Groups and don’t forget to add members to the group)

• IMPORTANT! If you don't assign the Teams room account to the group with the Compliance Profile, the device might still sign-in, but can show up as non-compliant for 30 days, then sign out.Select the Group you want to assign. 

• Click Select

• Click Next

• Click Create

Intune Configuration profiles (Optional)

Logitech recommends not using Device Restrictions under Manage Devices > Configuration in Intune for AOSP device management.

Please note that Intune Configuration Policies are not the same as Teams Admin Center Configuration Profiles, and may lead to unexpected behavior on Teams Rooms devices.

If you still choose to apply a Configuration Policy, ensure that all settings are left "not configured" (i.e., not explicitly blocked or enabled).

For example,:

• Blocking screen capture will interfere with Remote UI functionality, which is critical for remote support and diagnostics

• Blocking access to Camera will block the Camera in MS Teams meetings

• Disabling Bluetooth causes the remote control cease functioning

Intune Device Name Template (Optional)

Device name template is supported and details can be found here on how to use it.

Conditional Access policies/rules (Optional)

See Microsoft documentation for more details

Dynamic Device Groups (Not supported)

Do not use Dynamic Device Groups that require attributes that are populated by Intune (e.g. device.deviceManufacturer -eq "Logitech"), which may lead to device signing out.

Check Device Overview in Intune before updating

• Go to intune.microsoft.com

• Log in with your admin account

• Navigate to  Devices > by platform > Android

• Filter out your device in the search box

Confirm the information is correct according to the data below:

• Ownership: Personal

• Compliance: Compliant

• OS: Android (device administrator)

• OS version: 10

• Manufacturer: Logitech

• Model: VR0035 (or whatever your model is)

• Serial: 2225WTXXXXXX  (or whatever your serial is)

4. Software Update

Important considerations before updating:

• If you have a Tap IP connected, please make sure that you update the Rally Bar / Rally Bar Mini / Rally Bar Huddle / Rally Board 65 / RoomMate first, then the associated Tap IP.

• Before you click update, make sure that the device will update to at least the minimum required CollabOS version:

  • Rally Bar, Rally Bar Mini: CollabOS 1.14.377 or higher

  • Rally Bar Huddle: CollabOS 1.14.363 or higher

  • Rally Board 65: CollabOS 2.0.300 or higher

  • RoomMate: CollabOS  1.14.370 or higher

  • Tap IP:  CollabOS 1.14.371 or higher

  • Tap Scheduler: CollabOS 1.14.373 or higher

  • Dock Flex: CollabOS 1.14.361 or higher

• Wait until all devices have been updated and rebooted

• Repeat update process for all connected devices (e.g. Tap IP)

Option 1:  Update via Logitech Sync

Update via Logitech Sync, see How to Update CollabOS Devices

Option 2:  Update via Logitech device settings

• Go to Logitech Device Settings click the update tile

• Click Update Now

• Wait until all devices have been updated and rebooted

• Repeat update process for all connected devices

6. Confirmation after successful update

• Confirm that Teams Rooms is logged in, the Teams Home screen is shown, and the application is ready to use.

• Confirm that Intune, Teams Admin Center, and CollabOS device settings show the correct information.

Check Device Overview in Intune

• Go to intune.microsoft.com

• Log in with your admin account

• Navigate to  Devices > by platform > Android

• Filter out your device in the search box

Confirm the information is correct according to the data below

• Ownership: Corporate

• Compliance: Compliant

• OS: Android (AOSP corporate-owned, user-associated)

• OS version: 10

Check CollabOS and App versions in Teams Admin Center (TAC)

• Confirm that the software shows the correct CollabOS and App versions in both Logitech device settings and Teams Admin Center 

  • Rally Bar: CollabOS 1.14.377 or higher

  • Rally Bar Mini:  CollabOS 1.14.377 or higher

  • Rally Bar Huddle: CollabOS 1.14.363 or higher

  • Rally Board 65: CollabOS 2.0.300 or higher

  • RoomMate: CollabOS 1.14.370 or higher

  • Tap IP:  CollabOS 1.14.371 or higher

  • Tap Scheduler: CollabOS 1.14.373 or higher

  • Dock Flex: CollabOS 1.14.361 or higher

  • Authenticator 6.2503.2060 or higher

  • Microsoft Intune 24.09.1 or higher

  • Teams Rooms 1449/1.0.96.2025031102 or higher

  • Teams Panels 1449/1.0.97.2025031901 or higher

  

• Migration is complete

How to use Teams without Intune?

You can use Teams without creating an Intune enrollment profile and compliance policy. You will need to disable the Microsoft Intune Plan on Microsoft 365 account level. If you are already using Teams without Intune and have already removed Microsoft Intune Plan from the Microsoft 365 account, there are no additional steps to migrate to AOSP. 

1. Sign in to the Microsoft 365 admin center.

2. Deselect the Intune license from the Teams account for the Android device.

After you remove an Intune license, there's a 30 day grace period, during which the device still functions. The device must sign in again after this step to avoid enrolling in Intune under device administrator management again. See this guide from Microsoft for more details.

Resources

Logitech

• Logitech CollabOS devices transitioning to Microsoft Intune and Authenticator for Android Device Management

• How to Update CollabOS Devices 

• Logitech Sync portal

Microsoft

• Moving Teams Android Devices to AOSP Device Management

• Intune ending support for Android device administrator on devices with GMS in December 2024

• Microsoft Intune admin center Message center: MC665936, 

• Moving Teams Android Devices to AOSP Device Management

• Set up Intune enrollment for Android (AOSP) corporate-owned userless devices

• Set up Intune enrollment for Android (AOSP) corporate-owned user-associated devices

• How to use Intune in environments without Google Mobile Services

• Teams Certified Releases.

• Microsoft Intune admin center

• Update Teams Rooms on Android via Teams Admin Center

Google

• What you need to know about Device Admin deprecation

• Is Android Enterprise available in my country?