Skip to content

Commit c15ed68

Browse files
Merge pull request #238030 from barclayn/2023-may-freshness
freshness work
2 parents ee39ec3 + 761ef1c commit c15ed68

File tree

7 files changed

+19
-18
lines changed

7 files changed

+19
-18
lines changed
Loading

articles/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: msi
1010
ms.topic: how-to
1111
ms.workload: identity
12-
ms.date: 03/08/2022
12+
ms.date: 05/10/2023
1313
ms.author: barclayn
1414
ms.custom: devx-track-azurecli
1515
zone_pivot_groups: identity-mi-methods
@@ -57,7 +57,7 @@ To list or read a user-assigned managed identity, your account needs to have eit
5757
1. Sign in to the [Azure portal](https://portal.azure.com).
5858
1. In the search box, enter **Managed Identities**. Under **Services**, select **Managed Identities**.
5959
1. A list of the user-assigned managed identities for your subscription is returned. To see the details of a user-assigned managed identity, select its name.
60-
1. You can now view the details about the managed identity as shown in the image below.
60+
1. You can now view the details about the managed identity as shown in the image.
6161

6262
:::image type="content" source="media/how-manage-user-assigned-managed-identities/list-user-assigned-managed-identity-portal.png" alt-text="Screenshot that shows the list of user-assigned managed identity.":::
6363

@@ -76,7 +76,7 @@ Deleting a user-assigned identity doesn't remove it from the VM or resource it w
7676

7777
## Manage access to user-assigned managed identities
7878

79-
In some environments, administrators choose to limit who can manage user-assigned managed identities. You do this by using [built-in](../../role-based-access-control/built-in-roles.md#identity) RBAC roles. You can use these roles to grant a user or group in your organization rights over a user-assigned managed identity.
79+
In some environments, administrators choose to limit who can manage user-assigned managed identities. Administrators can implement this limitation using [built-in](../../role-based-access-control/built-in-roles.md#identity) RBAC roles. You can use these roles to grant a user or group in your organization rights over a user-assigned managed identity.
8080

8181
1. Sign in to the [Azure portal](https://portal.azure.com).
8282
1. In the search box, enter **Managed Identities**. Under **Services**, select **Managed Identities**.

articles/active-directory/managed-identities-azure-resources/how-to-use-vm-token.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.subservice: msi
1212
ms.topic: how-to
1313
ms.tgt_pltfrm: na
1414
ms.workload: identity
15-
ms.date: 02/18/2022
15+
ms.date: 05/15/2023
1616
ms.author: barclayn
1717
ms.collection: M365-identity-device-management
1818
---
@@ -36,7 +36,7 @@ If you plan to use the Azure PowerShell examples in this article, be sure to ins
3636
> - All sample code/script in this article assumes the client is running on a virtual machine with managed identities for Azure resources. Use the virtual machine "Connect" feature in the Azure portal, to remotely connect to your VM. For details on enabling managed identities for Azure resources on a VM, see [Configure managed identities for Azure resources on a VM using the Azure portal](qs-configure-portal-windows-vm.md), or one of the variant articles (using PowerShell, CLI, a template, or an Azure SDK).
3737
3838
> [!IMPORTANT]
39-
> - The security boundary of managed identities for Azure resources, is the resource it's being used on. All code/scripts running on a virtual machine can request and retrieve tokens for any managed identities available on it.
39+
> - The security boundary of managed identities for Azure resources, is the resource where the identity is used. All code/scripts running on a virtual machine can request and retrieve tokens for any managed identities available on it.
4040
4141
## Overview
4242

@@ -145,8 +145,10 @@ For .NET applications and functions, the simplest way to work with managed ident
145145

146146
To learn more about Microsoft.Azure.Services.AppAuthentication and the operations it exposes, see the [Microsoft.Azure.Services.AppAuthentication reference](/dotnet/api/overview/azure/service-to-service-authentication) and the [App Service and KeyVault with managed identities for Azure resources .NET sample](https://github.com/Azure-Samples/app-service-msi-keyvault-dotnet).
147147
148+
148149
## Get a token using C#
149150

151+
150152
```csharp
151153
using System;
152154
using System.Collections.Generic;
@@ -395,7 +397,7 @@ This section documents the possible error responses. A "200 OK" status is a succ
395397

396398
It's recommended to retry if you receive a 404, 429, or 5xx error code (see [Error handling](#error-handling) above). If you receive a 410 error, it indicates that IMDS is going through updates and will be available in a maximum of 70 seconds.
397399

398-
Throttling limits apply to the number of calls made to the IMDS endpoint. When the throttling threshold is exceeded, IMDS endpoint limits any further requests while the throttle is in effect. During this period, the IMDS endpoint will return the HTTP status code 429 ("Too many requests"), and the requests fail.
400+
Throttling limits apply to the number of calls made to the IMDS endpoint. When the throttling threshold is exceeded, IMDS endpoint limits any further requests while the throttle is in effect. During this period, the IMDS endpoint returns the HTTP status code 429 ("Too many requests"), and the requests fail.
399401

400402
For retry, we recommend the following strategy:
401403

articles/active-directory/managed-identities-azure-resources/managed-identities-status.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: List of services supporting managed identities
44
services: active-directory
55
author: barclayn
66
ms.author: barclayn
7-
ms.date: 05/10/2023
7+
ms.date: 05/25/2023
88
ms.topic: conceptual
99
ms.service: active-directory
1010
ms.subservice: msi

articles/active-directory/managed-identities-azure-resources/qs-configure-powershell-windows-vm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.subservice: msi
99
ms.topic: quickstart
1010
ms.tgt_pltfrm: na
1111
ms.workload: identity
12-
ms.date: 06/24/2022
12+
ms.date: 05/10/2023
1313
ms.author: barclayn
1414
ms.collection: M365-identity-device-management
1515
ms.custom: devx-track-azurepowershell, mode-api
@@ -35,7 +35,7 @@ In this article, using PowerShell, you learn how to perform the following manage
3535

3636
## System-assigned managed identity
3737

38-
In this section, you'll learn how to enable and disable the system-assigned managed identity using Azure PowerShell.
38+
In this section, we go over how to enable and disable the system-assigned managed identity using Azure PowerShell.
3939

4040
### Enable system-assigned managed identity during creation of an Azure VM
4141

@@ -151,7 +151,7 @@ To assign a user-assigned identity to a VM, your account needs the [Virtual Mach
151151

152152
To remove a user-assigned identity to a VM, your account needs the [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor) role assignment.
153153

154-
If your VM has multiple user-assigned managed identities, you can remove all but the last one using the following commands. Be sure to replace the `<RESOURCE GROUP>` and `<VM NAME>` parameter values with your own values. The `<USER ASSIGNED IDENTITY NAME>` is the user-assigned managed identity's name property, which should remain on the VM. This information can be found by querying the `Identity` property of the VM object. For example, `$vm.Identity`:
154+
If your VM has multiple user-assigned managed identities, you can remove all but the last one using the following commands. Be sure to replace the `<RESOURCE GROUP>` and `<VM NAME>` parameter values with your own values. The `<USER ASSIGNED IDENTITY NAME>` is the user-assigned managed identity's name property, which should remain on the VM. This information is discoverable using a query to search for the `Identity` property of the VM object. For example, `$vm.Identity`:
155155

156156
```azurepowershell-interactive
157157
$vm = Get-AzVm -ResourceGroupName myResourceGroup -Name myVm

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,12 @@ documentationcenter: ''
66
author: barclayn
77
manager: amycolannino
88
editor: daveba
9-
109
ms.service: active-directory
1110
ms.subservice: msi
1211
ms.topic: tutorial
1312
ms.tgt_pltfrm: na
1413
ms.workload: identity
15-
ms.date: 02/18/2022
14+
ms.date: 05/25/2023
1615
ms.author: barclayn
1716
ms.collection: M365-identity-device-management
1817
#Customer intent: As a developer or administrator I want to configure a Windows virtual machine to retrieve a secret from key vault using a managed identity and have a simple way to validate my configuration before using it for development

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,12 @@ ms.subservice: msi
1111
ms.topic: tutorial
1212
ms.tgt_pltfrm: na
1313
ms.workload: identity
14-
ms.date: 01/11/2022
14+
ms.date: 05/25/2023
1515
ms.author: barclayn
1616
ms.collection: M365-identity-device-management
1717
---
1818
# Tutorial: Use a Windows VM system-assigned managed identity to access Azure SQL
1919

20-
[!INCLUDE [preview-notice](../../../includes/active-directory-msi-preview-notice.md)]
2120

2221
This tutorial shows you how to use a system-assigned identity for a Windows virtual machine (VM) to access Azure SQL Database. Managed Service Identities are automatically managed by Azure and enable you to authenticate to services that support Azure AD authentication, without needing to insert credentials into your code. You learn how to:
2322

@@ -50,20 +49,21 @@ There are two steps to granting your VM access to a database:
5049
**To [configure Azure AD authentication](/azure/azure-sql/database/authentication-aad-configure):**
5150

5251
1. In the Azure portal, select **SQL servers** from the left-hand navigation.
53-
2. Click the SQL server to be enabled for Azure AD authentication.
52+
2. Select the SQL server to be enabled for Azure AD authentication.
5453
3. In the **Settings** section of the blade, click **Active Directory admin**.
5554
4. In the command bar, click **Set admin**.
5655
5. Select an Azure AD user account to be made an administrator of the server, and click **Select.**
5756
6. In the command bar, click **Save.**
5857

58+
5959
### Create contained user
6060

6161
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](/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:
6262

6363
- [Universal Authentication with SQL Database and Azure Synapse Analytics (SSMS support for MFA)](/azure/azure-sql/database/authentication-mfa-ssms-overview)
6464
- [Configure and manage Azure Active Directory authentication with SQL Database or Azure Synapse Analytics](/azure/azure-sql/database/authentication-aad-configure)
6565

66-
SQL DB requires unique Azure AD display names. With this, the Azure AD accounts such as users, groups and Service Principals (applications), and VM names enabled for managed identity must be uniquely defined in Azure AD regarding their display names. SQL DB checks the Azure AD display name during T-SQL creation of such users and if it is not unique, the command fails requesting to provide a unique Azure AD display name for a given account.
66+
SQL DB requires unique Azure AD display names. With this, the Azure AD accounts such as users, groups and Service Principals (applications), and VM names enabled for managed identity must be uniquely defined in Azure AD regarding their display names. SQL DB checks the Azure AD display name during T-SQL creation of such users and if it isn't unique, the command fails requesting to provide a unique Azure AD display name for a given account.
6767

6868
**To create a contained user:**
6969

@@ -75,7 +75,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
7575
6. In the **Connect to database** field, enter the name of the non-system database you want to configure.
7676
7. Click **Connect**. Complete the sign-in process.
7777
8. In the **Object Explorer**, expand the **Databases** folder.
78-
9. Right-click on a user database and click **New query**.
78+
9. Right-click on a user database and select **New query**.
7979
10. In the query window, enter the following line, and click **Execute** in the toolbar:
8080

8181
> [!NOTE]
@@ -89,7 +89,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
8989
11. Clear the query window, enter the following line, and click **Execute** in the toolbar:
9090
9191
> [!NOTE]
92-
> `VMName` in the following command is the name of the VM that you enabled system assigned identity on in the prerequsites section.
92+
> `VMName` in the following command is the name of the VM that you enabled system assigned identity on in the prerequisites section.
9393
9494
```sql
9595
ALTER ROLE db_datareader ADD MEMBER [VMName]

0 commit comments

Comments
 (0)