Phones would be registered in Intune, because they’re running Android – and that means any ‘all user’ Android policy would apply. This problem also disappeared later and now I can create accounts on my primary domain – put it down to another portal issue. I believe this is because I’m running in hybrid mode, so Teams can’t create an account on my primary domain – changing the domain to then let me create the Resource Account. When creating a Resource Account used for Auto Attendant or Call queues, I was getting a very unhelpful error.

Configure call forwarding in Gateway (Pilot Users only that were being given a new number out of our normal number range).

Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity Set-CsOnlineVoiceUser -Identity -TelephoneNumber 61812341234 $Session = New-CSOnlineSession -OverrideAdminDomain

Form a machine with the Teams PowerShell Module installed:.

Move-CsUser -Identity –Target -MoveToTeams -Credential $cred -HostedMigrationOverrideUrl $url $url=' ' (different links here for different countries)

From Skype for Business Server Management Shell:.

These licenses are bought from and feed into Microsoft 365.

Add user to AD Group “Azure AD Licensing Telstra Calling for Office 365” as this allocates a Telstra Calling for Office 365 license.

The migration was from Skype for Business Server 2015 and Skype for Business 2016 clients with Enterprise Voice, moving users across to Microsoft Teams. I thought I’d document a few lessons learned in this migration.

Skype for business autostart registry