Skip to content

Commit f3e47c0

Browse files
committed
Acrolinx round 3
1 parent 7de0003 commit f3e47c0

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/storage-discovery/resource-move.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article describes how to make changes to resource group, subscription, or M
1818
It's important to understand the impact of a resource move on the insights Storage Discovery provides to you.
1919
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.
2020

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.
2222

2323
> [!IMPORTANT]
2424
> 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
3535
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.
3636
When such a storage resource moves, one of two results can occur:
3737

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.
3939
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.
4040

4141
## 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
5252
## Move a storage resource to a different Microsoft Entra tenant
5353

5454
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.
5656

5757
> [!WARNING]
5858
> Storage Discovery can only generate insights for storage resources located in the same tenant as the Discovery workspace.

0 commit comments

Comments
 (0)