
Windows AD to Azure AD DS may make sense. Offering, and it’s understandable how, given these directives, moving from “We want to get rid of on-premises domain controllers” or “I was given theĭirective that we will no longer support Windows AD.” Azure AD DS is a Platform as a Service (PaaS) The problem usually starts with something like: Azure AD DS is compatible with Windows AD.īased on online forums and social media posts, The compatibilityīetween Azure AD DS and Windows AD has caused problems. At a high level, both Azure AD DS and Windows AD offer network-based authentication with Kerberos and NTLM support. I understand the confusion, one of my most popular videos is on the difference between Azure AD DS, Windows AD and Azure AD ( here). I'd rather not manually add each failed attribute or object class using the GUI.Azure Active Directory Domain Services (Azure AD DS) is not a replacement for Windows Active Directory. It is listed as an attribute on the Microsoft site (v=vs.85).aspx which makes me think that it is just not included in the default Schema in ApacheDS. (If I take out the userPrincipalName lines everything is fine).

However, this fails because ATTRIBUTE_TYPE for OID userprincipalname does not exist!.

Member: cn=Joel Spolsky,ou=Users,dc=serverfault,dc=com Member: cn=Jeff Atwood,ou=Users,dc=serverfault,dc=com UserPrincipalName: cn=Joel Spolsky,ou=Users,dc=serverfault,dc=comĭn: CN=Dev,ou=Groups,dc=serverfault,dc=com I then created an ldif file to add users and groups.ĭn: cn=Jeff Atwood,ou=Users,dc=serverfault,dc=com I am trying to set up Apache DS to simulate my company Active Directory locally.
