Office Mobile App Config Policies

Iron Contributor

I noticed new documentation for App Configuration policies for the Outlook mobile app recently. The settings prompt my curiosity so I ran an experiment.


I applied the IntuneMAMAllowedAccountsOnly and IntuneMAMUPN  settings to Excel, OneDrive, PowerPoint and Word on iOS to see what the effect would be. My actions were as follows.


1) Create an App Config policy (Managed Device) for each app

2) Apply the following settings in each policy

  • IntuneMAMAllowedAccountsOnly String Enabled
  • IntuneMAMUPN String {{userprincipalname}}

3) Factory reset an iPhone and re-setup the phone with a fresh iTunes ID (to prevent inheritance of settings)

4) Enroll the iPhone with Intune

5) Push the apps to the phone as required apps

5) After enrollment open each app in turn


The behavior that I saw was that each app automatically configured a user account using the Azure AD account. I did not see the usual prompts to add an account.


I have attached a screenshot of the settings that I used.


Has anyone else experimented with Office mobile App Config settings? I would be interested to hear if there are any other undocumented settings that might be useful.

6 Replies

I was wondering if that behaviour with those Key Value Pairs would work on the other Office apps like Word, Excel etc. Thanks, I am going to test it out!

Hi Andrew,


I've been trying to use this functionality to prevent users from adding their personal cloud services to Word, etc and thus leak data but I haven't found them to be effective.


Were you able to block additional services/locations from being added to Word, etc after rolling this out?

The behaviour is a bit odd when you add other accounts. I could add other accounts but then got a huge error and the account got deleted.


If you want to block data loss in mobile apps then App Protection policies are the gold standard. You can add as many accounts as you like but data does not leak from the protected corporate account to another account, even within the same App.

Thanks Andrew.


Good point about the app protection policies for doing the bulk of the work in reducing the likelihood of data leakage.  In my case, I have app protection policies configured but was looking at how the app config policies could be used to further lock down COBO devices and thus make over-zealous security folk sleep at night. :)


I've found the behaviour to be a bit hit or miss, especially on devices already running Word, etc and configured with personal accounts.  Outlook, on the other hand, works perfectly; it removed all other accounts I had configured but the other apps retained the private accounts.  Hopefully, the functionality improves over the coming weeks.

OneDrive and Skype for Business on Android don't seem to support the Key Value Pairs of the other office clients for mobile. Another thing I noticed is Outlook app doesn't work with the Key Value Pair of IntuneMAMAllowedAccountsOnly enabled when using Exchange on-premises. That option is assuming Exchange Online mailbox is being used from what I can tell. Would be good to fix that for Exchange on-premises, so that we can lock Outlook down to just the organization provided mailbox.

Interesting.  I'll test it tomorrow with an on-premises Exchange environment I have access to and see if I get the same results.  Will report back.