STIGQter STIGQter: STIG Summary: Microsoft Azure SQL Managed Instance Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 23 Sep 2025:

Azure SQL Managed Instances must integrate with Microsoft Entra ID for providing account management and automation for all users, groups, roles, and any other principals.

DISA Rule

SV-276225r1150094_rule

Vulnerability Number

V-276225

Group Title

SRG-APP-000023-DB-000001

Rule Version

MSQL-00-000100

Severity

CAT I

CCI(s)

Weight

10

Fix Recommendation

If mixed mode is required, document the need and justification; describe the measures taken to ensure the use of Azure SQL Managed Instance authentication is kept to a minimum; describe the measures taken to safeguard passwords; list or describe the SQL logins used; and obtain official approval.

If mixed mode is not required, for each account being managed by SQL MI but not requiring it, drop or disable the SQL Database user. Replace it with an appropriately configured account, as needed.

To drop a user in the SSMS Object Explorer, navigate to Databases >> database >> Security >> Users.

Right-click on the user name and then click "Delete".

To drop a user via a query, change the context to the database_name to be evaluated: DROP USER.

To enable Microsoft Entra-only Authentication, in a PowerShell or Cloud Shell interface, run the statement:

az sql mi ad-only-auth enable --resource-group myresource --name myinstance

OR

Enable-AzSqlInstanceActiveDirectoryOnlyAuthentication -InstanceName myinstance -ResourceGroupName myresource

More information regarding this process is available at the following link:
https://docs.microsoft.com/en-us/azure/azure-sql/database/authentication-azure-ad-only-authentication.

Check Contents

Determine if Azure SQL Managed Instance is configured to use Microsoft Entra ID authentication only.

Only Microsoft Entra ID will be used to authenticate to the server. SQL authentication will be disabled, including SQL Server administrators and users.

In a PowerShell or Cloud Shell interface, run the statement:

az sql mi ad-only-auth get --resource-group myresource --name myinstance

OR

Get-AzSqlInstanceActiveDirectoryOnlyAuthentication -InstanceName myinstance -ResourceGroupName myresource

If the returned value in the "AzureADOnlyAuthentication" column is "True", this is not a finding.

If Mixed mode (both SQL Server authentication and Entra ID authentication) is in use and the need for mixed mode has not been documented and approved, this is a finding.

From the documentation, obtain the list of accounts authorized to be managed by Azure SQL Managed Instance.

Determine the accounts (SQL Logins) actually managed by Azure SQL Managed Instance. Run the statement:

SELECT name FROM sys.database_principals WHERE type_desc = 'SQL_USER' AND authentication_type_desc = 'INSTANCE';

If any accounts listed by the query are not listed in the documentation, this is a finding.

Risk must be accepted by the information system security officer (ISSO)/information system security manager (ISSM).

More information regarding this process is available at: https://docs.microsoft.com/en-us/azure/azure-sql/database/authentication-azure-ad-only-authentication.

Vulnerability Number

V-276225

Documentable

False

Rule Version

MSQL-00-000100

Severity Override Guidance

Determine if Azure SQL Managed Instance is configured to use Microsoft Entra ID authentication only.

Only Microsoft Entra ID will be used to authenticate to the server. SQL authentication will be disabled, including SQL Server administrators and users.

In a PowerShell or Cloud Shell interface, run the statement:

az sql mi ad-only-auth get --resource-group myresource --name myinstance

OR

Get-AzSqlInstanceActiveDirectoryOnlyAuthentication -InstanceName myinstance -ResourceGroupName myresource

If the returned value in the "AzureADOnlyAuthentication" column is "True", this is not a finding.

If Mixed mode (both SQL Server authentication and Entra ID authentication) is in use and the need for mixed mode has not been documented and approved, this is a finding.

From the documentation, obtain the list of accounts authorized to be managed by Azure SQL Managed Instance.

Determine the accounts (SQL Logins) actually managed by Azure SQL Managed Instance. Run the statement:

SELECT name FROM sys.database_principals WHERE type_desc = 'SQL_USER' AND authentication_type_desc = 'INSTANCE';

If any accounts listed by the query are not listed in the documentation, this is a finding.

Risk must be accepted by the information system security officer (ISSO)/information system security manager (ISSM).

More information regarding this process is available at: https://docs.microsoft.com/en-us/azure/azure-sql/database/authentication-azure-ad-only-authentication.

Check Content Reference

M

Target Key

5711