networkInterfaceIP into public preview for Azure Network Watcher virtual network (VNet) flow logs. The Azure Updates entry (ID 578787, published November 17, 2026) labels it "In preview." Microsoft's own scale for that label is availability to Azure customers for non-production use and testing, so don't build production alerting on it yet.The update listing doesn't render a detailed description. The schema details below come from Microsoft Learn's VNet flow logs overview, which has a section on the field. My search turned up no independent third-party coverage of the schema.
What the field does
Microsoft Learn says networkInterfaceIP adds capture-side interface context to VNet flow-log records. It records the IP address, or addresses, of the network interface where the flow was captured.
Per the documentation, the field supports four scenarios:
- Resource attribution: tie a record to the right resource ID.
- Capture-point identification: show which interface address saw the traffic.
- Next-hop tracing: correlate records across resources to find intermediate interfaces that traffic passes through.
- Dual-stack visibility: show both IPv4 and IPv6 addresses when the interface is dual-stack.
Before this, a record identified the capturing interface mainly by its MAC address. The docs describe macAddress as the network interface that the flow applies to. MAC addresses are awkward to map back to inventory, so an IP on the record should make that mapping easier. That is my inference. Microsoft doesn't frame it this way.
Schema details for parser owners
Microsoft documents the following behavior:
- Type: a JSON array of IP address strings.
- Scope: record level. It describes the interface that captured the flow, not the flow's source or destination.
- IPv4 interface: the array holds the IPv4 address.
- Dual-stack interface: the array can hold both IPv4 and IPv6 addresses.
- Unidentified interface: the array is empty (
[]) when the IP can't be identified. - Placement: the field sits beside
macAddressandcategoryin the record.
Microsoft's guidance for ingestion pipelines is to keep the field name as networkInterfaceIP, keep the value as an array, and make sure downstream consumers handle IPv4 and IPv6 strings. A parser that assumes a scalar string will break on dual-stack interfaces and on empty arrays.
The overview also mentions a Kusto Query Language property, FlowCapturedAtResourceIp. It is used to pull flow records tied to a specific captured resource IP. The documentation doesn't say which table holds it, so check your Log Analytics schema before writing queries.
What Microsoft hasn't said
The sources don't settle several questions that matter in practice:
- Regional availability and rollout: the update page gives no schedule or region list for this field. The documentation's general note says that if a capability is in preview in your environment, you should validate the final public schema and regional availability before using it in production automation.
- Opt-in: no separate switch is documented for the field. Don't assume it is enabled automatically or that it appears on existing logs.
- Version interaction: the documentation's examples show the field alongside
flowLogVersion4. Flow log version 5, which adds Private Link Service context, is documented separately. Version 5 is currently supported only in West Central US, East Asia and Canary regions. I couldn't confirm how the new field relates to either version beyond those examples. - Cost: VNet flow logs are billed per gigabyte collected, and the guidance on the field doesn't say whether it changes record size.
Practical steps
- Check your current setup. Open the Azure portal, go to Network Watcher, select Logs, then Flow logs. Confirm which VNet, subnet or network interface targets are logged.
- Confirm the prerequisites. The
Microsoft.Insightsresource provider must be registered. The storage account must be in the same region as the virtual network and be a standard account, not premium. - Sample a preview log. Download a
PT1H.jsonfile from theinsights-logs-flowlogfloweventcontainer. Look fornetworkInterfaceIPin the records. If it's absent, the preview hasn't reached your region or subscription. - Harden your parser. Handle an array of strings, an empty array, mixed IPv4 and IPv6, and the field being missing.
- Keep it out of production logic. Use it for exploration until Microsoft publishes the full details.
Avoid duplicate logging
Microsoft recommends disabling NSG flow logs before enabling VNet flow logs on the same underlying workloads. Otherwise you risk duplicate recording and extra cost, or you may get only the VNet flow logs. Where more than one level is configured, the order of preference is NIC, then subnet, then virtual network.
Why it matters
Flow logs are used to analyze flows from compromised IPs and network interfaces, and to feed SIEM and intrusion-detection tools. In an investigation, "which interface saw this?" is a basic question. Answering it with an IP instead of a MAC means less joining against inventory data. This is a small schema change, but it should help correlation in multi-hop and dual-stack environments.
The caveat is that the field is only context. It doesn't replace the flow's own source and destination addresses, and it says nothing about who or what generated the traffic.
References
- (In preview) Public Preview: Network Watcher VNet Flow Logs enriched with networkInterfaceIP field Azure Updates · 2026-11-17T20:00:32Z
- Azure updates | Microsoft Azure azure.microsoft.com
- Virtual Network Flow Logs - Azure Network Watcher | Microsoft Learn learn.microsoft.com