Power Platform Community Forum Thread Details

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.

User's image

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.

Categories:

Power Automate Desktop

Hi @KL-11031833-0,

Yes, you are right, it is not listed! Azure Table Storage is not supported for Power Platform VNet Integration.

It is missing from the official list of VNet‑supported connectors and services, so Power Automate cannot reach it when an environment uses delegated subnet integration. The correct workaround is to introduce a VNet‑integrated API layer (Azure Functions or API Management) and consume Table Storage through that secured endpoint.

By placing a "proxy" layer that does support VNet integration between Power Automate and Table Storage, you bridge the gap.

Alternate approaches:

Option 1 — Use an Azure Function as a VNet‑integrated proxy
Option 2 — Use an API Management instance inside or peered with the VNet
Option 3 - Build a Custom Connector
Option 4 - Move data to a supported storage service (Azure Blob Storage/Azure File Storage/Azure SQL / Azure SQL DW)

Component	Role	Integration Method
Azure Function	Acts as the Data Access Layer (DAL).	Enable Outbound VNet Integration on the Function App.
API Management	Provides a managed endpoint for the Flow.	Deploy in Internal/External VNet mode.
Custom Connector	Connects Power Automate to the API layer.	Traffic stays within the VNet boundary.
Supported Storage	Migrate or replicate to supported storage.	Azure Blob/File Storage, Azure SQL/Azure SQL DW.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.