Merge pull request #195372 from whhender/6-azure-purview-to-microsoft-purview

Purview Catalog - Azure Purview to Microsoft Purview

Author: ttorble

articles/data-factory/how-to-access-secured-purview-account.md

@@ -21,8 +21,8 @@ If your Microsoft Purview account is protected by firewall and denies public acc
 
 | Scenario                                                     | Required Microsoft Purview private endpoints                           |
 | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [Run pipeline and report lineage to Microsoft Purview](tutorial-push-lineage-to-purview.md) | For Data Factory pipeline to push lineage to Microsoft Purview, Microsoft Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Microsoft Purview](#managed-private-endpoints-for-microsoft-purview) section to create managed private endpoints in the Data Factory managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-azure-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
-| [Discover and explore data using Microsoft Purview on ADF UI](how-to-discover-explore-purview-data.md) | To use the search bar at the top center of Data Factory authoring UI to search for Microsoft Purview data and perform actions, you need to create Microsoft Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Data Factory Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-azure-purview-accounts). |
+| [Run pipeline and report lineage to Microsoft](tutorial-push-lineage-to-purview.md) | For Data Factory pipeline to push lineage to Microsoft, Microsoft Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Microsoft Purview](#managed-private-endpoints-for-microsoft-purview) section to create managed private endpoints in the Data Factory managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-microsoft-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
+| [Discover and explore data using Microsoft on ADF UI](how-to-discover-explore-purview-data.md) | To use the search bar at the top center of Data Factory authoring UI to search for Microsoft Purview data and perform actions, you need to create Microsoft Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Data Factory Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-microsoft-purview-accounts). |
 
 ## Managed private endpoints for Microsoft Purview
 

articles/purview/catalog-asset-details.md

@@ -8,18 +8,18 @@ ms.subservice: purview-data-catalog
 ms.topic: how-to
 ms.date: 02/24/2022
 ---
-# View, edit and delete assets in Azure Purview catalog
+# View, edit and delete assets in Microsoft Purview catalog
 
 This article discusses how you can view your assets and their relevant details. It also describes how you can edit and delete assets from your catalog.
 
 ## Prerequisites
 
 - Set up your data sources and scan the assets into your catalog.
-- *Or* Use the Azure Purview Atlas APIs to ingest assets into the catalog. 
+- *Or* Use the Microsoft Purview Atlas APIs to ingest assets into the catalog. 
 
 ## Viewing asset details
 
-You can discover your assets in the Azure Purview data catalog by either:
+You can discover your assets in the Microsoft Purview data catalog by either:
 - [Browsing the data catalog](how-to-browse-catalog.md)
 - [Searching the data catalog](how-to-search-catalog.md)
 
@@ -81,25 +81,25 @@ If you edit an asset by adding a description, asset level classification, glossa
 
 If you make some column level updates, like adding a description, column level classification, or glossary term, then subsequent scans will also update the asset schema (new columns and classifications will be detected by the scanner in subsequent scan runs). 
 
-Even on edited assets, after a scan Azure Purview will reflect the truth of the source system. For example: if you edit a column and it's deleted from the source, it will be deleted from your asset in Azure Purview. 
+Even on edited assets, after a scan Microsoft Purview will reflect the truth of the source system. For example: if you edit a column and it's deleted from the source, it will be deleted from your asset in Microsoft Purview. 
 
 >[!NOTE]
-> If you update the **name or data type of a column** in an Azure Purview asset, later scans **will not** update the asset schema. New columns and classifications **will not** be detected.
+> If you update the **name or data type of a column** in a Microsoft Purview asset, later scans **will not** update the asset schema. New columns and classifications **will not** be detected.
 
 ## Deleting assets
 
 You can delete an asset by selecting the delete icon under the name of the asset.
 
 ### Delete behavior explained
 
-Any asset you delete using the delete button is permanently deleted in Azure Purview. However, if you run a **full scan** on the source from which the asset was ingested into the catalog, then the asset is reingested and you can discover it using the Azure Purview catalog.
+Any asset you delete using the delete button is permanently deleted in Microsoft Purview. However, if you run a **full scan** on the source from which the asset was ingested into the catalog, then the asset is reingested and you can discover it using the Microsoft Purview catalog.
 
-If you have a scheduled scan (weekly or monthly) on the source, the **deleted asset will not get re-ingested** into the catalog unless the asset is modified by an end user since the previous run of the scan.   For example, if a SQL table was deleted from Azure Purview, but after the table was deleted a user added a new column to the table in SQL, at the next scan the asset will be rescanned and ingested into the catalog.
+If you have a scheduled scan (weekly or monthly) on the source, the **deleted asset will not get re-ingested** into the catalog unless the asset is modified by an end user since the previous run of the scan.   For example, if a SQL table was deleted from Microsoft Purview, but after the table was deleted a user added a new column to the table in SQL, at the next scan the asset will be rescanned and ingested into the catalog.
 
-If you delete an asset, only that asset is deleted. Azure Purview does not currently support cascaded deletes. For example, if you delete a storage account asset in your catalog - the containers, folders and files within them are not deleted. 
+If you delete an asset, only that asset is deleted. Microsoft Purview does not currently support cascaded deletes. For example, if you delete a storage account asset in your catalog - the containers, folders and files within them are not deleted. 
 
 
 ## Next steps
 
-- [Browse the Azure Purview Data catalog](how-to-browse-catalog.md)
-- [Search the Azure Purview Data Catalog](how-to-search-catalog.md)
+- [Browse the Microsoft Purview Data catalog](how-to-browse-catalog.md)
+- [Search the Microsoft Purview Data Catalog](how-to-search-catalog.md)

articles/purview/catalog-conditional-access.md

@@ -1,24 +1,24 @@
 ---
-title: Configure Azure AD Conditional Access for Azure Purview
-description: This article describes steps how to configure Azure AD Conditional Access for Azure Purview
+title: Configure Azure AD Conditional Access for Microsoft Purview
+description: This article describes steps how to configure Azure AD Conditional Access for Microsoft Purview
 author: zeinam
 ms.author: zeinam
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
 ms.date: 01/14/2022
-# Customer intent: As an identity and security admin, I want to set up Azure Active Directory Conditional Access for Azure Purview, for secure access.
+# Customer intent: As an identity and security admin, I want to set up Azure Active Directory Conditional Access for Microsoft Purview, for secure access.
 ---
 
-# Conditional Access with Azure Purview
+# Conditional Access with Microsoft Purview
 
-[Azure Purview](./overview.md) supports Microsoft Conditional Access.
+[Microsoft Purview](./overview.md) supports Microsoft Conditional Access.
 
-The following steps show how to configure Azure Purview to enforce a Conditional Access policy.  
+The following steps show how to configure Microsoft Purview to enforce a Conditional Access policy.  
 
 ## Prerequisites
 
-- When multi-factor authentication is enabled, to sign in to Azure Purview Studio, you must perform multi-factor authentication.
+- When multi-factor authentication is enabled, to sign in to Microsoft Purview Studio, you must perform multi-factor authentication.
 
 ## Configure conditional access
 
@@ -31,7 +31,7 @@ The following steps show how to configure Azure Purview to enforce a Conditional
 
   :::image type="content" source="media/catalog-conditional-access/select-users-and-groups.png" alt-text="Screenshot that shows User and Group selection"lightbox="media/catalog-conditional-access/select-users-and-groups.png":::
 
-1. Select **Cloud apps**, select **Select apps**. You see all apps available for Conditional Access. Select **Azure Purview**, at the bottom select **Select**, and then select **Done**.  
+1. Select **Cloud apps**, select **Select apps**. You see all apps available for Conditional Access. Select **Microsoft Purview**, at the bottom select **Select**, and then select **Done**.  
 
     :::image type="content" source="media/catalog-conditional-access/select-azure-purview.png" alt-text="Screenshot that shows Applications selection"lightbox="media/catalog-conditional-access/select-azure-purview.png":::
 
@@ -43,4 +43,4 @@ The following steps show how to configure Azure Purview to enforce a Conditional
 
 ## Next steps
 
-- [Use Azure Purview Studio](./use-purview-studio.md)
+- [Use Microsoft Purview Studio](./use-purview-studio.md)

articles/purview/catalog-lineage-user-guide.md

@@ -1,22 +1,22 @@
 ---
 title: Data Catalog lineage user guide
-description: This article provides an overview of the catalog lineage feature of Azure Purview.
+description: This article provides an overview of the catalog lineage feature of Microsoft Purview.
 author: chanuengg
 ms.author: csugunan
 ms.service: purview
 ms.topic: conceptual
 ms.date: 01/20/2022
 ---
-# Azure Purview Data Catalog lineage user guide
+# Microsoft Purview Data Catalog lineage user guide
 
-This article provides an overview of the data lineage features in Azure Purview Data Catalog.
+This article provides an overview of the data lineage features in Microsoft Purview Data Catalog.
 
 ## Background
 
-One of the platform features of Azure Purview is the ability to show the lineage between datasets created by data processes. Systems like Data Factory, Data Share, and Power BI capture the lineage of data as it moves. Custom lineage reporting is also supported via Atlas hooks and REST API.
+One of the platform features of Microsoft Purview is the ability to show the lineage between datasets created by data processes. Systems like Data Factory, Data Share, and Power BI capture the lineage of data as it moves. Custom lineage reporting is also supported via Atlas hooks and REST API.
 
 ## Lineage collection 
- Metadata collected in Azure Purview from enterprise data systems are stitched across to show an end to end data lineage. Data systems that collect lineage into Azure Purview are broadly categorized into following three types:
+ Metadata collected in Microsoft Purview from enterprise data systems are stitched across to show an end to end data lineage. Data systems that collect lineage into Microsoft Purview are broadly categorized into following three types:
 
  - [Data processing systems](#data-processing-systems)
  - [Data storage systems](#data-storage-systems)
@@ -25,7 +25,7 @@ One of the platform features of Azure Purview is the ability to show the lineage
 Each system supports a different level of lineage scope. Check the sections below, or your system's individual lineage article, to confirm the scope of lineage currently available.
 
 ### Data processing systems
-Data integration and ETL tools can push lineage into Azure Purview at execution time. Tools such as Data Factory, Data Share, Synapse, Azure Databricks, and so on, belong to this category of data processing systems. The data processing systems reference datasets as source from different databases and storage solutions to create target datasets. The list of data processing systems currently integrated with Azure Purview for lineage are listed in below table.
+Data integration and ETL tools can push lineage into Microsoft Purview at execution time. Tools such as Data Factory, Data Share, Synapse, Azure Databricks, and so on, belong to this category of data processing systems. The data processing systems reference datasets as source from different databases and storage solutions to create target datasets. The list of data processing systems currently integrated with Microsoft Purview for lineage are listed in below table.
 
 | Data processing system | Supported scope |
 | ---------------------- | ------------|
@@ -35,7 +35,7 @@ Data integration and ETL tools can push lineage into Azure Purview at execution
 | Azure Data Share | [Share snapshot](how-to-link-azure-data-share.md) |
 
 ### Data storage systems
-Databases & storage solutions such as Oracle, Teradata, and SAP have query engines to transform data using scripting language. Data lineage from views/stored procedures/etc are collected into Azure Purview and stitched with lineage from other systems. Lineage is supported for the following data sources via Azure Purview data scan. Learn more about the supported lineage scenarios from the respective article.
+Databases & storage solutions such as Oracle, Teradata, and SAP have query engines to transform data using scripting language. Data lineage from views/stored procedures/etc are collected into Microsoft Purview and stitched with lineage from other systems. Lineage is supported for the following data sources via Microsoft Purview data scan. Learn more about the supported lineage scenarios from the respective article.
 
 |**Category**|  **Data source**  |
 |---|---|
@@ -54,7 +54,7 @@ Databases & storage solutions such as Oracle, Teradata, and SAP have query engin
 || [SAP S/4HANA](register-scan-saps4hana-source.md) |
 
 ### Data analytics and reporting systems
-Data analytics and reporting systems like Azure ML and Power BI report lineage into Azure Purview. These systems will use the datasets from storage systems and process through their meta model to create BI Dashboards, ML experiments and so on.
+Data analytics and reporting systems like Azure ML and Power BI report lineage into Microsoft Purview. These systems will use the datasets from storage systems and process through their meta model to create BI Dashboards, ML experiments and so on.
 
 | Data analytics & reporting system | Supported scope |
 | ---------------------- | ------------|
@@ -64,27 +64,27 @@ Data analytics and reporting systems like Azure ML and Power BI report lineage i
 
 > [!VIDEO https://www.microsoft.com/videoplayer/embed/RWxTAK]
 
-Lineage in Azure Purview includes datasets and processes. Datasets are also referred to as nodes while processes can be also called edges:
+Lineage in Microsoft Purview includes datasets and processes. Datasets are also referred to as nodes while processes can be also called edges:
 
-* **Dataset (Node)**: A dataset (structured or unstructured) provided as an input to a process. For example, a SQL Table, Azure blob, and files (such as .csv and .xml), are all considered datasets. In the lineage section of Azure Purview, datasets are represented by rectangular boxes.
+* **Dataset (Node)**: A dataset (structured or unstructured) provided as an input to a process. For example, a SQL Table, Azure blob, and files (such as .csv and .xml), are all considered datasets. In the lineage section of Microsoft Purview, datasets are represented by rectangular boxes.
 
-* **Process (Edge)**: An activity or transformation performed on a dataset is called a process. For example, ADF Copy activity, Data Share snapshot and so on. In the lineage section of Azure Purview, processes are represented by round-edged boxes.
+* **Process (Edge)**: An activity or transformation performed on a dataset is called a process. For example, ADF Copy activity, Data Share snapshot and so on. In the lineage section of Microsoft Purview, processes are represented by round-edged boxes.
 
-To access lineage information for an asset in Azure Purview, follow the steps:
+To access lineage information for an asset in Microsoft Purview, follow the steps:
 
-1. In the Azure portal, go to the [Azure Purview accounts page](https://aka.ms/purviewportal).
+1. In the Azure portal, go to the [Microsoft Purview accounts page](https://aka.ms/purviewportal).
 
-1. Select your Azure Purview account from the list, and then select **Open Azure Purview Studio** from the **Overview** page.
+1. Select your Microsoft Purview account from the list, and then select **Open Microsoft Purview Studio** from the **Overview** page.
 
-1. On the Azure Purview Studio **Home** page, search for a dataset name or the process name such as ADF Copy or Data Flow activity. And then press Enter.
+1. On the Microsoft Purview Studio **Home** page, search for a dataset name or the process name such as ADF Copy or Data Flow activity. And then press Enter.
 
 1. From the search results, select the asset and select its **Lineage** tab.
 
    :::image type="content" source="./media/catalog-lineage-user-guide/select-lineage-from-asset.png" alt-text="Screenshot showing how to select the Lineage tab." border="true":::
 
 ## Asset-level lineage
 
-Azure Purview supports asset level lineage for the datasets and processes. To see the asset level lineage go to the **Lineage** tab of the current asset in the catalog. Select the current dataset asset node. By default the list of columns belonging to the data appears in the left pane.
+Microsoft Purview supports asset level lineage for the datasets and processes. To see the asset level lineage go to the **Lineage** tab of the current asset in the catalog. Select the current dataset asset node. By default the list of columns belonging to the data appears in the left pane.
 
    :::image type="content" source="./media/catalog-lineage-user-guide/view-columns-from-lineage.png" alt-text="Screenshot showing how to select View columns in the lineage page" border="true":::
 
@@ -113,7 +113,7 @@ To see column-level lineage of a dataset, go to the **Lineage** tab of the curre
    :::image type="content" source="./media/catalog-lineage-user-guide/use-toggle-to-filter-nodes.png" alt-text="Screenshot showing how to use the toggle to filter the list of nodes on the lineage page." lightbox="./media/catalog-lineage-user-guide/use-toggle-to-filter-nodes.png":::
 
 ## Process column lineage
-Data process can take one or more input datasets to produce one or more outputs. In Azure Purview, column level lineage is available for process nodes. 
+Data process can take one or more input datasets to produce one or more outputs. In Microsoft Purview, column level lineage is available for process nodes. 
 1. Switch between input and output datasets from a drop down in the columns panel.
 2. Select columns from one or more tables to see the lineage flowing from input dataset to corresponding output dataset.