We've configured Google as the default search provider through an Edge Recommended policy, which should let users change it while preserving their custom search engines. This setup worked for years, but after updating to Edge 154, address-bar searches can suddenly stop working. In edge://settings/search, the policy-configured provider appears as "----" and cannot be selected, even though it remains in the search-engine list. Selecting the built-in Google entry restores searching.
The problem is reproducible: the policy provider works on first launch or immediately after changing a policy value, but stops working after switching to another provider and then switching back. It also happens with plain search URLs, unique provider names, and unique keywords. There are no conflicting mandatory search policies or ManagedSearchEngines settings.
Has anyone else seen this behavior in Edge 154? Is there a way to default users to the built-in Google provider while still allowing them to change it and retain custom engines?
3 Answers
Microsoft support confirmed this as a known issue and said a fix is being worked on, but there is no ETA. The available workarounds are to have users select the built-in Google provider again, roll back to Edge 153, or make the provider mandatory. Making it mandatory may not fit environments that need to preserve user-selected engines. The issue was still present in Edge beta 155 at the time of the report.
Yes, this started for us with Edge 154, including when the same configuration is delivered through Intune. The provider still appears in the list, but after switching away and back it becomes "----" and no longer works. This looks like an Edge regression rather than a bad URL or policy configuration.
For now, selecting the built-in Google entry manually is the least disruptive workaround because it sticks and does not remove custom search engines. There does not appear to be a policy setting that both reliably selects the built-in provider and preserves the user's ability to change it while this bug is present.
We see the same pattern: it works initially, then breaks after the provider is changed and selected again. The policy continues to show as successfully applied.