The Microsoft Azure® identity bridge uses OpenID Connect and OAuth to connect to your Azure provider (OP) to authenticate your users and access user information. In OpenID terms, PingOne is the Relying Party (RP) that sends authentication and information requests to the Azure provider.
To configure the identity bridge, you'll be working on both the Azure and PingOne sides and copying information from your Azure tenant to the PingOne identity bridge setup.
OpenID Connect supports a discovery mechanism whereby an OpenID Connect host
publishes metadata using a well-known URL, by convention of the form:
https://host.com/.well-known/openid-configuration. The URL
returns OpenID Connect and OAuth endpoints, supported scopes and claims, public keys
used to sign tokens, and other metadata. We use this metadata to complete your
authentication requests and requests for user information.
- Go to Connect to an Identity Repository, and select Microsoft Azure AD. Click Next. , click
Sign on to your Azure tenant and go to
The application overview page is displayed.
- On the Register an application page, enter a name for the PingOne client (such as, "PingOne").
- Under Supported Account Types, click to select which Microsoft account types you will allow access.
- Optional: Under Redirect URI, select an authentication method from the list, and in the text field enter a URL.
- Click Register to save the PingOne client.
- Copy the Application (client) ID value.
- On the Configure Your Microsoft Azure Connection tab, paste the Application (client) ID value into the Client ID field.
Click Add a certificate or secret and click New
Enter a description and expiration for the client secret.
You’ll need to update the client secret when it expires.
- Click Add to add the new client secret.
- Copy the Value value.
- Enter a description and expiration for the client secret.
- Paste the Client ID value into the Client Secret field.
Return to the overview page.
- Click Endpoints to display the OAuth endpoints for your Azure tenant.
- Copy the URL for the OpenID Connect metadata document endpoint.
- While still on the Configure Your Microsoft Azure Connection panel, for Discovery Endpoint, enter the URL for the OpenID Connect metadata document endpoint you copied from your Azure tenant.
PingOne will verify that it can query the endpoint or endpoints you've specified. If verification isn't successful, check that the endpoint or endpoints appear exactly as they do on your OpenID Connect provider.
For Scope, select the OAuth scopes that you'd like us to
include in authentication requests, then click
The available scopes of authorization for your Azure tenant are displayed based on the response from your supplied Discovery Endpoint. The scopes indicate the access privileges you're requesting for the access token returned by Azure. We use the access token to request additional claims from the userinfo endpoint.
Close the Endpoints panel and from the clientName IdP (Test) page, click
API permissions for your PingOne client.
Check whether User.Read is already added by
If it isn't already added, you'll add it in a subsequent step.
- Click Add a permission.
- The Request API permissions page is displayed. Select .
- For What type of permissions does your application require?, select Application permissions.
- The list of APIs is displayed. Expand Group and select Group.Read.All.
- If the User.Read permission wasn't added by default, expand User and select User.Read.
- On the API permissions page, click Add permissions.
Click Grant admin consent for....
Doing this ensures your users don't need to grant consent during SSO.
- Check whether User.Read is already added by default.
- On the clientName IdP (Test) page, click Manifest.
Find the groupMembershipClaims element and change it
from "null" to either "SecurityGroup" or
This will ensure that the group membership claim is sent in the access token to during SSO.
On the Microsoft Azure Provider panel, copy the displayed PingOne
The PingOne Redirect URI is the URI assigned by PingOne to which your Azure tenant sends OAuth authorization codes indicating whether or not a user was authenticated.To ensure security, the PingOne redirect URI includes a verification code unique to your account. The redirect URI used by your Azure tenant for the PingOne client must include the verification code for SSO to be successful.
Go to the Overview page for your registered PingOne client and click the link
for Redirect URIs.
- Add a new Redirect URI of type Web.
- Enter the URI you copied from the Microsoft Azure Provider panel in PingOne.
- Click Save.
Assign the Azure provider-to-PingOne attribute mapping.
This assignment maps your selected Azure provider attributes to the default PingOne attributes (used by PingOne dock). This attribute mapping is not used by applications that you add to PingOne. You will configure those identity provider-to-service provider attribute mappings for each application.Note:
If you're also using PingID for Azure Conditional Access, make sure the
MFA_SUBJECTmapping for PingOne for Enterprise matches the
usernamemapping for PingID.
For more information, see Configuring PingID MFA for Microsoft Azure AD Conditional Access in the PingID documentation.
- For any of the attribute mappings, you can choose to configure an advanced mapping. See Creating advanced attribute mappings for instructions.
- Click Next when you're finished.
Choose whether or not to synchronize the user groups on your Azure provider
with your PingOne user groups.
Group synchronization relies on the Microsoft Graph API permissions you specified for the PingOne client you registered in Azure. The permissions User.Read and Group.Read.All are required for synchronization to be successful.Any PingOne user groups that do not exist in your Azure provider will be replaced by the Azure groups.Each of your Azure group members are automatically added to the corresponding PingOne groups when the user initially signs on (SSO) to PingOne. This is PingOne's just-in-time user provisioning.
When you elect to synchronize your Azure groups with PingOne, a banner
is displayed notifying you that synchronization is under way. In the
banner is a User Groups link. Clicking this link
will take you to the User Groups page where you can see the groups being
added to PingOne.
The Azure groups are added using their Azure group IDs. After this initial synchronization, when additions or changes to your Azure groups occur, you'll need to choose to resynchronize the groups using the Synchronize Groups button on the User Groups page. See Add groups for more information.
- Click Done.
- When you elect to synchronize your Azure groups with PingOne, a banner is displayed notifying you that synchronization is under way. In the banner is a User Groups link. Clicking this link will take you to the User Groups page where you can see the groups being added to PingOne.