Microsoft SQL Server (Azure AD)

Last modified on January 3, 2024


A datasource consists of a database resource and the credentials used to access it. This guide describes how to add a Microsoft SQL Server (Azure AD) database as a datasource in the StrongDM Admin UI. This resource type only supports Azure Active Directory (AD) authentication. For other options, see the Microsoft SQL Server and Microsoft SQL Server (Kerberos) resource types.


To add a datasource, make sure you have met the following prerequisites:

  • Properly configure an account for your database resource. If you choose to store credentials for the resource with StrongDM, have those credentials ready. When not using Strong Vault, set up a Secret Store integration and be able to enter the location of the secrets required to access the resource.
  • The hostname or endpoint you enter for your resource must be accessible by at least one gateway or relay. To verify this, log in to the gateway or relay and use the nc -zv <YOUR_HOSTNAME> <YOUR_PORT> Netcat command. For example, use nc -zv 5432. If your gateway server can connect to this hostname, you can proceed.
  • You need your Azure DB set up, app registration complete, and the intended user added to your Azure VM. If these steps are already done, the Azure Setup section can provide guidance.

Add a Datasource

To add your new Microsoft SQL Server database as a StrongDM datasource, use the following steps.

  1. Log in to the Admin UI.

  2. Go to Infrastructure > Datasources.

  3. Click Add datasource.

  4. Select Microsoft SQL Server (Azure AD) as the Datasource Type and set other configuration properties for your new database resource.

    Add Microsoft SQL Server (Azure AD) Datasource
    Add Microsoft SQL Server (Azure AD) Datasource
  5. Complete all required fields.

  6. Click Create to save the resource.

  7. Click the resource name to view status, diagnostic information, and setting details.

Resource properties

Configuration properties are visible when you add a datasource or when you click to view its settings. The following table describes the settings available for your Microsoft SQL Server database.

Display NameRequiredMeaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource TypeRequiredSelect Microsoft SQL Server (Azure AD)
HostnameRequiredHostname for your Microsoft SQL Server database resource; must be accessible to a gateway or relay
PortRequiredPort to use when connecting to your Microsoft SQL Server database; default port value is 1433
Port OverrideRead onlyAutomatically generated with a value between 1024-59999 as long as that port is not used by another resource; preferred port can be modified later under Settings > Port Overrides
DatabaseRequiredDatabase name you would like to connect to using this datasource
Secret StoreOptionalCredential store location with the default set to Strong Vault; learn more about Secret Store options
Client IDRequiredApplication (Client) ID value from app registration
SecretRequiredMicrosoft Entra (formerly Azure AD) client secret (application password) with which to authenticate
Tenant IDRequiredMicrosoft Entra (formerly Azure AD) Directory ID with which to authenticate
SchemaOptionalName of the schema that should be used if the user belongs to a particular schema
Override Default DatabaseOptionalBy default, StrongDM limits all connections to the configured database. Uncheck the box to disable this option. If this option is deselected, the value entered in the Database field is only used for healthchecks, not for user connections. When accessing the database via StrongDM, users need to explicitly pass the database name they wish to connect to in the connection string. If they do not, the value of the Username field is passed in as the database name. This is the default behavior of the database type.
Resource TagsOptionalDatasource tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)

Secret Store options

By default, datasource credentials are stored in Strong Vault. However, these credentials can also be saved in a third-party secrets management tool.

Options other than Strong Vault appear in the Secret Store dropdown if they are created under Network > Secret Stores. When you select another Secret Store type, its unique properties display. Instead of the normal Client ID, Tenant ID, and Secret fields, you see versions of them that indicate that you need to enter a path. This is the path to where the secret is stored in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional).

For more details, see Configure Secret Store Integrations.

Resource status

After a resource is created, the Admin UI displays that resource as unhealthy until the health checks run successfully. When the resource is ready, the Health icon indicates a positive, green status.

Datasource Ready
Datasource Ready

When the resource does not display a positive status, click the resource name to go to the Diagnostics tab and check for errors.

Azure Setup

This section explains one way to create and configure a new app registration in Azure Active Directory, add an admin user, and give the user proper permissions to connect to your SQL database. If your registered app is not yet configured, please follow these steps for guidance. Note that your particular configuration may differ slightly from these instructions.

Set up your SQL database

  1. Sign in to the Azure portal using an account with administrator permission.
  2. Select Azure SQL Database from the services at the top of the page. Click Create and follow the creation wizard instructions.
  3. Once creation is complete, go to Azure Active Directory and click Set admin.
  4. Set the admin to a user that you have the password for, in the format Be sure to copy the admin name for later use.
  5. From the Networking blade, add your IP address to the firewall rules.
  6. Click into the database and copy the server name, which is in the format

Create a new Azure app registration

Next, you need to create an Azure app registration.

  1. Search for “app registrations” and click on New Registrations. Enter the display name to use for the app, and copy the display name for later use.
  2. Click Register and then open the newly created app registration.
  3. Copy the Application (client) ID and the Directory (tenant) ID for later use.
  4. Go to the Certificates and Secrets blade and click New Client Secret.
  5. Name the new client secret, and then copy the value of the client secret for later use. You may not be able to see it again.

Add the user to the database

Next, you need to add the user to the DB and grant it permissions. For this you need an Azure VM with SQL Server Management Studio installed.

  1. RDP into the VM and open SQL Server Management Studio.

  2. In the object explorer, click Connect. Then click Database Engine.

  3. Enter the name of the server that you saved in a previous step (in our example,

  4. Enter the admin username (in our example, and the password, and connect.

  5. In the object explorer, find the database you created. Right-click on it and select New Query.

  6. You need to run a few queries to give your app registration proper permissions. In the following examples, make sure you replace <ENTRA_ID_USER> with the display name of your app registration.


    Set database role permissions:


    Grant database permissions:


    Grant permission to specific objects:

    GRANT SELECT ON [dbo].[promotion] TO <ENTRA_ID_USER>
    GRANT EXECUTE ON [dbo].[sp_procedure] TO <ENTRA_ID_USER>
    GRANT UPDATE ON [dbo].[promotion] TO <ENTRA_ID_USER>

Setup is complete. Now you can connect to the database using StrongDM.