From 4ad41520e7864728f84d69c50b0ea11cc417bcef Mon Sep 17 00:00:00 2001 From: Jose Gabriel Ortega Castro Date: Mon, 13 May 2019 10:13:28 -0500 Subject: [PATCH] Update windows/deployment/deploy-enterprise-licenses.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> --- windows/deployment/deploy-enterprise-licenses.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index cdecd2c70f..38252eee03 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -79,7 +79,6 @@ For more information about integrating on-premises AD DS domains with Azure AD, >[!NOTE] >If you are implementing Azure AD, and you already have an on-premises domain, you don't need to integrate with Azure AD, since your main authentication method is your internal AD. If you want to manage all your infrastructure in the cloud, you can safely configure your domain controller remotely to integrate your computers with Azure AD, but you won't be able to apply fine controls using GPO. Azure AD is best suited for the global administration of devices when you don't have any on-premises servers. ->The whole idea of using Azure AD, is mostly when you don't have any on-premises servers, and you want and enterprise administration of devices worldwide. ## Preparing for deployment: reviewing requirements