Skip to content

Commit fda563f

Browse files
Merge pull request #213644 from inward-eye/main
changes in register-scan doc
2 parents a92429e + 04c2218 commit fda563f

File tree

1 file changed

+22
-3
lines changed

1 file changed

+22
-3
lines changed

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

Lines changed: 22 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: athenads
55
ms.author: athenadsouza
66
ms.service: purview
77
ms.topic: how-to
8-
ms.date: 04/26/2022
8+
ms.date: 10/04/2022
99
ms.custom: template-how-to, ignite-fall-2021
1010
---
1111
# Connect to Azure SQL Database in Microsoft Purview
@@ -360,9 +360,28 @@ Scans can be managed or run again on completion
360360
361361
## Access policy
362362
363+
### Access policy pre-requisites on Azure SQL Database
364+
[!INCLUDE [Access policies Azure SQL DB pre-requisites](./includes/access-policies-prerequisites-azure-sql-db.md)]
365+
366+
### Configuration of Microsoft Purview account for policies
367+
[!INCLUDE [Access policies generic configuration](./includes/access-policies-configuration-generic.md)]
368+
369+
### Register the data source and enable Data use management
370+
The Azure SQL Database resource needs to be registered first with Microsoft Purview before you can create access policies. You can follow these guides:
371+
372+
[Register Azure SQL DB](./register-scan-azure-sql-database.md#register)
373+
374+
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**:
375+
376+
[How to enable Data Use Management](./how-to-enable-data-use-management.md)
377+
378+
Once your data source has the **Data Use Management** option *Enabled*, it will look like this picture.
379+
![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)
380+
381+
### Create a policy
363382
To create an access policy for Azure SQL Database, follow these guides:
364-
* [Single SQL account](./how-to-policies-data-owner-azure-sql-db.md) - This guide will allow you to enable access policies on a single Azure SQL Database account in your subscription.
365-
* [All data sources in a subscription or resource group](./how-to-policies-data-owner-resource-group.md) - This guide will allow you to enable access policies on all enabled and available sources in a resource group, or across an Azure subscription.
383+
* [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.
384+
* [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.
366385
367386
## Lineage (Preview)
368387
<a id="lineagepreview"></a>

0 commit comments

Comments
 (0)