This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 97%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
Hi
We have an on-premise Exchange server. The users are running Office 365 and up to a few days ago, Outlook was working fine and the users were connecting to their local Exchange mailboxes.
Now they are disconnected from their mailboxes and are getting a prompt to enter an account to reconnect to it. However, their domain account never gets accepted.
In the past if we created a new Outlook profile it would automatically find the Exchange mailbox and connect. However, now they get the prompt to enter the account to use autodiscover.xml.
Before this occurred, we did not change anything on the Exchange server or in the local Windows DNS Manager.
We have tried a number of troubleshooting steps but none have been successful.
We have even added to the registry path "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover" the DWORD (32-bit)Value with the name ExcludeExplicitO365EndPoint and gave it the value 1.
What could be causing this behaviour?
Regards,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi @GIC-AUA ,
I want to know if you create a new profile with only one on-premises mailbox, will this issue persist?
If yes, please use ExRCA to check if it can connect to Exchange server successfully.
If Autodiscover is working and pointing to the correct server, You should be able to stop Outlook from checking Office 365 settings by setting both registry keys.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\office\16.0\outlook\autodiscover
DWORD: ExcludeExplicitO365Endpoint
Value = 1
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\outlook\autodiscover
DWORD: ExcludeExplicitO365Endpoint
Value = 1
Please restart the Outlook2016 client after you modify the registry and recreate the profile to see if it can works.
Hi @GIC-AUA ,
Thanks for your detailed information.
Do you have any websites running with the root domain(domain.com)?
If so , the website will take over the request of search for the Autodiscover URL.
Please following steps below to add the value ExcludeHttpsRootDomain will force Outlook to skip domain.com and go direct to Autodiscover.domain.com, and then see if it works:
1.open regedit.exe on the client computer and locate
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
2.add a DWORD value named ExcludeHttpsRootDomain and set its value data to 1
3.restart Outlook and check if you are able to configure the profile
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @GIC-AUA ,
It has been a few days and I am checking in to see how things are going on with this issue.
Does this issue have any updates?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 23%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDG%3C/text%3E%3C/svg%3E)
Exchange is a rhino on heat. I get a problem where i can connect only on my local LAN IP connectivity. soon as i switch my IP to my public IP address of my router it does not connect and tries to connect to office 365 online, clearly it is a DNS issue of some sought, mail flow, autodiscover works fine on my mobile and iphone even mac clients. when it comes to windows 10, 11, it just does not connect from a public IP and tries to connect to microsoft 365 online exchange, it needs to default to microsoft exchange on premise, regardless of LAN or WAN IP address. Any ideas?
Editing regedit is really bad idea i have found. How about DNS? SSL for autodiscover and fqdn domain name for 2. you need public IP for domain name in question for fqdn.com and SSL autodiscover "A" record for autodiscover.fqdn.com with SSL. fqdn.com should have "A" record of public IP. fqdn should have SSL binded as well in IIS, DNS, exchange ECP.
Exchange is a rhino on heat. I get a problem where i can connect only on my local LAN IP connectivity. soon as i switch my IP to my public IP address of my router it does not connect and tries to connect to office 365 online, clearly it is a DNS issue of some sought, mail flow, autodiscover works fine on my mobile and iphone even mac clients. when it comes to windows 10, 11, it just does not connect from a public IP and tries to connect to microsoft 365 online exchange, it needs to default to microsoft exchange on premise, regardless of LAN or WAN IP address. Any ideas?
My exchange works perfect on my mobiles, apple, samsung, OWA, macs, etc, except when i connect from a public IP anywhere then microsoft exchange does not work but i can connect using Microsoft Exchange Active Sync Client for outlook and that goes to my microsoft exchange on premise server. How to make exchange connect from anyIP with out being on the same LAN? 192.168.50.40 my windows desktop client public IP from ISP when on laptop, it fails to connect to exchange on premise and tries to connect to microsoft 365 online, i do not want this. when i switch back to my local IP LAN IP then exchange connects to my on premise server and functions normally. I guess this is fine for people in the office on the same LAN but when they are remote on their laptops then they should be able to connect just the same as if theyre on any IP across the world 4g wifi or any connection. Any one know how to fix this? Clearly it is a DNS issue with windows 2022 Server, Exchange 2019 DNS lookup addresses? As mentioned, i can connect to exchange great on the same IP. soon as i'm on another IP thats public IP on 4g then exchange bails and refuses to connect, i can connect to Microsoft Exchange ActiveSync and OWA, that works fine anywhere but why exchange client on windows dont work on any device away from the office, e.g. on 4g connection?
all the suggestions here are wrong to fix the problem. you should not have to edit a clients computer registery on every single machine to login to exchange server to on premise, that would be ridiculous on a large scale setup with exchange. It is an autodiscover error with DNS error to go with, I have had the same issue with my exchange server for months, i can login perfectly by Microsoft Exchange Active Sync - that works fine on all my clients with exchange server but not connecting via the Microsoft Exchange method, it always defaults to office 365, that is wrong. It needs to connect to your own domain setup with on premise exchange server. I assume it is DNS, Autodiscover and port 443. I have tried a number of fixes but how to just connect to on premise exchange server domain without the need to custom microsoft exchange server active sync connection. Ps. my mobile logging in perfectly fine on my iphone 14 pro max to exchange server, it is only relevant to exchange server problem and windows desktop client client in outlook client where DNS and autodiscover is not working correctly, how to fix this, please?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 98%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHH%3C/text%3E%3C/svg%3E)
Same issue here. OUTLOOK365 is a nightmare.
MS seems to have BAKED in ther own servers, and to hell with the rest of the world.
Outlook 2013 we were able to enter all the neccessary details about our hosted exchange (NOT MICROSOFT SERVERS) and it worked flawlessly.
Now with this new flavour, it's a joke. Outlook INSISTS on connecting to thier own servers. Even if we do get it to work, it sticks for less than 24 hours, the then somwhow, "AUTOMATICALLY" it switchs back over to 0ffice365.microsoft.com GARBAGE.
We don't use MS Servers, never have, never will. Get over it and fix this issue.
HUGE WASTE OF TIME WITH THIS PRODUCT.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 69%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPW%3C/text%3E%3C/svg%3E)
Are there any news related to the problem?
I have the exact same setup and therefore the same problem.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 1%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJO%3C/text%3E%3C/svg%3E)
I also started having this exact issue on 10/18/2023