Skip to content

Commit 3448fae

Browse files
committed
restructured to leverage how-to-enable-data-use-governance file
1 parent c91fd43 commit 3448fae

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/purview/how-to-enable-data-use-governance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,10 +58,10 @@ To disable data use governance for a source, resource group, or subscription, a
5858

5959

6060
### Important considerations related to Data use governance
61-
1. Make sure you write down the **Name** you use when registering in Azure Purview. You will need it when you publish a policy. The recommended practice is to make the registered name exactly the same as the endpoint name.
62-
2. To disable a source for *Data use governance*, remove it first from being bound (i.e. published) in any policy.
63-
3. While user needs to have both data source *Owner* and Azure Purview *Data source admin* to enable a source for *Data use governance*, either of those roles can independently disable it.
64-
4. Disabling *Data use governance* for a subscription will disable it also for all assets registered in that subscription.
61+
- Make sure you write down the **Name** you use when registering in Azure Purview. You will need it when you publish a policy. The recommended practice is to make the registered name exactly the same as the endpoint name.
62+
- To disable a source for *Data use governance*, remove it first from being bound (i.e. published) in any policy.
63+
- While user needs to have both data source *Owner* and Azure Purview *Data source admin* to enable a source for *Data use governance*, either of those roles can independently disable it.
64+
- Disabling *Data use governance* for a subscription will disable it also for all assets registered in that subscription.
6565

6666
> [!WARNING]
6767
> **Known issues** related to source registration

0 commit comments

Comments
 (0)