Forum Discussion
Solved
Edge Chromium default search engine using Microsoft Edge - Policies
Hi everyone, I have been creating lots of Edge Chromium policies using: Microsoft Edge Browser Policy Documentation | Microsoft Docs I managed to configure everything to the required setting...
Ivooo ‘This policy is blocked - its value will be ignored.’ means, that Edge has not recognised your device as AD-Joined or MDM-Managed.
I'm not familiar with "Azure AD-Joined" devices, but as I understand this technology no GPO's are deployed or assigned onto "Azure AD-Joined" devices, so you would have to use MDM to configure their Policies.
It seems that the policy's do indeed generate some errors, not very useful ones I must say. DefaultSearchProviderEnabled is ignored because ‘This policy is blocked - its value will be ignored.’. The other policy’s are ignored because the default search provider is not enabled, see screenshot.
Most of my other policy's are accepted except for a few.
Microsoft states:
"This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain, Windows 10 Pro or Enterprise instances that enrolled for device management, or macOS instances that are that are managed via MDM or joined to a domain via MCX.."
I'm running Windows 10 Enterprise and the device is Azure AD joined, so this should work right?
Ivooo ‘This policy is blocked - its value will be ignored.’ means, that Edge has not recognised your device as AD-Joined or MDM-Managed.
I'm not familiar with "Azure AD-Joined" devices, but as I understand this technology no GPO's are deployed or assigned onto "Azure AD-Joined" devices, so you would have to use MDM to configure their Policies.
- That's incredibly disappointing of Microsoft to exclude their cloud based users like this, so I would have to buy Intune in order for me to configure something as simple as a default search engine... Too bad, I was enjoying the new Edge so far, back to Chrome it is.
