How can we help? 👋

How to set up an Azure SSO Connection (Legacy)

Directions for setting up an SSO connection with Microsoft’s Azure AD.

Verbate now works with WorkOS to set up new SSO connections. To see those instructions, click here.


Verbate uses Auth0 to manage identity, so the below process gives us the information we need to leverage Auth0’s Azure Enterprise Connection.

To create an Azure Enterprise Connection, we’ll need to exchange a few pieces of information. When we’ll use these pieces of information will be explained below.

What Information We’ll Exchange

What you’ll need from Verbate:


What we’ll need from you:

  • Your Azure Domain Name

Register Verbate as an Application with Azure AD


Registering Verbate with Azure establishes a trust relationship between Verbate and the Microsoft identity platform. The trust is unidirectional: Verbate trusts the Microsoft identity platform, and not the other way around.

Register the Application and Create Client ID

  1. Sign in to the Azure portal.
  1. If you have access to multiple tenants, use the Directories + subscriptions filter in the top menu to switch to the tenant in which you want to register the application.
  1. Search for and select Azure Active Directory.
  1. Under Manage, select App registrations > New registration.
  1. Enter the name Verbate for your application. Users of your application might see the display name when they use the app, for example during sign-in. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies your app within the identity platform.
  1. Specify who can use the application, sometimes called its sign-in audience. For customers of Verbate, you’ll likely want to select Accounts in this organizational directory only.
  1. Enter for Redirect URI (optional) and select “Web”.
  1. Select Register to complete the initial app registration.

When registration finishes, the Azure portal displays the app registration's Overview pane. You see the Application (client) ID. Also called the client ID, this value uniquely identifies your application in the Microsoft identity platform.

Save this Application (client) ID - you’ll need to provide this to the Verbate team.

Add a client secret

Sometimes called an application password, a client secret is a string value your app can use in place of a certificate to identity itself.

  1. In the Azure portal, in App registrations, select your application.
  1. Select Certificates & secrets > Client secrets > New client secret.
  1. Add a description for your client secret.
  1. Select an expiration of 24 months for the secret.
  1. Select Add.
  1. Record the secret's value for use in your client application code. This secret value is never displayed again after you leave this page.
Save this Client Secret - you’ll need to provide this to the Verbate team.

Update App Visibility

New app registrations are hidden to users by default. When you are ready for users to see the app on their My Apps page you can enable it. To enable the app, in the Azure portal navigate to Azure Active Directory > Enterprise applications and select the app. Then on the Properties page toggle Visible to users? to Yes.


Define Custom Homepage/Sign in URL for the Published App

Now that you’ve created an app, you need to ensure that the app knows where to send the user after they’ve been authenticated by your systems.

Within the Verbate app you built in Azure, head to Branding -> Homepage URL, and add the following URL:


These instructions were created based on Microsoft’s documentation on how to add an application to Azure. Click here to read Microsoft’s documentation directly. Here’s the documentation for updating the home page URL, which recently changed.

Did this answer your question?