Power Platform VNet support covers supported outbound traffic

Power Platform VNet support lets supported components make outbound connections to enterprise resources through a delegated subnet. Those resources don’t need to be exposed over the public internet for the supported connection. This isn’t a blanket setting that routes every connector or every Power Platform request through your VNet.

What it covers

Microsoft documents VNet support for Dataverse plugins and supported connectors. Examples include supported connections to private Azure resources and services hosted inside an enterprise network. Check the current supported scenarios before designing around a particular connector.

For those connections, Power Platform uses the delegated subnet to reach the resource. Network administrators can apply the subnet’s network policies to the traffic. Other connectors and platform traffic aren’t automatically covered by this path.

What to check before setup

VNet support uses Azure subnet delegation and an enterprise policy. Review the setup requirements, supported regions, and connector list before creating the policy. Size the subnet for the number and type of environments you plan to associate with it instead of assuming that one CIDR size fits every tenant.

Test the exact connector or Dataverse plugin against the private resource, including DNS and firewall rules. Keep data loss prevention policies in the design too. VNet support controls a network path; DLP policies control which connectors makers can use.

Sources

• Microsoft Azure Virtual Network support, Microsoft Learn
• Set up and configure VNet support, Microsoft Learn