2.3. Implement Identity and Compliance
💡 First Principle: A tenant has two sets of keys. The admin keys open the admin center — who can change policies, wipe devices and read passwords. The device keys open company data — which devices and sign-ins are trustworthy enough to reach it. Least privilege governs the first, verified device health the second, and in both the safest design separates deciding from doing.
Why care? Device-estate breaches rarely need an exotic exploit; they come from an over-privileged admin account, a help desk operator who could wipe the wrong devices, a shared local administrator password, or a device that reached email without proving it was healthy. The controls that close those gaps: Intune role-based access control and Multi Admin Approval for the admin keys; compliance policies, Conditional Access, Windows Hello for Business and Windows LAPS for the device keys.
Think of a bank branch: staff badges set what each employee may do (roles) and which accounts they see (scope tags), big transfers need a second signature (Multi Admin Approval), the vault key changes after every use (LAPS), and the teller checks a customer's standing before paying out (compliance plus Conditional Access).
⚠️ Common Misconception: Because scope tags are configured alongside roles and visibly change what an admin sees, it's easy to believe a scope tag grants permissions. It doesn't: permissions come only from the role. A role assignment combines the role (which actions), members (who), scope groups (which users and devices they can act on) and scope tags (which objects they can see), and a tag never adds a right the role doesn't already contain.