IT Glossary
Active Directory is Microsoft's on-premises directory service for Windows identities. Learn how AD works and where it stops covering your SaaS apps.
August 7, 2026
Active Directory (AD) is Microsoft's on-premises directory service that stores user accounts, groups, and computers for a Windows network and authenticates them through Kerberos and LDAP. Shipped with Windows 2000 Server, it remains the identity backbone of most European mid-market companies, including those now running the majority of their software in the cloud.
Active Directory governs Windows resources, not SaaS. When a team buys Slack, Notion, or Figma outside the domain, those accounts live entirely outside AD. That is where orphaned accounts and shadow IT accumulate: disabling an AD account does nothing to the fifty cloud tools a departing employee also had access to.
A 300-person manufacturer runs AD for file shares, VPN, and Windows logins, synced to Microsoft Entra ID for Microsoft 365. HR triggers an AD account on day one and the process works. The gap appears at offboarding: AD is disabled in minutes, but the engineer keeps an active GitHub, Datadog, and Miro seat because none of them was ever federated. Closing that gap needs a SaaS-aware governance layer on top of the directory, which is what Corma adds by connecting to the directory and covering the applications it never saw.
No. Active Directory is the on-premises directory built on Kerberos and LDAP. Microsoft Entra ID, formerly Azure AD, is the cloud identity service built on SAML, OAuth 2.0, and OpenID Connect. Most companies run both and keep them in sync with Entra Connect.
Yes. AD still handles Windows domain logins, file servers, VPN authentication, and legacy applications, even in companies whose daily work has moved almost entirely to SaaS.
An orphaned account is an AD object that no longer maps to an active employee or owner, usually left behind after a departure or a closed project. It is one of the most common findings in ISO 27001 and NIS2 audits.
Only for applications federated to AD or to Entra ID. Any SaaS tool with its own local login keeps working until someone deactivates the account inside that tool.