From 56e843ac8c1b999aa946417f9696541c45e4ea3a Mon Sep 17 00:00:00 2001
From: Reece Peacock <49645174+Reeced40@users.noreply.github.com>
Date: Thu, 8 Aug 2019 08:30:24 +0200
Subject: [PATCH] Update hello-deployment-guide.md

---
 .../hello-for-business/hello-deployment-guide.md               | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md b/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
index 63a1c40ec4..db9b0e1330 100644
--- a/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
+++ b/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
@@ -25,9 +25,6 @@ Windows Hello for Business is the springboard to a world without passwords. It r
 
 This deployment guide is to guide you through deploying Windows Hello for Business, based on the planning decisions made using the Planning a Windows Hello for Business Deployment Guide. It provides you with the information needed to successfully deploy Windows Hello for Business in an existing environment.
 
-> [!NOTE]
-> Two Azure AD Connect synchronizations are required in order for WHfB to begin working.
-
 ## Assumptions
 
 This guide assumes that baseline infrastructure exists which meets the requirements for your deployment. For either hybrid or on-premises deployments, it is expected that you have: