Merge pull request #272838 from flang-msft/FXL---Broken-links-to-Redis-documentation-ado-27724445

Fxl---broken links to redis documentation-- ado 27724445

Author: prmerger-automator[bot]

articles/azure-cache-for-redis/cache-best-practices-performance.md

@@ -17,7 +17,7 @@ Fortunately, several tools exist to make benchmarking Redis easier. Two of the m
 
 ## How to use the redis-benchmark utility
 
-1. Install open source Redis server to a client VM you can use for testing. The redis-benchmark utility is built into the open source Redis distribution. Follow the [Redis documentation](https://redis.io/docs/getting-started/#install-redis) for instructions on how to install the open source image.
+1. Install open source Redis server to a client VM you can use for testing. The redis-benchmark utility is built into the open source Redis distribution. Follow the [Redis documentation](https://redis.io/docs/latest/operate/oss_and_stack/install/install-redis/) for instructions on how to install the open source image.
 
 1. The client VM used for testing should be _in the same region_ as your Azure Cache for Redis instance.
 

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

@@ -5,7 +5,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: overview
-ms.date: 09/18/2023
+ms.date: 04/19/2024
 ---
 
 # About Vector Embeddings and Vector Search in Azure Cache for Redis
@@ -20,7 +20,7 @@ For a tutorial on how to use Azure Cache for Redis and Azure OpenAI to perform v
 |--------- |:------------------:|:----------:|:---------:|:---------:|
 |Available | No          | No       |  Yes  | Yes (preview) |
 
-Vector search capabilities in Redis require [Redis Stack](https://redis.io/docs/about/about-stack/), specifically the [RediSearch](https://redis.io/docs/interact/search-and-query/) module. This capability is only available in the [Enterprise tiers of Azure Cache for Redis](./cache-redis-modules.md).
+Vector search capabilities in Redis require [Redis Stack](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/), specifically the [RediSearch](https://redis.io/docs/interact/search-and-query/) module. This capability is only available in the [Enterprise tiers of Azure Cache for Redis](./cache-redis-modules.md).
 
 ## What are vector embeddings?
 
@@ -76,7 +76,7 @@ Redis has a wide range of vector search capabilities through the [RediSearch mod
 - Support for both KNN (using `FLAT`) and ANN (using `HNSW`) indexing methods.
 - Vector storage in hash or JSON data structures
 - Top K queries
-- [Vector range queries](https://redis.io/docs/interact/search-and-query/search/vectors/#creating-a-vss-range-query) (i.e., find all items within a specific vector distance)
+- [Vector range queries](https://redis.io/docs/latest/develop/interact/search-and-query/advanced-concepts/vectors/#range-queries) (that is, find all items within a specific vector distance)
 - Hybrid search with [powerful query features](https://redis.io/docs/interact/search-and-query/) such as:
   - Geospatial filtering
   - Numeric and text filters

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

@@ -5,7 +5,7 @@ author: flang-msft
 ms.author: franlanglois
 ms.service: cache
 ms.topic: overview
-ms.date: 09/29/2023
+ms.date: 04/19/2024
 ---
 
 # What is Azure Cache for Redis?
@@ -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://docs.redis.com/latest/modules/redisearch/), [RedisBloom](https://docs.redis.com/latest/modules/redisbloom/), [RedisTimeSeries](https://docs.redis.com/latest/modules/redistimeseries/), and [RedisJSON](https://docs.redis.com/latest/modules/redisjson/). These modules add new data types and functionality to Redis.
+- **Redis Modules**: Enterprise tiers support [RediSearch](Link 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.
 
 You can scale your cache from the Basic tier up to Premium after it has been 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-cache-for-redis/monitor-cache-reference.md

@@ -96,13 +96,13 @@ The following list provides details and more information about the supported Azu
     - This metric is only emitted _from the geo-primary_ cache instance. On the geo-secondary instance, this metric has no value.
     - This metric is only available in the Premium tier for caches with geo-replication enabled.
   - Geo Replication Full Sync Event Finished
-    - Depicts the completion of full synchronization between geo-replicated caches. When you see lots of writes on geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See [this page](https://redis.io/docs/manual/replication/#how-redis-replication-works) for a more detailed explanation.
+    - Depicts the completion of full synchronization between geo-replicated caches. When you see lots of writes on geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See [this page](https://redis.io/docs/latest/operate/oss_and_stack/management/replication/#how-redis-replication-works) for a more detailed explanation.
     - The metric reports zero most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization.
     - This metric is only emitted _from the geo-secondary_ cache instance. On the geo-primary instance, this metric has no value.
     - This metric is only available in the Premium tier for caches with geo-replication enabled.
 
   - Geo Replication Full Sync Event Started
-    - Depicts the start of full synchronization between geo-replicated caches. When there are many writes in geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See [this page](https://redis.io/docs/manual/replication/#how-redis-replication-works) for a more detailed explanation.
+    - Depicts the start of full synchronization between geo-replicated caches. When there are many writes in geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See [this page](https://redis.io/docs/latest/operate/oss_and_stack/management/replication/#how-redis-replication-works) for a more detailed explanation.
     - The metric reports zero most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization.
     - The metric is only emitted _from the geo-secondary_ cache instance. On the geo-primary instance, this metric has no value.
     - The metric is only available in the Premium tier for caches with geo-replication enabled.

articles/azure-functions/functions-bindings-cache-trigger-redispubsub.md

@@ -8,7 +8,7 @@ ms.author: franlanglois
 ms.service: azure-functions
 ms.custom: devx-track-dotnet, devx-track-extended-java, devx-track-js, devx-track-python
 ms.topic: reference
-ms.date: 02/27/2024
+ms.date: 04/19/2024
 ---
 
 # RedisPubSubTrigger for Azure Functions (preview)
@@ -609,4 +609,4 @@ JSON string format
 - [Tutorial: Get started with Azure Functions triggers in Azure Cache for Redis](/azure/azure-cache-for-redis/cache-tutorial-functions-getting-started)
 - [Tutorial: Create a write-behind cache by using Azure Functions and Azure Cache for Redis](/azure/azure-cache-for-redis/cache-tutorial-write-behind)
 - [Redis connection string](functions-bindings-cache.md#redis-connection-string)
-- [Redis pub sub messages](https://redis.io/docs/manual/pubsub/)
+- [Redis pub sub messages](https://redis.io/docs/latest/develop/interact/pubsub/)