Ensure users have one of the following licenses:
Microsoft Intune Plan 1
Microsoft 365 E3/E5
Microsoft 365 Business Premium
Enterprise Mobility + Security (EMS) E3/E5
Navigate to:
Microsoft Intune admin center
Tenant administration
Tenant status
Verify:
MDM authority = Microsoft Intune
Navigate to:
Microsoft Entra admin center
Mobility (MDM and MAM)
Microsoft Intune
Navigate to:
Devices
→ Enrollment
→ Enrollment restrictions
Recommended settings:
Allow Windows enrollment
Block unsupported operating systems if required
Configure device limit restrictions
Purpose
Used for:
Existing Microsoft Entra joined devices
Existing Microsoft Entra hybrid joined devices
Automatic Intune enrollment without manual registration
Navigate: Microsoft Entra admin center → Mobility (MDM and MAM) → Microsoft Intune
↓
Configure:
MDM User Scope: All (or Selected Groups)
MAM User Scope: None (Unless using App Protection Policies for Windows)
Navigate: Group Policy Management → Computer Configuration → Administrative Templates → Windows Components → MDM
↓
Action: Enable: Enable automatic MDM enrollment using default Azure AD credentials
↓
Choose Credential Type:
Device Credential (Recommended for Windows 10 1903+ and Windows 11)
User Credential
Navigate on Client PC: Settings → Accounts → Access work or school
↓
Action: Click: Info → Click: Sync
Navigate: Intune Admin Center → Devices → Windows
↓
Verify Device Displays:
Managed by: Intune
Compliance: Compliant (after policy evaluation)
Zero-touch provisioning for new corporate devices.
Supports:
Microsoft Entra Join
Hybrid Microsoft Entra Join
Self-deploying mode
Pre-provisioning (White Glove)
User-driven mode
Choose one of the following methods to register your device hardware hashes:
Option 1 (Preferred / Automated): The OEM or hardware distributor uploads the hardware hash directly to your Microsoft Entra tenant at the time of purchase.
Option 2 (Manual / PowerShell): Run the following commands on a target device to extract the hardware hash locally:
PowerShell
Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo.ps1 -OutputFile AutoPilot.csv
Navigate:
Devices → Windows → Windows enrollment → Devices → Import
↓
Action:
Upload the generated AutoPilot.csv file.
↓
Verification:
Monitor the device list until the Profile Status changes to Assigned.
Navigate:
Devices → Windows → Windows enrollment → Deployment Profiles
↓
Action:
Click Create profile → Name it (e.g., Corporate Laptop Profile).
Apply the following recommended configuration options within your profile:
Setting Recommended Value
Join Type Microsoft Entra Joined
User Account Type Standard User
Skip Privacy Settings Yes
Skip Cortana Yes
Skip OneDrive Optional
Skip OEM Registration Yes
Automatically Configure Keyboard Yes
↓
Action:
Assign this deployment profile to your target Autopilot device group.
Action:
Create a dynamic Microsoft Entra ID group utilizing the Autopilot device attributes:
↓
Targeting:
Assign the following core resources directly to this dynamic group:
Deployment Profile (Created in Step 3)
Configuration Profiles (Wi-Fi, certificates, VPN)
Compliance Policies
Required Applications (Microsoft 365 Apps, security agents)
User turns on the unboxed device
↓
Connects to a local Wi-Fi or cellular network
↓
Enters organizational Microsoft Entra ID credentials
↓
Autopilot automatically downloads and applies:
• Enrollment Profile
• Applications
• Configuration Profiles
• Compliance Policies
↓
Device reaches the Windows desktop, secured and ready for use.
Personal Windows laptops and desktops.
The user enrolls the device into Intune while retaining personal ownership.
Navigate:
Devices → Enrollment → Enrollment restrictions
↓
Action:
Edit your platform restrictions profile and set Windows (MDM) for Personally owned devices to Allow.
Navigate on Personal PC:
Settings → Accounts → Access work or school
↓
Action:
Click the Connect button.
Action:
The user enters their corporate organizational credentials (Microsoft Entra ID account) when prompted by the login wizard, followed by any required Multi-Factor Authentication (MFA) challenges.
Action:
During the sign-in handshake, the user must ensure the following option remains checked:
☑ Allow my organization to manage my device
↓
Status:
Clicking OK/Next triggers the silent MDM auto-enrollment registration, anchoring the personal device certificate into Microsoft Intune.
Navigate on Client PC:
Settings → Accounts → Access work or school
↓
Verify Text/Icons Displayed:
Connected to [Organization Name] Microsoft Entra ID
Click Info to verify it states: Managed by Microsoft Intune
Manage existing Configuration Manager-managed devices using both Configuration Manager and Intune during a phased migration.
Prerequisites
Ensure the environment meets the following baseline requirements before initiating co-management:
Supported version of Configuration Manager Current Branch
Active Microsoft Intune tenant
Active Microsoft Entra tenant
Cloud Attach enabled
Managed endpoints running a supported version of Windows 10 or Windows 11
Navigate:
Administration → Cloud Services → Cloud Attach in the Configuration Manager console.
↓
Action:
Run the Cloud Attach wizard to configure:
Tenant attach: Integrates the on-premises site with the cloud service.
Device upload: Specifies which device collections upload to the cloud console.
Targeting: Select targeted device collections for synchronization.
Navigate:
Administration → Cloud Services → Co-management
↓
Action:
Launch the Co-management Configuration Wizard and input the required infrastructure properties:
Microsoft Entra tenant credentials
Microsoft Intune subscription details
Cloud enrollment restrictions and settings
Action:
Configure the system to trigger silent, automatic MDM enrollment once devices are cloud-attached.
↓
Set Enrollment Scope:
Pilot: Automatically enrolls only the devices contained within a designated Configuration Manager pilot collection.
All: Automatically enrolls all supported Windows devices managed by the hierarchy.
When moving management authority from Configuration Manager (on-premises) to Microsoft Intune (cloud), utilize a phased approach by shifting the sliders (dials) gradually.
Transition Strategy:
Validate functionality within the pilot group first, then slide the workload dials completely to Intune to transition authority globally.
Move workloads gradually as testing completes
On-Premises Verification (Configuration Manager console)
Navigate: Assets and Compliance → Devices
Confirm the targeted device column displays: Co-management = Yes
Cloud Verification (Intune Admin Center)
Navigate: Devices → Windows
Verify the endpoint object appears in the inventory and successfully checks in to receive cloud policies.
Validation Checklist
After enrollment, verify:
Device appears in Microsoft Intune.
Correct ownership (Corporate or Personal) is shown.
Compliance policies are evaluated.
Configuration profiles are applied.
Required applications are installed.
Microsoft Defender policies are enforced (if configured).
BitLocker escrow is working (for managed devices).
Windows Update for Business policies are applied where appropriate.
Best Practices
Use Windows Autopilot for all new corporate devices.
Use Automatic Enrollment for Microsoft Entra joined or Hybrid joined devices.
Use BYOD enrollment only for employee-owned devices that require management.
Use Co-management as a transition strategy for existing Configuration Manager environments, migrating workloads to Intune in phases rather than all at once.
Use dynamic device groups to target deployment profiles, applications, and policies consistently.
Test all enrollment methods with a pilot group before broad deployment to production.