Set up SAML SSO with Microsoft Entra ID (Azure AD)

1. Sign in to Microsoft Entra. Navigate to Enterprise apps. Click New application.
   
2. Click Create your own application.
   
3. Create your application. Click Create to proceed. 
   • Name the application (e.g., Otter.ai SSO)
   • Select Integrate any other application you don't find in the gallery (Non-gallery)
     
4. Once the application has been created. Click Set up single sign on.
   
5. Select SAML.
   

Follow the steps below to set up SSO. 

Know your Team Handle ✨ 

Before starting, copy your Team Handle.

1. Navigate to Manage Workspace → Settings. Under SAML Authentication, click Configure.
   
2. Each workspace will have its own unique team handle. Click Copy to copy your workspace's team handle.
   

1) Basic SAML configuration

1. Edit Basic SAML Configuration.
2. Click Add identifier and Add reply URL.
   

3. Add the following URLs, replacing yourhandle with your Team Handle obtained in Step 1. Click Save when finished.

   • Identifier (Entity ID): https://otter.ai/saml/metadata/yourhandle
   • Reply URL (Assertion Consumer Service URL: https://otter.ai/saml/yourhandle
     
   Note: Otter does not require Sign-on URL, Relay State, or Logout URL. These fields can be left blank.
4. ✅ Basic SAML Configuration is complete.
   

2) Attributes & Claims

Follow the steps below to ensure the correct attributes & claims are added. 

1. Edit Attributes & Claims.
   
   

   Note: Microsoft Entra ID may use default claim names (e.g., http://schemas...). Update each claim name to match the SAML attributes required by Otter, such as email, first_name, and last_name.
2. Click into Unique User Identifier (NameID). Edit the following settings, then click Save.
   • Name identifier format: Persistent

   • Source attribute: A unique, permanent identifier for the user (e.g., employee ID). Learn more about selecting a NameID in our FAQs.
     

     Note: Avoid using email addresses for your NameID attribute. Email addresses can change over time, leading to duplicate accounts.
3. Click into user.mail claim. Edit the following settings, then click Save.
   • Name: email
   • Namespace: Leave blank
   • Name format: Unspecified
   • Source attribute: user.mail
     
4. Click into user.givenname claim. Edit the following settings, then click Save.
   • Name: first_name
   • Namespace: Leave blank
   • Name format: Unspecified
   • Source attribute: user.givenname
     
5. Click into user.surname claim. Edit the following settings, then click Save.
   • Name: last_name
   • Namespace: Leave blank
   • Name format: Unspecified
   • Source attribute: user.surname
     
6. Delete the user.userprincipalname claim under Additional claims. It is not needed. 
   

7. ✅ Attributes & Claims setup is complete.

   

   Note: Microsoft Entra ID may use default claim names (e.g., http://schemas...). Update each claim name to match the SAML attributes required by Otter, such as email, first_name, and last_name.

3) SAML Certificates

1. Download Certificate (Base64).
   
2. Once the file has downloaded. Open the certificate to view the content. Copy the certificate.
   

4) Set up Otter.ai SSO

Configure the SSO settings on Otter's side. 

1. Navigate to Manage Workspace → Settings. Under SAML Authentication, click Configure.
   
2. Fill out the fields using the info generated by your IdP.
   • Login URL → SAML Endpoint
   • Microsoft Entra Identifier → Identity Provider Issuer

   • Certificate content → Public Certificate

     

3. Click Save and Test.

   

Once testing is complete and everything looks correct, toggle Enable SAML on for your workspace. You’ll have two options when enabling SSO:

• Allow other login options: SSO is optional; team members can continue using their preferred sign-in methods. Recommended during the testing phase to ensure uninterrupted access.

• Require SSO for all Team members: All team members must sign in using SSO. Other sign-in methods are disabled.

  

If your organization uses assignment-based access, ensure the required users and groups are assigned to the Otter SSO enterprise application.

Review and adjust the following application properties as needed:

• Enabled for users to sign in: Set to Yes for users to be able to authenticate into Otter using SSO.
• Logo: Optionally add a logo to make the application easier to recognize. The Otter logo is available at the bottom of this article.

• User access URL: Share this link with team members for direct access. It supports both signing in and creating a new account through just-in-time (JIT) provisioning.

  Tip: Team members can also access the Otter SSO application through Microsoft My Apps. 
• Assignment required: Review this setting to control access by assigning specific users or groups.
• Visible to users: Set to Yes if you want the application to appear in Microsoft My Apps.

Once SAML SSO is enabled, members who have been added to or have access to the SSO flow can sign in to Otter using your organization’s identity provider (IdP).

SP-initiated sign-in

For an SP-initiated sign-in, members start from Continue with Microsoft or Other ways to log in and are redirected to your identity provider to authenticate. After successful authentication, they are redirected back to Otter and signed in.

IdP-initiated sign-in

For an IdP-initiated sign-in, members can start from Microsoft Apps. After successful authentication, they are redirected to Otter and signed in.