Merge pull request #245259 from linda33wj/main

Update SHIR & connector articles

Author: prmerger-automator[bot]

articles/purview/manage-integration-runtimes.md

@@ -7,7 +7,7 @@ ms.service: purview
 ms.subservice: purview-data-map
 ms.custom: devx-track-extended-java
 ms.topic: how-to
-ms.date: 05/08/2023
+ms.date: 07/18/2023
 ---
 
 # Create and manage a self-hosted integration runtime
@@ -147,7 +147,8 @@ Make sure the account has the permission of Log-on as a service. Otherwise self-
 You can associate a self-hosted integration runtime with multiple on-premises machines or virtual machines in Azure. These machines are called nodes. You can have up to four nodes associated with a self-hosted integration runtime. The benefits of having multiple nodes are:
 
 - Higher availability of the self-hosted integration runtime so that it's no longer the single point of failure for scan. This availability helps ensure continuity when you use up to four nodes.
-- Run more concurrent scans. Each self-hosted integration runtime can empower many scans at the same time, auto determined based on the machine's CPU/memory. You can install more nodes if you have more concurrency need. Each scan will be executed on one of the nodes. Having more nodes doesn't improve the performance of a single scan execution.
+- Run more concurrent scans. Each self-hosted integration runtime can empower many scan runs at the same time, auto determined based on the machine's CPU/memory. You can install more nodes if you have more concurrency need. 
+- When scanning sources like Azure Blob, Azure Data Lake Storage Gen1, Azure Data Lake Storage Gen2 and Azure Files, each scan run can leverage all those nodes to boost the scan performance. For other sources, scan will be executed on one of the nodes.
 
 You can associate multiple nodes by installing the self-hosted integration runtime software from [Download Center](https://www.microsoft.com/download/details.aspx?id=39717). Then, register it by using the same authentication key.
 

articles/purview/register-scan-power-bi-tenant.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 06/08/2023
+ms.date: 07/17/2023
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -188,7 +188,7 @@ Use any of the following deployment checklists during the setup or for troublesh
    3. Under **Authentication**, **Allow public client flows** is enabled.
 
 2. Review network configuration and validate if:
-   1. A [private endpoint for Power BI tenant](/power-bi/enterprise/service-security-private-links) is deployed.
+   1. If your Power BI doesn't allow public access, make sure [private endpoint for Power BI tenant](/power-bi/enterprise/service-security-private-links) is deployed.
    2. All required [private endpoints for Microsoft Purview](./catalog-private-link-end-to-end.md) are deployed.
    3. Network connectivity from Self-hosted runtime to Power BI tenant is enabled. The following endpoints must be reachable from self-hosted runtime VM:
       - `*.powerbi.com` 

articles/purview/register-scan-snowflake.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 06/12/2023
+ms.date: 07/17/2023
 ms.custom: template-how-to
 ---
 
@@ -37,13 +37,18 @@ When scanning Snowflake source, Microsoft Purview supports:
     - Tasks
     - Sequences
 
-- Fetching static lineage on assets relationships among tables, views, and streams.
+- Fetching static lineage on assets relationships among tables, views, streams, and stored procedures.
 
-When setting up scan, you can choose to scan one or more Snowflake database(s) entirely, or further scope the scan to a subset of schemas matching the given name(s) or name pattern(s).
+For stored procedures, you can choose the level of details to extract on [scan settings](#scan). Stored procedure lineage is supported for Snowflake Scripting (SQL) and JavaScript languages, and generated based on the procedure definition.
+
+When setting up scan, you can choose to scan one or more Snowflake database(s) entirely based on the given name(s) or name pattern(s), or further scope the scan to a subset of schemas matching the given name(s) or name pattern(s).
 
 ### Known limitations
 
-When object is deleted from the data source, currently the subsequent scan won't automatically remove the corresponding asset in Microsoft Purview.
+- When object is deleted from the data source, currently the subsequent scan won't automatically remove the corresponding asset in Microsoft Purview.
+- Stored procedure lineage is not supported for the following patterns:
+    - Stored procedure defined in Java, Python and Scala languages.
+    - Stored procedure using SQL [EXECUTE IMMEDIATE](https://docs.snowflake.com/en/sql-reference/sql/execute-immediate) with static SQL query as variable.
 
 ## Prerequisites
 
@@ -145,7 +150,7 @@ On the **Register sources (Snowflake)** screen, follow these steps:
 
 1. Enter a **Name** that the data source will be listed within the Catalog.
 
-1. Enter the **server** URL used to connect to the Snowflake account in the form of `<account_identifier>.snowflakecomputing.com`, for example, `xy12345.east-us-2.azure.snowflakecomputing.com`. Learn more about Snowflake [account identifier](https://docs.snowflake.com/en/user-guide/admin-account-identifier.html#).
+1. Enter the **server** URL used to connect to the Snowflake account in the form of `<account_identifier>.snowflakecomputing.com`, for example, `orgname-accountname.snowflakecomputing.com`. Learn more about Snowflake [account identifier](https://docs.snowflake.com/en/user-guide/admin-account-identifier.html#).
 
 1. Select a collection or create a new one (Optional)
 
@@ -208,11 +213,14 @@ To create and run a new scan, follow these steps:
 
     1. **Stored procedure details**: Controls the number of details imported from stored procedures:
 
-        - Signature: The name and parameters of stored procedures.
+        - Signature (default): The name and parameters of stored procedures.
         - Code, signature: The name, parameters and code of stored procedures.
         - Lineage, code, signature: The name, parameters and code of stored procedures, and the data lineage derived from the code.
         - None: Stored procedure details aren't included.
 
+        > [!Note]
+        > If you use Self-hosted Integration Runtime for scan, customized setting other than the default Signature is supported since version 5.30.8541.1. The earlier versions always extract the name and parameters of stored procedures.
+
     1. **Maximum memory available** (applicable when using self-hosted integration runtime): Maximum memory (in GB) available on customer's VM to be used by scanning processes. It's dependent on the size of Snowflake source to be scanned.
 
         > [!Note]