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
For **Basic, Standard, and Premium tier** caches, your application should connect to `<cachename>.redis.cache.windows.net` on port `6380`. A private DNS zone, named `*.privatelink.redis.cache.windows.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.cache.windows.net` in configuration or connection string.
348
349
349
-
For **Enterprise and Enterprise Flash** tier caches, your application should connect to `<cachename>.<region>.redisenterprise.cache.azure.net` on port `10000`.
350
+
For **Enterprise and Enterprise Flash** tier caches, your application should connect to `<cachename>.<region>.redisenterprise.cache.azure.net` on port `10000`. If you're using OSS clustering, then your client library also creates connections to your Redis Enterprise instance on ports 8500 - 8599 as your application needs to connect to each shard individually in OSS clustering configuration.
350
351
351
352
For more information, see [Azure services DNS zone configuration](../private-link/private-endpoint-dns.md).
352
353
353
354
### Why can't I connect to a private endpoint?
354
355
355
356
- Private endpoints can't be used with your cache instance if your cache is already a VNet injected cache.
356
357
357
-
- For Basic, Standard, and Premium tier caches, you are limited to 100 private links.
358
+
- For Basic, Standard, and Premium tier caches, you're limited to 100 private links.
358
359
359
-
- On Premium tier caches using clustering, you are limited to one private link.
360
+
- On Premium tier caches using clustering, you're limited to one private link.
360
361
361
362
- Enterprise and Enterprise Flash tier caches are limited to 84 private links.
362
363
@@ -368,7 +369,7 @@ For more information, see [Azure services DNS zone configuration](../private-lin
368
369
369
370
- Trying to connect from the Azure portal console is an unsupported scenario where you see a connection failure.
370
371
371
-
- Private links can't be added to caches that are already using [passive geo-replication](cache-how-to-geo-replication.md) in the Premium tier. To add a private link to a geo-replicated cache: 1. Unlink the geo-replication. 2. Add a Private Link. 3. Last, relink the geo-replication. (Enterprise tier caches using [active geo-replication](cache-how-to-active-geo-replication.md)do not have this restriction.)
372
+
- Private links can't be added to caches that are already using [passive geo-replication](cache-how-to-geo-replication.md) in the Premium tier. To add a private link to a geo-replicated cache: 1. Unlink the geo-replication. 2. Add a Private Link. 3. Last, relink the geo-replication. (Enterprise tier caches using [active geo-replication](cache-how-to-active-geo-replication.md)don't have this restriction.)
372
373
373
374
### How do I verify if my private endpoint is configured correctly?
374
375
@@ -383,7 +384,7 @@ When set to `Enabled`, this flag is allows both public and private endpoint acce
383
384
384
385
To change the value in the Azure portal, follow these steps:
385
386
386
-
1. In the Azure portal, search for **Azure Cache for Redis**. Then, press enter or select it from the search suggestions.
387
+
1. In the Azure portal, search for **Azure Cache for Redis**. Then, press enter or select it from the search suggestions.
387
388
388
389
1. Select the cache instance you want to change the public network access value.
389
390
@@ -418,7 +419,7 @@ Once you delete the private endpoints on your cache, your cache instance can bec
418
419
419
420
### Are network security groups (NSG) enabled for private endpoints?
420
421
421
-
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](../private-link/disable-private-endpoint-network-policy.md) 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.
422
+
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](../private-link/disable-private-endpoint-network-policy.md) 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 an /32 prefix, changing the default routing behavior requires a similar UDR.
422
423
423
424
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.
0 commit comments