Be careful when copying and pasting the 'Value' data above in respect of the speech marks ('') as if they are wrong, you'll get a remediation error within Intune.

Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingWhitelist

Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~NativeMessaging/NativeMessagingBlacklist To use the legacy policies, add the following Blacklist and Whitelist in: Once this policy was updated to the new version or a whitelist entry added for the extension for the older policy version, it worked.ĮDIT: Please note that the above NativeMessagingBlocklist and NativeMessagingAllowlist are only supported in Chrome 86 and onwards. This was the original problem setting within Intune in the custom OMA-URI format with no whitelist set: You can either add in NativeMessagingWhitelist with your exceptions or use the newer Chrome policy of NativeMessagingBlocklist. Using this tool is quite easy just click on its icon when you find the right site, and it will provide you with a list of similar Google pages. One of those policies (which is now deprecated by Google) - NativeMessagingBlacklist with a wildcard (*) blocks access to the Native Messaging API's. To find more similar pages on Google search results, the Google Similar Pages chrome extension comes in need. We use Chrome CIS Level 1 security benchmarks that use ADMX ingestion (Chrome ADMX). I did try older versions of Windows 10 (1903 etc.) and this wasn't the issue. Hi and I managed after some lengthy testing, to get to the bottom of the problem for us.

Google chrome extension