Forum Discussion

Brass Contributor

Jan 17, 2019

Solved

Outlook 365 Outlook Install Does Not See Local Exchange Account

Just beginning our Office 365 deployment to the desktops and will migrate to the hosted exchange model after we've deployed the software. But we've run into one caveat. If we install Office 365 o...

office 365

VasilMichev
Jan 19, 2019
I wouldn't advise manual config, as while it's still technically possible, it hasn't been "supported" for a while. I do think I have an idea of what's causing the issue though - the new "Check for Office 365 as priority" step in the autodiscover process, which fires even before the SCP lookup does. The bad news is that the only way to disable this step is via registry changes: https://support.microsoft.com/en-us/help/3211279/outlook-2016-implementation-of-autodiscover

VasilMichev

MVP

Jan 19, 2019

I wouldn't advise manual config, as while it's still technically possible, it hasn't been "supported" for a while. I do think I have an idea of what's causing the issue though - the new "Check for Office 365 as priority" step in the autodiscover process, which fires even before the SCP lookup does. The bad news is that the only way to disable this step is via registry changes: https://support.microsoft.com/en-us/help/3211279/outlook-2016-implementation-of-autodiscover

ChrisHoardMVP

MVP

Jan 19, 2019

Ah ok. Vasil - do you know when this change came in? Was it recent? Since moving to the role I’m in I don’t manage migrations on a day to day basis anymore and in the later days these were typically to 365 as opposed to configuration back to local exchange so this scenario didn’t apply.

In that case it’ll would then be purging the existing profile and either adding an Autodiscover XML to the local machine modifying the registry settings or modifying the registry directly specifically

ExcludeExplicitO365Endpoint DWORD =1

Best, Chris

drawson
Brass Contributor
Jan 25, 2019
Hey Vasil, thanks for that link. Doing a little more digging and this one specific entry resolved this for us as Chris was eluding to.

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\outlook\autodiscover
DWORD: ExcludeExplicitO365Endpoint
Value = 1

Eventually finding that quick answer here as well: https://www.gothamweb.com/portal/index.php/knowledgebase/8/Outlook-bypasses-AutoDiscover-and-connects-directly-to-Office-365-mailbox.html

I'd also like to add that the addition of this one reg key was enough to resolve our issue. We didn't need to modify autodiscover.xml or the AutoD.user.xml after adding that.

Thank you Vasil and Chris! Much appreciated.