Fix broken links

Author: flang-msft

articles/redis/administration.md

@@ -94,7 +94,7 @@ Each SKU of Azure Managed Redis is configured to run a specific number of Redis
 |     1920 *     |       64/48      |         256/192         |          -         |           -        |
 |     4500 *     |       144/96      |        -         |          -         |           -        |
 
-  * These tiers are in Public Preview.
+  \* These tiers are in Public Preview.
 
 ## Running without high availability mode enabled
 
@@ -106,7 +106,7 @@ On each Azure Managed Redis Instance, approximately 20% of the available memory
 
 ## Scaling down
 
-Scaling down is not currently supported on Azure Managed redis. For more information, see [Prerequisites/limitations of scaling Azure Managed Redis](how-to-scale.md#prerequisiteslimitations-of-scaling-azure-managed-redis).
+Scaling down is not currently supported on Azure Managed redis. For more information, see [Limitations of scaling Azure Managed Redis](how-to-scale.md#limitations-of-scaling-azure-managed-redis).
 
 ## Flash Optimized tier
 

articles/redis/architecture.md

@@ -50,14 +50,16 @@ The NuGet package downloads and adds the required assembly references and adds t
 </caching>
 ```
 
+[aad](/azure/azure-cache-for-redis/cache-configure?tabs=access-keys)
+
 Configure the attributes in the first column with the values from your cache in the Microsoft Azure portal. Also, configure the other values you want. For instructions on accessing your cache properties, see  [Configure Azure Managed Redis settings](configure.md#configure-azure-managed-redis-settings).
 
 | Attribute | Type | Default | Description |
 | --------- | ---- | ------- | ----------- |
 | _host* | string | "localhost" | The Redis server IP address or host name |
 | _port_ | positive integer | 6379 (non-TLS/SSL)<br/>6380 (TLS/SSL)<br/>10000 for Redis Enterprise and Azure Managed Redis | Redis server port |
 | _accessKey_ | string | "" | Redis server password when Redis authorization is enabled. The value is an empty string by default, which means the session state provider doesn't use any password when it connects to Redis server. **If your Redis server is in a publicly accessible network like Azure Cache for Redis, be sure to enable Redis authorization to improve security, and provide a secure password.** |
-| _ssl_ | boolean | **false** | Whether to connect to Redis server via TLS. This value is **false** by default because Redis doesn’t support TLS by default. **If you're using Azure Cache for Redis, which supports SSL by default, be sure to set this value to true to improve security.**<br/><br/>The non-TLS port is disabled by default for new caches. Specify **true** for this setting to use the non-TLS port. For more information about enabling the non-TLS port, see the [Access Ports](configure.md#access-ports) section in the [Configure a cache](configure.md) article. |
+| _ssl_ | boolean | **false** | Whether to connect to Redis server via TLS. This value is **false** by default because Redis doesn’t support TLS by default. **If you're using Azure Cache for Redis, which supports SSL by default, be sure to set this value to true to improve security.**<br/><br/>The non-TLS port is disabled by default for new caches. Specify **true** for this setting to use the non-TLS port. For more information about enabling the non-TLS port, see the [Access Ports](/azure/azure-cache-for-redis/cache-configure.md#access-ports). |
 | _databaseIdNumber_ | positive integer | 0 | _This attribute can be specified only through either web.config or AppSettings._<br/><br/>Specify which Redis database to use. |
 | _connectionTimeoutInMilliseconds_ | positive integer | Provided by StackExchange.Redis | Used to set _ConnectTimeout_ when creating StackExchange.Redis.ConnectionMultiplexer. |
 | _operationTimeoutInMilliseconds_ | positive integer | Provided by StackExchange.Redis | Used to set _SyncTimeout_ when creating StackExchange.Redis.ConnectionMultiplexer. |

articles/redis/aspnet-output-cache-provider.md

@@ -23,10 +23,9 @@ Set an expiration value on your keys. An expiration removes keys proactively ins
 
 ## Monitor memory usage
 
-Consider adding alerting on "Used Memory Percentage" metric to ensure that you don't run out of memory and have the chance to scale your cache before seeing issues. If your "Used Memory Percentage" is consistently over 75%, consider increasing your memory by scaling to a higher tier. See [here](architecture.md#sharding-configuration) for information on tiers.
+Consider adding alerting on "Used Memory Percentage" metric to ensure that you don't run out of memory and have the chance to scale your cache before seeing issues. If your "Used Memory Percentage" is consistently over 75%, consider increasing your memory by scaling to a higher tier. For information on tiers, see [Architecture](architecture.md#sharding-configuration) for information on tiers.
 
 ## Next steps
 
 - [Best practices for development](best-practices-development.md)
-- [maxmemory-reserved setting](configure.md#memory-policies)
 - [Best practices for scaling](best-practices-scale.md)

articles/redis/best-practices-memory-management.md

@@ -19,11 +19,6 @@ sections:
         answer: |
           Using TLS is recommended as a best practice across virtually all Redis use-cases. The option to connect without TLS is included for backwards compatibility purposes. 
           
-          >[!NOTE]
-          >The non-TLS port is disabled by default for new Azure Managed Redis instances. If your client doesn't support TLS, then you must enable the non-TLS port by following the directions in the [Access ports](configure.md#access-ports) section of the [Configure a cache in Azure Managed Redis](configure.md) article.
-          >
-          >
-          
       - question: |
           What are some production best practices?
         answer: |
@@ -151,7 +146,7 @@ sections:
         answer: |
           Different SKUs might have different limits for client connections, memory, and bandwidth. While each size of cache allows up to some number of connections, each connection to Redis has overhead associated with it. An example of such overhead would be CPU and memory usage because of TLS/SSL encryption. The maximum connection limit for a given cache size assumes a lightly loaded cache. If load from connection overhead plus load from client operations exceeds capacity for the system, the cache can experience capacity issues even if you don't exceed the connection limit for the current cache size.
           
-          For more information about the different connections limits for each tier, see [Azure Managed Redis pricing](https://azure.microsoft.com/pricing/details/cache/). For more information about connections and other default configurations, see [Default Redis server configuration](configure.md#default-redis-server-configuration).
+          For more information about the different connections limits for each tier, see [Azure Managed Redis pricing](https://azure.microsoft.com/pricing/details/cache/).
           
 additionalContent: |
 

articles/redis/management-faq.yml

@@ -117,7 +117,7 @@ The following table helps describe some of the features supported by tier:
 >
 
 > [!NOTE]
-> Scaling down support is limited in some situations. For more information, see [Prerequisites/limitations of scaling Azure Managed Redis](how-to-scale.md#prerequisiteslimitations-of-scaling-azure-managed-redis).
+> Scaling down support is limited in some situations. For more information, see [Limitations of scaling Azure Managed Redis](how-to-scale.md#limitations-of-scaling-azure-managed-redis).
 >
 
 ### Other considerations when picking a tier

articles/redis/overview.md

@@ -83,7 +83,7 @@ Additionally, **RediSearch** can function as a secondary index, expanding your c
 You can use **RediSearch** is used in a wide variety of use-cases, including real-time inventory, enterprise search, and in indexing external databases. [For more information, see the RediSearch documentation page](https://redis.io/search/).
 
 >[!IMPORTANT]
-> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering](architecture.md#clustering) and [Memory Policies](configure.md#memory-policies)
+> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering](architecture.md#clustering).
 >
 
 ### RedisBloom