image
Setting Up Android Open Source Project (AOSP) Enrollment
Start course
Difficulty
Beginner
Duration
30m
Students
142
Ratings
5/5
Description

In this course, we review the enrollment options available and processes to follow for enrolling Android devices in Microsoft 365.

Learning Objectives

  • An overview of the many enrollment options available for Android devices
  • Learn the prerequisites needed before enrolling Android devices in Microsoft 365 via Intune 
  • Cover Android Enterprise, Android Device Administrator, and Android Open Source Project enrollment options

Intended Audience

This course is intended for those who wish to learn about Enrolling Android devices in Microsoft 365.

Prerequisites

You will require a basic understanding of Mobile Device Management in Microsoft 365.
Transcript

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.

About the Author
Students
91021
Courses
89
Learning Paths
56

Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.

In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.

In his spare time, Tom enjoys camping, fishing, and playing poker.