Merge pull request #94952 from sgsshankar/sgsshankar-msft-snowflake-patch-2

Updated Data Strategies to reflect Snowflake

Author: Jak-MS

articles/data-factory/connector-snowflake.md

@@ -42,7 +42,7 @@ If your data store is located inside an on-premises network, an Azure virtual ne
 
 If your data store is a managed cloud data service, you can use the Azure Integration Runtime. If the access is restricted to IPs that are approved in the firewall rules, you can add [Azure Integration Runtime IPs](azure-integration-runtime-ip-addresses.md) to the allowed list.
 
-The Snowflake account that is used for Source or Sink should have the necessary `USAGE` access on the Database and Read / Write access on Schema and the Tables/Views under it. In addition, it should also have `CREATE STAGE` on the schema to be able to create the External stage with SAS URI.
+The Snowflake account that is used for Source or Sink should have the necessary `USAGE` access on the database and read/write access on schema and the tables/views under it.. In addition, it should also have `CREATE STAGE` on the schema to be able to create the External stage with SAS URI.
 
 The following Account properties values must be set
 

articles/data-factory/data-access-strategies.md

@@ -41,7 +41,7 @@ This should work in many scenarios, and we do understand that a unique Static IP
 For more information about supported network security mechanisms on data stores in Azure Integration Runtime and Self-hosted Integration Runtime, see below two tables.
 * **Azure Integration Runtime**
 
-    | Data Stores                  | Supported Network Security Mechanism on Data Stores | Private Link     | Trusted Service     | Static IP range | Service Tags | Allow Azure Services |
+   | Data Stores                  | Supported Network Security Mechanism on Data Stores | Private Link     | Trusted Service     | Static IP range | Service Tags | Allow Azure Services |
     |------------------------------|-------------------------------------------------------------|---------------------|-----------------|--------------|----------------------|-----------------|
     | Azure PaaS Data stores       | Azure Cosmos DB                                     | Yes              | -                   | Yes             | -            | Yes                  |
     |                              | Azure Data Explorer                                 | -                | -                   | Yes*            | Yes*         | -                    |
@@ -52,9 +52,11 @@ For more information about supported network security mechanisms on data stores
     |                              | Azure SQL DB,  Azure Synapse Analytics), SQL   Ml  | Yes (only Azure SQL DB/DW)        | -                   | Yes             | -            | Yes                  |
     |                              | Azure Key Vault (for fetching secrets/   connection string) | yes      | Yes                 | Yes             | -            | -                    |
     | Other PaaS/ SaaS Data stores | AWS   S3, SalesForce, Google Cloud Storage, etc.    | -                | -                   | Yes             | -            | -                    |
+    |                               | Snowflake                                         |   Yes             |   -                 | Yes             | -         | -                         |
     | Azure IaaS                   | SQL Server, Oracle,   etc.                          | -                | -                   | Yes             | Yes          | -                    |
-    | On-premises IaaS              | SQL Server, Oracle,   etc.                          | -                | -                   | Yes             | -            | -                    |
-
+    | On-premises IaaS              | SQL Server, Oracle,   etc.                          | -                | -                   | Yes             | -            | - 
+    
+    
     **Applicable only when Azure Data Explorer is virtual network injected, and IP range can be applied on NSG/ Firewall.*
 
 * **Self-hosted Integration Runtime (in VNet/on-premises)**