Azure AD Domain Services and Exchange online relationship

Lando 1 Reputation point
2020-12-29T18:02:55.72+00:00

I have an environment that has no on premises AD, but is using Exchange online for email and I see the email users in Azure active directory.
It seems that the best path would be to azure domain join computers to the existing azure active directory, then manage these devices via Microsoft Endpoint Manager and skip any on premise AD setup. (Or at least test this option to see if it meets there needs.)

I'm trying to understand the relationship between Exchange online and Azure active directory.
Is Azure active directory created automatically when Exchange online is setup for a tenant?
And then is Azure AD Domain Services created as well?

Thanks for your help.

Microsoft Security | Microsoft Entra | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Andreas Baumgarten 124K Reputation points MVP Volunteer Moderator
    2020-12-29T20:54:18.993+00:00

    If you setup up Exchange Online an Azure tenant with an Azure Active Directory (AAD) is created/deployed as well.
    For Exchange Online an AAD is mandatory.

    The Azure Active Directory Domain Services (AADDS) are not created automatically. The AADDS is not required for Exchange Online.


    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten

    0 comments No comments

  2. Jon Alfred Smith 541 Reputation points
    2020-12-29T21:30:52.92+00:00

    No Azure AD is created. When Andreas Baumgarten talkes about "created", I believe he means configured. Azure AD is a shared resource, the backbone for Microsoft's three cloud platforms (Microsoft / Office 365; Azure and Dynamics 365). It's called Identity as a Service, your next-generation Active Directory.

    The concept of tenant means that you rent a small part of Azure AD. What happens in the background is that your tenant, your small portion of Azure AD, is set up with strong isolated security. This architecture is called multi-tenancy. (Local AD is single-tenancy, at least for most of the time.) Such an approach is used by all cloud providers, Dropbox, Salesforce etc.

    Azure AD does much of the same things as your local Windows AD DS. But it has no group policies. Make sure you sign up for a license with Intune and Azure AD Premium P1 for conditional access. Then you have Intune with MDM/MAM, in practical terms Configuration Manager for the cloud, combined with group policies for the cloud. Microsoft 365 Business Premium is a good and cost-effective choice.

    You might wonder: Is the schema for Exchange Online extended in Azure AD? No. Exchange uses its own directory store: Exchange Online Directory Services (EXODS). Same thing for Skype and SharePoint. These stores communicate with Azure AD and use it for authentication and so on. Perhaps a bit over-simplified, but you'll get the idea.

    You should definitely Azure AD-join your computers and have them enrolled in Microsoft Intune, part of Microsoft Endpoint Manager. Your IT-life will never be the same again.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.