Skip to content

Commit d3d729f

Browse files
Merge pull request #268763 from anaharris-ms/relocate-mg-ident
Relocation: Managed Identities
2 parents d3521e3 + 247d859 commit d3d729f

File tree

3 files changed

+57
-3
lines changed

3 files changed

+57
-3
lines changed

articles/operational-excellence/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,10 @@
2828
href: relocation-log-analytics.md
2929
- name: Azure Private Link Service
3030
href: relocation-private-link.md
31-
- name: Storage Account
31+
- name: Azure Storage Account
3232
href: relocation-storage-account.md
33+
- name: Managed identities for Azure resources
34+
href: relocation-managed-identity.md
3335
- name: Strategic services
3436
items:
3537
- name: Azure Automation

articles/operational-excellence/overview-relocation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,8 +55,8 @@ The following tables provide links to each Azure service relocation document. Th
5555
[Azure Monitor - Log Analytics](./relocation-log-analytics.md)| ❌ | ✅| ❌ |
5656
[Azure Database for PostgreSQL](./relocation-postgresql-flexible-server.md)| ✅ | ✅| ❌ |
5757
[Azure Private Link Service](./relocation-private-link.md) | ❌ | ✅| ❌ |
58-
[Storage Account](relocation-storage-account.md)| ✅ | ✅| ❌ |
59-
58+
[Azure Storage Account](relocation-storage-account.md)| ✅ | ✅| ❌ |
59+
[Managed identities for Azure resources](relocation-storage-account.md)| ❌ | ✅| ❌ |
6060

6161

6262
### ![An icon that signifies this service is strategic.](./media/relocation/icon-strategic.svg) Strategic services
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Relocation guidance for managed identities for Azure resources
3+
description: Learn how to relocate managed identities for Azure resources to a new region.
4+
author: anaharris-ms
5+
ms.author: barclayn
6+
ms.date: 03/14/2024
7+
ms.service: entra-id
8+
ms.subservice: managed-identities
9+
ms.topic: concept
10+
ms.custom:
11+
- subject-relocation
12+
#CustomerIntent: As a cloud architect/engineer, I want to learn how to relocate managed identities for Azure resources to another region.
13+
---
14+
15+
# Relocate managed identities for Azure resources to another region
16+
17+
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.
18+
19+
Moving user-assigned managed identities across Azure regions isn't supported. You can however, recreate a user-assigned managed identity in the target region.
20+
21+
## Prerequisites
22+
23+
Managed identities for Azure resources is a feature of Azure Entra ID. Each of the Azure services that support managed identities for Azure resources is subject to its own timeline.
24+
25+
- Make sure that you review the [availability status of managed identities for your resource](/entra/identity/managed-identities-azure-resources/managed-identities-status)
26+
- Understand [known issues with managed identities for Azure resources](/entra/identity/managed-identities-azure-resources/known-issues).
27+
- Create a dependency map with the Azure services that are used by the managed identity you wish to move. For the services that are in scope of a relocation, you must [select the appropriate relocation strategy](overview-relocation.md).
28+
29+
- Permissions to list permissions granted to existing user-assigned managed identity.
30+
- Permissions to grant a new user-assigned managed identity the required permissions.
31+
- Permissions to assign a new user-assigned identity to the Azure resources.
32+
- Permissions to edit Group membership, if your user-assigned managed identity is a member of one or more groups.
33+
34+
## Prepare and move
35+
36+
1. Copy user-assigned managed identity assigned permissions. You can list [Azure role assignments](/azure/role-based-access-control/role-assignments-list-powershell) but that may not be enough depending on how permissions were granted to the user-assigned managed identity. You should confirm that your solution doesn't depend on permissions granted using a service specific option.
37+
1. Create a [new user-assigned managed identity](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-powershell#create-a-user-assigned-managed-identity-2) at the target region.
38+
1. Grant the managed identity the same permissions as the original identity that it's replacing, including Group membership. You can review [Assign Azure roles to a managed identity](/azure/role-based-access-control/role-assignments-portal-managed-identity), and [Group membership](/entra/fundamentals/groups-view-azure-portal).
39+
1. Specify the new identity in the properties of the resource instance that uses the newly created user assigned managed identity.
40+
41+
## Verify
42+
43+
After reconfiguring your service to use your new managed identities in the target region, you must confirm that all operations have been restored.
44+
45+
## Clean up
46+
47+
Once that you confirm your service is back online, you can proceed to delete any resources in the source region that you no longer use.
48+
49+
## Next steps
50+
51+
52+
- [Manage user-assigned managed identities](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-powershell#delete-a-user-assigned-managed-identity-2)

0 commit comments

Comments
 (0)