Power Platform Community Forum Thread Details

I have a Power Platform solution where Power Automate needs to call an internal API exposed through API Management, and the backend is hosted in a private network with Private DNS.

The issue is that Power Platform / Power Automate cannot resolve the internal DNS name of the API endpoint.

What is the recommended setup to allow Power Platform to connect to this kind of private internal endpoint?

Categories:

General topics

Using flows

@KW-18110402-0

You need the on-premises data gateway for this. That's Microsoft's recommended way to connect Power Automate to anything sitting inside a private network.

The gateway installs on a machine inside your network, handles the DNS resolution locally, and acts as the bridge between Power Automate in the cloud and your internal API endpoint. Since it's inside your network it can reach your private DNS no problem.

For the API Management side, use the HTTP with on-premises data gateway connector in Power Automate and point it at your internal APIM URL. The gateway handles the rest.

One thing to make sure , the machine running the gateway needs line of sight to your APIM endpoint and private DNS. If APIM is locked down to a VNet, the gateway machine needs to be either inside that VNet or able to reach it.

If you're on a larger enterprise setup and want something more scalable, VNet data gateway is the newer option , runs inside your Azure VNet directly without needing a physical machine to manage.

https://www.microsoft.com/en-us/power-platform/blog/power-automate/on-premise-apis/

https://usmanjalil.medium.com/part-1-call-an-on-premise-web-api-endpoint-in-power-automate-cloud-flow-with-a-data-gateway-2da1b926b3c4

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥