Merge pull request #245261 from linda33wj/main

prmerger-automator[bot] · web-flow · commit 2370db2cb2d6 · 2023-07-18T06:59:17.000Z
Update connector and scan monitoring doc
diff --git a/articles/purview/catalog-managed-vnet.md b/articles/purview/catalog-managed-vnet.md
@@ -6,7 +6,7 @@ ms.author: zeinam
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 02/17/2023
+ms.date: 07/18/2023
 ms.custom: references_regions
 # Customer intent: As a Microsoft Purview admin, I want to set up Managed Virtual Network and managed private endpoints for my Microsoft Purview account.
 ---
@@ -167,7 +167,9 @@ Before deploying a Managed VNet and Managed VNet Runtime for a Microsoft Purview
 
 ### Deploy managed private endpoints for data sources
 
-To scan any data sources using Managed VNet Runtime, you need to deploy and approve a managed private endpoint for the data source prior to create a new scan. To deploy and approve a managed private endpoint for a data source, follow these steps selecting data source of your choice from the list:
+You can use managed private endpoints to connect your data sources to ensure data security during transmission. If your data source allows public access and you want to connect via public network, you can skip this step. Scan run can be executed as long as the integration runtime can connect to your data source.
+
+To deploy and approve a managed private endpoint for a data source, follow these steps selecting data source of your choice from the list:
 
 1. Navigate to **Management**, and select **Managed private endpoints**.
    
diff --git a/articles/purview/how-to-monitor-data-map-population.md b/articles/purview/how-to-monitor-data-map-population.md
@@ -15,7 +15,7 @@ In Microsoft Purview, you can scan various types of data sources and view the sc
 
 ## Monitor scan runs
 
-1. Open the the Microsoft Purview governance portal by:
+1. Open the Microsoft Purview governance portal by:
 
     - Browsing directly to [https://web.purview.azure.com](https://web.purview.azure.com) and selecting your Microsoft Purview account.
     - Opening the [Azure portal](https://portal.azure.com), searching for and selecting the Microsoft Purview account. Selecting the [**the Microsoft Purview governance portal**](https://web.purview.azure.com/) button.
@@ -62,8 +62,8 @@ You can click the **run ID** to check more about the scan run details:
         | Failed      | The scan phase fails. You can check the error details by clicking the "More info" link next to it. |
         | Canceled    | The scan run is canceled by user.                           |
         | In Progress | The scan is running in progress.                             |
-        | Queued      | The scan run is waiting for available integration runtime resource.<br>If you use self-hosted integration runtime, note each node can run a number of concurrent scans at the same time depending on your machine specification (CPU and memory). More scans will be in Queued status. |
-        | Throttled   | The scan run is being throttled. It means this Microsoft Purview account at the moment has more ongoing scan runs than the allowed max concurrent count. Learn more about the limit [here](how-to-manage-quotas.md). This particular scan run will be waiting and be executed once your other ongoing scan(s) finishes. |
+        | Queued      | The scan run is waiting for available integration runtime resource.<br>If you use self-hosted integration runtime, note each node can run a number of concurrent scans at the same time depending on your machine specification (CPU and memory). More scans are in Queued status. |
+        | Throttled   | The scan run is being throttled. It means this Microsoft Purview account at the moment has more ongoing scan runs than the allowed max concurrent count. Learn more about the limit [here](how-to-manage-quotas.md). This particular scan run is waiting and will be executed once your other ongoing scan(s) finishes. |
 
         The scan run is not charged during "Throttled" or "Queued" status.
 
@@ -91,6 +91,21 @@ You can click the **run ID** to check more about the scan run details:
 
     - **Duration**: The ingestion duration and the start/end time.
 
+## View the exception log (Preview)
+
+When some assets or relationship fail to ingest into data map during scan, e.g. ingestion status ends up as partially completed, you can see a "**Download log**" button in the [scan run details](#scan-run-details) panel. It provides exception log files that capture the details of the failures.
+
+The following table shows the schema of a log file.
+
+| Column | Description |
+| ------ | ----------- |
+| TimeStamp	| The UTC timestamp when the ingestion operation happens.| 
+| ErrorCode	| Error code of the exception. | 
+| OperationItem	| Identifier for the failed asset/relationship, usually using the fully qualified name. | 
+| Message | More information on which asset/relationship failed to ingest due to what reason. If there is ingestion failure for resource set, it may apply to multiple assets matching the same naming pattern, and the message includes the impacted count. |
+
+Currently, the exception log doesn't include failures happened during scan phase (metadata discovery). It will be added later.
+
 ## Monitor links
 
 You can connect other services with Microsoft Purview to establish a "link", which will make the metadata and lineage of that service's assets available to Microsoft Purview. Currently, link is supported for [Azure Data Factory](how-to-link-azure-data-factory.md) and [Azure Synapse Analytics](how-to-lineage-azure-synapse-analytics.md).
diff --git a/articles/purview/register-scan-cassandra-source.md b/articles/purview/register-scan-cassandra-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 07/18/2023
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -134,7 +134,7 @@ To create and run a new scan:
     1. **Maximum memory available** (applicable when using self-hosted integration runtime): Specify the maximum memory (in GB) available on your VM to be used for scanning processes. This value depends on the size of Cassandra server to be scanned.
         :::image type="content" source="media/register-scan-cassandra-source/scan.png" alt-text="scan Cassandra source" border="true":::
 
-1. Select **Test connection** (available when using self-hosted integration runtime).
+1. Select **Test connection** to validate the settings.
 
 1. Select **Continue**.
 
diff --git a/articles/purview/register-scan-looker-source.md b/articles/purview/register-scan-looker-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 07/18/2023
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -137,7 +137,7 @@ To create and run a new scan, follow these steps:
 
         :::image type="content" source="media/register-scan-looker-source/setup-scan.png" alt-text="trigger scan" border="true":::
 
-1. Select **Test connection** (available when using self-hosted integration runtime).
+1. Select **Test connection** to validate the settings.
 
 1. Select **Continue**.
 
diff --git a/articles/purview/register-scan-mysql.md b/articles/purview/register-scan-mysql.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 07/18/2023
 ms.custom: template-how-to
 ---
 
@@ -135,6 +135,8 @@ To create and run a new scan, follow these steps:
 
         :::image type="content" source="media/register-scan-mysql/scan.png" alt-text="scan MySQL" border="true":::
 
+1. Select **Test connection** to validate the settings (available when using Azure Integration Runtime).
+
 1. Select **Continue**.
 
 1. Choose your **scan trigger**. You can set up a schedule or ran the scan once.
diff --git a/articles/purview/register-scan-postgresql.md b/articles/purview/register-scan-postgresql.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 07/18/2023
 ms.custom: template-how-to
 ---
 
@@ -139,6 +139,8 @@ To create and run a new scan, follow these steps:
 
         :::image type="content" source="media/register-scan-postgresql/scan.png" alt-text="scan PostgreSQL" border="true":::
 
+1. Select **Test connection** to validate the settings (available when using Azure Integration Runtime).
+
 1. Select **Continue**.
 
 1. Choose your **scan trigger**. You can set up a schedule or ran the scan once.
diff --git a/articles/purview/register-scan-salesforce.md b/articles/purview/register-scan-salesforce.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 07/18/2023
 ms.custom: template-how-to
 ---
 
@@ -38,7 +38,7 @@ When object is deleted from the data source, currently the subsequent scan won't
 - You need Data Source Administrator and Data Reader permissions to register a source and manage it in the Microsoft Purview governance portal. For more information about permissions, see [Access control in Microsoft Purview](catalog-permissions.md).
 - A Salesforce connected app, which will be used to access your Salesforce information.
   - If you need to create a connected app, you can follow the [Salesforce documentation](https://help.salesforce.com/s/articleView?id=sf.connected_app_create_basics.htm&type=5).
-  - You will need to [enable OAuth for you Salesforce application](https://help.salesforce.com/s/articleView?id=sf.connected_app_create_api_integration.htm&type=5).
+  - You will need to [enable OAuth for your Salesforce application](https://help.salesforce.com/s/articleView?id=sf.connected_app_create_api_integration.htm&type=5).
 
 > [!NOTE]
 > **If your data store is not publicly accessible** (if your data store limits access from on-premises network, private network or specific IPs, etc.), **you will need to configure a self hosted integration runtime to connect to it**.
@@ -131,6 +131,8 @@ To create and run a new scan, follow these steps:
 
         :::image type="content" source="media/register-scan-salesforce/scan.png" alt-text="scan Salesforce" border="true":::
 
+1. Select **Test connection** to validate the settings (available when using Azure Integration Runtime).
+
 1. Select **Continue**.
 
 1. Choose your **scan trigger**. You can set up a schedule or ran the scan once.
diff --git a/articles/purview/register-scan-snowflake.md b/articles/purview/register-scan-snowflake.md
@@ -228,6 +228,8 @@ To create and run a new scan, follow these steps:
 
         :::image type="content" source="media/register-scan-snowflake/scan.png" alt-text="scan Snowflake" border="true":::
 
+1. Select **Test connection** to validate the settings (available when using Azure Integration Runtime).
+
 1. Select **Continue**.
 
 1. Select a **scan rule set** for classification. You can choose between the system default, existing custom rule sets, or [create a new rule set](create-a-scan-rule-set.md) inline. Check the [Classification](apply-classifications.md) article to learn more.
