SOLVED

Unable to switch to Teams-only mode

%3CLINGO-SUB%20id%3D%22lingo-sub-1728036%22%20slang%3D%22en-US%22%3EUnable%20to%20switch%20to%20Teams-only%20mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728036%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20to%20switch%20from%20Island%20mode%20to%20Teams-only%20mode.%20But%20the%20admin%20center%20is%20not%20accepting%20the%20setting.%20Why%3F%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-09-30%2010_32_37-Teams%20upgrade%20-%20Microsoft%20Teams%20admin%20center%20%E2%80%93%20Opera.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223009i19967B0FC31304DB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222020-09-30%2010_32_37-Teams%20upgrade%20-%20Microsoft%20Teams%20admin%20center%20%E2%80%93%20Opera.png%22%20alt%3D%222020-09-30%2010_32_37-Teams%20upgrade%20-%20Microsoft%20Teams%20admin%20center%20%E2%80%93%20Opera.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20screenshot%20shows%20one%20of%20my%20demo%20tenants.%20But%20I%20have%20the%20exact%20same%20issue%20with%20one%20of%20my%20prod.%20Tenants%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1728036%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1728087%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20switch%20to%20Teams-only%20mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728087%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33043%22%20target%3D%22_blank%22%3E%40Robert%20K%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ECould%20be%20an%20issue%20with%20the%20TAC.%20Try%20with%20Powershell%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblog.bardalen.no%2Findex.php%2F2020%2F05%2F25%2Fhow-to-upgrade-users-coexistence-mode-to-teams-only-using-powershell%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.bardalen.no%2Findex.php%2F2020%2F05%2F25%2Fhow-to-upgrade-users-coexistence-mode-to-teams-only-using-powershell%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELet%20me%20know%20how%20you%20get%20on.%20Hope%20this%20answers%20your%20question%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1728108%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20switch%20to%20Teams-only%20mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728108%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3BHaha%2C%20just%20when%20I%20was%20about%20to%20post%20this!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fgrant-csteamsupgradepolicy%3Fview%3Dskype-ps%23example-3--grant-policy-to-the-entire-tenant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fgrant-csteamsupgradepolicy%3Fview%3Dskype-ps%23example-3--grant-policy-to-the-entire-tenant%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1728308%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20switch%20to%20Teams-only%20mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728308%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%20This%20helped%20a%20lot.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EGrant-CsTeamsUpgradePolicy%20-PolicyName%20UpgradeToTeams%20-Global%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3Band%20got%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3EThis%20organization%20cannot%20be%20upgraded%20to%20TeamsOnly%20at%20the%20tenant%20level%20because%20there%20is%20an%20on-premise%20deployment%20of%20Skype%20for%20%20Business%20detected%20in%201%20or%20more%20of%20it%20sip%20domains%2C%20xxxx.yyy.%20Users%20can%20be%20individually%20upgraded%20to%20TeamsOnly%20using%20either%20Move-CsUser%20(if%20the%20user%20has%20an%20on-premises%20Skype%20for%20Business%20account)%20or%20Grant-CsTeamsUpgradePolicy%20(if%20the%20user%20is%20homed%20in%20Skype%20for%20Business%20online).%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20I%20tried%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E%24userlist%20%3D%20Get-CSOnlineUser%0Aforeach(%24User%20in%20%24userlist)%0A%7B%0A%20Grant-CsTeamsUpgradePolicy%20-PolicyName%20UpgradeToTeams%20-Identity%20%24User.SipAddress%0A%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20this%20worked%20for%20me.%20Case%20closed.%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1799004%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20switch%20to%20Teams-only%20mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1799004%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33043%22%20target%3D%22_blank%22%3E%40Robert%20K%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20need%20to%20make%20sure%20you%20don%C3%B8t%20have%20any%20wildcard%20DNS%20records%2C%20as%20the%20Teams%20upgrade%20experience%20will%20try%20and%20do%20a%20DNS%20lookup%20for%20the%20SfB%20on-prem%20Autodiscover%20records.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20can't%20remove%20the%20wildcard%20A%20or%20CNAME%20records%2C%20you%20will%20need%20to%20enter%20the%20Office%20365%20admin%20center%20and%20enable%20Skype%20For%20business%20services%20for%20your%20domain%2Cs%20and%20get%20the%20DNS%20records%20for%20Skype%20for%20Business%20Online%20setup%20in%20DNS%20so%20the%20Teams%20upgrade%20experience%20can%20then%20determine%20that%20you%20are%20not%20using%20Skype%20for%20Business%20on-prem.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20ask%20me%2C%20they%20should%20add%20a%20-Force%20switch%20to%20the%20PowerShell%20command%20%3B)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I tried to switch from Island mode to Teams-only mode. But the admin center is not accepting the setting. Why? 

 

2020-09-30 10_32_37-Teams upgrade - Microsoft Teams admin center – Opera.png

 

The screenshot shows one of my demo tenants. But I have the exact same issue with one of my prod. Tenants too.

 

6 Replies
Highlighted
Best Response confirmed by Robert K (Contributor)
Solution
Hi @Robert K

Could be an issue with the TAC. Try with Powershell

https://blog.bardalen.no/index.php/2020/05/25/how-to-upgrade-users-coexistence-mode-to-teams-only-us...

Let me know how you get on. Hope this answers your question

Best, Chris
Highlighted
Highlighted

@Christopher Hoard 

 

Thank you. This helped a lot.

 

I tried

Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Global

 and got

This organization cannot be upgraded to TeamsOnly at the tenant level because there is an on-premise deployment of Skype for  Business detected in 1 or more of it sip domains, xxxx.yyy. Users can be individually upgraded to TeamsOnly using either Move-CsUser (if the user has an on-premises Skype for Business account) or Grant-CsTeamsUpgradePolicy (if the user is homed in Skype for Business online).

 

Then I tried

$userlist = Get-CSOnlineUser
foreach($User in $userlist)
{
 Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity $User.SipAddress
}

 

And this worked for me. Case closed. ;)

Highlighted

@Robert K 

You need to make sure you donøt have any wildcard DNS records, as the Teams upgrade experience will try and do a DNS lookup for the SfB on-prem Autodiscover records.

If you can't remove the wildcard A or CNAME records, you will need to enter the Office 365 admin center and enable Skype For business services for your domain,s and get the DNS records for Skype for Business Online setup in DNS so the Teams upgrade experience can then determine that you are not using Skype for Business on-prem.

If you ask me, they should add a -Force switch to the PowerShell command ;)

Highlighted

@Michael MardahlAre you saying to remove the lyncdiscover and sip cnames? We have been using skype online only and the DNS entries look correct for our domain but we are using a wild card and are seeing this error. I don't want to remove the DNS entries if that isn't the fix. 

Highlighted

@kevinlause You don't need to remove the Wildcard. Just make sure, that the correct SIP-records are set, from the templates in the admin-panel in 365.

 

I had the same issue, where we couldn't switch to 'Teams Only':

- New tenant

- No prior SfB setup, hence no SIP-records in DNS.

- Wildcard on primary domain.

 

I added the SIP-records and I was then able to upgrade through the TAC.