azure-docs
azure-docs copied to clipboard
MicrosoftDocs
Is it possible to explicitly list the inbound/outbound port requirements for client-side NSGs?
[Enter feedback here] The client-side NSG requirements are probably just the reverse of the inbound/outbound requirements for Redis vnet NSG, but it will be more user-friendly if our official documentation can include a section for this.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 3bced23e-5c67-3a63-06f7-c659ba56b5e7
- Version Independent ID: 10d48e1f-e090-ab51-553c-64655a102c9d
- Content: Configure a virtual network - Premium-tier Azure Cache for Redis instance
- Content Source: articles/azure-cache-for-redis/cache-how-to-premium-vnet.md
- Service: cache
- GitHub Login: @flang-msft
- Microsoft Alias: franlanglois
@yichungyu Thanks for your feedback! We will look into it and update as appropriate.
@yichungyu - Thanks for the feedback. As you suggest "the client-side NSG requirements are probably just the reverse of the inbound/outbound requirements for Redis vnet NSG," Our investment now is in the Private Link as opposed to VNet:
Tier flexibility – Azure Private Link is supported on all our tiers; Basic, Standard, Premium, Enterprise, and Enterprise Flash. Compared to Virtual Network injection, which is only offered on our premium tier.
Simplified Network Security Group (NSG) Rule Management - NSG rules do not need to be configured to adhere to requirements from Azure Cache for Redis.
Azure Policy Support – Ensure all caches in your organization are created with Private Link and audit your organization’s existing caches to verify they all utilize Private Link.
https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-vnet-migration
I will close the issue in a few days.
