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
- 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 and navigate to Azure Active Directory → App Registrations → New Registration.

Step 2: Configure Application
- Provide a name for your application (e.g., "Discngine Admin Center")
- Select the appropriate supported account types
- Set the Redirect URI to:
https://account.discngine.cloud/oauth2/callback - 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

Create a Client Secret
Step 1: Generate Secret
Navigate to Azure Active Directory → App Registrations → Your Application → Certificates & secrets → New client secret.

Step 2: Save Secret Value
- Add a description for the secret (e.g., "Discngine Admin Center Secret")
- Choose an expiration period
- Click Add
- 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
- Log in to Discngine Admin Center as an Organisation Administrator.
- Navigate to Identity Providers in the left sidebar or via the Identity Providers card on the home page.
- Click New Provider and set Provider Type to OpenID Connect with Issuer URL.

Step 2: Configure Provider Settings
The OpenID Connect form is simplified — you only need the following fields:
- Name:
Azure ADorMicrosoft 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
- Azure AD v1:
- 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.
- Open the provider from the Identity Providers page and switch to the Application Registration tab.
- Your applications are listed grouped by environment. Turn the Enabled toggle on for each application that should use this provider.
- Click Save.
For more details on assigning providers to applications, see 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
- Enter your email address
- You should see the Login with Azure AD button
- Click the button
- You will be redirected to the Azure AD login page
- Enter your Azure AD credentials
- After successful authentication, you'll be redirected back to Discngine Admin Center

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
emailscope is included - Verify that users have email addresses in their Azure AD profiles