| [What's new](windows-autopilot-whats-new.md) | Windows Autopilot is always being updated with new features! Check this topic to read about the latests capabilities. + |
| What's new | Windows Autopilot is always being updated with new features! Check this topic to read about the latests capabilities. |
| [Overview of Windows Autopilot](windows-autopilot.md) | A review of Windows Autopilot is provided with a video walkthrough. Benefits and general requirements are discussed. - |
| [Requirements](windows-autopilot-requirements.md) | Detailed software, network, licensiing, and configuration requirments are provided. - |
| [Scenarios and Capabilities](windows-autopilot-scenarios.md) | A summary of Windows Autopilot deployment scenarios and capabilities. - |
| [Get started](demonstrate-deployment-on-vm.md) | Interested in trying out Autopilot? See this step-by-step walkthrough to test Windows Autopilot on a virtual machine or physical device with a free 30-day trial premium Intune account. + |
| Overview of Windows Autopilot | A review of Windows Autopilot is provided with a video walkthrough. Benefits and general requirements are discussed. + |
| Requirements | Detailed software, network, licensiing, and configuration requirments are provided. + |
| Scenarios and Capabilities | A summary of Windows Autopilot deployment scenarios and capabilities. + |
| Get started | Interested in trying out Autopilot? See this step-by-step walkthrough to test Windows Autopilot on a virtual machine or physical device with a free 30-day trial premium Intune account. |
| [User-driven mode](user-driven.md) | Requirements and validation steps for deploying a new Azure Active Directory (AAD) joined or hybrid AAD-joined Windows 10 device are provided. - |
| [Self-deploying mode](self-deploying.md) | Requirements and validation steps for deploying a new Windows 10 device device with little to no user interaction are provided. - |
| [Windows Autopilot Reset](windows-autopilot-reset.md) | Using Windows Autopilot Reset, a device can be restored to its original settings, taking it back to a business-ready state. Both local and remote reset scenarios are discussed. - |
| [Windows Autopilot for white glove deployment](white-glove.md) | Requirements and procedures are described that enable additional policies and apps to be delivered to a Windows Autopilot device. - |
| [Support for existing devices](existing-devices.md) | This topic describes how Windows Autopilot can be used to convert Windows 7 or Windows 8.1 domain-joined computers to AAD-joined computers running Windows 10. + |
| User-driven mode | Requirements and validation steps for deploying a new Azure Active Directory (AAD) joined or hybrid AAD-joined Windows 10 device are provided. + |
| Self-deploying mode | Requirements and validation steps for deploying a new Windows 10 device device with little to no user interaction are provided. + |
| Windows Autopilot Reset | Using Windows Autopilot Reset, a device can be restored to its original settings, taking it back to a business-ready state. Both local and remote reset scenarios are discussed. + |
| Windows Autopilot for white glove deployment | Requirements and procedures are described that enable additional policies and apps to be delivered to a Windows Autopilot device. + |
| Support for existing devices | This topic describes how Windows Autopilot can be used to convert Windows 7 or Windows 8.1 domain-joined computers to AAD-joined computers running Windows 10. |
| [Registering devices](add-devices.md) | The process of registering a device with the Windows Autopilot deployment service is described. - |
| [Configuring device profiles](profiles.md) | The device profile settings that specifie its behavior when it is deployed are described. - |
| [Enrollment status page](enrollment-status.md) | Settings that are available on the Enrollment Status Page are described. - |
| [Bitlocker encryptions](bitlocker.md) | Available options for configuring BitLocker on Windows Autopilot devices are described. - |
| [Troubleshooting Windows Autopilot](troubleshooting.md) | Diagnotic event information and troubleshooting procedures are provided. - |
| [Known issues](known-issues.md) | A list of current known issues and solutions is provided. + |
| Registering devices | The process of registering a device with the Windows Autopilot deployment service is described. + |
| Configuring device profiles | The device profile settings that specifie its behavior when it is deployed are described. + |
| Enrollment status page | Settings that are available on the Enrollment Status Page are described. + |
| Bitlocker encryption | Available options for configuring BitLocker on Windows Autopilot devices are described. + |
| Troubleshooting Windows Autopilot | Diagnotic event information and troubleshooting procedures are provided. + |
| Known issues | A list of current known issues and solutions is provided. |
| [FAQ](autopilot-faq.md) | Frequently asked questions on several topics are provided. - |
| [Support contacts](autopilot-support.md) | Support information is provided. - |
| [Registration authorization](registration-auth.md) | This article discusses how a CSP partner or OEM can obtain customer authorization to register Windows Autopilot devices. + |
| FAQ | Frequently asked questions on several topics are provided. + |
| Support contacts | Support information is provided. + |
| Registration authorization | This article discusses how a CSP partner or OEM can obtain customer authorization to register Windows Autopilot devices. |
| Service | Information - |
|---|---|
| **Windows Autopilot Deployment Service and Windows Activation** | After a network connection is in place, each Windows 10 device will contact the Windows Autopilot Deployment Service. With Windows 10 builds 18204 and above, the following URLs are used: https://ztd.dds.microsoft.com, https://cs.dds.microsoft.com. + |
| Windows Autopilot Deployment Service and Windows Activation | After a network connection is in place, each Windows 10 device will contact the Windows Autopilot Deployment Service. With Windows 10 builds 18204 and above, the following URLs are used: https://ztd.dds.microsoft.com, https://cs.dds.microsoft.com. -For all supported Windows 10 releases, Windows Autopilot also uses Windows Activation services. See [Windows activation or validation fails with error code 0x8004FE33](https://support.microsoft.com/help/921471/windows-activation-or-validation-fails-with-error-code-0x8004fe33) for details about problems that might occur when you connect to the Internet through a proxy server. - |
| **Azure Active Directory** | User credentials are validated by Azure Active Directory, and the device can also be joined to Azure Active Directory. See [Office 365 IP Address and URL Web service](https://docs.microsoft.com/en-us/office365/enterprise/office-365-ip-web-service) for more information. - |
| **Intune** | Once authenticated, Azure Active Directory will trigger enrollment of the device into the Intune MDM service. See the following link for details about network communication requirements: [Intune network configuration requirements and bandwidth](https://docs.microsoft.com/intune/network-bandwidth-use#network-communication-requirements). - |
| **Windows Update** | During the OOBE process, as well as after the Windows 10 OS is fully configured, the Windows Update service is leveraged to retrieve needed updates. If there are problems connecting to Windows Update, see [How to solve connection problems concerning Windows Update or Microsoft Update](https://support.microsoft.com/help/818018/how-to-solve-connection-problems-concerning-windows-update-or-microsof). +For all supported Windows 10 releases, Windows Autopilot also uses Windows Activation services. See Windows activation or validation fails with error code 0x8004FE33 for details about problems that might occur when you connect to the Internet through a proxy server. + |
| Azure Active Directory | User credentials are validated by Azure Active Directory, and the device can also be joined to Azure Active Directory. See Office 365 IP Address and URL Web service for more information. + |
| Intune | Once authenticated, Azure Active Directory will trigger enrollment of the device into the Intune MDM service. See the following link for details about network communication requirements: Intune network configuration requirements and bandwidth. + |
| Windows Update | During the OOBE process, as well as after the Windows 10 OS is fully configured, the Windows Update service is leveraged to retrieve 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 will not be available. - |
| **Delivery Optimization** | When downloading Windows Updates, Microsoft Store apps and app updates, Office Updates and Intune Win32 Apps, the [Delivery Optimization](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization) service is contacted to enable peer-to-peer sharing of content so that only a few devices need to download it from the internet. + |
| Delivery Optimization | When downloading Windows Updates, Microsoft Store apps and app updates, Office Updates and Intune Win32 Apps, the Delivery Optimization service is contacted to enable peer-to-peer sharing of content so that only a few devices need to download it from the internet. 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 accurate. 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** | To enable Windows Analytics and related diagnostics capabilities, see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization). + |
| 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 accurate. 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 | To enable Windows Analytics and related diagnostics capabilities, see Configure Windows diagnostic data in your organization. If diagnostic data cannot be sent, the Autopilot process will still continue, but services that depend on diagnostic data, such as Windows Analytics, will not work. - |
| **Network Connection Status Indicator (NCSI)** | Windows must be able to tell that the device is able to access the internet. For more information, see [Network Connection Status Indicator (NCSI)](https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1709-endpoints#network-connection-status-indicator-ncsi). + |
| Network Connection Status Indicator (NCSI) | Windows must be able to tell that the device is able to access the internet. For more information, see Network Connection Status Indicator (NCSI). -[www.msftconnecttest.com](http://www.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 apps and services. See [Microsoft Store](https://docs.microsoft.com/en-us/windows/privacy/manage-windows-1809-endpoints#microsoft-store) for more information. +www.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 apps and services. See Microsoft Store for more information. If the WNS services are not 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](https://docs.microsoft.com/microsoft-store/prerequisites-microsoft-store-for-business)(also includes Azure AD and Windows Notification Services). + |
| 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 is not accessible, the AutoPilot process will still continue without Microsoft Store apps. - |
| **Office 365** | As part of the Intune device configuration, installation of Office 365 ProPlus may be required. For more information, see [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2)(includes all Office services, DNS names, IP addresses; includes Azure AD and other services that may overlap with those 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. A full list of these is documented at [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_crl) and [Office 365 Certificate Chains](https://aka.ms/o365chains). + |
| Office 365 | As part of the Intune device configuration, installation of Office 365 ProPlus may be required. For more information, see Office 365 URLs and IP address ranges (includes all Office services, DNS names, IP addresses; includes Azure AD and other services that may overlap with those 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. A full list of these is documented at Office 365 URLs and IP address ranges and Office 365 Certificate Chains. |