How to setup Android Enterprise – Corporate-owned dedicated devices with Microsoft Intune

Earlier I wrote about how to configure Android Enterprise – Work Profile. This Android Enterprise mode is designed for personal-owned mobile devices. For corporate-owned devies there are two Android Enterprise modes, one for dedicated devices and one for fully managed user devices. In this blog I will show you how to configure Android Enterprise – Corporate-owned dedicated device mode within Microsoft Intune.

As the name suggests, Corporate-owned dedicated device mode is for devices without user affinity. For example, Kiosk devices and hand scanners.

Requirements

Before you can start with the configuration of the Corporate-owned dedicated device mode, make sure you have the following in place;

  • An Azure tenant with Microsoft Intune up and running
  • A Google Account linked to Microsoft Intune like described in Step 1 of this blog
  • Android test device(s)

In this blog

In this blog I will cover the following topics;

  1. Create an Android Enterprise Corporate-owned dedicated device enrollment profile
  2. Created an Azure AD Dynamic group
  3. Assign Managed Google Play app(s)
  4. Create and Assign a Restriction Profile (optional)
  5. Test the results

Step 1: Create an Android Enterprise Corporate-owned dedicated device enrollment profile

Let’s start with creating the Android Enterprise Corporate-owned dedicated device enrollment profile. To do this, login to the Microsoft Azure Portal.

Navigate to: Microsoft Intune > Device enrollment > Android enrollment and click Corporate-owned dedicated devices

Click the + Create profile button

Fill in a Name and optional a Description. A token will be created in the next step with an expire date. A token can be valid for maximum 90 days (Policy of Google). Select your expiration date and click Create

Click Token

Click Show token.

This token is needed when enrolling the Corporate-owned dedicated devices.

Step 2: Created an Azure AD Dynamic group

Second step is to create an Azure AD Dynamic group to scope the Android devices that are enrolling with the token from step one. All policies (profiles) and applications needs to be assigned to this group.

Navigate to: Microsoft Intune > Groups > All groups and click the +New group button

Select Security as Group type. Give this group a name and description and select Dynamic Device as Membership type.

Click Dynamic device members

Create the following Simple rule;

Add devices where: enrollmentProfileName – Match – And then the name of the profile created in step 1. In my case this is AE-Kiosk.

Click Add query and Create 

Step 3: Assign Managed Google Play app(s)

To publish applications to Android devices that are in Corporate-owned dedicated device mode, Google Managed apps needs to be assigned as Required to the group created in step 2. For this blog I will assign Microsoft Edge as a required application. For step-by-step instructions on how to publish Google Managed apps, see step 2 in this blog.

Step 4: Create and Assign a Restriction Profile (optional)

An Android device in Corporate-owned dedicated device mode is already pretty locked down. There is not much a user can do on the device other than starting the published applications (and make phone calls if it is a phone). However, there are some possibilities the user can do that maybe you want to block as administrator. Examples are use of the camera and performing a factory reset.

To block these functionalities, you can create and assign a restriction profile. I show you step-by-step how to do this below;

Navigate to: Microsoft Intune > Device configuration > Profiles and click +Create profile

Fill in a Name and a Description and select Device restrictions (Under Device Owner Only) as Profile type.

Click Settings and configure the settings that apply to you. For this blog I will Block the Factory reset. Click OK and Save.

Open the Assignments page

Select the group created in step 2 and click Save

Step 5: Test the results

Lets test the results by enrolling a new Android device.

Left: Tab 7 times a white space on the screen

Right: Tab Next

Left: Select the Wi-Fi you want to connect with or select Use Mobile network for setup

Right: Updates and the QR reader will be installed

Left: This is the moment where you need to scan the QR Code

Right: After you scan the QR code select I have read and agree to all of the above (if you do) and click Next

Left: Select at least End User License Agreement and tab Next

Right: The device will now be configured in Android Enterprise – Corporate-owned dedicated device mode

Left: As you can see, only some basic apps are available like the Phone, Contacts and Settings. As you also can see, the Microsoft Edge browser is installed.

Right: It is not possible for the end user to perform a Factory reset, this indicates that the Restriction policy is applied successful.

5 comments

  • Thanks for sharing this interesting article, Robin!! Android Enterprise is creating waves, benefitting major industries with its simple and yet powerful features. This was another good thing to know and will be helpful.

  • Excellent article and I have been building some kiosk devices on Intune attempting to mimic how we currently have it in MI Cloud.
    Running into a couple issues but my main one right now is when the device is setup I cannot seem to get the camera to work in Chrome even though I have it set to not configured. I have tried permissions to device default, prompted and always allow and no success. Any ideas or have you run into this?

  • This is awesome. When you create the token for hte Corporate-owned dedicated devices how do you assign a Device Enrollment manager?

About Robin Hobo

Robin Hobo

I work as a Senior Solution Architect with focus on the Modern Workspace. I am specialized in Azure Virtual Desktop (AVD), Windows 365 and Microsoft EM+S (including Microsoft Endpoint Manager - Microsoft Intune).

For my full bio, check the About Me page. You can also join me on the following social networks:

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close