Cover of Microsoft Entra ID Fundamentals Field Guide
Microsoft Entra Field Guides

Microsoft Entra ID Fundamentals Field Guide

Microsoft Graph PowerShell, dynamic groups, and group-based licensing for bulk provisioning

This is the companion page for Microsoft Entra ID Fundamentals Field Guide. If the book is in your hands, start with the placement quiz: it tells you whether to start at Chapter 1 or skip ahead. The chapter map and the hardest SC-300 questions answered in full are on this page too.

Get the book on Amazon See where you are The hard set

What this guide covers

Most Entra ID problems are not bugs. They are gaps the portal will never warn you about. A P2 license sits unused because nobody set a user's Usage Location, the per-user country/region attribute Entra ID requires before it will assign a license. A dynamic group quietly turns into its own access control the moment it is built on an attribute the user can write. A Global Administrator elevates to Azure root scope and forgets to toggle it back. You open Identity Protection and get a blank page instead of an error, because the admin center will not tell you which plan you have before you try to use a feature.

The documentation covers all of this, scattered across dozens of pages that never quite connect. This book is the connected account: one practitioner's mental model of how the identity control plane behaves in production, with the failure modes named before you hit them. It treats Entra ID as the decision engine every sign-in passes through, not a user database with SSO bolted on, and it works the licensing maze, the object model, and the two control planes that never cross.

Every product specific is grounded against current Microsoft Learn and validated in a live Microsoft 365 E5 lab, so the limits and portal paths reflect what the product does today. You do not need a production tenant to follow along. A trial tenant and a single test device are enough to reproduce everything here. Revised against Microsoft Learn, September 2026.

Chapter map

  1. Microsoft Entra ID as the Identity Control Plane
  2. The Microsoft Entra Admin Center
  3. Tenant Fundamentals, Structure, Settings, and Branding
  4. Licensing, Free, P1, P2, Governance, and the Entra Suite
  5. Creating and Managing Users
  6. Groups, Security, Microsoft 365, Assigned, and Dynamic
  7. Custom Security Attributes
  8. Bulk Operations and Microsoft Graph PowerShell
  9. Group-Based License Assignment
  10. Device Identity and Join Types
  11. Entra ID Roles, Built-In, Custom, and Least Privilege
  12. Administrative Units and Scoped Delegation
  13. Entra Roles vs. Azure RBAC, Effective Permissions, and the Production Checklist

Appendices: PowerShell and Graph Quick Reference; Build a Lab Tenant; Production Readiness Checklist; One Monday Morning in the Lab Tenant.

Who it is for

This is for administrators and engineers who already run Entra ID and want the moving parts wired together rather than listed, for IT pros ramping onto the platform who need one coherent and production-focused reference, and for anyone studying the SC-300 certification who wants depth beyond exam cramming.

See where you are

7 questions from this guide's territory (3 easy, 4 medium), with the explanation after each. Nothing is stored and nothing is sent anywhere.

The rest of the Microsoft Entra Field Guides

One product per book, a lab build in every one, and a companion page like this one for each. The last card is the collection: every volume of this series in one book, so check it against what you already own.

  • Cover of Authentication and Conditional Access with Microsoft Entra ID
    Field guide

    Authentication and Conditional Access with Microsoft Entra ID

    A disabled method can stay live in a legacy MFA or SSPR policy, and a policy that ships without emergency access exclusions can lock out recovery and administrators.

  • Cover of Hybrid Identity and Global Secure Access with Microsoft Entra ID
    Field guide

    Hybrid Identity and Global Secure Access with Microsoft Entra ID

    An organizational-unit rename can silently delete synchronized objects.

  • Cover of Identity Governance with Microsoft Entra ID
    Field guide

    Identity Governance with Microsoft Entra ID

    Access reviews can miss post-snapshot provisioning, and PIM group permissions can take up to 24 hours to apply.

  • Cover of Workload Identities and App Registrations with Microsoft Entra ID
    Field guide

    Workload Identities and App Registrations with Microsoft Entra ID

    Software authentication should not depend on stored client secrets.

  • Cover of Microsoft Entra Field Guides: The Complete Collection
    The whole series in one volume

    Microsoft Entra Field Guides: The Complete Collection

    A Conditional Access policy can look stronger while never evaluating the user it was meant to protect. All five field guides in one volume.

    Kindle$29.99Get it on Amazon

Every Kindle book here has a sample on its Amazon page, about the first 10 percent of the book.

The hard set (1 question)

The hardest SC-300 question this guide publishes, not repeated from the placement quiz above: the answer first, why every other option is wrong, and the Microsoft Learn page behind it. The practice book holds the full bank.

A company must guarantee that Helpdesk Administrators and even tenant-level Global Administrators cannot reset the passwords of C-level executive accounts or read their BitLocker keys, without stripping those admins of their tenant-wide roles. Only a small, explicitly designated set of administrators should be able to manage the executive accounts. Which Microsoft Entra capability meets this requirement?

Correct answer: B. A restricted management administrative unit containing the executive accounts, with a role scoped to that unit assigned only to the designated administrators

A restricted management administrative unit protects specific objects so that only administrators explicitly assigned a role at the scope of that unit can modify them. Even tenant-level Global Administrators and Privileged Role Administrators are blocked from modifying the objects unless they scope themselves to the unit, which is an auditable event. Placing the executive accounts in a restricted management administrative unit and assigning the trusted administrators a role (for example, Authentication Administrator) at that scope meets the requirement without removing anyone's tenant-wide roles.

Why the other options are wrong:

  • A. Conditional Access governs sign-in access conditions, not which administrators may perform a password reset on an object. It cannot enforce this admin-scoping requirement.
  • C. A regular (non-restricted) administrative unit narrows a scoped admin's reach, but it does not block tenant-level administrators. A Global Administrator, or a Helpdesk Administrator with tenant scope, could still reset the executives' passwords. Only a restricted management administrative unit blocks tenant-level admins.
  • D. Privileged Role Administrator manages role assignments tenant-wide and does not restrict who can manage the executives' accounts. Assigning it to executives is both incorrect for the goal and a privilege-escalation risk.

Memory hook: Block even Global Admins from touching sensitive accounts, without removing their roles = Restricted Management AU. A regular AU does not stop tenant-level admins.

Microsoft Learn: Admin units restricted management

Exam prep? The SC-300 sampler scores you by topic and points you to the guide behind each miss.

Take the SC-300 sampler All 75 SC-300 sampler questions, with explanations