Autodiscover conflict between cPanel and Microsoft 365

Autodiscover lets Outlook obtain the settings for an Exchange or Microsoft 365 account. If the domain's website is on cPanel and the email is with Microsoft, a response from the website can interfere with that discovery.

The symptom may be that Outlook suggests a local IMAP server, asks for a password repeatedly or never finishes adding an account that does work in Microsoft's webmail. Those symptoms have other causes too: you need to check which destination is responding.

Why it can happen

Depending on Outlook's version and configuration, discovery may query a path on the root domain before other alternatives:

https://example.com/autodiscover/autodiscover.xml

If that endpoint returns a valid local configuration, Outlook may use it before reaching the right service. Microsoft documents this conflict and recommends fixing the web hosting's response.

In a setup entirely on Microsoft 365, the domain wizard may ask for an autodiscover CNAME pointing to autodiscover.outlook.com. In hybrid Exchange, follow the topology your administrator specifies. Having that CNAME right does not on its own prevent an earlier incorrect response from the root domain.

What to check and report

Check where the mailbox is hosted and whether you can sign in to the provider's webmail. Give support the domain, the Outlook version, the error and the server it is trying to use. Do not include the password or a log containing tokens.

We can check whether the hosting responds wrongly to that path and adjust what it publishes where appropriate. Do not turn off HTTPS for the whole website or change its MX records to fix a configuration discovery issue.

Windows registry changes that skip parts of Autodiscover are specific, temporary workarounds, not a general setting to apply on every computer. After fixing the response, test again and review stored configurations if Outlook keeps using the previous destination.