Updated: February 6, 2024 (September 19, 2016)

  Analyst Report

Integrating AD and Azure Active Directory

My Atlas / Analyst Reports

1,323 wordsTime to read: 7 min
Wes Miller by
Wes Miller

Wes Miller analyzes and writes about Microsoft’s security, identity management, and systems management technologies. Before joining Directions on Microsoft, Wes... more

Organizations deploying Microsoft’s hosted services, including Office 365, Intune, and Azure, already use Azure Active Directory (AAD) to authenticate to these services and enforce licensing compliance. Organizations with both AAD and on-premises directories need to integrate those directories to integrate management and simplify sign-on for users. Ongoing changes and updates to AAD, including management, security, and reporting features, require staying alert to avoid redundant AAD tenancies and ensure proper integration with on-premises directories.

Azure Active Directory Fundamentals

AAD is a multitenant, Microsoft-hosted identity and access management (IAM) service, used primarily for managing user identity. AAD stores information about users (such as the user’s name, organization, and privileges) as directory objects and associated attributes in a tenancy. An AAD tenancy is a distinct, logically independent directory for an individual organization or division of an organization (the tenant), typically associated with an organizational domain name. Tenancies are created automatically when an individual from that organization subscribes to a new instance of a Microsoft-hosted service that relies on AAD, such as Azure or Office 365 services.

Atlas Members have full access

Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.

Membership Options

Already have an account? Login Now