Skip to content

Commit 81424eb

Browse files
committed
Minor linter, acrolinx fixes
1 parent 675a06a commit 81424eb

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Azure Private Link provides private connectivity from a virtual network to Azure
3232
> Enterprise/Enterprise Flash tier does not support `publicNetworkAccess` flag.
3333
3434
- Any external cache dependencies don't affect the VNet's NSG rules.
35-
- Persisting to any Storage accounts protected with firewall rules is supported when using managed identity to connect to Storage account, see more [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md#how-to-export-if-i-have-firewall-enabled-on-my-storage-account)
35+
- Persisting to any storage accounts protected with firewall rules is supported when using managed identity to connect to Storage account, see more [Import and Export data in Azure Cache for Redis](cache-how-to-import-export-data.md#how-to-export-if-i-have-firewall-enabled-on-my-storage-account)
3636

3737
### Limitations of Private Link
3838

@@ -55,11 +55,11 @@ Virtual Network (VNet) is the fundamental building block for your private networ
5555

5656
### Limitations of VNet injection
5757

58-
- Creating and maintaining virtual network configurations can be error prone. Troubleshooting is challenging. Incorrect virtual network configurations can lead to various issues:
59-
- obstructed metrics transmission from your cache instances,
60-
- failure of replica node to replicate data from primary node,
61-
- potential data loss,
62-
- failure of management operations like scaling,
58+
- Creating and maintaining virtual network configurations can be error prone. Troubleshooting is challenging. Incorrect virtual network configurations can lead to various issues:
59+
- obstructed metrics transmission from your cache instances,
60+
- failure of replica node to replicate data from primary node,
61+
- potential data loss,
62+
- failure of management operations like scaling,
6363
- and in the most severe scenarios, loss of availability.
6464
- VNet injected caches are only available for Premium-tier Azure Cache for Redis instances.
6565
- 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.

0 commit comments

Comments
 (0)