HR-driven provisioning
Reviewed 2026-11-10
Using the HR system as the source of truth, so that hiring, role changes and departures create, change and disable accounts automatically. Okta and Entra ID each list the HR systems they support. Keep identity, access policy and resource permission separate. Check the source before choosing a control for your applications.
How it works
Using the HR system as the source of truth, so that hiring, role changes and departures create, change and disable accounts automatically. Okta and Entra ID each list the HR systems they support.
Identify the actor, the resource and the decision this term describes. Record which system makes that decision and which system enforces it.
A sign-in event, a policy decision and an application permission are not interchangeable. Test the relevant boundary rather than relying on a product label.
What Okta and Entra ID call it
Okta and Entra ID each list the HR systems they support.
Use the linked comparison to locate the relevant product scope. Do not infer a vendor capability from a similar name alone.
Example
Consider an application access review as an illustrative exercise, not a customer story. Identify the person or service involved, the resource requested and the evidence needed.
Locate where hr-driven provisioning affects that decision. Ask what would change if the identity, device or permission changed.
Write down the expected result before testing. Keep the observation separate from a vendor's description of the feature.