Teams Admin FAILED_TO_AUTO_DISCOVER_DOMAIN

[Melo1983]

Hi everyone few days ago i buy one license of Microsoft 365 Business Basic for use Teams

I get this error when i try to connect Teams Admin center FAILED_TO_AUTO_DISCOVER_DOMAIN

In my dns server i put this records:

• sipdir.online.lync.com. (cname)
• webdir.online.lync.com. (cname)
• sipfed.online.lync.com. (srv)
• sipdir.online.lync.com. (srv)

The Domain is in a good integrity check 

Any ideas?

Thanks

[#2]

@Melo1983 

Hi, take a look at this - https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/failed-to-auto-dis...

Hope this helps?

[#3]

@PeterRising 

Yes i try, but i get this error in powershell command

import-module Skypeonlineconnector ok

$sfbsession = New-csonlinesession : adminuser@domain.com 

Get-CsOnlinePowerShellEndpoint : Remote server error: (404) Non Found.

In C:\Program Files\Common Files\Skype for Business

Online\Modules\Skypeonlineconnector\SkypeOnlineConnectorStartup.psm1:149 car:26

+ ... targetUri = Get-CsOnlinePowerShellEndpoint -TargetDomain $adminDomain ...

+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-CsOnlinePowerShellEndpoint], WebException

    + FullyQualifiedErrorId : System.Net.WebException,Microsoft.Rtc.Management.OnlineConnector.GetPowerShellEndpointCm

   dlet

[#4]

@Melo1983 

Please can you share screen shots of your attempts in PowerShell?

[#5]

@PeterRising 

[#6]

@Melo1983 

Sorry I don't see anything in your reply?

[#7]

@PeterRising Sorry!

Now?

[#8]

@Melo1983 

What permission does your O365 account have?  Do you have Global Admin rights?

[#9]

@Melo1983 

Give this a try - https://docs.microsoft.com/en-us/office365/enterprise/powershell/connect-to-all-office-365-services-...

[#10]

@PeterRising Yes my account is global admin and Teams Admin

I try, but i get the same error...

[#11]

@Melo1983 

OK, give this a try and see if it lets you connect;

Import-Module SkypeOnlineConnector

$userCredential = Get-Credential

$sfbSession = New-CsOnlineSession -Credential $userCredential

Import-PSSession $sfbSession -AllowClobber -Verbose

[#12]

@PeterRising 

Same error after this code

$sfbSession = New-CsOnlineSession -Credential $userCredential

[#13]

@Melo1983 

Have you tried this on more than one computer?

[#14]

@PeterRising @Melo1983 

The issue isn't restricted to Melo1983.  I'm having the same issue after creating a new tenant and adding that domain to the new tenant.  

I'm getting the same errors, and unable to manage Teams through Teams Admin console.
Tried from multiple machines, and same machines after reformat.

I do have an open case with Microsoft.  Waiting to hear back today after providing correlation token & tenant information.

[#15]

Update:

My issue has been resolved by working through the ticketing system and getting a Microsoft O365 support engineer to help troubleshooting.  It had been a week, and my users were stuck in the "Provisioning" stage:
https://admin.microsoft.com/Adminportal/Home#/teamsprovisioning

What worked for me:

I ran the following PowerShell as Admin:

Import-Module LyncOnlineConnector
$Session = New-CsOnlineSession –UserName ‘[your-global-admin]@yourdomain.com‘ –OverrideAdminDomain ‘[your-tenant-name].onmicrosoft.com’
Import-PSSession $Session

Enable-CsOnlineSipDomain –Domain ‘[yourdomain.com]‘
Disable-CsOnlineSipDomain –Domain ‘[yourdomain.com]‘

Enable-CsOnlineSipDomain –Domain ‘[yourdomain.com]‘

Paste the following into a browser:

https://webdir.online.lync.com/Autodiscover/AutodiscoverService.svc/root?Domain=[yourdomain.com]

(This initially didn't work for me.....I kept seeing an XML message which roughly translates to a 404).

# It may take some time to complete these changes on your tenant.  I left work at 5pm, and at 7am, everything was working. (including the URL).

[#16]

For anyone else having this issue...

After trying many of the recommended things here and elsewhere over the net, I was able to finally resolve the issue by logging into the Teams portal by using the default "domain.onmicrosoft.com" Global Admin account rather than my personal global admin account.

Try it out!