Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

1.1.2. Identity, Licenses, and Roles: The Three Gates

💡 First Principle: A user gets a feature only when three independent gates are all open — the identity exists and can sign in, a license includes the service plan and that plan is switched on, and policy permits it. Troubleshooting is just checking the gates in order.

Most "user can't use X" scenarios on this exam resolve to one of three gates:

The identity gate is Microsoft Entra: the account exists, is enabled, can complete the required authentication methods, and isn't blocked by a Conditional Access policy. The license gate is more subtle than "a license is assigned." A license is a bundle of service plans, and an admin can switch individual plans off — a user with a Copilot license whose Copilot service plan is disabled is licensed on paper and blocked in practice. Group-based licensing adds another wrinkle: it applies only to direct members of the licensing group, not to members of nested groups. The policy gate covers everything an admin can turn on or off afterwards: a Copilot setting scoped to certain groups, an agent blocked in the registry, a Teams meeting policy, a DLP rule.

Admin roles are the same idea applied to administrators. Microsoft's guidance is least privilege: give an admin the narrowest role that does the job — User Administrator for account work, License Administrator for licensing, Exchange, SharePoint or Teams Administrator for a workload, AI Administrator for Copilot and agent settings — and keep Global Administrator for the few tasks that genuinely require it. Roles can also be scoped: an administrative unit limits a role to a subset of users and groups, which is how a regional help desk can reset passwords for its own staff only.

⚠️ Exam Trap: "The license is assigned, but the user still can't use the feature" usually points to a disabled service plan, a nested-group assumption with group-based licensing, or a policy setting — not to a missing license. Don't pick "assign a license" when the scenario already says one is assigned.

Reflection Question: A help desk technician in the Paris office needs to reset passwords for Paris users only. Which two concepts from this section combine to make that possible without granting tenant-wide rights?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned