Skip to content

Commit d78b920

Browse files
authored
Merge pull request #100746 from MarkusVi/arturo20204
arturo20204
2 parents b0e3581 + 797793c commit d78b920

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-sql.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.devlang: na
1313
ms.topic: tutorial
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
16-
ms.date: 10/16/2019
16+
ms.date: 01/10/2020
1717
ms.author: markvi
1818
ms.collection: M365-identity-device-management
1919
---
@@ -33,7 +33,7 @@ This tutorial shows you how to use a system-assigned identity for a Windows virt
3333

3434
[!INCLUDE [msi-tut-prereqs](../../../includes/active-directory-msi-tut-prereqs.md)]
3535

36-
## Grant your VM access to a database in an Azure SQL server
36+
## Grant access
3737

3838
To grant your VM access to a database in an Azure SQL Server, you can use an existing SQL server or create a new one. To create a new server and database using the Azure portal, follow this [Azure SQL quickstart](https://docs.microsoft.com/azure/sql-database/sql-database-get-started-portal). There are also quickstarts that use the Azure CLI and Azure PowerShell in the [Azure SQL documentation](https://docs.microsoft.com/azure/sql-database/).
3939

@@ -42,7 +42,7 @@ There are two steps to granting your VM access to a database:
4242
1. Enable Azure AD authentication for the SQL server.
4343
2. Create a **contained user** in the database that represents the VM's system-assigned identity.
4444

45-
## Enable Azure AD authentication for the SQL server
45+
## Enable Azure AD authentication
4646

4747
[Configure Azure AD authentication for the SQL server](/azure/sql-database/sql-database-aad-authentication-configure) using the following steps:
4848

@@ -53,9 +53,9 @@ There are two steps to granting your VM access to a database:
5353
5. Select an Azure AD user account to be made an administrator of the server, and click **Select.**
5454
6. In the command bar, click **Save.**
5555

56-
## Create a contained user in the database that represents the VM's system assigned identity
56+
## Create user
5757

58-
For this next step, you will need [Microsoft SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms) (SSMS). Before beginning, it may also be helpful to review the following articles for background on Azure AD integration:
58+
This section shows how to create a contained user in the database that represents the VM's system assigned identity. For this step, you need [Microsoft SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms) (SSMS). Before beginning, it may also be helpful to review the following articles for background on Azure AD integration:
5959

6060
- [Universal Authentication with SQL Database and SQL Data Warehouse (SSMS support for MFA)](/azure/sql-database/sql-database-ssms-mfa-authentication)
6161
- [Configure and manage Azure Active Directory authentication with SQL Database or SQL Data Warehouse](/azure/sql-database/sql-database-aad-authentication-configure)
@@ -94,9 +94,9 @@ SQL DB requires unique AAD display names. With this, the AAD accounts such as us
9494
9595
Code running in the VM can now get a token using its system-assigned managed identity and use the token to authenticate to the SQL server.
9696
97-
## Get an access token using the VM's system-assigned managed identity and use it to call Azure SQL
97+
## Get an access token
9898
99-
Azure SQL natively supports Azure AD authentication, so it can directly accept access tokens obtained using managed identities for Azure resources. You use the **access token** method of creating a connection to SQL. This is part of Azure SQL's integration with Azure AD, and is different from supplying credentials on the connection string.
99+
This section shows how to get an access token using the VM's system-assigned managed identity and use it to call Azure SQL. Azure SQL natively supports Azure AD authentication, so it can directly accept access tokens obtained using managed identities for Azure resources. You use the **access token** method of creating a connection to SQL. This is part of Azure SQL's integration with Azure AD, and is different from supplying credentials on the connection string.
100100
101101
Here's a .NET code example of opening a connection to SQL using an access token. This code must run on the VM to be able to access the VM's system-assigned managed identity's endpoint. **.NET Framework 4.6** or higher or **.NET Core 2.2** or higher is required to use the access token method. Replace the values of AZURE-SQL-SERVERNAME and DATABASE accordingly. Note the resource ID for Azure SQL is `https://database.windows.net/`.
102102

0 commit comments

Comments
 (0)