Avatar
Andrew Mojko
  • Updated

🔄 What Is Exchange Autodiscover?

Autodiscover is a service provided by Microsoft Exchange that allows email clients like Mailbird Next to automatically detect and configure your email server settings using just your email address.

If Mailbird Next tells you that Exchange autodiscover is missing or not configured correctly, or you see errors mentioning "autodiscover is not set up", "autodiscover not working", XML parsing errors, "Login Timeout 440", or in-app Error #32 / Error #33, the autodiscover service on your Exchange server either isn't reachable or is returning an invalid response.

⚠️ Note: This article covers on-premise Exchange servers. If you use Microsoft 365 (Office 365), Mailbird Next handles configuration automatically via OAuth 2.0 — you shouldn't see this error. If you do, see our Microsoft 365 OAuth 2.0 guide.

🔍 What's happening

Autodiscover is the service Exchange uses to automatically tell email clients where your mailbox lives. When it's misconfigured, Mailbird Next can reach the autodiscover endpoint but the response is malformed — unlike a "cannot be located" error, which means the endpoint can't be reached at all.

Common causes include:

  • The autodiscover endpoint returns an HTML login page (often "Login Timeout 440") instead of the expected XML response.
  • The SSL certificate on the autodiscover virtual directory is misconfigured.
  • Authentication settings on the autodiscover virtual directory are incorrect.
  • A reverse proxy or load balancer is intercepting autodiscover requests.
  • DNS records for autodiscover are missing or point to the wrong host.

🛠️ What you can do

If this is a work or school account

Contact your IT administrator and share the exact error message (including any Error #32 / #33 reference). They'll need to check the Exchange server configuration — this isn't something you can fix from the client side. The sections below are for administrators.

For administrators: validate autodiscover

1. Test autodiscover from a browser

Visit https://autodiscover.yourdomain.com/autodiscover/autodiscover.xml in a browser. You should be prompted for credentials and then see an XML response. If you see:

  • An HTML login page — authentication is misconfigured on the virtual directory.
  • A certificate warning — the SSL certificate needs to be replaced or include the autodiscover hostname as a SAN.
  • A 404 or timeout — the autodiscover virtual directory isn't published, or DNS/firewall is blocking the endpoint.

2. Run Test-OutlookWebServices (PowerShell)

On your Exchange server:

Test-OutlookWebServices -Identity: user@example.com -MailboxCredential (Get-Credential)
  • Replace user@example.com with a valid mailbox address.
  • All results should show Success. Any failure points to a specific misconfigured service.

See Microsoft's official documentation on Test-OutlookWebServices.

3. Test from Outlook (alternative)

If you have Outlook installed on a domain-joined machine, you can validate autodiscover end-to-end:

  1. Hold CTRL and right-click the Outlook icon in your system tray.
  2. Click Test Email AutoConfiguration…
  3. Enter valid email credentials, ensure only "Use Autodiscover" is checked, and click Test.
  4. Open the Log tab and look for: "Autodiscover to [...] Succeeded"

If that line is missing, the Autodiscover service is likely misconfigured.

4. Check the autodiscover virtual directory

Get-AutodiscoverVirtualDirectory | Format-List Identity, InternalUrl, ExternalUrl, *Authentication*

Verify the URL is reachable and that at least one authentication method matches what your clients use (typically Basic or Windows Integrated).

5. Check your SSL certificate

The certificate bound to IIS must include autodiscover.yourdomain.com as a Subject Alternative Name (SAN). If it doesn't, browsers and clients will reject the response.

6. Check DNS

Your public DNS should resolve autodiscover.yourdomain.com to your Exchange server (A/CNAME record), or publish an SRV record:

  • Type: SRV
  • Name: _autodiscover._tcp.yourdomain.com
  • Value: 0 0 443 mail.yourdomain.com (or the hostname your Exchange server is published under, e.g. autodiscover.yourdomain.com)

⚠️ DNS changes may take several hours to propagate. Allow enough time before retesting.

🛠️ Workaround: Manual EWS configuration

If autodiscover can't be fixed quickly (or can't be exposed publicly), you can configure Mailbird Next manually using your Exchange Web Services (EWS) URL:

  1. Add your account in Mailbird Next as usual.
  2. When you reach the settings screen, click Edit server settings.
  3. Enter the EWS URL in the Server URL field — typically https://mail.yourdomain.com/EWS/Exchange.asmx.

⚠️ URLs ending in /Microsoft-Server-ActiveSync, /OWA, or /EAS are not supported.

💬 Need more help?

If you're still having trouble, contact our Customer Happiness Team. Include:

  • The exact error message from Mailbird Next (and any Error # shown).
  • Whether this is on-premise Exchange or hosted Exchange.
  • Your Exchange server version, if known.

Related articles

Articles in this section