Identity Provider (IdP): Definition and Function

Access & IdentitiesAlso known as: IdP, Identity Provider, Identity Service, Identity-Provider
In brief

An Identity Provider (IdP) is a system that verifies a person's identity at login and passes the result as a signed confirmation to other applications. The applications trust the IdP via standards such as SAML 2.0 or OpenID Connect and do not need to store their own passwords; examples include Microsoft Entra ID, Google Workspace, and Okta.

Key Takeaways

  • An IdP authenticates people and issues a signed assertion or token to connected applications.
  • Common protocols between an IdP and an application are SAML 2.0 and OpenID Connect.
  • The IdP is the technical foundation for Single Sign-On.
  • Which permissions a person has inside the application is usually governed by the application itself.

How does an Identity Provider work?

An Identity Provider handles login on behalf of connected applications. The flow:

  • The person opens an application, which redirects them to the IdP.
  • The IdP verifies the password, second factor, or passkey.
  • The IdP sends a signed confirmation, such as a SAML assertion or an ID token.
  • The application trusts the confirmation and opens the session.

What Identity Providers exist?

Identity Providers exist both as part of office suites and as standalone services.

  • Included in office suites: Microsoft Entra ID for Microsoft 365, Google Workspace.
  • Standalone cloud services: such as Okta, JumpCloud, or Auth0.
  • Self-hosted solutions: such as Keycloak or Active Directory Federation Services.

Why is an Identity Provider important for small and medium-sized businesses?

An Identity Provider centralizes logins and security policies in one place. Multi-factor authentication only needs to be set up once, and upon departure, disabling the account in the IdP ends access to all applications connected via Single Sign-On. Most small and medium-sized businesses already have an IdP with Microsoft 365 or Google Workspace, but do not use it for all applications.

Example: Identity Provider (IdP) in practice

Real-world example

Example: A tax consultancy with 35 employees uses Microsoft 365 and thus Microsoft Entra ID as its Identity Provider. 8 cloud applications are connected via SAML or OpenID Connect. Employees log in once in the morning with a password and authenticator app. For 4 additional applications that do not support SSO on the subscribed tier, separate accounts remain in place.

Identity Provider (IdP) vs. Single Sign-On (SSO)

AspectIdentity Provider (IdP)Single Sign-On (SSO)
NatureSystem or serviceMethod or login experience
TaskVerify identity and issue confirmationUse multiple applications with a single login
DependencyCan also be used without SSORequires an IdP as its foundation
ExampleMicrosoft Entra ID, Google WorkspaceLogging in to the CRM via the Microsoft account

The Identity Provider is the system that verifies identities, whereas Single Sign-On is the method that uses this verification across multiple applications.

How does Sovaro help with Identity Provider (IdP)?

How Sovaro helps

Sovaro is not an Identity Provider and not an SSO service. Sovaro connects to Google Workspace or Microsoft Entra so that a new hire or departure there triggers an onboarding or offboarding workflow. Sovaro detects apps via its agent and browser extension, even without SSO, and assigns them to the person.

Frequently Asked Questions about Identity Provider (IdP)

Sources

See Sovaro with your own data.

Connect Google Workspace or Microsoft Entra, share the setup link, and see devices, apps, and licenses per person in one place.

14-day free trial, no payment details required. Cancel monthly.