After "transporting" to 5.0 I noticed that some of my 3rd party apps permissions were not able to be manually set such as Google Mobile App and Shazam.

This occured only after assigning a software configuration in the 5.0 world, which now includes a "App Control Policy for Unlisted Applications", i.e. any 3rd party software besides the one in your s/w config.

I chose the default "Standard Unlisted Optional" which seems to be what one needs, it doesn't seem like it would lock anything down when looking at the policy details. Some settings are just set to Prompt instead of Allow except for Browser Filters API and Event Injector which are Disallowed. No problem, my unlisted apps don't need those. But still, no go on modifying app permissions, such as Shazam, which won't run unless it sees they are set the way it wants, and Google Mobile App, in which certain functions like voice control just won't work.

After some experimentation I found that each of the settings that the 3rd party apps are trying to set to "Allow" on the device, also need to be set to "Allow" in the ACP for Unlisted Apps, in order for the apps to update them successfully on the device.

So basically it appears that BES 5.0 causes the device to be more locked down if you choose the default ACP for unlisted apps when setting up a software configuration. I have a feeling this is going to cause quite some confusion.

Wasn't able to make it to WES this year, was this covered in detail (or at all) in any of the sessions / training?