Policy needed: "Go to an intranet site for a one-word entry in the Address bar"

OliverS91 It still works in our organization, so it must be because of your custom DNS response

JaredB81 did this get reverted?

I had a request for this within my organisation and implemented expecting the search behaviour mentioned in the thread but it appears it is back to behaving like the original implementation.

Entering google changes the address bar to google/ and fails to google search instead.

entering whatisthemeaningoflife gives me a failed page rather than a search.

I checked the policy docs and even they make no mention of the search fallback. They still talk about single word searches failing.

Is this intended?

Edit: I think I've worked out why its not working, if its still working for everyone else. On a failed DNS request our orgs DNS responds with a custom response page. Will keep testing. I'll leave this here as a note that the docs (and ADMX description) have not been updated to reflect the search fallback.

JaredB81 With Dev 84.0.495.2 one-word-intranet has come back. Thanks folks.

ThiloLangbein, thanks for the clarification.  The policy did get into the template files but a change from Chromium upstream broke the implementation of the policy if configured.

The fix has been in Edge Canary for a few days and the latest Dev build has the fix as well.  Please test with the latest Dev build and let us know if you encounter any issues.  

Thank you and again, I apologize for the inconvenience this caused! 

JaredB81 Thanks. Policy sems to be inplace and is shown under edge://policy but it doesn't work in Dev84.

Thank you for the head's up, ThiloLangbein.  First, I hope you and everyone else in this community is safe and well.

The policy seems to have been omitted from the latest published ADMX and ADML files.  I'll look into why that took place and work to get the policy back ASAP.

I apologize for this inconvenience and I'll update this thread when I have an ETA for the policy's return to the administrative templates. 

Is this GPO broken in Dev V84?

Hi everyone,

Just a brief update that the search fallback behavior is now on by default (no command-line flag needed) if this policy is enabled in the Beta channel as Beta has reached version 81.

If you plan to deploy the Stable channel of Edge throughout your organization, this policy will include the search fallback behavior without any command-line flags necessary to enable it, when the Stable channel reaches version 81.

Please test this out in Beta and let us know if anything is not working as expected.

Thank you!
Jared

Hello everyone,

I wanted to post an update on the timing of the on-by-default state.  We are a little bit late to take that change into Edge 80 Beta and rather than rush it and risk that a regression makes it way into the  Stable channel, we are going to take the change into the Beta channel once Beta moves to Edge 81. 

This means that the full, end-to-end functionality of this policy as this audience has validated it, will still require a command line flag in the Stable channel until Stable moves to Edge 81.

As we are updating Stable channel with major releases every 6 weeks, the delay isn't very long, but I didn't want anyone to expect this when Stable moves to Edge 80, and be surprised that it was missing.

I apologize for the delay and I'll update this thread once the Beta channel has Edge 81.

Thank you,

Jared

ToMMeR, excellent! I'm very glad to hear that the fix for the no-trusted-certificate case is working as expected and that the other cases (dots, dashes, search fallback, etc.) continue to work as you expect.

Steve Whitcher and ToMMeR and to everyone else on this thread, we want to thank you! Thank you for spending time to test our Insider builds and to provide feedback.  While our team is committed to delivering a great experience, it is with your feedback that we are able to do so, particularly for cases that are specific to your organizations. 

As for which Stable release will contain this full end-to-end solution including the cert fix, by default, without any command line flags, we are aiming for the Edge 80 Stable release (so not the build we announced is going to the Stable channel when it first goes live next week, but the subsequent major Stable release which will follow it). 

We will have a build in Canary and Dev that removes the command line flag sooner than that however, so you'll be able to more easily test the cert fix and share it with other members of your organizations.  I'll update this thread once we've removed the flag and enabled the fix by default.

Finally, please keep any other feedback about the new Microsoft Edge coming!  Feel free to start new threads about other features/scenarios and if your feedback is about the Address Bar or Search, feel free to @ mention me.

On behalf of the Address Bar and Search team, thanks again and have a great weekend!