Skip to content
Okta vs Entra

Reviewed 10 November 2026

Workforce identity university: glossary and nine lessons in three tracks

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

Reference material for readers comparing identity providers: a glossary of 64 workforce identity terms and 9 short lessons in three tracks. Start with Basics if you are new to identity providers, or go straight to the track for the decision in front of you.

What is in the glossary?

64 terms, from Adaptive MFA to WS-Federation, in one to three sentences each. Terms that come from a standard or a regulator link to the source.

Basics

How single sign-on works, what an app catalog gives you, and how directories connect.

Lesson 1

How single sign-on works: SAML, OpenID Connect and the identity provider

3 min read

In single sign-on the user authenticates once at an identity provider, which then vouches for them to each application with a signed message. SAML sends an XML assertion; OpenID Connect sends a signed ID token on top of OAuth 2.0. Applications trust the signature, so the key that makes it is the most valuable secret in the setup.

Lesson 2

Pre-built integrations explained: what an identity provider's app catalog gives you

3 min read

A pre-built integration is a catalog entry that already holds an app's sign-in settings, and often its provisioning connector, so an admin configures it instead of building it. Okta publishes a count of more than 8,000; Microsoft says thousands without a number. The count matters less than whether your own apps are in the catalog.

Lesson 3

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

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.

Sign-in and access

Phishing-resistant sign-in, the policy that decides each sign-in, and the tokens that carry it.

Lesson 4

What makes MFA phishing-resistant, and how NIST grades authenticators

3 min read

MFA is phishing-resistant when the credential is bound to the real site or device, so a fake sign-in page cannot relay it. Passkeys, FIDO2 security keys, Windows Hello for Business and certificate-based authentication are on Microsoft's phishing-resistant list; a code typed from a phone is not. NIST sets out three authenticator assurance levels in SP 800-63B-4.

Lesson 5

Conditional access and adaptive MFA explained: how sign-in policy decides

3 min read

Sign-in policy is the set of if-then rules an identity provider runs before it lets someone in: who the user is, which device and network they are on, which app they want and how risky the attempt looks. In Entra ID the engine is Conditional Access, which needs P1. In Okta it is Adaptive MFA and device assurance, from Core Essentials.

Lesson 6

Tokens, assertions and signing keys: what an identity provider must protect

3 min read

After sign-in, access runs on tokens: SAML assertions and ID tokens say who the user is, and access tokens say what an app or agent may call. They are only as safe as the key that signs them and the time they stay valid. NIST IR 8587, final on 15 September 2026, is the current federal guidance on protecting them.

Buying and moving

Reading pricing pages, running two identity providers at once, and moving Microsoft 365 sign-in.

Lesson 7

How to read an identity provider pricing page: tiers, minimums and bundles

3 min read

Per-user list prices are only the start. Check the billing basis, any minimum contract or user count, what is already bundled into licences you own, which features are add-ons, and which tiers are priced only by quote. Two providers with the same headline price can cost very different amounts for your organisation.

Lesson 8

Running two identity providers at once: coexistence patterns that work

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.

Lesson 9

Federated and managed domains: how Microsoft 365 sign-in moves between providers

2 min read

A Microsoft 365 domain is either federated, sending users to an outside identity provider such as Okta, or managed, signing them in with Entra ID. Moving sign-in between providers means changing that setting. Microsoft documents doing it in stages: pilot groups first with staged rollout, then the whole domain.

How was this written?

Desk research from standards pages, regulator publications and vendor documentation, checked between 27 and 29 September 2026. No hands-on testing. The method explains how the comparison pages use the same sources.

Frequently asked questions

Where should I start?

With how single sign-on works, then the other two Basics lessons. If you are pricing a change, go to reading pricing pages.

Are the lessons vendor documentation?

No. They are short explanations written from standards, regulator publications and vendor pages, each linked at the end of the lesson, and they point to the comparison pages where the concept decides a call.