WS-Federation
Reviewed 2026-11-10
An older Microsoft-originated federation protocol. Okta's Microsoft 365 integration can use it to federate Microsoft 365 sign-in. Keep identity, access policy and resource permission separate. Check the source before choosing a control for your applications. Confirm the scope before implementation.
How it works
An older Microsoft-originated federation protocol. Okta's Microsoft 365 integration can use it to federate Microsoft 365 sign-in.
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
An older Microsoft-originated federation protocol. Okta's Microsoft 365 integration can use it to federate Microsoft 365 sign-in.
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 ws-federation 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.