Merge pull request #213652 from inward-eye/main

changes in register-scan doc

Author: prmerger-automator[bot]

articles/purview/register-scan-azure-sql-database.md

@@ -361,27 +361,25 @@ Scans can be managed or run again on completion
 ## Access policy
 
 ### Access policy pre-requisites on Azure SQL Database
-[!INCLUDE [Access policies Azure SQL DB pre-requisites](./includes/access-policies-prerequisites-azure-sql-db.md)]
+[!INCLUDE [Access policies specific Azure SQL DB pre-requisites](./includes/access-policies-prerequisites-azure-sql-db.md)]
 
 ### Configuration of Microsoft Purview account for policies
 [!INCLUDE [Access policies generic configuration](./includes/access-policies-configuration-generic.md)]
 
 ### Register the data source and enable Data use management
-The Azure SQL Database resource needs to be registered first with Microsoft Purview before you can create access policies. You can follow these guides:
+The Azure SQL Database resource needs to be registered first with Microsoft Purview before you can create access policies. 
+To register your resources, follow the **Prerequisites** and **Register** sections of this guide:
+[Register Azure SQL Database](./register-scan-azure-sql-database.md#prerequisites)
 
-[Register Azure SQL DB](./register-scan-azure-sql-database.md#register)
+After you've registered the data source, you'll need to enable Data Use Management. This enables access policies on the given Azure SQL server and all its contained databases. Data Use Management can impact the security of your data, as it delegates to certain Microsoft Purview roles managing access to the data sources. **Go through the secure practices related to Data Use Management in this guide**: [How to enable Data Use Management](./how-to-enable-data-use-management.md)
 
-After you've registered the data source, you'll need to enable Data Use Management. This enables access policies on the given Azure SQL server and all its contained databases. Data Use Management can impact the security of your data, as it delegates to certain Microsoft Purview roles to manage access to the data sources. **Go through the secure practices related to Data Use Management in this guide**:
-
-[How to enable Data Use Management](./how-to-enable-data-use-management.md)
-
-Once your data source has the **Data Use Management** option *Enabled*, it will look like this picture.
+Once your data source has the **Data Use Management** option *Enabled*, it will look like this screenshot.
 ![Screenshot shows how to register a data source for policy.](./media/how-to-policies-data-owner-sql/register-data-source-for-policy-azure-sql-db.png)
 
 ### Create a policy
 To create an access policy for Azure SQL Database, follow these guides:
-* [Single SQL account](./how-to-policies-data-owner-azure-sql-db.md#create-and-publish-a-data-owner-policy) - This guide will allow you to provision access on a single Azure SQL Database account in your subscription.
-* [All data sources in a subscription or resource group](./how-to-policies-data-owner-resource-group.md) - This guide will allow you to provision access on all enabled data sources in a resource group, or across an Azure subscription. The pre-requisite is that the subscription or resource group is registered with the Data use management option enabled. 
+* [Data owner policy on a single Azure SQL Database account](./how-to-policies-data-owner-azure-sql-db.md#create-and-publish-a-data-owner-policy) - This guide will allow you to provision access on a single Azure SQL Database account in your subscription.
+* [Data owner policy covering all sources in a subscription or resource group](./how-to-policies-data-owner-resource-group.md) - This guide will allow you to provision access on all enabled data sources in a resource group, or across an Azure subscription. The pre-requisite is that the subscription or resource group is registered with the Data use management option enabled. 
 
 ## Lineage (Preview) 
 <a id="lineagepreview"></a>