Cross App Access (XAA)
Reviewed 2026-11-10
Cross App Access lets an enterprise identity provider govern an application's delegated connection to another application. Okta's Agent SSO announcement describes short-lived tokens for agents supporting this standard. Connection authorization is not approval for every later action. The resource, requested scope and user context still determine what a token should permit.
How it works
Cross App Access lets an enterprise identity provider govern an application's delegated connection to another application. Okta's Agent SSO announcement describes short-lived tokens for agents supporting this standard. Connection authorization is not approval for every later action. The resource, requested scope and user context still determine what a token should permit.
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's Agent SSO announcement describes short-lived tokens for agents supporting this standard.
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 cross app access (xaa) 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.