During the deployment of Teams Voice for a customer, I found myself in the following situation: when trying to assign the licenses to a group (called, with a lot of creativity, “Licensing – Microsoft Teams Phone Standard”) the Microsoft 365 interface returned an error (with not much of an explanation attached to that)
The customer is using “Microsoft 365 E3” licenses, in the old version that included also Microsoft Teams as an App
As a basic test, suspecting that the error was tied to a dependency from the Teams license, I tried to remove from the Licensing group all the users that had no E3 licenses. Then I tried with an empty group with no luck whatsoever.
To get a bit more information, I have tried using PowerShell / Graph with the Set-MgGroupLicense command
The result was the following error:
Set-MgGroupLicense : License assignment failed because service plan 4828c8ec-dc2e-4779-b502-87ac9ce28ab7 depends on the service
plan(s) 57ff2da0-773e-42df-b2af-ffb7a2317929,0feaeb32-d00e-4d66-bd5a-43b5b83db82c
Status: 400 (BadRequest)
ErrorCode: Request_BadRequest
So, I was correct in thinking that the problem was a missing service. 4828c8ec-dc2e-4779-b502-87ac9ce28ab7 (Microsoft 365 Phone System) depends on Microsoft Teams (57ff2da0-773e-42df-b2af-ffb7a2317929) as you can see at https://learn.microsoft.com/en-us/entra/identity/users/licensing-service-plan-reference
Next step has been assigning the licenses to the single users and that worked correctly.
My idea, so far, is that in the Set-MgGroupLicense command Microsoft has added a check to verify that a Teams add-on is available to the group but (at least in a scenario involving customer that bought licenses before April 2024) the whole thing does not apply.
I will have to check if a similar error happens for customers that bought the Teams add-on as a separate item.
