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/storage-discovery/resource-move.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
9
9
ms.date: 10/08/2025
10
10
---
11
11
12
-
# Move resources to other resource groups, subscriptions, and Microsoft Entra tenants
12
+
# Move a Storage Discovery workspace or storage resource to other resource groups, subscriptions, and Microsoft Entra tenants
13
13
14
14
This article describes how to make changes to resource group, subscription, or Microsoft Entra tenant for your Azure Storage Discovery workspace resources. It also discusses the effects that moving dependent resource, such as storage accounts, can have on the insights generated by Azure Storage Discovery.
15
15
@@ -35,16 +35,16 @@ Storage Discovery workspace resources can move to different resource groups or s
35
35
Moving a storage resource to a new resource group or subscription in the same Microsoft Entra tenant can move that resource into or out of the scope of a Discovery workspace.
36
36
When such a storage resource moves, one of two results can occur:
37
37
38
-
1. The storage resource moves to a location not covered by the workspace root configuration. In this case, Discovery reports like: `Capacity`, `Activity`, and others start reporting changes. The storage resource and its data volume no longer appear. Such a resource move has the same impact on reports as if the resource is deleted. However, the insights history in your workspace retains these resource insights. As an example, such a move could manifest as a dip in overall used-capacity graph.
39
-
1. The storage resource moves to a new location that is also covered by the root configuration of the same workspace. Such a move also has an impact on the reports of this workspace. For instance, a distribution of capacity by subscription may show a dip for the original subscription and a jump for the subscription the storage resource moved to. It's also important to note that Storage Discovery doesn't change the resource URI in it's historic data. If you're observing insights for the resource before it moves, then those insights stop appearing when the move occurs. Insights for the moved storage resource (now has a different resource ID) begin to appear. That means you can't connect history of this individual storage account resource. A move starts recording new history as if this storage resource was newly created instead of moved.
38
+
- The storage resource moves to a location not covered by the workspace root configuration. In this case, Discovery reports like: `Capacity`, `Activity`, and others start reporting changes. The storage resource and its data volume no longer appear. Such a resource move has the same impact on reports as if the resource is deleted. However, the insights history in your workspace retains these resource insights. As an example, such a move could manifest as a dip in overall used-capacity graph.
39
+
- The storage resource moves to a new location that is also covered by the root configuration of the same workspace. Such a move also has an impact on the reports of this workspace. For instance, a distribution of capacity by subscription may show a dip for the original subscription and a jump for the subscription the storage resource moved to. It's also important to note that Storage Discovery doesn't change the resource URI in it's historic data. If you're observing insights for the resource before it moves, then those insights stop appearing when the move occurs. Insights for the moved storage resource (now has a different resource ID) begin to appear. That means you can't connect history of this individual storage account resource. A move starts recording new history as if this storage resource was newly created instead of moved.
40
40
41
41
## Move a workspace to a different Microsoft Entra tenant
42
42
43
43
Moving a Discovery workspace to a new tenant isn't supported. Tenant moves are accomplished by moving an entire subscription with all its resource groups and resources to another tenant. If a Discovery workspace moves in this way:
44
44
45
-
1. Any explicit Role Based Access Control (RBAC) role assignments are no longer functioning.
46
-
1. The workspace immediately stops aggregating insights about storage resources that are now located in a different tenant.
47
-
1. Insights collected about any storage resources become unavailable and can't be recovered.
45
+
- Any explicit Role Based Access Control (RBAC) role assignments are no longer functioning.
46
+
- The workspace immediately stops aggregating insights about storage resources that are now located in a different tenant.
47
+
- Insights collected about any storage resources become unavailable and can't be recovered.
48
48
49
49
> [!CAUTION]
50
50
> Data loss occurs when you move a Discovery workspace to a different Microsoft Entra tenant. All previously aggregated insights become unavailable and can't be recovered, even if the workspace moves back to the original tenant.
0 commit comments