An identity provider (IdP) is a service that creates and manages digital identities, authenticates people, and gives applications trusted identity information. It often sits between a directory service and the applications employees use, so those applications do not need to contact the directory directly. The IdP can also enforce policies such as multi-factor authentication and conditional access. section 10.3 section 10.3.1
A typical sign-in works like this:
- The employee authenticates with the IdP, often using multi-factor authentication. section 10.3.2
- The IdP issues a security token containing identity information or claims. An application validates the token rather than asking for another sign-in. section 10.3 section 10.3.2
- The application applies its own authorization rules. A valid token establishes who signed in; it does not, by itself, decide everything that person may do. section 10.3.2
One sign-in, several applications
An employee signs in once, then opens email, a ticketing system, and an internal wiki without reentering credentials. Think of the IdP as a theme park entrance that checks identification and issues a wristband. Each ride checks the wristband, but can still apply its own entry rules. If the wristband is lost, the entrance can invalidate it; similarly, an IdP can revoke a token or end a session. section 10.3.2
An IdP can also support federated identity management: one domain’s identity system vouches for a user to another. For example, an employee in an EU domain can access U.S. resources without creating new credentials. The receiving application validates the signed token and still applies its own access rules. section 10.3.3













