# Identity Integration and Compatibility Matrix 2026

Source: https://startwithidentity.com/reports/identity-integration-matrix-2026/
Last updated: 2026-11-19
License: content by Start with Identity. Cite the source URL.

---

**Most workforce identity providers now reach all three big clouds. Far fewer reach your HR system, your oldest apps or each other's security signals.** Start with Identity's [Identity Integration and Compatibility Matrix](https://startwithidentity.com/tools/integration-matrix/) checks what 13 workforce [identity providers](https://startwithidentity.com/glossary/identity-provider/) and 7 [ITDR](https://startwithidentity.com/glossary/itdr/) and [identity governance](https://startwithidentity.com/glossary/iga/) platforms document about 28 and 13 integration targets. **8 of the 13 IdPs document AWS, Azure and Google Cloud.** Only **4 document a Workday connector**, only **4 document every legacy integration we checked**, and only **2 document Shared Signals in production**. On the governance and detection side, all 7 ingest [Okta](https://startwithidentity.com/vendors/iam/okta/), [Microsoft Entra ID](https://startwithidentity.com/vendors/iam/microsoft-entra/) and Active Directory, but only the 4 governance tools document all three cloud permission models.

This report covers the method, five findings, the vendor-documented limits that change a design decision, and a short checklist for buyers. Every cell in the matrix links to the vendor's own documentation, and the data is free to reuse under CC BY 4.0.

## Methodology

**Scope.** Two groups. The **workforce** group is 13 identity providers and SSO services: Okta, Microsoft Entra ID, [Ping Identity](https://startwithidentity.com/vendors/iam/ping-identity/) (PingOne and PingFederate), [OneLogin](https://startwithidentity.com/vendors/iam/onelogin/), [JumpCloud](https://startwithidentity.com/vendors/iam/jumpcloud/), Google Cloud Identity and Google Workspace, [AWS IAM Identity Center](https://startwithidentity.com/vendors/iam/aws-iam-identity-center/), [Cisco Duo](https://startwithidentity.com/vendors/mfa/duo/), [Keycloak](https://startwithidentity.com/vendors/open-source/keycloak/), [authentik](https://startwithidentity.com/vendors/open-source/authentik/), [ZITADEL](https://startwithidentity.com/vendors/open-source/zitadel/), [miniOrange](https://startwithidentity.com/vendors/iam/miniorange/) and [Idira Workforce Identity](https://startwithidentity.com/vendors/pam/cyberark/) (formerly CyberArk Identity). The **ITDR and governance** group is [SailPoint](https://startwithidentity.com/vendors/iga/sailpoint/), [Saviynt](https://startwithidentity.com/vendors/iga/saviynt/), [Veza](https://startwithidentity.com/vendors/iga/veza/), [C1](https://startwithidentity.com/vendors/iga/conductorone/) (formerly ConductorOne), [CrowdStrike Falcon Identity Protection](https://startwithidentity.com/vendors/itdr/crowdstrike-falcon-identity/), [Microsoft Defender for Identity](https://startwithidentity.com/vendors/itdr/microsoft-defender-identity/) and [Silverfort](https://startwithidentity.com/vendors/itdr/silverfort/). We chose widely deployed platforms, not a random sample.

**Columns.** Identity providers are scored on what they federate and provision to: three clouds, five HR systems, eight SaaS apps, six legacy and on-prem integrations ([Active Directory](https://startwithidentity.com/glossary/active-directory/) sync, [LDAP](https://startwithidentity.com/glossary/ldap/), [Kerberos](https://startwithidentity.com/glossary/kerberos/) or IWA, [RADIUS](https://startwithidentity.com/glossary/radius/), header-based apps and WS-Fed or AD FS relying parties) and six protocols ([SAML 2.0](https://startwithidentity.com/standards/saml-2-0/), [OpenID Connect](https://startwithidentity.com/standards/openid-connect/), WS-Fed, outbound and inbound [SCIM 2.0](https://startwithidentity.com/standards/scim-2-0/), and the [Shared Signals Framework](https://startwithidentity.com/standards/shared-signals-framework/) with [CAEP](https://startwithidentity.com/glossary/caep/)). ITDR and governance tools are scored on the identity sources they ingest: Okta, Entra ID, AD, Ping, Google Workspace, AWS IAM, Azure RBAC and Google Cloud IAM, plus the five HR systems.

**Sources.** The platform's own documentation and integration catalog, or the target's official documentation that names the platform (for example the AWS IAM Identity Center list of supported identity providers, or Slack's SCIM article). Analyst reports, reviews, forums and third-party blogs never count. Every cell was checked on November 5, 2026. We did not deploy the integrations; a "yes" means it is documented.

**What the values mean.**

| Value | Clouds and SaaS apps | HR systems | Legacy and protocols |
|---|---|---|---|
| Yes | Documented sign-in plus automated provisioning (for Google Cloud, Workforce Identity Federation counts) | A connector that creates, updates and deactivates users | Documented feature |
| Partial | SSO only, provisioning only, a generic SAML or OIDC template, or a partner connector | Import only, or the HR system pushes over SCIM | Limited: add-on, one app only, preview or experimental |
| No | Docs say it is not supported | Same | Same |
| Not documented | We could not find or read a vendor page that says either way | Same | Same |

"Not documented" is never counted as "no". For native cases (Entra ID for Azure and Microsoft 365, Google for Google Cloud and Workspace, IAM Identity Center for AWS), the cell is "yes" with a note saying so.

**Limits.** Documentation coverage varies a lot between vendors, and it drives the results. 122 of the 364 workforce cells (33.5%) are "not documented". Two vendors' documentation could not be read at all by our tools: every docs.cyberark.com page (now branded Idira Docs) returned HTTP 404, and OneLogin's knowledge base renders only with JavaScript, so their rows rely mostly on target-side docs (26 of 28 and 20 of 28 cells not documented). AWS IAM Identity Center's full application catalog is visible only in the AWS console, which leaves 17 of its 28 cells undetermined. Read the counts in this report as "documented publicly", and check a vendor's console or ask for a doc link before ruling a platform out. The script `scripts/reports/integration-matrix-report.mjs` prints every number below with its denominator.

## Finding 1: eight IdPs document all three clouds, and AWS is the common target

| Cloud target | Yes | Partial | Not documented |
|---|---|---|---|
| AWS (SAML plus SCIM into IAM Identity Center) | 11 | 2 | 0 |
| Microsoft Azure / Entra ID tenant | 8 | 1 | 4 |
| Google Cloud | 10 | 0 | 3 |
| **All three, yes** | **8 of 13** | | |

AWS is the best-documented target because AWS itself publishes setup guides for named identity providers, including Okta, Entra ID, PingOne, OneLogin, JumpCloud, Google Workspace and CyberArk, which is how the Idira and OneLogin rows get their AWS "yes". Keycloak and ZITADEL reach AWS only through generic SAML with no documented provisioning. Google Cloud's Workforce Identity Federation needs no user sync, and Google's own docs name providers such as Okta, Entra ID, PingFederate and Keycloak.

The "yes" for AWS hides differences in group sync, which matters because IAM Identity Center assigns permission sets to groups:

- AWS documents that [PingOne cannot provision groups](https://docs.aws.amazon.com/singlesignon/latest/userguide/pingone-idp.html) to IAM Identity Center over SCIM, only users.
- Google Workspace provisions users to AWS, and [AWS says it does not support SCIM group provisioning](https://docs.aws.amazon.com/singlesignon/latest/userguide/provision-automatically.html), so groups are managed by hand.
- [OneLogin does not support the SCIM DELETE operation for groups](https://docs.aws.amazon.com/singlesignon/latest/userguide/onelogin-idp.html) or multiple ACS URLs, which affects multi-Region setups.

The [AWS IAM Identity Center federation recipe](https://startwithidentity.com/recipes/aws-iam-identity-center-federation/) and the [Google Cloud Workforce Identity Federation recipe](https://startwithidentity.com/recipes/gcp-workforce-identity-federation/) walk through both setups with Entra ID and Okta.

## Finding 2: HR-driven provisioning is the thinnest column

| HR source | Workforce IdPs, yes (of 13) | Governance platforms, yes (of 4) | ITDR platforms, yes (of 3) |
|---|---|---|---|
| Workday | 4 | 4 | 0 |
| SAP SuccessFactors | 3 | 3 | 0 |
| BambooHR | 2 | 2 | 0 |
| Rippling | 2 | 0 | 0 |
| UKG | 1 | 2 | 0 |

Joiner, mover and leaver automation starts at the HR system, yet 8 of 13 identity providers do not document a Workday connector. The four that do are JumpCloud, Microsoft Entra ID, Okta and Ping Identity, and each comes with a caveat worth knowing before you design around it:

- JumpCloud's legacy Workday connector is [deprecated as of May 2026](https://jumpcloud.com/support/integrate-with-workday); the replacement is a Custom API Import that reads a Workday report.
- PingOne's [Workday connector](https://docs.pingidentity.com/pingone/integrations/p1_create_workday_connection.html) brings in full-time employees only, not contingent workers.
- Microsoft has no first-party BambooHR or UKG connector. Both appear only through a partner on Microsoft's [partner-driven integrations](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/partner-driven-integrations) page, and Rippling builds its own push into Entra's API-driven inbound provisioning.

Only Okta documents all five. Governance tools cover HR better, which is expected since the HR record is their starting point: all four document Workday. Rippling is the gap across the board, with no governance platform documenting it as a full identity source (C1 and Saviynt have connectors that sync or import accounts only). If HR-driven lifecycle matters and your IdP lacks the connector, the governance platform is often where it lives.

## Finding 3: legacy coverage falls off at Kerberos, headers and WS-Fed

| Legacy and on-prem integration | Yes (of 13) | Partial |
|---|---|---|
| Active Directory sync or agent | 10 | 1 |
| LDAP directory or LDAP interface | 10 | 0 |
| RADIUS | 6 | 3 |
| Kerberos / IWA desktop SSO | 6 | 0 |
| On-prem SAML or WS-Fed apps (AD FS replacement) | 5 | 5 |
| Header-based web apps | 5 | 3 |
| **All six, yes** | **4** | |

Directory sync is close to universal. The protocols that older line-of-business apps actually use are not. Only authentik, miniOrange, Okta and Ping Identity document all six, and they get there with on-prem components: Okta through its AD, LDAP and RADIUS agents and Okta Access Gateway, Ping through PingFederate and PingAccess, miniOrange through an LDAP Gateway, an IIS-hosted IWA module and an Access Gateway, and authentik through its LDAP, RADIUS and proxy outposts. Microsoft Entra ID documents five; its RADIUS story is the NPS extension, which adds Entra MFA to a Windows NPS server rather than making Entra a RADIUS server.

The cloud provider IdPs are the weakest here. [AWS IAM Identity Center](https://aws.amazon.com/iam/identity-center/faqs/) supports only SAML 2.0 applications, so OIDC and WS-Fed are both "no", and Google documents SAML only for custom apps. Some "yes" cells carry limits: [Okta's RADIUS agent](https://help.okta.com/en-us/content/topics/integrations/okta_radius_app.htm) supports PAP only and not Wi-Fi, [JumpCloud's Cloud LDAP](https://jumpcloud.com/support/use-cloud-ldap) is read-only, and [authentik's WS-Fed provider](https://docs.goauthentik.io/add-secure-apps/providers/wsfed/) is passive only. If you are retiring AD FS, the [AD FS to Entra ID migration recipe](https://startwithidentity.com/recipes/migrate-app-adfs-to-entra/) covers the relying-party side.

## Finding 4: inbound SCIM is common, production Shared Signals is not

Inbound SCIM, where the platform runs a SCIM server that an HR system or another IdP can provision into, is documented by **8 of 13** identity providers: authentik, AWS IAM Identity Center, Cisco Duo, JumpCloud, Keycloak, miniOrange, Okta and PingOne. Keycloak's became [supported and on by default in 26.8](https://www.keycloak.org/2026/10/keycloak-2680-released). Two more are partial: Entra ID's [API-driven inbound provisioning](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/inbound-provisioning-api-concepts) takes SCIM-shaped bulk payloads but is not a full SCIM server and needs P1 or P2, and ZITADEL's SCIM server is a preview that handles users only. Outbound SCIM to apps is documented by 8; Google's custom SCIM profiles are a [limited beta](https://knowledge.workspace.google.com/admin/users/advanced/automated-user-provisioning-with-custom-scim-profiles).

Shared Signals is a different story. Only **2 of 13** document a production SSF transmitter: [Okta](https://help.okta.com/oie/en-us/content/topics/apps/configure-shared-signal-transmitter.htm), which sends Session Revoked and Credential Change events and also receives CAEP and RISC, and authentik on its Enterprise edition. Keycloak's [SSF transmitter is experimental](https://www.keycloak.org/securing-apps/ssf-support) and not for production. Entra ID's continuous access evaluation is based on CAEP but applies to Microsoft resources, with no documented SSF stream for third parties. Google's [RISC-based Cross-Account Protection](https://developers.google.com/identity/protocols/risc) does not send events for Workspace users. Duo's only reference is an interop demo on its blog. Eight of 13 document nothing. If session revocation across vendors is part of your incident plan, ask for the transmitter and receiver docs by name.

## Finding 5: ITDR and governance tools all ingest the big three IdPs, but only governance reads cloud permissions

| Identity source | Yes (of 7) | ITDR (of 3) | Governance (of 4) |
|---|---|---|---|
| Okta | 7 | 3 | 4 |
| Microsoft Entra ID | 7 | 3 | 4 |
| Active Directory | 7 | 3 | 4 |
| Ping Identity | 5 | 2 | 3 |
| Google Workspace | 4 | 0 | 4 |
| AWS IAM | 5 | 1 | 4 |
| Azure RBAC | 4 | 0 | 4 |
| Google Cloud IAM | 4 | 0 | 4 |

Every platform in this group documents Okta, Entra ID and on-prem AD, so "deep integration with identity providers" is table stakes for the big three. Ping is where it thins: Microsoft Defender for Identity shows PingOne only in [posture recommendations](https://learn.microsoft.com/en-us/defender-xdr/identity-security/identity-security-recommendations), and Saviynt's PingOne connector is community-built. The split is cloud permissions. All four governance platforms document AWS IAM, Azure RBAC and Google Cloud IAM, though [SailPoint's Azure and GCP coverage](https://documentation.sailpoint.com/saas/help/ciem/gcp/connect_gcp.html) sits behind a separate CIEM license. None of the three ITDR platforms documents all three: CrowdStrike documents AWS IAM Identity Center, and lists Google Cloud only under its separate Falcon Shield SaaS security module; Silverfort documents read-only discovery of non-human and AI agent identities in the clouds. Microsoft Defender for Identity's docs cover none of them, while its [Okta connector](https://learn.microsoft.com/en-us/defender-for-identity/okta-defender-for-identity-overview) can revoke sessions and deactivate users in Okta.

For an [identity fabric](https://startwithidentity.com/glossary/identity-fabric/), the matrix suggests a pairing rather than one product: an IdP for sign-in and provisioning, a governance tool for cloud entitlements and HR-driven lifecycle, and an ITDR tool for detection on AD and the IdPs.

## What to ask a vendor

1. **Name the stack.** Use the matrix's stack picker with your real targets (for example AWS, Workday, Slack and AD), then ask each shortlisted vendor for a public doc link for every cell that is "partial" or "not documented".
2. **Ask about groups, not just users.** For AWS IAM Identity Center and SaaS apps that assign access by group, confirm group push and group deletion. Three of the AWS guides above document a group limit.
3. **Ask who owns the HR connector.** A connector built and run by the HR vendor or a partner changes who you call when a termination does not flow.
4. **List your legacy protocols first.** Inventory which apps use Kerberos, headers, RADIUS or WS-Fed before comparing; that list decides the shortlist more than SaaS catalog size.
5. **Ask for Shared Signals by event.** "Supports CAEP" can mean one event type, a receiver only, or Microsoft resources only. Ask which events are sent and received, and to whom.
6. **Provision with SCIM and test leavers.** The [SCIM provisioning recipe](https://startwithidentity.com/recipes/scim-provisioning-entra-okta-saas/) covers attribute mapping and deprovisioning tests, and the [Phishing-Resistant MFA Support Matrix](https://startwithidentity.com/tools/mfa-matrix/) shows which SaaS apps put SCIM on a pricier plan.

## About the data

- **Dataset:** the [Identity Integration and Compatibility Matrix](https://startwithidentity.com/tools/integration-matrix/), 20 platforms and 455 cells, downloadable as CSV and JSON (below). Every cell carries a note, a status, the vendor documentation URL and a check date. Each platform has a stable anchor (`/tools/integration-matrix/#<slug>`).
- **Reproduce it:** `node scripts/reports/integration-matrix-report.mjs` prints every figure in this report with its denominator. `scripts/verify-integrations.mjs` validates the records and writes the downloads.
- **Re-checks:** integration catalogs change monthly. We plan to re-verify the matrix quarterly and to re-run the Idira and OneLogin rows as soon as their documentation is readable.
- **License and citation:** CC BY 4.0. Cite as "Start with Identity, Identity Integration and Compatibility Matrix 2026" with a link to this page. Each key finding has a stable anchor (for example `#finding-2`).
- **Corrections:** if you are a vendor and a cell is wrong or "not documented" when you have a public page, send the link through the [contact page](https://startwithidentity.com/contact/). We update from public documentation only and date every change.
