A cloud-based workflow connects securely to a protected data center in a bright blue digital illustration.
Microsoft has announced virtual network integration for Logic Apps Automation in public preview. The announcement is short on detail, but the history around it explains what it likely means for you.

A cloud-based workflow connects securely to a protected data center in a bright blue digital illustration. What was announced​

The Azure Updates entry is titled "[In preview] Public Preview: Virtual network integration in Logic Apps Automation." Microsoft's Ignite 2026 post on the Azure Integration Services blog, dated November 17, 2026, backs it up. Logic Apps Automation is a new Logic Apps SKU that Microsoft first put into public preview at Build 2026. The Ignite post says Microsoft is adding built-in connectors for GitHub, Azure DevOps, Azure Monitor Logs, Azure Resource Graph, and Azure Advisor. It also adds virtual network integration "for access to private enterprise resources."

That is the full extent of the official announcement. The Ignite post doesn't say which network topologies work, which regions have it, how to configure it, or whether inbound traffic is covered. The Azure Updates page I could retrieve showed no entry detail, so the title and date are all I have from it.

Why this is more than a new checkbox​

This feature has a history. When Automation launched at Build, Microsoft's launch post listed isolated compute, virtual network integration and private endpoints among the day-one enterprise capabilities. Microsoft Learn's comparison page also lists virtual networks and private endpoints under Automation's isolation features.

Independent commentary in the preview period was less certain. Blogger Sjoerd de Wiggers wrote that the launch post called VNet and private endpoints a day-zero capability, while an MVP testing the preview reported it as missing. He also noted that the same launch post listed "VNet support and private endpoints" in its coming-soon section.

The most reasonable reading is that the launch messaging was ahead of the shipped product. This November announcement appears to be the point where the capability is formally in preview. That is my inference from these sources, not something Microsoft has said. If you tried Automation earlier and couldn't reach private resources, it is worth testing again.

Don't confuse it with Standard Logic Apps​

Logic Apps Standard has supported VNet integration for years. The new item concerns Automation only. Microsoft Learn says Automation and Standard share the same runtime, connectors and management tools in some respects, but they are separate offerings. Automation uses dedicated compute that scales to zero, while Standard compute is configured and managed by you.

Standard's documented behavior is a useful model for what to ask about, but it is not a spec for Automation. Microsoft documents that in Standard, private endpoints handle inbound traffic and virtual network integration handles outbound traffic. Treat the same split as an open question for Automation until Microsoft documents it. "VNet integration" alone does not mean your workflow endpoints become private.

Standard details that may or may not carry over​

These come from Standard documentation. Microsoft has not confirmed that any of them apply to Automation.

  • Subnet: Standard requires a subnet without delegations. Microsoft recommends a /26 and says the portal minimum is /27. The subnet size can't be changed after assignment.
  • Connectors: Built-in connectors run in the same cluster as the runtime and can use VNet integration. Shared managed connectors run in separate multitenant clusters and can't. If your subnet has an NSG or firewall, it has to allow outbound traffic to the managed connectors' regional IP addresses.
  • DNS: If you use your own DNS server, Standard uses the WEBSITE_DNS_SERVER and WEBSITE_DNS_ALT_SERVER app settings.
  • Ports: In Standard, when backend storage sits behind a private endpoint, the documented ports are TCP 443, TCP 445, and TCP 20000 to 30000.

Connector behavior is the one to watch. If Automation follows the Standard pattern, a workflow that mixes built-in and managed connectors could reach some private systems and not others.

What to check before you rely on it​

This is still a preview. Microsoft defines preview as available for non-production use and testing. It also isn't clear that every customer, region or subscription can use the feature yet. Before piloting it, confirm these points in Automation-specific documentation or in a test environment:

  1. Whether your region and subscription are eligible.
  2. Whether the integration covers outbound traffic, inbound traffic, or both.
  3. What subnet, delegation and sizing requirements apply.
  4. How DNS and routing work for private name resolution.
  5. Which connectors, built-in versus managed, can reach private resources.
  6. What firewall and NSG rules the workflow needs.
  7. What preview limitations or unsupported features are listed.

Bottom line​

The announcement is brief, but it matters to teams that want AI-driven workflows to touch internal systems without exposing them to the internet. The Ignite blog is the main evidence of what is in preview, and the earlier Build-era discrepancy is a reason to test before you commit. Keep early trials to non-production workloads, and don't rely on Standard's network behavior until Microsoft publishes Automation's own setup guide.

 

References

  1. (In preview) Public Preview: Virtual network integration in Logic Apps Automation Azure Updates 2026-11-17T20:00:32Z
  2. Secure Traffic between Standard Workflows and Virtual Networks - Azure Logic Apps learn.microsoft.com
  3. Compare Automation Services - Azure Logic Apps Automation | Microsoft Learn learn.microsoft.com