Update windows/deployment/deploy-enterprise-licenses.md

Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com>
This commit is contained in:
Jose Gabriel Ortega Castro 2019-05-13 10:13:14 -05:00 committed by GitHub
parent 67f98f7e71
commit f5ca28c668
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -78,7 +78,7 @@ For more information about integrating on-premises AD DS domains with Azure AD,
- [Azure AD + Domain Join + Windows 10](https://blogs.technet.microsoft.com/enterprisemobility/2016/02/17/azure-ad-domain-join-windows-10/)
>[!NOTE]
>If you are implementing Azure AD, and have already an on-premises, you don't need to join the computers into Azure AD, since your main authentication method is your internal AD. In case, that you want to manage all your infrastructure on the cloud, then you can safely remote your domain controller and work with the join of the computers into the Azure AD, but you won't be able to apply fine control into the computers using GPO.
>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