
What MDM enrollment means, the enrollment methods for Apple, Windows and Android, company vs personal devices, and how to unenroll a device.
Discover six Windows device enrollment methods, with comparison tables to help you choose the right approach for your organization.


Content writer, trio.so
Windows device enrollment is how you register corporate devices into your mobile device management system for security controls and configuration. Your choice between manual, bulk, or automated enrollment directly impacts IT workload, deployment time, and device security across your Windows fleet. According to recent research, Autopilot reduces deployment effort by 67% and cuts provisioning time nearly in half.
This article covers six Windows device enrollment methods, explains which scenarios demand bulk enrollment for Windows devices, and provides decision-making tables to match your organization's size and technical requirements. You'll learn the exact steps for each enrollment method, understand prerequisites for Windows MDM enrollment, and identify when to use Autopilot versus provisioning packages.
Windows MDM enrollment registers devices with cloud-based management platforms like Microsoft Intune or third-party solutions to enforce security policies, deploy applications, and maintain compliance. The enrollment process establishes a trust relationship between the Windows device and the MDM server by exchanging certificates and configuration data. Organizations gain centralized control over device settings, software distribution, and remote management capabilities through this connection.
Modern Windows enrollment relies on Entra ID integration rather than legacy on-premises Active Directory. When a user signs into Windows with organizational credentials during setup or through the Settings app, the device joins Entra ID and triggers automatic MDM enrollment based on configured policies. This shift to cloud-based enrollment eliminates manual configuration tasks and enables immediate security policy enforcement from the moment a device powers on.
The enrollment process varies based on device ownership, deployment scale, and organizational infrastructure. Corporate-owned devices typically use automated methods like Windows Autopilot, while BYOD scenarios rely on user-initiated enrollment through the Company Portal app. According to Redmond Magazine, over 53% of enterprise-managed Windows devices still run Windows 10 version 22H2, indicating many organizations continue managing mixed OS environments through MDM enrollment strategies.
Microsoft offers several ways to bring Windows devices into management, ranging from automated, zero-touch deployments for corporate hardware to manual registration for personal devices. These six methods provide the flexibility needed to secure and configure any device, regardless of whether it is company-owned or part of a BYOD program.
Windows Autopilot transforms device provisioning by enabling IT administrators to register hardware IDs with Microsoft's cloud service before devices ship to end users. The device receives a pre-configured deployment profile during the out-of-box experience that automatically joins Entra ID, enrolls in Intune, and applies security policies without IT intervention. This zero-touch approach eliminates traditional imaging workflows and allows devices to ship directly from manufacturers or resellers to employees.
The Autopilot process requires device hardware hash registration in the Microsoft Intune admin center before initial setup. OEM partners can pre-register devices during manufacturing, or IT teams can capture hardware IDs using PowerShell scripts from existing devices. Once registered, the deployment profile determines whether the device undergoes user-driven self-deployment or pre-provisioning scenarios where IT partially configures the device before handoff.
Pros:
Cons:
Key Features:
Bulk enrollment uses provisioning packages created through Windows Configuration Designer to join multiple devices to Entra ID and enroll them in MDM simultaneously. IT administrators build a .ppkg file containing enrollment tokens, certificates, and configuration settings, then distribute it via USB drives or network shares. Technicians apply the package during Windows setup or on existing installations to automate the enrollment process across device fleets.
This method works best when Autopilot isn't feasible due to budget constraints or when enrolling existing devices already running Windows 10 or 11. The provisioning package approach requires physical access to devices during deployment but provides faster bulk enrollment than manual methods. Organizations staging large device deployments can create specialized packages for different departments or device types with customized configurations.
Pros:
Cons:
Key Features:
Group Policy auto-enrollment leverages existing Active Directory infrastructure to automatically enroll Microsoft Entra hybrid joined devices into MDM. Administrators configure a Group Policy Object that triggers MDM enrollment when domain-joined Windows devices sign in with organizational credentials. The policy creates a scheduled task that registers the device with Intune using Entra ID authentication tokens without user intervention.
This enrollment method serves organizations transitioning from traditional domain management to cloud-based MDM while maintaining Active Directory dependencies. The approach works exclusively with Microsoft Entra hybrid join scenarios where devices maintain both on-premises domain membership and Microsoft Entra registration. IT teams can target specific organizational units with enrollment policies to control rollout pace and scope.
Pros:
Cons:
Key Features:
Company Portal enrollment allows users to manually register their devices by signing into the Intune Company Portal app or adding a work account through Windows Settings. Users navigate to Settings > Accounts > Access work or school, select Connect, and enter organizational credentials to initiate Microsoft Entra join and MDM enrollment. The process suits BYOD scenarios where employees use personal devices for work tasks while maintaining separate personal and work profiles.
This user-initiated approach provides the simplest enrollment path for small deployments and organizations without dedicated IT deployment resources. The method requires users to download the Company Portal app from the Microsoft Store or enroll directly through system settings. Users maintain control over the enrollment process but must follow organization-specific instructions to complete setup correctly.
Pros:
Cons:
Key Features:
Microsoft Entra join with automatic enrollment combines device registration and MDM enrollment into a single streamlined process during Windows setup. When users select "Set up for an organization" during OOBE and sign in with work credentials, Windows automatically joins Entra ID and enrolls in Intune if automatic enrollment is configured. This method provides faster deployment than traditional domain join while maintaining centralized management capabilities.
Organizations configure automatic MDM enrollment in the Microsoft Intune admin center by setting MDM user scope to include target users or groups. The configuration ensures every Microsoft Entra join triggers immediate Intune enrollment without additional user steps. This approach works for both new device deployments and when users manually join existing devices through Windows Settings.
Pros:
Cons:
Key Features:
Device Enrollment Manager accounts allow designated users to enroll up to 1,000 shared devices into MDM without associating them with specific end users. IT administrators create DEM accounts in Intune and grant enrollment permissions to staff responsible for configuring shared tablets, kiosks, or point-of-sale devices. These accounts bypass the typical one-user-per-device limitation for scenarios where multiple people use the same hardware.
DEM enrollment suits retail environments, healthcare facilities, and educational institutions deploying shared device pools. The enrolled devices receive standard configuration policies but cannot access user-specific resources like email, OneDrive, or personal apps. Organizations use DEM for utility devices requiring basic management without individual user profiles.
Pros:
Cons:
Key Features:
Enrolling Windows devices in MDM requires proper Entra ID configuration, user permissions, and network connectivity. The fundamental steps remain consistent across enrollment methods, though specific prerequisites vary based on your chosen approach. Start by turning on automatic MDM enrollment, making sure the MDM user scope includes the users or groups who need device management.
In the Microsoft Intune admin center, go to Devices > Device onboarding > Enrollment, open the Windows tab and select Automatic Enrollment. Set the MDM user scope to All or Some based on your enrollment strategy. Configure MDM discovery URL, MDM terms of use URL, and MDM compliance URL using the default Intune values unless using a third-party MDM provider. Save the configuration to enable automatic enrollment for users within scope.
For new device deployment using Autopilot, register device hardware IDs in the Microsoft Intune admin center before shipping. Import the CSV file containing hardware hashes under Devices > Device onboarding > Enrollment > Windows > Windows Autopilot devices. Assign an Autopilot deployment profile specifying deployment mode, Microsoft Entra join type, and whether to skip privacy settings during OOBE. Devices automatically receive the profile during initial setup when connected to the internet.
When using bulk enrollment for existing devices, download Windows Configuration Designer from the Microsoft Store and create a new provisioning package project. Select Provision desktop devices and configure Microsoft Entra join settings using your organization's tenant information. In the same wizard, select Get Bulk Token and sign in with an account that is allowed to join devices, so the token is added to the provisioning package. Build the package and distribute it via USB drives or network shares to target devices.
For Group Policy auto-enrollment in hybrid environments, create a Group Policy Object in Group Policy Management Console and navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > MDM. Enable the policy "Enable automatic MDM enrollment using default Azure AD credentials" and link the GPO to organizational units containing target devices. Devices automatically enroll during the next Group Policy refresh cycle when users sign in with organizational credentials.
Manual Company Portal enrollment requires users to download the Intune Company Portal app from the Microsoft Store or enroll through Windows Settings. Guide users to Settings > Accounts > Access work or school > Connect, then enter organizational credentials when prompted. The device joins Entra ID and enrolls in MDM if automatic enrollment is configured. Users can verify enrollment success by checking for the work account under Access work or school settings.
Windows 10 MDM enrollment supports devices running version 1703 or later, while Windows 11 adds stricter hardware requirements including TPM 2.0, UEFI firmware, and Secure Boot capabilities. Both operating systems use identical enrollment protocols and management channels, but Windows 11 enforces security baselines preventing enrollment on hardware that doesn't meet specifications. Organizations managing mixed fleets should verify device compatibility before attempting Windows 11 Autopilot deployments.
The enrollment user experience remains nearly identical between Windows 10 and Windows 11, with both supporting the same six enrollment methods. Windows 11's redesigned OOBE interface presents slightly different visual elements during Microsoft Entra join, but the underlying enrollment process executes the same authentication and certificate exchange. IT administrators can use the same Intune policies, configuration profiles, and compliance settings across both operating systems without modification.
Windows 11 introduces enhanced security features that affect post-enrollment management rather than the enrollment process itself. Virtualization-based security, hardware-based isolation, and measured boot requirements provide stronger endpoint protection but don't change how devices connect to MDM servers. Organizations enrolling Windows 11 devices gain immediate access to these security improvements while maintaining enrollment workflows established for Windows 10 fleets.
Device hardware requirements create the primary differentiation between Windows 10 and Windows 11 enrollment scenarios. Legacy devices lacking TPM 2.0 or sufficient RAM cannot enroll as Windows 11 devices and must remain on Windows 10, which reached end of support on 14 October 2025, so those devices need paid Extended Security Updates or replacement. This hardware divide forces organizations to segment enrollment strategies based on device capabilities rather than operating system preferences.
Intune enrollment methods for Windows devices leverage Microsoft's cloud infrastructure to provide seamless integration with Entra ID, Microsoft 365, and security services. The platform supports all six enrollment approaches with native configuration options in the Microsoft Intune admin center. Administrators configure enrollment restrictions, device limits, and platform requirements through Intune policies that automatically apply during the enrollment process.
Intune's automatic enrollment capability eliminates manual MDM server configuration by pre-populating discovery URLs and terms of use during Microsoft Entra join. When users sign into Windows with organizational credentials, the device queries Entra ID for MDM configuration and automatically initiates Intune enrollment if the user falls within the configured MDM scope. This tight integration reduces enrollment failures caused by misconfigured server settings or certificate issues common with third-party MDM providers.
MDM for Windows solutions beyond Intune often require additional certificate configuration and discovery service setup compared to Microsoft's native integration. Organizations using Workspace ONE, SOTI, or other third-party platforms must configure Entra ID app registrations and MDM discovery URLs manually. The enrollment process follows the same Windows protocols but lacks the automatic discovery features built into Intune deployments.
Intune enrollment includes built-in compliance checking that evaluates device health immediately after enrollment completes. The platform assesses BitLocker encryption status, antivirus definitions, firewall configuration, and password complexity before granting resource access. Conditional access policies integrated with Entra ID can block non-compliant devices from accessing corporate email or SharePoint until IT addresses security gaps identified during enrollment.
Bulk enrollment for Windows devices makes sense when deploying 50 or more devices without Autopilot hardware registration and when IT staff can physically access devices during setup. The provisioning package approach costs less than Autopilot since it doesn't require OEM partnerships or hardware hash collection, but it sacrifices the zero-touch deployment experience that ships devices directly to users. Organizations with warehouse staging areas or deployment technicians benefit most from this method.
Compare your deployment timeline against available resources before selecting bulk enrollment. Creating and testing provisioning packages requires 4-6 hours for initial setup plus 2-3 hours per customized package variant. Applying packages takes 5-10 minutes per device depending on configuration complexity and storage media speed. Calculate total deployment time by multiplying per-device minutes by your fleet size, then compare against Autopilot's ship-from-manufacturer timeline.
Autopilot provides superior user experience and lower long-term costs for organizations deploying new devices regularly. The upfront investment in hardware ID registration and deployment profile configuration pays dividends across multiple deployment waves. Bulk enrollment via provisioning packages suits one-time migrations or organizations with existing device inventory that cannot support Autopilot enrollment due to age or hardware limitations.
Consider hybrid approaches combining multiple enrollment methods based on device types and deployment scenarios. Use Autopilot for executive laptops requiring immediate deployment, bulk provisioning for refreshing conference room tablets, and Group Policy auto-enrollment for existing hybrid joined workstations. This segmented strategy optimizes IT effort while meeting diverse deployment requirements across your organization.
Security implications differ between enrollment methods based on certificate storage and authentication flows. Autopilot and Microsoft Entra join leverage cloud-based certificate issuance with hardware-backed key storage when TPM is available. Provisioning packages can include pre-shared certificates that present risk if improperly secured during distribution. Evaluate your organization's security posture when choosing enrollment approaches for devices accessing sensitive data.
trio.so manages Windows devices next to Macs, Linux machines, iPhones, iPads and Android phones in one console. Windows devices enroll through Windows Autopilot, through Microsoft Entra join with automatic enrollment, or in bulk with a provisioning package, so the methods above still apply.
Once a device is enrolled, IT applies configuration and security policies, deploys apps, and sees for every device whether each policy applied, failed or is still pending. The inventory shows installed apps, the serial number, the owner and the encryption status. trio.so handles Windows updates through Auto Patch policies and third-party fixes through remediation plans, and shows the result for each device. On the Zero Trust plan, conditional access keeps a device that fails its policies away from company apps, and the Microsoft Defender for Endpoint integration shows Defender alerts for each device.
trio.so syncs users and groups from Microsoft Entra ID, and IT can connect to a Windows PC with remote desktop or run a remote wipe if it is lost or stolen.
Ready to simplify Windows device management for your organization? Start your free trial, or book a demo to see how trio.so handles your specific deployment requirements.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Related
The related industry news, interviews, technologies, and resources.

What MDM enrollment means, the enrollment methods for Apple, Windows and Android, company vs personal devices, and how to unenroll a device.

Stop manually setting up Apple devices. Learn how SMB IT teams can leverage Apple Zero-Touch Deployment for fast, seamless, and automated device enrollment.

Seven IBM MaaS360 alternatives compared on platforms and published pricing, with MaaS360's own plans and what to check before you switch.

Seven Miradore alternatives compared on platforms and published pricing, with Miradore's own plans and its 50-device free limit.

Seven 42Gears SureMDM alternatives compared on platforms and published pricing, with SureMDM's own plans and when it still fits.

The best Microsoft Intune alternatives for IT teams: an honest comparison of features, platforms and published pricing, and when to stay on Intune.

Learn how to calculate ROI of MDM with proven cost savings formulas. Organizations achieve 200-400% return through reduced IT costs and enhanced productivity.

Mobile device security protects endpoints through encryption, MDM, and threat defense to safeguard business data from cyber attacks.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients