You can connect your Microsoft Entra ID account with your Dext account and enable single sign-on to access your Dext account via your Entra ID SSO login details.
First, you need to install Dext as an “Enterprise Application” in your Microsoft Entra ID tenant. After that you have to configure the SAML details and connect your account in Dext with the installed application.
- Add Dext as Enterprise Application in Microsoft Entra ID
- Connect Microsoft Entra ID SSO to your Dext Account
- Setting up Microsoft Entra ID SSO for Multiple Dext Accounts
- Troubleshooting
Add Dext as Enterprise Application in Microsoft Entra ID
- Login to Microsoft Entra ID.
- Go to ‘Enterprise Applications’ and select New Application.
You will need to be assigned the Application Administrator at least.
- Then click Create your own application.
- Enter ‘Dext’ as the name of your application. Select the ‘Integrate any other application you don’t find in the gallery (Non-gallery)’ checkbox and when ready click Create.
- Once that is created, go to ‘Set up single sign on’ or click on ‘Single sign-on’ in the left sidebar.
- Then go to SAML.
- Click Edit on the first step of the configuration to add the relevant information for Dext account.
Set the following configurations:
- ‘Identifier (Entity ID)’ must be set to your Dext Account CRN
- ‘Reply URL (Assertion Consumer Service URL)’ must be set to: https://app.dext.com/saml/entra/complete
- Be sure to save the configuration settings before proceeding. Then, go to the ‘SAML certificates’ section and copy the ‘App Federation Metadata Url’
- Now return to your Dext account and follow the steps in the section below to Connect Microsoft Entra ID SSO to your Dext Account.
Connect Microsoft Entra ID SSO to your Dext Account
To enable Microsoft Entra ID SSO in your Dext account:
- Go to the Practice settings in the sidebar, then Authentication.
- Click Connect next to Microsoft Entra ID.
- Read the summary of steps, and tick the ‘I have created a new enterprise application in my Microsoft Entra ID tenant’ checkbox. Then, click Next.
- Next, if you have completed the steps in the ‘Add Dext as Enterprise Application in Microsoft Entra ID’ section above, tick the checkbox to confirm you ‘have configured the SAML settings in my Microsoft Entra ID tenant’. When ready, click Next.
If you haven’t completed these steps, follow the steps provided in the Add Dext as Enterprise Application in Microsoft Entra ID section above and use the ‘Identifier’ and ‘Reply URL’ provided on this page when requested.
- Next, enter the Metadata URL you copied from your application in Entra ID. It can be found in your SAML configurations. When ready, click Connect.
- Finally you will see a confirmation of a successful connection.
That’s it! Now, you can assign users (or groups) to your application in Microsoft Entra ID and start using the SSO.
Setting up Microsoft Entra ID SSO for Multiple Dext Accounts
All of your Dext accounts can be set up for SSO. To connect them with Microsoft Entra ID, you need to install a separate Dext application in your Entra ID tenant for each of them. These applications can after that be linked to your Dext accounts by specifying the relevant account CRN in your SAML configuration.
When you configure the application in Entra ID, go to your Dext account and enter the relevant Metadata URL.
Troubleshooting
Change in SAML Certificates
If you change your certificate in Microsoft Entra ID, your SSO will stop working until you synchronize your connection in Dext.
To do that:
- Go to your Authentications page and click on Refresh.
- You will see a modal that shows from which URL Dext will fetch your data. Click Refresh.
- You can also manually enter your new credentials in the form on the page.
Connecting to a New Dext Application
If you want to connect to a new Dext application in your Microsoft Entra ID tenant, you have to disconnect your current connection in Dext.
To do that:
- Go to your Authentications page and click Disconnect, and confirm your action.
- After that go through the integration flow again by entering your new Metadata URL. Verify that the fetched certificates match.