Removal and renaming of a file

Author: pthippeswamy

articles/storage-discovery/TOC.yml

@@ -8,8 +8,6 @@ items:
   expanded: true
 - name: Concepts
   items:
-  - name: Core concepts
-    href: core-concepts.md 
   - name: Management components
     href: management-components.md
   - name: Planning for deployment

articles/storage-discovery/core-concepts.md

@@ -1,64 +1,70 @@
 ---
-title: Understanding the Azure Storage Discovery management components
-description: Understanding the Azure Storage Discovery management components
+title: Planning for Storage Discovery deployment | Microsoft Docs
+titleSuffix: Azure Storage Discovery
+description: Storage Discovery provides insights on storage capacity, transactions, and configurations - providing visibility into your storage estate at entire organization level and aiding business decisions.
 author: fauhse
-ms.author: fauhse
 ms.service: azure-storage-discovery
-ms.topic: conceptual
+ms.topic: overview
 ms.date: 08/01/2025
+ms.author: fauhse
+ms.custom: references_regions
 ---
 
-# Understanding the Azure Storage Discovery management components
+# Azure Storage Discovery concepts
 
-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.
+The concepts and terminology used throughout this documentation are defined below.
 
-:::image type="content" source="media/management-components/discovery-components.png" alt-text="An image showing the Storage Discovery management resources further described in this article." lightbox="media/management-components/discovery-components.png":::
+## Key concepts
 
-## Workspace
+### Azure Storage Discovery workspace 
+The Azure Storage Discovery workspace (ASDW) 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 storage accounts within the selected "scope".
 
-A storage discovery workspace is the name of the top-level service resource that you deploy in a resource group of your choice. All aspects of the service are controlled from this resource. In most cases, deploying a single storage discovery workspace is sufficient for even the largest cloud estate.
+### Workspace Root
+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.
 
-You're better able to manage your data if all resources find their home in the same storage discovery workspace.
+Example:
 
-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.
+```json
+"workspaceRoots": [
+  "/subscriptions/ffff5f5f-aa6a-bb7b-cc8c-dddddd9d9d9d",
+  "/subscriptions/ffff5f5f-aa6a-bb7b-cc8c-dddddd9d9d9d/resourceGroups/myResourceGroup"
+]
+```
 
-:::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":::
+This configuration means the workspace will monitor storage accounts under the specified subscription and resource group.
 
-## Root
+> [!NOTE]
+> - Users need Reader access on subscriptions or resource groups to add them to workspace roots during Discovery workspace deployment.
 
-The workspace root consists of 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.
 
-> [!TIP]
-> The proximity and network quality between your subscriptions and resource groups in Azure determine aggregation velocity in early stages of your discovery. The region of the storage discovery workspace you've deployed doesn't play a role for performance.
+### Scope 
+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:
 
-## Scope
+- A scope without any ARM tags will include all storage accounts within the defined scope
+- A scope with tags enables users to selectively choose specific storage accounts based on Azure tags assigned to the storage accounts.
 
-A Scope represents a logical grouping of storage accounts in Azure 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.
+Deploying Azure Storage Discovery workspace in one of your Azure subscriptions is the first step in starting aggregation of storage account metrics.
 
+## Select a subscription and region for Azure Storage Discovery workspace deployment
 
-Users have flexibility to define:
+Azure Storage Discovery workspace can be deployed in a subscription of your choice and in one of the supported regions.  
+[!INCLUDE [control-plane-regions](includes/control-plane-regions.md)]
 
-- A scope without any ARM tags will include all storage accounts within the defined scope.
-- A scope with specific ARM tags will only include storage accounts that match those tags.
-- A scope with a combination of ARM tags and resource groups will include storage accounts that match the tags within the specified resource groups.
-- A scope with a combination of ARM tags and subscriptions will include storage accounts that match the tags within the specified subscriptions.
-- A scope with a combination of ARM tags, resource groups, and subscriptions will include storage accounts that match the tags within the specified resource groups and subscriptions.
-- A scope with a combination of ARM tags, resource groups, subscriptions, and regions will include storage accounts that match the tags within the specified resource groups, subscriptions, and regions.
-- A scope with a combination of ARM tags, resource groups, subscriptions, regions, and storage account types will include storage accounts that match the tags within the specified resource groups, subscriptions, regions, and storage account types.
-- A scope with a combination of ARM tags, resource groups, subscriptions, regions, storage account types, and storage account names will include storage accounts that match the tags within the specified resource groups, subscriptions, regions, storage account types, and storage account names.
-- A scope with a combination of ARM tags, resource groups, subscriptions, regions, storage account types, storage account names, and storage account locations will include storage accounts that match the tags within the specified resource groups, subscriptions, regions, storage account types, storage account names, and storage account locations.
-- A scope with a combination of ARM tags, resource groups, subscriptions, regions, storage account types, storage account names, storage account locations, and storage account access tiers will include storage accounts that match the tags within the specified resource groups, subscriptions, regions, storage account types, storage account names, storage account locations, and storage account access tiers.
-- A scope with a combination of ARM tags, resource groups, subscriptions, regions, storage account types, storage account names, storage account locations, storage account access tiers, and storage account replication types will include storage accounts that match the tags within the specified resource groups, subscriptions, regions, storage account types, storage account names, storage account locations, storage account access tiers, and storage account replication types.
+Once a discovery workspace is created in a specific region, it can aggregate metrics from storage accounts located across a broader set of supported regions, irrespective of the region in which the discovery workspace itself resides.
+[!INCLUDE [data-plane-regions](includes/data-plane-regions.md)]
 
+## Permissions
 
-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.
+To deploy a Discovery Workspace, user must have following access:
 
-> [!TIP]
-> You can optionally add a description to your workspace. A description can help to keep track of additional information for your workspace.
+| Scenario | Minimal RBAC role assignments needed |
+|---|---| 
+| To deploy Discovery workspace | Contributor access on the subscription or the resource group| 
+| To include the subscription or resource groups in a Discovery workspace as part of *workspaceRoots* | Microsoft.Storage/storageAccounts/read access on the subscription or resource group | 
+| To view Discovery reports | Reader access on the Discovery workspace |
 
-## Next steps
+## Azure Storage Discovery pricing plans
 
-After understanding the resources involved in an Azure Storage Mover deployment, it's a good idea to start a proof-of-concept deployment. These articles are good, next reads:
+Storage Discovery is available in two different SKUs or pricing plans.
 
-- [Plan your Storage Discovery deployment.](deployment-planning.md)
-- [Deploy a storage discovery workspace in your subscription.](create-workspace.md)
+[!INCLUDE [pricing-plan-differentiation](includes/pricing-plan-differentiation.md)]