Welcome to Android (AOSP) Enrollment.

The last two Android enrollment options I want to touch on are the Android (AOSP) Corporate-Owned User-Associated Enrollment option and the Android (AOSP) Corporate-Owned Userless Enrollment option. Since these are both currently in preview, I’m not gonna dive too deep, since it’s possible that they go away at some point. But, that said, I do want to introduce them to you.

If you have corporate-owned, user-associated devices that are built on the Android Open Source Project platform, you can use Intune’s Android (AOSP) Corporate-Owned User-Associated Enrollment to get them enrolled in Intune. This option is good for single-user devices that are not integrated with Google Mobile Services and are to be used only for work.

Before you can enroll and manage these devices, you need an active Microsoft Intune tenant, and the devices must be RealWear devices that have been updated to Firmware 11.2 or later.

As was the case with many of the other Android enrollment options, this option also requires you to set Microsoft Intune as the MDM authority. You’ll also need to assign valid licenses to all RealWear device users.

Once you’ve met the necessary prerequisites, you can then create an enrollment profile to allow device enrollment.

After the enrollment profile is created, Intune will generate a QR code token that you use for enrollment. You scan the QR code to enroll devices in Intune.

You should also create device groups so you can group and enroll devices as you see fit. 

During the enrollment process, the Intune app and the Microsoft Authenticator app are both automatically installed and opened on the device. This allows the device to be enrolled.

Once a device has been enrolled, the Intune app automatically installs app updates for itself and for the Authenticator app. Devices that have been enrolled using Android (AOSP) Corporate-Owned User-Associated Enrollment can be remotely wiped and remotely deleted.

If you have corporate-owned, userless devices that are built on the Android Open Source Project platform, you can use Intune’s Android (AOSP) Corporate-Owned Userless Enrollment to get them enrolled in Intune. This option is good for shared devices that are not integrated with Google Mobile Services and are to be used to accomplish a specific set of tasks at work.

Before you can enroll and manage these devices, you need an active Microsoft Intune tenant, and the devices must be RealWear devices that have been updated to Firmware 11.2 or later.

As was the case with many of the other Android enrollment options, this option also requires you to set Microsoft Intune as the MDM authority. You’ll also need to assign valid licenses to all RealWear device users.

Once you’ve met the necessary prerequisites, you can then create an enrollment profile to allow device enrollment.

After the enrollment profile is created, Intune will generate a QR code token that you use for enrollment. You scan the QR code to enroll devices in Intune.

You should also create device groups so you can group and enroll devices as you see fit.

During the enrollment process, the Intune app and the Microsoft Authenticator app are both automatically installed and opened on the device. This allows the device to be enrolled.

Once a device has been enrolled, the Intune app automatically installs app updates for itself and for the Authenticator app. Devices that have been enrolled using Android (AOSP) Corporate-Owned Userless Enrollment can be remotely wiped and remotely deleted.