Skip to content
Start with Identity
Analysis

8 of 13 identity providers document AWS, Azure and Google Cloud. Only 4 document Workday

SWI's Identity Integration and Compatibility Matrix checked 20 identity platforms against their own documentation: 8 of 13 IdPs document all three clouds, 4 document Workday, 4 document every legacy integration and 2 document Shared Signals in production. Here is what it is and how to use it.

By SWI Community TeamNov 19, 2026

Of 13 workforce identity providers, 8 document federation to AWS, Microsoft Azure and Google Cloud, but only 4 document a Workday connector and only 4 document every legacy integration we checked, according to Start with Identity's new Identity Integration and Compatibility Matrix. It covers 20 platforms and 455 cells, each linked to vendor documentation checked on November 5, 2026. The analysis is in the full report.

Why we built it

"Does this IdP work with our stack?" is the question behind most identity shortlists, and the answer is spread across integration catalogs, setup guides and the target's own docs. AWS publishes IdP setup guides with group-sync caveats that the IdP's marketing page leaves out. Some catalogs list hundreds of apps but do not say which of them include provisioning. Two vendors' documentation could not be read by our tools at all.

So we built one table. The stack picker lets you tick what you run (for example AWS, Workday, Slack and Active Directory) and shows which platforms document all of it, with the source behind every cell. For that example stack, four do: JumpCloud, Microsoft Entra ID, Okta and Ping Identity.

Four findings

Clouds are mostly solved, group sync is not. 8 of 13 IdPs document all three clouds and 11 document SAML plus SCIM into AWS IAM Identity Center. But AWS's own guides say PingOne and Google Workspace cannot provision groups over SCIM and OneLogin cannot delete them, which matters because access in IAM Identity Center is assigned by group.

HR-driven provisioning is the thinnest column. Only 4 of 13 IdPs document a Workday connector that creates, updates and deactivates users, and only Okta documents all five HR systems we checked. All four identity governance platforms document Workday, so the HR connector often lives in the governance tool.

Old protocols decide the shortlist. Only 4 IdPs document all six legacy integrations: authentik, miniOrange, Okta and Ping Identity. Directory sync is nearly universal, but Kerberos or IWA (6 of 13), header-based apps (5) and WS-Fed relying parties (5) are not. AWS IAM Identity Center supports only SAML 2.0 applications.

ITDR and governance tools all read Okta, Entra ID and AD, and split on cloud permissions. All 7 document the big three identity sources. The 4 governance platforms (C1, SailPoint, Saviynt and Veza) document AWS IAM, Azure RBAC and Google Cloud IAM, while none of the 3 ITDR platforms documents all three.

The report also covers the SCIM and Shared Signals gap: inbound SCIM is documented by 8 of 13 IdPs, but only Okta and authentik document a production Shared Signals transmitter.

How it helps

IAM architects. Tick your real targets before the shortlist, not after. The legacy columns (Kerberos, headers, RADIUS, WS-Fed) usually narrow the field faster than SaaS catalog size. The setup recipes for AWS IAM Identity Center, Google Cloud Workforce Identity Federation, SCIM provisioning and AD FS migration are linked from the matching columns.

Security teams evaluating ITDR. The identity-source tab shows which detection tools ingest which IdPs and directories, and which only see posture or a partner connector. Pair it with the ITDR tools rankings.

Procurement and vendor risk. Every "partial" and "not documented" cell is a question for the vendor: ask for a public doc link. The source URLs are evidence you can attach to the assessment.

Analysts. The data is CC BY 4.0. Download the CSV or JSON, cite "Start with Identity, Identity Integration and Compatibility Matrix 2026", and link a figure by its anchor, such as #finding-2. Each platform has its own anchor, for example /tools/integration-matrix/#okta.

Vendors. If a cell is wrong or "not documented" and you have a public page, send it through the contact page. We update from public documentation only and date every change.

What to do now

List the clouds, HR system, SaaS apps and legacy protocols you actually run, put them into the stack picker, and take the gaps to each vendor as named questions: group sync to AWS, who owns the HR connector, which Kerberos, header and WS-Fed apps are covered, and which Shared Signals events are sent and received. Our earlier post on where SCIM provisioning breaks covers what to test once the connectors are live.

Last reviewed By SWI Community TeamSuggest a correctionHow we research
Independent analysis. No vendor sponsorship. Editorial policy · Report a correction