How To Fix AWS Outlook Autodiscover Failing for New WorkMail Mailboxes

Select Language:

If you’re having trouble connecting new or recently recreated mailboxes in Outlook to your Amazon WorkMail setup in the us-east-1 region, you’re not alone. Your older mailboxes work fine because they connect through the legacy endpoint, but newer mailboxes need the new autodiscover endpoint to be properly configured.

Since you’ve already checked that your DNS record points to the correct new endpoint and have tested that it resolves correctly, but new mailboxes still won’t connect, here’s what you can do next:

First, make sure that your DNS setup is correct and that the autodiscover record is pointing to “autodiscover-service.mail.us-east-1.awsapps.com”. It sounds like it is, so double-check the DNS propagation and settings.

Next, verify that your firewall or network settings aren’t blocking access to this endpoint. Sometimes, security settings can prevent Outlook from reaching the autodiscover service, especially with new configurations.

Then, try configuring Outlook manually for a new mailbox. When adding a new account, choose the manual setup option and enter the server details explicitly, especially if auto-discover fails.

If manual configuration works, it’s a sign that the autodiscover process isn’t functioning correctly for new mailboxes. In this case, consider resetting the autodiscover service for your domain. This involves clearing any cached autodiscover data and refreshing the DNS records.

Lastly, contact AWS Support or your Microsoft Outlook admin, as there may be backend issues or CNAME routing problems affecting autodiscover for your new mailboxes. Providing them with the troubleshooting steps you’ve already taken will help speed up the resolution.

By following this process, you should be able to identify whether the problem lies with DNS, network, or Outlook configuration and take the proper steps to fix the autodiscover connection issues for your new mailboxes.