question

sebastianhalbig avatar image
0 Votes"
sebastianhalbig asked sebastianhalbig commented

Teams Admin Center Autodiscover fails

Hey there,

I'm currently facing the problem that I am unable to access the Teams Admin Center in a freshly created tenant.

Error code: FAILED_TO_AUTO_DISCOVER_DOMAIN

There are at least 10 users with Teams licenses assigned. I also use an account with the "Global Administrator" role to access the Admin Center.

However, the solutions provided elsewhere by signing in via Powershell throws another error stating that "lyncdiscover.domain.onmicrosoft.com" could not be resolved.

I tried everything I could find with the different error codes but do not come to a solution.

Anybody here who has an idea what I can try next?

Best regards and thanks in advance.

office-teams-windows-itprooffice-skype-business-server-administration
· 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

sebastianhalbig avatar image sebastianhalbig ·

Does anyone have another idea?

I disconnected the custom domain for testing yesterday. Still no success. I think I might be deleting the whole thing and start over. For my testing tenant this might be ok but that doesn't really solve it for my customer's tenant.

Hope anyone produces another idea until tomorrow. If not, I need to look for alternatives.

0 Votes 0 ·

2 Answers

udara avatar image
0 Votes"
udara answered sebastianhalbig commented

Check FAILED_TO_AUTO_DISCOVER_DOMAIN error in Microsoft Teams admin center


· 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

sebastianhalbig avatar image sebastianhalbig ·

Unfortunately, this did not help by any means since I'm unable to connect via PS to the tenant as I stated in my original post.

0 Votes 0 ·
SharonZhao-MSFT avatar image
0 Votes"
SharonZhao-MSFT answered sebastianhalbig commented

@SebastianHalbig-0633,

Does anyone else have the global admin access? And could he login in Microsoft Teams admin center successfully?

Please note that when you connect to Skype for Business Online with PowerShell, it needs your account with the default domain.

It also recommends you try to specify the OverridePowerShellUri parameter in New-CsOnlineSession command.

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 7
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

sebastianhalbig avatar image sebastianhalbig ·

There are two global admins in summary. I tried to connect with credentials of both.

I also tried to connect via PS as mentioned in my original post. If you mean the parameter "OverrideAdminDomain", I tried this as well. However, when connecting with this parameter, the error changes from "404 not found" to "could not resolve remote-name lyncdiscover.domain.onmicrosoft.com".

0 Votes 0 ·
SharonZhao-MSFT avatar image SharonZhao-MSFT sebastianhalbig ·

@SebastianHalbig-0633
You could check if there is any related error message about Microsoft Teams in Office 365 admin center > Health > Service health.

0 Votes 0 ·
sebastianhalbig avatar image sebastianhalbig SharonZhao-MSFT ·

I checked the health center and there is no issue with teams currently. Also, the history tab does not show any issues related to this in the past.

However, I was able to activate guest access now in the client's tenant via the Office Admin center and its "Home" tab. The Microsoft Teams card did show, that Teams is not enabled for my organization, which changed now.

The Teams admin center still shows the same error but I will try to resolve this via PowerShell again.

0 Votes 0 ·
Show more comments