Software
In brief
The page received metadata, wording, and formatting updates. RSS guidance and requirement labels were rephrased, while the listed Windows 11 versions and KB references were reformatted.
What Intune admins need to know
Use the updated page when reviewing device preparation prerequisites; no administrator action is indicated.
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.
permissioned-type: public
uhfHeaderId: MSDocsHeader-Windows
description: Software, Networking, Licensing, Configuration, and RBAC requirements for Windows Autopilot device preparation.
ms.date: 2025-06-11T00:2026-10-28T00:00:00.0000000Z
ms.collection:
- M365-modern-desktop ms.topic: article ms.custom:
- CI 116757
Tip
Use RSS can be used to notifyget notified when requirements are added or updated to this page.article is updated. For example, the following RSS link includes this article:
https://learn.microsoft.com/api/search/rss?search=%22Software%2C+Networking%2C+Licensing%2C+Configuration%2C+and+RBAC+requirements+for+Windows+Autopilot+device%22&locale=en-us&%24filter=
This example includes the &locale=en-us variable. The locale variable is required, but you can change it can be changedto another supported locale. For example, &locale=es-es.
For more information onabout using RSS for notifications, see How to use the docs in the Intune documentation.
The list of requirements for Windows Autopilot device preparation is organized into five different categories:
- Software
- OS requirements.: operating system requirements - Networking
-: networkingrequirements.requirements - Licensing
-: licensingrequirements.requirements - Configuration
-: configurations required in Microsoft Entra ID and MicrosoftIntune.Intune - RBAC
-: RBAC permissions required for a Windows Autopilot device preparationadministrator.administrator
Select the appropriate tab to see the relevant requirements:
Software
Software requirements
Windows Autopilot device preparation depends on specific features available in Windows client, Microsoft Entra ID, and a mobile device management (MDM) service such as Microsoft Intune. To use Windows Autopilot device preparation and access these features, someyou must meet software requirements must be met.requirements.
Windows 11
- Windows 11, version 24H2 or later.
- Windows 11, version 23H2 with KB5035942 or
later -later, Windows 11, version 23H2 installation media dated April 2024 or later has KB5035942 included. - Windows 11, version 22H2 with KB5035942 or
later -later, Windows 11, version 22H2 installation media dated April 2024 or later has KB5035942 included.
Important
Windows 365 Cloud PCs
- Windows 11, version 24H2 with KB5052093 or
later -later. The Windows 11, version 24H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5052093.However when creatingWhen you create custom images, make sure to use Windows 11, version 24H2 installation media dated March 2025 or later which has KB5052093 included. - Windows 11, version 23H2 with KB5035942 or
later -later. The Windows 11, version 23H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942.However when creatingWhen you create custom images, make sure to use Windows 11, version 23H2 installation media dated March 2025 or later which has KB5035942 included. - Windows 11, version 22H2 with KB5035942 or
later -later. The Windows 11, version 22H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942.However when creatingWhen you create custom images, make sure to use Windows 11, version 22H2 installation media dated March 2025 or later which has KB5035942 included.
The following editions are supported:
Networking
Networking requirements
Windows Autopilot device preparation depends on various internet-based services. AccessYou must provide access to these services must be provided for Windows Autopilot device preparation to function properly. In the simplest case, enabling proper functionality can be achieved by ensuringensure the following conditions:
Ensure Domain Name Services (DNS)DNS name resolution for internet DNS names.Allow accessAccess to all hostsviausing port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP).
Additional configurationYou might be requiredneed to configure additional settings to grant access to required services in environments that:
- Have more restrictive internet access.
- Require authentication before internet access can be obtained.
Note
Smart card and certificate based authentication isnaren't supported during the out-of-box experience (OOBE). For more information, see Smartcards and certificate-based authentication.
Service requirements
Windows Autopilot device preparation relies on several different typetypes of services to function properly. In orderYou might need to perform certain network configurations for these services to function properly, certain network configurations might need to be performed.properly. These services and their required network configurations are as follows:follows.
Windows Autopilot deployment service
After a network connection is in place, each Windows device will contactcontacts the Windows Autopilot deployment service. The following URLs are used:
https://login.live.com
Microsoft Entra ID
Microsoft Entra ID validates user credentials. Additionally,Also, the device is joined to Microsoft Entra ID during Windows Autopilot device preparation. For more information, see Office 365 IP Address and URL Web service.
Microsoft Intune
Once authenticated,After it authenticates, Microsoft Entra ID triggers enrollment of the device into the Intune mobile device management (MDM) service. For more information about Intune's network communication requirements, see the following articles:
Windows Autopilot device preparation automatic device diagnostics collection
For diagnostics to be able to upload successfully from the client, make sureensure that the URL lgmsapeweu.blob.core.windows.net isn't blocked on the network. Diagnostics are available for 28 days before they're removed.
For more information, see Collect diagnostics from a Windows device.
Windows Update
During the out-of-box experience (OOBE) process and after the Windows OS configuration, the Windows Update service retrievesgets needed updates. If there are problems connecting to Windows Update, see Windows Update issues troubleshooting.
If Windows Update is inaccessible, the Windows Autopilot device preparation process still continues but critical updates aren't available.
Windows Autopilot device preparation contacts the Delivery Optimization service when downloading the applications and updates. This contact establishes peer-to-peer sharing of content so that only a few devices need to download it from the internet.
- Windows
Updates.Updates - Microsoft Store applications and application
updates.updates - Office
Updates.Updates - Intune Win32
Applications.Applications
If the Delivery Optimization Service is inaccessible, the Windows Autopilot process still continues with Delivery Optimization downloads from the cloud without peer-to-peer.
Network Time Protocol (NTP) sync
Domain Name Services (DNS)
To resolve internet names for all services, the device communicates with a DNS server, typically provided viaby using DHCP. This DNS server must be able to resolve internet names.
Diagnostics data
Diagnostic data collection is enabled by default. For more information, see Manage enterprise diagnostic data.
If the device can't send diagnostic data, the Windows Autopilot device preparation process still continues. However, servicesServices that depend on diagnostic data don't work.
Network Connection Status Indicator (NCSI)
Windows must be able to tell that the device can access the internet. For more information, see Network Connection Status Indicator (NCSI).
*.msftconnecttest.com must be resolvable via DNS and accessible viaby using HTTP.
Windows Notification Services (WNS)
This service is used to enable Windows to receive notifications from applications and services. For more information, see Microsoft Store.
If the WNS services aren't available, the Windows Autopilot device preparation process still continues without notifications.
Microsoft Store
Applications in the Microsoft Store can be pushed to the device by triggering them viaby using Intune or otheranother MDM service. App updates and additional applications might also be needed when the user first logs in. For more information, see Update to Intune integration with the Microsoft Store on Windows and FAQ: Supporting Microsoft Store experiences on managed devices.
If the Microsoft Store isn't accessible, the Windows Autopilot process still continues without Microsoft Store applications.
Microsoft 365
As part of the Intune device configuration, installation ofyou might need to install Microsoft 365 Applications for enterprise might be required.Enterprise. For a list that includes allof Office services, DNS names, IP addresses, including Microsoft Entra ID and other services that might overlap with the previously listed services, see Microsoft 365 URLs and IP address ranges.
Certificate revocation lists (CRLs)
Some of these services also need to check certificate revocation lists (CRLs) for certificates used in the services. For a full list, see Microsoft 365 URLs and IP address ranges and Microsoft 365 Certificate Chains.
Proxy settings
Deploying proxy settings for Windows Autopilot device preparation should be configured on the proxy server itself. Implementing proxy settings viaby using Intune policy isn't fully supported as itsupported. It might cause issues and unexpected behavior with privileged access deployments.
Licensing
Licensing requirements
Windows Autopilot device preparation depends on specific capabilities available in Windows client and Microsoft Entra ID. It also requires a mobile device management (MDM) service such as Microsoft Intune. TheseYou can get these capabilities can be obtained through various editions and subscription programs.
To provide the needed Microsoft Entra ID and MDM functionality, including automatic MDM enrollment and company branding features, you need one of the following subscriptions is required:subscriptions:
- Microsoft 365 Business Premium subscription
. - Microsoft 365 F1 or F3 subscription
. - Microsoft 365 Academic A1, A3, or A5 subscription
. - Microsoft 365 Enterprise E3 or E5 subscription, which include all Windows client, Microsoft 365, and EMS features (Microsoft Entra ID and Intune)
. - Enterprise Mobility + Security E3 or E5 subscription, which include all needed Microsoft Entra ID and Intune
features.features - Intune for Education subscription, which include all needed Microsoft Entra ID and Intune
features.features - Microsoft Entra ID P1 or P2 and Microsoft Intune subscription or an alternative MDM
service.service
Note
When you use a Microsoft 365 subscription is used, licensessubscription, you still need to be assignedassign licenses to users so they can enroll devicedevices in Intune. For more information, see assign licenses to users so they can enroll devices in Intune.
Additionally,We recommend the following are also recommended, but not required:resources:
- Microsoft 365 Apps for enterprise
-. You can deploy Microsoft 365ApplicationsApps for enterprisecan be deployedeasilyviaby using Intune orotheranother MDM service. - Windows Subscription Activation
- automatically step. Step up devices from Windows Pro to Windows Enterprise edition.
Configuration
Configuration requirements
Before you can use Windows Autopilot device preparation can be used, somepreparation, complete the following configuration tasks are required to support the common Windows Autopilot device preparation scenarios.
- Configure Microsoft Entra automatic enrollment. For Microsoft Intune, see Set up Windows automatic Intune enrollment and Enable Windows automatic enrollment for details.
If usingTo use a different mobile device management (MDM) service, contact the vendor for the specific URLs or configuration needed for those services. - The first user that signs in needs to have Microsoft Entra join permissions. For more information, see Allow users to join devices to Microsoft Entra ID.
TheWe recommend the following configurations are optional but recommended. They aren't required:configurations:
- Automatically step up from Windows Pro to Windows Enterprise. For more information, see Windows Subscription Activation.
There are no additional hardware requirements to use Windows Autopilot device preparation, beyond the hardware requirements to run Windows. For more information, see:
- Find Windows 11 specs, features, and computer requirements
. - Windows minimum hardware requirements
. - Windows 11 requirements
.
RBAC
Required RBAC permissions
To create a custom role with these permissions for use with Windows Autopilot device preparation:
Sign in to the Microsoft Intune admin center.
In the Home screen, in the left pane, select Tenant administration
in the left hand pane..In the Tenant admin | Tenant status screen, select Roles.
In the Endpoint Manager roles | All roles screen, make sure All roles is selected under Manage.
Select
theCreatedrop down menuand then select Intune role. The Add Custom Role screen opens.In the Add Custom Role screen:
In the Basics page:
- Name
- enter. Enter a name for the custom role, such as Windows Autopilot device preparation administrator. - Description
- enter. Enter a description for the custom role.
- Name
Select Next.
In the Permissions page, under Select a category below to configure settings.,
scroll through the list tofind the following settings.Once the setting is located,After you find a setting, expand it, and then change to the following permissions:Device configurations
- Read: Yes
All other permissions can be left at the default of No.
OnceWhen all permissions are set correctly, select Next.In the Scope tags page, select Next.
Note
Scope tags are optional. If you need to specify a custom scope
tag needs to be specified, do so attag, add it on this page. For more information about scope tags, see Use role-based access control and scope tags for distributed IT.In the Review + create page, verify that all permissions are correct, and then select Create.
TheAssign the new custom Windows Autopilot device preparation rolecan now be assignedto users who administer Windows Autopilot device preparation.
For more information, see Role-based access control (RBAC) with Microsoft Intune.
@@ -15,9 +15,8 @@ feedback_system: Standard permissioned-type: public uhfHeaderId: MSDocsHeader-Windows description: Software, Networking, Licensing, Configuration, and RBAC requirements for Windows Autopilot device preparation.-ms.date: 2025-06-11T00:00:00.0000000Z-ms.collection:-- M365-modern-desktop+ms.date: 2026-10-28T00:00:00.0000000Z+ms.collection: M365-modern-desktop ms.topic: article ms.custom: - CI 116757@@ -53,36 +52,36 @@ platformId: 729abfa5-a5e6-f6e6-2f08-c9638484d2d9 Tip
-RSS can be used to notify when requirements are added or updated to this page. For example, the following RSS link includes this article:
+Use RSS to get notified when this article is updated. For example, the following RSS link includes this article:
```url
https://learn.microsoft.com/api/search/rss?search=%22Software%2C+Networking%2C+Licensing%2C+Configuration%2C+and+RBAC+requirements+for+Windows+Autopilot+device%22&locale=en-us&%24filter=
```
-This example includes the `&locale=en-us` variable. The `locale` variable is required, but it can be changed another supported locale. For example, `&locale=es-es`.
+This example includes the `&locale=en-us` variable. The `locale` variable is required, but you can change it to another supported locale. For example, `&locale=es-es`.
-For more information on using RSS for notifications, see [How to use the docs](/en-us/intune/use-docs#notifications) in the Intune documentation.
+For more information about using RSS for notifications, see [How to use the docs](/en-us/intune/use-docs#notifications) in the Intune documentation.
The list of requirements for Windows Autopilot device preparation is organized into five different categories:
-- **Software** - OS requirements.
-- **Networking** - networking requirements.
-- **Licensing** - licensing requirements.
-- **Configuration** - configurations required in Microsoft Entra ID and Microsoft Intune.
-- **RBAC** - RBAC permissions required for a Windows Autopilot device preparation administrator.
+- **Software**: operating system requirements
+- **Networking**: networking requirements
+- **Licensing**: licensing requirements
+- **Configuration**: configurations required in Microsoft Entra ID and Microsoft Intune
+- **RBAC**: RBAC permissions required for a Windows Autopilot device preparation administrator
Select the appropriate tab to see the relevant requirements:
# [Software](#tab/software)
### Software requirements
-Windows Autopilot device preparation depends on specific features available in Windows client, Microsoft Entra ID, and a mobile device management (MDM) service such as Microsoft Intune. To use Windows Autopilot device preparation and access these features, some software requirements must be met.
+Windows Autopilot device preparation depends on specific features available in Windows client, Microsoft Entra ID, and a mobile device management (MDM) service such as Microsoft Intune. To use Windows Autopilot device preparation and access these features, you must meet software requirements.
#### Windows 11
- Windows 11, version 24H2 or later.
-- Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - Windows 11, version 23H2 installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
-- Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - Windows 11, version 22H2 installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
+- Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later, Windows 11, version 23H2 installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
+- Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later, Windows 11, version 22H2 installation media dated April 2024 or later has [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) included.
Important
@@ -91,9 +90,9 @@ Important
#### Windows 365 Cloud PCs
-- Windows 11, version 24H2 with [KB5052093](https://support.microsoft.com/en-us/topic/february-25-2025-kb5052093-os-build-26100-3323-preview-053856ea-f984-4bdb-866c-5f356f5a451b) or later - The Windows 11, version 24H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5052093. However when creating custom images, make sure to use Windows 11, version 24H2 installation media dated March 2025 or later which has KB5052093 included.
-- Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - The Windows 11, version 23H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942. However when creating custom images, make sure to use Windows 11, version 23H2 installation media dated March 2025 or later which has KB5035942 included.
-- Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later - The Windows 11, version 22H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942. However when creating custom images, make sure to use Windows 11, version 22H2 installation media dated March 2025 or later which has KB5035942 included.
+- Windows 11, version 24H2 with [KB5052093](https://support.microsoft.com/en-us/topic/february-25-2025-kb5052093-os-build-26100-3323-preview-053856ea-f984-4bdb-866c-5f356f5a451b) or later. The Windows 11, version 24H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5052093. When you create custom images, make sure to use Windows 11, version 24H2 installation media dated March 2025 or later which has KB5052093 included.
+- Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later. The Windows 11, version 23H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942. When you create custom images, make sure to use Windows 11, version 23H2 installation media dated March 2025 or later which has KB5035942 included.
+- Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later. The Windows 11, version 22H2 images in the Windows 365 image gallery are updated with the latest updates, including KB5035942. When you create custom images, make sure to use Windows 11, version 22H2 installation media dated March 2025 or later which has KB5035942 included.
The following editions are supported:
@@ -107,27 +106,27 @@ The following editions are supported: # [Networking](#tab/networking)
### Networking requirements
-Windows Autopilot device preparation depends on various internet-based services. Access to these services must be provided for Windows Autopilot device preparation to function properly. In the simplest case, enabling proper functionality can be achieved by ensuring the following conditions:
+Windows Autopilot device preparation depends on various internet-based services. You must provide access to these services for Windows Autopilot device preparation to function properly. In the simplest case, ensure the following conditions:
-- Ensure Domain Name Services (DNS) name resolution for internet DNS names.
-- Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP).
+- DNS name resolution for internet DNS names.
+- Access to all hosts using port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP).
-Additional configuration might be required to grant access to required services in environments that:
+You might need to configure additional settings to grant access to required services in environments that:
- Have more restrictive internet access.
- Require authentication before internet access can be obtained.
Note
-Smart card and certificate based authentication isn't supported during the out-of-box experience (OOBE). For more information, see [Smartcards and certificate-based authentication](/en-us/azure/active-directory/devices/azureadjoin-plan#smartcards-and-certificate-based-authentication).
+Smart card and certificate based authentication aren't supported during the out-of-box experience (OOBE). For more information, see [Smartcards and certificate-based authentication](/en-us/azure/active-directory/devices/azureadjoin-plan#smartcards-and-certificate-based-authentication).
#### Service requirements
-Windows Autopilot device preparation relies on several different type of services to function properly. In order for these services to function properly, certain network configurations might need to be performed. These services and their required network configurations are as follows:
+Windows Autopilot device preparation relies on several different types of services to function properly. You might need to perform certain network configurations for these services to function properly. These services and their required network configurations are as follows.
#### Windows Autopilot deployment service
-After a network connection is in place, each Windows device will contact the Windows Autopilot deployment service. The following URLs are used:
+After a network connection is in place, each Windows device contacts the Windows Autopilot deployment service. The following URLs are used:
- `https://login.live.com`
@@ -137,24 +136,24 @@ Windows Autopilot device preparation requires Windows Activation services. For m
#### Microsoft Entra ID
-Microsoft Entra ID validates user credentials. Additionally, the device is joined to Microsoft Entra ID during Windows Autopilot device preparation. For more information, see [Office 365 IP Address and URL Web service](/en-us/microsoft-365/enterprise/microsoft-365-ip-web-service).
+Microsoft Entra ID validates user credentials. Also, the device is joined to Microsoft Entra ID during Windows Autopilot device preparation. For more information, see [Office 365 IP Address and URL Web service](/en-us/microsoft-365/enterprise/microsoft-365-ip-web-service).
#### Microsoft Intune
-Once authenticated, Microsoft Entra ID triggers enrollment of the device into the Intune mobile device management (MDM) service. For more information about Intune's network communication requirements, see the following articles:
+After it authenticates, Microsoft Entra ID triggers enrollment of the device into the Intune mobile device management (MDM) service. For more information about Intune's network communication requirements, see the following articles:
-- [Network endpoints for Microsoft Intune](/en-us/intune/fundamentals/endpoints).
-- [Network requirements for PowerShell scripts and Win32 apps](/en-us/intune/fundamentals/endpoints).
+- [Network endpoints for Microsoft Intune](/en-us/intune/fundamentals/endpoints)
+- [Network requirements for PowerShell scripts and Win32 apps](/en-us/intune/fundamentals/endpoints)
#### Windows Autopilot device preparation automatic device diagnostics collection
-For diagnostics to be able to upload successfully from the client, make sure that the URL `lgmsapeweu.blob.core.windows.net` isn't blocked on the network. Diagnostics are available for 28 days before they're removed.
+For diagnostics to upload successfully from the client, ensure that the URL `lgmsapeweu.blob.core.windows.net` isn't blocked on the network. Diagnostics are available for 28 days before they're removed.
For more information, see [Collect diagnostics from a Windows device](/en-us/intune/device-management/actions/collect-diagnostics).
#### Windows Update
-During the out-of-box experience (OOBE) process and after the Windows OS configuration, the Windows Update service retrieves needed updates. If there are problems connecting to Windows Update, see [Windows Update issues troubleshooting](/en-us/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting).
+During the out-of-box experience (OOBE) process and after the Windows OS configuration, the Windows Update service gets needed updates. If there are problems connecting to Windows Update, see [Windows Update issues troubleshooting](/en-us/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting).
If Windows Update is inaccessible, the Windows Autopilot device preparation process still continues but critical updates aren't available.
@@ -162,12 +161,12 @@ If Windows Update is inaccessible, the Windows Autopilot device preparation proc
Windows Autopilot device preparation contacts the [Delivery Optimization](/en-us/windows/deployment/update/waas-delivery-optimization) service when downloading the applications and updates. This contact establishes peer-to-peer sharing of content so that only a few devices need to download it from the internet.
-- Windows Updates.
-- Microsoft Store applications and application updates.
-- Office Updates.
-- Intune Win32 Applications.
+- Windows Updates
+- Microsoft Store applications and application updates
+- Office Updates
+- Intune Win32 Applications
-If the Delivery Optimization Service is inaccessible, the Windows Autopilot process still continues with Delivery Optimization downloads from the cloud without peer-to-peer.
+If the Delivery Optimization Service is inaccessible, the Windows Autopilot process continues with Delivery Optimization downloads from the cloud without peer-to-peer.
#### Network Time Protocol (NTP) sync
@@ -175,85 +174,85 @@ When a Windows device starts up, it talks to a network time server to ensure tha
#### Domain Name Services (DNS)
-To resolve internet names for all services, the device communicates with a DNS server, typically provided via DHCP. This DNS server must be able to resolve internet names.
+To resolve internet names for all services, the device communicates with a DNS server, typically provided by using DHCP. This DNS server must be able to resolve internet names.
#### Diagnostics data
Diagnostic data collection is enabled by default. For more information, see [Manage enterprise diagnostic data](/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization#manage-diagnostic-data-using-group-policy-and-mdm).
-If the device can't send diagnostic data, the Windows Autopilot device preparation process still continues. However, services that depend on diagnostic data don't work.
+If the device can't send diagnostic data, the Windows Autopilot device preparation process continues. Services that depend on diagnostic data don't work.
#### Network Connection Status Indicator (NCSI)
Windows must be able to tell that the device can access the internet. For more information, see [Network Connection Status Indicator (NCSI)](/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services#14-network-connection-status-indicator).
-`*.msftconnecttest.com` must be resolvable via DNS and accessible via HTTP.
+`*.msftconnecttest.com` must be resolvable via DNS and accessible by using HTTP.
#### Windows Notification Services (WNS)
This service is used to enable Windows to receive notifications from applications and services. For more information, see [Microsoft Store](/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services#26-microsoft-store).
-If the WNS services aren't available, the Windows Autopilot device preparation process still continues without notifications.
+If the WNS services aren't available, the Windows Autopilot device preparation process continues without notifications.
#### Microsoft Store
-Applications in the Microsoft Store can be pushed to the device by triggering them via Intune or other MDM service. App updates and additional applications might also be needed when the user first logs in. For more information, see [Update to Intune integration with the Microsoft Store on Windows](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/update-to-intune-integration-with-the-microsoft-store-on-windows/ba-p/3585077) and [FAQ: Supporting Microsoft Store experiences on managed devices](https://techcommunity.microsoft.com/t5/windows-management/faq-supporting-microsoft-store-experiences-on-managed-devices/m-p/3585286).
+Applications in the Microsoft Store can be pushed to the device by triggering them by using Intune or another MDM service. App updates and additional applications might also be needed when the user first logs in. For more information, see [Update to Intune integration with the Microsoft Store on Windows](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/update-to-intune-integration-with-the-microsoft-store-on-windows/ba-p/3585077) and [FAQ: Supporting Microsoft Store experiences on managed devices](https://techcommunity.microsoft.com/t5/windows-management/faq-supporting-microsoft-store-experiences-on-managed-devices/m-p/3585286).
-If the Microsoft Store isn't accessible, the Windows Autopilot process still continues without Microsoft Store applications.
+If the Microsoft Store isn't accessible, the Windows Autopilot process continues without Microsoft Store applications.
#### Microsoft 365
-As part of the Intune device configuration, installation of Microsoft 365 Applications for enterprise might be required. For a list that includes all Office services, DNS names, IP addresses, including Microsoft Entra ID and other services that might overlap with the previously listed services, see [Office 365 URLs and IP address ranges](/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges).
+As part of the Intune device configuration, you might need to install Microsoft 365 Applications for Enterprise. For a list of Office services, DNS names, IP addresses, including Microsoft Entra ID and other services that might overlap with the previously listed services, see [Microsoft 365 URLs and IP address ranges](/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges).
#### Certificate revocation lists (CRLs)
-Some of these services also need to check certificate revocation lists (CRLs) for certificates used in the services. For a full list, see [Office 365 URLs and IP address ranges](/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges) and [Office 365 Certificate Chains](/en-us/microsoft-365/compliance/encryption-office-365-certificate-chains).
+Some of these services also need to check certificate revocation lists (CRLs) for certificates used in the services. For a full list, see [Microsoft 365 URLs and IP address ranges](/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges) and [Microsoft 365 Certificate Chains](/en-us/microsoft-365/compliance/encryption-office-365-certificate-chains).
#### Proxy settings
-Deploying proxy settings for Windows Autopilot device preparation should be configured on the proxy server itself. Implementing proxy settings via Intune policy isn't fully supported as it might cause issues and unexpected behavior with privileged access deployments.
+Deploying proxy settings for Windows Autopilot device preparation should be configured on the proxy server itself. Implementing proxy settings by using Intune policy isn't fully supported. It might cause issues and unexpected behavior with privileged access deployments.
# [Licensing](#tab/licensing)
### Licensing requirements
-Windows Autopilot device preparation depends on specific capabilities available in Windows client and Microsoft Entra ID. It also requires a mobile device management (MDM) service such as Microsoft Intune. These capabilities can be obtained through various editions and subscription programs.
+Windows Autopilot device preparation depends on specific capabilities available in Windows client and Microsoft Entra ID. It also requires a mobile device management (MDM) service such as Microsoft Intune. You can get these capabilities through various editions and subscription programs.
-To provide needed Microsoft Entra ID and MDM functionality, including automatic MDM enrollment and company branding features, one of the following subscriptions is required:
+To provide the needed Microsoft Entra ID and MDM functionality, including automatic MDM enrollment and company branding features, you need one of the following subscriptions:
-- [Microsoft 365 Business Premium subscription](https://www.microsoft.com/microsoft-365/business).
-- [Microsoft 365 F1 or F3 subscription](https://www.microsoft.com/microsoft-365/enterprise/firstline).
-- [Microsoft 365 Academic A1, A3, or A5 subscription](https://www.microsoft.com/education/products/microsoft-365).
-- [Microsoft 365 Enterprise E3 or E5 subscription](https://www.microsoft.com/microsoft-365/enterprise), which include all Windows client, Microsoft 365, and EMS features (Microsoft Entra ID and Intune).
-- Enterprise Mobility + Security E3 or E5 subscription, which include all needed Microsoft Entra ID and Intune features.
-- [Intune for Education subscription](/en-us/intune-education/what-is-intune-for-education), which include all needed Microsoft Entra ID and Intune features.
-- [Microsoft Entra ID P1 or P2](https://azure.microsoft.com/services/active-directory/) and [Microsoft Intune subscription](https://www.microsoft.com/security/business/microsoft-intune-pricing) or an alternative MDM service.
+- [Microsoft 365 Business Premium subscription](https://www.microsoft.com/microsoft-365/business)
+- [Microsoft 365 F1 or F3 subscription](https://www.microsoft.com/microsoft-365/enterprise/firstline)
+- [Microsoft 365 Academic A1, A3, or A5 subscription](https://www.microsoft.com/education/products/microsoft-365)
+- [Microsoft 365 Enterprise E3 or E5 subscription](https://www.microsoft.com/microsoft-365/enterprise), which include all Windows client, Microsoft 365, and EMS features (Microsoft Entra ID and Intune)
+- Enterprise Mobility + Security E3 or E5 subscription, which include all needed Microsoft Entra ID and Intune features
+- [Intune for Education subscription](/en-us/intune-education/what-is-intune-for-education), which include all needed Microsoft Entra ID and Intune features
+- [Microsoft Entra ID P1 or P2](https://azure.microsoft.com/services/active-directory/) and [Microsoft Intune subscription](https://www.microsoft.com/security/business/microsoft-intune-pricing) or an alternative MDM service
Note
-When a Microsoft 365 subscription is used, licenses still need to be assigned to users so they can enroll device in Intune. For more information, see [assign licenses to users so they can enroll devices in Intune](/en-us/intune/fundamentals/assign-licenses).
+When you use a Microsoft 365 subscription, you still need to assign licenses to users so they can enroll devices in Intune. For more information, see [assign licenses to users so they can enroll devices in Intune](/en-us/intune/fundamentals/assign-licenses).
-Additionally, the following are also recommended, but not required:
+We recommend the following resources:
-- [Microsoft 365 Apps for enterprise](https://www.microsoft.com/microsoft-365/enterprise/microsoft-365-apps-for-enterprise-product) - Microsoft 365 Applications for enterprise can be deployed easily via Intune or other MDM service.
-- [Windows Subscription Activation](/en-us/windows/deployment/windows-subscription-activation) - automatically step up devices from Windows Pro to Windows Enterprise edition.
+- [Microsoft 365 Apps for enterprise](https://www.microsoft.com/microsoft-365/enterprise/microsoft-365-apps-for-enterprise-product). You can deploy Microsoft 365 Apps for enterprise easily by using Intune or another MDM service.
+- [Windows Subscription Activation](/en-us/windows/deployment/windows-subscription-activation). Step up devices from Windows Pro to Windows Enterprise edition.
# [Configuration](#tab/configuration)
### Configuration requirements
-Before Windows Autopilot device preparation can be used, some configuration tasks are required to support the common Windows Autopilot device preparation scenarios.
+Before you can use Windows Autopilot device preparation, complete the following configuration tasks to support the common Windows Autopilot device preparation scenarios.
-- **Configure Microsoft Entra automatic enrollment**. For Microsoft Intune, see [Set up Windows automatic Intune enrollment](tutorial/user-driven/entra-join-automatic-enrollment) and [Enable Windows automatic enrollment](/en-us/intune/intune-service/enrollment/windows-enroll#enable-windows-automatic-enrollment) for details. If using a different mobile device management (MDM) service, contact the vendor for the specific URLs or configuration needed for those services.
+- **Configure Microsoft Entra automatic enrollment**. For Microsoft Intune, see [Set up Windows automatic Intune enrollment](tutorial/user-driven/entra-join-automatic-enrollment) and [Enable Windows automatic enrollment](/en-us/intune/intune-service/enrollment/windows-enroll#enable-windows-automatic-enrollment) for details. To use a different mobile device management (MDM) service, contact the vendor for the specific URLs or configuration needed for those services.
- **The first user that signs in needs to have Microsoft Entra join permissions**. For more information, see [Allow users to join devices to Microsoft Entra ID](tutorial/user-driven/entra-join-allow-users-to-join).
-The following configurations are optional but recommended. They aren't required:
+We recommend the following configurations:
- **Automatically step up from Windows Pro to Windows Enterprise**. For more information, see [Windows Subscription Activation](/en-us/windows/deployment/windows-subscription-activation).
There are no additional hardware requirements to use Windows Autopilot device preparation, beyond the hardware requirements to run Windows. For more information, see:
-- [Find Windows 11 specs, features, and computer requirements](https://www.microsoft.com/windows/windows-11-specifications).
-- [Windows minimum hardware requirements](/en-us/windows-hardware/design/minimum/minimum-hardware-requirements-overview).
-- [Windows 11 requirements](/en-us/windows/whats-new/windows-11-requirements).
+- [Find Windows 11 specs, features, and computer requirements](https://www.microsoft.com/windows/windows-11-specifications)
+- [Windows minimum hardware requirements](/en-us/windows-hardware/design/minimum/minimum-hardware-requirements-overview)
+- [Windows 11 requirements](/en-us/windows/whats-new/windows-11-requirements)
# [RBAC](#tab/rbac)
### Required RBAC permissions
@@ -283,18 +282,18 @@ The following role-based access control (RBAC) permissions are required in a rol To create a custom role with these permissions for use with Windows Autopilot device preparation:
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-2. In the **Home** screen, select **Tenant administration** in the left hand pane.
+2. In the **Home** screen, in the left pane, select **Tenant administration**.
3. In the **Tenant admin | Tenant status** screen, select **Roles**.
4. In the **Endpoint Manager roles | All roles** screen, make sure **All roles** is selected under **Manage**.
-5. Select the **Create** drop down menu and then select **Intune role**. The **Add Custom Role** screen opens.
+5. Select **Create** and then select **Intune role**. The **Add Custom Role** screen opens.
6. In the **Add Custom Role** screen:
1. In the **Basics** page:
- 1. **Name** - enter a name for the custom role, such as **Windows Autopilot device preparation administrator**.
- 2. **Description** - enter a description for the custom role.
+ 1. **Name**. Enter a name for the custom role, such as **Windows Autopilot device preparation administrator**.
+ 2. **Description**. Enter a description for the custom role.
2. Select **Next**.
- 3. In the **Permissions** page, under **Select a category below to configure settings.**, scroll through the list to find the following settings. Once the setting is located, expand it, and then change to the following permissions:
+ 3. In the **Permissions** page, under **Select a category below to configure settings.**, find the following settings. After you find a setting, expand it, and then change to the following permissions:
- **Device configurations**
@@ -325,14 +324,14 @@ To create a custom role with these permissions for use with Windows Autopilot de - **Read**: Yes
All other permissions can be left at the default of **No**.
- 4. Once all permissions are set correctly, select **Next**.
+ 4. When all permissions are set correctly, select **Next**.
5. In the **Scope tags** page, select **Next**.
Note
- **Scope tags** are optional. If a custom scope tag needs to be specified, do so at this page. For more information about scope tags, see [Use role-based access control and scope tags for distributed IT](/en-us/intune/fundamentals/role-based-access-control/scope-tags).
+ **Scope tags** are optional. If you need to specify a custom scope tag, add it on this page. For more information about scope tags, see [Use role-based access control and scope tags for distributed IT](/en-us/intune/fundamentals/role-based-access-control/scope-tags).
6. In the **Review + create** page, verify that all permissions are correct, and then select **Create**.
-7. The new custom Windows Autopilot device preparation role can now be assigned to users who administer Windows Autopilot device preparation.
+7. Assign the new custom Windows Autopilot device preparation role to users who administer Windows Autopilot device preparation.
For more information, see [Role-based access control (RBAC) with Microsoft Intune](/en-us/intune/fundamentals/role-based-access-control/overview).