SF: You should only ask practical, answerable questions based on actual problems that you face. Forwarding: This question may be debatable regarding the answerable-part. However, for me this is an actual problem regarding best-practices and I think it is definitely answerable in terms of “Is there an alternative?” vs. “You're answering the wrong question and should move in a totally different direction.”
I'm evaluating Azure out of the DevOp scope for the first time right now. While setting up an server/cloud infrastructure with several services, I came to the point where I wanted to centralize access control.
Back in the good old days I managed Windows Domain Controllers in rather big environments for years, so it felt just natural to dive into Azure. Starting from zero, I created a tenant with the intention of a pure Azure service - not hybrid (i.e. no Sync with a Windows Server instance).
Update 1: Thanks to a comment below I realized that the Microsoft link below is about hosted ADDS - i.e. not Azure AD, more like abstracted hosted AD. I let it sit there, as this just proves my question on how to do this purely cloud-based After reading through some articles, including MS own one on Create Organizational Units in Azure AD I also realized that this is not due to a lack of implementation but by design.
I guess my precise question now is pretty simple but I really would like to get some unbiased input and notes from user-experiences regarding this: What is todays state-of-the-art basis for establishing a simple, centralized, secure access control unit like traditional AD with ldaps? I know the hype about OAuth2 and SSO services, but most of them seemed like much overhead with little organization capabilities when dealing with a lot of users/groups (but I have to note that I only took a deeper look into SAML and OAuth2 in general, because Azure implements it).
How do you do this today? Any azure-only domain administrators here?