Skype for Business Certified IP Phones with Microsoft Teams

Quick update from my attempted test:

• I created an E5 test tenant and assigned my test domain.
• I created users, assigned licenses and voice enabled.
• I created a test distribution list.
• I obtained a domestic call plan trial.
• I obtained service phone numbers (this was done using the legacy portal).
• I created a call queue (in the legacy portal).

This is where I realized there has been a dramatic change. It automatically created a Resource Account and assigned the phone number I had assigned to the call queue in the legacy portal to the number. Resource accounts are a new option under Org Wide Settings. I looked at one of my customers Teams Admin Portal and noticed under Voice, that they had the option to create and manage Auto Attendants and Call Queues from the Teams Admin Center, without having to go to the legacy portal and the options are different. You can assign a resource account. My test tenant does not have these options, yet (nor do my other customers). Apparently the way AAs and CQs are managed and licensed has dramatically changed (yes, they now need to be licensed, if they are assigned a phone number). On the bright side, you can now use on prem phone numbers as service numbers with Direct Routing.

Reference:

https://docs.microsoft.com/en-US/microsoftteams/manage-resource-accounts?WT.mc_id=TeamsAdminCenterCSH

My testing is on hold until the test tenant I am using gets the updated tools for managing AAs and CQs (PowerShell commands don't even work, yet). My guess is this tenant has not seen the updates mentioned above, yet. Hopefully we will get them by the end of the week.

I deleted the call queue I had created in the legacy portal and was able to create and assign licensing and a phone number to a deliberately created resource account, but I cannot yet create or manage a call queue (or auto attendant).

I will post an update, when I have one.