1. Knowledge Base
  2. Configure
  3. Remote from a web browser

Frequently Asked Questions - Intune AOSP

Q: What is Microsoft Intune AOSP update about?

Brief background

Microsoft Endpoint manager (Intune) is a popular EMM platform for device management. RealWear HMT-1 and HMT-1Z1 device can be managed by an enterprise IT admin using Intune.

Android device admin mode (legacy) enrollment was the only support option available in Intune for managing RealWear HMT devices, which had limited capabilities.


Microsoft has announced Android AOSP (Android Open-Source Project) public preview enrollment feature with 2 new options for Android devices.

IT admins can now enroll HMT devices with this option using simple QR codes.

RealWear-Microsoft-Endpoint-Manager_blog v3[1]
Q: What does the AOSP announcement change?

Out of the box, HMT devices can be enrolled into Microsoft Endpoint Manager using an enrollment QR code.

Prior to the AOSP update, Company portal app had to be pre-installed on the HMT to onboard them to Intune.

Q: What are the available enrollment types now?

IT admins now get 3 options to enroll HMT devices with Intune:

  1. Continue to use device admin enrollment (Legacy mode)
  2. Use Android AOSP – user-based enrollment
  3. Use Android AOSP – user less enrollment

Q: What is the difference in the 2 AOSP enrollment types?

Both options provide QR code-based enrollment,

  1. Corporate owned user associated devices are directly associated with an AD user
  2. Corporate owned user less devices – not mapped to any user at enrollment

This gives the IT admin freedom of options to choose from while planning device enrolment and deployment scenarios.

Also, the end user experience is simplified with the user of a QR code.

More details including steps and screenshots are available in the Microsoft blog post.

Q: Who creates the QR code and how?

Enrollment QR codes are created by the Microsoft Endpoint manager admin within an enterprise IT or the EUC mobility team.

Detailed instructions on how to create the QR codes are available on Microsoft blog post.

Q: What happens to RealWear Foresight?

RealWear Foresight and Microsoft Intune have always worked together and will continue to remain compatible with each other. 

Q: Do I need to change anything on RealWear Foresight?

It is not required to make any changes to Foresight.

We can continue to use Foresight to manage HMT devices for application deployment.

Microsoft Teams app for HMT will continue to be deployed through Foresight only.


Q: Where can I find more information on Microsoft AOSP announcement?

Below are some links for more information:

  1. Microsoft Technical update link
  2. RealWear Announcement Link

Q: What configuration profiles are possible today with AOSP?

While most of the device compliance and conditional access policies are available to validate in the public preview, there are a few scenarios not yet supported in this preview release but will be completed when Microsoft will roll this capability out for general availability, including:

  • Certificate and WiFi management
  • App protection policies on user-associated devices
  • End user experiences - such as providing device compliance information in the Microsoft Intune app
  • Filters and scope tags
  • Additional remote actions e.g., pin reset

Q: When will Microsoft release General Availability for AOSP?

Please contact your Microsoft account manager for the GA timelines.

Q: Who can help us to validate the AOSP with HMT devices?

Please reach out to Realwear support team – support@realwear.com
for assistance with setting up HMT devices for validation.

For Intune related question, reach out to your internal IT admin or Microsoft support.