Skip to content
Okta vs Entra

Reviewed 10 November 2026

Directories and sync: how Active Directory connects to Okta and Entra ID

Reviewed 2026-11-10 · Editorial assessment by the editors

By the editors · 3 min read

Most companies still hold their users in on-premises Active Directory, and the cloud identity provider needs a copy. Okta imports users and groups through its AD agent; Entra ID syncs them with Entra Connect or lighter cloud provisioning agents. How passwords are checked after that is a separate choice with its own options.

Why does a cloud identity provider need a directory?

An identity provider can only sign in users it knows about. It needs a list of people, their groups and the attributes applications ask for, such as department or email address. In a company that has run Windows for years, that list usually lives in Active Directory on premises, so the first job of any cloud identity provider is to get a trustworthy copy of it.

Each provider keeps its own cloud directory for this. Okta lists Universal Directory in every plan from Starter. Entra ID is itself the directory that Microsoft 365 runs on. JumpCloud describes a cloud directory, and Ping includes a directory in PingOne for Workforce Essential.

How do users get from Active Directory to the cloud?

Through a small piece of software installed on premises. Okta's AD agent imports Active Directory users and groups into Okta. For Entra ID, Microsoft offers Entra Connect, a sync server, or cloud provisioning agents, which are lighter and managed from the cloud. Microsoft lists one or the other as a prerequisite for moving Microsoft 365 sign-in off Okta.

In organisations that use both Okta and Microsoft 365, both can be in place at once: Okta imports from Active Directory for its own apps, and Entra Connect keeps Entra ID in step for Microsoft 365.

Where is the password checked?

Once users are in the cloud directory, someone still has to check their password or passwordless credential at sign-in. Entra ID documents two options when it takes over from a federated provider: password hash synchronization, which extends the sync so users sign in to Entra ID with their Active Directory password, and pass-through authentication, where an on-premises agent checks the password against Active Directory. With passwordless methods such as passkeys, the password question matters less, but the directory copy still has to be right.

What about apps that still speak LDAP or RADIUS?

VPNs, Wi-Fi and older applications often authenticate over LDAP or RADIUS rather than SAML or OpenID Connect. Some cloud providers cover this directly: Ping includes LDAP, Kerberos and a RADIUS gateway in PingOne for Workforce Essential, JumpCloud offers cloud LDAP and cloud RADIUS, and Google lists Secure LDAP in Cloud Identity Premium. Microsoft documents provisioning into on-premises apps over LDAP, SQL, REST and SOAP connectors, which is about accounts rather than sign-in.

What if you have more than one Entra tenant?

Acquisitions often bring a second Microsoft tenant. Cross-tenant synchronization creates, updates and removes B2B collaboration users across tenants an organisation owns. Each synced user needs P1 in the source tenant. The verdict covers how this plays into the mergers use case.

Next lesson: Phishing-resistant MFA