Using conditional launch in Intune App Protection Policy to manage MAM enrollments

-

When it comes to managing devices using Intune, organization can either enroll using MDM (Mobile Device Management) and\or MAM (Mobile Application Management). Normally, most organizations go for MDM for managing corporate devices and MAM for managing BYO devices. In case of MDM, enrollments involving manufacturer and OS version, as shown below -


But how do you this in MAM? Well the answer lies in the App Protection Policy (APP). Conditional launch settings validate aspects of the app and device prior to allowing the user to access work or school account data, or if necessary, remove the work or school account data. APP consists of many conditional launch parameters and I am going to cover 2 scenarios for Android and iOS OS platforms.

APP Conditional Launch using Manufacturer

Let's say an organization wants to restrict MAM enrollments against Samsung BYO devices only. This can be achieved by configuring the Device Manufacturer(s) setting under Conditional launch as shown below -


You can either block access against non-specified manufacturer name or initiate a wipe of corporate data automatically.

When a user tries to access corporate data using a non Samsung device, the access will be blocked and user will see a message similar to the one shown below -


APP Conditional Launch using OS version

Just like the manufacture setting, OS versions can be used for restricting access. This is typically handy if organizations consider certain OS patch versions to be vulnerable and want the end users to update their devices before allowing access to company data. In the example below, I am setting the minimum OS version to be iOS 17.0 and the action as 'Warn' letting the end user know about the minimum requirement policy laid down by the organization. As an action, one can also set to 'Block' or 'Wipe' data as shown below -


When a user tries to access corporate data on an iOS device running an OS version lower than the one specified, then they will be warned to update as shown below -


Well, there you have it. Even though, the settings covered in this blog post have been around for some time, the fact I only got to use them now and also how little I have come across them being used in the wild, I decided to quickly cover my experience and the importance of using conditional launch settings in MAM based enrollments. Hope it helps. Until next time..

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"){              ...
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. $P...
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 st...
Read more