azureblog.co.uk
← MD-102 study plan
MD-102 · Prepare infrastructure for devices

Implement identity and compliance with Intune

Intune and Windows 365 roles, scope tags, multi admin approval, compliance policies, compliance-based Conditional Access, Windows Hello for Business, Windows LAPS and local group membership.

  • 22 min
  • 8 concepts
  • Try it yourself
  • 5-question check

Learn

Intune decides whether a device is healthy; Conditional Access uses that answer to decide whether it can reach company data. Around that sit admin roles, approvals for risky changes, and controls for local admin accounts and sign-in.

  1. 1

    Manage built-in and custom roles for Intune and Windows 365, including role assignments

    Intune RBAC roles include Policy and Profile Manager, Help Desk Operator, Application Manager, School Administrator and Read Only Operator; Windows 365 has roles such as Cloud PC Administrator. A role assignment sets members (admins), scope groups (which users and devices they manage) and scope tags. Custom roles pick specific permissions. Intune Administrator in Entra ID has full access.

    Remember: Assignment = who, over which groups, with which scope tags.

  2. 2

    Configure scope tags and scoped administration for multi-admin environments

    Scope tags label policies, apps and devices (for example 'London'). Admins whose role assignment has the London tag see only London-tagged objects. Combine with scope groups so regional IT teams manage only their own devices and policies.

    Remember: Scope tags control what admins can see.

  3. 3

    Implement and manage multi-admin approval

    Multi admin approval uses access policies to require a second admin to approve changes to protected areas, such as app deployments, scripts, role changes and device wipes. The requester can't approve their own change. It protects against a compromised or careless admin account.

    Remember: Two-person rule for risky Intune changes.

  4. 4

    Implement compliance policies for all supported device platforms by using Intune

    Compliance policies set requirements: minimum OS, BitLocker, Secure Boot, password, firewall, antivirus, jailbreak/root detection, and Defender for Endpoint machine risk score. Actions for noncompliance: mark noncompliant (with a grace period), email the user, remotely lock, retire. Tenant-wide compliance policy settings decide whether devices with no policy are compliant and the validity period.

    Remember: Set 'mark devices with no policy as' Not compliant.

  5. 5

    Implement Microsoft Entra Conditional Access policies that require a compliance status

    Intune reports compliance to Entra ID. A Conditional Access policy with Require device to be marked as compliant then blocks noncompliant or unenrolled devices from apps such as Exchange Online and SharePoint. Exclude emergency accounts and allow the Intune enrolment apps so users can fix their device.

    Remember: Intune decides; Conditional Access enforces.

  6. 6

    Configure Windows Hello for Business by using Intune

    Configure WHfB tenant-wide in Windows enrollment > Windows Hello for Business, or per group with an account protection policy or settings catalog: PIN length and complexity, biometrics, TPM requirement and enhanced sign-in security. For hybrid, use cloud Kerberos trust.

    Remember: Group-targeted settings override the tenant-wide policy.

  7. 7

    Implement and manage Windows Local Administrator Password Solution (Windows LAPS) by using Microsoft Intune and Microsoft Entra ID

    Turn on Enable Microsoft Entra Local Administrator Password Solution in Entra device settings, then create an Intune account protection > LAPS policy: backup directory (Entra ID or AD), password age, length, complexity and post-authentication actions. View passwords in Intune or Entra with the right permissions, and rotate them on demand.

    Remember: Turn LAPS on in Entra ID first, then the Intune policy.

  8. 8

    Manage the membership of local groups on Windows devices by using Intune

    An account protection > Local user group membership policy adds, removes or replaces members of local groups such as Administrators, using Entra users and groups. Replace removes anyone not listed, which is how you strip local admin rights from users.

    Remember: Replace = only the listed members remain.

From device health to access

  1. EnrolDevice is managed by Intune.
  2. EvaluateCompliance policy checks settings.
  3. ReportCompliance state written to Entra ID.
  4. EnforceConditional Access requires a compliant device.
  5. RemediateNoncompliance actions and user guidance in Company Portal.

Try it

Conditional Access requires a compliant device for Exchange Online. Your compliance policy requires BitLocker and Windows 11 23H2 or later, with a 1-day grace period.

This interactive part needs JavaScript.

In the portal

  • Compliance policiesIntune admin center: Devices > Compliance > Policies
  • RolesIntune admin center: Tenant administration > Roles
  • Multi admin approvalIntune admin center: Tenant administration > Multi Admin Approval
  • LAPS policyIntune admin center: Endpoint security > Account protection > Create policy

Key terms

Click a card to see the definition.

Check your understanding

5 questions. Score 80% or more and these skills are marked as confident in your MD-102 study plan.

  1. What makes London IT see only London policies?

  2. Which local group membership action removes users not listed?

  3. What must be turned on in Entra ID before Windows LAPS backs up to Entra?

  4. A device fails compliance but is within its grace period. Can it get through 'require compliant device'?

  5. Who can approve a change under multi admin approval?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.