Windows Autopilot requirements

• חל על:

  ✅ Windows 11, ✅ Windows 10, ✅ Windows Holographic

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:

https://learn.microsoft.com/en-us/search/?terms=%22The%20list%20of%20requirements%20for%20Windows%20Autopilot%20is%20organized%20into%20four%20different%20categories%22

This example includes the &locale=en-us variable. The locale variable is required, but it can be changed to another supported locale. For example, &locale=es-es.

For more information on using RSS for notifications, see How to use the docs in the Intune documentation.

The list of requirements for Windows Autopilot is organized into four different categories:

• Software - OS requirements.
• Networking - networking requirements.
• Licensing - licensing requirements.
• Configuration - configurations required in Microsoft Entra ID and Microsoft Intune.

Select the appropriate tab to see the relevant requirements:

Software

Software requirements

Windows Autopilot depends on specific features available in Windows client, Microsoft Entra ID, and the mobile device management (MDM) service such as Microsoft Intune. To use Windows Autopilot and access these features, some software requirements must be met.

Note

For a list of OEMs that currently support Windows Autopilot, see the Participant device manufacturers section at Windows Autopilot.

Windows 11

A supported version of Windows 11 General Availability Channel is required.

The following editions of Windows 11 are supported:

• Windows 11 Pro.
• Windows 11 Pro Education.
• Windows 11 Pro for Workstations.
• Windows 11 Enterprise.
• Windows 11 Education.

Windows 10

A supported version of Windows 10 is required.

The following editions of Windows 10 are supported:

• Windows 10 Pro.
• Windows 10 Pro Education.
• Windows 10 Pro for Workstations.
• Windows 10 Enterprise.
• Windows 10 Education.
• Windows 10 Enterprise LTSC.

HoloLens

• Windows Autopilot for HoloLens 2 requires a currently supported version of Windows Holographic. For more information, see Windows Autopilot for HoloLens 2.

Note

Procedures for deploying Windows Autopilot might refer to specific products and versions. The inclusion of these products in this content doesn't imply an extension of support for a version that is beyond its support lifecycle. Windows Autopilot doesn't support products that are beyond their support lifecycle. For more information, see Microsoft Lifecycle Policy.

Networking

Networking requirements

Windows Autopilot depends on various internet-based services. Access to these services must be provided for Autopilot to function properly. In the simplest case, enabling proper functionality can be achieved by ensuring 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).

Additional configuration might be required 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.

Service requirements

Windows Autopilot relies on several different type of services to function properly. In order for these services to function properly, certain network configurations need to be performed. 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:

• https://ztd.dds.microsoft.com
• https://cs.dds.microsoft.com
• https://login.live.com

Windows Activation

Windows Autopilot requires Windows Activation services. For more information about the URLs that need to be accessible for the activation services, see Windows activation or validation fails with error code 0x8004FE33.

Microsoft Entra ID

Microsoft Entra ID validates user credentials. Additionally, the device is joined or registered to Microsoft Entra ID during Windows Autopilot. For more information, see Office 365 IP Address and URL 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:

• Intune network configuration requirements and bandwidth.
• Network endpoints for Microsoft Intune.

Autopilot 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 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 retrieves needed updates. If there are problems connecting to Windows Update, see Windows Update issues troubleshooting.

If Windows Update is inaccessible, the Autopilot process still continues but critical updates aren't available.

Delivery Optimization

Autopilot 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.
• Microsoft Store applications and application updates.
• Office Updates.
• Intune Win32 Applications.

If the Delivery Optimization Service is inaccessible, the Autopilot process still continues with Delivery Optimization downloads from the cloud without peer-to-peer.

Network Time Protocol (NTP) sync

When a Windows device starts up, it talks to a network time server to ensure that the time on the device is correct. Ensure that UDP port 123 to time.windows.com is accessible.

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.

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 Autopilot process still continues. However, 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).

*.msftconnecttest.com must be resolvable via DNS and accessible via 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 Autopilot process still 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 and FAQ: Supporting Microsoft Store experiences on managed devices.

If the Microsoft Store isn't accessible, the Autopilot process still continues without Microsoft Store apps.

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.

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 and Office 365 Certificate Chains.

Microsoft Entra hybrid join

Important

Microsoft recommends deploying new devices as cloud-native using Microsoft Entra join. Deploying new devices as Microsoft Entra hybrid join devices isn't recommended, including through Autopilot. For more information, see Microsoft Entra joined vs. Microsoft Entra hybrid joined in cloud-native endpoints: Which option is right for your organization.

The device can be Microsoft Entra hybrid joined. The computer should be on the internal network for Microsoft Entra hybrid join to work. For more information, see Windows Autopilot user-driven mode.

Autopilot self-deploying mode and Autopilot pre-provisioning

The TPM attestation process requires access to a set of HTTPS URLs, which are unique for each TPM provider. Ensure access to this URL pattern: *.microsoftaik.azure.net.

Firmware TPM devices, which are only provided by Intel, AMD, or Qualcomm, don't include all needed certificates at boot time and must be able to retrieve them from the manufacturer on first use. Devices with discrete TPM chips come with these certificates preinstalled. These devices include ones from any other manufacturer. For more information, see TPM recommendations.

For each firmware TPM provider, make sure that the appropriate URL is accessible so that certificates can be successfully requested. For example:

• Intel: https://ekop.intel.com/ekcertservice
• Qualcomm: https://ekcert.spserv.microsoft.com/EKCertificate/GetEKCertificate/v1
• AMD: https://ftpm.amd.com/pki/aia

Proxy settings

Deploying proxy settings for Windows Autopilot 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.

Licensing

Licensing requirements

Windows Autopilot 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.

To provide needed Microsoft Entra ID and MDM functionality, including automatic MDM enrollment and company branding features, one of the following subscriptions is required:

• 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.
• Intune for Education subscription, which include all needed Microsoft Entra ID and Intune features.
• Microsoft Entra ID P1 or P2 and Microsoft Intune subscription 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.

Additionally, the following are also recommended (but not required):

• Microsoft 365 Apps for enterprise - Microsoft 365 Applications for enterprise can be deployed easily via Intune or other MDM service.
• Windows Subscription Activation - automatically step up devices from Windows Pro to Windows Enterprise edition.

Configuration

Configuration requirements

Before Windows Autopilot can be used, some configuration tasks are required to support the common Autopilot scenarios.

• Configure Microsoft Entra automatic enrollment. For details when using Microsoft Intune, see Set up Windows automatic Intune enrollment or Enable Windows automatic enrollment. If using a different 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 some deployment scenarios. For details, see Allow users to join devices to Microsoft Entra ID. The exception to this requirement is Windows Autopilot self-deployment mode since this method works in a userless context.

The following configurations are optional but recommended. They aren't required:

• Automatically step up from Windows Pro to Windows Enterprise. For more information, see Windows Subscription Activation.

• Configure Microsoft Entra custom branding. To display an organization-specific sign-on page, configure Microsoft Entra ID with the images and text that need to be displayed. For more information, see Quickstart: Add company branding to your sign-in page in Microsoft Entra ID. Key elements for Windows Autopilot include the square logo, sign-in page text, and Microsoft Entra tenant name. The tenant name is configured separately in the Microsoft Entra tenant properties.

Specific scenarios have additional requirements. Generally, there are two specific tasks:

• Device registration. Devices must be added to Windows Autopilot to support most Windows Autopilot scenarios. For more information, see Register devices as Autopilot devices or Adding devices to Windows Autopilot.

• Profile configuration. Once devices are added to Windows Autopilot, a profile of settings needs to be applied to each device. For details see Configure Autopilot profiles. Microsoft Intune can automate this profile assignment. For more information, see Create an Autopilot device group and Assign an Autopilot deployment profile to a device group.

For more information, see Windows Autopilot Scenarios.

For a walkthrough for some of these and related steps, see this video:

There are no additional hardware requirements to use Autopilot, beyond the hardware requirements to run Windows. For more information, see:

• Find Windows 11 specs, features, and computer requirements.
• How to Find Windows 10 Computer Specifications & Systems Requirements.
• Windows minimum hardware requirements.
• Windows 11 requirements.