MD-102 · CHEAT SHEET
Microsoft 365 Certified: Endpoint Administrator Associate
Key concepts grouped by official exam weight.
Download as PDF (free, no sign-up)1. Prepare infrastructure for devices
20–25%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.
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
2. Manage and maintain devices
25–30%Deploy and upgrade Windows clients by using cloud-based tools
- Windows Autopilot with deployment profiles requires device registration, uses the ESP and supports pre-provisioning, self-deploying and hybrid join. Windows Autopilot device preparation needs no registration, does only Microsoft Entra join in user-driven or automatic mode, adds the device to an assigned group owned by the Intune Provisioning Client and installs Win32 and LOB apps together.
- User-driven mode associates the device with the user who signs in and supports Microsoft Entra join or hybrid join. Pre-provisioning splits the process: a technician applies device-targeted content and reseals the device, then the user finishes. Self-deploying asks for no credentials, suits kiosks and shared devices, supports only Microsoft Entra join and, like pre-provisioning, needs physical TPM 2.0 with attestation.
- In a Microsoft Entra join deployment profile, Apply device name template uses %SERIAL% for the serial number and %RAND:x% for random digits, and a name can't be all numbers. Hybrid join only offers a prefix in the Domain Join profile, and with device preparation the template requires associating the device with the tenant.
- To deploy with Windows Autopilot you register the hardware hash (through the vendor, Get-WindowsAutopilotInfo or a CSV), build a dynamic group with rules such as [ZTDid] or [OrderID] for the group tag, and assign the profile. If two profiles target the same group the oldest wins, and hybrid join requires the Intune Connector for Active Directory and a Domain Join profile.
- The Enrollment Status Page (ESP) shows provisioning progress and can block device use until required apps and profiles are installed. Intune applies the highest-priority profile assigned to the device first, then the user's, and otherwise the default profile; with a selected apps list, the ESP only waits for those blocking apps.
Plan and implement device configuration profiles
- For Windows, Intune offers the settings catalog, templates and imported administrative templates built from custom or third-party ADMX and ADML files, which must be imported respecting their namespace dependencies. Group Policy analytics imports GPOs exported as XML, shows which settings MDM supports and can migrate them to a settings catalog policy.
- For Android Enterprise, device restrictions profiles (templates or the settings catalog) control corporate-owned devices and the work profile of personal devices. On dedicated and fully managed devices, kiosk mode runs one app or several through Managed Home Screen, and those apps must be required and assigned; in the work profile, clipboard and data sharing between profiles are controlled.
- iOS/iPadOS device restrictions profiles use Apple's restrictions, and many settings need devices supervised through automated device enrollment. Kiosk mode (App Lock) and the show or hide apps list require supervision; the restricted apps list only reports, and to stop an app from running you use the settings catalog.
- On macOS, Intune offers the settings catalog, the device features and device restrictions templates and custom profiles built from .xml or .mobileconfig files, which accept device tokens in double curly brackets. Privacy preferences pre-approve or pre-deny app access to protected resources, and the Microsoft Entra ID SSO app extension needs the Company Portal to deliver the plug-in.
- Zebra devices on Android Enterprise are configured with OEMConfig profiles and Zebra's OEMConfig app from Managed Google Play; MX profiles built in StageNow are for Android device administrator. HoloLens 2 uses Windows Holographic for Business profiles, with VPN only in device scope. Autopilot Teams Rooms are grouped by the MTR- group tag and excluded from other policies.
Implement Intune Suite add-on capabilities
- Endpoint Privilege Management (EPM) lets standard users elevate specific files. The elevation settings policy enables the client and sets the device-wide default elevation response and reporting scope; elevation rules set the elevation type (automatic, user confirmed, support approved or deny) and child process behaviour.
- The Enterprise App Catalog provides Win32 apps prepared by Microsoft with prefilled commands, requirements and detection rules; the Intune management extension installs them, not WinGet. With a Required assignment you can turn on auto-update; to review or stage new versions, use guided update supersedence, which does not copy assignments or scope tags.
- Remote Help is enabled tenant-wide and requires both helper and sharer to sign in with Microsoft Entra accounts from the same organization. A helper needs Remote Tasks - Offer remote assistance, Remote Assistance Connector - Read and at least one Remote Help permission (view screen, full control, elevation or unattended control), scoped to the sharer's user or device.
- Microsoft Cloud PKI creates a root CA and an issuing CA in the cloud (or an issuing CA anchored to your own CA) and provides a SCEP service, with no NDES or Intune Certificate Connector. For each platform you create trusted certificate profiles for the root and issuing CAs and a SCEP profile with the issuing CA's SCEP URI. Each issuing CA dashboard shows active, expired and revoked certificates and lets you revoke them.
- Microsoft Tunnel Gateway runs in a container on a Linux server; Tunnel for MAM extends it to unenrolled Android and iOS devices. On Android, Microsoft Defender is the tunnel client and you need two app configuration policies (Defender and Edge) plus an app protection policy that starts the tunnel when the app launches. Server health is reviewed in the admin center, with mst-cli and with journalctl.
Perform remote actions on devices
- Sync forces an immediate check-in with Intune, and restart depends on a push notification. Retire removes corporate data, apps and profiles and unenrolls the device while keeping personal data; wipe restores factory settings. On Windows, wipe can keep the enrollment state and user account, or continue even if the device loses power.
- Bulk device actions run one action on many devices at once: you pick the OS and the action, select the devices and create the task. Available actions depend on the platform; on Windows they include Autopilot Reset, collect diagnostics, rename, sync, restart, retire, wipe and delete. Retire, wipe and delete take precedence over any other pending actions.
- The Update Windows Defender security intelligence action downloads Microsoft Defender Antivirus security intelligence files right away, separate from quick and full scans. In Graph it is windowsDefenderUpdateSignatures, which needs DeviceManagementManagedDevices.PrivilegedOperations.All. In antivirus policy, a check interval of 0 turns off checking for new updates.
- The BitLocker key rotation action remotely refreshes the recovery key of the OS drive, for example after the helpdesk has shared it. On Microsoft Entra joined or hybrid joined devices, BitLocker policy must enable client-driven recovery password rotation and save recovery information to Microsoft Entra ID before BitLocker is turned on.
- The Rotate local admin password action manually changes the password of the local admin account managed by Windows LAPS, outside the policy schedule, and resets the PasswordAgeDays countdown. The device must have Windows LAPS backing up the account to the directory and, if Microsoft Entra joined, be online. You rotate one device at a time, not as a bulk action.
3. Protect devices
15–20%Configure endpoint security
- Endpoint security antivirus policies group only the Microsoft Defender Antivirus settings for Windows, macOS and Linux, with profiles for antivirus, exclusions, Windows Security experience (including tamper protection) and update controls. Exclusions merge across policies; for other conflicts the most secure policy wins, then the last modified one.
- Disk encryption policy uses BitLocker and Personal Data Encryption profiles on Windows and FileVault on macOS; silent encryption requires turning off the other-encryption warning and no startup PIN. Keys are escrowed to Microsoft Entra ID, rotated with a remote action and available to users through self-service. The encryption report shows readiness and OS drive status.
- Firewall policy configures the built-in firewall on macOS and Windows, and on Windows Server through Defender for Endpoint security settings management. Two Windows Firewall profiles with different values for the same setting stop it from being sent; non-conflicting rules from several rules profiles merge, while conflicting rules are both delivered to the device.
- Attack surface reduction policies include ASR rules, Device Control, Exploit Protection and other profiles, and require Defender Antivirus as the primary antivirus. Rules merge per device and only conflicting settings are held back; exclusions can be global or per rule. Following Zero Trust, rules other than the standard protection ones are tested in Audit by rings before Block.
- Security baselines are groups of settings preconfigured by Microsoft security teams (Windows, Defender for Endpoint, Microsoft 365 Apps, Edge, Windows 365) that you can customize. When a new version ships, older profiles become read-only; updating creates a side-by-side copy without assignments or scope tags. Multiple baselines or policies can conflict, so review their values.
Manage device updates
- Planning updates in Intune means combining tools per platform: on Windows, update rings plus feature, quality and driver update policies (the latter three do not support Microsoft Entra registered devices); on mobile, enrollment restrictions, compliance policies with a minimum OS version and app protection policies that warn or block. Maintenance windows limit when installs and restarts start.
- Update rings control client behaviour (deferrals, deadlines, restarts) and support pausing for up to 35 days, uninstalling or extending the pause. Feature update policies hold devices on a Windows version until the policy changes, and quality update policies add orchestration, hotpatch and expedite, which overrides the deferral only for the specified update.
- Windows Autopatch automates Windows, Microsoft 365 Apps, Edge and Teams updates, and Autopatch groups combine device-based Microsoft Entra groups into deployment rings, with Test and Last always present. Hotpatch applies security updates without a restart when the quality update policy or the tenant setting allows it; it requires VBS to be on and, on Arm64, CHPE to be disabled.
- In Intune, iOS/iPadOS and macOS updates are configured in the settings catalog with declarative device management: Enforce Latest installs the newest release after Delay in Days at a local Install Time, and the targeted model requires a Target OS Version by Target Date Time. Software Update Settings shape user interaction, and a Success status only means the policy reached the device.
- On corporate-owned Android Enterprise devices, the device restrictions profile controls updates through System update (Device Default, Automatic, Postponed or Maintenance window) and freeze periods that also block manual checks. For firmware, Intune integrates Samsung Knox E-FOTA and Zebra LifeGuard OTA; Zebra deployments are one-time actions that cannot be modified after creation.
4. Manage and secure applications
15–20%Deploy and update apps
- Preparing apps for Intune starts with choosing the type: Win32 apps are converted to .intunewin with the Microsoft Win32 Content Prep Tool, which compresses the whole source folder, and must install silently; Windows LOB apps accept .msi, .appx or .msix with a single argument. To protect LOB apps without source code you use the App Wrapping Tool; with code, the Intune App SDK.
- Win32 apps are packaged as .intunewin files with the Microsoft Win32 Content Prep Tool and support install commands, requirement and detection rules, dependencies and supersedence; Windows LOB apps (.msi, .appx, .msix) accept only one command-line argument. Microsoft Store app (new) searches the Store from Intune, keeps apps updated automatically and needs System context on Microsoft Entra registered devices.
- Quiet Time policies mute Outlook email and Teams notifications on iOS/iPadOS and Android. There are three types: Date Range (start and end), Days of the week (all day or certain hours, with an option to let users change the settings) and Non-working time, which affects only Teams and requires the tenant to be integrated with the Working Time API. They are assigned to groups of users.
- The Microsoft 365 Apps (Windows 10 and later) app type is configured with the designer or with XML data (required for the business edition) and downloads the suite from the Office CDN. Remove existing .msi versions of Office, or the installation fails; the 32-bit version installs on 32-bit and 64-bit devices, and only one Microsoft 365 deployment is delivered per device.
- Cloud Policy enforces user settings for Microsoft 365 Apps even on unmanaged devices; it uses only user objects, priority 0 wins, it takes precedence over Group Policy and it takes effect when the app restarts. For computer settings such as the update channel on enrolled devices, use the Intune settings catalog.
Plan and implement app protection and app configuration policies
- App protection policies target users and protect data on enrolled and unenrolled devices; managed app filters on app.deviceManagementType separate BYOD policies from policies for managed devices. Android needs the Company Portal app, a MAM selective wipe keeps the app installed, and the data protection framework defines three protection levels.
- App-based Conditional Access combines Intune app protection policies with the Require app protection policy grant, which Microsoft recommends for new policies. The device registers in Microsoft Entra ID through Authenticator on iOS or Company Portal on Android, and the policy should start in Report-only mode before it is turned on.
- App configuration policies use the MDM channel (managed devices) on enrolled devices or the MAM channel (managed apps) for Intune App SDK apps regardless of enrollment. On iOS, IntuneMAMAllowedAccountsOnly and IntuneMAMUPN restrict accounts, and an updated Android LOB app needs a new policy for the new version.
5. Optimize endpoint operations by using automation, monitoring, and reporting
10–15%Automate management tasks
- Intune is automated with Microsoft Graph and the Microsoft Graph PowerShell SDK: Connect-MgGraph with -Scopes for delegated access, or with ClientId, TenantId and a certificate for app-only access. Reading devices needs DeviceManagementManagedDevices.Read.All, actions such as syncDevice or wipe need PrivilegedOperations.All, and every Intune scope requires admin access.
- The Vulnerability Remediation Agent uses Microsoft Defender Vulnerability Management data to list and prioritize CVEs on managed Windows devices, rating impact by exposure score and adding Intune remediation steps. It runs under a Microsoft Entra agentic identity with delegated permissions, excludes Windows Server editions and does not support scope tags.
- To analyze performance, Copilot in Intune generates KQL for device query from natural language, compares a healthy device with a problem device and, with the Windows 365 plug-in, recommends Cloud PC resizing. The resource performance report scores CPU and RAM spikes, and Copilot only sees data allowed by the admin RBAC roles and scope tags.
- Vulnerability Remediation Agent suggestions are reviewed in Intune: for the OS they recommend quality update policies and update rings, and for apps, newer versions or profiles. Mark as applied only records a dated attestation; the agent never changes devices, a run cannot be paused, and removing the agent deletes all of its suggestions.
- Custom compliance extends Intune policies with a discovery script (PowerShell on Windows) and a JSON file with SettingName, Operator, DataType and Operand rules. The script is uploaded before the policy is created, runs as System by default and must end with ConvertTo-Json -Compress; the result counts for Conditional Access.
Monitor and optimize health
- Intune reports are grouped as operational, organizational, historical and specialist, with search, filters and exports that keep the search. For custom data, Diagnostic settings send logs such as DeviceComplianceOrg to Log Analytics and Azure Monitor workbooks, and the Microsoft Graph exportJobs API exports reports asynchronously.
- Endpoint analytics collects data through the Intune data collection policy and needs the DiagTrack service running. It gives startup performance, application reliability and work from anywhere scores, with your own baselines and a regression threshold; to act on its insights you assign Remediations script packages, such as the built-in ones.
- A Remediations package combines a detection script and, optionally, a remediation script, which runs only when detection ends with exit 1. The schedule is set in the assignment (once, hourly or daily, in local time or UTC), and if the signature check is enforced the device execution policy applies.
- The startup score combines boot and sign-in, and restart frequency separates abnormal shutdowns (Stop errors, power button) from normal ones; about one update restart a month is ideal. Each app's reliability is based on mean time to failure and total usage, with comparisons across app versions and OS versions.
- The Tenant status page brings together tenant details, connector status (the least healthy status summarizes each type), service health with the incidents that affect the tenant, and the message center. Email preferences are set in the Microsoft 365 admin center, and audit logs show who changed what.