We need GPO setting to block one word address bar search

%3CLINGO-SUB%20id%3D%22lingo-sub-1678901%22%20slang%3D%22en-US%22%3EWe%20need%20GPO%20setting%20to%20block%20one%20word%20address%20bar%20search%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1678901%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20enabled%26nbsp%3B%3CSTRONG%3EGoToIntranetSiteForSingleWordEntriesInAddressBar%20%3C%2FSTRONG%3Eand%20thought%20this%20would%20block%20single%20word%20search%20in%20the%20selected%20search%20engine.%20That%20is%20not%20the%20case.%3C%2FP%3E%3CP%3EThere%20should%20be%20a%20setting%20to%20block%20single%20word%20search%20from%20the%20address%20bar.%3C%2FP%3E%3CP%3EEven%20better%20if%20there%20was%20a%20way%20to%20split%20the%20bar%20into%20old%20school%20style%20url%20and%20separate%20search%20bar.%3C%2FP%3E%3CP%3EThe%20reason%20for%20this%20is%20that%20the%20one%20word%20searches%20leak%20internal%20server%20names%20etc%20to%20the%20search%20engine.%3C%2FP%3E%3CP%3ESuggested%20setting%3A%20%3CSTRONG%3EDisableSingleWordSearchInAddressBar%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eex.%3C%2FP%3E%3CP%3ECurrent%20behavior%3A%3C%2FP%3E%3CP%3E%22server123%22%20is%20typed%20in%20the%20address%20bar.%3C%2FP%3E%3CP%3EEdge%20tries%20to%20connect%20to%20the%20server%20but%20fails%20because%20the%20server%20name%20does%20not%20exist.%20Browser%20redirects%20this%20as%20a%20search%20to%20the%20default%20search%20engine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eexpected%20behavior%3A%3C%2FP%3E%3CP%3E%22server123%22%20is%20typed%20in%20the%20address%20bar.%3C%2FP%3E%3CP%3EEdge%20tries%20to%20connect%20to%20the%20server%20but%20fails%20because%20the%20server%20name%20does%20not%20exist.%20Browser%20returns%20404%2C%20site%20does%20not%20exist.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1678901%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAddress%20Bar%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EEdge%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Egpo%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESearching%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1681320%22%20slang%3D%22en-US%22%3ERe%3A%20We%20need%20GPO%20setting%20to%20block%20one%20word%20address%20bar%20search%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1681320%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F667763%22%20target%3D%22_blank%22%3E%40David421%3C%2FA%3E%26nbsp%3BHi%20David!%26nbsp%3B%20Thanks%20for%20the%20feature%20request!%26nbsp%3B%20I've%20contacted%20our%26nbsp%3B%3CSPAN%3EAddress%20Bar%20%26amp%3B%20Search%20Team%20regarding%20your%20suggestion.%26nbsp%3B%20Currently%20it%20is%20not%20on%20our%20roadmap%20to%20disable%20single%20word%20search%20as%20a%20fallback%20when%26nbsp%3Bthe%20policy%20%3CSTRONG%3EGoToIntranetSiteForSingleWordEntryInAddressBar%3C%2FSTRONG%3E%20is%20set.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThere%20was%20a%20previous%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fenterprise%2Fpolicy-needed-quot-go-to-an-intranet-site-for-a-one-word-entry%2Fm-p%2F837472%2Fhighlight%2Ftrue%23M289%22%20target%3D%22_self%22%3Ethread%3C%2FA%3E%26nbsp%3Bhere%20discussing%2Frequesting%20single%20word%20search%20for%20the%20policy.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EThe%20team%20is%20interested%20in%20gathering%20some%20additional%20data.%26nbsp%3B%20Can%20you%26nbsp%3Bshare%20some%20more%20insight%20from%20your%20end%20about%20why%20this%20specific%20scenario%20is%20necessary%20and%20if%20this%20is%20a%20deployment%20blocker%20for%20you%3F%26nbsp%3B%20Thanks!%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CEM%3E-Kelly%3C%2FEM%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1682520%22%20slang%3D%22en-US%22%3ERe%3A%20We%20need%20GPO%20setting%20to%20block%20one%20word%20address%20bar%20search%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1682520%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F757644%22%20target%3D%22_blank%22%3E%40Kelly_Y%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20customer%20is%20concerned%20that%20internal%20server%20names%20could%20be%20leaked%20to%20the%20search%20engine%20if%20typed%20miss%20spelled%20or%20if%20a%20server%20is%20temporary%20offline.%20So%20they%20cannot%20use%20Edge%20Chromium%20unless%20this%20feature%20has%20a%20disable%20option.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We have enabled GoToIntranetSiteForSingleWordEntriesInAddressBar and thought this would block single word search in the selected search engine. That is not the case.

There should be a setting to block single word search from the address bar.

Even better if there was a way to split the bar into old school style url and separate search bar.

The reason for this is that the one word searches leak internal server names etc to the search engine.

Suggested setting: DisableSingleWordSearchInAddressBar

 

ex.

Current behavior:

"server123" is typed in the address bar.

Edge tries to connect to the server but fails because the server name does not exist. Browser redirects this as a search to the default search engine.

 

expected behavior:

"server123" is typed in the address bar.

Edge tries to connect to the server but fails because the server name does not exist. Browser returns 404, site does not exist.

3 Replies
Highlighted

@David421 Hi David!  Thanks for the feature request!  I've contacted our Address Bar & Search Team regarding your suggestion.  Currently it is not on our roadmap to disable single word search as a fallback when the policy GoToIntranetSiteForSingleWordEntryInAddressBar is set.  

 

There was a previous thread here discussing/requesting single word search for the policy.  The team is interested in gathering some additional data.  Can you share some more insight from your end about why this specific scenario is necessary and if this is a deployment blocker for you?  Thanks! 

 

-Kelly 

 

Highlighted

@Kelly_Y 

 

The customer is concerned that internal server names could be leaked to the search engine if typed miss spelled or if a server is temporary offline. So they cannot use Edge Chromium unless this feature has a disable option.

Highlighted

@David421 Thanks for the additional details!  I've passed it on to our team.  We'll follow up if there are more questions or if there are any updates.  

 

-Kelly