We’re in the process of publishing our on-premises UiPath Orchestrator using Azure Application Proxy. The proxy is configured and working in general, but we’re running into issues with Identity and URL redirection, especially when it comes to login and authentication redirections via Microsoft Entra ID.
Setup Details:
UiPath Orchestrator: On-prem version
Microsoft Entra ID: Used for authentication
Azure Application Proxy: Set up with a connector and external URL
Internal URL: e.g., https://server.local
External URL via Azure App Proxy: e.g., https://orchestrator.msappproxy.net
Issue:
After navigating to the external URL and signing in via Microsoft Entra, the redirection either:
Redirects back to the internal URL (which isn’t reachable externally),
Or results in a error page status #200.
Questions:
Are there specific configurations needed on Orchestrator’s side to support Azure App Proxy?
Is it possible to use Azure App Proxy with an on-prem Orchestrator that uses Microsoft Entra?
Any guidance, working examples, or official documentation references would be greatly appreciated!
The Azure Application Proxy is functioning correctly, as I can access the external link (https://company.msappproxy.net/identity), log in successfully, and the Identity page displays as expected.
Let me explain some of the issues as I see it:
If I access the main external link without /identity
After clicking it, the page fails to load because it redirects to the internal URL:https://local.server.intern. The same happens when clicking Management even though the URL displayed on hover is: https://company.msappproxy.net/identity/management
it still tries to route to the internal address and fails outside the VPN.
Basically, this is the setup I would like to implement—if it’s possible. However, I haven’t been able to find any resources that clearly explain how to configure this.