Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra ID – Integrating Microsoft Entra ID identities for access to Azure SQL

Posted on February 25, 2020

Hello, everyone. In today’s article, we’ll explain step by step how to configure Microsoft Entra ID accounts to access a SQL database in Azure. The integration between Microsoft Entra ID and SQL database instances allows for centralization and greater access control over SQL resources hosted in Azure. It’s possible to use credentials replicated to Azure through Microsoft Entra Connect (hybrid) or created directly in Microsoft Entra ID (Microsoft Entra ID-only).

Creating a database

Let’s start by creating a database-type resource in Azure. To do this, search for the SQL databases resource in Azure search or access this link.

In the SQL databases menu, click + Add.

Select the Resource group you want to use to create the database.

In the Database details option, follow the steps below:
1 – In the Database name field, enter the database name.
2 – In the Server field, if you don’t have a SQL server created, click Create new.

To create the new server, enter the information as below:
1 – In the Server name field, enter the server name.
2 – In the Server admin login field, enter the local administrator credential for the SQL server.
3 – Enter the local administrator user’s password.
4 – Confirm the password created.
5 – Select the SQL server location.

Click Review + create.

Click Create.

Configuring the database firewall

With the database created, let’s configure the SQL server firewall to be accessed only by my external IP.

Select the created database and click Set server firewall.

The external IP connected to the Azure portal is captured and displayed in the Client IP Address option. To configure only my external IP, follow the steps below:
1 – In the Allow Azure services and resources to access this server option, select ON.
2 – Enter the rule name.
3 – Enter the start IP. For illustration purposes, I’ll configure only one external IP for access to the SQL server.
4 – Enter the same IP as in step 3.
5 – Click Save.

Confirm the configuration by clicking OK.

Configuring the AD user as DB admin

To configure the Azure administrator user for the SQL server, access the SQL Servers menu in Azure or click this link.

Click the server you created to host your database.

Select the Active Directory Admin menu.

Click the Set admin option.

Let’s select the user chrystal@ulyneves.com for this illustration. It’s possible to use groups to centralize administrators of the selected SQL server.

Click Save.

Connecting to the SQL database

Let’s connect to the database using Visual Studio. If you haven’t installed it, access this link to download it.

With Visual Studio installed, let’s connect to Azure with the credential we granted access to the SQL server resource with in the previous step. Follow the steps below:
1 – Select Server Explorer.
2 – Right-click the Azure icon.
3 – Select Connect to Microsoft Azure Subscription…

Enter the credentials of the account that received access to the SQL server resource in Azure.

With the SQL administrator authenticated in Azure, let’s connect to the database by selecting the connect to database option, as below:

Select the options below:
1 – As Data Source, select the Microsoft SQL Server option.
2 – Click Continue.

To configure the connection to the database, perform the steps below:
1 – Enter the SQL server address in Azure.
2 – Select the Active Directory Password Authentication option.
3 – Enter the Azure user credential.
4 – Enter the user’s password.
5 – Select the database.
6 – Click OK.

Creating a table in the database

Let’s create a table in the Ulysses-DB database. Right-click the database we connected to in the previous step.

Select New Query.

Let’s create a table by entering the command below and clicking Run.

In the image below, we can see that the table was created successfully.

Validating the table created in the database

Now let’s validate the table creation through the Azure portal.

In the database menu, select the Query editor (preview) option.

Let’s connect using the local administrator credential we created at the beginning of this article by performing the steps below:
1 – Enter the local administrator credential.
2 – Enter the password.
3 – Click OK.

Expanding the Tables menu, we can see the TestUlysses table created.

Summary

In today’s article, we explained step by step how to configure a Microsoft Entra ID identity with administrative access to a SQL database resource in Azure.

During the illustration we performed the following steps:

  • We created a SQL server in Azure
  • We created a SQL database in Azure
  • We configured the firewall rules on the database
  • We configured admin permission for the user chrystal@ulyneves.com
  • We connected to the database using the Microsoft Entra ID credential
  • We created a table using Visual Studio
  • We validated the table created in the database through the Azure portal.

I hope this content has helped enrich your knowledge of Azure.

Did you like the post?

Like it and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra ID topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}