Review

Author: whhender

articles/purview/catalog-conditional-access.md

@@ -6,7 +6,7 @@ ms.author: zeinam
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 01/14/2022
+ms.date: 03/23/2023
 # Customer intent: As an identity and security admin, I want to set up Azure Active Directory Conditional Access for Microsoft Purview, for secure access.
 ---
 

articles/purview/how-to-lineage-powerbi.md

@@ -6,19 +6,25 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 01/30/2022
+ms.date: 03/23/2023
 ---
 # How to get lineage from Power BI into Microsoft Purview
 
-This article elaborates on the data lineage aspects of Power BI source in Microsoft Purview. The prerequisite to see data lineage in Microsoft Purview for Power BI is to [scan your Power BI.](../purview/register-scan-power-bi-tenant.md) 
+This article elaborates on the data lineage for Power BI sources in Microsoft Purview.
+
+## Prerequisites
+
+To see data lineage in Microsoft Purview for Power BI, you must first [register and scan your Power BI source.](../purview/register-scan-power-bi-tenant.md)
 
 ## Common scenarios
 
-1. After the Power BI source is scanned, data consumers can perform root cause analysis of a report or dashboard from Microsoft Purview. For any data discrepancy in a report, users can easily identify the upstream datasets and contact their owners if necessary.
+After a Power BI source has been scanned, lineage information for your current data assets, and data assets referenced by Power BI, will automatically be added in the Microsoft Purview Data Catalog.
+
+1. Data consumers can perform root cause analysis of a report or dashboard from Microsoft Purview. For any data discrepancy in a report, users can easily identify the upstream datasets and contact their owners if necessary.
 
-2. Data producers can see the downstream reports or dashboards consuming their dataset. Before making any changes to their datasets, the data owners can make informed decisions.
+1. Data producers can see the downstream reports or dashboards consuming their dataset. Before making any changes to their datasets, the data owners can make informed decisions.
 
-2. Users can search by name, endorsement status, sensitivity label, owner, description, and other business facets to return the relevant Power BI artifacts.
+1. Users can search by name, endorsement status, sensitivity label, owner, description, and other business facets to return the relevant Power BI artifacts.
 
 ## Power BI artifacts in Microsoft Purview
 
@@ -35,16 +41,20 @@ Once the [scan of your Power BI](../purview/register-scan-power-bi-tenant.md) is
 
 ## Lineage of Power BI artifacts in Microsoft Purview
 
-Users can search for the Power BI artifact by name, description, or other details to see relevant results. Under the asset overview & properties tab the basic details such as description, classification and other information are shown. Under the lineage tab, asset relationships are shown with the upstream and downstream dependencies.
+Users can search for a Power BI artifact by name, description, or other details to see relevant results. Under the asset overview and properties tabs, the basic details such as description, classification are shown. Under the lineage tab, asset relationships are shown with the upstream and downstream dependencies.
 
-Microsoft Purview captures lineage among Power BI artifacts (e.g. Dataflow -> Dataset -> Report -> Dashboard) as well as external data assets.
+Microsoft Purview captures lineage among Power BI artifacts (for example: Dataflow -> Dataset -> Report -> Dashboard) and external data assets.
 
 >[!NOTE]
-> For lineage between Power BI artifacts and external data assets, currently the supported source types are: Azure SQL Database, Azure Blob Storage, Azure Data Lake Store Gen1, and Azure Data Lake Store Gen2.
+> For lineage between Power BI artifacts and external data assets, currently the supported source types are:
+>* Azure SQL Database
+>* Azure Blob Storage
+>* Azure Data Lake Store Gen1
+>* Azure Data Lake Store Gen2
 
 :::image type="content" source="./media/how-to-lineage-powerbi/powerbi-lineage.png" alt-text="Screenshot showing how lineage is rendered for Power BI." lightbox="./media/how-to-lineage-powerbi/powerbi-lineage.png":::
 
-In addition, column level lineage (Power BI sub-artifact lineage) and transformation inside of Power BI datasets are captured when using Azure SQL Database as source. For measures, you can further click into the column -> Properties -> expression to see the transformation details.
+In addition, column level lineage (Power BI subartifact lineage) and transformation inside of Power BI datasets are captured when using Azure SQL Database as source. For measures, you can further select column -> Properties -> expression to see the transformation details.
 
 >[!NOTE]
 > Column level lineage and transformations is supported when using Azure SQL Database as source. Other sources are currently not supported.
@@ -53,11 +63,11 @@ In addition, column level lineage (Power BI sub-artifact lineage) and transforma
 
 ## Known limitations
 
-* Limited information is currently shown for the Data sources from which the Power BI Dataflow or Power BI Dataset is created. For example, for SQL server source of Power BI dataset, only server/database name is captured.
-* Few measures aren't shown in the sub-artifact lineage, for example, `COUNTROWS`.
-* In the lineage graph, when selecting measure that is derived by columns using COUNT function, underlying column isn't selected automatically. Check the measure expression in the column properties tab to identify the underlying column.
-* If you used to scan Power BI before sub-artifact lineage is supported, you may see a database asset along with the new table assets in the lineage graph, which isn't removed.
-* In case you have the dataset table connected to another dataset table, when the middle dataset disables "Enable load" option inside the Power BI desktop, the lineage cannot be extracted.
+* Limited information is currently shown for data sources where the Power BI Dataflow or Power BI Dataset is created. For example, for a SQL server source of Power BI dataset, only server/database name is captured.
+* Some measures aren't shown in the subartifact lineage, for example, `COUNTROWS`.
+* In the lineage graph, when selecting a measure that is derived by columns using the COUNT function, the underlying column isn't selected automatically. Check the measure expression in the column properties tab to identify the underlying column.
+* If you scanned your Power BI source before subartifact lineage was supported, you may see a database asset along with the new table assets in the lineage graph, which isn't removed.
+* In case you have the dataset table connected to another dataset table, when the middle dataset disables the "Enable load" option inside the Power BI desktop, and the lineage can't be extracted.
 
 ## Next steps