Skip to content

Commit 6a368b0

Browse files
committed
Adding images to avoide getting called out by the publishing team
1 parent e6844c5 commit 6a368b0

File tree

3 files changed

+3
-5
lines changed

3 files changed

+3
-5
lines changed

articles/storage-discovery/management-components.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,7 @@ ms.date: 08/01/2025
1212

1313
Several Azure resources are involved in a Storage Discovery deployment. This article describes each of these resources, their uses, and best practices for expressing your migration needs with them.
1414

15-
> [!NOTE]
16-
> An image goes here.
15+
:::image type="content" source="media/management-components/managements-components.png" alt-text="An image showing the Storage Discovery management resources further described in this article." lightbox="media/management-components/management-components.png":::
1716

1817
## Workspace
1918

@@ -23,8 +22,7 @@ You're better able to manage your data if all resources find their home in the s
2322

2423
When you deploy the workspace, your subscription is registered with the *Microsoft.StorageDiscovery* resource provider. You also assign the region in which control messages and metadata about your cloud estate is stored. The Storage Discovery workspace itself isn't directly responsible for aggregating your storage insights. Instead, the dingsbum sends them directly to the reporting interface Azure Storage. Because the dingsbum performs most the work, the proximity between storage account and the dingsbum is more important for performance than your storage discovery workspace's location.
2524

26-
> [!NOTE]
27-
> An image goes here.
25+
:::image type="content" source="media/management-components/discovery-components.png" alt-text="An image showing the Storage Discovery Azure resources further described in this article." lightbox="media/management-components/discovery-components.png":::
2826

2927
## Root
3028

@@ -54,7 +52,7 @@ Users have flexibility to define:
5452

5553
...ad nauseam.
5654

57-
Grouping sources into a scoppe doesn't mean you have to analyze all of them in parallel. You have control over what to aggregate and when to aggregate it. The remaining sections in this article describe more resources that allow for such fine-grained control.
55+
Grouping sources into a scope doesn't mean you have to analyze all of them in parallel. You have control over what to aggregate and when to aggregate it. The remaining sections in this article describe more resources that allow for such fine-grained control.
5856

5957
> [!TIP]
6058
> You can optionally add a description to your workspace. A description can help to keep track of additional information for your workspace.
104 KB
Loading
104 KB
Loading

0 commit comments

Comments
 (0)