Skip to content

Entra OIDC Authentication

Client SDK
Backend API
Mobile approve
SSO
Sub-journey

Authenticates the user with Microsoft Entra ID using OIDC redirect

Description

This step authenticates the user by redirecting them to Microsoft Entra ID–an external identity provider–for authentication using the OIDC Authorization Code flow. It is used for Just-In-Time (JIT) migration scenarios where users are gradually migrated from Entra ID to Mosaic as they log in.

Before using this step, configure an Entra ID connection in Integration Hub.

When the journey reaches this step, the user is redirected to Entra ID to authenticate. After successful authentication, Entra ID redirects the user back to Mosaic using the configured callback URL. The authentication result is stored in the output variable and can be used in subsequent steps (e.g., to create a user in Mosaic).

If the authentication fails, the journey proceeds to the failure branch (if specified); otherwise, the journey is aborted and an error is sent to the client.

Configuration

FieldDescription
Azure AD integrationThe Entra ID connector to use for authentication, as configured in Integration Hub.
Callback URLThe URL where Entra ID redirects the user after authentication.
ScopeOAuth scopes to request from Entra ID. Default: openid profile email.
Response modeDetermines if the authorization response is returned in a query or a form post.
Advanced OIDC configurationAllows configuring ACR values, claims, and additional authorize parameters.
Output variableName of the variable that stores the authentication result returned by Entra ID.
Error output variableName of the variable that stores any errors returned by the step.
Failure behaviorDetermines the behavior in case of failure, which either aborts the journey or proceeds to a failure branch of the control flow (default).
Journey event data

This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see Additional data reporting.

Example

Consider a migration journey where users authenticate via Entra ID's login page. The Entra OIDC Authentication step redirects the user to Entra ID. After successful authentication, the output variable (azuread_oidc_output) contains user information, including ID token and user_info, that can be used to create or update a user in Mosaic using the Create user step.