Skip to content

Commit 3021be2

Browse files
Merge pull request #212470 from v-amallick/Sept-26-2022-vault
Move Backup vault GA updates
2 parents f1fb65b + 1ccf40c commit 3021be2

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

articles/backup/backup-vault-overview.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Overview of Backup vaults
33
description: An overview of Backup vaults.
44
ms.topic: conceptual
5-
ms.date: 02/14/2022
5+
ms.date: 09/26/2022
66
ms.custom: references_regions
77
author: v-amallick
88
ms.service: backup
@@ -120,7 +120,7 @@ In the **Backup Instances** tile, you get a summarized view of all backup instan
120120

121121
![Backup jobs](./media/backup-vault-overview/backup-jobs.png)
122122

123-
## Move a Backup vault across Azure subscriptions/resource groups (Public Preview)
123+
## Move a Backup vault across Azure subscriptions/resource groups
124124

125125
This section explains how to move a Backup vault (configured for Azure Backup) across Azure subscriptions and resource groups using the Azure portal.
126126

@@ -241,7 +241,13 @@ Troubleshoot the following common issues you might encounter during Backup vault
241241

242242
**Cause**: Resource move for Backup vault is currently not supported in the selected Azure region.
243243

244-
**Recommendation**: Ensure that you've selected one of the supported regions to move Backup vaults. See [Supported regions](#supported-regions).
244+
**Recommendation**: Ensure that you've selected one of the supported regions to move Backup vaults. See [Supported regions](#supported-regions
245+
246+
#### UserErrorCrossTenantMSIMoveNotSupported
247+
248+
**Cause**: This error occurs if the subscription with which resource is associated has moved to a different Tenant, but the Managed Identity is still associated with the old Tenant.
249+
250+
**Recommendation**: Remove the Managed Identity from the existing Tenant; move the resource and add it again to the new one.
245251

246252
## Next steps
247253

0 commit comments

Comments
 (0)