Azure Table Storage with Power Platform VNet Integration

Question

Hello everyone,

I’m currently troubleshooting an issue where Power Automate (Power Platform) with Virtual Network integration is unable to connect to Azure Table Storage.

While reviewing the Microsoft documentation for Virtual Network support in Power Platform, I noticed that Azure Table Storage isn’t listed among the supported connectors.

Documentation reviewed:

https://learn.microsoft.com/en-us/power-platform/admin/vnet-support-overview

https://learn.microsoft.com/en-us/power-platform/admin/virtual-network-support-whitepaper

Based on this information, it appears that Azure Table Storage may not currently be supported when using Power Platform VNet integration.

Is there any recommended workaround or supported architecture that would allow accessing Table Storage in this scenario?

Any confirmation or guidance would be greatly appreciated.

Thank you.

Answer 1

Hello @LeRoy, Kevin

Thanks for reaching out to Microsoft Q&A.

Power platform related is currently not supported in the Q&A forums, the supported products are listed over here Supported products on MS Q&A (more to be added later on).

You can ask the experts in the dedicated MS Power platform community forum.

Can you please open as a new thread in MS Power platform community Find Answers | Microsoft Power Platform Community

I hope it helps! and do let me know if you have further queries.

Answer 2

Azure Table Storage isn’t listed among the connectors and services that support Azure subnet delegation for Power Platform Virtual Network support, so it isn’t supported directly in a VNet-integrated Power Platform environment.

When Virtual Network support is enabled for an environment, all supported services (Dataverse plug-ins and the listed connectors) run inside the delegated subnet and must comply with the network policies there. Calls to public endpoints that aren’t reachable via private connectivity will fail unless explicitly allowed by the network configuration.

Given the current supported list (SQL Server, Azure SQL Data Warehouse, Azure Queues, Azure Blob/File Storage, Azure Key Vault, HTTP with Microsoft Entra ID, Snowflake, Databricks, AI search, and custom connectors), the viable pattern for Azure Table Storage is to introduce an intermediate service that is supported in the VNet and have that service access Table Storage on behalf of Power Platform. Typical options based on the documented patterns are:

1. Dataverse plug-in in the VNet
   • Implement a Dataverse plug-in that runs in the VNet-enabled environment.
   • The plug-in connects to a service inside the same VNet (for example, a Web API or Azure Function) using private endpoints, as described for API workloads.
   • That Web API/Azure Function then accesses Azure Table Storage (over private endpoint or allowed outbound rules) and returns the data to the plug-in.
2. Custom connector fronting a VNet-hosted API
   • Host a Web API in the VNet (or behind private endpoints) that exposes the required operations over HTTP.
   • Use a custom connector (which is supported with VNet integration) to call this API from Power Apps/Power Automate.
   • The API performs all interaction with Azure Table Storage.
3. HTTP with Microsoft Entra ID (preauthorized)
   • If the intermediary API is protected by Microsoft Entra ID and reachable privately, use the HTTP with Microsoft Entra ID (preauthorized) connector (supported with VNet) to call it.
   • The API then reads/writes Azure Table Storage.

In all cases, the documented considerations apply:

• Review apps, flows, and plug-in code so that, once VNet support is enabled, they no longer rely on direct calls to public endpoints that are blocked by the VNet.
• Ensure any services used as intermediaries are reachable via private endpoints or otherwise allowed by the delegated subnet’s network policies.

There is no direct, VNet-supported Azure Table Storage connector listed; the supported architecture is to use Dataverse plug-ins, custom connectors, or HTTP with Microsoft Entra ID to reach an API inside the VNet, and let that API handle Table Storage access.

---

References:

• Virtual Network support overview
• Virtual Network support white paper
• Set up virtual network support for Power Platform (manual)
• Set up virtual network support for Power Platform (powershell)