Identity Integration and Compatibility Matrix
Which of 13 workforce identity providers connect to AWS, Azure and Google Cloud, your HR system, your SaaS apps and your on-prem directories, and which 7 ITDR and governance tools ingest which identity sources. Tick your stack to see who covers all of it. Every cell links to the vendor's own documentation.
Pick targets above to see which platforms document all of them.
Compact view: hover or tap a cell for the note; each cell links to its source. Pick a column group for notes inline.
- authentikOpen-source IdP
20 yes, 2 partial of 28 columns: show all
- Azure / Entra
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Microsoft 365
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- AWS IAM Identity CenterCloud provider IdP
4 yes, 5 partial of 28 columns: show all
- Azure / Entra
- Not documentedno documented federation of Entra ID to Identity Center as IdP
- Google Cloud
- Not documentedno Google Cloud doc listing Identity Center as IdP
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- Not documentedno desktop SSO documented
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM out
- SCIM in
- SSF / CAEP
- Cisco Duo (Duo SSO and Duo Directory)MFA and SSO
14 yes, 5 partial of 28 columns: show all
- Azure / Entra
- YesEntra tenant domain federated to Duo SSO (SAML + WS-Trust) with user and group provisioningSource
- Google Cloud
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Microsoft 365
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- Google Cloud Identity and Google WorkspaceCloud provider IdP
12 yes, 7 partial of 28 columns: show all
- Azure / Entra
- Google Cloud
- Workday
- SuccessFactors
- Not documentedno inbound HR connector found
- BambooHR
- Not documentedno inbound HR connector found
- Rippling
- Not documentedno inbound HR connector found
- UKG
- Not documentedno inbound HR connector found
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- Not documentedno Kerberos or IWA desktop SSO found
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- Not documentedno SCIM server endpoint found
- SSF / CAEP
- Idira Workforce Identity (formerly CyberArk Identity)Commercial IdP
2 yes, 0 partial of 28 columns: show all
- Azure / Entra
- Not documentedMicrosoft federation compatibility page silent; vendor docs not machine-readableSource
- Google Cloud
- Not documentedno CyberArk guide in Google Workforce Identity Federation docs; vendor docs not machine-readableSource
- Workday
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- SuccessFactors
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- BambooHR
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Rippling
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- UKG
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Microsoft 365
- Not documentedMicrosoft federation compatibility page silent; vendor docs not machine-readableSource
- Google Workspace
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Salesforce
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Slack
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- GitHub
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Atlassian
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- ServiceNow
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Zoom
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Active Directory
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- LDAP
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Kerberos / IWA
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- RADIUS
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- Header-based
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- AD FS apps
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- SAML
- OIDC
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- WS-Fed
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- SCIM out
- Not documentedSCIM 2.0 to AWS shown in AWS guide; generic SCIM outbound not verified, vendor docs not machine-readableSource
- SCIM in
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- SSF / CAEP
- Not documenteddocs not machine-readable (docs.cyberark.com, now Idira Docs, returned HTTP 404 to every fetch)
- JumpCloudCommercial IdP
20 yes, 3 partial of 28 columns: show all
- Azure / Entra
- YesEntra ID domain federation (SAML or WS-Fed) + M365 Cloud Directory Integration provisioningSource
- Google Cloud
- YesGoogle Workspace/Cloud Identity SAML SSO + Google Workspace Cloud Directory Integration provisioningSource
- Workday
- YesWorkday Custom API Import via RaaS report; create, update, deprovision; legacy connector deprecated May 2026Source
- SuccessFactors
- BambooHR
- PartialBambooHR pushes via SCIM (one-way, managed by BambooHR); Custom API connector for extra attributesSource
- Rippling
- UKG
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- YesActive Directory Integration agents on DCs or member servers; two-way sync of users, groups, passwordsSource
- LDAP
- Kerberos / IWA
- Not documentedno Kerberos or IWA desktop SSO docs found
- RADIUS
- Header-based
- AD FS apps
- Not documentedno AD FS migration or WS-Fed relying party docs found
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- Not documentedno SSF or CAEP docs found
- KeycloakOpen-source IdP
7 yes, 12 partial of 28 columns: show all
- Azure / Entra
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- Microsoft Entra IDCommercial IdP
22 yes, 6 partial of 28 columns: show all
- Azure / Entra
- Google Cloud
- YesGoogle documents Workforce Identity Federation with Entra ID (OIDC or SAML); Entra gallery also provisions Google Cloud / WorkspaceSource
- Workday
- SuccessFactors
- BambooHR
- PartialNo Microsoft connector; listed under partner Aquera HR Sync connectors, or build on API-driven inbound provisioningSource
- Rippling
- UKG
- Google Workspace
- Slack
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- YesLDAP interface via Entra Domain Services managed domain; provisioning agent can also write to LDAP directoriesSource
- Kerberos / IWA
- YesDesktop SSO via Kerberos tickets on domain-joined devices (Entra Connect feature); PRT SSO on Entra joined devicesSource
- RADIUS
- PartialNPS extension on Windows NPS adds Entra MFA to RADIUS; primary auth stays in AD, no native RADIUS serverSource
- Header-based
- AD FS apps
- YesDocumented AD FS app migration; SAML and WS-Fed apps as enterprise apps or app registrationsSource
- SAML
- OIDC
- SCIM in
- PartialAPI-driven inbound provisioning: Graph /bulkUpload accepts SCIM bulk payloads, not a full SCIM server; P1/P2Source
- SSF / CAEP
- PartialContinuous access evaluation based on CAEP, but for Microsoft resources (Exchange, SharePoint, Teams, Graph); no documented SSF stream for third partiesSource
- miniOrange Workforce IAMCommercial IdP
22 yes, 3 partial of 28 columns: show all
- AWS
- YesSAML to IAM Identity Center as external IdP + SCIM provisioning; IAM SAML roles also documentedSource
- Azure / Entra
- YesMicrosoft 365/Entra ID federation via SAML or WS-Fed + users, groups and license provisioningSource
- Google Cloud
- YesSAML SSO via Google Admin third-party IdP + Google Workspace provisioning app; no Workforce Identity Federation guide foundSource
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Google Workspace
- Atlassian
- PartialSAML SSO to Jira Cloud via Atlassian Access; no Atlassian Cloud provisioning guide foundSource
- ServiceNow
- Zoom
- Active Directory
- LDAP
- YesLDAP directory integration via LDAP Gateway (sync and authentication); no LDAP interface for apps documentedSource
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- Not documentedno SSF or CAEP docs found
- Okta Workforce IdentityCommercial IdP
28 yes, 0 partial of 28 columns: show all
- Azure / Entra
- YesEntra tenant domain federation (WS-Fed) plus user and group provisioning via Microsoft Office 365 appSource
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM out
- SCIM in
- SSF / CAEP
- YesSSF transmitter (Session Revoked, Credential Change) and receiver (CAEP, RISC); Identity Threat ProtectionSource
- OneLogin Workforce IdentityCommercial IdP
7 yes, 1 partial of 28 columns: show all
- Azure / Entra
- Not documentedOneLogin docs not machine-readable
- Google Cloud
- Not documentedno OneLogin-specific Workforce Identity Federation guide found
- Workday
- SuccessFactors
- Not documentedOneLogin docs not machine-readable
- BambooHR
- Not documentedOneLogin docs not machine-readable
- Rippling
- Not documentedOneLogin docs not machine-readable
- UKG
- Not documentedOneLogin docs not machine-readable
- Microsoft 365
- Not documentedOneLogin docs not machine-readable
- Google Workspace
- Not documentedOneLogin docs not machine-readable
- Salesforce
- Not documentedOneLogin docs not machine-readable
- Atlassian
- ServiceNow
- Not documentedOneLogin docs not machine-readable
- Zoom
- Active Directory
- LDAP
- Not documentedOneLogin docs not machine-readable
- Kerberos / IWA
- Not documentedOneLogin docs not machine-readable
- RADIUS
- Header-based
- Not documentedOneLogin docs not machine-readable
- AD FS apps
- Not documentedOneLogin docs not machine-readable
- SAML
- OIDC
- WS-Fed
- Not documentedOneLogin docs not machine-readable
- SCIM in
- SSF / CAEP
- Not documentedno OneLogin SSF or CAEP documentation found
- Ping Identity (PingOne and PingFederate)Commercial IdP
20 yes, 3 partial of 28 columns: show all
- AWS
- YesPingOne SAML + SCIM to IAM Identity Center (users only, no group SCIM); PingFederate SCIM guide also existsSource
- Azure / Entra
- YesPingOne WS-Fed/WS-Trust federation of Entra ID domain + Microsoft Azure (Office 365) provisioning connectorSource
- Google Cloud
- Workday
- YesPingOne inbound and outbound Workday connector; full-time employees only, no contingent workersSource
- SuccessFactors
- Not documentednot in PingOne provisioning connector list; documented only for PingOne Advanced Identity CloudSource
- BambooHR
- Rippling
- UKG
- Microsoft 365
- YesPingOne WS-Fed (passive) and WS-Trust (active) for Microsoft 365 + Microsoft Azure (Office 365) provisioning connectorSource
- Google Workspace
- Salesforce
- YesPingOne Salesforce provisioning connector; SAML SSO guides for PingFederate and PingOne for EnterpriseSource
- Slack
- GitHub
- YesPingOne GitHub EMU provisioning connector (users and groups); SAML SSO guides for PingFederateSource
- Atlassian
- PartialSAML SSO guides (PingFederate, PingOne for Enterprise); no PingOne Atlassian provisioning connector listedSource
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- RADIUS
- Header-based
- SAML
- OIDC
- SCIM in
- SSF / CAEP
- Not documentedno SSF or CAEP docs found for PingOne or PingFederate
- ZITADELOpen-source IdP
4 yes, 7 partial of 28 columns: show all
- Azure / Entra
- Workday
- SuccessFactors
- BambooHR
- Rippling
- UKG
- Google Workspace
- Atlassian
- ServiceNow
- Zoom
- Active Directory
- LDAP
- Kerberos / IWA
- Not documentednot found in docs
- RADIUS
- Not documentednot found in docs
- Header-based
- SAML
- OIDC
- WS-Fed
- Not documentednot found in docs
- SCIM in
- SSF / CAEP
- Not documentednot found in docs
How to read it
Yes means the vendor (or the target, such as AWS or Slack) documents the integration. For clouds and SaaS apps that means sign-in plus automated provisioning; for HR systems, a connector that creates, updates and deactivates users. Partial means something is missing, for example SAML only with no provisioning, a generic template, a partner connector or a preview. No means the docs say it is not supported. Not documented means we could not find or read a vendor page that says either way (34% of workforce cells), which is a finding about the documentation, not proof the feature is missing.
The two tabs use different columns: identity providers are scored on what they federate and provision to, ITDR and governance tools on which identity sources they ingest. Full definitions are in the dataset schema. Download the data as CSV or JSON. Example: for AWS, Workday, Slack and Active Directory, 4 platforms document full support for all four (JumpCloud, Microsoft Entra ID, Okta Workforce Identity and Ping Identity).
Set it up
- Federate AWS IAM Identity Center with Entra ID or Okta
- Google Cloud Workforce Identity Federation
- SCIM provisioning from Entra ID or Okta into a SaaS app
- Migrate an app from AD FS to Entra ID
- SCIM 2.0, SAML 2.0, OpenID Connect and Shared Signals Framework explained
- Phishing-Resistant MFA Support Matrix: SSO plan and SCIM support on the app side
- IAM platform rankings, ITDR tools and IGA tools
SSF / CAEP in preview or limited form: Keycloak and Microsoft Entra ID. Inbound SCIM (another system can provision into the platform) documented by 8 of 13.
About the matrix
- Which SSO integrates with AWS, GCP, and Azure?
- Of the 13 workforce identity platforms in this matrix, 8 document federation to all three clouds (AWS sign-in with provisioning, an Entra ID tenant or Azure portal as a target, and Google Cloud through Workforce Identity Federation or Cloud Identity with provisioning): authentik, Cisco Duo, Google Cloud Identity and Google Workspace, JumpCloud, Microsoft Entra ID, miniOrange Workforce IAM, Okta Workforce Identity and Ping Identity. Checked against vendor and cloud provider documentation on 2026-11-05. Tick AWS, Azure and Google Cloud in the stack picker for the current list and the source behind each cell.
- Which identity provider is best at integrating with old SSO systems?
- For legacy and on-prem systems, 4 of 13 workforce platforms document all six legacy integrations we check (Active Directory sync, LDAP, Kerberos or IWA desktop SSO, RADIUS, header-based web apps and on-prem SAML or WS-Fed apps): authentik, miniOrange Workforce IAM, Okta Workforce Identity and Ping Identity. Coverage drops on the older protocols: 6 document Kerberos or IWA, 5 header-based apps and 5 WS-Fed relying parties or AD FS migration. "Best" depends on which of those your apps use, so pick them in the stack picker.
- How to integrate IAM with AWS, Azure and GCP?
- Use one workforce identity provider as the source of truth and federate each cloud to it: SAML plus SCIM into AWS IAM Identity Center, domain federation or provisioning into Microsoft Entra ID (or use Entra ID as the IdP), and Workforce Identity Federation into Google Cloud, which needs no user sync. 8 of the 13 platforms here document all three. SWI's recipes walk through AWS IAM Identity Center federation, Google Cloud Workforce Identity Federation and SCIM provisioning from Entra ID or Okta step by step.
- IAM platform comparison for regional banks core banking integration
- Core banking systems are not a column: the matrix records only integrations named in vendor documentation, and we did not survey core banking connectors. What it does show is on-prem reach: 4 workforce platforms (authentik, miniOrange Workforce IAM, Okta Workforce Identity and Ping Identity) document Active Directory, LDAP, Kerberos or IWA, RADIUS, header-based and on-prem SAML or WS-Fed integration. If your core banking front ends authenticate through any of those, check those columns, then ask the vendor for a named reference integration with your core provider.
- Which leading ITDR platforms offer deep integration with identity providers?
- All 3 ITDR platforms in the matrix (CrowdStrike Falcon Identity Protection, Microsoft Defender for Identity and Silverfort Identity Security Platform) document ingesting Okta, Microsoft Entra ID and on-prem Active Directory. 2 of them also document Ping Identity as a full source: CrowdStrike Falcon Identity Protection and Silverfort Identity Security Platform. Cloud IAM is the weak spot for ITDR: none of the 3 document ingesting AWS IAM, Azure RBAC and Google Cloud IAM together, against 4 of 4 identity governance platforms.
- Which identity fabric solutions offer the best integration with cloud platforms?
- Among governance and ITDR platforms, 4 of 7 document connectors for all three cloud permission models (AWS IAM, Azure RBAC and Google Cloud IAM): C1, SailPoint Identity Security Cloud, Saviynt Identity Cloud and Veza Access Platform. Among workforce identity providers, 8 of 13 document sign-in federation to AWS, Azure and Google Cloud. An identity fabric usually combines one of each, so use both tabs of the matrix.
- Which identity providers support Workday as an HR source?
- 4 of 13 workforce identity platforms document a Workday connector that creates, updates and deactivates users: JumpCloud, Microsoft Entra ID, Okta Workforce Identity and Ping Identity. Only Okta Workforce Identity documents all five HR systems we check (Workday, SAP SuccessFactors, BambooHR, Rippling and UKG). Identity governance tools cover HR better: 4 of 4 document Workday as an identity source.
- How is this matrix sourced and can I reuse it?
- The matrix has 455 cells. Every Yes, Partial and No (314) links to the platform's own documentation or integration catalog, or to the target's official docs that list the platform, with a check date. "Not documented" (141 cells) means we could not find or read a vendor page that says either way, never that the feature is missing. The data is CC BY 4.0: download the CSV or JSON, cite the page and link back. Send corrections with a public doc link through the contact page.