Removed images and refined create experience.

flang-msft · flang-msft · commit aa53cfd0eed5 · 2024-12-19T11:40:05.000-08:00
diff --git a/articles/azure-cache-for-redis/managed-redis/managed-redis-private-link.md b/articles/azure-cache-for-redis/managed-redis/managed-redis-private-link.md
@@ -23,13 +23,14 @@ Azure Private Endpoint is a network interface that connects you privately and se
 
 - Azure subscription - [create one for free](https://azure.microsoft.com/free/)
 
-
 ## Create a private endpoint with a new Azure Managed Redis instance
 
 In this section, you create a new Azure Managed Redis instance with a private endpoint.
 
 ### Create a virtual network for your new cache
 
+To create a cache using the portal:
+
 1. Sign in to the [Azure portal](https://portal.azure.com) and select **Create a resource**.
 
     :::image type="content" source="media/managed-redis-private-link/1-create-resource.png" alt-text="Select Create a resource.":::
@@ -42,7 +43,7 @@ In this section, you create a new Azure Managed Redis instance with a private en
 
    | Setting      | Suggested value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
-   | **Subscription** | Drop down and select your subscription. | The subscription under which to create this virtual network. |
+   | **Subscription** | Drop down and select your subscription. | The subscription where you create this virtual network. |
    | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your virtual network and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
    | **Name** | Enter a virtual network name. | The name must: begin with a letter or number; end with a letter, number, or underscore; and contain only letters, numbers, underscores, periods, or hyphens. |
    | **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your virtual network. |
@@ -67,19 +68,11 @@ To create a cache instance, follow these steps:
 
 1. Go back to the Azure portal homepage or open the sidebar menu, then select **Create a resource**.
 
-1. On the **New** page, select **Databases** and then select **Azure Managed Redis**.
-
-   :::image type="content" source="media/managed-redis-private-link/2-select-cache.png" alt-text="Select Azure Cache for Redis.":::
+1. In the search box, type _Azure Cache for Redis_. Refine your search to Azure services only, and select **Azure Cache for Redis**.
 
 1. On the **New Redis Cache** page, configure the settings for your new cache.
-
-   | Setting      | Suggested value  | Description |
-   | ------------ |  ------- | -------------------------------------------------- |
-   | **DNS name** | Enter a globally unique name. | The cache name must be a string between 1 and 63 characters. The string must contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* is *\<DNS name>.\<region>.redis.azure.net*. |
-   | **Subscription** | Drop down and select your subscription. | The subscription under which to create this new Azure Managed Redis instance. |
-   | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
-   | **Location** | Drop down and select a location. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your cache. |
-   | **Pricing tier** | Drop down and select a [Pricing tier](https://azure.microsoft.com/pricing/details/cache/). |  The pricing tier determines the size, performance, and features that are available for the cache. For more information, see [Azure Managed Redis Overview](managed-redis-overview.md). |
+    1. Select an Azure Managed Redis cache in **Cache SKU**.
+    1. Select an appropriate option in **Cache size**.
 
 1. Select the **Networking** tab or select the **Networking** button at the bottom of the page.
 
@@ -107,7 +100,6 @@ To create a cache instance, follow these steps:
 
 It takes a while for the cache to create. You can monitor progress on the Azure Managed Redis **Overview** page. When **Status** shows as **Running**, the cache is ready to use.
 
-
 ## Create a private endpoint with an existing Azure Managed Redis instance
 
 In this section, you add a private endpoint to an existing Azure Managed Redis instance.
@@ -126,7 +118,7 @@ To create a virtual network, follow these steps:
 
    | Setting      | Suggested value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
-   | **Subscription** | Drop down and select your subscription. | The subscription under which to create this virtual network. |
+   | **Subscription** | Drop down and select your subscription. | The subscription where you create this virtual network. |
    | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your virtual network and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
    | **Name** | Enter a virtual network name. | The name must: begin with a letter or number; end with a letter, number, or underscore; and contain only letters, numbers, underscores, periods, or hyphens. |
    | **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your virtual network. |
@@ -149,23 +141,23 @@ To create a virtual network, follow these steps:
 
 To create a private endpoint, follow these steps:
 
-1. In the Azure portal, search for **Azure Managed Redis**. Then, press enter or select it from the search suggestions.
+1. In the Azure portal, search for **Azure Cache for Redis**. Then, press enter or select it from the search suggestions for your cache.
 
-    :::image type="content" source="media/managed-redis-private-link/4-search-for-cache.png" alt-text="Search for Azure Managed Redis.":::
+    <!-- :::image type="content" source="media/managed-redis-private-link/4-search-for-cache.png" alt-text="Search for Azure Managed Redis."::: -->
 
 1. Select the cache instance you want to add a private endpoint to.
 
 1. On the left side of the screen, select **Private Endpoint**.
 
 1. Select the **Private Endpoint** button to create your private endpoint.
 
-    :::image type="content" source="media/managed-redis-private-link/5-add-private-endpoint.png" alt-text="Add private endpoint.":::
+    <!-- :::image type="content" source="media/managed-redis-private-link/5-add-private-endpoint.png" alt-text="Add private endpoint."::: -->
 
 1. On the **Create a private endpoint page**, configure the settings for your private endpoint.
 
    | Setting      | Suggested value  | Description |
    | ------------ |  ------- | -------------------------------------------------- |
-   | **Subscription** | Drop down and select your subscription. | The subscription under which to create this private endpoint. |
+   | **Subscription** | Drop down and select your subscription. | The subscription where you create this private endpoint. |
    | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your private endpoint and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
    | **Name** | Enter a private endpoint name. | The name must: begin with a letter or number; end with a letter, number, or underscore; and can contain only letters, numbers, underscores, periods, or hyphens. |
    | **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your private endpoint. |
@@ -197,7 +189,7 @@ To create a private endpoint, follow these steps:
 >
 ## Create a private endpoint using Azure PowerShell
 
-To create a private endpoint named *MyPrivateEndpoint* for an existing Azure Managed Redis instance, run the following PowerShell script. Replace the variable values with the details for your environment:
+To create a private endpoint named _MyPrivateEndpoint_ for an existing Azure Managed Redis instance, run the following PowerShell script. Replace the variable values with the details for your environment:
 
 ```azurepowershell-interactive
 
@@ -245,7 +237,7 @@ Remove-AzPrivateEndpoint -Name $PrivateEndpointName -ResourceGroupName $Resource
 
 ## Create a private endpoint using Azure CLI
 
-To create a private endpoint named *myPrivateEndpoint* for an existing Azure Managed Redis instance, run the following Azure CLI script. Replace the variable values with the details for your environment:
+To create a private endpoint named _myPrivateEndpoint_ for an existing Azure Managed Redis instance, run the following Azure CLI script. Replace the variable values with the details for your environment:
 
 ```azurecli-interactive
 # Resource group where the Azure Managed Redis and virtual network resources are located
@@ -313,21 +305,20 @@ az network private-endpoint delete --name MyPrivateEndpoint --resource-group MyR
 - [What features aren't supported with private endpoints?](#what-features-arent-supported-with-private-endpoints)
 - [How do I verify if my private endpoint is configured correctly?](#how-do-i-verify-if-my-private-endpoint-is-configured-correctly)
 - [How can I change my private endpoint to be disabled or enabled from public network access?](#how-can-i-change-my-private-endpoint-to-be-disabled-or-enabled-from-public-network-access)
-<!-- - [How can I migrate my VNet injected cache to a Private Link cache?](#how-can-i-migrate-my-vnet-injected-cache-to-a-private-link-cache) -->
 - [How can I have multiple endpoints in different virtual networks?](#how-can-i-have-multiple-endpoints-in-different-virtual-networks)
 - [What happens if I delete all the private endpoints on my cache?](#what-happens-if-i-delete-all-the-private-endpoints-on-my-cache)
 - [Are network security groups (NSG) enabled for private endpoints?](#are-network-security-groups-nsg-enabled-for-private-endpoints)
 - [My private endpoint instance isn't in my VNet, so how is it associated with my VNet?](#my-private-endpoint-instance-isnt-in-my-vnet-so-how-is-it-associated-with-my-vnet)
 
 ### How do I connect to my cache with private endpoint?
 
-Your application should connect to `<cachename>.<region>.redis.azure.net` on port `10000`. A private DNS zone, named `*.privatelink.redis.azure.net`, is automatically created in your subscription. The private DNS zone is vital for establishing the TLS connection with the private endpoint.  We recommend avoiding the use of `<cachename>.privatelink.redis.azure.net` in configuration for client connection.
+Your application should connect to `<cachename>.<region>.redis.azure.net` on port `10000`. A private DNS zone, named `*.privatelink.redis.azure.net`, is automatically created in your subscription. The private DNS zone is vital for establishing the TLS connection with the private endpoint. We recommend avoiding the use of `<cachename>.privatelink.redis.azure.net` in configuration for client connection.
 
 For more information, see [Azure services DNS zone configuration](/azure/private-link/private-endpoint-dns).
 
 ### Why can't I connect to a private endpoint?
 
-- Private endpoints can't be used with your cache instance if your cache is already a VNet injected cache.
+- Private endpoints can't be used with your cache instance if your cache is already a virtual network (VNet) injected cache.
   
 - Azure Managed Redis caches are limited to 84 private links.
 
@@ -337,43 +328,43 @@ For more information, see [Azure services DNS zone configuration](/azure/private
 
 ### What features aren't supported with private endpoints?
 
-- There is no restriction for using private endpoint with Azure Managed Redis (Preview).
+- There's no restriction for using private endpoint with Azure Managed Redis (Preview).
 
 ### How do I verify if my private endpoint is configured correctly?
 
-Go to **Overview** in the Resource menu on the portal. You see the **Host name** for your cache in the working pane. Run a command like `nslookup <hostname>` from within the VNet that is linked to the private endpoint to verify that the command resolves to the private IP address for the cache.
+Go to **Overview** in the Resource menu on the portal. You see the **Host name** for your cache in the working pane. To verify that the command resolves to the private IP address for the cache, run a command like `nslookup <hostname>` from within the VNet that is linked to the private endpoint.
 
    :::image type="content" source="media/managed-redis-private-link/managed-redis-private-ip-address.png" alt-text="In the Azure portal, private endpoint D N S settings.":::
 
 ### How can I change my private endpoint to be disabled or enabled from public network access?
 
 To change the value in the Azure portal, follow these steps:
 
-  1. In the Azure portal, search for **Azure Managed Redis**.  Then, press enter or select it from the search suggestions.
+  1. In the Azure portal, search for **Azure Managed Redis**. Then, press enter or select it from the search suggestions.
 
   1. Select the cache instance you want to change the public network access value.
 
   1. On the left side of the screen, select **Private Endpoint**.
 
-  1. Delete the private endpoint. 
+  1. Delete the private endpoint.
 
 ### How can I have multiple endpoints in different virtual networks?
 
-To have multiple private endpoints in different virtual networks, the private DNS zone must be manually configured to the multiple virtual networks *before* creating the private endpoint. For more information, see [Azure Private Endpoint DNS configuration](/azure/private-link/private-endpoint-dns).
+To have multiple private endpoints in different virtual networks, the private DNS zone must be manually configured to the multiple virtual networks before creating the private endpoint. For more information, see [Azure Private Endpoint DNS configuration](/azure/private-link/private-endpoint-dns).
 
 ### What happens if I delete all the private endpoints on my cache?
 
-Deleting all private endpoints on your Azure Managed Redis (preview) will make the service to have public network access.
+If you delete all private endpoints on your Azure Managed Redis (preview) cache, networking defaults to have public network access.
 
 ### Are network security groups (NSG) enabled for private endpoints?
 
-No, they're disabled for private endpoints. While subnets containing the private endpoint can have NSG associated with it, the rules aren't effective on traffic processed by the private endpoint. You must have [network policies enforcement disabled](/azure/private-link/disable-private-endpoint-network-policy) to deploy private endpoints in a subnet. NSG is still enforced on other workloads hosted on the same subnet. Routes on any client subnet will be using an /32 prefix, changing the default routing behavior requires a similar UDR.
+No, they're disabled for private endpoints. While subnets containing the private endpoint can have NSG associated with it, the rules aren't effective on traffic processed by the private endpoint. You must have [network policies enforcement disabled](/azure/private-link/disable-private-endpoint-network-policy) to deploy private endpoints in a subnet. NSG is still enforced on other workloads hosted on the same subnet. Routes on any client subnet use a /32 prefix, changing the default routing behavior requires a similar UDR.
 
 Control the traffic by using NSG rules for outbound traffic on source clients. Deploy individual routes with /32 prefix to override private endpoint routes. NSG Flow logs and monitoring information for outbound connections are still supported and can be used.
 
 ### My private endpoint instance isn't in my VNet, so how is it associated with my VNet?
 
-It's only linked to your VNet. Because it's not in your VNet, NSG rules don't need to be modified for dependent endpoints.
+Your private endpoint is only linked to your VNet. Because it's not in your VNet, NSG rules don't need to be modified for dependent endpoints.
 
 ## Related content
 
