You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.subservice: msi
10
10
ms.topic: how-to
11
11
ms.workload: identity
12
-
ms.date: 03/08/2022
12
+
ms.date: 05/10/2023
13
13
ms.author: barclayn
14
14
ms.custom: devx-track-azurecli
15
15
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
57
57
1. Sign in to the [Azure portal](https://portal.azure.com).
58
58
1. In the search box, enter **Managed Identities**. Under **Services**, select **Managed Identities**.
59
59
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.
61
61
62
62
:::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.":::
63
63
@@ -76,7 +76,7 @@ Deleting a user-assigned identity doesn't remove it from the VM or resource it w
76
76
77
77
## Manage access to user-assigned managed identities
78
78
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.
80
80
81
81
1. Sign in to the [Azure portal](https://portal.azure.com).
82
82
1. In the search box, enter **Managed Identities**. Under **Services**, select **Managed Identities**.
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/how-to-use-vm-token.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.subservice: msi
12
12
ms.topic: how-to
13
13
ms.tgt_pltfrm: na
14
14
ms.workload: identity
15
-
ms.date: 02/18/2022
15
+
ms.date: 05/15/2023
16
16
ms.author: barclayn
17
17
ms.collection: M365-identity-device-management
18
18
---
@@ -36,7 +36,7 @@ If you plan to use the Azure PowerShell examples in this article, be sure to ins
36
36
> - 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).
37
37
38
38
> [!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.
40
40
41
41
## Overview
42
42
@@ -145,8 +145,10 @@ For .NET applications and functions, the simplest way to work with managed ident
@@ -395,7 +397,7 @@ This section documents the possible error responses. A "200 OK" status is a succ
395
397
396
398
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.
397
399
398
-
ThrottlinglimitsapplytothenumberofcallsmadetotheIMDSendpoint. Whenthethrottlingthresholdisexceeded, IMDSendpointlimitsanyfurtherrequestswhilethethrottleisineffect. Duringthisperiod, theIMDSendpointwillreturntheHTTPstatuscode429 ("Too many requests"), andtherequestsfail.
400
+
ThrottlinglimitsapplytothenumberofcallsmadetotheIMDSendpoint. Whenthethrottlingthresholdisexceeded, IMDSendpointlimitsanyfurtherrequestswhilethethrottleisineffect. Duringthisperiod, theIMDSendpointreturnstheHTTPstatuscode429 ("Too many requests"), andtherequestsfail.
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/qs-configure-powershell-windows-vm.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.subservice: msi
9
9
ms.topic: quickstart
10
10
ms.tgt_pltfrm: na
11
11
ms.workload: identity
12
-
ms.date: 06/24/2022
12
+
ms.date: 05/10/2023
13
13
ms.author: barclayn
14
14
ms.collection: M365-identity-device-management
15
15
ms.custom: devx-track-azurepowershell, mode-api
@@ -35,7 +35,7 @@ In this article, using PowerShell, you learn how to perform the following manage
35
35
36
36
## System-assigned managed identity
37
37
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.
39
39
40
40
### Enable system-assigned managed identity during creation of an Azure VM
41
41
@@ -151,7 +151,7 @@ To assign a user-assigned identity to a VM, your account needs the [Virtual Mach
151
151
152
152
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.
153
153
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`:
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,12 @@ documentationcenter: ''
6
6
author: barclayn
7
7
manager: amycolannino
8
8
editor: daveba
9
-
10
9
ms.service: active-directory
11
10
ms.subservice: msi
12
11
ms.topic: tutorial
13
12
ms.tgt_pltfrm: na
14
13
ms.workload: identity
15
-
ms.date: 02/18/2022
14
+
ms.date: 05/25/2023
16
15
ms.author: barclayn
17
16
ms.collection: M365-identity-device-management
18
17
#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
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:
23
22
@@ -50,20 +49,21 @@ There are two steps to granting your VM access to a database:
50
49
**To [configure Azure AD authentication](/azure/azure-sql/database/authentication-aad-configure):**
51
50
52
51
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.
54
53
3. In the **Settings** section of the blade, click **Active Directory admin**.
55
54
4. In the command bar, click **Set admin**.
56
55
5. Select an Azure AD user account to be made an administrator of the server, and click **Select.**
57
56
6. In the command bar, click **Save.**
58
57
58
+
59
59
### Create contained user
60
60
61
61
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:
62
62
63
63
-[Universal Authentication with SQL Database and Azure Synapse Analytics (SSMS support for MFA)](/azure/azure-sql/database/authentication-mfa-ssms-overview)
64
64
-[Configure and manage Azure Active Directory authentication with SQL Database or Azure Synapse Analytics](/azure/azure-sql/database/authentication-aad-configure)
65
65
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.
67
67
68
68
**To create a contained user:**
69
69
@@ -75,7 +75,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
75
75
6. In the **Connect to database** field, enter the name of the non-system database you want to configure.
76
76
7. Click **Connect**. Complete the sign-in process.
77
77
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**.
79
79
10. In the query window, enter the following line, and click **Execute** in the toolbar:
80
80
81
81
> [!NOTE]
@@ -89,7 +89,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
89
89
11. Clear the query window, enter the following line, and click **Execute** in the toolbar:
90
90
91
91
> [!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.
0 commit comments