Azure SQL Managed Instance must separate user functionality (including user interface services) from database management functionality.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-276250	SRG-APP-000211-DB-000122	MSQL-00-008900	SV-276250r1150065_rule	2025-10-07	1

Description
Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding Azure SQL Managed Instance management is presented on an interface available for users, information on Azure SQL Managed Instance settings may be inadvertently made available to the user.

Description

Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding Azure SQL Managed Instance management is presented on an interface available for users, information on Azure SQL Managed Instance settings may be inadvertently made available to the user.

ℹ️ Check
To validate Azure role-based access controls (RBAC) for a specific resource, use the PowerShell script below: $ManagedInstanceName = '<ManagedInstanceName>' $SqlMI = Get-AzSqlInstance -Name $ManagedInstanceName Get-AzRoleAssignment -Scope $SqlMI.Id \| Select-Object DisplayName,SignInName,RoleDefinitionName,ObjectType If a user not assigned information system management responsibilities has membership in any of the following roles, this is a finding: - SQL Managed Instance. - Contributor. - SQL Security Manager. - SqlMI Migration Role. - User Access Administrator. - Owner. - Reader. - Role Based Access Control. - Administrator.

ℹ️ Check

To validate Azure role-based access controls (RBAC) for a specific resource, use the PowerShell script below: $ManagedInstanceName = '<ManagedInstanceName>' $SqlMI = Get-AzSqlInstance -Name $ManagedInstanceName Get-AzRoleAssignment -Scope $SqlMI.Id | Select-Object DisplayName,SignInName,RoleDefinitionName,ObjectType If a user not assigned information system management responsibilities has membership in any of the following roles, this is a finding: - SQL Managed Instance. - Contributor. - SQL Security Manager. - SqlMI Migration Role. - User Access Administrator. - Owner. - Reader. - Role Based Access Control. - Administrator.

✔️ Fix
To remove an Azure RBAC role assignment, use the Remove-AzRoleAssignment PowerShell command. Example command: $userPrincipalName = 'Fourth.Coffee@contoso.onmicrosoft.us' $RoleDefinitionName = 'SQL Managed Instance Contributor' $ResourceGroupName ='stigtestingrg' $ResourceName ='fourthcoffeemi' $userObjectId =(Get-AzAdUser -UserPrincipalName $userPrincipalName).Id $ResourceID =(Get-AzSqlInstance -ResourceGroupName $ResourceGroupName -Name $ManagedInstanceName).Id Remove-AzRoleAssignment -Scope $ResourceID -RoleDefinitionName $RoleDefinitionName -ObjectId $userObjectId

✔️ Fix

To remove an Azure RBAC role assignment, use the Remove-AzRoleAssignment PowerShell command. Example command: $userPrincipalName = 'Fourth.Coffee@contoso.onmicrosoft.us' $RoleDefinitionName = 'SQL Managed Instance Contributor' $ResourceGroupName ='stigtestingrg' $ResourceName ='fourthcoffeemi' $userObjectId =(Get-AzAdUser -UserPrincipalName $userPrincipalName).Id $ResourceID =(Get-AzSqlInstance -ResourceGroupName $ResourceGroupName -Name $ManagedInstanceName).Id Remove-AzRoleAssignment -Scope $ResourceID -RoleDefinitionName $RoleDefinitionName -ObjectId $userObjectId