1.1.2. The Intune Admin Center and Its Neighbors
💡 First Principle: Endpoint administration spans several portals because several teams own the decisions it touches — identity belongs to the identity team, threat response to security operations, Office servicing to the apps team. Knowing which team owns a decision tells you which portal holds the setting.
Most of your MD-102 work happens in the Microsoft Intune admin center, which manages enrollment, configuration, compliance, apps, endpoint security, updates, Windows 365 Cloud PCs and remote actions. But Intune constantly hands off to, or reads from, its neighbors:
| If the requirement is about... | Configure it in... | Examples from this exam |
|---|---|---|
| Enrolling, configuring, securing and updating devices; deploying apps | Microsoft Intune admin center | Enrollment restrictions, Autopilot, settings catalog, compliance, app protection, update rings, Remote Help |
| Device identity, groups and access decisions | Microsoft Entra admin center | Device settings (who may join), dynamic device groups, Conditional Access, the LAPS tenant setting |
| Threat detection, investigation and response on endpoints | Microsoft Defender portal | Defender for Endpoint onboarding status, incidents and alerts, device isolation, vulnerability management |
| Office (Microsoft 365 Apps) policies, servicing and inventory | Microsoft 365 Apps admin center | Cloud Policy, cloud update, Microsoft 365 Apps inventory and security update status |
| Cloud PCs | Intune admin center (Windows 365 node) | Provisioning policies, Azure network connections, custom images |
Some decisions genuinely live in two places, and the exam exploits that. Conditional Access policies are created in the Entra admin center even though the compliance status they check is produced by Intune. Policies for Microsoft 365 Apps can come from Intune (settings catalog or administrative templates) or from Cloud Policy in the Microsoft 365 Apps admin center. Defender for Endpoint is onboarded by an Intune policy but investigated in the Defender portal.
Permissions follow the same split. Intune has its own role-based access control — built-in roles like Policy and Profile Manager or Help Desk Operator, custom roles and scope tags — while Microsoft Entra roles such as Intune Administrator grant tenant-wide Intune rights. Phase 2 explains how the two systems combine.
⚠️ Exam Trap: "Create a Conditional Access policy in Intune" is a distractor pattern. You can reach Conditional Access from a link in the Intune admin center, but the policy is a Microsoft Entra object, and it needs Microsoft Entra ID P1 (or a plan that includes it, such as Microsoft 365 Business Premium). Intune compliance itself does not require Entra ID P1.
Reflection Question: A security analyst needs to isolate a compromised laptop and review the alert timeline, while you need to make sure the same laptop gets a stricter firewall policy. Which portal does each of you use, and why are they different?