Allow reconcile of conflicting service options across licensing plans
Assigning licenses for service options across license plans is buggy and unpredictable. E.g. You have enabled SharePoint Online (Plan 1) service option in a licensing plan that's assigned to a group via Azure AD. Project Online has SharePoint Online (Plan 2) and you'd like to assign the license to your Project Services Role Group. You can't because, it won't let you disable SP Plan 1 from the existing licensing plan and then you can't enable SP Plan 2 because SP Plan 1 is already enabled. Project Online demands that you use SP Plan 2. Basically, you're snookered. If this issue were handled correctly then I'd be able to reconcile the two. The whole point of group license assignment is surely to allow role based digital workspaces so it needs the flexibility to be fit for purpose for such a solution.
Eric Kool-Brown commented
Why can't the licensing code just compute the sum of the licenses and assign the highest of each product? It's just code, but the current implementation is completely broken. Why should paying customers have to pull out their hair to be compliant with MS licensing? Customers are trying to do the right thing but the licensing is an intractable mess!
Amen to this. We've even seen conflicts with SharePoint Online Plan 2 and SharePoint Online Plan 2 for EDU. Having to process these all manually to ensure no service disruption defeats the purpose of the flexibility group licensing is to provide. Please fix this Microsoft.
Exactly this. Dynamic group-based licensing in Azure AD has the power to solve a lot of the pain of using cloud-based licenses, and yet it can't sort out two versions of Sharepoint. Fix this.