What is Azure Active Directory Domain Services?
Azure Active
Directory Domain Services enables organizations to use domains
services such as domain joining, Group Policies, LDAP, Kerberos/NTLM
authentication same as the on-premises windows based active directory.
Azure active
directory domain services extend Azure AD to support DNS name resolution, Custom
Organizational Units, Kerberos, NTLM, Group Policy, domain joining, LDAP bind
or read and Secure LDAP. With managed domain as the name suggests we can use
domain services without the need of deploying, managing or patching domain
controllers.
What are the
prerequisites?
To deploy
azure ADDS following resources and privileges are required:
·
An Azure Subscription,
·
Azure AD tenant associated to the
subscription, the tenant either be synchronized with an on-premises directory
or cloud-only directory. For our demo purpose, I will use the cloud-only directory,
·
Global administrator privilege on the
tenant to deploy Azure ADDS,
·
And Contributor privilege on the
subscription
What are the
advantages?
· Easy to deploy: Azure AD Domain
services can be enabled with a single wizard on the Azure portal, without the need of
deployment of domain controllers and it’s management.
· High Availability, managed domains
are Azure service with an uptime of 99.9 % SLA.
· With Kerberos/NTLM Authentication support,
you can deploy any application or workload, those have a dependency on legacy
authentication protocol.
· In-Built DNS Update, same as on-premises
AD, the managed domain is also highly dependent on DNS for name resolution, Azure
AD Domain Services comes with in-built DNS records and updates. You do not need
to managed DNS separately.
· Microsoft manages the Domain
Controllers including the deployment, backup, and restoration.
What are the
limitations?
Since it is
managed domain, it comes with certain limitations:
· Lack of control, you do not get
domain admin or enterprise admin privileges. For any application installation requires
such access are of the list for example ADFS or Exchange
·
Kerberos delegation is not possible.
·
Custom GPOs are not allowed.
· One way sync, any custom object created
under the managed domain will not be reflected in Azure AD.
Custom schema extension is not supported.
Next:
How to Configured
Azure AD Domain Service – Step
by Step
Comments
Post a Comment
Appreciate your Feedbacks\Comments