WORKFORCE IDENTITY · US TEAMS OF 100–999
What happens when someone leaves?
Check all three stops. A documented provisioning action does not prove the result in every app.
- 01
Source identity
Which HR or directory record starts the change?
- 02
App account
Does this connector suspend, delete or only remove a group?
- 03
Open session
Check a session that was already signed in.
Start with the employee record
Rippling describes HR-driven provisioning, approvals and offboarding workflows.
IAM product claim; the selected page does not establish the required base bundle or its price. Connector behavior and disable timing need testing. Source
Microsoft documents API-driven provisioning to on-premises AD or Entra ID with P1, P2 or Governance.
Each identity sourced through /bulkUpload needs a license seat. This does not establish a ready-made connector for every HR or legacy app. Source
Then check the exact app
Duo SCIM provisioning is included in Essentials, Advantage and Premier.
Only supported downstream SAML/OIDC applications; provisioning and deprovisioning behavior depends on the target app. Source
Duo says removing a user from a provisioned group can deprovision them in the application.
Duo says these behaviors depend on the target app. Test account state, existing sessions and app-side records separately. Source
Microsoft lists automated SaaS user provisioning in Free, P1 and P2; automated group provisioning is listed in P1 and P2.
This is the saved licensing table, not a tested connector. It does not establish each app’s supported actions, deprovisioning behavior or session revocation. P1 is not required just for the user-provisioning row. Source
Rippling lists LDAP, AD, OIDC, RADIUS, custom SCIM and SAML apps.
Protocol support on the product page does not prove a particular connector or plan includes every action. Source
Ask for the last mile
Use one app from your own stack. Ask who owns failed provisioning jobs, expired connector credentials and exceptions to the offboarding rule.
This is buying guidance; we have not run these workflows or tested session revocation.
Three terms worth separating
- Single sign-on (SSO)
- One identity provider handles sign-in to connected apps.
- Provisioning
- Create or update an account in another system.
- Deprovisioning
- Remove or disable access in that system. The exact action depends on the connector and app.