You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/concept-asset-normalization.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Asset normalization
3
-
description: Learn how Azure Purview prevents duplicate assets in your data map through asset normalization
3
+
description: Learn how Microsoft Purview prevents duplicate assets in your data map through asset normalization
4
4
author: djpmsft
5
5
ms.author: daperlov
6
6
ms.service: purview
@@ -12,13 +12,13 @@ ms.custom: ignite-fall-2021
12
12
13
13
# Asset normalization
14
14
15
-
When ingesting assets into the Azure Purview data map, different sources updating the same data asset may send similar, but slightly different qualified names. While these qualified names represent the same asset, slight differences such as an extra character or different capitalization may cause these assets on the surface to appear different. To avoid storing duplicate entries and causing confusion when consuming the data catalog, Azure Purview applies normalization during ingestion to ensure all fully qualified names of the same entity type are in the same format.
15
+
When ingesting assets into the Microsoft Purview data map, different sources updating the same data asset may send similar, but slightly different qualified names. While these qualified names represent the same asset, slight differences such as an extra character or different capitalization may cause these assets on the surface to appear different. To avoid storing duplicate entries and causing confusion when consuming the data catalog, Microsoft Purview applies normalization during ingestion to ensure all fully qualified names of the same entity type are in the same format.
16
16
17
17
For example, you scan in an Azure Blob with the qualified name `https://myaccount.file.core.windows.net/myshare/folderA/folderB/my-file.parquet`. This blob is also consumed by an Azure Data Factory pipeline which will then add lineage information to the asset. The ADF pipeline may be configured to read the file as `https://myAccount.file.core.windows.net//myshare/folderA/folderB/my-file.parquet`. While the qualified name is different, this ADF pipeline is consuming the same piece of data. Normalization ensures that all the metadata from both Azure Blob Storage and Azure Data Factory is visible on a single asset, `https://myaccount.file.core.windows.net/myshare/folderA/folderB/my-file.parquet`.
18
18
19
19
## Normalization rules
20
20
21
-
Below are the normalization rules applied by Azure Purview.
21
+
Below are the normalization rules applied by Microsoft Purview.
description: This article provides process and best practice guidance to effectively manage the lifecycle of assets in the Azure Purview catalog
2
+
title: Microsoft Purview asset management processes
3
+
description: This article provides process and best practice guidance to effectively manage the lifecycle of assets in the Microsoft Purview catalog
4
4
author: Jubairp
5
5
ms.author: jubairpatel
6
6
ms.service: purview
@@ -10,34 +10,34 @@ ms.date: 01/06/2022
10
10
11
11
# Business processes for managing data effectively
12
12
13
-
As data and content has a lifecycle that requires active management (for example, acquisition - processing - disposal) assets in the Azure Purview data catalog need active management in a similar way. "Assets" in the catalog include the technical metadata that describes collection, lineage and scan information. Metadata describing the business structure of data such as glossary, classifications and ownership also needs to be managed.
13
+
As data and content has a lifecycle that requires active management (for example, acquisition - processing - disposal) assets in the Microsoft Purview data catalog need active management in a similar way. "Assets" in the catalog include the technical metadata that describes collection, lineage and scan information. Metadata describing the business structure of data such as glossary, classifications and ownership also needs to be managed.
14
14
15
15
To manage data assets, responsible people in the organization must understand how and when to apply data governance processes and manage workflows.
16
16
17
-
## Why do you need business processes for managing assets in Azure Purview?
17
+
## Why do you need business processes for managing assets in Microsoft Purview?
18
18
19
-
An organization employing Azure Purview should define processes and people structure to manage the lifecycle of assets and ensure data is valuable to users of the catalog. Metadata in the catalog must be maintained to be able to manage data at scale for discovery, quality, security and privacy.
19
+
An organization employing Microsoft Purview should define processes and people structure to manage the lifecycle of assets and ensure data is valuable to users of the catalog. Metadata in the catalog must be maintained to be able to manage data at scale for discovery, quality, security and privacy.
20
20
21
21
### Benefits
22
22
23
-
- Agreed definition and structure of data is required for the Azure Purview data catalog to provide effective data search and protection functionality at scale across organizations' data estates.
23
+
- Agreed definition and structure of data is required for the Microsoft Purview data catalog to provide effective data search and protection functionality at scale across organizations' data estates.
24
24
25
25
- Defining and using processes for asset lifecycle management is key to maintaining accurate asset metadata, which will improve usability of the catalog and the ability to protect relevant data.
26
26
27
27
- Business users looking for data will be more likely to use the catalog to search for data when it is maintained using data governance processes.
28
28
29
-
### Best practice processes that should be considered when starting the data governance journey with Azure Purview:
29
+
### Best practice processes that should be considered when starting the data governance journey with Microsoft Purview:
30
30
31
31
-**Capture and maintain assets** - Understand how to initially structure and record assets in the catalog for management
32
32
-**Glossary and Classification management** - Understand how to effectively manage the catalog metadata needed to apply and maintain a business glossary
33
-
-**Moving and deleting assets** – Managing collections and assets by understanding how to move assets from one collection to another or delete asset metadata from Azure Purview
33
+
-**Moving and deleting assets** – Managing collections and assets by understanding how to move assets from one collection to another or delete asset metadata from Microsoft Purview
34
34
35
35
## Data curator organizational personas
36
36
37
-
The [Data Curator](catalog-permissions.md) role in Azure Purview controls read/write permission to assets within a collection group. To support the data governance processes, the Data Curator role has been granted to separate data governance personas in the organization:
37
+
The [Data Curator](catalog-permissions.md) role in Microsoft Purview controls read/write permission to assets within a collection group. To support the data governance processes, the Data Curator role has been granted to separate data governance personas in the organization:
38
38
39
39
> [!Note]
40
-
> The 4 **personas** listed are suggested read/write users, and would all be assigned Data Curator role in Azure Purview.
40
+
> The 4 **personas** listed are suggested read/write users, and would all be assigned Data Curator role in Microsoft Purview.
41
41
42
42
- Data Owner or Data Expert:
43
43
@@ -53,33 +53,33 @@ The [Data Curator](catalog-permissions.md) role in Azure Purview controls read/w
53
53
54
54
## 1. Capture and maintain assets
55
55
56
-
This process describes the high-level steps and suggested roles to capture and maintain assets in the Azure Purview data catalog.
56
+
This process describes the high-level steps and suggested roles to capture and maintain assets in the Microsoft Purview data catalog.
57
57
58
58
:::image type="content" source="media/concept-best-practices/assets-capturing-asset-metadata.png" alt-text="Business Process 1 - Capturing and Maintaining Assets."lightbox="media/concept-best-practices/assets-capturing-asset-metadata.png" border="true":::
59
59
60
60
### Process Guidance
61
61
62
62
| Process Step | Guidance |
63
63
| ------------ | -------- |
64
-
| 1 |[Azure Purview collections architecture and best practices](concept-best-practices-collections.md)|
64
+
| 1 |[Microsoft Purview collections architecture and best practices](concept-best-practices-collections.md)|
65
65
| 2 | [How to create and manage collections](how-to-create-and-manage-collections.md)
| 6 | [How to manage multi-cloud data sources](manage-data-sources.md)
69
-
| 7 | [Best practices for scanning data sources in Azure Purview](concept-best-practices-scanning.md)
69
+
| 7 | [Best practices for scanning data sources in Microsoft Purview](concept-best-practices-scanning.md)
70
70
| 8, 9 & 10 | [Search the data catalog](how-to-search-catalog.md) <br> [Browse the data catalog](how-to-browse-catalog.md)
71
71
72
72
## 2. Glossary and classification maintenance
73
73
74
-
This process describes the high-level steps and roles to manage and define the business glossary and classifications metadata to enrich the Azure Purview data catalog.
74
+
This process describes the high-level steps and roles to manage and define the business glossary and classifications metadata to enrich the Microsoft Purview data catalog.
75
75
76
76
:::image type="content" source="media/concept-best-practices/assets-maintaining-glossary-and-classifications.png" alt-text="Business Process 2 - Maintaining glossary and classifications"lightbox="media/concept-best-practices/assets-maintaining-glossary-and-classifications.png" border="true":::
77
77
78
78
### Process Guidance
79
79
80
80
| Process Step | Guidance |
81
81
| ------------ | -------- |
82
-
| 1 & 2 |[Understand Azure Purview access and permissions](catalog-permissions.md)|
82
+
| 1 & 2 |[Understand Microsoft Purview access and permissions](catalog-permissions.md)|
83
83
| 3 | [Create custom classifications and classification rules](create-a-custom-classification-and-classification-rule.md)
84
84
| 4 | [Create a scan rule set](create-a-scan-rule-set.md)
85
85
| 5 & 6 | [Apply classifications to assets](apply-classifications.md)
@@ -89,31 +89,31 @@ This process describes the high-level steps and roles to manage and define the b
89
89
| 12 & 13 | [Browse the Data Catalog](how-to-browse-catalog.md)
90
90
91
91
> [!Note]
92
-
> It is not currently possible to edit glossary term attributes (for example, Status) in bulk using the Azure Purview UI, but it is possible to export the glossary in bulk, edit in Excel and re-import with amendments.
92
+
> It is not currently possible to edit glossary term attributes (for example, Status) in bulk using the Microsoft Purview UI, but it is possible to export the glossary in bulk, edit in Excel and re-import with amendments.
93
93
94
94
## 3. Moving assets between collections
95
95
96
-
This process describes the high-level steps and roles to move assets between collections using the Azure Purview portal.
96
+
This process describes the high-level steps and roles to move assets between collections using the Microsoft Purview portal.
97
97
98
98
:::image type="content" source="media/concept-best-practices/assets-moving-assets-between-collections.png" alt-text="Business Process 3 - Moving assets between collections"lightbox="media/concept-best-practices/assets-moving-assets-between-collections.png" border="true":::
99
99
100
100
### Process Guidance
101
101
102
102
| Process Step | Guidance |
103
103
| ------------ | -------- |
104
-
| 1 & 2 |[Azure Purview collections architecture and best practice](concept-best-practices-collections.md)|
104
+
| 1 & 2 |[Microsoft Purview collections architecture and best practice](concept-best-practices-collections.md)|
105
105
| 3 | [Create a collection](quickstart-create-collection.md)
106
106
| 4 | [Understand access and permissions](catalog-permissions.md)
107
107
| 5 | [How to manage collections](how-to-create-and-manage-collections.md#add-assets-to-collections)
| 7 | [Browse the Azure Purview Catalog](how-to-browse-catalog.md)
109
+
| 7 | [Browse the Microsoft Purview Catalog](how-to-browse-catalog.md)
110
110
111
111
> [!Note]
112
-
> It is not currently possible to bulk move assets from one collection to another using the Azure Purview portal.
112
+
> It is not currently possible to bulk move assets from one collection to another using the Microsoft Purview portal.
113
113
114
114
## 4. Deleting asset metadata
115
115
116
-
This process describes the high-level steps and roles to delete asset metadata from the data catalog using the Azure Purview portal.
116
+
This process describes the high-level steps and roles to delete asset metadata from the data catalog using the Microsoft Purview portal.
117
117
118
118
Asset Metadata may need to be deleted manually for many reasons:
119
119
@@ -125,7 +125,7 @@ Asset Metadata may need to be deleted manually for many reasons:
125
125
> [!Note]
126
126
> Before deleting assets, please refer to the how-to guide to review considerations: [How to delete assets](catalog-asset-details.md#deleting-assets)
127
127
128
-
:::image type="content" source="media/concept-best-practices/assets-deleting-asset-metadata.png" alt-text="Business Process 4 - Deleting Assets in Azure Purview"lightbox="media/concept-best-practices/assets-deleting-asset-metadata.png" border="true":::
128
+
:::image type="content" source="media/concept-best-practices/assets-deleting-asset-metadata.png" alt-text="Business Process 4 - Deleting Assets in Microsoft Purview"lightbox="media/concept-best-practices/assets-deleting-asset-metadata.png" border="true":::
129
129
130
130
### Process Guidance
131
131
@@ -138,12 +138,12 @@ Asset Metadata may need to be deleted manually for many reasons:
138
138
| 6 | [Scanning best practices](concept-best-practices-scanning.md)
139
139
140
140
> [!Note]
141
-
> - Deleting a collection, registered source or scan from Azure Purview does not delete all associated asset metadata.
142
-
> - It is not possible to bulk delete asset metadata using the Azure Purview Portal
141
+
> - Deleting a collection, registered source or scan from Microsoft Purview does not delete all associated asset metadata.
142
+
> - It is not possible to bulk delete asset metadata using the Microsoft Purview Portal
143
143
> - Deleting the asset metadata does not delete all associated lineage or other relationship data (for example, glossary or classification assignments) about the asset from the data map. The asset information and relationships will no longer be visible in the portal.
144
144
145
145
## Next steps
146
-
-[Azure Purview accounts architectures and best practices](concept-best-practices-accounts.md)
147
-
-[Azure Purview collections architectures and best practices](concept-best-practices-collections.md)
148
-
-[Azure Purview glossary best practices](concept-best-practices-glossary.md)
149
-
-[Azure Purview classifications best practices](concept-best-practices-classification.md)
146
+
-[Microsoft Purview accounts architectures and best practices](concept-best-practices-accounts.md)
147
+
-[Microsoft Purview collections architectures and best practices](concept-best-practices-collections.md)
148
+
-[Microsoft Purview glossary best practices](concept-best-practices-glossary.md)
149
+
-[Microsoft Purview classifications best practices](concept-best-practices-classification.md)
0 commit comments