Skip to content

Commit 293ea8b

Browse files
committed
Added specifics to firewall limitations
1 parent fc0e4d4 commit 293ea8b

File tree

1 file changed

+21
-19
lines changed

1 file changed

+21
-19
lines changed

articles/azure-cache-for-redis/cache-network-isolation.md

Lines changed: 21 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -18,19 +18,19 @@ Azure Private Link provides private connectivity from a virtual network to Azure
1818

1919
### Advantages of Private Link
2020

21-
* Supported on Basic, Standard, and Premium Azure Cache for Redis instances.
22-
* By using [Azure Private Link](../private-link/private-link-overview.md), you can connect to an Azure Cache instance from your virtual network via a private endpoint. The endpoint is assigned a private IP address in a subnet within the virtual network. With this private link, cache instances are available from both within the VNet and publicly.
23-
* Once a private endpoint is created, access to the public network can be restricted through the `publicNetworkAccess` flag. This flag is set to `Disabled` by default, which will only allow private link access. You can set the value to `Enabled` or `Disabled` with a PATCH request. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md).
24-
* All external cache dependencies won't affect the VNet's NSG rules.
21+
- Supported on Basic, Standard, and Premium Azure Cache for Redis instances.
22+
- By using [Azure Private Link](../private-link/private-link-overview.md), you can connect to an Azure Cache instance from your virtual network via a private endpoint. The endpoint is assigned a private IP address in a subnet within the virtual network. With this private link, cache instances are available from both within the VNet and publicly.
23+
- Once a private endpoint is created, access to the public network can be restricted through the `publicNetworkAccess` flag. This flag is set to `Disabled` by default, which will only allow private link access. You can set the value to `Enabled` or `Disabled` with a PATCH request. For more information, see [Azure Cache for Redis with Azure Private Link](cache-private-link.md).
24+
- All external cache dependencies won't affect the VNet's NSG rules.
2525

2626
### Limitations of Private Link
2727

28-
* Network security groups (NSG) are disabled for private endpoints. However, if there are other resources on the subnet, NSG enforcement will apply to those resources.
29-
* Currently, portal console support, and persistence to firewall storage accounts aren't supported.
30-
* To connect to a clustered cache, `publicNetworkAccess` needs to be set to `Disabled` and there can only be one private endpoint connection.
28+
- Network security groups (NSG) are disabled for private endpoints. However, if there are other resources on the subnet, NSG enforcement will apply to those resources.
29+
- Currently, portal console support, and persistence to firewall storage accounts aren't supported.
30+
- To connect to a clustered cache, `publicNetworkAccess` needs to be set to `Disabled`, and there can only be one private endpoint connection.
3131

3232
> [!NOTE]
33-
> When adding a private endpoint to a cache instance, all Redis traffic will be moved to the private endpoint because of the DNS.
33+
> When adding a private endpoint to a cache instance, all Redis traffic is moved to the private endpoint because of the DNS.
3434
> Ensure previous firewall rules are adjusted before.
3535
3636
## Azure Virtual Network injection
@@ -39,30 +39,32 @@ VNet is the fundamental building block for your private network in Azure. VNet e
3939

4040
### Advantages of VNet injection
4141

42-
* When an Azure Cache for Redis instance is configured with a VNet, it's not publicly addressable. It can only be accessed from virtual machines and applications within the VNet.
43-
* When VNet is combined with restricted NSG policies, it helps reduce the risk of data exfiltration.
44-
* VNet deployment provides enhanced security and isolation for your Azure Cache for Redis. Subnets, access control policies, and other features further restrict access.
45-
* Geo-replication is supported.
42+
- When an Azure Cache for Redis instance is configured with a VNet, it's not publicly addressable. It can only be accessed from virtual machines and applications within the VNet.
43+
- When VNet is combined with restricted NSG policies, it helps reduce the risk of data exfiltration.
44+
- VNet deployment provides enhanced security and isolation for your Azure Cache for Redis. Subnets, access control policies, and other features further restrict access.
45+
- Geo-replication is supported.
4646

4747
### Limitations of VNet injection
4848

49-
* VNet injected caches are only available for Premium Azure Cache for Redis.
50-
* When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
49+
- VNet injected caches are only available for Premium Azure Cache for Redis.
50+
- When using a VNet injected cache, you must change your VNet to cache dependencies such as CRLs/PKI, AKV, Azure Storage, Azure Monitor, and more.
5151

5252
## Azure Firewall rules
5353

5454
[Azure Firewall](../firewall/overview.md) is a managed, cloud-based network security service that protects your Azure VNet resources. It’s a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. You can centrally create, enforce, and log application and network connectivity policies across subscriptions and virtual networks.
5555

5656
### Advantages of firewall rules
5757

58-
* When firewall rules are configured, only client connections from the specified IP address ranges can connect to the cache. Connections from Azure Cache for Redis monitoring systems are always permitted, even if firewall rules are configured. NSG rules that you define are also permitted.
58+
- When firewall rules are configured, only client connections from the specified IP address ranges can connect to the cache. Connections from Azure Cache for Redis monitoring systems are always permitted, even if firewall rules are configured. NSG rules that you define are also permitted.
5959

6060
### Limitations of firewall rules
6161

62-
* Firewall rules can be used with VNet injected caches, but not private endpoints currently.
62+
- Firewall rules can be used with VNet injected caches, but not private endpoints.
63+
- Firewall rules configuration is available for all Basic, Standard, and Premium tiers.
64+
- Firewall rules configuration isn't available for Enterprise nor Enterprise Flash tiers.
6365

6466
## Next steps
6567

66-
* Learn how to configure a [VNet injected cache for a Premium Azure Cache for Redis instance](cache-how-to-premium-vnet.md).
67-
* Learn how to configure [firewall rules for all Azure Cache for Redis tiers](cache-configure.md#firewall).
68-
* Learn how to [configure private endpoints for all Azure Cache for Redis tiers](cache-private-link.md).
68+
- Learn how to configure a [VNet injected cache for a Premium Azure Cache for Redis instance](cache-how-to-premium-vnet.md).
69+
- Learn how to configure [firewall rules for all Azure Cache for Redis tiers](cache-configure.md#firewall).
70+
- Learn how to [configure private endpoints for all Azure Cache for Redis tiers](cache-private-link.md).

0 commit comments

Comments
 (0)