Forum Discussion
ToMMeR
Aug 02, 2019Brass Contributor
Policy needed: "Go to an intranet site for a one-word entry in the Address bar"
For enterprise a policy like the one in IE called "Go to an intranet site for a one-word entry in the Address bar" is very needed. As an enterprise we have a lot of intranet sites and services usi...
- Aug 14, 2019
Thank you, ToMMeR, stesch79 and paf_skov for your feedback. I can appreciate those circumstances and your request.
We will look into adding a policy to make single-word queries navigate and I'll follow up on this thread with an update as soon as I have one.
Thanks again for giving us this important feedback and for describing your specific scenarios! It helps!Jared
JaredB81
Microsoft
Aug 30, 2019JaredB81
Microsoft
Aug 30, 2019Quick update. My suspicion upon reading Aaron Roma's response was that the published ADMX files are for Dev channel and above only, however this policy has not been published to the Dev channel yet (currently, it's only available in Canary).
I was able to confirm that a few moments ago. Unfortunately, this means testing will have to wait until the next Dev channel build and its accompanying ADMX update.
Please be on the lookout for those updates at some point next week (barring any unexpected issues). I apologize for the delay and I look forward to your feedback once you're able to test this.
- JaredB81Sep 04, 2019
Microsoft
Update: The latest Dev build is out and its accompanying Dev policy file contains GoToIntranetSiteForSingleWordEntryInAddressBar, so this policy is ready for you to try out.
Using gpedit.msc, you can find the policy under Computer Configuration > Administrative Templates > Microsoft Edge and it's Setting title reads, "Forces direct intranet site navigation instead of searching on single word entries in the Address Bar".
Now that you're able to test this, please test this out in your environments and let us know if this meets your needs.I'm particularly interested in feedback on the following:
- Does this policy satisfy the requirement originally stated in this thread? If not, how can we improve it?
- How does this policy interact with the other policies you enforce (for example, if you disable the default search provider or if you force deletion of history on exit as described).
- How your organization members respond to having this policy applied when they attempt to search for single-word entries or navigate to external websites with single-word domains (in environments where the default search provider is permitted and firewalls permit access to such domains).
Of course, I'd love to hear any other feedback you have related to this policy as well.
Thank you and hopefully this works for you this time 🙂Jared
- Omega47Sep 05, 2019Copper Contributor
Same result here. Would expect it to automatically fail-over to do a search per the configured search engine if the short-name can't be resolved.
- JaredB81Sep 06, 2019
Microsoft
AngelPRU, ToMMeR, and Omega47,
Thank you very much for testing so quickly and for already providing feedback! I'm glad to hear this largely meets your needs.
I've made a note about the request for a search fallback on timeout rather than the error message. I will discuss this with the team and we will look into it.
ToMMeR, have a great vacation and I look forward to any additional feedback upon your return!
In the meantime, if anyone else has additional feedback about this policy, I will continue to monitor this thread.
Thanks again,
Jared
- ToMMeRSep 05, 2019Brass Contributor
JaredB81
My preliminary tests have the same result as AngelPRU.
The policy does what it says, but it would be a much better user experience if it would do a search engine search for the single word if it is not resolved internally instead of ending in a 404/"Hmmm... can't reach this page".
The policy for Internet Explorer worked this way, and Edge should too in order to be really user friendly.I don't have time to do thorough testing with various search engine policies etc. right now as i am going on vacation tomorrow. But i will do more thorough testing when i get back in 2 weeks.
- AngelPRUSep 04, 2019Brass Contributor
FYI, quick test with DEV build 78.0.262.0 and the latest DEV Policy files succeeded. In my test, single-word URL appended the trailing forward-slash and navigated to a local intranet site, as requested.
If the site is not available, it displays a "can't reach this page" error. Multiple words default to a Bing search, as expected.
This would work, but it would be a better user experience it if worked like IE 11, where if it can't resolve the single-word URL on the local intranet it sends the request for the URL to the default search provider, similar to EdgeC's default behavior.We don't use the search provider or browser history deletion GPOs in our environment, so current implementation, although not ideal, would meet our needs.
Thank you for your continued support.