Forum Discussion
Solved
[Solution] Parallel // Provider Exchange & Office 365 // Autodiscovery issue
EDIT2: My apologies.. I took this in my feverish search for a solution as an offical support forum. I'm sorry. Thanks for reading and contribution as well.
EDIT --> THE SOLUTION!!!. // NEXT THING TO COME --> THE PROPER SPF RECORD 😉*
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover]
"EnableOffice365ConfigService"=dword:00000001
"ExcludeLastKnownGoodURL"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeHttpsAutoDiscoverDomain"=dword:00000001
AND you must be logged in with the Office 365 Tenant in your Office Suite
not sure what exactly the proper key for surpressing this wrong autodiscvoery behaviour is... 16.0 in path of registry for Outlook 2016 - funny is when I delete the keys.. and even reconfigure mailbox no autodiscovery popups are comming. Condition is that I'm logged in with the Microsoft O365 tennant which is connected to the Mailbox
The <domain> (DNS-record) is already in use for a Provider based Exchange solution. We have a subsidiary that wants to work almost independently.
goal: have a edit: "parallel scenario" John over O365 direct / provider exchange still using its autodiscovery service
(provider exchange and Office 365 Exchange) - DNS record could only be adjusted in that way that it doesn't interfere with full functionality of the Provider Exchange solution our Headquarter is using.
The problem:
autodiscover.<domain>.<tld> of the Provider based Exchange solution kicks in.
workaround 1 - edit IP in hosts for autodiscover.<domain>.<tld>:
edit hosts vor autodiscover.<domain>.<tld> so that Outlook get the right Konfiguration. As you see above the DNS of the <domain> should not interfere with full functionality for our HQ.
result of ping autodiscover.<domain>.<tld> showed the adjusted IP (autodiscover.outlook.com) but it didn't worked out.
nslookup autodiscover.<domain>.<tld> showed Provider Exchange solution - so it thought this old workaround did not work here..
workaround 2 - adjust autodiscover values:
Maybe this could be some part of the solution?
- SCP lookup
- HTTPS root domain query
- HTTPS Autodiscover domain query
- Local XML file
- HTTP redirect method
- SRV record query
- Cached URL in the Outlook profile (new for Outlook 2010 version 14.0.7140.5001 and later versions)
- Direct Connect to Office 365 (new for Outlook 2016 version 16.0.6741.2017 and later versions)
workaround 3: seemed promising
after I logged out with the Office 365 Account in Office which has the Mailbox connected and logged in again I somehow managed to get the login screen. Just seems like Outlook then connects somehow directly to Office 365.
but still some popups for credentials, and some autodiscovery popup from the provider exchange solution.
iOS Devices seems to use the or a direct method... there is no interference with the autodiscovery.<domain>.<tld>
Please help me find a stable and Poupfree solution.
Greetings,
Benjamin
Found it after 18 hours ;-) This was a very helpful link:
EDIT --> THE SOLUTION!!! / it only works when login with the tenant.. user@xyz.onmicrosoft.com or when you changed primary email to user@<domain>.<tld.> it is till working. -------> AND!!! Made some registry tweaks see below
not sure what exactly the proper key is... 16.0 stands for Outlook 2016 - funny is when I delete the keys.. and even reconfigure mailbox no autodiscovery popups are comming. Condition is that I'm logged in with the Microsoft O365 tennant which is connected to the Mailbox.
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover]
"EnableOffice365ConfigService"=dword:00000001
"ExcludeLastKnownGoodURL"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeHttpsAutoDiscoverDomain"=dword:00000001
From what I understood, your goal is not to have Exchange-Exchange Online hybrid configuration as it is usually understood. If you would build a real hybrid, you wouldn't need to worry about autodiscover at all.
Anyways, in your workaround 1, where did you change DNS record? Internal or external DNS? If they run on different servers, please double check that you have changed both records. It is also advisable to clear all DNS caches you might have (local computer, DNS server, etc.).
If you like to test whether the "workaround 1" works, you can also edit C:\Windows\System32\drivers\etc\hosts -file to add autodiscover record:
40.101.65.200 autodiscover.<domain>.<tld>
I got it working before I wrote my post (Headquarter still have the provider Exchange and we have the Office 365 Exchange) But still getting popups to enter credentials when Outlook Autodiscover (autodiscover.<domain>.<tld>) kicks in. Why does it kick in? Why does it do the stuff to me?
I knew before how to get Office 365 configured directly know even if autodiscover.<domain>.<tld> is pointing to a provider Autodiscover-Server - Workaround as above. DNS record should be untouched in that way that nothing is interfering with Headquarter Exchange. Maybe adjusting SPF properly.
It still seems to be a DNS issue. Your clients (Outlook) seems to be getting the wrong autodiscover record and therefore are prompted for credentials.
Have you tried Remote Connectivity Analyzer tools to check records, or SARA on your client PCs?
