Skip to content

Commit 5429d5a

Browse files
committed
Language updates
1 parent 137e6dd commit 5429d5a

File tree

1 file changed

+23
-23
lines changed

1 file changed

+23
-23
lines changed

articles/purview/reference-azure-purview-glossary.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
11
---
2-
title: Microsoft Purview product glossary
3-
description: A glossary defining the terminology used throughout Microsoft Purview
2+
title: Microsoft Purview governance portal product glossary
3+
description: A glossary defining the terminology used throughout the Microsoft Purview governance portal
44
author: djpmsft
55
ms.author: daperlov
66
ms.service: purview
77
ms.custom: event-tier1-build-2022
88
ms.topic: conceptual
99
ms.date: 05/27/2022
1010
---
11-
# Microsoft Purview product glossary
11+
# Microsoft Purview governance portal product glossary
1212

13-
Below is a glossary of terminology used throughout Microsoft Purview.
13+
Below is a glossary of terminology used throughout the Microsoft Purview governance portal, and documentation.
1414

1515
## Advanced resource sets
16-
A set of features activated at the Microsoft Purview instance level that, when enabled, enrich resource set assets by computing additional aggregations on the metadata to provide information such as partition counts, total size, and schema counts. Resource set pattern rules are also included.
16+
A set of features activated at the Microsoft Purview instance level that, when enabled, enrich resource set assets by computing extra aggregations on the metadata to provide information such as partition counts, total size, and schema counts. Resource set pattern rules are also included.
1717
## Annotation
18-
Information that is associated with data assets in Microsoft Purview, for example, glossary terms and classifications. After they are applied, annotations can be used within Search to aid in the discovery of the data assets.
18+
Information that is associated with data assets in the Microsoft Purview Data Map, for example, glossary terms and classifications. After they're applied, annotations can be used within Search to aid in the discovery of the data assets.
1919
## Approved
2020
The state given to any request that has been accepted as satisfactory by the designated individual or group who has authority to change the state of the request.
2121
## Asset
@@ -27,7 +27,7 @@ A cloud solution that supports labeling of documents and emails to classify and
2727
## Business glossary
2828
A searchable list of specialized terms that an organization uses to describe key business words and their definitions. Using a business glossary can provide consistent data usage across the organization.
2929
## Capacity unit
30-
A measure of data map usage. All Microsoft Purview data maps include one capacity unit by default, which provides up to 2GB of metadata storage and has a throughput of 25 data map operations/second.
30+
A measure of data map usage. All Microsoft Purview Data Maps include one capacity unit by default, which provides up to 2 GB of metadata storage and has a throughput of 25 data map operations/second.
3131
## Classification report
3232
A report that shows key classification details about the scanned data.
3333
## Classification
@@ -39,21 +39,21 @@ An asset where Microsoft Purview extracts schema and applies classifications dur
3939
## Collection
4040
An organization-defined grouping of assets, terms, annotations, and sources. Collections allow for easier fine-grained access control and discoverability of assets within a data catalog.
4141
## Collection admin
42-
A role that can assign roles in Microsoft Purview. Collection admins can add users to roles on collections where they're admins. They can also edit collections, their details, and add subcollections.
42+
A role that can assign roles in the Microsoft Purview governance portal. Collection admins can add users to roles on collections where they're admins. They can also edit collections, their details, and add subcollections.
4343
## Column pattern
4444
A regular expression included in a classification rule that represents the column names that you want to match.
4545
## Contact
4646
An individual who is associated with an entity in the data catalog.
4747
## Control plane operation
48-
An operation that manages resources in your subscription, such as role-based access control and Azure policy, that are sent to the Azure Resource Manager end point. Control plane operations can also apply to resources outside of Azure across on-premises, multicloud, and SaaS sources.
48+
An operation that manages resources in your subscription, such as role-based access control and Azure policy that are sent to the Azure Resource Manager end point. Control plane operations can also apply to resources outside of Azure across on-premises, multicloud, and SaaS sources.
4949
## Credential
5050
A verification of identity or tool used in an access control system. Credentials can be used to authenticate an individual or group to grant access to a data asset.
5151
## Data Catalog
5252
A searchable inventory of assets and their associated metadata that allows users to find and curate data across a data estate. The Data Catalog also includes a business glossary where subject matter experts can provide terms and definitions to add a business context to an asset.
5353
## Data curator
5454
A role that provides access to the data catalog to manage assets, configure custom classifications, set up glossary terms, and view insights. Data curators can create, read, modify, move, and delete assets. They can also apply annotations to assets.
5555
## Data map
56-
A metadata repository that is the foundation of Microsoft Purview. The data map is a graph that describes assets across a data estate and is populated through scans and other data ingestion processes. This graph helps organizations understand and govern their data by providing rich descriptions of assets, representing data lineage, classifying assets, storing relationships between assets, and housing information at both the technical and semantic layers. The data map is an open platform that can be interacted with and accessed through Apache Atlas APIs or the Microsoft Purview governance portal.
56+
A metadata repository that is the foundation of the Microsoft Purview governance portal. The data map is a graph that describes assets across a data estate and is populated through scans and other data ingestion processes. This graph helps organizations understand and govern their data by providing rich descriptions of assets, representing data lineage, classifying assets, storing relationships between assets, and housing information at both the technical and semantic layers. The data map is an open platform that can be interacted with and accessed through Apache Atlas APIs or the Microsoft Purview governance portal.
5757
## Data map operation
5858
A create, read, update, or delete action performed on an entity in the data map. For example, creating an asset in the data map is considered a data map operation.
5959
## Data owner
@@ -69,9 +69,9 @@ A role that can manage data sources and scans. A user in the Data source admin r
6969
## Data steward
7070
An individual or group responsible for maintaining nomenclature, data quality standards, security controls, compliance requirements, and rules for the associated object.
7171
## Data dictionary
72-
A list of canonical names of database columns and their corresponding data types. It is often used to describe the format and structure of a database, and the relationship between its elements.
72+
A list of canonical names of database columns and their corresponding data types. It's often used to describe the format and structure of a database, and the relationship between its elements.
7373
## Discovered asset
74-
An asset that Microsoft Purview identifies in a data source during the scanning process. The number of discovered assets includes all files or tables before resource set grouping.
74+
An asset that the Microsoft Purview Data Map identifies in a data source during the scanning process. The number of discovered assets includes all files or tables before resource set grouping.
7575
## Distinct match threshold
7676
The total number of distinct data values that need to be found in a column before the scanner runs the data pattern on it. For example, a distinct match threshold of eight for employee ID requires that there are at least eight unique data values among the sampled values in the column that match the data pattern set for employee ID.
7777
## Expert
@@ -85,7 +85,7 @@ An entry in the Business glossary that defines a concept specific to an organiza
8585
## Incremental scan
8686
A scan that detects and processes assets that have been created, modified, or deleted since the previous successful scan. To run an incremental scan, at least one full scan must be completed on the source.
8787
## Ingested asset
88-
An asset that has been scanned, classified (when applicable), and added to the Microsoft Purview data map. Ingested assets are discoverable and consumable within the data catalog through automated scanning or external connections, such as Azure Data Factory and Azure Synapse.
88+
An asset that has been scanned, classified (when applicable), and added to the Microsoft Purview Data Map. Ingested assets are discoverable and consumable within the data catalog through automated scanning or external connections, such as Azure Data Factory and Azure Synapse.
8989
## Insight reader
9090
A role that provides read-only access to insights reports for collections where the insights reader also has the **Data reader** role.
9191
## Data Estate Insights
@@ -95,7 +95,7 @@ The compute infrastructure used to scan in a data source.
9595
## Lineage
9696
How data transforms and flows as it moves from its origin to its destination. Understanding this flow across the data estate helps organizations see the history of their data, and aid in troubleshooting or impact analysis.
9797
## Management
98-
An area within Microsoft Purview where you can manage connections, users, roles, and credentials. Also referred to as "Management center."
98+
An area within the Microsoft Purview Governance Portal where you can manage connections, users, roles, and credentials. Also referred to as "Management center."
9999
## Minimum match threshold
100100
The minimum percentage of matches among the distinct data values in a column that must be found by the scanner for a classification to be applied.
101101

@@ -109,21 +109,21 @@ Data that is in a data center controlled by a customer, for example, not in the
109109
## Owner
110110
An individual or group in charge of managing a data asset.
111111
## Pattern rule
112-
A configuration that overrides how Microsoft Purview groups assets as resource sets and displays them within the catalog.
112+
A configuration that overrides how the Microsoft Purview Data Map groups assets as resource sets and displays them within the catalog.
113113
## Microsoft Purview instance
114-
A single Microsoft Purview account.
114+
A single Microsoft Purview (formerly Azure Purview) account.
115115
## Registered source
116116
A source that has been added to a Microsoft Purview instance and is now managed as a part of the Data catalog.
117117
## Related terms
118118
Glossary terms that are linked to other terms within the organization.
119119
## Resource set
120-
A single asset that represents many partitioned files or objects in storage. For example, Microsoft Purview stores partitioned Apache Spark output as a single resource set instead of unique assets for each individual file.
120+
A single asset that represents many partitioned files or objects in storage. For example, the Microsoft Purview Data Map stores partitioned Apache Spark output as a single resource set instead of unique assets for each individual file.
121121
## Role
122122
Permissions assigned to a user within a Microsoft Purview instance. Roles, such as Microsoft Purview Data Curator or Microsoft Purview Data Reader, determine what can be done within the product.
123123
## Root collection
124124
A system-generated collection that has the same friendly name as the Microsoft Purview account. All assets belong to the root collection by default.
125125
## Scan
126-
A Microsoft Purview process that discovers and examines metadata in a source or set of sources to populate the data map. A scan automatically connects to a source, extracts metadata, captures lineage, and applies classifications. Scans can be run manually or on a schedule.
126+
A Microsoft Purview Data Map process that discovers and examines metadata in a source or set of sources to populate the data map. A scan automatically connects to a source, extracts metadata, captures lineage, and applies classifications. Scans can be run manually or on a schedule.
127127
## Scan rule set
128128
A set of rules that define which data types and classifications a scan ingests into a catalog.
129129
## Scan trigger
@@ -137,22 +137,22 @@ The scoring of data assets that determine the order search results are returned.
137137
## Self-hosted integration runtime
138138
An integration runtime installed on an on-premises machine or virtual machine inside a private network that is used to connect to data on-premises or in a private network.
139139
## Sensitivity label
140-
Annotations that classify and protect an organization’s data. Microsoft Purview integrates with Microsoft Purview Information Protection for creation of sensitivity labels.
140+
Annotations that classify and protect an organization’s data. The Microsoft Purview Data Map integrates with Microsoft Purview Information Protection for creation of sensitivity labels.
141141
## Sensitivity label report
142142
A summary of which sensitivity labels are applied across the data estate.
143143
## Service
144144
A product that provides standalone functionality and is available to customers by subscription or license.
145145
## Source
146-
A system where data is stored. Sources can be hosted in various places such as a cloud or on-premises. You register and scan sources so that you can manage them in Microsoft Purview.
146+
A system where data is stored. Sources can be hosted in various places such as a cloud or on-premises. You register and scan sources so that you can manage them in the Microsoft Purview governance portal.
147147
## Source type
148-
A categorization of the registered sources used in a Microsoft Purview instance, for example, Azure SQL Database, Azure Blob Storage, Amazon S3, or SAP ECC.
148+
A categorization of the registered sources used in the Microsoft Purview Data Map, for example, Azure SQL Database, Azure Blob Storage, Amazon S3, or SAP ECC.
149149
## Steward
150-
An individual who defines the standards for a glossary term. They are responsible for maintaining quality standards, nomenclature, and rules for the assigned entity.
150+
An individual who defines the standards for a glossary term. They're responsible for maintaining quality standards, nomenclature, and rules for the assigned entity.
151151
## Term template
152152
A definition of attributes included in a glossary term. Users can either use the system-defined term template or create their own to include custom attributes.
153153
## Workflow
154154
An automated process that coordinates the creation and modification of catalog entities, including validation and approval. Workflows define repeatable business processes to achieve high quality data, policy compliance, and user collaboration across an organization.
155155

156156
## Next steps
157157

158-
To get started with Microsoft Purview, see [Quickstart: Create a Microsoft Purview account](create-catalog-portal.md).
158+
To get started with other Microsoft Purview governance services, see [Quickstart: Create a Microsoft Purview (formerly Azure Purview) account](create-catalog-portal.md).

0 commit comments

Comments
 (0)