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. Logitech CollabOS 1.14.B AOSP will be available June 30th, 2025, see CollabOS Devices: Teams AOSP Device Management Launches June 30th
Please see Microsoft Blog Post, which is recommended to read for more details. You will find an FAQ on migration, recommendations on CA policies etc.
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 that supports Intune AOSP device management via Teams Admin Center (TAC).
Phase
Days
Auto Update window
Validation phase
Days 0â15
July 21âAugust 4
General availability (default)
Days 16â45
August 5âSeptember 4
Final
Days 46â60
September 5âSeptember 19
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
The following steps will outline the mandatory steps to transition Teams Android devices to AOSP DM if you use Intune device management.
Review the guides belowÂ
Update to CollabOS 1.14.0
Create a new Intune Enrollment Profile
Create a new Intune Compliance Policy
Update to CollabOS 1.14.B
Confirmation after successful update
Recommended deployment steps:
Roll out the update in controlled batches
Verify that all Logitech devices are running CollabOS 1.14.0 or higher
You can control CollabOS version deployment using update channels in Sync.
Monitor device behavior after each batch
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
The following guide is a simplified guide based on Microsoft AOSP documentation, but is tailored for Logitech devices.
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/ Rally Bar Mini: 1.14.180
Rally Bar Huddle: 1.14.130
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.
Overview
The following steps will outline the mandatory steps to transition Teams Android devices to AOSP DM if you use Intune device management.
Update to CollabOS 1.14.0
Create a new Intune Enrollment Profile
Create a new Intune Compliance Policy
Update to CollabOS 1.14.B
Confirmation 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 areon the following releases:
Rally Bar/ Rally Bar Mini: 1.14.180
Rally Bar Huddle: 1.14.130
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âs recommendation is not to use Configuration Profiles for AOSP Device management in Intune, since the device will not function properly if it is used. Intune Configuration Profiles are not the same as Teams Admin Center Configuration Profiles.
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.4. Software Update
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)
5 Update to CollabOS 1.14.B
Important before updating:
If you have a Tap IP connected, please make sure that you update the Rally Bar first, then Tap IP.
Do not try to update to CollabOS 1.14.B via TAC, since it will yet be available.
Before you click update, make sure that the update shows the correct CollabOS 1.14.B version. If you donât see these versions.
Please verify that software update shows one of the following CollabOS versions:
Rally Bar, Rally Bar Mini: CollabOS 1.14.377
Rally Bar Huddle: CollabOS 1.14.363
RoomMate: CollabOS Â 1.14.370
Tap IP:Â CollabOS 1.14.371
Tap Scheduler: CollabOS 1.14.373
Dock Flex: CollabOS 1.14.361
Rally Board 65: Coming soon
Option 1:Â Update via Logitech Sync
Make sure that you are on the CollabOS Beta channel
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 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
Rally Bar Mini:Â CollabOS 1.14.377
RoomMate: CollabOSÂ 1.14.370
Rally Bar Huddle: CollabOS 1.14.363
Tap IP:Â CollabOS 1.14.371
Tap Scheduler: CollabOS 1.14.373
Dock Flex: CollabOS 1.14.361
Authenticator 6.2503.2060
Microsoft Intune 24.09.1
Teams Rooms 1449/1.0.96.2025031102
Teams Panels 1449/1.0.97.2025031901
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.Â
Sign in to the Microsoft 365 admin center.
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
Microsoft
Intune ending support for Android device administrator on devices with GMS in December 2024
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