MicrosoftThought I would weigh in here. I have been participating in another forum here https://community.spiceworks.com/topic/2271628-outlook-2019-search-something-went-wrong?page=1 I am spicehead-c6dzn over there. I have been tracking this problem since May 6th since one of my clients reported it. They are running Exchange 2013 CU23 on-premises and Windows 10 Pro workstations with retail Office 2019 Click-To-Run. So no Office365 - Microsoft Accounts. Exchange 2013 is also using FAST search and is affected.
The following CTR builds are affected 12730.20236 - 12730.20250 - 12730.20270
Out of all the workarounds that have been proposed. ExcludeExplicitO365Endpoint mentioned by dztek79 is in my opinion the best work around for my clients setup. Thanks dztek79! I like that it can be rolled out using GPO if you have the latest ADMX templates. I like that it also fixes another potential problem with AutoDiscover.
However after extensive testing, I have determined that only one of the registry paths works for me. I am not sure why. I applied the registry changes via manually via regedit. I followed abdias_ruiz advice to apply the change wait and restart Outlook. I also tried logoff/logon and rebooting the machine just to make sure. This is the one that works for me. It would be the one applied via GPO, did not require reboot, logoff starting/restarting Outlook.
Path: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\AutoDiscover
DWORD: ExcludeExplicitO365Endpoint
Value: 1
abdias_ruiz thanks for your work on this! I suspected the patched version will be available very soon. I am wondering if the above registry change prevents Telemetry data being sent to Microsoft 
. You mentioned earlier that was involved. Not sure what is being transmitted. Perhaps search queries? Please advise.
