A township tries to purchase a Microsoft 365 add-on SKU for a few clerks without any eligible base Microsoft 365 license underneath. What typically happens conceptually?
Select an answer to reveal the explanation.
Short Explanation
An add-on is the sidecar, not the motorcycle. Without an eligible base license, there is nothing solid to attach those extra features to.
Full Explanation
Add-ons generally require an eligible base license; an add-on cannot stand alone as a complete replacement for the foundational suite entitlement. Municipal buyers who purchase only an add-on without a qualifying base will not get the intended complete productivity stack.
Add-ons do not automatically create a full Microsoft 365 E5 suite for every clerk. Add-ons do not replace Conditional Access policies so no base license is ever needed. Add-ons do not convert on-premises Active Directory into Microsoft Entra ID by themselves.
Exam caveat: a few standalone products exist in the catalog, but exam language about add-ons emphasizes dependency on eligible base licenses. Operational check: attempt to assign a known add-on to a user lacking an eligible base in a lab and confirm the admin center blocks or warns, reinforcing the prerequisite model. In municipal Microsoft 365 fundamentals scenarios, map the business need to the named capability, reject distractors from a different pillar, and verify the control or commercial setting in the admin or billing experience before reporting risk closed to leadership. In municipal Microsoft 365 fundamentals scenarios, map the business need to the named capability, reject distractors from a different pillar, and verify the control or commercial setting in the admin or billing experience before reporting risk closed to leadership.