---
updatedAt: 2025-09-19T00:40:39.000Z
agentTools:
  projectIndex: https://docs.synthesia.io/llms.txt
---

# Set up Entra/Azure for SSO Configuration

## Step 1: Request SSO Setup

Start by reaching out to your Customer Success Manager to ensure your current plan allows SSO setup. Then loop in the Support Team (<support@synthesia.io>) and ask them to kickstart the process.

## Step 2: Configure the connection between your Identity Provider (IdP) and Synthesia’s SSO service provider

1. After the support team sends you the WorkOS setup link, please click on it and follow the Admin Portal instructions
2. You will see a list of the IdP providers available. Choose the one you need and follow the corresponding step-by-step guidelines on how to configure the IdP settings.

Once done, you will be able to test your SSO integration with that identity provider.

<Image align="center" border={false} caption="Configure Single Sign-On - WorkOS" src="https://files.readme.io/24ecdefbd00fa4bf80c7bc2f350ef32bb1298884e2f4d42f2f7a15717fc06bf7-sso.png" />

## Step 3: Create an Enterprise Application

1. Sign in to the [Microsoft Entra admin center⁠](https://entra.microsoft.com/).
2. In the left navigation menu, expand the *Identity* section.
3. Expand the *Applications* sub-section.
4. Select the *Enterprise applications* tab and click `New application`.

<Image align="center" border={false} caption="Enterprise applications - Microsoft Entra admin center" src="https://files.readme.io/45d501b502d960ce0f240b8cadde6300a2b1a2ab3d2cc6bfcd4ba7d3fb0a87ee-2246abd4-f06f-4d61-a791-c0b4b8289024.avif" />

5. On the *Browse Microsoft Entra Gallery* page, click `Create your own application`.

<Image align="center" border={false} caption="Create your own application - Browse Microsoft Entra Gallery" src="https://files.readme.io/1aa4d1094a5b9c3acf38cc579a7c97f7eb5bd11cfc122d9970463f2ac6534b6c-c1f651d3-bfa4-4ecb-8bbb-be69d6b91565.png" />

6. Enter an appropriate app name, such as "Synthesia".
7. Select the `Integrate any other application you don’t find in the gallery (Non-gallery)` option, then click `Create`.

## Step 4: Basic SAML Configuration

1. In the left navigation menu, select the `Single sign-on` tab and click on the `SAML` tile.

<Image align="center" border={false} caption="SAML tile - Single-sign on" src="https://files.readme.io/e85c30527ccf544f5a160879fe8300d0afd0f3e72d3cfdc80e02203531ff58d9-b857e492-a90e-4a8f-b6d5-c2c8dfccfdf9.png" />

2. The *Setup Single Sign-On with SAML* page will open.
3. Locate the *Basic SAML Configuration* section and click on the `Edit` icon in the top right corner of the step.

<Image align="center" border={false} caption="Basic SAML Configuration - Setup Single Sign-On with SAML" src="https://files.readme.io/c1ac85c9c86b4de93790b9c192daf06948cd5b5db4f12892ae02b8dbecdb4849-35bd6593-702c-4b86-8179-0f2a564d9f45.png" />

4. Copy the *Identifier (Entity ID)* and the *Reply URL (Assertion Consumer Service URL)* from the WorkOS guide setup link you received and paste them into the *Basic SAML Configuration* panel.
5. Click `Save`, then close the edit panel.

<Image align="center" border={false} caption="Basic SAML Configuration - Setup Single Sign-On with SAML" src="https://files.readme.io/b30ed569a69c94cdbf7fc1eb8ea8bdb77fb8b288722c456e214d119aa8ed33b8-d11e974e-3fa6-40db-bc63-b677dcf1ce0a.png" />

## Step 5: Configure Attributes and Claims

1. Locate the *Attributes & Claims* section and click on the `Edit` icon in the top right corner of the step.

<Image align="center" src="https://files.readme.io/49cd47f498e14f357966d651369907f72e3e220d28bd9f1a040c3968886ada2e-c5fdba60-2e25-4ae9-a267-970e37c5ba14.png" />

2. Ensure that the required claims listed below are configured. The claims may or may not already be configured, depending on your current configuration.

| Name                          | Source Attribute           |
| :---------------------------- | :------------------------- |
| **emailaddress** *(Required)* | **user.mail**              |
| **givenname** *(Required)*    | **user.givenname**         |
| **name** *(Required)*         | **user.userprincipalname** |
| **surname** *(Required)*      | **user.surname**           |

Below is an example of how to format your claim within the Azure claim editor. Make sure the Namespace value ends in `/claims`.

<Image align="center" src="https://files.readme.io/476b2424131a66c2f8f7891b28df9d034f89ecfe73f225bdd509f61a55e9f923-ee2f90fc-2c4c-4d3f-bed8-b85d5515bf55.png" />

<Image align="center" src="https://files.readme.io/9fd05cd21f2e054bc6fd0585d71c8c9aa8956147769fb097dc6eb4cf172d2ff9-b3467340-bdf9-4f0b-8ca6-354fc1f8f33e.png" />

## Step 6: Assign Users and Groups

1. In the left navigation menu, select the `Users and groups` tab, then click `Add user/group`.

<Image align="center" border={false} caption="Users and groups - Attributes & Claims" src="https://files.readme.io/9eb0afbb09a7a8fa642c35010adb89e941e0261a25304efde7a7627579fc3aba-15448828-6288-4350-9ac3-27c9997f04e4.png" />

2. Select appropriate users and groups to add to the SAML application.

<Image align="center" border={false} caption="Add Assignment - Attributes & Claims" src="https://files.readme.io/ddc739169eec4892a9ca145954fe2bd966c9a193f828533e2b5664ef293d2622-e3964bfc-92b2-497d-b291-098cbe1ee94f.png" />

3. When finished, click `Assign` to add the selected users and groups to your SAML application.

<Image align="center" border={false} caption="Assign Users and Groups - Attributes & Claims" src="https://files.readme.io/65d7cf0cc007cc0c1e6bd002a404e5c9f76c6e4a139e1645c0210c874a5e5035-80e136c6-6e9f-41f4-aed9-85421746906b.png" />

## Step 7: Add an Application Logo

Optionally, you can add a logo to serve as the app’s entry point on the Microsoft Entra My Apps portal. Including a logo helps users easily identify and access Synthesia.

1. In the left navigation menu, select the `Properties` tab and locate the *Logo* field.
2. Click on the blue folder icon to upload the logo image, then click `Save`.

<Image align="center" border={false} caption="Application logo - Attributes & Claims" src="https://files.readme.io/031731f698a459141fceaf73017f91940e7ec69374e2cb73462f824d96cfc536-f0d4365a-c2a8-4779-9326-2e640b3e6279.png" />

## Step 8: Set Identity Provider Metadata

1. Choose either `Dynamic configuration` (recommended) or `Manual configuration` (enter your identity provider settings).
2. In the left navigation menu, select the `Single sign-on` tab.
3. Scroll down to the *SAML Certificates* section and  locate the *App Federation Metadata Url*.
4. Click on the field to copy the URL.

<Image align="center" border={false} caption="SAML Certificates - SAML-based Sign-on" src="https://files.readme.io/96ddaef352407ece0be228326d5b6397f89f6121c17f57496f74531468ee2fa9-00afd3fe-0a2a-40b3-b240-37401ae53294.png" />

5. Paste the value into the *Identity provider metadata URL* field in the WorkOS setup guide you received to continue to the next step.

<Image align="center" src="https://files.readme.io/69e33c33274667edd89c3356bfdba79c86cf846c6052d49f92f1a920c261b65a-fixfix.png" />

## Step 9: Test Single Sign-On

Test signing in with Entra ID to verify that the single sign-on connection was configured correctly.

When you finish the setup, you should get the *SSO successful test* notification, which would mean that the connection between WorkOS and your IdP was established:

<Image align="center" border={false} caption="SSO Test succeeded notification" src="https://files.readme.io/add0e14c343874d96b4a221d078f1f1c3fb40709381d176747beef180ff6a2a6-final.png" />

## Step 10: Enforce SSO

After a successful test, please [reach out to the Synthesia support team](support@synthesia.io), who will send you a test login link to try accessing your account with SSO and after you confirm a successful attempt, they will be able to enforce your SSO in production.

Be sure to include:

* A validation that the tests worked
* A list of domain names managed by your IdP (e.g. synthesia.io)

# What’s Next

* [How can I restrict access to videos using SSO? - Synthesia Knowledge Base](https://help.synthesia.io/en/articles/11173480-how-can-i-restrict-access-to-videos-using-sso-beta)