Azure Update Digest (2026-08-05)

Period: today · Items: 2 · Source: Azure official updates RSS

Azure Daily Learning Digest

Today's Intro

There are not many items today, but there is one fairly practical update from a network security perspective. With Azure Firewall explicit proxy now GA, there is now a more flexible option beyond the traditional design question of, “Do we have to control traffic through routing alone?” It is also a great day to connect and understand HTTP/HTTPS proxy settings in browsers and applications with Azure network security.

Today's learning points

· Explicit proxy — a method where an application or browser directly specifies a proxy server and sends HTTP/HTTPS requests through it
· Azure Firewall — a managed firewall that goes beyond simple L3/L4 filtering and can be designed for application-layer traffic control scenarios
· Route-based vs Proxy-based — forced network pathing (UDR/default route) and application proxy settings differ in operational model and scope of application
· HTTP/HTTPS egress control — the security and operational model changes depending on which layer you choose to control outbound internet traffic
· Confidential VM retirement — even security-focused VMs go through generational transitions, so workload lifecycle and SKU migration planning are important

Networking & Security

1 item

GA Generally Available: Explicit proxy in Azure Firewall

• · Azure Firewall’s explicit proxy feature is now generally available (GA).
• · This feature allows applications and browsers to be configured to send HTTP/HTTPS traffic directly to Azure Firewall through proxy settings.
• · In other words, beyond traditional route-based traffic steering, there is now also the option to use Azure Firewall in a proxy-based model.
• · Especially in environments where client-side proxy settings can be configured, you can evaluate web traffic control scenarios without redesigning network routes.

What it is: Explicit proxy is a method in which the client specifies “where to send traffic” through proxy settings rather than routing. This GA means Azure Firewall now officially supports serving as an HTTP/HTTPS proxy endpoint within its supported capabilities.

Why it matters: When learning Azure network security, many people are familiar with path-centric designs such as UDR, forced tunneling, and NAT. This feature broadens that perspective by making application-layer traffic steering another Azure Firewall design option. It is especially useful for comparing outbound control models for end-user browsers and business applications.

Try it: Open the Azure Firewall documentation and review the explicit proxy concept and configuration method, then sketch out a PoC scenario where a test VM or browser is configured to use Azure Firewall as its proxy.
Source: https://azure.microsoft.com/updates?id=568825

Retirements at a glance

• Retirement Nested confidential (cc_v5) VMs — retires on September 1, 2026, resize required in advance — https://azure.microsoft.com/updates?id=568661

Today's learning mission

1. Network security: Compare the Azure Firewall explicit proxy concept with the route-based model, and summarize in which situations a proxy-based design is advantageous
2. Azure Firewall: Assume a test browser or VM environment and draw a configuration diagram that sends HTTP/HTTPS proxy traffic to Azure Firewall
3. Outbound control: When controlling internet egress with Azure Firewall, note the operational differences between a UDR-based forced-routing approach and an explicit proxy-based approach
4. Architecture study: Design your own reference architecture including Azure Firewall explicit proxy for an internal user web access control scenario
5. Infrastructure lifecycle: Check whether any Confidential VMs in use are in the cc_v5 family, and draft an Azure VM SKU migration plan