New Outlook for Windows supports Microsoft 365 work or school accounts, Outlook.com/Hotmail, Gmail, Yahoo, iCloud, and other accounts that connect by IMAP or POP. It does not support on-premises Exchange accounts, and unsupported accounts can show connection errors.
Since the same 3 accounts work in Classic Outlook, use this troubleshooting path:
- Confirm the account type in New Outlook
- In New Outlook, go to View > View settings > Accounts > Your accounts.
- Try adding the failing address again with Add Account.
- If the account is being treated like a shared mailbox, open it instead from Settings > Accounts > Shared with me > Add.
- If New Outlook shows an app password message
- Some non-Microsoft providers require an app password for Outlook, especially for certain IMAP or iCloud-style connections.
- Generate the app password on the mail provider side, then paste that app password into Outlook instead of the normal mailbox password.
- Check whether the domain is still returning bad Autodiscover results
- A known cause of setup failure is when the domain’s web hosting service responds incorrectly to Outlook Autodiscover requests after a Microsoft 365 or custom-domain mail change.
- In that case, the fix is to have the web hosting or web service provider stop responding to Autodiscover requests for the root domain.
- Work around stale Autodiscover data in Outlook
- Create a new Outlook profile and add one of the failing accounts there:
- Exit Outlook.
- Open Control Panel > Mail.
- Select Show Profiles.
- Select Add.
- Enter a profile name and select OK.
- Use the Add Account wizard to add the mailbox.
- In Mail, set Always use this profile to the new profile.
- This is the safest first step before registry changes.
- If the problem started after the previous Google Workspace change and still persists
- Outlook can keep using a last known good Autodiscover URL.
- A documented workaround is to set the registry value ExcludeLastKnownGoodUrl = 1 under:
-
HKEY_CURRENT_USER\Software\Microsoft\Office\<x.0>\Outlook\Autodiscover
- or
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\<x.0>\Outlook\Autodiscover
- For the custom-domain Autodiscover issue, another documented workaround is ExcludeHttpsRootDomain = 1 under the same Autodiscover path.
- Warning: registry changes can affect Outlook account discovery. Back up the registry first, then restart Outlook and try adding the account again.
- If New Outlook still rejects only those 3 accounts
- That points to a provider-side compatibility or Autodiscover problem for those specific mailboxes or the domain, not a general Outlook installation issue.
- Classic Outlook working is a valid workaround while the provider-side configuration is corrected.
References: