Teams Phone Resource Account licenses for Microsoft 365 developer subscription

Gerry Pearson 25 Reputation points
2023-03-31T13:00:42.74+00:00

I am using a Microsoft 365 developer subscription (sandbox tenant) to develop PowerShell automation around the provisioning of Teams services. These tenants come with 25 DEVELOPERPACK_E5 licenses.

One part of this automation is the creation of Call Queues and Auto Attendants, each of which must have an associated Resource Account. These Resource Accounts must be appropriately licensed with Teams Phone Resource Account licenses. It used to be that I could use the existing DEVELOPERPACK_E5 licenses for this purpose. That is no longer the case.

In a standard, production tenant with E5 licenses you get some number of these Teams Phone Resource Account licenses for free. But in the sandbox tenant these licenses do not appear to be available. This is problematic as I am no longer able to completely test my automation in a developer sandbox.

Is there an alternative solution for sandbox tenants? Are there any plans to include Teams Phone Resource Account licenses in developer sandbox tenants going forward?

Microsoft Teams | Development
Microsoft Teams | Microsoft Teams for business | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Oktay Yildiran 0 Reputation points
    2023-05-08T12:12:49.0666667+00:00

    There is a workaround for continuing the testing of your automation. You can create a new user with an E5 Developer license and assign a phone number. Additionally, the phone number that should be assigned to the resource account can be assigned to the newly created user to facilitate this process. Then, in the Teams Admin Center, you can set up callforwarding to the Resource Account. This method should enable your automation to function properly.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.