A glowing firewall blocks unauthorized users while securely routing approved devices and services to a cloud database.
Azure Managed Redis has picked up a feature that many administrators had been asking for: IP filtering. It is in public preview, so it is for testing, not production.

A glowing firewall blocks unauthorized users while securely routing approved devices and services to a cloud database. What Microsoft announced​

Microsoft describes the feature as firewall rules for publicly accessible cache endpoints. Connections can be restricted to approved source IP addresses or Azure service tags. It was one of seven Azure Managed Redis updates in Microsoft's Ignite 2026 roundup, published on November 17, 2026. That roundup also covered Redis 8, an agent kit and shard-level metrics, all in preview. Its own example is simple: use the source IPs of your application to narrow which clients can reach a public cache endpoint.

The Azure Updates entry for this item (ID 577589) did not render its details when it was checked. It showed "0 Updates found." The Ignite announcement is therefore the main primary source for the feature description.

Why this matters: closing a documented gap​

Until now, Azure Managed Redis had no IP firewall. Microsoft's migration guidance for Basic, Standard and Premium caches says the service doesn't support virtual network injection or IP-based firewall rules. It tells customers who relied on VNet injection to move to Azure Private Link.

The gap was visible to customers. In a Microsoft Q&A thread from June 2026, a volunteer moderator confirmed that Azure Managed Redis had dropped the legacy IP firewall model. He said there was no direct equivalent to az redis firewall-rules for dynamically allowing public CIDR ranges. Network isolation had been limited to Private Link and the public network access setting. The preview addresses that gap for caches that need to stay publicly reachable.

Azure Cache for Redis already had firewall rules, so this narrows the gap between the two services. It matters most to teams migrating from Azure Cache for Redis. Those teams may have built allow-lists around the old model.

What the feature is, and what it isn't​

IP filtering is a network-layer control. It decides which source addresses or service tags may connect to a public endpoint. It does not replace authentication.

  • Identity: Azure Managed Redis supports Microsoft Entra ID authentication and access keys. Those control who you are once you connect.
  • Network: IP filtering controls where you can connect from.
  • Private connectivity: Where policy requires no public exposure, Private Link remains the stronger option. The preview announcement doesn't change that.

Microsoft's general update definitions also matter here. "In preview" means available for non-production use and testing. Don't move production workloads onto this feature on the strength of the announcement alone.

What isn't documented yet​

The material I could find leaves several practical questions open:

  • Rule limits, and whether ranges and CIDR notation are supported.
  • IPv4 versus IPv6 handling.
  • Portal, CLI and API configuration steps, and the API version.
  • How quickly rule changes take effect.
  • How the rules interact with private endpoints and the public network access setting.
  • Regional availability and preview terms.
  • The start date. A third-party update tracker lists November 30, 2026 as a "preview from" date. I couldn't confirm that against Microsoft sources, so treat it as unverified.

I won't guess at menu paths or commands. Wait for Microsoft's configuration documentation.

Practical guidance for administrators​

Microsoft's existing connectivity guidance already offers some useful habits.

  1. Check client IPs when you test. Microsoft says that if a firewall is configured on the cache, your client IP must be in its rules. A connection that fails right after you enable filtering is a likely sign of a missing source address. The troubleshooting page points to the Firewall item under Settings in the Azure portal for existing firewall configurations. Confirm the equivalent location for this preview in the new documentation.
  2. Test with the built-in command. Microsoft's guide describes az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name>. It sends a ping to verify end-to-end connectivity, using Entra ID authentication by default.
  3. Connect through the hostname. Clients should use the cache DNS name and port 10000. Microsoft also advises relying on the hostname rather than the cache's public IP. The public IP can change, and any networking or security resource that hardcodes it can break.
  4. Don't confuse the two firewalls. Microsoft's guidance says third-party firewalls or proxies on the client side should allow *.redis.azure.net and port 10000. Clustered caches or geo-replication may need more ports. That is client-side egress. It is separate from the new cache-side IP filtering.
  5. Plan for dynamic IPs. Developers on changing home or office IPs were the group most affected by the missing firewall. Until the rule syntax is documented, don't assume dynamic updates through scripts will work.

Analysis​

This is a modest feature, but it is useful. Many real deployments keep a public endpoint behind a short allow-list of app servers. Having to choose between "open to the internet with keys" and "fully private via Private Link" was a harsh trade-off.

The caveats are the usual ones for a preview. Details may change before general availability. Missing documentation leaves operators guessing about limits and behavior. Allow-listing source IPs is also weaker than private connectivity, because IPs can be shared or spoofed upstream, and cloud egress addresses change. This is general industry reasoning, not a Microsoft statement.

Teams planning a migration from Azure Cache for Redis should test the feature in a non-production environment. They should also keep Private Link on the roadmap for sensitive workloads.

 

References

  1. (In preview) Public Preview: IP filtering in Azure Managed Redis Azure Updates 2026-11-17T20:00:32Z
  2. Public Preview: IP filtering in Azure Managed Redis | 365Fanatic Cloud cloud.365fanatic.com
  3. Azure updates | Microsoft Azure azure.microsoft.com