Neat Devices and Microsoft Teams AOSP Device Management Migration

Last updated June 17, 2025

Table on Contents

1. Introduction

The content in this article applies to all Neat devices running Microsoft Teams software. These include the Neat Bar, Neat Bar Gen 2, Neat Bar Pro, Neat Board, Neat Board 50, Neat Board Pro, Neat Pad (as Room controller or Teams Panel), and Neat Frame (running Teams Displays in Personal, Hot Desking and Virtual Front Desk modes).

1.1 What is AOSP Device Management?

AOSP Device Management enrolment project is Microsoft’s replacement for the Android Device Administrator and Company Portal application that is currently used for authenticating Android based devices in Microsoft Intune. The Company Portal app uses Android Device Administrator (ADA) registrations, which Google is discontinuing, requiring a new method for device registration and authentication.

Android Open-Source Project (AOSP), is what Neat uses to build the platform for Microsoft Teams Rooms on Android. Neat is closely working with Microsoft on the AOSP Device Management enrolment development for our devices.

Your administrator can find a reference to this upcoming change in the Microsoft 365 Admin Center here (Message ID: MC665936). You can also find a blog post here from Microsoft on device migrations.

For Microsoft Teams devices based on Android, your Microsoft Intune administrator will need to make some adjustments before the software rolls out to Neat devices. There are two main processes involved in this initiative:

  1. New Device Setups or after a Factory Reset:
    • For new installations or post-factory reset, the latest firmware will run Microsoft Intune and Microsoft Authenticator apps, requiring the registration of the device with the latest AOSP policies in Intune.
  2. Migrating Existing Devices:
    • For existing deployments, it will require transitioning the devices from using Company Portal with ADA registration to AOSP device management enrolment and migrating the room credentials. This method eliminates the need for on-site visits, as the migration is handled remotely via a Neat firmware update.

Important Note: If you need to manage devices remotely, Neat Pulse provides full remote control capabilities for your deployment. If you haven’t signed up for Neat Pulse yet, visit Neat Pulse to create a free account that includes the Remote Control feature. For more information or to demo this cloud service please have a look here.

2. Getting ready for AOSP Device Management Enrolment

To prepare for AOSP Device Management enrolment, Microsoft has provided documentation which can be viewed on their website: Migrating Teams Android Devices to AOSP Device Management from Device Administrator

2.1 Steps to Prepare:

  1. Create a new AOSP Enrolment Profile:
    • Follow Microsoft’s guidelines to create the necessary enrolment profile.
  2. Create Configuration and Compliance Policies: (see video below)
    • Create new Configuration and Compliance policies, as any existing policies configured with Android Device Administrator will not be compatible with the new AOSP devices.
    • For further information, see the Microsoft Learn site here.
    • Microsoft has listed out which Compliance Policies are supported with AOSP Device Management – visit their document here.

Below is an example of the enrolment policy that will need to be created:

Figure 1: Example of Neat device Enrolment policy

If you have created a token previously, it might have expired. You can simply replace that token or extend it. Token expiration date can be set to 65 years. Also note that you can only have one profile that is enabled for Microsoft Teams devices. If you try to create a second one, you’ll receive an error, but it won’t explicitly tell you what the error is and why.

Note that Wi-Fi is not supported in the AOSP profile, even though it is shown in the profile creation. That is planned for future use by Microsoft.

Here are short videos with step by step guide on both stages of the setup.

Step One

Step Two (optional)

3. Full Video overview of Migration to AOSP Device Management

4. Step by Step Overview

Step One – Visit Teams Admin Center and find your device and head to Health tab. If you don’t see any updates for Firmware, then your Teams App could be out of date (as per below). As a minimum, it must be on the March 2025 release (1449/1.0.96.2025031102).

Step Two – Update the Microsoft Teams App first and wait for that to complete.

Update Teams App first

Step Three – Once the Teams App is updated, we should now see a Firmware update.

Step Four – Apply the Firmware update to both Neat Bar and Neat Pad (under Touch Console tab). It will remind you to complete the step beforehand of creating your Enrolment Profile in Microsoft Intune.

Step Five – Observe the Firmware Update progress via the Device > History tab. First it will be queued for around 15 minutes and then will move to In Progress.

Step Six – Once the devices are In Progress, they will show the Neat UI and the progress bar of Downloading and then Applying the firmware. Once completed, they will reboot.

Step Seven – Once device has completed the migration, you will see the apps are updated in Teams Admin Center.

Step Eight – Verify your Intune devices and it will show as a Compliant AOSP Corporate Owned device.

5. General Availability timeline

As of May 2025, Neat AOSP Firmware entered the Microsoft TAP (Technology Adoption Program) process for testing. This update will be a special build for just Microsoft TAP customer, available exclusively via Teams Admin Center.

Recently, Microsoft announced that Automatic Updates will resume from May 15th 2025. However, this is not for Neat devices, as Neat devices are still being tested in the TAP Preview. Neat devices are planned to begin the auto updates from June 17th 2025 with devices in the Validation ring. See below for a timeline.

After successful testing when the TAP process has finished, and all users have migrated to AOSP device management via Teams Admin Center, the AOSP device management enrolment firmware will be made default as part of the Neat firmware updates later in 2025. This means that any new devices will then be AOSP Device Management from the out of box experience and will not do a migration upon setup. This will happen at some point in the second half of 2025.

This migration will be free of charge, like all other Neat software updates. There will be notifications in Teams Admin Center warning you when before you push the build containing the AOSP device enrolment migration, that you must ensure you have your policies setup beforehand.

As of May 2025, when you navigate to the Teams Devices section of TAC has a new splash page reminding you of all the changes coming up required for AOSP Migration.

Here are all the links for reference:

If you dismiss that popup, you can access it still in the dashboard, as highlighted below.

Currently, no changes or configurations are required on your Neat devices.

If you have any further questions, please contact us at support@neat.no.

6. FAQs

Q.1. Is Microsoft switching off Device Administrator on 31st December 2024?
A.1. No, Device Administrator is not being removed from Intune, but it is being moved to an Unsupported state for GMS devices. As Microsoft Teams Certified Devices do not contain GMS services, they will carry on working as normal and be supported. More details here.

Q.2. Will devices running Device Administrator be supported by Neat and Microsoft after 31st December 2024?
A.2. Yes, any certified Microsoft Teams device will continue working and be supported whilst still operating with Device Administrator.

Q.3. What happens if I do nothing?
A.3. Your devices will not sign out, but will carry on working being configured with ADA. However, if you update the Neat firmware that only has AOSP device registration apps of Microsoft Intune and Microsoft Authenticator, then your device will sign out upon reboot, if the Intune profile hasn’t been created.

Q.4 What happens if I create an AOSP profile now?
A.4 Nothing, Neat devices will ignore it for now. We actually would advise creating the enrolment token now, so you are ready. However, you will also need to create/modify any other Intune policies that might want to use.

Q.5. What version will contain the AOSP software image?
A,5. Neat OS 25.1 will be in Preview and Stable channels (not AOSP enabled) and 25.1.3 will be exclusively available in Microsoft Teams Admin Center for Microsoft TAP customers only.

Q.6. What happens if I factory reset my device on 25.1.3? Will I lose the AOSP migration?
A.6. No, your device will remain on 25.1.3 and will continue to sign in and setup as a AOSP registered device.

Q.7. What happens if I upgrade to 25.2.x, will I lose the AOSP registration?
A.7. No, your device will remain as an AOSP registered device and again, 25.2.1 will be exclusively available via Teams Admin Center if you’ve not upgraded yet.

Q.8. When will Neat devices be forced to use AOSP?
A.8. Based upon Microsoft’s timeline detailed here, all Neat devices will get the automatic updates by 14th August 2025.

Q.9. Could I just remove the Intune license from the resource account licenses.
A.9. Absolutely, you can do this if you do not want to use Intune controls or policies.

Q.10. Can I roll back from AOSP to ADA enrolment?
A.10. No you cannot, once you have migrated your device in 2025 when Neat has AOSP device enrolment only firmware, you will not be able to register with Device Administrator.

Q.11. What happens when my Intune enrolment profile expires? Do devices get signed out?
A.11. No, devices already registered and signed in, do not get signed out. Only new device registrations will fail. However, you can create an enrolment profile token that lasts for 65 years (previously it was 90 days).

Q.12. Do I still need to add the serial numbers to Intune as Corporate Identifiers with AOSP Device Management devices?
A.12. No, AOSP Device Management automatically marks the devices as Corporate owned devices. Non Microsoft Teams devices do not have access to the enrolment token, ensuring personal devices such as mobile/cell phones would have to follow the standard Intune policies in place.

Q.13. Why isn’t Microsoft using Google Enterprise features in Intune?
A.13. Google Enterprise features in Intune require components like the Google Play services and other components, the whole idea around this piece of work is that it doesn’t require any extra Google services running on the device, keeping the appliance software slimmed down.

Q14. Will I now be able to use SCEP and Intune to deployed certificates once on the AOSP Firmware?
A14. No, there are no additional benefits with the AOSP firmware relating to SCEP and Intune today.

Q.15. Is AOSP device enrolment the same thing as MDEP (Microsoft Device Ecosystem Platform).
A.15. No, this AOSP device enrolment migration has nothing to do with MDEP which is the operating system Microsoft is development on the Android Open Source Project, just like Neat does).