From 7d33ad4d30fe53f10a1a67adabbfb9e1f6d1b203 Mon Sep 17 00:00:00 2001
From: Yves Perrenoud <37378949+yvperren@users.noreply.github.com>
Date: Wed, 20 Mar 2019 11:54:20 +0100
Subject: [PATCH] Added additional Requirement

Added the Requirement that in a Proxy Environment WDAP Proxy Settings needs to be enabled and configured.
---
 windows/deployment/windows-autopilot/user-driven-hybrid.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/windows/deployment/windows-autopilot/user-driven-hybrid.md b/windows/deployment/windows-autopilot/user-driven-hybrid.md
index 2381c3b8c8..c084916d3e 100644
--- a/windows/deployment/windows-autopilot/user-driven-hybrid.md
+++ b/windows/deployment/windows-autopilot/user-driven-hybrid.md
@@ -32,6 +32,7 @@ To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
 - The device must be connected to the Internet and have access to an Active Directory domain controller.
 - The Intune Connector for Active Directory must be installed.
     - Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf. 
+- If using Proxy, WDAP Proxy settings option must be enabled and configured.
 
 **AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.