The change was announced on November 17, 2026 under the title "Public Preview: Network Watcher Private Link support." Microsoft's wording is that virtual network flow logs now support flow-log enrichment for Azure Private Link Service. The goal is better visibility into traffic passing through PLS. Microsoft's live Azure Updates page did not display the full record when we looked, so the technical detail below comes from Microsoft Learn's current flow-log documentation.
The problem: every client looks like the same address
Microsoft Learn describes the gap plainly. The source address visible at the backend is commonly the PLS source network address translation (SNAT) address. The platform needs that translated address to deliver traffic. It also makes it hard to tell which client, and which Private Endpoint connection, started a flow.
If you run a service that many customers or business units reach through their own Private Endpoints, your backend logs may show one translated source for everyone. Troubleshooting then becomes guesswork.
What the enrichment adds
The fix is flow log version 5. According to Microsoft, version 5 adds NAT and Private Link context to virtual network flow logs so service providers can trace connections from the original client, through the Private Endpoint and PLS translation layer, to the backend workload.
Each record keeps the backend flow details and adds context that identifies the original source, the translated PLS address information, and the Private Link connection identifier. The field table also lists a PLS Link Identifier. Microsoft says it identifies the Private Endpoint-to-Private Link Service connection associated with the traffic flow.
In practice, you can:
- Follow a connection from client to Private Endpoint, PLS and backend.
- Match backend traffic to the Private Endpoint connection that sent it.
- Keep both the original and the translated endpoint context for investigations and support cases.
Microsoft says the enrichment is for operators who run or support a service exposed through Private Link Service and need end-to-end source visibility. It is especially useful with overlapping address spaces, multiple Private Endpoints or shared backend infrastructure.
What it does not do
The scope is narrower than the announcement title suggests.
- Backend capture only. Microsoft's documentation says version 5 Private Link context applies only to PLS traffic captured at the backend. Capturing traffic at private endpoint NICs isn't currently supported.
- SNAT stays. The documented effect is added correlation context in the log record. Nothing in the documentation says SNAT is removed or that packet delivery changes.
- Not a connectivity tool. This is separate from Network Watcher's Connection troubleshoot, which tests reachability and latency. Flow logs are a record of what happened. They don't run diagnostic probes.
Preview caveats and availability
Microsoft's documentation says support for provisioning flow log version 5 by using Azure PowerShell was introduced in Az PowerShell version 16.4.0.
The overview page also carries a regional note. It says version 5 must be supported in the region and subscription where you enable it. At the time of the Learn page we reviewed, version 5 was listed in West Central US, East Asia and Canary regions. The page tells readers in preview environments to validate the final public schema and regional availability before using it in production automation. That text may change as the preview rolls out, so check the current page before you plan around it.
We could not confirm preview enrollment steps, a full region list, or CLI and API parameters beyond the PowerShell version note. Don't assume a portal toggle or switch exists until you see it in your own tenant.
Practical steps for administrators
These are our own operational suggestions, not Microsoft instructions.
- Confirm you are in scope. The feature matters if you operate a service behind a Private Link Service. It isn't aimed at consumers of Private Endpoints.
- Check region and subscription support. Version 5 has to be available where you enable it.
- Update your tooling. If you provision with PowerShell, check your Az version against the 16.4.0 note.
- Test your parsers. Microsoft's guidance is to use the published version 5 field-order specification and not guess tuple positions. It also says to treat the tuple as versioned data and branch parsing on
flowLogVersion. SIEM queries and dashboards that assume version 2 fields could misread new records. - Keep it off production for now. Preview features are for non-production use and testing.
Costs and related changes
Flow log pricing doesn't change with this announcement, as far as the evidence shows. The Learn page says virtual network flow logs are charged per gigabyte collected with a 5 GB per month free tier per subscription. Storage is billed separately. Traffic Analytics adds per-gigabyte processing charges with no free tier. Microsoft also notes that broader flow-log coverage can mean higher log volumes.
If you still depend on network security group flow logs, note Microsoft's separate timeline. NSG flow logs retire on September 30, 2027, new NSG flow log creation is no longer supported, and Microsoft recommends migrating to virtual network flow logs. That makes virtual network flow logs the long-term option, and version 5 is where the Private Link visibility is being added.
Our take
Private Link is a good privacy and security feature, but a shared SNAT address is a real forensics headache for the provider. Adding the original source and connection ID to the log record addresses that directly. It's an incremental, schema-level change. If you run a Private Link Service, it could save you real investigation time once it reaches general availability. For everyone else, it's a note for the roadmap.
References
- (In preview) Public Preview: Network Watcher Private Link support Azure Updates · 2026-11-17T20:00:32Z
- Virtual Network Flow Logs - Azure Network Watcher | Microsoft Learn learn.microsoft.com
- Azure Private Link availability | Microsoft Learn learn.microsoft.com