# Ensure that Microsoft Entra Admin is Configured for SQL Servers

- Source: https://support.icompaas.com/support/solutions/articles/62000229874-ensure-that-microsoft-entra-admin-is-configured-for-sql-servers
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

Microsoft Entra admin (formerly Azure AD admin) allows Azure SQL servers to use Microsoft Entra ID authentication. This enables centralized identity management, MFA, Conditional Access, group-based access, and eliminates reliance on SQL-only authentication.

  

Rationale:

Configuring a Microsoft Entra admin strengthens security by enabling MFA, reducing SQL password logins, and allowing centralized, controlled access. Without it, SQL servers rely on less secure SQL authentication.

  

Impact:

Enabling a Microsoft Entra admin does not break SQL logins but enables Entra authentication. If you choose the optional setting "Support only Microsoft Entra authentication", SQL logins will be disabled — use this only if ready.

  

Default Value:

By default, SQL servers show: Admin name: No Microsoft Entra admin

  

Pre-requisites:

-   You must have Owner, Contributor, or SQL Server Contributor access.
    
-   The admin you choose must be a valid Microsoft Entra user or group.
    

  

Test Plan:

1.  Sign in to the Azure portal  [https://portal.azure.com](https://portal.azure.com/)
    
2.  In the portal, search for SQL servers. Select the target SQL server.
    
3.  Under Settings, click Microsoft Entra ID.
    
4.  Under the Microsoft Entra admin, look at the Admin name.
    
5.  Confirm that it does not display “No Microsoft Entra admin.”
    

![](https://support.icompaas.com/assets/kb/58af824dda7b9cd0.png)

6.  If it shows “No Microsoft Entra admin,” then follow the implementation plan.
    

Implementation Plan:

1.  Sign in to the Azure portal [https://portal.azure.com](https://portal.azure.com/)
    
2.  In the portal, search for SQL servers and select the SQL server.
    

![](https://support.icompaas.com/assets/kb/24de354407ae3bbc.png)

3.  Under Settings, select Microsoft Entra ID. Click Set admin.
    

![](https://support.icompaas.com/assets/kb/e2f1a6009e8d74da.png)

4.  Choose the Entra user or group you want to assign as the admin.
    
5.  Click Save.
    

  

Backout Plan:

1.  Sign in to the Azure portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  In the portal, search for SQL servers and select the server.
    
3.  Open Microsoft Entra ID under Settings.
    
4.  Click Remove admin.
    
5.  Click Save to apply the rollback.
    

Reference:

-   [https://learn.microsoft.com/azure/azure-sql/database/authentication-aad-configure](https://learn.microsoft.com/azure/azure-sql/database/authentication-aad-configure)
    
-   [https://learn.microsoft.com/entra](https://learn.microsoft.com/entra)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
