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
There are situations in which you'd want to move your existing user-assigned managed identities from one region to another. For example, you may need to move a solution that uses user-assigned managed identities to another region. You may also want to move an existing identity to another region as part of disaster recovery planning, and testing.
22
22
23
-
Moving User-assigned managed identities across Azure regions is not supported. You can however, recreate a user-assigned managed identity in the target region.
23
+
Moving User-assigned managed identities across Azure regions isn't supported. You can however, recreate a user-assigned managed identity in the target region.
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vmss.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.subservice: msi
11
11
ms.topic: quickstart
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: identity
14
-
ms.date: 01/11/2022
14
+
ms.date: 05/25/2023
15
15
ms.author: barclayn
16
16
ms.collection: M365-identity-device-management
17
17
ms.custom: mode-api, devx-track-azurecli
@@ -25,6 +25,7 @@ ms.devlang: azurecli
25
25
Managed identities for Azure resources provide Azure services with an automatically managed identity in Azure Active Directory. You can use this identity to authenticate to any service that supports Azure AD authentication, without having credentials in your code.
26
26
27
27
In this article, you learn how to perform the following managed identities for Azure resources operations on an Azure virtual machine scale set, using the Azure CLI:
28
+
28
29
- Enable and disable the system-assigned managed identity on an Azure virtual machine scale set
29
30
- Add and remove a user-assigned managed identity on an Azure virtual machine scale set
30
31
@@ -169,13 +170,13 @@ This section walks you through creation of a virtual machine scale set and assig
169
170
170
171
### Remove a user-assigned managed identity from an Azure virtual machine scale set
171
172
172
-
To [remove](/cli/azure/vmss/identity#az-vmss-identity-remove) a user-assigned managed identity from a virtual machine scale set use `az vmss identity remove`. If this is the only user-assigned managed identity assigned to the virtual machine scale set, `UserAssigned` will be removed from the identity type value. Be sure to replace the `<RESOURCE GROUP>` and `<VIRTUAL MACHINE SCALE SET NAME>` parameter values with your own values. The `<USER ASSIGNED IDENTITY>` will be the user-assigned managed identity's `name` property, which can be found in the identity section of the virtual machine scale set using `az vmss identity show`:
173
+
To [remove](/cli/azure/vmss/identity#az-vmss-identity-remove) a user-assigned managed identity from a virtual machine scale set use `az vmss identity remove`. If this is the only user-assigned managed identity assigned to the virtual machine scale set, `UserAssigned` is removed from the identity type value. Be sure to replace the `<RESOURCE GROUP>` and `<VIRTUAL MACHINE SCALE SET NAME>` parameter values with your own values. The `<USER ASSIGNED IDENTITY>` is the user-assigned managed identity's `name` property, which can be found in the identity section of the virtual machine scale set using `az vmss identity show`:
173
174
174
175
```azurecli-interactive
175
176
az vmss identity remove -g <RESOURCE GROUP> -n <VIRTUAL MACHINE SCALE SET NAME> --identities <USER ASSIGNED IDENTITY>
176
177
```
177
178
178
-
If your virtual machine scale set does not have a system-assigned managed identity and you want to remove all user-assigned managed identities from it, use the following command:
179
+
If your virtual machine scale set doesn't have a system-assigned managed identity and you want to remove all user-assigned managed identities from it, use the following command:
179
180
180
181
> [!NOTE]
181
182
> The value `none` is case sensitive. It must be lowercase.
Managed identities for Azure resources provide Azure services with an automatically managed system identity in Azure Active Directory. You can use this identity to authenticate to any service that supports Azure AD authentication, without having credentials in your code.
26
24
27
25
In this article, using CURL to make calls to the Azure Resource Manager REST endpoint, you learn how to perform the following managed identities for Azure resources operations on a virtual machine scale set:
This quickstart shows you how to use a system-assigned identity for a Linux virtual machine (VM) to access the Azure Resource Manager API. Managed identities for Azure resources 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.
24
+
This quickstart shows you how to use a system-assigned managed identity as a Linux virtual machine (VM)'s identity to access the Azure Resource Manager API. Managed identities for Azure resources 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.
25
25
You learn how to:
26
26
27
27
> [!div class="checklist"]
@@ -30,14 +30,14 @@ You learn how to:
30
30
31
31
## Prerequisites
32
32
33
-
- An understanding of Managed identities. If you're not familiar with the managed identities for Azure resources feature, see this [overview](overview.md).
33
+
- An understanding of Managed identities. If you're not familiar with managed identities, see this [overview](overview.md).
34
34
- An Azure account, [sign up for a free account](https://azure.microsoft.com/free/).
35
35
- You also need a Linux Virtual machine that has system assigned managed identities enabled. If you have a VM but need to enable [system assigned managed identities](qs-configure-portal-windows-vm.md) you can do it in the identity section of the virtual machine's properties.
36
36
- If you need to create a virtual machine for this tutorial, you can follow the article titled [Create a Linux virtual machine with the Azure portal](../../virtual-machines/linux/quick-create-portal.md#create-virtual-machine)
37
37
38
38
## Grant access
39
39
40
-
Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication. The Azure Resource Manager API supports Azure AD authentication. First, we need to grant this VM's identity access to a resource in Azure Resource Manager, in this case, the Resource Group in which the VM is contained.
40
+
When you use managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication. The Azure Resource Manager API supports Azure AD authentication. First, we need to grant this VM's identity access to a resource in Azure Resource Manager, in this case, the Resource Group in which the VM is contained.
41
41
42
42
1. Sign in to the [Azure portal](https://portal.azure.com) with your administrator account.
43
43
1. Navigate to the tab for **Resource Groups**.
@@ -54,7 +54,7 @@ Using managed identities for Azure resources, your code can get access tokens to
54
54
55
55
## Get an access token using the VM's system-assigned managed identity and use it to call Resource Manager
56
56
57
-
To complete these steps, you'll need an SSH client. If you're using Windows, you can use the SSH client in the [Windows Subsystem for Linux](/windows/wsl/about). If you need assistance configuring your SSH client's keys, see [How to Use SSH keys with Windows on Azure](../../virtual-machines/linux/ssh-from-windows.md), or [How to create and use an SSH public and private key pair for Linux VMs in Azure](../../virtual-machines/linux/mac-create-ssh-keys.md).
57
+
To complete these steps, you need an SSH client. If you're using Windows, you can use the SSH client in the [Windows Subsystem for Linux](/windows/wsl/about). If you need assistance configuring your SSH client's keys, see [How to Use SSH keys with Windows on Azure](../../virtual-machines/linux/ssh-from-windows.md), or [How to create and use an SSH public and private key pair for Linux VMs in Azure](../../virtual-machines/linux/mac-create-ssh-keys.md).
58
58
59
59
1. In the portal, navigate to your Linux VM and in the **Overview**, select **Connect**.
60
60
2.**Connect** to the VM with the SSH client of your choice.
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-datalake.md
+4-4Lines changed: 4 additions & 4 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: tutorial
13
13
ms.tgt_pltfrm: na
14
14
ms.workload: identity
15
-
ms.date: 01/11/2022
15
+
ms.date: 05/25/2023
16
16
ms.author: barclayn
17
17
ms.collection: M365-identity-device-management
18
18
---
@@ -43,12 +43,12 @@ In Data Lake Store, create a new folder and grant our Linux VM system-assigned m
43
43
2. Select the Data Lake Store instance that you want to use.
44
44
3. Select **Data Explorer** on the command bar.
45
45
4. The root folder of the Data Lake Store instance is selected. Select **Access** on the command bar.
46
-
5. Select **Add**. In the **Select** box, enter the name of your VM--for example, **DevTestVM**. Select your VM from the search results, and then click**Select**.
47
-
6.Click**Select Permissions**. Select **Read** and **Execute**, add to **This folder**, and add as **An access permission only**. Select **Ok**. The permission should be added successfully.
46
+
5. Select **Add**. In the **Select** box, enter the name of your VM--for example, **DevTestVM**. Select your VM from the search results, and then select**Select**.
47
+
6.Select**Select Permissions**. Select **Read** and **Execute**, add to **This folder**, and add as **An access permission only**. Select **Ok**. The permission should be added successfully.
48
48
7. Close the **Access** pane.
49
49
8. For this tutorial, create a new folder. Select **New Folder** on the command bar, and give the new folder a name--for example **TestFolder**. Select **Ok**.
50
50
9. Select the folder that you created, and then select **Access** on the command bar.
51
-
10. Similar to step 5, select **Add**. In the **Select** box, enter the name of your VM. Select your VM from the search results, and then click**Select**.
51
+
10. Similar to step 5, select **Add**. In the **Select** box, enter the name of your VM. Select your VM from the search results, and then select**Select**.
52
52
11. Similar to step 6, select **Select Permissions**. Select **Read**, **Write**, and **Execute**, add to **This folder**, and add as **An access permission entry and a default permission entry**. Select **Ok**. The permission should be added successfully.
53
53
54
54
Managed identities for Azure resources can now perform all operations on files in the folder that you created. For more information on managing access to Data Lake Store, see [Access Control in Data Lake Store](../../data-lake-store/data-lake-store-access-control.md).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments