Skip to content

Commit 1d32a67

Browse files
authored
Merge pull request #100747 from MarkusVi/arturo20205
arturo20205
2 parents d78b920 + d16b269 commit 1d32a67

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 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: 11/20/2017
16+
ms.date: 01/10/2020
1717
ms.author: markvi
1818
ms.collection: M365-identity-device-management
1919
---
@@ -35,9 +35,9 @@ You learn how to:
3535

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

38-
## Grant your VM access to a Secret stored in a Key Vault 
38+
## Grant access  
3939

40-
Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication.  However, not all Azure services support Azure AD authentication. To use managed identities for Azure resources with those services, store the service credentials in Azure Key Vault, and use the VM's managed identity to access Key Vault to retrieve the credentials. 
40+
This section shows how to grant your VM access to a Secret stored in a Key Vault. Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication.  However, not all Azure services support Azure AD authentication. To use managed identities for Azure resources with those services, store the service credentials in Azure Key Vault, and use the VM's managed identity to access Key Vault to retrieve the credentials. 
4141

4242
First, we need to create a Key Vault and grant our VM’s system-assigned managed identity access to the Key Vault.   
4343

@@ -62,9 +62,9 @@ Next, add a secret to the Key Vault, so that later you can retrieve the secret u
6262
5. Leave the activation date and expiration date clear, and leave **Enabled** as **Yes**
6363
6. Click **Create** to create the secret. 
6464

65-
## Get an access token using the VM identity and use it to retrieve the secret from the Key Vault  
65+
## Get an access token  
6666

67-
If you don’t have PowerShell 4.3.1 or greater installed, you'll need to [download and install the latest version](https://docs.microsoft.com/powershell/azure/overview).
67+
This section shows how to get an access token using the VM identity and use it to retrieve the secret from the Key Vault. If you don’t have PowerShell 4.3.1 or greater installed, you'll need to [download and install the latest version](https://docs.microsoft.com/powershell/azure/overview).
6868

6969
First, we use the VM’s system-assigned managed identity to get an access token to authenticate to Key Vault:
7070

0 commit comments

Comments
 (0)