--- title: "Configure OpenID Connect with Azure Active Directory/Microsoft Entra ID" slug: "azure-ad-microsoft-entra" updated: 2026-07-24T16:26:09Z published: 2026-07-24T16:26:09Z canonical: "docs.discngine.com/azure-ad-microsoft-entra" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.discngine.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure OpenID Connect with Azure Active Directory/Microsoft Entra ID ## Overview This guide will walk you through configuring OpenID Connect authentication with Azure Active Directory (Microsoft Entra ID) for Discngine Admin Center. Once completed, users will be able to log in using their Azure AD credentials. > **Note:** Azure AD is now called Microsoft Entra ID, but both names refer to the same service. ## Prerequisites Before configuring Azure AD OpenID Connect, ensure you have: - Organisation Administrator access to Discngine Admin Center - Administrator access to the [Azure Portal](https://azure.microsoft.com/en-us/features/azure-portal/) - Permissions to create and configure Azure AD applications ## Register a New Azure Active Directory Application ### Step 1: Access Azure Portal Log in to the [Azure Portal](https://azure.microsoft.com/en-us/features/azure-portal/) and navigate to **Azure Active Directory** → **App Registrations** → **New Registration**. ![Register a new Azure AD Application](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/azure-register-application.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=dS3A8MH8AnUOIG1%2Bmg7TLuxt9bPmSVoUqnyNJ%2FWsguM%3D) ### Step 2: Configure Application 1. Provide a name for your application (e.g., "Discngine Admin Center") 2. Select the appropriate supported account types 3. Set the **Redirect URI** to: `https://account.discngine.cloud/oauth2/callback` 4. Click **Register** ### Step 3: Note Application Details Once the application is created, record the following values (you'll need them later): - **Application (client) ID** - This will be your Client ID - **Directory (tenant) ID** - This will be used to construct your Issuer URL ![Azure AD Client ID and Tenant ID](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/azure-client-tenant-id.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=nG7muM8g3A73LiOZsDCicCbwrwJx8CxvPsfs51%2F14d4%3D) ## Create a Client Secret ### Step 1: Generate Secret Navigate to **Azure Active Directory** → **App Registrations** → **Your Application** → **Certificates & secrets** → **New client secret**. ![Azure AD Client Secret](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/azure-client-secret.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=UIjeX877ylfyhWjrYMz5kfc1G62hGjHlWZ%2BByurG3MQ%3D) ### Step 2: Save Secret Value 1. Add a description for the secret (e.g., "Discngine Admin Center Secret") 2. Choose an expiration period 3. Click **Add** 4. **Important:** Copy the secret **VALUE** immediately - you won't be able to see it again ## Configure OpenID Connect in Discngine Admin Center ### Step 1: Access Identity Providers 1. Log in to Discngine Admin Center as an Organisation Administrator. 2. Navigate to **Identity Providers** in the left sidebar or via the **Identity Providers** card on the home page. 3. Click **New Provider** and set **Provider Type** to **OpenID Connect with Issuer URL**. ![Create a new OpenID integration](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/new_idp_provider.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=w5HGwX4KmbW%2BUtg89hIRI9NNByNElB8BGS7MwWwEGy8%3D) ### Step 2: Configure Provider Settings The OpenID Connect form is simplified — you only need the following fields: - **Name:** `Azure AD` or `Microsoft Entra ID` - **Issuer URL:** the OIDC issuer from Azure (endpoint discovery happens automatically from this URL). Use one of the following formats, replacing `{tenantId}` with your Directory (tenant) ID: - Azure AD v1: `https://login.microsoftonline.com/{tenantId}` - Azure AD v2: `https://login.microsoftonline.com/{tenantId}/v2.0` - **Client ID:** the Application (client) ID from Azure - **Client Secret:** the client secret VALUE you copied earlier Click **Save**. ### Step 3: Enable for Applications By default, the new provider is not enabled for any application. 1. Open the provider from the Identity Providers page and switch to the **Application Registration** tab. 2. Your applications are listed grouped by environment. Turn the **Enabled** toggle on for each application that should use this provider. 3. Click **Save**. For more details on assigning providers to applications, see [How to Manage Identity Providers](/public/docs/how-to-manage-identity-providers). ## Testing the Configuration ### Step 1: Access Login Page Navigate to `https://admin-<organisation-name>.discngine.cloud/` ### Step 2: Test Login 1. Enter your email address 2. You should see the **Login with Azure AD** button 3. Click the button 4. You will be redirected to the Azure AD login page 5. Enter your Azure AD credentials 6. After successful authentication, you'll be redirected back to Discngine Admin Center ![Login with Azure AD](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/azure-login-button.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A18Z&se=2026-11-16T06%3A43%3A18Z&sr=b&sp=r&sig=giMyo5VuB4FxHCa6b%2Fi%2FB%2By179wS3ORADvAZtddNEFU%3D) ## Troubleshooting ### Common Issues **Redirect URI Mismatch** - Ensure the redirect URI in Azure AD exactly matches: `https://account.discngine.cloud/oauth2/callback` **Invalid Client Secret** - Client secrets expire - check if yours has expired and generate a new one if needed **Tenant ID Issues** - Verify you're using the correct tenant ID from the Azure AD directory - Check that you're using the correct Azure cloud URL (global, government, etc.) **User Email Not Available** - Ensure the `email` scope is included - Verify that users have email addresses in their Azure AD profiles ## Additional Resources - [Microsoft Entra ID - Register An App Quickstart Guide](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) - [Azure AD Documentation](https://learn.microsoft.com/en-us/azure/active-directory/) ## Next Steps - [← Back to How to Manage Identity Providers](/public/docs/how-to-manage-identity-providers)