Skip to content

Commit b318fb1

Browse files
flang-msftflang-msft
committed
Updated procedure, fixed link.
1 parent 7aff4ab commit b318fb1

File tree

2 files changed

+56
-81
lines changed

2 files changed

+56
-81
lines changed

‎articles/redis/private-link.md

Lines changed: 54 additions & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -24,166 +24,139 @@ Azure Private Endpoint is a network interface that connects you privately and se
2424

2525
- Azure subscription - [create one for free](https://azure.microsoft.com/free/)
2626

27-
## Create a new Azure Managed Redis instance with Private Endpoint connection
27+
## Create a new Azure Managed Redis cache with a private endpoint connection
2828

29-
In this section, you create a new Azure Managed Redis instance with a private endpoint.
29+
In this section, you create a new Azure Managed Redis cache with a private endpoint.
3030

31-
### 1. Create a virtual network with Subnet for your new cache
31+
1. The first step is to create a virtual network for your new cache.
32+
1. Then, you create a new cache. During the create experience, add the subnet that you created to in the first step.
33+
34+
### Create a virtual network with a subnet
3235

3336
To create a cache using the portal:
3437

3538
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Create a resource**.
3639

3740
:::image type="content" source="media/private-link/1-create-resource.png" alt-text="Select Create a resource.":::
3841

39-
2. On the **New** page, select **Networking** and then select **Virtual network**.
42+
1. On the **New** pane, select **Networking** and then select **Virtual network**.
4043

41-
3. Select **Add** to create a virtual network.
44+
1. Select **Add** to create a virtual network.
4245

43-
4. In **Create virtual network**, enter or select this information in the **Basics** tab:
46+
1. In **Create virtual network**, enter or select this information in the **Basics** pane:
4447

4548
| Setting | Suggested value | Description |
4649
| ------------ | ------- | -------------------------------------------------- |
4750
| **Subscription** | Drop down and select your subscription. | The subscription where you create this virtual network. |
4851
| **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. |
49-
| **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. |
52+
| **Virtual network 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. |
5053
| **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your virtual network. |
5154

52-
5. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
55+
1. Select the **IP Addresses** pane or select the **Next: IP Addresses** button at the bottom of the pane.
5356

54-
6. In the **IP Addresses** tab, specify the **IPv4 address space** as one or more address prefixes in CIDR notation (for example, 192.168.1.0/24).
57+
1. In the **IP Addresses** pane, specify the **IPv4 address space** or **IPv6 address space**. For this procedure, use **IPv4 address space**.
5558

56-
7. Under **Subnet name**, select on **default** to edit the subnet's properties.
59+
1. Select **Add a subnet**. Under **Subnet name**, select **default** or add a name. You can also edit the subnet properties as needed for your application.
5760

58-
8. In the **Edit subnet** pane, specify a **Subnet name** and the **Subnet address range**. The subnet's address range should be in CIDR notation (for example, 192.168.1.0/24). It must be contained by the address space of the virtual network.
61+
1. Select **Add**.
5962

60-
9. Select **Save**.
63+
1. Select the **Review + create** pane or select the **Review + create** button.
6164

62-
10. Select the **Review + create** tab or select the **Review + create** button.
63-
64-
11. Verify that all the information is correct and select **Create** to create the virtual network.
65+
1. Verify that all the information is correct and select **Create** to create the virtual network.
6566

66-
### 2. Create an Azure Managed Redis instance with a private endpoint connected to a Virtual Network Subnet
67+
### Create an Azure Managed Redis instance with a private endpoint connected to a Virtual Network Subnet
6768

6869
To create a cache instance, follow these steps:
6970

70-
1. Go back to the Azure portal homepage or open the sidebar menu, then select **Create a resource**.
71+
1. Go back to the Azure portal home page or open the sidebar menu, then select **Create a resource**.
7172

72-
1. In the search box, type _Azure Cache for Redis_. Refine your search to Azure services only, and select **Azure Cache for Redis**.
73+
1. In the search box, type _Azure Managed Redis_. Refine your search to Azure services only, and select **Azure Managed Redis**.
7374

74-
1. On the **New Redis Cache** page, configure the settings for your new cache.
75+
1. On the **New Redis Cache** pane, configure the settings for your new cache.
7576
1. Select an Azure Managed Redis cache in **Cache SKU**.
7677
1. Select an appropriate option in **Cache size**.
7778

78-
1. Select the **Networking** tab or select the **Networking** button at the bottom of the page.
79+
1. Select the **Networking** pane or select the **Networking** at the bottom of the pane.
7980

80-
1. In the **Networking** tab, select **Private Endpoint** for the connectivity method.
81+
1. In the **Networking** pane, select **Private Endpoint** for the connectivity method.
8182

8283
1. Select the **Add** button to create your private endpoint.
8384

8485
:::image type="content" source="media/private-link/3-add-private-endpoint.png" alt-text="In networking, add a private endpoint.":::
8586

86-
1. On the **Create a private endpoint** page, configure the settings for your private endpoint with the virtual network and subnet you created in the last section and select **OK**.
87+
1. On the **Create a private endpoint** pane, configure the settings for your private endpoint with the virtual network and subnet you created in the last section and select **OK**.
8788

88-
1. Select the **Next: Advanced** tab or select the **Next: Advanced** button on the bottom of the page.
89+
1. On the **Active geo-replication** pane, make the setting required for your resource.
8990

90-
1. In the **Advanced** tab for a basic or standard cache instance, select the enable toggle if you want to enable a non-TLS port.
91+
1. Select the **Next: Advanced** pane or select the **Next: Advanced** button on the bottom of the pane.
9192

92-
1. In the **Advanced** tab for premium cache instance, configure the settings for non-TLS port, clustering, and data persistence.
93+
1. In the **Advanced** pane for Azure Managed Redis instance, configure the settings needed for your resource.
9394

94-
1. Select the **Next: Tags** tab or select the **Next: Tags** button at the bottom of the page.
95+
1. Select the **Next: Tags** pane or select the **Next: Tags** button at the bottom of the pane.
9596

96-
1. Optionally, in the **Tags** tab, enter the name and value if you wish to categorize the resource.
97+
1. Optionally, in the **Tags** pane, enter the name and value if you wish to categorize the resource.
9798

98-
1. Select **Review + create**. You're taken to the Review + create tab where Azure validates your configuration.
99+
1. Select **Review + create**. You're taken to the Review + create pane where Azure validates your configuration.
99100

100101
1. After the green Validation passed message appears, select **Create**.
101102

102-
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.
103+
It takes a while for the cache to create. You can monitor progress on the Azure Managed Redis **Overview** pane. When **Status** shows as **Running**, the cache is ready to use.
103104

104-
## Create a private endpoint with an existing Azure Managed Redis instance
105+
## Create a private endpoint for use with an existing Azure Managed Redis instance
105106

106107
In this section, you add a private endpoint to an existing Azure Managed Redis instance.
107108

108-
### 1. Create a virtual network wuth Subnet for your existing cache
109-
110-
To create a virtual network, follow these steps:
111-
112-
1. Sign in to the [Azure portal](https://portal.azure.com) and select **Create a resource**.
113-
114-
1. On the **New** page, select **Networking** and then select **Virtual network**.
109+
1. The first step is to [create a virtual network](#create-a-virtual-network-with-subnet) for use with your existing cache.
110+
1. Then, you open your cache in the portal and add the subnet that you created to in the first step.
115111

116-
1. Select **Add** to create a virtual network.
112+
### Create a virtual network with a subnet for your existing cache
117113

118-
1. In **Create virtual network**, enter or select this information in the **Basics** tab:
114+
To create a virtual network, follow these [steps](#create-a-virtual-network-with-subnet).
119115

120-
| Setting | Suggested value | Description |
121-
| ------------ | ------- | -------------------------------------------------- |
122-
| **Subscription** | Drop down and select your subscription. | The subscription where you create this virtual network. |
123-
| **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. |
124-
| **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. |
125-
| **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your virtual network. |
126-
127-
1. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
128-
129-
1. In the **IP Addresses** tab, specify the **IPv4 address space** as one or more address prefixes in CIDR notation (for example, 192.168.1.0/24).
130-
131-
1. Under **Subnet name**, select on **default** to edit the subnet's properties.
132-
133-
1. In the **Edit subnet** pane, specify a **Subnet name** and the **Subnet address range**. The subnet's address range should be in CIDR notation (for example, 192.168.1.0/24). It must be contained by the address space of the virtual network.
134-
135-
1. Select **Save**.
136-
137-
1. Select the **Review + create** tab or select the **Review + create** button.
138-
139-
1. Verify that all the information is correct and select **Create** to create the virtual network.
140-
141-
### 2. Add a private endpoint for your existing Azure Managed Redis
116+
### Add a private endpoint to an existing Azure Managed Redis cache
142117

143118
To create a private endpoint, follow these steps:
144119

145-
1. In the Azure portal, search for **Azure Cache for Redis**. Then, press enter or select it from the search suggestions for your cache.
146-
147-
1. Select the cache instance you want to add a private endpoint to.
120+
1. In the Azure portal, select the cache instance you want to add a private endpoint to.
148121

149-
1. On the left side of the screen, select **Private Endpoint**.
122+
1. Select **Private Endpoint** from the resource menu to create your private endpoint for your cache.
150123

151-
1. Select the **Private Endpoint** button to create your private endpoint.
152-
153-
1. On the **Create a private endpoint page**, configure the settings for your private endpoint.
124+
1. On the **Create a private endpoint** pane, configure the settings for your private endpoint.
154125

155126
| Setting | Suggested value | Description |
156127
| ------------ | ------- | -------------------------------------------------- |
157128
| **Subscription** | Drop down and select your subscription. | The subscription where you create this private endpoint. |
158129
| **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. |
159130
| **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. |
131+
| **Network Interface Name** | Autogenerated based on the **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. |
160132
| **Region** | Drop down and select a region. | Select a [region](https://azure.microsoft.com/regions/) near other services that use your private endpoint. |
161133

162-
1. Select the **Next: Resource** button at the bottom of the page.
163-
164-
1. In the **Resource** tab, select your subscription, choose the resource type as `Microsoft.Cache/redisEnterprise`, and then select the cache you want to connect the private endpoint to.
134+
1. Select the **Next: Resource** at the bottom of the pane.
165135

166-
1. Select the **Next: Configuration** button at the bottom of the page.
136+
1. In the **Resource** pane, select your **Subscription**.
137+
1. Then, choose the **Resource type** as `Microsoft.Cache/redisEnterprise`.
138+
1. Then select the cache you want to connect the private endpoint to for the **Resource** property.
167139

168-
1. Select the **Next: Virtual Network** button at the bottom of the page.
140+
1. Select the **Next: Virtual Network** button at the bottom of the pane.
169141

170-
1. In the **Configuration** tab, select the virtual network and subnet you created in the previous section.
142+
1. In the **Virtual Network** pane, select the **Virtual Nnetwork** and **Subnet** you created in the previous section.
171143

172-
1. In the **Virtual Network** tab, select the virtual network and subnet you created in the previous section.
144+
<!-- We don't talk about DNS zones -->
173145

174-
1. Select the **Next: Tags** button at the bottom of the page.
146+
1. Select the **Next: Tags** button at the bottom of the pane.
175147

176-
1. Optionally, in the **Tags** tab, enter the name and value if you wish to categorize the resource.
148+
1. Optionally, in the **Tags** pane, enter the name and value if you wish to categorize the resource.
177149

178-
1. Select **Review + create**. You're taken to the **Review + create** tab where Azure validates your configuration.
150+
1. Select **Review + create**. You're taken to the **Review + create** pane where Azure validates your configuration.
179151

180152
1. After the green **Validation passed** message appears, select **Create**.
181153

182154
> [!IMPORTANT]
183155
>
184156
> There is currently no `publicNetworkAccess` property for Azure Managed Redis resource.
185-
> If there is a Private Endpoint connected to the Azure Managed Redis resource, it would only accept private traffic from the Virtual Network it's connected to
186-
> If you delete the Private Endpoint, the resource will automatically be opened to public network access
157+
> If there is a Private Endpoint connected to the Azure Managed Redis resource, it would only accept private traffic from the Virtual Network it's connected to.
158+
> If you delete the Private Endpoint, the resource is automatically opened to public network access.
159+
187160
## Create an AMR connected to a private endpoint using Azure PowerShell
188161

189162
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:
@@ -295,7 +268,7 @@ To remove a private endpoint, use the following CLI command:
295268
az network private-endpoint delete --name MyPrivateEndpoint --resource-group MyResourceGroup
296269
```
297270
## Azure Managed Redis Private Endpoint Private DNS zone value
298-
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.
271+
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 espanelishing the TLS connection with the private endpoint. We recommend avoiding the use of `<cachename>.privatelink.redis.azure.net` in configuration for client connection.
299272

300273
For more information, see [Azure services DNS zone configuration](/azure/private-link/private-endpoint-dns).
301274

‎articles/redis/troubleshoot-connectivity.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,8 @@ You can confirm the number of sent packets is equal to the received packets. Con
6868
Steps to check your private endpoint configuration:
6969

7070
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).
71+
1.
72+
1.
7173

7274
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.
7375

0 commit comments

Comments
 (0)