Forum Discussion

Copper Contributor

Jan 17, 2018

Outlook error when doing a search

when doing a search "in current mailbox" or other I get an error "Something went wrong and your search couldn't be completed" It looks like there's a problem with your network connection Le...

exchange

woonks

Copper Contributor

May 13, 2020

AlexRomain

I blocked my internal DNS servers from resolving outlook.office365.com.

Various ways to do this, easiest is create an empty DNS authoritative zone outlook.office365.com to blackhole the dns requests.

Be warned, this may break some Outlook365 webmail functions. The download attachments function couldnt work due to unable to resolve attachment.outlook.live.net, which actually just a CNAME to outlook.office365.com.

But at least, your office outlook users will stop the persistent calls for support......

dztek79

Copper Contributor

May 14, 2020

Hey,
use AutoDiscovery paramter ExcludeExplicitO365Endpoint instead blocking via DNS.
Either via GPO (newest admx templates) -> User Template Outlook 2016 -> Account -> Exchange -> Disable Autodiscover (Subtype O365 Autodiscovery)
Or Registry:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\AutoDiscover or
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
DWORD:ExcludeExplicitO365Endpoint = 1

This also resolve the the acutal search problem since Version 2004 😉

Semyonoff
MCT
May 27, 2020
AlexRomain If you are saying about registry fix
DisableServerAssistedSearch
Make sure to copy its name without trailing space. Restart outlook then.
dztek79
Copper Contributor
May 15, 2020
Hi,
don't know why, but some clients apply these settings fast, some other very slow.
After the gpo/registry is set, it takes some time while outlook is open until it recognize the change.
Seems there must run the autodiscover procedure once...
AlexRomain
Copper Contributor
May 15, 2020
Hi,

Doesn't seem to work here 😞