Windows Autopilot networking requirements
- Windows 10
- Windows Holographic, version 2004 or later
Windows Autopilot depends on a variety of 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 may be required to grant access to required services in environments that:
- have more restrictive Internet access.
- require authentication before internet access can be obtained.
Smart card and certificate based authentication isn't supported during OOBE. For more information, see Smartcards and certificate-based authentication.
For additional details about each of these services and their specific requirements, review the following details:
|Windows Autopilot Deployment Service||After a network connection is in place, each Windows 10 device will contact the Windows Autopilot Deployment Service. With Windows 10 version 1903 and above, the following URLs are used: https://ztd.dds.microsoft.com, https://cs.dds.microsoft.com, and https://login.live.com.|
|Windows Activation||Windows Autopilot requires Windows Activation services. For details about the URLs that need to be accessible for the activation services, see Windows activation or validation fails with error code 0x8004FE33.|
|Azure Active Directory||User credentials are validated by Azure Active Directory, and the device can also be joined to Azure Active Directory. For more information, see Office 365 IP Address and URL Web service.|
|Intune||Once authenticated, Azure Active Directory will trigger enrollment of the device into the Intune mobile device management (MDM) service. See the following link for details about network communication requirements: Intune network configuration requirements and bandwidth.|
|Windows Update||During the OOBE process and after the Windows 10 OS configuration, the Windows Update service retrieves needed updates. If there are problems connecting to Windows Update, see How to solve connection problems concerning Windows Update or Microsoft Update.|
If Windows Update is inaccessible, the Autopilot process will still continue but critical updates won't be available.
|Delivery Optimization||Autopilot contacts the Delivery Optimization service when downloading the apps 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 apps and app updates
- Office Updates
- Intune Win32 Apps|
If the Delivery Optimization Service is inaccessible, the Autopilot process will still continue with Delivery Optimization downloads from the cloud (without peer-to-peer).
|Network Time Protocol (NTP) Sync||When a Windows device starts up, it will talk 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 DNS 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||Starting in Windows 10, 1903, diagnostic data collection will be enabled by default. To disable Windows Analytics and related diagnostics capabilities, see Manage enterprise diagnostic data level.|
If diagnostic data can't be sent, the Autopilot process still continues. However, services that depend on diagnostic data, such as Windows Analytics, won'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).
|Windows Notification Services (WNS)||This service is used to enable Windows to receive notifications from apps and services. For more information, see Microsoft Store.|
If the WNS services aren't available, the Autopilot process will still continue without notifications.
|Microsoft Store, Microsoft Store for Business||Apps in the Microsoft Store can be pushed to the device, triggered via Intune (MDM). App updates and additional apps may also be needed when the user first logs in. For more information, see Prerequisites for Microsoft Store for Business and Education (also includes Azure AD and Windows Notification Services).|
If the Microsoft Store isn't accessible, the Autopilot process will still continue without Microsoft Store apps.
|Microsoft 365||As part of the Intune device configuration, installation of Microsoft 365 Apps for enterprise may be required. For more information, see Office 365 URLs and IP address ranges. This article includes all Office services, DNS names, IP addresses. It also includes Azure AD and other services that may overlap with the services listed above.|
|Certificate revocation lists (CRLs)||Some of these services will 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.|
|Hybrid Azure AD join||The device can be hybrid Azure AD joined. The computer should be on corporate network for hybrid Azure AD join to work. See details at 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 (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 (including devices from any other manufacturer) come with these certificates preinstalled. 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: