Body
The examples below were provided to TeamDynamix by clients who were able to successfully configure Single Sign On using Entra ID (formerly Azure Active Directory). Please note that TeamDynamix does not have expertise in IdP configurations for Entra ID. It is best for you to speak with your internal technical team or an Entra ID professional for any issues or questions related to configuring Single Sign On in Entra ID.
Overview
This article covers how other TeamDynamix clients have configured Entra ID to allow Single Sign On authentication with iPaaS and Conversational AI.
Step 1: Gather Assertion Consumer Service URL from iPaaS + Converational AI Metadata
Before configuring SSO in Entra ID, you will need the AssertionConsumerService URL from iPaaS + Conversational AI.
- Log in to iPaaS + Conversational AI
- On the top navigation bar, go to Administration > Organization Settings
- Click on the Settings tab
- Set the User Authentication Requirements dropdown to SAML
- In the top right corner, click the Service Provider Metadata link
- The metadata will open in a new tab
- Find the link that starts with "<md:AssertionConsumerService Binding", and copy what's in the "Location=" section
- US example: https://us1.teamdynamix.com/tdapp/SAML/SingleLogoutService?__cust=CUSTOMERNAME
- CA example: https://ca1.teamdynamix.com/tdapp/SAML/SingleLogoutService?__cust=CUSTOMERNAME
- Copy this value. You will need it when configuring Entra ID
- Click Cancel to cancel out of the SAML configuration for now
Step 2: Create SAML Application in Entra ID
Step 2a. Create the SAML Application
- Login to the Azure Portal at https://portal.azure.com/ and click on Entra ID.
- n your Azure Portal, navigate to Microsoft Entra ID > Enterprise Applications and choose + New Application.
- Select the Non-gallery application option.
- Enter a Name for the application and click Add to finish.
Step 2b. Configure Basic SAML Configuration
- In the application you just created, go to the Single sign-on tab and choose the SAML box.
- Choose the edit icon in the Basic SAML Configuration box.
- Click Create New App.
- Click SAML 2.0 and click Create.
- Give the app an appropriate Name and tick both boxes to not display the app icon to users. This will confuse the users.
- Click Next.
- For Single-sign on URL, copy and paste the Consumer Assertion URL you copied from iPaaS in the "Step 1" section above
- In the Identifier (Entity ID) field, copy and paste the appropriate value for your region and environment:
- For United States Customers: https://us1.teamdynamix.com
- For Canadian Customers: https://ca1.teamdynamix.com
- In the Reply URL (Assertion Consumer Service URL) field, enter the Assertion Consumer Service URL you copied earlier, from the from iPaaS + Converational AI Metadata
- Click Save to complete the basic configuration.
Step 2c. Configure the User Attributes & Claims:
- Choose the edit icon in the User Attributes & Claims box.
- Remove any existing claims except for the default one used by the Name Identifier value.
- Click the + Add new claim button.
- In the Name field, select the SAML attribute the iPaaS + Conversational AI platform will use as the username value for authentication. This value must be a scoped, or fully qualified value in the format of user@domain.
- Leave the Namespace field blank.
- Click the Save button to create the attribute.
- Repeat steps 3 - 6 to add any other SAML attributes you wish to release to iPaaS + Conversational AI. Common attributes released include givenName (first name), sn (surname, last name), and mail (email address).
Step 2d. Determine Who Can Use the App
The organization must decide how they want to grant access to the Entra ID application to their users. There are two general ways to do this, with pros and cons to each approach.
Application Level Access
If you grant Application Level Access, any user in the Entra ID directory can pass through the Entra ID application for authentication to iPaaS + Conversational AI. This does not, however, implicitly grant them access to iPaaS + Conversational AI. iPaaS + Conversational AI still requires an internal user record, with a username value matched to the Entra ID value released in the eppn attribute, to be authorized for iPaaS + Conversational AI sign in.
To use this method, go to Manage > Properties > User assignment required? and select No. You should read the help text by clicking the icon next to this option to understand the full options for this method.

Explicit User/Group Access Grants
If you want to have more specific control over who is allowed to pass through the Entra ID application for authentication into iPaaS + Conversational AI, leave the application level setting above set to Yes. Instead, go to Manage > Users and groups and assign specific users and/or groups who can pass through this application. Any user/group not specified in this page will be prevented at the Entra ID side of the SSO authentication flow from continuing on into iPaaS + Conversational AI! Again, users/groups allowed in this page will not be implicitly granted access to iPaaS + Conversational AI. iPaaS + Conversational AI still requires an internal user record, with a username value matched to the Entra ID value released in the eppn attribute, to be authorized for iPaaS + Conversational AI sign in.

Step 3: Store Entra ID Metadata URL in iPaaS + Conversational AI
The last step before you can enable and test Entra ID authentication into iPaaS + Conversational AI is a metadata exchange.
First, get the identity provider metadata URL in Entra ID:
- In Entra ID, navigate to the application you created.
- Copy the App Federation Metadata Url link from the SAML Signing Certificate box.

Next, input it into iPaaS + Conversational AI:
- Log in to iPaaS + Conversational AI
- On the top navigation bar, go to Administration > Organization Settings
- Click on the Security tab
- Set the User Authentication Requirements dropdown to SAML
- In the SAML Definition URL box, paste the metadata URL you copied from Entra ID, then click the refresh icon
- At the bottom of the window, click Save Changes
Testing SSO Authentication
To test SSO authentication, use your organization-specific login URL to log in to iPaaS + Conversational AI.
Organization-Specific Sign-In Links
If you are logged in to SSO and access the generic iPaaS + Conversational AI URL for your region (e.g., https://ca1.teamdynamix.com), you will be automatically redirected to SSO and signed in to the environment. If you are not signed in to SSO, you will need to use your organization-specific SSO login link.
To access your organization-specific SSO URL:
- Log in to iPaaS + Conversational AI
- On the top navigation bar, go to Administration > Organization Settings
- Click on the Security tab
- Scroll to the bottom of the page
- The SSO Login URL is your organization-specific SSO URL
Best Practices for Testing SSO
When testing, a recommended approach is to use one browser (for instance Google Chrome) to have the iPaaS + Conversational AI SAML Settings page open in. Use a second browser (such as Firefox) in in-cognito or private browsing mode to actually test that SSO authentication is in fact working.
With this approach, if SSO authentication is not working or is in some way broken, you may quickly toggle SSO off back in the first browser. You can then safely troubleshoot the issues found and not be locked out of the system until you are ready to test again.
SSO Bypass URLs
If you misconfigured your SSO setup and you need to log back into iPaaS and Conversational AI to correct it, use the appropriate SSO bypass URL:
This URL will send you to the iPaaS and Conversational AI login screen where you can use your local iPaaS and Conversational AI account to log in.