Merge pull request #231555 from whhender/update-share-include

Adding storage configuration include

Author: v-shils

articles/purview/how-to-receive-share.md

@@ -6,6 +6,7 @@ ms.author: sidontha
 ms.service: purview
 ms.subservice: purview-data-share
 ms.topic: how-to
+ms.custom: references_regions
 ms.date: 02/16/2023
 ---
 # Receive Azure Storage in-place share with Microsoft Purview Data Sharing (preview)
@@ -51,17 +52,12 @@ Microsoft Purview Data Sharing supports in-place data sharing from Azure Data La
     ```
     The *RegistrationState* should be **Registered**. It could take 15 minutes to 1 hour for registration to complete. For more information, see the [register preview feature article](../azure-resource-manager/management/preview-features.md?tabs=azure-portal#register-preview-feature).
 
+[!INCLUDE [share-storage-configuration](includes/share-storage-configuration.md)]
+
 * A target storage account **created after** the registration step is completed. **The target storage account must be in the same Azure region as the source storage account.** If you don't know the Azure region of the source storage account, you can find out during the share attaching step later in the process. Target storage account can be in a different Azure region from your Microsoft Purview account.
 
     > [!IMPORTANT]
     > The target storage account must be in the same Azure region as the source storage account.
-
-    > [!NOTE]
-    > The following are supported storage account configurations:
-    >
-    > - Azure regions: Canada Central, Canada East, UK South, UK West, Australia East, Japan East, Korea South, and South Africa North 
-    > - Performance: Standard
-    > - Redundancy options: LRS, GRS, RA-GRS
  
 * You need the **Contributor** or **Owner** or **Storage Blob Data Owner** or **Storage Blob Data Contributor** role on the target storage account. You can find more details on the [ADLS Gen2](register-scan-adls-gen2.md#data-sharing) or [Blob storage](register-scan-azure-blob-storage-source.md#data-sharing) data source pages.
 * If the target storage account is in a different Azure subscription than the one for Microsoft Purview account, the Microsoft.Purview resource provider needs to be registered in the Azure subscription where the Storage account is located. It's automatically registered at the time of share consumer attaching the share and if the user has permission to do the `/register/action` operation and therefore, Contributor or Owner roles to the subscription where the Storage account is located. 

articles/purview/how-to-share-data.md

@@ -52,14 +52,9 @@ Microsoft Purview Data Sharing supports in-place data sharing from Azure Data La
     ```
     The *RegistrationState* should be **Registered**. It could take 15 minutes to 1 hour for registration to complete. For more information, see [Register preview feature](../azure-resource-manager/management/preview-features.md?tabs=azure-portal#register-preview-feature).
 
-* A source storage account **created after the registration step is completed**. Source storage account can be in a different Azure region from your Microsoft Purview account, but needs to follow these configurations:
-
-    > [!NOTE]
-    > The following are supported storage account configurations:
-    >
-    > - Azure regions: Canada Central, Canada East, UK South, UK West, Australia East, Japan East, Korea South, and South Africa North 
-    > - Performance: Standard
-    > - Redundancy options: LRS, GRS, RA-GRS
+[!INCLUDE [share-storage-configuration](includes/share-storage-configuration.md)]
+
+* A source storage account **created after the registration step is completed**. Source storage account can be in a different Azure region from your Microsoft Purview account, but needs to follow the available configurations.
 
 * You need the **Owner** or **Storage Blob Data Owner** role on the source storage account to be able to share data. You can find more details on the [ADLS Gen2](register-scan-adls-gen2.md#data-sharing) or [Blob storage](register-scan-azure-blob-storage-source.md#data-sharing) data source page.
 

articles/purview/includes/data-share-quickstart-prerequisites.md

@@ -38,15 +38,9 @@ ms.date: 02/16/2023
     ```
     The *RegistrationState* should be **Registered**. It could take 15 minutes to 1 hour for registration to complete. For more information, see [Register preview feature](../../azure-resource-manager/management/preview-features.md?tabs=azure-portal#register-preview-feature).
 
-* Source and target storage accounts **created after** the registration step is completed. **Both storage accounts must be in the same Azure region as each other**. Both storage accounts need to be ADLS Gen2 or Blob Storage accounts. Your storage accounts can be in a different Azure region from your Microsoft Purview account.
-
-    > [!NOTE]
-    > The following are supported storage account configurations:
-    >
-    > - Azure regions: Canada Central, Canada East, UK South, UK West, Australia East, Japan East, Korea South, and South Africa North 
-    > - Performance: Standard
-    > - Redundancy options: LRS, GRS, RA-GRS
+[!INCLUDE [share-storage-configuration](share-storage-configuration.md)]
 
+* Source and target storage accounts **created after** the registration step is completed. **Both storage accounts must be in the same Azure region as each other**. Both storage accounts need to be ADLS Gen2 or Blob Storage accounts. Your storage accounts can be in a different Azure region from your Microsoft Purview account.
 * Latest version of the storage SDK, PowerShell, CLI and Azure Storage Explorer. Storage REST API version must be February 2020 or later.
 * The storage accounts need to be registered in the collections where you'll send or receive the share. If you're using one Microsoft Purview account, this can be two different collections, or the same collection. For instructions to register, see the [ADLS Gen2](../register-scan-adls-gen2.md) or [Blob storage](../register-scan-azure-blob-storage-source.md) data source pages.
 * If the source or target storage accounts are in a different Azure subscription than the one for Microsoft Purview account, the Microsoft.Purview resource provider is automatically registered in the Azure subscription where the data store is located at the time of share provider adding an asset or share consumer mapping an asset and **ONLY** if the user has permission to do the /register/action operation for the resource provider. The permission is included in the Contributor and Owner roles.

articles/purview/includes/share-storage-configuration.md

@@ -0,0 +1,18 @@
+---
+title: Share Storage Configuration
+description: Include file for the supported storage account configurations for Data Sharing in Microsoft Purview.
+services: purview
+author: whhender
+ms.author: whhender
+ms.service: purview
+ms.topic: include
+ms.custom: include file, references_regions
+ms.date: 03/21/23
+---
+
+> [!NOTE]
+> The following are supported storage account configurations:
+>
+> - Azure regions: Canada Central, Canada East, UK South, UK West, Australia East, Japan East, Korea South, and South Africa North 
+> - Performance: Standard
+> - Redundancy options: LRS, GRS, RA-GRS