Running two identity providers at once: coexistence patterns that work
Reviewed 2026-11-10 · Editorial assessment by the editors
By the editors · 2 min read
Plenty of organisations run two identity providers on purpose, most often Okta in front of Entra ID. It works when each app has one clear owner, policies are kept aligned, and every change has a rollback. The cost is two licences, two consoles and two policy sets.
Why would anyone run two?
Usually because each one is strong where the other is not. Entra ID is the directory Microsoft 365 needs, and its P1 or P2 licence may already be paid. Okta brings a larger published catalog for non-Microsoft SaaS and signals from security tools such as CrowdStrike, Zscaler and Jamf. Others arrive through an acquisition, or through a trial of a new provider that has not yet replaced anything.
Pattern 1: Okta in front of Entra ID
Okta's Microsoft Office 365 integration federates Microsoft 365 sign-in to Okta over WS-Federation or SAML and provisions users, groups and attributes into Microsoft 365. Users sign in at Okta for everything, while Entra ID stays underneath as the directory. The Microsoft 365 domain is federated to Okta.
Pattern 2: one provider's policy, another's factor
With External MFA, which Microsoft lists as generally available in February 2026, Entra ID keeps enforcing Conditional Access while a preferred MFA provider handles the factor. This lets a team adopt a different sign-in method without moving policy.
Pattern 3: split by group or by app
Move one group or one set of apps and leave everything else alone. On the Microsoft side, staged rollout sends pilot groups to cloud authentication while the rest of the domain stays federated. For SaaS apps, a separate SAML or OpenID Connect connection on a test instance of the app lets a second provider handle sign-in without touching production.
Pattern 4: share risk signals between them
Two providers are safer when each knows what the other has seen. The Shared Signals Framework and CAEP exist for this: one system can tell another that a device has become non-compliant or a session looks risky, so access is re-evaluated.
What should a coexistence claim cover?
NewCore adds agent governance alongside Okta or Entra ID, without moving employee sign-in. Later identity provider adoption is a separate path. The NewCore agent profile explains that division.
What keeps two providers manageable?
- Give every app one authoritative identity provider and write it down.
- Keep one policy baseline and review both engines against it on a schedule.
- Write the rollback step before every change.
- Price both licences honestly; the calculator shows list prices side by side.