SSO with Microsoft Entra ID
Microsoft Entra ID (formerly Azure Active Directory) supports OpenID Connect (OIDC) for secure single sign-in. OX supports OIDC SSO with Entra ID so your users can sign in to OX with their company credentials. This section matches the structure and tone of your Okta SSO page for consistency.
Prerequisites
Entra admin permissions to register applications and manage Enterprise applications.
OX Owner or Admin permissions.
Step 1: Register the application [Entra]
Create an application registration in Entra ID that represents OX. This app sets the redirect URI and provides the Application (client) ID you will use in OX.
To register the application:
In the Entra admin center, go to Applications > App registrations > New registration, and set the following parameters:
Name:
Set the app name, for example, OX Security SSO.
Supported account types:
Accounts in this organizational directory only (Single tenant).
Redirect URI:
Platform: Web | URL: https://auth.app.ox.security/login/callback
Select Register.
Step 2: Create a client secret [Entra]
Open the app Certificates & secrets page.
Select New client secret.
Enter a description and select an expiry period.
Select Add.

Copy and save the Value now. You will not see it again.
Step 3: Configure SSO in OX [OX]
In the OX platform, go to Settings > Login Settings and select Microsoft Entra ID. Take the values from the Configuration screen.

Fill the fields using as follows:
Entra domain or Tenant (Directory) ID
Enter your tenant primary domain (for example, contoso.onmicrosoft.com) or the Directory (tenant) ID GUID.
Application (client) ID
Paste the Application (client) ID from the Entra app registration Overview.
Client Secret (Value)
Paste the client secret value you created in Entra.
Enable auto provisioning
Enable this if you want users to sign in without inviting them in the OX Members page and to control roles and scopes using Entra ID groups. Note: If you do not configure auto-provisioning with roles, users who are not invited sign in as Read Only. If you do configure roles, manage role assignments only in Entra ID. OX role changes are ignored for Entra SSO users.
Sync OX Group Roles
When enabled, OX assigns a role (Admin, Developer, Policy Manager, Read Only) based on the user’s Entra ID group membership. Manage memberships in Entra ID.
Sync OX Group Scopes
When enabled, OX grants data visibility based on Entra ID group names that represent application owner scopes or tag scopes. Manage memberships in Entra ID.
Select Save.
Step 4: Assign users to the Enterprise application [Entra]
In the Entra admin center, go to Enterprise applications and open your app.
Go to Users and groups.
Select Add user/group and assign the people and groups who can sign in to OX.
Select Assign.
Step 5: Enable app-initiated login and catalog visibility [Entra]
In App registrations > your app > Branding & properties, set the following parameters:
Home page URL
https://app.ox.security/sso-login?organization=<ORG_ID>&organization_name=<ORG_SLUG>&display_name=<DISPLAY_NAME>&connection=waad-<ORG_SLUG>
In Enterprise applications > your app > Properties, set the following parameters:
Enabled for users to sign-in?
Yes
Assignment required?
Yes
Visible to users?
Yes
Select Save.
Step 6: Map Entra ID groups to OX roles [Entra and OX]
This step enables the automatic assignment of OX Security roles based on user groups in your IdP. There are the following types of roles:
Roles predefined by OX,
Custom roles.
Create user groups for predefined roles
Each predefined role group requires a prefix. The default is: OXApp-. You can change the default prefix to a custom one.
To change the default prefix:
Go to Settings > Login > [IdP icon] and enter a different prefix.

Create IdP role groups: In your IdP, go to Directory > Groups and create groups using these exact names (case-sensitive) for each OX role you want to sync:
OXApp-Admin
OXApp-Developer
OXApp-Dev Manager/Security Champion
OXApp-Policy Manager
OXApp-Read Only
Create user groups for custom roles
In case you have custom role(s) defined in OX, you need to create groups using the exact labels OX generates for your custom roles. The label is different from the custom role name.
You can view the custom role label only in the instructions provided by OX within the Configuration dialog.
To locate the custom role label:
Go to Settings > Login > [IdP icon] and in the instruction box, select +.
Scroll down in the instructions box until you get to Advanced settings (auto provisioning) - Setting roles.
Read the procedure. The custom role label appears next to the custom role name in brackets. You cannot change it.
Use this label as the name of your new group in IdP.
For example:
I know that the admin defined a custom role called Executive Viewer. If I am looking for the label that OX generated for the custom role Executive Viewer, first I locate the custom role Executive Viewer in brackets and then I can see that OX generated a label for this custom role "OXApp-CustomRole1".

Complete the process
Map group attributes: In your IdP, ensure you have groups attribute mapping enabled.
Enable sync: In OX, go to Settings > Login > [IdP icon] and enable Sync OX Group Roles using the prefix you selected.
Select Save.
In the IdP, assign users who need that specific scope access as members of the corresponding group.
Step 7: Map Entra ID groups to OX scopes [Entra and OX]
In Groups, create scope groups using these formats. Use values from View details in the OX Application scope dropdown.
App Owner scope
OXAppOwnerScope-<SCOPE_NAME>-id:<APP_OWNER_ID>Example:OXAppOwnerScope-DevOps-id:[email protected]Tag scope
OXTagScope-<TAG_NAME>-id:<TAG_ID>Example:OXTagScope-app-id:acme-appAdd members to each scope group.
Ensure group claims include these groups for OX.
In the OX platform, enable Sync OX Group Scopes in Settings > Login Settings.
Step 8: Test the sign-in [OX]
In the OX platform, go to
https://app.ox.security/or your environment URL.Select Sign in with Microsoft and sign in with an assigned user.
If you configured the Home page URL in Step 5, open that link to start the flow.
Troubleshooting
Reply URL mismatch
Entra
The Redirect URI must exactly match https://auth.app.ox.security/login/callback.
Invalid client secret
Entra and OX
Paste the secret Value in OX and verify it is not expired.
User not authorized to use the app
Entra
Enterprise applications → your app → Users and groups. Ensure the user or their group is assigned.
Roles or scopes do not match after sign-in
Entra and OX
Verify the user’s Entra group membership, ensure group claims are in the ID token, and confirm Sync OX Group Roles or Sync OX Group Scopes is on in OX.
Last updated
