S1 Published pre-built integrations
Called for Okta
Okta's Integration Network lists more than 8,000 pre-built integrations. Microsoft describes the Entra app gallery as thousands of applications without publishing a count.
Reviewed 10 November 2026
Reviewed 2026-11-10 · Editorial assessment by the editors
Okta has the larger published catalog of pre-built SSO integrations; Entra ID is the natural sign-in layer for Microsoft 365 and includes unlimited SSO across SaaS apps even in its free tier. On protocols they are level. Pick on where your apps live.
1 ties · 0 depends · 4 criteria
Called for Okta
Okta's Integration Network lists more than 8,000 pre-built integrations. Microsoft describes the Entra app gallery as thousands of applications without publishing a count.
Tie
Both federate apps over SAML 2.0 and OpenID Connect and both offer password-based SSO for apps that cannot federate. Microsoft also lists linked SSO in its gallery; Okta lists WS-Federation and SWA on its Microsoft 365 integration.
Called for Entra ID
Microsoft 365 authenticates against Entra ID natively. Okta supports it by federating the Microsoft 365 domain to Okta over WS-Federation or SAML, which works and leaves Entra ID in place underneath.
Called for Entra ID
Entra ID Free, included with Microsoft cloud subscriptions, lists unlimited SSO across SaaS apps. Okta's lowest tier, Starter, is $6 per user per month with a $1,500 annual minimum.
On published numbers, yes. Okta shows more than 8,000 pre-built integrations and its catalog filter counted 8,367 on 27 September 2026. Microsoft says its gallery contains thousands of applications and does not give a figure. A published count is not the same as coverage of your apps, so the practical test is to take your top 50 applications and check each one in both catalogs before you decide.
Both catalogs also allow custom SAML and OIDC apps, so a missing gallery entry means more configuration work, not a blocked app.
Okta's Microsoft Office 365 integration federates your Microsoft 365 domain so that users authenticate at Okta and are passed to Microsoft 365. The same integration provisions users and groups and writes attributes back. Entra ID still holds the user objects that Microsoft 365 needs; Okta sits in front of it.
This is the pattern to expect if you choose Okta in a Microsoft 365 organisation: two identity systems, with Okta deciding sign-in and Entra ID serving Microsoft's own apps. Microsoft documents how to reverse it, starting with a staged rollout for pilot groups.
Entra ID. Microsoft lists unlimited SSO across SaaS apps in Entra ID Free, which comes with Microsoft cloud subscriptions. Okta Starter, at $6 per user per month billed annually with a $1,500 minimum, bundles SSO with MFA and Universal Directory. If SSO is the whole requirement and you already have Microsoft 365, the free tier covers it.
Yes. Microsoft lists SAML and OpenID Connect among the SSO options for applications, and custom apps can be configured outside the gallery.
Okta's Integration Network lists more than 8,000 pre-built integrations; the catalog filter showed 8,367 on 27 September 2026.
Yes. Okta's Microsoft Office 365 integration supports WS-Federation and SAML sign-in and user provisioning. Entra ID remains the directory Microsoft 365 uses underneath.
Read dates are recorded beside each source.