The official Microsoft 365 Certified: Endpoint Administrator Associate syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Add devices to Microsoft Entra ID
Microsoft Entra join suits organization-owned devices that sign in with a work account and are managed only through MDM; Microsoft Entra registration covers BYOD with a personal sign-in; hybrid join keeps the on-premises domain join for Group Policy or apps that use machine authentication. Entra join doesn't support Sysprep imaging or Home editions.
Plan your Microsoft Entra join deployment ↗What are Microsoft Entra registered devices? ↗
Windows devices join Microsoft Entra ID through self-service in OOBE or Settings, Windows Autopilot, or bulk enrollment with a provisioning package. In self-service, the joining user becomes the primary user and a local administrator by default; the device registration policy controls who may join devices and who becomes a local administrator.
Plan your Microsoft Entra join deployment ↗Manage devices in Microsoft Entra ID using the Microsoft Entra admin center ↗
Microsoft Entra registration gives BYOD devices an identity without requiring a work account to sign in: on Windows from Settings or when opening a work app, on iOS and Android with Company Portal or Authenticator, and on macOS with Company Portal. Registration isn't Intune enrollment, and the maximum number of devices per user is controlled in Microsoft Entra ID.
What are Microsoft Entra registered devices? ↗Manage devices in Microsoft Entra ID using the Microsoft Entra admin center ↗
Intune uses Microsoft Entra security groups, assigned or dynamic. Device rules evaluate only device attributes (deviceOSType, devicePhysicalIds with [ZTDId] or [OrderID], enrollmentProfileName, deviceTrustType, deviceOwnership with the value Company) and are written in the text box; they can't mix users and devices. For Intune-only targeting, consider assignment filters.
Manage rules for dynamic membership groups in Microsoft Entra ID ↗Add groups to organize users and devices for Microsoft Intune ↗
Enroll devices to Microsoft Intune
Intune offers device platform restrictions (platform, OS version, manufacturer on Android and personal ownership) and device limit restrictions, each with a default policy that applies until you assign a higher-priority one. They affect only user-driven enrollments and aren't a security control. Corporate identifiers mark devices as corporate-owned before they enroll.
Overview of enrollment restrictions ↗Add corporate identifiers to Intune ↗
Windows automatic enrollment enrolls devices in Intune when they join or register in Microsoft Entra ID, based on the MDM user scope (None, Some or All). It's used with BYOD, bulk enrollment, Group Policy for hybrid joined devices, co-management and Windows Autopilot. The MDM URLs are left at their default values.
Enable MDM automatic enrollment for Windows ↗Windows device enrollment guide for Microsoft Intune ↗
For personal iPhones and iPads, Intune offers device enrollment with Company Portal or on the web, which manages the whole device, and account driven user enrollment, which separates work data and needs a service discovery file on the domain. On personal Macs, users install Company Portal from Microsoft's package and approve the enrollment profile.
iOS/iPadOS device enrollment guide for Microsoft Intune ↗macOS device enrollment guide for Microsoft Intune ↗
Android Enterprise offers personally owned work profile (BYOD), fully managed (one user, work only), dedicated (userless kiosk, optionally with Entra shared mode) and corporate-owned with a work profile. Corporate profiles generate a token and QR code and require a factory reset. For enrollment failures, check Conditional Access that requires compliance and which methods each Android version supports.
Android device enrollment guide for Microsoft Intune ↗Enroll Android Enterprise dedicated, fully managed, or corporate-owned work profile devices in Intune ↗
Automated device enrollment (ADE) connects Intune to Apple Business (formerly Apple Business Manager) through a token: download the Intune public key, create the MDM server in Apple, upload the .p7m token and assign devices. Set a default enrollment policy early; changes to a policy apply only after the device is reset, except the device name template.
Set up an iOS/iPadOS ADE token in Intune ↗Set up automated device enrollment (ADE) for iOS/iPadOS ↗
Samsung Knox Mobile Enrollment and Google zero-touch enrollment enroll corporate Android devices (dedicated, fully managed or with a work profile) when they're turned on. With Knox, the Knox Admin Portal profile must include the Intune token in Custom JSON data; with zero-touch, devices come from an authorized reseller and the configuration carries the token in the DPC extras or is linked from Intune.
Automatically enroll devices with Samsung Knox Mobile Enrollment ↗Enroll Android Enterprise dedicated, fully managed, or corporate-owned work profile devices in Intune ↗
Implement identity and compliance
Intune RBAC combines built-in roles (such as Intune Role Administrator, Policy and Profile Manager or Help Desk Operator), custom roles with specific permissions, and role assignments with admin groups, scope groups and scope tags. Windows 365 adds Cloud PC Administrator and Cloud PC Reader, and custom Cloud PC roles are created in the Intune admin center.
Role-based access control (RBAC) with Microsoft Intune ↗Windows 365 role-based access ↗
In Intune, roles define what an admin can do and scope tags define which objects the admin sees. A role assignment combines members, Scope (Groups) and Scope (Tags); objects an admin creates inherit that admin's tags, and an assignment with no tags sees every object. The Intune Administrator Microsoft Entra role ignores scope tags, and Windows Autopilot devices do not support them.
Use role-based access control (RBAC) and scope tags for distributed IT ↗
Intune multi admin approval uses access policies, one per resource type (apps, compliance, settings catalog, device actions, roles, scripts and tenant configuration), so a different account approves each change. The approver group must be a security group assigned to an Intune role; nobody approves their own requests, and the requestor selects Complete after approval.
Each platform needs its own Intune compliance policy, and the tenant-wide compliance setting decides whether a device with no policy is marked compliant or not compliant. The built-in Mark device noncompliant action is scheduled at zero days; delaying it creates a grace period, and other actions send email, lock the device or add it to the retire list.
Use compliance policies to set rules for devices you manage with Intune ↗Configure actions for noncompliant devices in Intune ↗
Intune reports compliance status to Microsoft Entra ID, and the Require device to be marked as compliant grant control uses it to allow or block access. Create the compliance policy first, exclude emergency access accounts and start in Report-only; the control doesn't block Intune enrollment and can be combined with MFA through Require one of the selected controls.
Require device compliance with Conditional Access ↗Conditional Access: Grant ↗
Intune offers a tenant-wide Windows Hello for Business policy that applies when devices enroll, including through Windows Autopilot, with settings such as a required or preferred TPM, PIN complexity and biometrics. For specific groups of enrolled devices you use the Account protection policy or the settings catalog; if two policies control the PIN, the Windows Hello for Business policy wins.
Configure Windows Hello for Business on devices when they enroll with Intune ↗
Intune configures Windows LAPS through the account protection profile: password requirements, scheduled rotation and backup to Microsoft Entra ID or Active Directory, never both. Microsoft Entra joined devices need LAPS enabled in the Entra device settings; viewing passwords requires Entra permissions, and manual rotation requires a custom Intune role.
Microsoft Intune support for Windows LAPS ↗Windows Local Administrator Password Solution in Microsoft Entra ID ↗
The Local user group membership profile in account protection manages the built-in Windows local groups through the LocalUsersAndGroups CSP. Add (Update) and Remove (Update) keep unspecified members while Add (Replace) replaces them and wins over Update; the Users selection works only for Microsoft Entra join, while Manual, with a SID or domain\user, also works for hybrid join.
Account protection policy for endpoint security in Intune ↗Policy CSP - LocalUsersAndGroups ↗