Study guide
3.1 Autopilot vs. Provisioning Packages
MD-102 Endpoint Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Exam Overview and MD-102 Study Strategy
Current Exam Facts Audience Profile and Endpoint Admin Mental Model Domain Map and Weighting Strategy Six-to-Ten-Week Study Plan and Readiness Checklist
2 Prepare Infrastructure for Devices
Microsoft Entra Device Identity and Grouping Intune Enrollment by Platform Compliance and Conditional Access Admin Roles, Windows Hello, Windows LAPS, and Local Groups
3 Deploy and Configure Managed Devices
3.1 Autopilot vs. Provisioning Packages 3.2 Autopilot Modes, ESP, and Naming 3.3 Windows 11 Upgrades and Windows 365 Cloud PCs 3.4 Configuration Profiles and Assignment Filters
4 Intune Suite, Remote Actions, and Operational Troubleshooting
4.1 Endpoint Privilege Management and Enterprise App Catalog 4.2 Advanced Analytics, Remote Help, Cloud PKI, and Tunnel for MAM 4.3 Remote Actions and Bulk Actions 4.4 Defender Intelligence, BitLocker Key Rotation, and KQL Device Query Troubleshooting
5 Manage Applications with Intune
5.1 App Deployment Decision Matrix and Packaging 5.2 Microsoft 365 Apps, Office Policies, ODT, OCT, and Admin Center 5.3 App Stores and Update Lifecycle 5.4 App Protection, App Configuration, and Conditional Access
6 Protect Devices, Manage Updates, and Final Review
6.1 Endpoint Security Policies and Security Baselines 6.2 Defender for Endpoint Integration and Onboarding 6.3 Update Rings, Feature Updates, Platform Updates, and Delivery Optimization 6.4 Final Seven-Day Review Plan and Mixed Scenario Priorities
3.1 Autopilot vs. Provisioning Packages
Key Takeaways Explain This Topic AI
Windows Autopilot is the better fit when devices can be registered with the Autopilot service and assigned an Intune deployment profile before first use.
Provisioning packages are local .ppkg files created with Windows Configuration Designer and are useful for bulk enrollment when devices are not pre-registered for Autopilot.
Autopilot profile assignment is device-centered, while most post-enrollment apps and settings can still be targeted to user groups, device groups, or both.
Windows bulk enrollment with a provisioning package is userless; the Microsoft Entra users who later sign in are standard users and receive assigned Intune policies and required apps.
A provisioning package can create a fragile state if domain join, scripts, certificates, or network assumptions are wrong, so it should be tested on disposable pilot devices first.
Last updated: June 2026
Choosing the deployment path
The Manage and maintain devices domain begins with a practical choice: should Windows be deployed through Windows Autopilot or through a provisioning package ? Both can get a corporate-owned Windows device into Microsoft Entra ID and Intune, but they solve different operational problems, and the exam phrasing usually points clearly to one.
Autopilot is a cloud deployment workflow. A device is registered with the Windows Autopilot deployment service, associated with the tenant, placed in a Microsoft Entra device group, and assigned an Autopilot profile. The profile controls the out-of-box experience (OOBE), join type, deployment mode, naming behavior, and enrollment flow. Critically, Autopilot reuses the OEM Windows installation rather than reimaging the device.
A provisioning package is a local .ppkg file, usually created with Windows Configuration Designer (WCD) . It can be applied from removable media or a network location during or after initial setup. In Intune bulk enrollment scenarios, the package joins new corporate-owned Windows devices to Microsoft Entra ID and enrolls them into Intune. It is local, immediate, and technician-applied rather than service-driven.
- Decision point Windows Autopilot Provisioning package
- Primary control plane Autopilot service and Intune profile Local .ppkg created with WCD
Device preparation Device registered by OEM, reseller, partner, automatic registration, or admin upload Package copied or made available locally
Best for New corporate PCs, remote delivery, standardized OOBE, profile-driven deployment Labs, kiosks, schools, bulk staging, devices not pre-registered for Autopilot
Assignment model Autopilot profile targets device groups; ESP can target device or user depending on scenario Bulk enrollment is userless; post-enrollment policy can target user or device groups
User state Usually one primary user in user-driven or pre-provisioned flows No primary user during enrollment; users sign in later
Risk area Missing registration, profile conflict, hybrid join connectivity, ESP blockers Expired bulk token, enrollment restriction, network dependency, risky scripts
What Autopilot gives you
Autopilot avoids traditional imaging. The device uses the Windows installation that already came from the OEM and then receives identity, enrollment, app, and policy configuration from cloud services. This is why Autopilot is the exam answer when a company wants to ship devices directly to remote employees without IT touching each device, and when a customized, guided corporate OOBE is required.
Autopilot also makes device assignment explicit. You normally assign a deployment profile to a Microsoft Entra device group, often a dynamic group that contains registered Autopilot devices. Required apps, compliance policies, configuration profiles, and security policies may be assigned separately to user groups or device groups. A frequent exam trap is assuming the Autopilot profile assigns apps; it does not. Apps must be assigned independently and can be tracked by the Enrollment Status Page.
What provisioning packages give you
A provisioning package is more local and more immediate. WCD can include a device name pattern, Wi-Fi settings, certificates, local settings, an edition upgrade key, apps, and a bulk enrollment token. Applying the package can restart the device, join it to Microsoft Entra ID, and enroll it into Intune.
For Intune bulk enrollment, remember these details:
The account used to request the bulk token must be allowed by the MDM user scope, and Windows automatic enrollment must be enabled.
The bulk token has a limited validity period and should be protected like a credential, because anyone with the package can enroll devices.
Bulk enrollment is userless, so only the default (All Users / All Devices) enrollment restriction applies during enrollment.
Microsoft Entra users who later sign in are standard users unless another policy or role grants more privileges.
Apps installed through a package are not the same as apps deployed and managed by Intune; managed updates and reporting come from Intune assignments, not the package.
Exam scenario cues
Pick Autopilot when the question mentions new devices purchased from an OEM, remote workers, a customized OOBE, pre-assigned deployment profiles, pre-provisioning by IT, or a need to reset a device to a business-ready state.
Pick provisioning packages when the question mentions WCD, .ppkg , USB staging, classrooms, kiosks, shared devices, no prior Autopilot registration, or bulk enrollment where a technician applies a package to many corporate-owned devices.
The safest exam habit is to identify the object being assigned. Autopilot deployment profiles are assigned to device groups . Provisioning packages are applied to devices directly . After the device is enrolled, Intune policies can be assigned to users or devices, and assignment filters can narrow the effective target. Because a bad provisioning package can leave a half-configured device, always test packages on disposable pilot hardware before mass staging.
When the question seems to allow both
Some scenarios technically permit either method, and the exam expects you to pick the one that best fits the operational constraints. If the devices come from an OEM that can register hardware hashes, ship to remote users, and need a standardized, low-touch experience, Autopilot is the cleaner answer because it scales without a technician at each device. If the devices are not registered with the Autopilot service, must be staged on-site by a technician, or need offline or air-gapped configuration from local media, a provisioning package fits better.
Watch for the word registered : if the hardware is already (or can be) registered with Autopilot, that strongly favors Autopilot; if the scenario stresses that devices are unregistered and a technician applies a file locally, that favors a provisioning package.
A related distractor is the suggestion to build a custom image and deploy it to each device. Modern MD-102 deployment is image-light: both Autopilot and provisioning packages start from the OEM Windows installation and layer cloud configuration on top. Unless a scenario explicitly requires a legacy task-sequence or Configuration Manager workflow, custom imaging is usually the wrong answer. Likewise, manual workgroup join followed by Company Portal enrollment is rarely the best choice for corporate fleets because it does not scale and skips the deployment profile entirely.
Finally, remember the post-enrollment picture is the same regardless of method. Once a device is Microsoft Entra joined and Intune enrolled, you target it with the same compliance policies, configuration profiles, security policies, and app assignments. The deployment method decides how the device arrives at that managed state; it does not change how you manage the device afterward.