Comment on page

Microsoft Entra ID (Azure AD) SSO Integration



You can connect your Microsoft Entra ID to Oort to enable SSO to your organization. Enable and control your organization members access to Oort’s platform easily, by following this guide to setting up Oort as an app in your Microsoft Entra ID console.

Types of SSO Integrations Available

Oort supports two methods of SSO integration with Microsoft Entra ID:
  1. 1.
    OIDC - this method provides a fast and simple App Registration flow for SSO to your Oort tenant. It is useful for preview or test Oort tenants ("Staging" environment) or in scenarios where full RBAC group management and access to the Oort tenant is not required.
  2. 2.
    SAML - a SAML integration with Oort for sign-on provides the ability to enable RBAC groups for full admin, help desk, and read-only roles.
This article provides instructions for both methods. In many cases, an Oort tenant may start with OIDC-based SSO and migrate to SAML SSO to enable RBAC functionality, as mentioned above.


To add the necessary configuration in Microsoft Entra ID you need:


Set up and configure Oort App Registration in Microsoft Entra ID

You will need to create the app registration in your Entra ID tenant, assign the correct permissions, and add an API secret.

Add an app in your Microsoft Entra ID tenant

  1. 1.
    Go to Microsoft Entra ID → App registrations
  1. 2.
    Click on New registration
  1. 3.
    Fill in the details for the new app
  • Enter an app Name
  • In “Who can use this application or access this API?” Select: Accounts in this organizational directory only (<tenant name> – Single tenant)
  • In “Redirect URI”:
  1. 3.
    Click on Register
  1. 5.
    Copy and save the Application ID. You will later send it to Oort’s support team.
Add API Permissions
  1. 1.
    Go to API Permissions under your newly created Oort Integration app
  2. 2.
    Click on Add a permission
  3. 3.
    Click on Microsoft Graph
  1. 4.
    Click on Application Permissions
  2. 5.
    Search for “Directory.Read.All”
  3. 6.
    Check the box next to Directory.Read.All
  1. 7.
    Search for “User.Read.All”
  2. 8.
    Check the box next to “User.Read.All”
  1. 9.
    Once added to the list, click Add Permissions
  2. 10.
    Click on Grant admin consent for <tenant name>
  1. 11.
    Click Yes to accept admin consent.
Create API secret
  1. 1.
    Go to Certificates & Secrets under your Oort Integration app
  2. 2.
    Click on New client secret
  3. 3.
    Fill in the details for the secret and click Add
  1. 4.
    Save the Secret Value
  • Click the copy icon to copy and save it somewhere
  • Important: Once you leave this page you WILL NOT be able to get the key again and will have to delete and create a new one.

Provide Client ID and Client Secret to Oort Success & Support Team

As part of this process, Oort Customer Success or Support team will guide you in securely transmitting the App Registration data below so that the configurations can be finished on the Oort authentication platform.
  • Client ID
  • API Secret
  • Azure tenant external FQDN or primary domain (e.g. or

Make the Azure App Visible to End Users

Oort strongly recommends you make the Azure SSO app visible to your Oort users, so that they have quick access to the Oort console from their Azure My Apps page.
  1. 1.
    Navigate Enterprise Applications
  1. 2.
    Find Oort's SSO app in the list and click it.
  2. 3.
    In the app’s page, click Properties in the Menu
  3. 4.
    Select Yes for Assignment required and for Visible to users
  4. 5.
    Click Save


This method uses SAML, which enables the provider (Microsoft Entra ID) to pass group information that will be used in the Role-based Access (RBAC) and Reviewing Access Logs configuration for your tenant.

Create a New SAML SSO App

  1. 1.
    Within Microsoft Entra ID Enterprise Apps blade, click Create your own application and provide a name as shown. Then click Create and the bottom of the slide-out.
  2. 2.
    From this page, click Set up single sign on
  3. 3.
    Click SAML
  4. 4.
    Click the Edit button for the Basic SAML Configuration section
  5. 5.
    At this point, the values entered will differ whether your tenant is in Oort Staging or Production environments. Please discuss with your Oort representative to ensure the right configuration. Production Identifier (Entity ID): urn:auth0:oort:<companyname>-saml Production Reply URL: Staging Identifier (Entity ID): urn:auth0:oort-staging:<companyname>-saml Production Reply URL:
  6. 6.
    Save the config.
  7. 7.
    Click Edit for section 2 - Attributes & Claims
  8. 8.
    Click Add new claim
  9. 9.
    Configure the claim as shown below: Name: groups Namespace: In the Claim conditions section, add a row for each RBAC of the three groups that you've created for Oort roles in your Microsoft Entra ID tenant. If you haven't created them yet, do that now and populate them with the appropriate users. User type: Any Scoped group: Select one for each row Source: Transformation Values: Transformation: IfNotEmpty() Attribute name (Input): user.userprincipalname Attribute name (Output): <name of group specified for this condition, case sensitive>
  10. 10.
    Click enter and then save this configuration after adding a row for all three groups.
  11. 11.
    In section 3, Download the Base64 Certificate
  12. 12.
    In section 4, copy the Login URL value.
  13. 13.
    Provide both the downloaded certificate and the URL to your Oort representative.

Appendix: Enable Microsoft Entra ID resource provider

Enable AzureAD resource provider under your license.
  1. 1.
    Go to Home → Subscriptions
  1. 2.
    Click your subscription (the relevant subscription)
  1. 3.
    Click Resource Providers in the menu
  2. 4.
    Search for Microsoft.AzureActiveDirectory and select it.
  3. 5.
    If the Status says NotRegistered
  4. 6.
    Click on the Register button to register the Microsoft AzureAD resource provider.