Tutorial: Set up Azure Active Directory authentication for SQL Server
Applies to: SQL Server 2022 (16.x) Preview
This document describes a step-by-step process on how to set up Azure Active Directory (Azure AD) authentication for SQL Server, and how to use different Azure AD authentication methods. This feature is available in SQL Server 2022 (16.x) Preview or later versions, and is only supported for SQL Server on-premises, for Windows and Linux hosts. Azure Virtual Machines aren't supported.
In this tutorial, you learn how to:
- Create and register an Azure AD application
- Grant permissions to the Azure AD application
- Create and assign a certificate
- Configure Azure AD authentication for SQL Server through Azure portal
- Create logins and users
- Connect with a supported authentication method
- SQL Server 2022 (16.x) Preview is installed.
- SQL Server is connected to Azure cloud. For more information, see Connect your SQL Server to Azure Arc.
- SQL Server Azure Arc extension version 1.1.1795.50 or higher for Windows, or version 1.0.2018.1 or higher for Linux, is installed.
- Access to Azure Active Directory is available for authentication purpose. For more information, see Azure Active Directory authentication for SQL Server.
- SQL Server Management Studio (SSMS) version 18.0 or higher is installed on the client machine. Or download the latest Azure Data Studio.
Extended functionality has been implemented in Azure to allow the automatic creation of the Azure Key Vault certificate and Azure AD application during setting up an Azure AD admin for the SQL Server. For more information, see Tutorial: Using automation to set up the Azure Active Directory admin for SQL Server.
To perform Azure AD authentication, SQL Server needs to be able to query Azure AD and requires an Azure AD app registration, which it can authenticate as. The app registration also needs a handful of permissions for the queries SQL Server will perform.
SQL Server uses a certificate for this authentication, and it is stored in Azure Key Vault (AKV). The Azure Arc agent downloads the certificate to the SQL Server instance host.
Connections authenticated by Azure AD are always encrypted. If SQL Server is using a self-signed certificate, you must add
trust server cert = true in the connection string. SQL Server and Windows authenticated connections don't require encryption, but it is recommended.
Create and register an Azure AD application
- Go to the Azure portal, select Azure Active Directory > App Registrations > New Registration.
- Specify a name - In the example below, we use SQLServerCTP1.
- Select Supported account types and use Accounts in this organization directory only
- Don't set a redirect URI
- Select Register
See the application registration below:
Grant application permissions
Select the newly created application, and on the left side menu, select API Permissions.
Select Add a permission > Microsoft Graph > Application permissions
- Check Directory.Read.All
- Select Add permissions
Select Add a permission > Microsoft Graph > Delegated permissions
- Check Application.Read.All
- Check Directory.AccessAsUser.All
- Check Group.Read.All
- Check User.Read.All
- Select Add permissions
Select Grant admin consent
To grant Admin consent to the permissions above, your account requires a role of Azure AD Global Administrator or Privileged Role Administrator.
Create and assign a certificate
Go to the Azure portal, select Key vaults, and select the key vault you wish to use or create a new one. Select Certificates > Generate/Import
For the Method of certificate creation, use Generate.
Add a certificate name and subject.
The recommended validity period is at most 12 months. The rest of the values can be left as default.
Once the certificate is created, it may say it is disabled. Refresh the site and it will show the certificate as enabled.
Navigate to the new certificate, and select the row for the certificate's latest version. Select Download in CER format to save the certificate's public key.
This does not need to be done on the SQL Server host. Rather, any client that will access the Azure portal for the next step.
In the Azure portal, navigate to the app registration created above and select Certificates & secrets
- Select upload certificate.
- Select the public key (.cer file) downloaded in the last step.
- Select Add.
In the Azure portal, navigate to the Azure Key Vault instance where the certificate is stored, and select Access policies
Select Add Access Policy.
For Key permissions, use 0 selected.
For Secret permissions, select Get and List.
For Certificate permissions, select Get and List.
For Select principal, use the account for your Azure Arc instance, which is the hostname of the SQL Server host.
Select Add and then select Save.
You must Save to ensure the permissions are applied. They are not applied after selecting Add. To ensure permissions have been stored, refresh the browser window, and check the row for your Azure Arc instance is still present.
Configure Azure AD authentication for SQL Server through Azure portal
Go to the Azure portal, and select SQL Server – Azure Arc, and select the instance for your SQL Server host.
Check the status of your SQL Server - Azure Arc resource and see if it's connected by going to the Properties menu. For more information, see Validate the SQL Server - Azure Arc resources.
Select Azure Active Directory on the left-hand column.
Select Set Admin, and choose an account that will be added as an admin login to SQL Server.
Select Customer-managed cert and Select a certificate.
Select Change certificate, and select your AKV instance and certificate that you created earlier in the new pane.
Select Customer-managed app registration.
Select Change app registration, and select the app registration you created earlier.
Select Save. This will send a request to the Arc server agent, which will configure Azure AD authentication for that SQL Server instance.
It takes several minutes to download certificates and configure settings. After setting all parameters and selecting Save on the Azure portal, the following message may appear:
SQL Server's Azure Arc agent is currently processing a request. Values below may be incorrect. Please wait until the agent is done before continuing. Wait until the save process is confirmed with
Saved successfully, before attempting an Azure AD login.
The Azure Arc server agent can only update once the previous action has completed. This means that saving a new Azure AD configuration before the last one has finalized can cause a failure. If you see the message Extended call failed when you select Save, wait 5 minutes and then try again.
The admin login specified in the portal will be added as a
sysadminto the SQL Server instance, but it will not be listed in
Create logins and users
After the Azure Arc agent on the SQL Server host has completed its operation, the admin account selected in the Azure Active Directory pane in the portal will be a
sysadmin on the SQL Server instance. To sign in, use any SQL Server client like SSMS or Azure Data Studio.
All connections to SQL Server that are done with Azure AD authentication require an encrypted connection. If the Database Administrator (DBA) has not set up a trusted SSL/TLS certificate for the server, logins will likely fail with the message The certificate chain was issued by an authority that is not trusted. To fix this, either configure the SQL Server instance to use an SSL/TLS certificate which is trusted by the client or select trust server certificate in the advanced connection properties. For more information, see Enable encrypted connections to the Database Engine.
Create login syntax
The same syntax that is used for creating Azure AD logins and users on Azure SQL Database and Azure SQL Managed Instance can now be used on SQL Server. However, on SQL Server this can be done by any account that has the
ALTER ANY LOGIN or
ALTER ANY USER permission. Any account with either of these permissions can create a login or user respectively. They don't need to be an Azure AD login.
To create a login for an Azure AD account, execute the T-SQL command below in the
CREATE LOGIN [principal name] FROM EXTERNAL PROVIDER;
For users, the principal name should be in the format
firstname.lastname@example.org. For all other account types, the tenant name isn't necessary and either the Azure AD group name or application name must be used.
Here's some examples:
-- login creation for Azure AD user CREATE LOGIN [email@example.com] FROM EXTERNAL PROVIDER; GO -- login creation for Azure AD group CREATE LOGIN [my_group_name] FROM EXTERNAL PROVIDER; GO -- login creation for Azure AD application CREATE LOGIN [my_app_name] FROM EXTERNAL PROVIDER; GO
To list the Azure AD logins in
master database, execute the T-SQL command:
SELECT * FROM sys.server_principals;
To grant an Azure AD user membership to the
sysadmin role (for example
firstname.lastname@example.org), execute the following commands in
CREATE LOGIN [email@example.com] FROM EXTERNAL PROVIDER; GO EXEC sp_addsrvrolemember @firstname.lastname@example.org', @rolename='sysadmin'; GO
sp_addsrvrolemember stored procedure must be executed as a member of the SQL Server
sysadmin server role.
Create user syntax
You can create an Azure AD user either as a user with an Azure AD login, or as an Azure AD contained user.
To create an Azure AD user from an Azure AD login in a SQL Server database where the user should reside in, use the following syntax:
CREATE USER [principal_name] FROM LOGIN [principal_name];
principal_name syntax is the same as for logins.
Here are some examples:
-- for Azure AD user CREATE USER [email@example.com] FROM LOGIN [firstname.lastname@example.org]; GO -- for Azure AD group CREATE USER [my_group_name] FROM LOGIN [my_group_name]; GO -- for Azure AD application CREATE USER [my_app_name] FROM LOGIN [my_app_name]; GO
To create an Azure AD contained user without a login, the following syntax can be executed:
CREATE USER [principal name] FROM EXTERNAL PROVIDER;
Use Azure AD group name or Azure AD application name as
<principal name> when creating an Azure AD user as a group or application.
Here are some examples:
-- for Azure AD contained user CREATE USER [email@example.com] FROM EXTERNAL PROVIDER; GO -- for Azure AD contained group CREATE USER [my_group_name] FROM EXTERNAL PROVIDER; GO --for Azure AD contained application CREATE USER [my_group_name] FROM EXTERNAL PROVIDER; GO
To list the users created in the database, execute the following T-SQL command:
SELECT * FROM sys.database_principals;
The newly created user in a database has only the Connect permission, by default. All other SQL Server permissions for this user must be explicitly granted by the grantors.
Azure AD guest accounts
CREATE LOGIN and
CREATE USER syntax also supports guest users. For example, if
firstname.lastname@example.org was invited to the
contoso.com tenant, it could be added as a login to SQL Server with the syntax below. In the example,
outlook.com is provided even though SQL Server will use the account registered in the
The following section has examples of creating guest users.
Create a guest user with login that exists
CREATE USER [email@example.com] FROM LOGIN [firstname.lastname@example.org];
Create a guest user as a contained user
CREATE USER [email@example.com] FROM EXTERNAL PROVIDER;
Connect with a supported authentication method
SQL Server supports four authentication methods for Azure AD authentication:
- Azure Active Directory Password
- Azure Active Directory Integrated
- Azure Active Directory Universal with Multi-Factor Authentication
- Azure Active Directory access token
Use one of these methods to connect to the SQL Server instance. For more information, see Azure Active Directory authentication for SQL Server.
Authentication example using SSMS
Below is the snapshot of the SQL Server Management Studio (SSMS) connection page using the authentication method, Azure Active Directory - Universal with MFA.
During the authentication process, a database where the user was created must be explicitly indicated in SSMS. Expand Options > Connection Properties > Connect to database:
For more information on Azure Active Directory - Universal with MFA authentication method, see Universal with MFA.
SQL Server tools that support Azure AD authentication for Azure SQL are also supported for SQL Server 2022 (16.x) Preview.
Location where Azure AD parameters are stored
Azure AD parameters are configured by the Azure Arc agent, and should not be reconfigured manually.
On Linux, Azure Active Directory parameters are stored in
mssql-conf. For more information about the Azure AD configuration options in Linux, see Configure SQL Server on Linux with the mssql-conf tool.
- Updating certificate doesn't propagate:
Once Azure AD is configured for SQL Server, updating the certificate in SQL Server - Azure Arc resource's Azure AD pane may not propagate fully. This results in the save being successful but the old value still being displayed. To update the certificate, do the following:
- Select Remove Admin.
- Select Save.
- Select Set Admin and reconfigure Azure AD authentication with the new certificate.
- Select Save.
Submit and view feedback for