Merge pull request #289129 from MicrosoftDocs/main

10/24 11:00 AM IST Publish

Author: PhilKang0704

articles/azure-cache-for-redis/cache-overview.md

@@ -79,7 +79,7 @@ Consider the following options when choosing an Azure Cache for Redis tier:
 - **High availability**: Azure Cache for Redis provides multiple [high availability](cache-high-availability.md) options. It guarantees that a Standard, Premium, or Enterprise cache is available according to our [SLA](https://azure.microsoft.com/support/legal/sla/cache/v1_0/). The SLA only covers connectivity to the cache endpoints. The SLA doesn't cover protection from data loss. We recommend using the Redis data persistence feature in the Premium and Enterprise tiers to increase resiliency against data loss.
 - **Data persistence**: The Premium and Enterprise tiers allow you to persist the cache data to an Azure Storage account and a Managed Disk respectively. Underlying infrastructure issues might result in potential data loss. We recommend using the Redis data persistence feature in these tiers to increase resiliency against data loss. Azure Cache for Redis offers both RDB and AOF (preview) options. Data persistence can be enabled through Azure portal and CLI. For the Premium tier, see [How to configure persistence for a Premium Azure Cache for Redis](cache-how-to-premium-persistence.md).
 - **Network isolation**: Azure Private Link and Virtual Network (VNet) deployments provide enhanced security and traffic isolation for your Azure Cache for Redis. VNet allows you to further restrict access through network access control policies. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md) and [How to configure Virtual Network support for a Premium Azure Cache for Redis](cache-how-to-premium-vnet.md).
-- **Redis Modules**: Enterprise tiers support [RediSearch](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/search/), [RedisBloom](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/bloom/), [RedisTimeSeries](https://docs.redis.com/latest/modules/redistimeseries/), and [RedisJSON](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/json/). These modules add new data types and functionality to Redis.
+- **Redis Modules**: Enterprise tiers support [RediSearch](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/search/), [RedisBloom](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/bloom/), [RedisTimeSeries](https://redis.io/docs/latest/develop/data-types/timeseries/), and [RedisJSON](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/json/). These modules add new data types and functionality to Redis.
 
 You can scale your cache from the Basic tier up to Premium after it is created. Scaling down to a lower tier isn't supported currently. For step-by-step scaling instructions, see [How to Scale Azure Cache for Redis](cache-how-to-scale.md) and [How to scale - Basic, Standard, and Premium tiers](cache-how-to-scale.md#how-to-scale---basic-standard-and-premium-tiers).
 

articles/azure-vmware/vmware-cloud-foundations-license-portability.md

@@ -1306,6 +1306,9 @@ items:
     - name: Diagnose connectivity in Azure-SSIS IR
       href: ssis-integration-runtime-diagnose-connectivity-faq.md
       displayName: timeout, troubleshooting
+    - name: Azure Data Factory known issues
+      href: known-issues-troubleshoot-guide.md
+      displayName: troubleshooting
 - name: SAP knowledge center
   items:
   - name: Overview

articles/data-factory/TOC.yml

@@ -0,0 +1,34 @@
+---
+title: Azure Data Factory known issues
+description: Learn about the currently known issues with Azure Data Factory and their possible workarounds or resolutions.
+author: sveldurthi
+ms.author: sveldurthi
+ms.reviewer: brianwan
+ms.date: 10/02/2024
+ms.service: azure-data-factory
+ms.topic: conceptual
+---
+
+# Azure Data Factory known issues
+
+This page lists the known issues in Azure Data factory. Before submitting [an Azure support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest), review this list to see if the issue that you're experiencing is already known and being addressed.
+
+## Active known issues
+
+|ADF Component|Known Issue |Status|
+|:---------|:---------|:---------|
+|Snow Flake Connector Issue|[Intermittent data retrieval issue with LookUp using the Snowflake Connector V2](#intermittent-data-retrieval-issue-with-lookup-using-the-snowflake-connector-v2)|Has workaround|
+
+
+## Recently ADF Closed known issues
+
+|ADF Component|Issue|Status|Date Resolved|
+|---------|---------|---------|---------|
+
+
+### Intermittent data retrieval issue with LookUp using the Snowflake Connector v2
+
+Intermittently, lookup queries against Snowflake return no values even when results are expected. No errors are generated, and the lookup activity completes successfully. This issue has been observed with Managed VNet IR and SHIR.
+
+**Workaround**: Add an If-condition activity after the Lookup to check its output. If the Lookup returns data, proceed without further action. If no data is returned, re-execute the Lookup activity.
+:::image type="content" source="media/known-issue/snowflake-rcs.png" alt-text="Diagram of Snowflake v2 Known issue.":::

articles/data-factory/known-issues-troubleshoot-guide.md

@@ -74,10 +74,7 @@ In the gateway migration experience, you need to validate if your resource is ca
 
 ### Virtual network 
 
-* Gateway Subnet needs two or more prefixes for migration.
-* MaxGatewayCountInVnetReached – Reached maximum number of gateways that can be created in a Virtual Network. 
-
- You must create a second prefix in your Gateway Subnet for migration.
+MaxGatewayCountInVnetReached – Reached maximum number of gateways that can be created in a Virtual Network. 
 
 ## Next steps
 

articles/data-factory/media/known-issue/snowflake-rcs.png

@@ -5,7 +5,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: internet-peering
 ms.topic: how-to
-ms.date: 08/09/2023
+ms.date: 10/23/2024
 ---
 
 # Internet peering for Azure Peering Service partner walkthrough
@@ -161,9 +161,9 @@ When your customers onboard to Peering Service, customers must follow the steps
 
 **Q.**	I need to set the prefix limit, how many routes Microsoft would be announcing?
 
-**A.** Microsoft announces roughly 280 prefixes on internet, and it may increase by 10-15% in future. So, a safe limit of 400-500 can be good to set as “Max prefix count”
+**A.** Microsoft announces roughly 280 prefixes on internet, and it might increase by 10-15% in future. So, a safe limit of 400-500 can be good to set as “Max prefix count”
 
-**Q.** Will Microsoft re-advertise the Peer prefixes to the Internet?
+**Q.** Will Microsoft readvertise the Peer prefixes to the Internet?
 
 **A.** No.
 

articles/expressroute/gateway-migration.md

@@ -72,7 +72,7 @@ The first option is to connect from within the cluster. This option uses the def
               expirationSeconds: 86400
       - name: trust-bundle
         configMap:
-          name: aio-ca-trust-bundle-test-only # Default root CA cert
+          name: azure-iot-operations-aio-ca-trust-bundle # Default root CA cert
     ```
 
 1. Use `kubectl apply -f client.yaml` to deploy the configuration. It should only take a few seconds to start.