Windows Autopilot

Windows Autopilot device preparation user-driven Microsoft Entra join - Step 5 of 7 - Assign applications and PowerShell scripts to device group

27 August 2026Doc update+7 / −6 lines

In brief

The tutorial now lists device association as an alternative to adding a Windows corporate identifier and clarifies the steps for deploying apps and PowerShell scripts.

What Intune admins need to know

Administrators have an additional documented setup path to follow when preparing devices; app and script assignments still target the designated device group.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

title: Windows Autopilot device preparation user-driven Microsoft Entra join - Step 5 of 7 - Assign applications and PowerShell scripts to device group description: How to - Windows Autopilot device preparation user-driven Microsoft Entra join - Step 5 of 7 - Assign applications and PowerShell scripts to device group. ms.date: ~~01/30/~~08/07/2026 ms.topic: tutorial appliesto:

✅ Windows 11
- Step 5: Assign applications and PowerShell scripts to device group
Step 6: Create Windows Autopilot device preparation policy
Step 7:7, option 1: Add Windows corporate identifier to device
Step 7, option 2: Associate devices

For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see Windows Autopilot device preparation user-driven Microsoft Entra join overview.

Any applications installed or PowerShell scripts that run during a Windows Autopilot device preparation deployment should be configured to install in the System context since the applications are installed and the PowerShell scripts ran during OOBE when no user is signed in.

For applications to install and PowerShell scripts ~~work~~to run successfully, they must be assigned to the device group created for Windows Autopilot device preparation in Step 3: Create an assigned device group.

For applications to install and PowerShell scripts ~~work~~to run successfully during a Windows Autopilot device preparation deployment, complete two ~~steps need to be taken:~~steps:

They must be assigned to the device group created for Windows Autopilot device preparation in Step 3: Create an assigned device group. This step is covered in this article.
They must be specified as part of the Windows Autopilot device preparation policy. This step is covered in the next step Step 5: Create Windows Autopilot device preparation policy.

Note
The below steps assume that the applications or PowerShell scripts that will be deployed during Windows Autopilot device preparation deployment are already added to Intune. For more information on how to add applications and PowerShell scripts to Intune if they aren't already created, see Add apps to Microsoft Intune
Note
The following steps assume that the applications or PowerShell scripts that will be deployed during Windows Autopilot device preparation deployment are already added to Intune. For more information on how to add applications and PowerShell scripts to Intune if they aren't already created, see Add apps to Microsoft Intune and Use PowerShell scripts on Windows devices in Intune.

Applications

Related content

~~Add apps to Microsoft Intune~~Add apps to Microsoft Intune.

Use PowerShell scripts on Windows devices in Intune.

Assign apps to groups with Microsoft Intune.

Win32 app management in Microsoft Intune.

@@ -1,7 +1,7 @@ --- title: Windows Autopilot device preparation user-driven Microsoft Entra join - Step 5 of 7 - Assign applications and PowerShell scripts to device group description: How to - Windows Autopilot device preparation user-driven Microsoft Entra join - Step 5 of 7 - Assign applications and PowerShell scripts to device group.-ms.date: 01/30/2026+ms.date: 08/07/2026 ms.topic: tutorial appliesto:   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>@@ -21,7 +21,8 @@ Windows Autopilot device preparation user-driven Microsoft Entra join steps: > - **Step 5: Assign applications and PowerShell scripts to device group**  - Step 6: [Create Windows Autopilot device preparation policy](entra-join-autopilot-policy.md)-- Step 7: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)+- Step 7, option 1: [Add Windows corporate identifier to device](entra-join-corporate-identifier.md)+- Step 7, option 2: [Associate devices](entra-join-device-association.md)  For an overview of the Windows Autopilot device preparation user-driven Microsoft Entra join workflow, see [Windows Autopilot device preparation user-driven Microsoft Entra join overview](entra-join-workflow.md#workflow). @@ -36,16 +37,16 @@ The applications and PowerShell scripts specified should be the essential applic  Any applications installed or PowerShell scripts that run during a Windows Autopilot device preparation deployment should be configured to install in the **System** context since the applications are installed and the PowerShell scripts ran during OOBE when no user is signed in. -For applications to install and PowerShell scripts work successfully, they must be assigned to the device group created for Windows Autopilot device preparation in [Step 3: Create an assigned device group](entra-join-device-group.md).+For applications to install and PowerShell scripts to run successfully, they must be assigned to the device group created for Windows Autopilot device preparation in [Step 3: Create an assigned device group](entra-join-device-group.md). -For applications to install and PowerShell scripts work successfully during a Windows Autopilot device preparation deployment, two steps need to be taken:+For applications to install and PowerShell scripts to run successfully during a Windows Autopilot device preparation deployment, complete two steps:  1. They must be assigned to the device group created for Windows Autopilot device preparation in [Step 3: Create an assigned device group](entra-join-device-group.md). This step is covered in this article. 2. They must be specified as part of the Windows Autopilot device preparation policy. This step is covered in the next step [Step 5: Create Windows Autopilot device preparation policy](entra-join-autopilot-policy.md).  > [!NOTE] >-> The below steps assume that the applications or PowerShell scripts that will be deployed during Windows Autopilot device preparation deployment are already added to Intune. For more information on how to add applications and PowerShell scripts to Intune if they aren't already created, see [Add apps to Microsoft Intune](/intune/app-management/deployment/index) and [Use PowerShell scripts on Windows devices in Intune](/intune/device-management/tools/management-extension-windows).+> The following steps assume that the applications or PowerShell scripts that will be deployed during Windows Autopilot device preparation deployment are already added to Intune. For more information on how to add applications and PowerShell scripts to Intune if they aren't already created, see [Add apps to Microsoft Intune](/intune/app-management/deployment/) and [Use PowerShell scripts on Windows devices in Intune](/intune/device-management/tools/management-extension-windows).  ### Applications @@ -134,7 +135,7 @@ To assign the desired PowerShell scripts to the device group created for Windows  ## Related content -- [Add apps to Microsoft Intune](/intune/app-management/deployment/index).+- [Add apps to Microsoft Intune](/intune/app-management/deployment/). - [Use PowerShell scripts on Windows devices in Intune](/intune/device-management/tools/management-extension-windows). - [Assign apps to groups with Microsoft Intune](/intune/app-management/deployment/assign-groups). - [Win32 app management in Microsoft Intune](/intune/app-management/deployment/win32).