Office 365 Autodiscover not working

Siraj Hydrose 10

After a Tenant to Tenant Migration Autodiscover is not working. Migrated from a Tenant with Azure Ad Connect synced to the new tenant using BitTitan. Autodiscover is publish via DNS Registrar and updated, but outlook is not connecting.

Error:

Attempting to send an Autodiscover POST request to potential Autodiscover URLs.

Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Test Steps

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com:443/Autodiscover/Autodiscover.xml for user user@domain.com .The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional DetailsAn error message was returned from the Autodiscover service XML response: <?xml version="1.0"?> <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response> <Error Time="20:34:28.4861487" Id="3560106202"> <ErrorCode>500</ErrorCode> <Message>The email address can't be found.</Message> <DebugData />

Glenn Van Rymenant 6 Reputation points

2024-04-28T10:10:13.1733333+00:00

Are you sure the email address is set correctly? Note that Outlook 16.0.6741.2017 and above has a feature called 'Direct Connect' which bypasses autodiscover altogether. So even if the autodiscover setup is incorrect, you should still be able to connect to the mailbox. (please check the address and whether Direct Connect is not disabled)
Loran Bruce 0 Reputation points

2024-04-29T01:24:04.6133333+00:00

We did a migration this weekend as well and are experiencing the exact same issue. Additionally, we can't preview or download attachments in OWA.
Glenn Van Rymenant 6 Reputation points

2024-04-30T09:14:30.7033333+00:00

Long shot, but you can query one of the endpoints used in AutoDetect, could you check if the output of the below cmdlet has discrepancies when compared to a domain/tenant where autodiscover is working as expected? (replace the email address and note that it has to be an existing address)

(Invoke-WebRequest -Uri 'https://prod-autodetect.outlookmobile.com/detect?services=office365,outlook,google,icloud,yahoo&protocols=rest-cloud,rest-outlook,rest-office365,eas,imap,smtp' -Headers @{'x-email'='glenn@vanrymenant.eu'})

One of the things I have run into during migrations is that when you migrate from a different platform (e.g.: Google Workspace), that this record is updated infrequently (according to MS support every 24 hours but last time it took 4 days to change) and that the provider remains on Google for a while. When migrated users open Outlook and enter their email address, Outlook will look for this record and propose setting up a connection to your Google mailbox, users then have to select the "Not google?" option in the prompt to open their Microsoft mailbox.
Noah Ma-MSFT 2,340 Reputation points Microsoft Vendor

2024-05-01T09:53:57.1766667+00:00

Just checking in to see if above information was helpful.

If the issue has been resolved, please mark the helpful replies as answers.
DC 5 Reputation points

2024-05-24T15:28:17.7433333+00:00
We are experiencing the same after deleting a domain from a tenant and adding it back to a different tenant. Outlook is unable to connect to the mailboxes.

Microsoft Connectivity Analyzer fails with error 500 'The email address can't be found.' when posting to https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml

Querying https://prod-autodetect.outlookmobile.com results in a code 204 (no content) for the email addresses on the affected domain (the same mailboxes return 200 ok for the onmicrosoft domain)

Mail flow is working fine with users receiving and sending mails via owa, however trying to open shared mailboxes returns

BootResult: accessDenied Back Filled Errors: Unhandled Rejection: Error: 500:undefined|Unhandled Rejection: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data:undefined|undefined:undefined|undefined:undefined
Jatin Patel 0 Reputation points

2024-05-24T21:25:12.7066667+00:00

Hi there, any luck with this? I’m in the same boat as you. Domain transferred to another tenant today and autodiscover does not work. Transferred almost 20 hours ago.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Niel Zanfardino 1 Reputation point

2024-06-04T16:11:02.5833333+00:00

Did this eventually start working for anyone? I am having the same issue after a tenant to tenant migration. Been almost 20 hours since adding the domain to the new tenant.
Steven Jones 5 Reputation points

2024-06-04T17:57:51.3233333+00:00

Does this resolve itself?

We are having the same issues. I have migrated 2 domains from tenant to tenant and one works fine while the other has no autodiscover entries. I have a ticket with support and they are assisting. Just waiting for a call back.
Niel Zanfardino 1 Reputation point

2024-06-04T20:35:41.8333333+00:00

Steven, any update from support? We submitted a ticket but have not heard back. We do these migrations often, first time it has taken this long for Autodiscover to update.
Terje Langvand 0 Reputation points

2024-06-06T05:46:51.8566667+00:00

We hade same issue, migrate email with bittitan, moved domain from one tenant to another and could not connect with Outlook.

Resolution: Turn off and save ‎Modern authentication‎, then turn it back on again. This enables the ‎Modern authentication‎ for the new accounts.

1 answer

Terje Langvand 0 Reputation points

2024-06-06T05:53:05.0433333+00:00

We hade same issue, migrate email with bittitan, moved domain from one tenant to another and could not connect with Outlook.

The DNS records was added automatically for the "new" domain so we removed them and added everything manually. May have done something but not convinced.

Ran Sara https://aka.ms/sara and did the Outlook tool. This noticed that there was a problem with Modern authentication‎ and seemed to fix it for the user. But did not fix for all users.

Resolution: Turn off and save ‎Modern authentication‎, then turn it back on again. This enables the ‎Modern authentication‎ for all accounts on the new domain.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

Office 365 Autodiscover not working

1 answer