Azure EAM - MPAS integration

This documentation has been tested and approved by Kelvin Zero's team

This document will outline the steps required to enable MPAS as an external authentication method in Microsoft Entra ID.

To set up Multi-Pass, ensure you meet the following requirements
- An Active MPAS subscription with admin
rights to a realm
- Global Admin or Application administrator
role on Azure
- metadata to configure an EAM
- Privileged Role Administrator on Azure
- Users must exist and be synced in both MPAS
and Azure using either SCIM or OIDC Force Sync
- Entra P1 or P2 License
Important: Custom elements in URLs (like realm names) are case sensitive. Make sure to match the exact casing from your environment.
Create
MPAS EAM for Entra
Edit Authentication Method AMR claim in MPAS
- First, log in to your dashboard by following this link: https://dashboard.kzero.com/
- Select the appropriate deployment and click on "Admin Console."
- On the left-hand side of your screen, click on "Authentication," then select "MPAS - Passwordless Selector."
Ensure that the Digital and Card steps include an AMR claim.

Create
EAM App Registration
- From the Azure portal, search for App Registrations
- Click on New Registration
- Enter a name for your registration
- For the Redirect URI:
- Open the dropdown menu labeled "Select a platform" and choose Web.
- Enter the following Redirect URI: https://ca.auth.kzero.com/realms/<realmname>/protocol/openid-connect/auth
- Click Register to complete the process

From the App Registration Overview page, take note of the Client ID of the newly created App Registration. You will need this for the next step.
Create EAM and Client
Create an EAM in the Entra Admin Center
- Sign in to https://entra.microsoft.com/.
- Navigate to Protection > Authentication methods.
- Click on Add external method (Preview)

You will need to provide the following information, which will be obtained from MPAS
Create a client on MPAS
- Sign in to your realm's admin console on MPAS at: https://ca.auth.kzero.com/admin/<realm>/console.
- Click on Clients in the navigation menu.
- Click on Create client
- Assign a unique Client ID and Name to your client.
- Click Next to proceed.
- Keep Client Authentication disabled.
- Enable Implicit Flow.
- Disable Standard Flow
- Click Save on the next screen to confirm your settings.
- On the Client Details page of the client you just created, click on Client Scopes.
- Select the dedicated assigned client scope.
- From this page, you will need to create the following Mappers.

Ensure that all claims are included in the JWT token by selecting Add to ID Token and Add to Access Token
To configure the AMR claim, follow these steps:
- Click on Add Mapper
- Select By Configuration > Authentication Method Reference (AMR)
- Apply the following settings
To configure the tid claim, follow these steps:
- Click on Add Mapper
- Select By Configuration > Hardcoded Claim
- Set the Claim Name to tid
- Enter your Tenant ID from your Azure tenancy as the Claim Value
To configure the AUD claim, follow these steps:
- Click on Add Mapper
- Select By Configuration > Audience
- Add the Client ID (App ID) from the Azure App Registration created earlier
To configure the ACR claim, follow these steps:
- Click on Add Mapper
- Select By Configuration > Authentication Context Class Reference (ACR)
- Add possessionorinherence as the claim value
Configuring the Azure External Authentication Method
- Return to the Azure External Authentication Method browser session
- Add the Client ID you just created:
- Enter the Client ID from MPAS into the Client ID field.
- Add the MPAS OIDC Discovery Endpoint:
- This URL can be copied from the Realm Settings page in MPAS.
- It will always follow this format: https://ca.auth.kzero.com/realms/<REALMNAME>/.well-known/openid-configuration
- Add the App ID:
- Enter the Application ID from the Azure App Registration, which enables Entra to act as an Identity Provider for MPAS.
- Once the App ID is added, Azure will inspect the value and determine if admin consent is required.
- If prompted, click on Request Permission to complete the process.
Related Articles
Blumira - SSO Configuration
This documentation has been tested and approved by Kelvin Zero's team This documentation provides a step-by-step guide to setting up Single Sign-On (SSO) for Blumira using MPAS. SSO simplifies user authentication by allowing access to multiple ...
Huntress - SSO configuration
This documentation has been tested and approved by Kelvin Zero's team This documentation provides a step-by-step guide to setting up Single Sign-On (SSO) for Huntress using MPAS. SSO simplifies user authentication by allowing access to multiple ...
FortiAuthenticator - SSO configuration
This documentation has been tested and approved by Kelvin Zero's team This documentation provides a step-by-step guide to setting up Single Sign-On (SSO) for FortiAuthenticator using MPAS. SSO simplifies user authentication by allowing access to ...
Google Workspace - SSO Configuration
This documentation has been tested and approved by Kelvin Zero's team This documentation provides a step-by-step guide to setting up Single Sign-On (SSO) for Google Workspace and its suite using MPAS. SSO simplifies user authentication by allowing ...
BambooHR - SSO Configuration
This documentation has been tested and approved by Kelvin Zero's team This documentation provides a step-by-step guide to setting up Single Sign-On (SSO) for Bamboo HR using MPAS. SSO simplifies user authentication by allowing access to multiple ...