This guide walks you through setting up SAML 2.0 single sign-on between TrueFoundry and Microsoft Entra ID (formerly Azure Active Directory). Once finished, members of your Entra tenant can sign in to TrueFoundry through a Login with Azure AD button.Documentation Index
Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A TrueFoundry tenant with Admin access to Settings → Security & Access → SSO.
- A Microsoft Entra ID tenant with permission to create Enterprise Applications (Cloud Application Administrator or higher).
Configuration overview
Create the SSO configuration in TrueFoundry
Create an Enterprise Application in Entra
Configure the SAML connection on both sides
Step 1 — Create the SSO configuration in TrueFoundry
Open SSO settings

Fill in the basic fields
- Enabled: turn this on.
- Name: a lowercase alphanumeric label — for example,
entraidsaml. - SSO Provider: choose Azure AD.
- Authentication Configuration: select SAML v2.
Save to reveal the Reply URL, Identifier (Entity ID), and Relay URL
- Identifier (Entity ID) in Entra — Audience URI (SP Entity ID) in TrueFoundry.
- Reply URL (Assertion Consumer Service URL) in Entra — Single Sign On URL in TrueFoundry.
- Relay State in Entra — Relay URL in TrueFoundry.

Step 2 — Create an Enterprise Application in Entra
Open the Microsoft Entra admin center

Create a new application
- Give the application a name — for example,
TrueFoundry. - Choose Integrate any other application you don’t find in the gallery (Non-gallery).
- Click Create. It may take a few seconds for Entra to finish provisioning the application.

Step 3 — Enter TrueFoundry’s details into Entra
On the Set up Single Sign-On with SAML page for the application you created in Step 2, edit the Basic SAML Configuration card using the Reply URL, Identifier (Entity ID), and Relay State from Step 1.Edit Basic SAML Configuration
| Entra field | Value from TrueFoundry |
|---|---|
| Identifier (Entity ID) | Audience URI (SP Entity ID) |
| Reply URL (Assertion Consumer Service URL) | Single Sign On URL |
| Relay State | Relay URL |


Add email and sub claims
Add the email claim
- Click Add new claim.
- Set Name to
email. - Leave Namespace blank and Name format as Omitted (default).
- Under Source, select Attribute and set Source attribute to
user.userprincipalname. - Click Save.

Add the sub claim
- Click Add new claim again.
- Set Name to
sub. - Leave Namespace blank and Name format as Omitted (default).
- Under Source, select Attribute and set Source attribute to
user.objectid. - Click Save.

email and sub alongside Entra’s default claims:| Claim name | Source attribute |
|---|---|
| Unique User Identifier (Name ID) | user.userprincipalname |
email | user.userprincipalname |
sub | user.objectid |

Step 4 — Copy Entra’s details back to TrueFoundry
Scroll down on Entra’s Set up Single Sign-On with SAML page to the SAML Certificates and Set up<Your App> cards.
Download the signing certificate
.cer file in a text editor and copy the entire contents — including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.
Step 5 — Assign users in Entra
Entra only lets users sign in to applications they’ve been explicitly assigned to.Open Users and groups

Step 6 — Test single sign-on
- Open a private/incognito window and go to your TrueFoundry login page.
- Click Login with Azure AD (or whichever button label you chose under Show advanced fields → Button Text).
- Authenticate with an Entra user that you assigned to the application.
Optional next steps
- Automate user lifecycle with SCIM — see SCIM with Microsoft Entra ID to push users and groups from Entra into TrueFoundry automatically.
- Use OIDC instead of SAML — see OIDC with Microsoft Entra ID for the equivalent OpenID Connect flow.
Troubleshooting
The Login button works but the user gets 'no matching user found'
The Login button works but the user gets 'no matching user found'
'AADSTS50105: The signed in user is not assigned to a role for the application'
'AADSTS50105: The signed in user is not assigned to a role for the application'
'Invalid Signature' or 'Could not validate SAML response'
'Invalid Signature' or 'Could not validate SAML response'
Users sign in but email or unique ID is empty
Users sign in but email or unique ID is empty
email and sub claims under Attributes & Claims as described in Step 3. If those claims are missing or mapped incorrectly, TrueFoundry cannot read the user’s email or unique ID from the SAML response.


