Rich integration with Azure AD- All identity data in Azure AD is seamlessly synced to AADDS, no tools, software, or connectors required.

Simplified deployment experience – All services are deployed within a matter of hours and ready for prime time.

Now that we are past the things to be aware of, let’s talk benefits and the simplicity gained from a deployment and migration to AADDS. If you ask me, required that this connection has redundancy as leveraging the cloud with a single connection will leave sites and locations in the dark if network connectivity is disrupted.

A Site-to-Site VPN or Express Route connection is required for any site or location that will need access to AADDS, and it is highly preferred.

Computers joined to On-Premise Active Directory will need to be migrated to AADDS.

Any additional DNS zones created in AADDS and other objects that qualify for forest-level sync will need to be made at the domain level since AADDS is a managed service.

So, any GPOs within AADDS will require item-level targeting via Groups. Moving users outside of this container is not permitted.

Users will reside in a single container, AADDC Users.

However, since this is a managed service, it is essential to note that you see what you get.

Schema Customizations are not possible – Most organizations will be okay with this.

However, since AADDS is mainly designed for servers and datacenter infrastructure, most organizations will be alright. When it comes to AADDS there are a few key roles at play to ensure it’s the right fit for your organization.

Ds active directory