Single sign-on (SSO)
Enterprise only
SSO is available exclusively on Enterprise plans. Contact sales to upgrade.
SSO lets users in your Organization authenticate with their existing corporate identity provider (IdP) credentials using SAML 2.0. We support any compliant IdP, including Okta, Microsoft Entra ID (formerly Azure AD), and Google Workspace.
Benefits
- Centralized authentication: users sign in with their familiar corporate credentials, reducing password fatigue.
- Automatic account creation: user accounts are provisioned on first sign-in through your IdP.
- Simplified management: manage access centrally from your IdP rather than inviting users one by one.
Prerequisites
Before you set up SSO, you need:
- An Enterprise plan subscription.
- Domain verification completed in the Admin Panel. This proves you control the domain and is required for both SSO and Email Domain Authentication. See domain verification below.
Domain verification
Domain verification is a one-time setup that proves you own your email domain.
- Open Admin›Access ↗ settings.
- Click Add domain in the Domain Ownership section.
- Enter your domain (e.g.,
yourcompany.com) and click Add domain. - Click Instructions and copy the DNS TXT record provided.
- In your domain registrar or DNS provider, add a new TXT record:
- Type:
TXT - Host/Name:
@or your domain (depends on your provider) - Value: paste the verification code (e.g.,
mistral-domain-verification=xxxxxx)
- Type:
- Save the record and wait for DNS propagation (typically 10 minutes to 24 hours).
You can check propagation status with:
nslookup -type=TXT yourcompany.comThe Admin Panel updates the status to Verified once propagation completes.
Keep the DNS TXT record active. Removing it breaks both Email Domain Authentication and SSO.
Set up SSO
- Open Admin›Access ↗ settings.
- In the Authentication section, find Single Sign-On (SAML SSO) and click Activate SSO.
- A configuration modal appears. Keep it open while you configure your IdP.
- In your IdP admin console, create a new SAML 2.0 application for Mistral AI.
- Copy the ACS URL and Entity ID from the Mistral modal into your IdP configuration.
- Map user attributes in your IdP (case-sensitive):
- User's first name:
firstName - User's last name:
lastName
- User's first name:
- Set Name ID Format to
EmailAddress. - Obtain the SAML metadata XML from your IdP.
- Paste the complete XML into the text box in the Mistral configuration modal.
- Click Enable SSO.
Users with email addresses matching your verified domain are now redirected to your IdP for authentication.
Signing in with SSO
From the user's perspective:
- Go to the Mistral AI login page.
- Enter your work email address.
- The password field disappears and the button changes to Sign in with SSO.
- Click Sign in with SSO, then select your organization.
- Authenticate with your corporate credentials on your IdP's login page.
- You're redirected back to Mistral AI, logged in.
Supported identity providers
We use the SAML 2.0 standard, so any compliant IdP should work. The most commonly used providers are:
- Microsoft Entra ID (formerly Azure Active Directory)
- Google Workspace / Google Identity Platform
- Okta
Refer to your IdP's documentation for specific SAML application setup instructions.
Disable SSO
You can disable SSO at any time from the Access settings page in the Admin Panel.
Disabling SSO means users can no longer sign in through your IdP. They'll need to set a password (via the reset flow) or be re-invited. Automatic user provisioning also stops. Consider enabling Email Domain Authentication as an alternative before disabling SSO.
Limitations
- OIDC isn't supported. We use SAML 2.0 only for enterprise SSO. (OIDC/OAuth 2.0 is used separately for individual social login with Google, Apple, or Microsoft.)
- SSO is available on Enterprise plans only.
Troubleshooting
If SSO fails after configuration:
- Verify the ACS URL and Entity ID match exactly between Mistral and your IdP.
- Confirm attribute mappings are case-sensitive (
firstName,lastName). - Check that Name ID Format is set to
EmailAddress. - Make sure the metadata XML is complete and correctly pasted.
- Contact support if issues persist.