EXO Device Mailbox Security Policy Vs Intune management policy

-

While working on a customer requirement involving implementation of Intune APP (App Protection Policy) on BYOD (Bring Your Own Devices), I came across an issue on Android devices where on accessing Outlook for Android, the end user was being asked to 'Activate device administrator' as shown below.

Having dealt with Exchange device mailbox policy in the past, I immediately knew what the issue was and thought of blogging about it to save others some time.

If you navigate to Exchange admin portal > Mobile > Mobile device mailbox policy, then you should see a policy that is present in every tenant by default and set as optional.


However, in case your users see the prompt to Activate device administrator, then chances are that either you have a separate custom policy created and assigned OR the default policy is modified requiring an encrypted device instead of being optional. As it was in my case.


So what is happening here?

One can use mobile device mailbox policies to manage many different settings. These include the following:

- Require a password

- Specify the minimum password length

- Allow a numeric PIN or require special characters in the password

- Designate how long a device can be inactive before requiring the user to re-enter a password

- Wipe a device after a specific number of failed password attempts

However, if you are configuring any of the above settings using Intune as well and if they do no match, then this will result in a conflict. To avoid such conflicts and the fact that Intune provides more features and granularity, it makes sense to only use Intune managed policies.

What is the fix? It is an easy one to begin with. Either make the default policy optional or remove the custom policy. 

Note: It is always better to test this out, so I will suggest to create another custom policy, assign it to a mailbox and test it against that. Once tested, you can go ahead and delete the custom policy and the assignment will revert to the default device mailbox policy.


That is all for now. 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"){                 $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