Merge pull request #298645 from flang-msft/fxl---for-cawa---public-and-private-access-mutually-exclusive-in-Enterprise--32388506

fxll---added file for bug fix for public-private access

Author: JillGrant615

articles/redis/machine-learning.md

@@ -44,8 +44,6 @@ You’ll be able to deploy a machine learning model to Azure Functions with any
 
 1. On the **New** page, select **Databases** and then select **Azure Cache for Redis**.
 
-    :::image type="content" source="media/private-link/2-select-cache.png" alt-text="Select Azure Cache for Redis.":::
-
 1. On the **New Redis Cache** page, configure the settings for your new cache.
 
    | Setting      | Suggested value  | Description |

articles/redis/media/private-link/1-create-resource.png

@@ -1,11 +1,9 @@
 ---
 title: Create, query, and delete a cache using Azure CLI
 description: Use the Azure CLI to create an Azure Redis instance, get cache details like status, hostname, ports, and keys, and delete the cache.
-
-
 ms.devlang: azurecli
 ms.topic: sample
-ms.date: 05/08/2025
+ms.date: 05/18/2025
 zone_pivot_groups: redis-type
 ms.custom: 
   - devx-track-azurecli, ignite-2024, build-2025
@@ -37,6 +35,7 @@ This article describes how to create and delete an Azure Redis cache instance by
 :::code language="azurecli" source="~/azure_cli_scripts/redis-cache/create-cache/create-manage-cache.sh" id="FullScript"::: 
 This sample is broken. When it is fixed, we can fix this include.
 -->
+
 To create an Azure Managed Redis cache by using Azure CLI, the `name`, `location`, `resourceGroup`, and `sku` parameters are required. Other parameters are optional and have defaults.
 
 You can use the Azure CLI script in this section to create an Azure Managed Redis cache with default settings. You can also use the following other methods to create a cache:

articles/redis/media/private-link/2-select-cache.png

@@ -69,7 +69,7 @@ You can confirm the number of sent packets is equal to the received packets. Con
 
 Steps to check your private endpoint configuration:
 
-1. Verify if your private endpoint is configured correctly. For more information, see [Create a private endpoint with a new Azure Managed Redis instance](private-link.md#create-a-private-endpoint-with-a-new-azure-managed-redis-instance).
+1. Verify if your private endpoint is configured correctly. For more information, see [Create a private endpoint with a new Azure Managed Redis instance](private-link.md#create-a-virtual-network-with-a-subnet).
 
 1. Verify if your application is connecting to `<instancename>.<region>.redis.azure.net` on port 10000. We recommend avoiding the use of `<instancename>.<region>.privatelink.redis.cache.windows.net` in the configuration or the connection string.