Within Intune I went and created a Windows 10 App Protection Policy.
I defined my Protected apps as you see above.
So the Required settings are as shown and utilise Windows Information protection (WIP). The idea is WIP is:
“Windows Information Protection (WIP), previously known as enterprise data protection (EDP), helps to protect against this potential data leakage without otherwise interfering with the employee experience. WIP also helps to protect enterprise apps and data against accidental data leak on enterprise-owned devices and personal devices that employees bring to work without requiring changes to your environment or other apps.”
After creating the policy I applied it to a test machine.
Most things worked as expected EXCEPT that I couldn’t use non-Microsoft browsers like Chrome! I kept getting a block message as shown above. if I removed the Application Protection policy then I could browse fine on non-Microsoft apps again. Clearly something to do with the policy was blocking Chrome browsing!
The root cause is the concept of enlightened apps in WIP.
“Windows Information Protection (WIP) classifies apps into two categories: enlightened and unenlightened. Enlighted apps can differentiate between corporate and personal data, correctly determining which to protect based on internal policies.”
As it turns out, third party browsers like Chrome are considered unenlightened apps. If you read a little bit further down that article you find the following table:
This explains why Chrome (unenlightened app) is being blocked because it is trying to connect via an IP address effectively. Ok, so now we know why, how do we fix the problem?
Turns out the fix is in the last column as highlighted above. We need to use the /*AppCompat*/ string!
To do this navigate to Advanced settings from the menu on the left. Then select the entry you should have there called Cloud resources as shown above.
Here you should see your Microsoft 365 SharePoint and OneDrive sites as shown above.
Add the string
to the end of the line. Ensure the little green tick appears on the right hand side. Select OK to close that blade and the Save to update the Advanced settings page.
If you now look closely on the Advanced settings page you will see the above information box alerting you to the need for the /*AppCompat*/ string if you want TLS by personal apps that connect directly to cloud resources via an IP. You can consider a third party browser unenlightened and therefore a personal app. Thus, it is telling us to do what we just did to allow third party browsers to connect to the Internet on machines where the policy is applied. Always read the configuration page eh?
Once you have saved the updated App Protection Policy and it has been applied to the devices, you should no longer be blocked when using third party browsers like Chrome and Firefox.