2. Prepare Infrastructure for Devices (20–25%)
A device you can't identify, enroll or trust is a device you can't govern. Why care? Without these foundations every later policy fails silently: there is no device object to target, no management channel to deliver through and no health signal for Conditional Access to read. This domain builds those foundations: an identity in Microsoft Entra ID for every device, the right enrollment method for each platform, and the two kinds of trust everything else leans on — trust in the administrators who change the tenant, and trust in the devices that reach company data. It carries up to a quarter of the exam, and Autopilot, configuration profiles, app protection and endpoint security all assume a device that is already joined, enrolled and grouped.
Think of it as a building's front door. Reception records the visitor (the device identity), issues a badge of the right type (the enrollment method), and the guards decide whether that badge opens the finance floor (compliance and Conditional Access). Behind the desk, a separate system controls which staff may issue badges and change the door rules (roles, scope tags and Multi Admin Approval).
The trap that runs through the whole domain is choosing by platform instead of by ownership. The same iPhone enrolls through Apple Business Manager if the company bought it and through account-driven user enrollment if the employee did.
⚠️ Exam Trap: Ownership, not the operating system, decides most answers in this domain. If two options both enroll the right platform, the correct one is the method that matches who owns the device and how much control the scenario says the organization may have.