From 92395558064e7c37625fb6f1da6cba00364b5835 Mon Sep 17 00:00:00 2001 From: Andre van den Berg Date: Sun, 28 Oct 2018 15:24:18 +0100 Subject: [PATCH] Update about AD Hybrid Join Did see a request about missing statement about AD onpremise Hybrid AD Join. --- windows/deployment/windows-autopilot/windows-10-autopilot.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/windows-autopilot/windows-10-autopilot.md b/windows/deployment/windows-autopilot/windows-10-autopilot.md index ab6fee76f2..eb7d114264 100644 --- a/windows/deployment/windows-autopilot/windows-10-autopilot.md +++ b/windows/deployment/windows-autopilot/windows-10-autopilot.md @@ -51,6 +51,9 @@ The Windows Autopilot Deployment Program enables you to: ##### Prerequisites + >[!NOTE] + >Today, Windows Autopilot user-driven mode supports joining devices to Azure Active Directory. Support for Hybrid Azure Active Directory Join (with devices joined to an on-premises Active Directory domain) will be available in a future Windows 10 release. See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options. + * [Devices must be registered to the organization](#device-registration-and-oobe-customization) * [Company branding needs to be configured](#configure-company-branding-for-oobe) * [Network connectivity to cloud services used by Windows Autopilot](#network-connectivity-requirements)