Views:

Applies to Product - Power Automate

What’s happening?
Issue integrating an on-premises API using an HTTP action in Power Automate, receiving an error stating, "The provided host name could not be resolved."


Reason:
The error indicates that the URI being used is not valid or accessible from the current network. This is likely caused by the use of a local or internal host name that is not reachable from the environment where the flow is running.
Possible causes include:

  • Incorrect API host name entered in the HTTP action configuration.
  • DNS resolution issue preventing the host name from being resolved.
  • Network connectivity problems between Power Automate and the on-premises server.
  • Firewall or security settings blocking the request from Power Automate to the on-premises server.
  • The API server may be down or incorrectly configured.
Resolution:
  • Verify that the host name specified in the Power Automate HTTP action matches the correct on-premises server name and that there are no typos or outdated entries.
  • Check if the on-premises server hosting the API is configured to allow connections from Power Automate, including any necessary firewall or network security group settings.
  • Ensure that the DNS settings are correctly configured to resolve the on-premises host name from the environment where Power Automate is running.
  • Test the API access from within the on-premises network using tools such as Postman to confirm connectivity.
  • Consider implementing a custom connector as an alternative method to integrate the on-prem API if the direct HTTP action continues to face resolution issues.