Use Microsoft Entra ID (formerly Azure AD) as your identity provider so users sign in to Dispel with their Microsoft credentials over OAuth (OIDC) or SAML.
Connect Microsoft Entra ID — Microsoft's cloud identity platform, formerly known as Azure AD — as your organization's identity provider. Once connected, your users sign in to Dispel with their Microsoft credentials through single sign-on. You can connect Entra over OAuth (OIDC) or SAML.
This page covers the Entra-specific setup. For the shared behavior that applies to every provider — how users sign in, group mapping, MFA, and disconnecting — see Identity Providers.
You'll configure the IdP side in the Microsoft Entra admin center (or Azure portal), so you'll need administrative access there.
Decide on a protocol — OAuth (OIDC) or SAML. See Choosing a protocol.
Make sure the users who will sign in via Entra are already invited to your organization in Dispel. SSO authenticates users but doesn't create access on its own.
In the Microsoft Entra admin center, go to App registrations → New registration and create an app for Dispel.
Add a the following 2 Web redirect URIs for your Dispel environment
/oauth/login-callback — (e.g.https://app.dispel.com/oauth/login-callback).
Click Connect on the Microsoft Entra ID card and Select Authentication Protocol → OAuth.
Fill in the fields:
Click Save settings.
In the Microsoft Entra admin center, go to Enterprise applications → New application → Create your own application, then open Single sign-on → SAML.
In Basic SAML Configuration, paste the values Dispel shows at the top of its SAML form:
Identifier (Entity ID) ← Dispel's Service Provider (SP) Entity ID.
Click Connect on the Microsoft Entra ID card and Select Authentication Protocol → SAML.
Copy the Service Provider (SP) Entity ID and Assertion Consumer Service URL shown at the top of the form (use Copy ID / Copy URL) into Entra, as above.
Fill in the fields:
Click Save settings.
Click Test connection. Dispel redirects you to Entra to sign in, then shows the email and name it received. If the test fails, confirm the values match your Entra app and that the test user is invited to your organization.
Users sign in by entering your Organization Identifier on the Dispel sign-in screen and authenticating with Microsoft. See .
Map Entra groups to Dispel groups so membership stays in sync — see .
MFA enforced in Entra applies during sign-in; Dispel's email one-time codes don't apply to SSO users. See .
To switch protocols or providers, disconnect first. See .
/client-app-launcher/oktaauth.dispel.io — (e.g. https://app.dispel.com/client-app-launcher/oktaauth.dispel.io).
Confirm the exact address for your environment with your Dispel representative if you're unsure.
Under Certificates & secrets, create a client secret and copy its value.
Note your Application (client) ID and your tenant's OAuth/OIDC endpoint.
From the Entra SAML setup, collect:
Login URL → Dispel's SSO URL.
Microsoft Entra Identifier → Dispel's Identity Provider Entity ID.
Download the Certificate (Base64) → Dispel's Base64 Signing Certificate.
Client URL
Your tenant's OAuth/OIDC endpoint (where tokens are issued).
Client ID
The Application (client) ID from your app registration.
Client Secret
The client secret value you created.
Organization Identifier
A unique identifier you choose; users type it on the sign-in screen.
SSO URL
The Entra Login URL.
Identity Provider Entity ID
The Microsoft Entra Identifier.
Base64 Signing Certificate
The downloaded Base64 certificate. Paste it or use Upload Certificate.
Organization Identifier
A unique identifier you choose; users type it on the sign-in screen.