The behavior is consistent with Outlook using cached or automatically discovered settings from the previous host’s Autodiscover configuration rather than the new provider’s settings.
In similar cases, Outlook’s Autodiscover logic receives an unexpected or incorrect response from a web server and keeps reapplying the old server details. This can happen when the root domain or another endpoint still responds to Autodiscover requests with the old configuration. Other clients (Thunderbird, Gmail app, Samsung Mail) often use only the explicit IMAP/POP/SMTP settings entered, so they are not affected.
To resolve this, the authoritative fix is on the hosting/DNS side:
- Contact the current web/hosting provider for the domain.
- Ask them to ensure their web server is not responding to Autodiscover requests for the domain (for example, requests like
https://<RootDomain>/AutoDiscover/AutoDiscover.xml).
- Once the web server stops responding to those Autodiscover requests, Outlook will fall back to the correct Autodiscover endpoints and should stop reverting to the old server settings.
If the hosting provider cannot change this behavior, a documented workaround is to adjust Outlook’s Autodiscover behavior via registry so it ignores problematic Autodiscover responses (for example, excluding the HTTPS root domain and other paths). After applying those registry keys, a new Outlook profile is created and the account is added again so Outlook no longer pulls the old configuration.
Because registry edits are potentially risky (they affect how Outlook discovers accounts system-wide), they should be applied carefully and only as described in the documented workaround.
References: