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/core-concepts.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,40 @@ author: pthippeswamy
5
5
ms.service: azure-storage-mover
6
6
ms.topic: overview
7
7
ms.date: 08/01/2025
8
-
ms.author: pthippeswamy
8
+
ms.author: shaas
9
9
---
10
10
11
11
# Azure Storage Discovery concepts
12
12
13
+
The concepts and terminology used throughout this documentation are defined below.
14
+
15
+
### Azure Storage Discovery Workspace (ASDW)
16
+
The Azure Storage Discovery Workspace is the resource used to deploy and manage Storage Discovery in your subscription. It defines the scope of analysis - such as subscriptions or resource groups and once created, it enables visibility into capacity, transactions, and configuration trends across selected storage accounts.
17
+
18
+
### Workspace Root
19
+
Azure Resource Manager (ARM) resource identifiers that define the root-level boundaries of an Azure Storage Discovery Workspace (ASDW). These roots specify the top-level Azure resources - such as subscriptions and/or resource groups - over which the discovery workspace will operate.
20
+
21
+
Example:
22
+
23
+
```json
24
+
"workspaceRoots": [
25
+
"/subscriptions/abc123...",
26
+
"/subscriptions/abc123/resourceGroups/rg1"
27
+
]
28
+
```
29
+
30
+
This configuration means the workspace will monitor storage accounts under the specified subscription and resource group.
31
+
32
+
> [!NOTE]
33
+
> - Users need Reader access on subscriptions or resource groups to add them to workspaceRoots during ASDW deployment.
34
+
35
+
36
+
### Scope
37
+
A Scope in Azure Storage Discovery represents a logical grouping of storage accounts based on user-defined criteria, such as resource tags. Scopes are configured within the boundaries of a workspace and serve as filters to organize and segment data for reporting and insights. By defining scopes, users can tailor their workspace to align with specific business units, workloads, or any segment of their Azure Storage environment they wish to monitor. This enables more targeted visibility and actionable insights across distinct areas of the storage estate. Users have flexibility to define:
38
+
39
+
- A scope without any ARM tags will include all storage accounts within the defined scope
40
+
- A scope with tags enables users to selectively choose specific storage accounts based on Azure tags assigned to the storage accounts.
41
+
13
42
Deploying Azure Storage Discovery workspace in one of your Azure subscriptions is the first step in starting aggregation of storage account metrics. This article discusses the important decisions and best practices for a Storage Discovery deployment.
14
43
15
44
## Select a subscription and region for Azure Storage Discovery workspace deployment
@@ -37,6 +66,7 @@ Storage Discovery is available in two different SKUs or pricing plans.
37
66
| Pricing Plan | Best for | Capacity | Transactions | Configuration | History |
38
67
|---|---|---|---|---|---|
39
68
| Free | Small-scale deployments and evaluation | • Trends<br>• Distributions<br>• Top storage accounts | Not available | • Resource configuration | • Backfill: 15 days<br>• Retention: 15 days |
40
-
| Standard | Production deployments with comprehensive insights | • Trends<br>• Distributions<br>• Top storage accounts | • Trends<br>• Distributions<br>• Top storage accounts | • Resource configuration<br>• Security configuration | • Backfill: 15 days<br>• Retention: 18 months |
69
+
| Standard | Production deployments with comprehensive insights | • Trends<br>• Distributions<br>• Top storage accounts | • Trends<br>• Distributions<br>• Top storage accounts | • Resource configuration<br>• Security configuration | • Backfill: 30 days<sup>1</sup> <br>• Retention: 18 months |
41
70
71
+
<sup>1</sup> Storage Discovery will soon support 6 months of historical data through upcoming backfill enhancements for Standard pricing plan.<br><br>
42
72
Refer [Storage Discovery Pricing page](pricing.md) for more details.
Copy file name to clipboardExpand all lines: articles/storage-discovery/create-workspace.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn how to create an discovery workspace.
5
5
author: pthippeswamy
6
6
ms.service: azure-storage-mover
7
7
ms.topic: how-to
8
-
ms.author: pthippeswamy
8
+
ms.author: shaas
9
9
ms.date: 08/01/2025
10
10
---
11
11
@@ -22,7 +22,7 @@ This article helps you create an ASDW resource.
22
22
Click on **Create**
23
23
24
24
> [!div class="mx-imgBorder"]
25
-
> 
25
+
> 
26
26
27
27
Choose a **Subscription** and **Resource group** to create the discovery workspace
28
28
@@ -46,20 +46,20 @@ WorkspaceRoots specifies the top-level Azure resource identifiers - such as subs
46
46
> - Up to 100 resources - subscriptions and/or resource groups can be included in one ASDW.
47
47
48
48
> [!div class="mx-imgBorder"]
49
-
> 
49
+
> 
50
50
51
51
Once the subscriptions, resource groups or tenant is added to the workspace, an access check is run to verify if the user has Microsoft.Storage/storageAccounts/read on the added resources. As the checks are running, status of the run is as shown:
52
52
53
53
> [!div class="mx-imgBorder"]
54
-
> 
54
+
> 
55
55
56
56
If you do not have Microsoft.Storage/storageAccounts/read on any of the resources added, remove the resource from the workSpaceRoots to proceed with the creation of workspace or resolve the access issue and try again.
57
57
58
58
### Create Scope
59
59
Scopes are logical groupings of storage accounts within the defined workspaceRoots.They allow you to filter and organize data using tags and resource types. Scope enables targeted insights - you can create scopes for different departments, environments, or compliance zones.
60
60
61
61
> [!div class="mx-imgBorder"]
62
-
> 
62
+
> 
63
63
64
64
> [!IMPORTANT]
65
65
> **Default Scope** is added automatically, which would include all storage accounts within the subscriptions or resource groups added in the **workspaceRoots**
@@ -69,15 +69,15 @@ Add tags, if needed on the ASDW resource and click on Review and Create.
69
69
If the access check for the workspaceRoots resources hasn’t finished yet, the Review and Create tab shows a message saying the check is still in progress. You won’t be able to deploy the resource until the check is complete.
70
70
71
71
> [!div class="mx-imgBorder"]
72
-
> 
72
+
> 
73
73
74
74
> [!NOTE]
75
75
> Note that Discovery resource creation fails if the access checks on any added subscription or resource group or tenant is not successful.
76
76
77
77
When the access checks completes successfully, resource can be deployed.
78
78
79
79
> [!div class="mx-imgBorder"]
80
-
> 
80
+
> 
81
81
82
82
> [!NOTE]
83
83
> Note that it will take upto 24 hours for the metrics to start appearing in the Reports after the scope is created.
0 commit comments