Getting App protection policies to work for the bundled Office app in iOS/iPadOS & Android in Intune

-
The not so new Office app was made 'generally available' in Feb 2020. Since then, Microsoft have already addressed the requirement for supporting App protection policies using Intune. As a matter of fact, I have been applying the policies myself for some time now, but every time I have worked on this, I felt that the details on the application of the policies are not that properly documented in Microsoft's official documentation and which is why I decided to blog about this now.

Unlike the traditional Microsoft office apps like Word, Excel, PowerPoint etc, Office app has been made available under the following categories -

For Android -

Office Hub – Meant to be installed on devices in China which is under the custom bundle id com.microsoft.office.officehub.

Office Hub [HL] – Meant to be installed on devices in the US which is under the custom bundle id com.microsoft.office.officehubhl.

Office Hub [ROW] – Meant to be installed on devices outside of the US and China which is under the custom bundle id com.microsoft.office.officehubrow.

This is how they show up in Intune.

For iOS/iPadOS -

Office - Universal app under the custom bundle id com.microsoft.officemobile. 

This is how the app will reflect in Intune.


Note: There have been instances where the Office app doesn't list for iOS/iPadOS. In such a case, you can add the custom bundle id directly as shown below.


However, in my case the app was already available in the list so despite adding it as a custom bundle id, it automatically reflected under Public apps (as you can make out from the warning message).

That's about it. Just add the apps shown above in your APP policies and you are good to go. You can verify in the APP report if the APP policies are applying or not.


If you are interested in learning about APP policies and the tier based data protection framework in Intune, then you can head over to my previous post Implementing App protection policies using Tier based Data Protection Framework.

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