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
+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
@@ -18,7 +18,7 @@ This article describes how to make changes to resource group, subscription, or M
18
18
It's important to understand the impact of a resource move on the insights Storage Discovery provides to you.
19
19
Storage Discovery aggregates information about different storage resources and presents them as insights in a Discovery workspace resource. Which storage resources are in scope is defined in the workspace resource itself.
20
20
21
-
Moving either the Discovery workspace or the storage resources to different resource groups or subscriptions is supported. In this article, you'll find important aspects worth considering.
21
+
Moving either the Discovery workspace or the storage resources to different resource groups or subscriptions is supported. In this article, you find important aspects worth considering.
22
22
23
23
> [!IMPORTANT]
24
24
> The Storage Discovery workspace resource and all storage resources, such as storage accounts it generates insights for, must reside in the same Microsoft Entra tenant.
@@ -35,7 +35,7 @@ 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 appears. 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.
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
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.
40
40
41
41
## Move a workspace to a different Microsoft Entra tenant
@@ -52,7 +52,7 @@ Moving a Discovery workspace to a new tenant isn't supported. Tenant moves are a
52
52
## Move a storage resource to a different Microsoft Entra tenant
53
53
54
54
This scenario is comparable with a storage resource moving out of the bounds of a workspace root configuration.
55
-
The storage resource leaves to a location not covered by the workspace root configuration. In this case, the impacts on your insights are changes to Discovery reports like: `Capacity`, `Activity`, and others. The storage resource and its data volume no longer appears. However, insights remain in the history of your workspace. As an example, such a move could manifest as a dip in an overall used-capacity graph.
55
+
The storage resource leaves to a location not covered by the workspace root configuration. In this case, the impacts on your insights are changes to Discovery reports like: `Capacity`, `Activity`, and others. The storage resource and its data volume no longer appear. However, insights remain in the history of your workspace. As an example, such a move could manifest as a dip in an overall used-capacity graph.
56
56
57
57
> [!WARNING]
58
58
> Storage Discovery can only generate insights for storage resources located in the same tenant as the Discovery workspace.
0 commit comments