Pre-built integrations explained: what an identity provider's app catalog gives you
Reviewed 2026-11-10 · Editorial assessment by the editors
By the editors · 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.
What is inside a pre-built integration?
When an administrator connects an application to an identity provider, someone has to supply the details: which protocol the app speaks, where to send the user, which attributes the app expects and, for account creation, which API to call. A pre-built integration is a catalog entry where the identity provider or the app vendor has done that work in advance. The admin picks the app, fills in a few values such as the tenant name, and assigns users.
Entries differ in depth. Some cover sign-in only, over SAML 2.0, OpenID Connect or password-based SSO. Others add automated provisioning, usually over SCIM, so accounts are created and updated from the identity provider.
How large are the catalogs?
Each vendor describes its catalog in its own units, which is why published figures are hard to compare:
- Okta: the Okta Integration Network lists more than 8,000 pre-built integrations, 8,367 in the catalog filter on 27 September 2026, with 943 marked for provisioning.
- Microsoft Entra ID: Microsoft says the Entra app gallery contains thousands of applications and lists SAML, OpenID Connect, password-based and linked SSO, plus automated provisioning. It publishes no count.
- Ping Identity: its marketplace describes 6,500+ orchestrated capabilities across 350+ connectors, a different unit from app entries.
- Google Cloud Identity: Google describes thousands of pre-integrated SAML 2.0 and OpenID Connect apps.
- JumpCloud: an application catalog is offered; we found no count on the pages reviewed.
What if an app is not in the catalog?
Most apps that support SAML or OpenID Connect can still be connected by hand: the admin copies the app's metadata into the identity provider and the identity provider's metadata into the app. Microsoft notes that custom apps can be configured outside the gallery. Apps with no federation support fall back to password-based SSO, where the identity provider stores the app's own credentials. Each hand-built connection is one more thing your team maintains when the app changes its settings.
How do you check your own app list?
Start with an inventory, which is also the first step Microsoft documents for moving apps off Okta. For each app, record four things: whether it is in the candidate's catalog, whether that entry includes provisioning, whether it needs a custom SAML or OpenID Connect setup, and whether it only supports passwords. Count each group. A provider with a larger catalog helps only if your apps are in it.
Where does this matter on this site?
Catalog size is our heaviest criterion, at 18 percent of the weighted score, and the first row on the verdict. The single sign-on comparison calls Okta and Entra ID on catalog, protocols and Microsoft 365 sign-in.