fixing links

fix broken links

updated folder names for links

refining TOC

structure fixes

updated for new AMR location

TOC, index fixes

fixes for TOC

Fixed TOC

file moves try 1

Author: flang-msft

articles/azure-cache-for-redis/.openpublishing.redirection.redis-cache.json

@@ -261,8 +261,8 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/azure-cache-for-redis/managed-redis/managed-redis-configure-role-based-access-control.md",
-            "redirect_url": "/azure/azure-cache-for-redis/managed-redis/managed-redis-entra-for-authentication",
+            "source_path_from_root": "/articles/azure-cache-for-redis/redis/configure-role-based-access-control.md",
+            "redirect_url": "/azure/azure-cache-for-redis/redis/entra-for-authentication",
             "redirect_document_id": false
         }
     ]

articles/azure-cache-for-redis/TOC.yml

@@ -5,200 +5,60 @@
   expanded: true
   items:
   - name: What's new
-    href: managed-redis/managed-redis-whats-new.md
+    href: cache-whats-new.md
   - name: Quickstarts
     expanded: false
     items:
     - name: Create a cache
       items: 
       - name: Create an Azure Managed Redis instance
-        href: quickstart-create-managed-redis.md  
+        href: /redis/quickstart-create-managed-redis.md  
       - name: Create an Azure Cache for Redis instance in the Basic, Standard and Premium tiers
-        href: quickstart-create-redis.md
+        href: /redis/quickstart-create-redis.md
       - name: Create an Azure Cache for Redis instance in the Enterprise tiers
-        href: quickstart-create-redis-enterprise.md    
+        href: /redis/quickstart-create-redis-enterprise.md    
       - name: Create and manage with Azure PowerShell
-        href: cache-how-to-manage-redis-cache-powershell.md
+        href: /redis/cache-how-to-manage-redis-cache-powershell.md
       - name: Create and manage with Azure CLI
         href: scripts/create-manage-cache.md
       - name: Create and manage premium cache with Azure CLI
         href: scripts/create-manage-premium-cache-cluster.md
       - name: Create Redis cache - Bicep
         displayName: ARM, Resource Manager, Template
-        href: cache-redis-cache-bicep-provision.md
+        href: /redis/cache-redis-cache-bicep-provision.md
       - name: Create Redis cache - ARM template
         displayName: Resource Manager
-        href: cache-redis-cache-arm-provision.md
+        href: /redis/cache-redis-cache-arm-provision.md
 
     - name: Use a cache
       expanded: false
       items:
       - name: ASP.NET app
-        href: cache-web-app-howto.md
+        href: /redis/web-app-howto.md
       - name: ASP.NET Core app
-        href: cache-web-app-aspnet-core-howto.md
+        href: /redis/web-app-aspnet-core-howto.md
       - name: .NET Core app
-        href: cache-dotnet-core-quickstart.md
+        href: /redis/dotnet-core-quickstart.md
       - name: .NET app
         href: cache-dotnet-how-to-use-azure-redis-cache.md
       - name: Java app
-        href: cache-java-get-started.md
+        href: /redis/java-get-started.md
       - name: Java app with JCache
-        href: cache-java-redisson-get-started.md
+        href: /redis/java-redisson-get-started.md
       - name: Node.js app
-        href: cache-nodejs-get-started.md
+        href: /redis/nodejs-get-started.md
       - name: Python app
-        href: cache-python-get-started.md
+        href: /redis/python-get-started.md
       - name: Go app
-        href: cache-go-get-started.md
+        href: /redis/go-get-started.md
       - name: Rust app
-        href: cache-rust-get-started.md
+        href: /redis/rust-get-started.md
 
-- name: Azure Managed Redis 
-  expanded: true
-  items:
-  - name: About Azure Managed Redis
-    href: managed-redis/managed-redis-overview.md
-
-  - name: Deploy and configure
-    items:
-    - name: Upgrade to a new version
-      href: managed-redis/managed-redis-how-to-upgrade.md
-    - name: Save with reservations 
-      href: managed-redis/managed-redis-reserved-pricing.md
-    - name: Migrate to Azure Cache for Redis
-      href: managed-redis/managed-redis-migration-guide.md
-    - name: Planning FAQs
-      href: managed-redis/managed-redis-planning-faq.yml
-    - name: Redis modules 
-      href: managed-redis/managed-redis-redis-modules.md
-    - name: Common caching patterns
-      href: /azure/architecture/best-practices/caching?toc=/azure/redis-cache/toc.json
-    - name: Azure Managed Redis architecture
-      href: managed-redis/managed-redis-architecture.md
-    - name: Create and manage with Azure PowerShell
-      href: cache-how-to-manage-redis-cache-powershell.md
-    - name: Use Azure CLI
-      items:
-      - name: Overview
-        href: cli-samples.md
-      - name: Create and manage a cache
-        href: scripts/create-manage-cache.md
-      - name: Create and manage a premium cache
-        href: scripts/create-manage-premium-cache-cluster.md
-
-  - name: Development and client libraries
-    items:
-    - name: Development FAQs
-      href: managed-redis/managed-redis-development-faq.yml
-    - name: Client libraries best practices
-      href: managed-redis/managed-redis-best-practices-client-libraries.md
-    - name: Development best practice
-      href: managed-redis/managed-redis-best-practices-development.md
-    - name: Memory management best practice
-      href: managed-redis/managed-redis-best-practices-memory-management.md
-    - name: Performance testing best practice
-      href: managed-redis/managed-redis-best-practices-performance.md
-    - name: Azure Managed Redis tiers best practices
-      href: managed-redis/managed-redis-best-practices-managed-cache.md
-    - name: Vector Search
-      href: managed-redis/managed-redis-overview-vector-similarity.md
-    - name: Connection resilience best practices
-      href: managed-redis/managed-redis-best-practices-connection.md
-    - name: Use Azure Functions triggers and bindings
-      items:
-      - name: Create a simple Function app for Redis triggers 
-        href: cache-tutorial-functions-getting-started.md 
-
-  - name: Logs and monitoring
-    items:
-    - name: Monitor Cache for Redis
-      href: monitor-cache.md
-    - name: Monitor using diagnostic settings
-      href: managed-redis/managed-redis-monitor-diagnostic-settings.md
-    - name: List of Redis metrics
-      href: monitor-cache-reference.md#metrics
-
-  - name: Scaling and performance
-    items:
-    - name: Change the size and tier of a cache
-      href: managed-redis/managed-redis-how-to-scale.md
-    - name: Development best practices
-      href: managed-redis/managed-redis-best-practices-development.md
-    - name: Scaling best practices
-      href: managed-redis/managed-redis-best-practices-scale.md
-    - name: Server load management best practice
-      href: managed-redis/managed-redis-best-practices-server-load.md
-    - name: Performance testing
-      href: managed-redis/managed-redis-best-practices-performance.md
-    - name: Kubernetes-hosted client applications best practices
-      href: managed-redis/managed-redis-best-practices-kubernetes.md
-
-  - name: Authentication and authorization
-    items:
-    - name: Microsoft Entra ID for authentication
-      href: managed-redis/managed-redis-entra-for-authentication.md
-
-  - name: Security and networking
-    items:
-    - name: Using TLS with a managed cache
-      href: managed-redis/managed-redis-tls-configuration.md
-    - name: Connect to cache using Private Link
-      href: managed-redis/managed-redis-private-link.md
-    - name: Security controls by Azure Policy
-      displayName: regulatory, compliance, standards, domains
-      href: ./security-controls-policy.md
-    - name: Security baseline
-      href: /security/benchmark/azure/baselines/azure-cache-for-redis-security-baseline?toc=/azure/azure-cache-for-redis/TOC.json
-
-  - name: Cache management 
-    items:
-    - name: Configure in Azure portal
-      href: managed-redis/managed-redis-configure.md
-    - name: Import/Export data
-      href: managed-redis/managed-redis-how-to-import-export-data.md
-    - name: Configure disk encryption 
-      href: managed-redis/managed-redis-how-to-encryption.md
-    - name: Configure redis-cli access
-      href: managed-redis/managed-redis-how-to-redis-cli-tool.md
-    - name: Management FAQs
-      href: managed-redis/managed-redis-management-faq.yml
-    - name: Azure Functions
-      href: ../azure-functions/functions-bindings-cache.md
-
-  - name: Resiliency
-    items:
-    - name: Persist your cache with Redis data persistence 
-      href: managed-redis/managed-redis-how-to-persistence.md
-    - name: Set up Enterprise active geo-replication
-      href: managed-redis/managed-redis-how-to-active-geo-replication.md
-    - name: Configure your cache for high availability
-      href: managed-redis/managed-redis-high-availability.md
-    - name: Failover and patching
-      href: managed-redis/managed-redis-failover.md
-    - name: Migrate to availability zone support
-      href: ../reliability/migrate-cache-redis.md
-
-  - name: Diagnose and troubleshoot
-    items:
-    - name: Troubleshoot connectivity issues
-      href: managed-redis/managed-redis-troubleshoot-connectivity.md
-    - name: Troubleshoot latency and timeouts
-      href: managed-redis/managed-redis-troubleshoot-timeouts.md
-    - name: Troubleshoot client 
-      href: managed-redis/managed-redis-troubleshoot-client.md
-    - name: Troubleshoot Redis server
-      href: managed-redis/managed-redis-troubleshoot-server.md
-    - name: Troubleshoot data loss
-      href: managed-redis/managed-redis-troubleshoot-data-loss.md
-    - name: Troubleshooting FAQs
-      href: managed-redis/managed-redis-monitor-troubleshoot-faq.yml
-
 - name: Migration 
   expanded: true
   items:
   - name: Migrate to Azure Managed Redis
-    href: migrate/migrate-overview.md
+    href: /redis/migrate/migrate-overview.md
 
 - name: Azure Cache for Redis 
   expanded: false
@@ -223,9 +83,9 @@
     - name: Caching architecture
       href: /azure/architecture/best-practices/caching?toc=/azure/redis-cache/toc.json
     - name: Create and manage with Azure PowerShell
-      href: cache-how-to-manage-redis-cache-powershell.md
+      href: /redis/how-to-manage-redis-cache-powershell.md
     - name: Connect an AKS application to a cache
-      href: cache-tutorial-aks-get-started.md
+      href: /redis/tutorial-aks-get-started.md
     - name: Use Azure CLI
       items:
       - name: Overview
@@ -249,22 +109,19 @@
       href: cache-best-practices-performance.md
     - name: Kubernetes-hosted client applications best practices
       href: cache-best-practices-kubernetes.md
-# temporarily added to build
-#    - name: Enterprise tiers best practices
-#      href: cache-best-practices-enterprise-tiers.md
     - name: Vector Search
-      href: cache-overview-vector-similarity.md
+      href: /redis/overview-vector-similarity.md
     - name: Connection resilience best practices
       href: cache-best-practices-connection.md
     - name: Use Azure Functions triggers and bindings
       items:
       - name: Create a simple Function app for Redis triggers 
-        href: cache-tutorial-functions-getting-started.md
+        href: /redis/tutorial-functions-getting-started.md
 
   - name: Logs and monitoring
     items:
     - name: Monitor Cache for Redis
-      href: monitor-cache.md
+      href: /redis/monitor-cache.md
     - name: Monitor using insights
       href: cache-insights-overview.md
     - name: Monitor using diagnostic settings
@@ -379,62 +236,60 @@
   - name: Use Azure Functions triggers and bindings
     items:
     - name: Create a simple Function app for Redis triggers
-      href: cache-tutorial-functions-getting-started.md
+      href: /redis/tutorial-functions-getting-started.md
     - name: Using Azure Functions to create a write-behind cache
-      href: cache-tutorial-write-behind.md
+      href: /redis/tutorial-write-behind.md
   - name: Use Azure Kubernetes Service with a cache
     items:
     - name: Connect an AKS application to a cache
-      href: cache-tutorial-aks-get-started.md
+      href: /redis/tutorial-aks-get-started.md
     - name: Use active geo-replication with an AKS-hosted application
-      href: cache-tutorial-active-replication.md
+      href: /redis/tutorial-active-replication.md
     - name: Kubernetes-hosted client applications best practices
-      href: managed-redis/managed-redis-best-practices-kubernetes.md
+      href: cache-best-practices-kubernetes.md
   - name: Artificial Intelligence
     items:
       - name: Vector search concepts
-        href: cache-overview-vector-similarity.md
+        href: /redis/overview-vector-similarity.md
       - name: Vector similarity search
-        href: cache-tutorial-vector-similarity.md
+        href: /redis/tutorial-vector-similarity.md
       - name: Semantic caching
-        href: cache-tutorial-semantic-cache.md
+        href: /redis/tutorial-semantic-cache.md
   - name: ASP.NET
     items:
     - name: Use ASP.NET core output cache
-      href: cache-aspnet-core-output-cache-provider.md
+      href: /redis/aspnet-core-output-cache-provider.md
     - name: Use session state provider
-      href: cache-aspnet-session-state-provider.md
+      href: /redis/aspnet-session-state-provider.md
     - name: Use output cache provider
-      href: cache-aspnet-output-cache-provider.md
+      href: /redis/aspnet-output-cache-provider.md
   - name: Java Spring
     items:
     - name: Use Spring Boot Initializer
       href: /azure/developer/java/spring-framework/configure-spring-boot-initializer-java-app-with-redis-cache
   - name: Azure Event Grid
     items:
     - name: Route events with Azure portal  
-      href: cache-event-grid-quickstart-portal.md
+      href: /redis/event-grid-quickstart-portal.md
     - name: Route events with Azure CLI 
-      href: cache-event-grid-quickstart-cli.md
+      href: /redis/event-grid-quickstart-cli.md
     - name: Route events with PowerShell 
-      href: cache-event-grid-quickstart-powershell.md
+      href: /redis/event-grid-quickstart-powershell.md
   - name: Create leaderboards
-    href: cache-web-app-cache-aside-leaderboard.md
+    href: /redis/web-app-cache-aside-leaderboard.md
   - name: Deploy a machine learning model 
-    href: cache-ml.md
+    href: /redis/ml.md
   - name: Create Web App with Redis cache - Bicep
     displayName: ARM, Resource Manager, Template
-    href: cache-web-app-bicep-with-redis-cache-provision.md
+    href: /redis/web-app-bicep-with-redis-cache-provision.md
   - name: Create Web App with Redis cache - ARM template
     displayName: Resource Manager
-    href: cache-web-app-arm-with-redis-cache-provision.md
+    href: /redis/web-app-arm-with-redis-cache-provision.md
 
 - name: Reference
   items:
     - name: Azure Managed Redis
       items:
-        - name: Azure Cache for Redis samples
-          href: cache-redis-samples.md
         - name: .NET
           href: /dotnet/api/overview/azure/resourcemanager.redisenterprise-readme
         - name: Java
@@ -467,7 +322,7 @@
         - name: Redis commands
           href: https://redis.io/commands#
         - name: Monitoring data reference
-          href: monitor-cache-reference.md
+          href: /redis/monitor-cache-reference.md
 
 - name:  Resources
   items:

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

@@ -30,7 +30,7 @@ Fortunately, several tools exist to make benchmarking Redis easier. Two of the m
 
 1. `Redis-benchmark` uses port 6379 by default. Use the `-p` parameter to override this setting. You need to do use `-p`, if you're using the SSL/TLS (port 6380) or are using the Enterprise tier (port 10000).
 
-1. If you're using an Azure Cache for Redis instance that uses [clustering](cache-how-to-scale.md), you need to add the `--cluster` parameter to your `redis-benchmark` command. Enterprise tier caches using the Enterprise [Clustering](managed-redis/managed-redis-architecture.md#clustering) can be treated as nonclustered caches and don't need this setting.
+1. If you're using an Azure Cache for Redis instance that uses [clustering](cache-how-to-scale.md), you need to add the `--cluster` parameter to your `redis-benchmark` command. Enterprise tier caches using the Enterprise [Clustering](redis/architecture.md#clustering) can be treated as nonclustered caches and don't need this setting.
 
 1. Launch `redis-benchmark` from the CLI or shell of the VM. For instructions on how to configure and run the tool, see the [redis-benchmark documentation](https://redis.io/docs/management/optimization/benchmarks/) and the [redis-benchmark examples](#redis-benchmark-examples) sections.
 
@@ -176,7 +176,7 @@ memtier_benchmark -h {your-cache-name}.{region}.redis.azure.net -p 10000 -a {you
 
 #### Enterprise & Enterprise Flash tiers
 
-The Enterprise and Enterprise Flash tiers offer a choice of cluster policy: _Enterprise_ and _OSS_. Enterprise cluster policy is a simpler configuration that doesn't require the client to support clustering. OSS cluster policy, on the other hand, uses the [Redis cluster protocol](https://redis.io/docs/management/scaling) to support higher throughputs. We recommend using OSS cluster policy in most cases. For more information, see [Clustering](managed-redis/managed-redis-architecture.md#clustering) . Benchmarks for both cluster policies are shown in the following tables.
+The Enterprise and Enterprise Flash tiers offer a choice of cluster policy: _Enterprise_ and _OSS_. Enterprise cluster policy is a simpler configuration that doesn't require the client to support clustering. OSS cluster policy, on the other hand, uses the [Redis cluster protocol](https://redis.io/docs/management/scaling) to support higher throughputs. We recommend using OSS cluster policy in most cases. For more information, see [Clustering](redis/architecture.md#clustering) . Benchmarks for both cluster policies are shown in the following tables.
 
 The following configuration was used to benchmark throughput for the Enterprise and Enterprise flash tiers:
 
@@ -213,7 +213,7 @@ redis-benchmark -h yourcache.region.redisenterprise.cache.azure.net -p 10000 -a
 
 #### Enterprise & Enterprise Flash Tiers - Scaled Out
 
-In addition to scaling up by moving to larger cache size, you can boost performance by [scaling out](cache-how-to-scale.md#how-to-scale-up-and-out---enterprise-and-enterprise-flash-tiers). In the Enterprise tiers, scaling out is called increasing the _capacity_ of the cache instance. A cache instance by default has capacity of two--meaning a primary and replica node. An Enterprise cache instance with a capacity of four indicates that the instance was scaled out by a factor of two. Scaling out provides access to more memory and vCPUs. Details on how many vCPUs are used by the core Redis process at each cache size and capacity can be found at the [Sharding configuration](managed-redis/managed-redis-architecture.md#sharding-configuration). Scaling out is most effective when using the OSS cluster policy.
+In addition to scaling up by moving to larger cache size, you can boost performance by [scaling out](cache-how-to-scale.md#how-to-scale-up-and-out---enterprise-and-enterprise-flash-tiers). In the Enterprise tiers, scaling out is called increasing the _capacity_ of the cache instance. A cache instance by default has capacity of two--meaning a primary and replica node. An Enterprise cache instance with a capacity of four indicates that the instance was scaled out by a factor of two. Scaling out provides access to more memory and vCPUs. Details on how many vCPUs are used by the core Redis process at each cache size and capacity can be found at the [Sharding configuration](redis/architecture.md#sharding-configuration). Scaling out is most effective when using the OSS cluster policy.
 
 The following tables show the `GET` requests per second at different capacities, using SSL and a 1-kB value size.