From bd84268cd6de8934232dc7f5190fd681644d674b Mon Sep 17 00:00:00 2001 From: Mike Stephens Date: Fri, 8 Sep 2017 13:43:25 -0700 Subject: [PATCH] Revert "resolve conflict" This reverts commit b41ad23f8c389e857143dc66754cc02c0e510939. --- .../hello-for-business/hello-planning-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/access-protection/hello-for-business/hello-planning-guide.md b/windows/access-protection/hello-for-business/hello-planning-guide.md index e74710904b..febf4b56d8 100644 --- a/windows/access-protection/hello-for-business/hello-planning-guide.md +++ b/windows/access-protection/hello-for-business/hello-planning-guide.md @@ -89,7 +89,7 @@ The goal of Windows Hello for Business is to move organizations away from passwo Cloud only and hybrid deployments provide many choices for multifactor authentication. On-premises deployments must use a multifactor authentication that provides an AD FS multifactor adapter to be used in conjunction with the on-premises Windows Server 2016 AD FS server role. Organizations can use from the on-premises Azure Multifactor Authentication server, or choose from several third parties (Read [Microsoft and third-party additional authentication methods](https://docs.microsoft.com/windows-server/identity/ad-fs/operations/configure-additional-authentication-methods-for-ad-fs#microsoft-and-third-party-additional-authentication-methods) for more information). >[!NOTE] -> Azure Multi-Factor Authentication is available through: +> Azure Multi-Factor Authentication is available through a: >* Microsoft Enterprise Agreement >* Open Volume License Program >* Cloud Solution Providers program