Custom claims provider (preview)
This article provides an overview to the Azure Active Directory (Azure AD) custom claims provider. When a user authenticates to an application, a custom claims provider can be used to add claims into the token. A custom claims provider is made up of a custom extension that calls an external REST API, to fetch claims from external systems. A custom claims provider can be assigned to one or many applications in your directory.
Key data about a user is often stored in systems external to Azure AD. For example, secondary email, billing tier, or sensitive information. Some applications may rely on these attributes for the application to function as designed. For example, the application may block access to certain features based on a claim in the token.
The following short video provides an excellent overview of the Azure AD custom extensions and custom claims providers:
Use a custom claims provider for the following scenarios:
- Migration of legacy systems - You may have legacy identity systems such as Active Directory Federation Services (AD FS) or data stores (such as LDAP directory) that hold information about users. You'd like to migrate these applications, but can't fully migrate the identity data into Azure AD. Your apps may depend on certain information on the token, and can't be rearchitected.
- Integration with other data stores that can't be synced to the directory - You may have third-party systems, or your own systems that store user data. Ideally this information could be consolidated, either through synchronization or direct migration, in the Azure AD directory. However, that isn't always feasible. The restriction may be because of data residency, regulations, or other requirements.
Token issuance start event listener
An event listener is a procedure that waits for an event to occur. The custom extension uses the token issuance start event listener. The event is triggered when a token is about to be issued to your application. When the event is triggered the custom extension REST API is called to fetch attributes from external systems.
For an example using a custom claims provider with the token issuance start event listener, check out the get started with custom claims providers article.
- Learn how to create and register a custom claims provider with a sample Open ID Connect application.
- If you already have a custom claims provider registered, you can configure a SAML application to receive tokens with claims sourced from an external store.
- Learn more about custom claims providers with the custom claims provider reference article.
Submit and view feedback for