Connecting Power Automate flow to send API requests to On-Premise Orchestrator

We have an On-Premise Orchestrator setup , and i am trying to automate the triggering of a bot based on an email received in Outlook, so trying to use the MS Power Automate as the middle layer. But connecting from Power Automate to an On-Premise Orchestrator is challenging. PA is not recognizing the Orchestrator Server. I get the following error- UnresolvableHostName , HTTP request failed with status code- ‘NameResolutionFailure’ . Has anyone encountered this? Is it possible to connect from Office 365 ¶ to OnPremise Orch.


it is possible, for one project I created with Microsoft Flow an app that set a trigger to enable on an On-Premise Orchestrator. It performs three HTTP requests to do this.

Did you set the right address? ex. https://{orchestrator}/api/Account/Authenticate
Can you test the request on Swagger?

Regards, Gio

https://{[orchestrator]}/api/Account/Authenticate . I am using the above link and it works fine with Swagger. But when i connect from Microsoft Flow it gives the error. Did you update any settings in the Orchestrator server side ? could you send me the screen shot of your PA HTTP request (of course without any sensitive information ).


in the Orchestrator, you should set the permissions (but if you don’t have the permission, the response will be 401 Unauthorized). Is the Orchestrator visible from the Internet or it is on a private LAN?

Here an HTTP request example, to retrieve a trigger (basically there are only the mandatory proprieties: schedulerID, authorization and “X-UIPATH-OrganizationUnitId”):

Regards, Gio

I was asking the screenshot for this specific HTTP request https://{[orchestrator]}/api/Account/Authenticate .

Also what permissions are you referring to set in orchestrator . The onpremise orchestrator is in our work network and we login using SSO .

Aha, ok.

So, here is the authentication request based on username and password:

The permissions to set are indicated in the Orchestrator guide or Swagger details:
Permissions Per Endpoint (


Hi @q.gio

Were you able to find a solution to your problem? I am facing the exact same situation. Power Automate works smoothly with the cloud orchestrator API, but not with an on-premise installation.

Am able to process requests using Postman or even using UiPath’s own HTTP request activity from another system, which is executed over the internet. So the application is available online.

Hi @Shabbir_Abid,

I used this with an on-premise version of the Orchestrator. So in my situation, it worked good. Which kind of error the HTTP request returns?

Regards, Gio

Hi @q.gio , am getting this error:

“error”: {
“code”: “BadRequest”,
“message”: “Http request failed with status code ‘ConnectFailure’ and status message: ‘Unable to connect to the remote server’.”

Just replacing the on-premise URL with a cloud orchestrator URL fixes the issue in Power Automate. But the on-premise URL itself is working, when accessed through Postman


in your situation is difficult, it should analyze your IT system because Power Automate cannot access your orchestrator. Probably Postman uses your authorizations while Power Automate runs on a Microsoft server and cannot connect with Orchestrator. Maybe your on-premise Orchestrator runs under a VPN or isn’t visible from the Internet.

Regards, Gio

Thank you @q.gio, for those inputs. My issue is that I have tried with Postman on a completely disconnected system (a different country), and we made the Orchestrator publicly accessible. I can now connect to the application without the VPN setup which was needed earlier.

So Orchestrator seems to be hosted correctly, and that I can access it from a different country without relying on a VPN seems to confirm that. Why Power Automate is then unable to connect is quite worrying.

Hi @q.gio,

I follow On Promise method. I have no issue when debugging in postman with a VPN connection and I am able to get the result. But when I run it from power automate with or without a VPN connection, it gives me this error:

UnresolvableHostName . Http request failed with status code ‘NameResolutionFailure’ and status message: 'The remote name could not be resolved: ‘{{url}}’

Like you said it could be the Orchestrator isn’t visible from the internet. What should I tell IT to resolve this problem?