Intune and Google's Cloud Device Policy Controller (DPC)

-
Recently, I was looking at some compliance reports for Android enrolled devices in Intune and Google's Cloud DPC caught my attention. 


This got me curious and while researching I realized that there is very little documentation available in relation to Google's Cloud DPC and Intune so I decided to blog about it.

Before we dive into it, lets see how DPC fits in Enterprise Mobility Management (EMM) model first.

An Android Enterprise solution is a combination of three components: EMM console, Android Device Policy, and managed Google Play.

EMM console

EMM solutions typically take the form of an EMM console—a web application you develop that allows IT admins to manage their organization, devices, and apps. To support these functions for Android, you integrate your console with the APIs and UI components provided by Android Enterprise.

Android Device Policy

All Android devices that an organization manages through your EMM console must install Android Device Policy during setup. Android Device Policy is an app supplied by Android that automatically applies the management policies set in your EMM console to devices. This is where Google's Cloud DPC comes into picture. 

The Device Policy Controller (DPC) acts as the bridge between EMM console (and server) and the device. It creates and manages the work profile on the device on which it is installed. The work profile encrypts work-related information and keeps it separate from users' personal apps and data. Before creating the work profile, the DPC can also provision a managed Google Play Account for use on the device. The device policy controller is also used to provision fully managed devices.

Managed Google Play

Managed Google Play is an enterprise version Google Play that facilitates certain app management capabilities for Android Enterprise solutions. It combines the familiar user experience and app store features of Google Play with a set of management capabilities designed specifically for enterprises.

Google's Cloud Device Policy Controller (DPC)

For the Android Enterprise corporate-owned device deployment scenarios, Microsoft Intune uses the Android Management API and the Android Device Policy as DPC. Microsoft makes the configuration options available in the Microsoft Endpoint Manager admin center and enables enforcement of the configuration settings to the DPC which acts as the management agent, bridging between Microsoft Intune and the managed devices.

The device policy controller app enables -

1. Communication with Intune to apply profile, device restrictions and settings.
2. Implementation of managed configurations and allows verification of device compliance with the Intune policies.

After a device or work profile is provisioned, it's ready to be managed. Through the Android Management API, Android supports over 80 device and app management policies.

Well there you have it. With Microsoft directly using the Android Management APIs, not only this cuts down on the need for developing APIs of their own, it also eliminates the need for adding new Android Management features separately. Whenever new features are added in Android Management APIs, Microsoft can just directly pull them and integrate in Intune.

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more