Bulk Enrollment for Windows Devices - Microsoft Intune | Microsoft Learn
In brief
The article updates its title, description, wording, metadata date, and screenshot formatting. It also adds clearer visual guidance for device naming, product keys, and Wi-Fi setup.
What Intune admins need to know
Administrators using the guide get clearer instructions for creating Windows bulk-enrollment provisioning packages; no action is required.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Bulk enrollmentEnrollment for Windows devicesDevices - Microsoft Intune | Microsoft Learn
Join new Windows devices to Microsoft Entra ID and Intune. To bulk enroll devices for your Microsoft Entra tenant, you create a provisioning package withby using the Windows Configuration Designer (WCD) app. ApplyingWhen you apply the provisioning package to corporate-owned devices joinsdevices, you join the devices to your Microsoft Entra tenant and enrollsenroll them for Intune management. OnceAfter you apply the package is applied, it'spackage, the devices are ready for your Microsoft Entra users to sign in.
Microsoft Entra users are standard users on these devices and receive assigned Intune policies and required apps. Windows devices that are enrolled into Intune by using Windows bulk enrollment can use the Company Portal app to install available apps.
Requirements
Enable Windows automatic enrollment.
Make sure thatEnsure the service principal for Microsoft.Azure.SyncFabric (AppID 00000014-0000-0000-c000-000000000000) is present in your Microsoft Entra tenant. In a command line, use theGet-MgServicePrincipal -Filter "AppId eq '00000014-0000-0000-c000-000000000000'"command to check for the service principal. Without the service principal, Windows Configuration Designer can't retrieve the bulk enrollment token, which results in an error.To register the service principal, use the
New-MgServicePrincipal -AppId "00000014-0000-0000-c000-000000000000"command. To learn more about this command, see New-MgServicePrincipal.Password Administrator
For more
information about these roles,information, see Microsoft Entra built-in roles.
Important
Create a provisioning package
Install Windows Configuration Designer (WCD) from the Microsoft Store.
Open the Windows Configuration Designer app and select Provision desktop devices.

A New project window opens where you specify the following information:
- Name - A name for your project
- Project folder - Save location for the project
- Description - An optional description of the project


Enter a unique name for your devices. Names can include a serial number (%SERIAL%) or a random set of characters. Optionally,
you can alsoenter a product key if youare're upgrading the edition ofWindows,Windows. You can also configure the device for shareduse,use and removepre-installedpreinstalled software.
Optionally, you can configure the Wi-Fi network devices connect to when they first start. If the network devices aren't configured, a wired network connection is required when the device is first started.

Select Enroll in Azure AD, enter a Bulk Token Expiry date, and then select Get Bulk Token. The token validity period is 90 days.
Note
OnceAfter you create a provisioningpackage is created,package, you can revoke itcan be revokedbeforeits expirationit expires by removing the associatedpackage_{GUID}user account from Microsoft Entra ID.Due to the use of the package_{GUID} user account inBecause the bulk enrollmentprocess,process uses thepackage_{GUID}user account, tenants that use Conditional Access policies with MFA must set an exclusion or disable MFA for thisprocess, becauseprocess. MFAis notisn't supported for this scenario.Provide your Microsoft Entra credentials to get a bulk token.
Make sureEnsure you authenticate byway ofusing password or CBA authentication, since the app doesn't support other methods of authenticationaren't supported by the appfor this operation.
Note
- The account
usedyou use to request the bulk enrollment token in the Windows Configuration Designer app must be included in the MDM user scope in Microsoft Entra ID. If you remove this account from a group that's tied to the MDM user scope, bulk enrollmentwill stopstops working. - Bulk token retrieval
does notdoesn't work for federated user accounts enabled for staged rollouts.
- The account
In the Stay signed in to all your apps page, select No, sign in to this app only. If you keep the
check boxcheckbox selected andpress OK,select OK, the device youare're usingwill becomebecomes managed by your organization. If youdo notdon't intend for your device to be managed,make sure toselect No, sign in to this app only.ClickSelect Next when Bulk Token is fetched successfully.Optionally,
you canAdd applications and Add certificates.These appsThe app and certificates are provisioned on the device.Optionally,
you canpassword protect your provisioning package.ClickSelect Create.
Provision devices
Access the provisioning package in the location specified in Project folder
specifiedin the app.Choose how
you're goingto apply the provisioning package to the device.AYou can apply a provisioning packagecan be appliedto a device in one of the following ways:- Place the provisioning package on a USB drive, insert the USB drive into the device you
'd likewant to bulk enroll, and apply it during initialsetupsetup. - Place the provisioning package on a network folder, and apply it after initial
setupsetup.
For step-by-step
instructioninstructions on applying a provisioning package, see Apply a provisioning package.- Place the provisioning package on a USB drive, insert the USB drive into the device you
After you apply the package, the device
willautomaticallyrestartrestarts in one minute.
When the device restarts, it connects to
theMicrosoft Entra ID and enrolls in Microsoft Intune.
Troubleshooting Windows bulk enrollment
Provisioning issues
Provisioning is intended to be usedUse provisioning on new Windows devices. Provisioning failures might require a wipe of the device or device recovery from a boot image. These examples describe some reasons for provisioning failures:
- A provisioning package that attempts to join an Active Directory domain or Microsoft Entra tenant
that does notbut doesn't create a local account could make the device unreachable if the domain-join process fails due to lack of network connectivity. - Scripts run by the provisioning package
arerun in system context. The scriptsare able tocan make arbitrary changes to the device file system and configurations. A malicious or bad script could put the device in a state that can only be recovered by reimaging or wiping the device.
You can checkCheck for success/success or failure of the settings in your package in the Provisioning-Diagnostics-Provider Admin log in Event Viewer.
Note
Bulk enrollment is considered a userless enrollment method, and becausemethod. Because of it,this characteristic, only the "Default" enrollment restriction in Intune would applyapplies during enrollment. Make sureEnsure Windows platform is allowed in the default restriction,restriction; otherwise, the enrollment will fail.fails. To check the capabilities alongside other Windows enrollment methods, see Intune enrollment method capabilities for Windows devices.
Bulk enrollment with Wi-Fi
When not usingyou don't use an open network, you must use device-level certificates to initiate connections. Bulk enrolled devices are unable tocan't use to user-targeted certificates for network access.
Conditional Access
Conditional Access is available for devices enrolled viaby using bulk enrollment running Windows 11 or Windows 10, version 1803 and later.
Important
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Bulk enrollment for Windows devices - Microsoft Intune | Microsoft Learn+title: Bulk Enrollment for Windows Devices - Microsoft Intune | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/device-enrollment/windows/create-bulk-package author: maholdaa ms.author: maholdaa@@ -11,8 +11,8 @@ ms.service: microsoft-intune ms.collection: - M365-identity-device-management ms.subservice: enrollment-description: Create a bulk enrollment package for Microsoft Intune-ms.date: 2025-09-29T00:00:00.0000000Z+description: Windows bulk enrollment lets you join corporate devices to Microsoft Entra ID and Intune at scale. Create a provisioning package and start enrolling.+ms.date: 2026-11-05T00:00:00.0000000Z ms.topic: how-to locale: en-us document_id: 2f7a3d73-6b8d-29dd-6ead-2f658936709a@@ -42,11 +42,11 @@ spProducts: platformId: adde4fd5-06b5-6111-25e2-96c97fe00ce4 --- -# Bulk enrollment for Windows devices - Microsoft Intune | Microsoft Learn+# Bulk Enrollment for Windows Devices - Microsoft Intune | Microsoft Learn -Join new Windows devices to Microsoft Entra ID and Intune. To bulk enroll devices for your Microsoft Entra tenant, you create a provisioning package with the Windows Configuration Designer (WCD) app. Applying the provisioning package to corporate-owned devices joins the devices to your Microsoft Entra tenant and enrolls them for Intune management. Once the package is applied, it's ready for your Microsoft Entra users to sign in.
+Join new Windows devices to Microsoft Entra ID and Intune. To bulk enroll devices for your Microsoft Entra tenant, create a provisioning package by using the Windows Configuration Designer (WCD) app. When you apply the provisioning package to corporate-owned devices, you join the devices to your Microsoft Entra tenant and enroll them for Intune management. After you apply the package, the devices are ready for your Microsoft Entra users to sign in.
-Microsoft Entra users are standard users on these devices and receive assigned Intune policies and required apps. Windows devices that are enrolled into Intune using Windows bulk enrollment can use the Company Portal app to install available apps.
+Microsoft Entra users are standard users on these devices and receive assigned Intune policies and required apps. Windows devices that are enrolled into Intune by using Windows bulk enrollment can use the Company Portal app to install available apps.
## Requirements
@@ -62,7 +62,7 @@ Microsoft Entra users are standard users on these devices and receive assigned I
>
> - Enable [Windows automatic enrollment](enable-automatic-mdm#enable-windows-automatic-enrollment).
-> - Make sure that the service principal for Microsoft.Azure.SyncFabric (AppID 00000014-0000-0000-c000-000000000000) is present in your Microsoft Entra tenant. In a command line, use the `Get-MgServicePrincipal -Filter "AppId eq '00000014-0000-0000-c000-000000000000'"` command to check for the [service principal](/en-us/entra/identity-platform/developer-glossary#service-principal-object). Without the service principal, Windows Configuration Designer can't retrieve the bulk enrollment token, which results in an error.
+> - Ensure the service principal for Microsoft.Azure.SyncFabric (AppID 00000014-0000-0000-c000-000000000000) is present in your Microsoft Entra tenant. In a command line, use the `Get-MgServicePrincipal -Filter "AppId eq '00000014-0000-0000-c000-000000000000'"` command to check for the [service principal](/en-us/entra/identity-platform/developer-glossary#service-principal-object). Without the service principal, Windows Configuration Designer can't retrieve the bulk enrollment token, which results in an error.
>
> To register the service principal, use the `New-MgServicePrincipal -AppId "00000014-0000-0000-c000-000000000000"` command. To learn more about this command, see [New-MgServicePrincipal](/en-us/powershell/module/microsoft.graph.applications/new-mgserviceprincipal).
>
@@ -77,7 +77,7 @@ Microsoft Entra users are standard users on these devices and receive assigned I > - Password Administrator
>
>
-> For more information about these roles, see [Microsoft Entra built-in roles](/en-us/entra/identity/role-based-access-control/permissions-reference).
+> For more information, see [Microsoft Entra built-in roles](/en-us/entra/identity/role-based-access-control/permissions-reference).
Important
@@ -86,68 +86,80 @@ On October 14, 2025, [Windows 10 reached end of support](/en-us/lifecycle/announ ## Create a provisioning package
1. Install [Windows Configuration Designer (WCD)](https://www.microsoft.com/p/windows-configuration-designer/9nblggh4tx22) from the Microsoft Store.
-2. Open the **Windows Configuration Designer** app and select **Provision desktop devices**. 
+2. Open the **Windows Configuration Designer** app and select **Provision desktop devices**.
+
+ 
3. A **New project** window opens where you specify the following information:
- **Name** - A name for your project
- **Project folder** - Save location for the project
- - **Description** - An optional description of the project 
-4. Enter a unique name for your devices. Names can include a serial number (%SERIAL%) or a random set of characters. Optionally, you can also enter a product key if you are upgrading the edition of Windows, configure the device for shared use, and remove pre-installed software.
+ - **Description** - An optional description of the project
+
+ 
+4. Enter a unique name for your devices. Names can include a serial number (%SERIAL%) or a random set of characters. Optionally, enter a product key if you're upgrading the edition of Windows. You can also configure the device for shared use and remove preinstalled software.
+
+ 
+5. Optionally, you can configure the Wi-Fi network devices connect to when they first start. If the network devices aren't configured, a wired network connection is required when the device is first started.
- 
-5. Optionally, you can configure the Wi-Fi network devices connect to when they first start. If the network devices aren't configured, a wired network connection is required when the device is first started. 
+ 
6. Select **Enroll in Azure AD**, enter a **Bulk Token Expiry** date, and then select **Get Bulk Token**. The token validity period is 90 days.
Note
- Once a provisioning package is created, it can be revoked before its expiration by removing the associated package\_{GUID} user account from Microsoft Entra ID.
+ After you create a provisioning package, you can revoke it before it expires by removing the associated `package_{GUID}` user account from Microsoft Entra ID.
- Due to the use of the package\_{GUID} user account in the bulk enrollment process, tenants that use Conditional Access policies with MFA must set an exclusion or disable MFA for this process, because MFA is not supported for this scenario.
-7. Provide your Microsoft Entra credentials to get a bulk token. Make sure you authenticate by way of password or CBA authentication, since other methods of authentication aren't supported by the app for this operation.
+ Because the bulk enrollment process uses the `package_{GUID}` user account, tenants that use Conditional Access policies with MFA must set an exclusion or disable MFA for this process. MFA isn't supported for this scenario.
+7. Provide your Microsoft Entra credentials to get a bulk token. Ensure you authenticate by using password or CBA authentication, since the app doesn't support other methods of authentication for this operation.
+
+ 
Note
- - The account used to request the bulk enrollment token in the Windows Configuration Designer app must be included in the [MDM user scope](enable-automatic-mdm#enable-windows-automatic-enrollment) in Microsoft Entra ID. If you remove this account from a group that's tied to the MDM user scope, bulk enrollment will stop working.
- - Bulk token retrieval does not work for federated user accounts enabled for staged rollouts.
-8. In the **Stay signed in to all your apps** page, select **No, sign in to this app only**. If you keep the check box selected and press OK, the device you are using will become managed by your organization. If you do not intend for your device to be managed, make sure to select **No, sign in to this app only**.
-9. Click **Next** when **Bulk Token** is fetched successfully.
-10. Optionally, you can **Add applications** and **Add certificates**. These apps and certificates are provisioned on the device.
-11. Optionally, you can password protect your provisioning package. Click **Create**. 
+ - The account you use to request the bulk enrollment token in the Windows Configuration Designer app must be included in the [MDM user scope](enable-automatic-mdm#enable-windows-automatic-enrollment) in Microsoft Entra ID. If you remove this account from a group that's tied to the MDM user scope, bulk enrollment stops working.
+ - Bulk token retrieval doesn't work for federated user accounts enabled for staged rollouts.
+8. In the **Stay signed in to all your apps** page, select **No, sign in to this app only**. If you keep the checkbox selected and select **OK**, the device you're using becomes managed by your organization. If you don't intend for your device to be managed, select **No, sign in to this app only**.
+9. Select **Next** when **Bulk Token** is fetched successfully.
+10. Optionally, **Add applications** and **Add certificates**. The app and certificates are provisioned on the device.
+11. Optionally, password protect your provisioning package. Select **Create**.
+
+ 
## Provision devices
-1. Access the provisioning package in the location specified in **Project folder** specified in the app.
-2. Choose how you're going to apply the provisioning package to the device. A provisioning package can be applied to a device one of the following ways:
+1. Access the provisioning package in the location specified in **Project folder** in the app.
+2. Choose how to apply the provisioning package to the device. You can apply a provisioning package to a device in one of the following ways:
+
+ - Place the provisioning package on a USB drive, insert the USB drive into the device you want to bulk enroll, and apply it during initial setup.
+ - Place the provisioning package on a network folder, and apply it after initial setup.
- - Place the provisioning package on a USB drive, insert the USB drive into the device you'd like to bulk enroll, and apply it during initial setup
- - Place the provisioning package on a network folder, and apply it after initial setup
+ For step-by-step instructions on applying a provisioning package, see [Apply a provisioning package](/en-us/windows/configuration/provisioning-packages/provisioning-apply-package).
+3. After you apply the package, the device automatically restarts in one minute.
- For step-by-step instruction on applying a provisioning package, see [Apply a provisioning package](/en-us/windows/configuration/provisioning-packages/provisioning-apply-package).
-3. After you apply the package, the device will automatically restart in one minute. 
-4. When the device restarts, it connects to the Microsoft Entra ID and enrolls in Microsoft Intune.
+ 
+4. When the device restarts, it connects to Microsoft Entra ID and enrolls in Microsoft Intune.
## Troubleshooting Windows bulk enrollment
### Provisioning issues
-Provisioning is intended to be used on new Windows devices. Provisioning failures might require a wipe of the device or device recovery from a boot image. These examples describe some reasons for provisioning failures:
+Use provisioning on new Windows devices. Provisioning failures might require a wipe of the device or device recovery from a boot image. These examples describe some reasons for provisioning failures:
-- A provisioning package that attempts to join an Active Directory domain or Microsoft Entra tenant that does not create a local account could make the device unreachable if the domain-join process fails due to lack of network connectivity.
-- Scripts run by the provisioning package are run in system context. The scripts are able to make arbitrary changes to the device file system and configurations. A malicious or bad script could put the device in a state that can only be recovered by reimaging or wiping the device.
+- A provisioning package that attempts to join an Active Directory domain or Microsoft Entra tenant but doesn't create a local account could make the device unreachable if the domain-join process fails due to lack of network connectivity.
+- Scripts run by the provisioning package run in system context. The scripts can make arbitrary changes to the device file system and configurations. A malicious or bad script could put the device in a state that can only be recovered by reimaging or wiping the device.
-You can check for success/failure of the settings in your package in the **Provisioning-Diagnostics-Provider** Admin log in Event Viewer.
+Check for success or failure of the settings in your package in the **Provisioning-Diagnostics-Provider** Admin log in Event Viewer.
Note
-Bulk enrollment is considered a userless enrollment method, and because of it, only the "Default" enrollment restriction in Intune would apply during enrollment. Make sure Windows platform is allowed in the default restriction, otherwise, the enrollment will fail. To check the capabilities alongside other Windows enrollment methods, see [Intune enrollment method capabilities for Windows devices](guide).
+Bulk enrollment is a userless enrollment method. Because of this characteristic, only the **Default** enrollment restriction in Intune applies during enrollment. Ensure Windows platform is allowed in the default restriction; otherwise, the enrollment fails. To check the capabilities alongside other Windows enrollment methods, see [Intune enrollment method capabilities for Windows devices](guide).
### Bulk enrollment with Wi-Fi
-When not using an open network, you must use [device-level certificates](../../fundamentals/certificates/overview) to initiate connections. Bulk enrolled devices are unable to use to user-targeted certificates for network access.
+When you don't use an open network, use [device-level certificates](../../fundamentals/certificates/overview) to initiate connections. Bulk enrolled devices can't use user-targeted certificates for network access.
### Conditional Access
-Conditional Access is available for devices enrolled via bulk enrollment running Windows 11 or Windows 10, version 1803 and later.
+Conditional Access is available for devices enrolled by using bulk enrollment running Windows 11 or Windows 10, version 1803 and later.
Important