We got the above to work… IF we turn off authentication to the Azure App Proxy… which is obviously less than ideal. The ‘Active Directory OAuth’ overrides the authorization header supplied that’s intended for UiPath. This was found out through intercepting the API call in the cloud.
My current question is, given the above, does anyone have instructions on how to setup a a Microsoft PowerAutomate flow (either a ‘custom connector’ or configure the basic HTTP connector) to communicate with our on-premise UiPath Orchestrator through an Azure App Proxy (that also enforces authentication via ‘Active Directory OAuth’)?
I’m thinking I somehow need to either hit a different endpoint (a Microsoft one) PRIOR to sending the authentication request to UiPath (on-prem)… then maybe use a cookie or something (to authenticate with the proxy) instead of the current method… so the bearer token created and intended for UiPath gets send correctly.