You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[What features aren't supported with private endpoints?](#what-features-arent-supported-with-private-endpoints)
314
314
-[How do I verify if my private endpoint is configured correctly?](#how-do-i-verify-if-my-private-endpoint-is-configured-correctly)
315
315
-[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)
316
-
-[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)
316
+
<!-- - [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)-->
317
317
-[How can I have multiple endpoints in different virtual networks?](#how-can-i-have-multiple-endpoints-in-different-virtual-networks)
318
318
-[What happens if I delete all the private endpoints on my cache?](#what-happens-if-i-delete-all-the-private-endpoints-on-my-cache)
319
319
-[Are network security groups (NSG) enabled for private endpoints?](#are-network-security-groups-nsg-enabled-for-private-endpoints)
@@ -335,16 +335,36 @@ For more information, see [Azure services DNS zone configuration](/azure/private
335
335
336
336
- You might not connect to your private endpoint if your cache instance is using an [unsupported feature](#what-features-arent-supported-with-private-endpoints).
337
337
338
+
### What features aren't supported with private endpoints?
339
+
340
+
- There is no restriction for using private endpoint with Azure Managed Redis (Preview).
341
+
338
342
### How do I verify if my private endpoint is configured correctly?
339
343
340
344
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.
341
345
342
346
:::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.":::
343
347
348
+
### How can I change my private endpoint to be disabled or enabled from public network access?
349
+
350
+
To change the value in the Azure portal, follow these steps:
351
+
352
+
1. In the Azure portal, search for **Azure Managed Redis**. Then, press enter or select it from the search suggestions.
353
+
354
+
1. Select the cache instance you want to change the public network access value.
355
+
356
+
1. On the left side of the screen, select **Private Endpoint**.
357
+
358
+
1. Delete the private endpoint.
359
+
344
360
### How can I have multiple endpoints in different virtual networks?
345
361
346
362
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).
347
363
364
+
### What happens if I delete all the private endpoints on my cache?
365
+
366
+
Deleting all private endpoints on your Azure Managed Redis (preview) will make the service to have public network access.
367
+
348
368
### Are network security groups (NSG) enabled for private endpoints?
349
369
350
370
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.
0 commit comments