A service plan is one individual service inside a Microsoft 365 license SKU: Exchange Online, SharePoint, or Teams inside an E3 or E5, for example. Assignments can disable specific plans, which is how organizations grant a suite while withholding parts of it.
Plans, SKUs, and assignments#
A SKU is the purchasable product; its service plans are the services it bundles. Both direct and group-based assignments can carry a disabled-plans list, and the user's effective services are computed from all of their assignments together.
The merge rule is permissive: if any assignment enables a plan, the user has it. Disabling a plan in one group's assignment therefore guarantees nothing unless every other path agrees.
Why disabled plans cause confusion#
Disabled plans are invisible at a distance. Two groups assigning the same SKU with different disabled lists produce users whose effective services differ from either group's intent, and a per-user comparison is the only way to see it. This is one of the most common sources of it works for some users mysteries in Microsoft 365.
VisualizerEngine
Service plans in VisualizerEngine
Disabled service plans are tracked per user as part of conflict and duplicate detection, alongside the granting groups and their paths. When two assignments disagree, the disagreement is listed instead of discovered one support ticket at a time.