“FAILED_TO_AUTO_DISCOVER_DOMAIN” error in Teams Admin Center

March 27, 2020 | by iaur | posted as Failure, Teams (formerly S4B)

Scenario

“Failed To Auto Discover Domain

  • You are getting the error message above and unable to access TAC (Teams admin center) as a result.
Failed To Auto Discover Domain
  • You are returned with a blank results when using this link on your browser (change the <yourdomain.com> to the troublesome domain)

Example 1:

Example 2: Working correctly (faceresionem.onmicrosoft.com)

Certainly, the problem could be related to an issue with the domain as described by “FAILED_TO_AUTO_DISCOVER_DOMAIN“. Further, below are the options you can choose from.

Use your initial domain.

A quick fix to access Teams admin center is to create a Global Administrator account that uses your Microsoft Online Direct Routing Domain (MODRD). Similarly, is to use an existing account that has your initial domain as its default.

To clarify, your initial domain is normally your organization name followed by “.onmicrosoft.com”. Please see this documentation for more details

Re-deploy Skype for Business Online services on your domain.

This shouldn’t be an issue in the first place. However, some administrator or end users tends to leave it as disabled as they weren’t planning to use the service at the time they were adding the domain to Microsoft 365. Hence, the error “Failed To Auto Discover Domain“.

In addition, I’ll suggest that you’ve gone through some other prerequisites beforehand. For instance, creating SIP and SRV records for Skype for Business online set other required sub-services. Therefore, save you from a lot of head ache in the long run.

Finally, to provision the service.

  1. Connect to Skype for Business Online PowerShell.

  2. Run the following cmdlets one at a time.

    Enable-CsOnlineSipDomain –Domain ‘ProblematicDomain.com‘
    Disable-CsOnlineSipDomain –Domain ‘ProblematicDomain.com‘
    Enable-CsOnlineSipDomain –Domain ‘ProblematicDomain.com‘

  3. After that, wait for an hour to propagate then run again this query to see if it is resolving to a value.

  4. Finally, if everything is in order. You can try to access again Teams admin center using a Global administrator with the troublesome domain.

Reference