Links on the page don't work for an Application Proxy application

This article helps you troubleshoot why links on your Azure Active Directory Application Proxy application don't work correctly.


After publishing an Application Proxy app, the only links that work by default in the application are links to destinations contained within the published root URL. The links within the applications aren’t working, the internal URL for the application probably does not include all the destinations of links within the application.

Why does this happen? When clicking a link in an application, Application Proxy tries to resolve the URL as either an internal URL within the same application, or as an externally available URL. If the link points to an internal URL that is not within the same application, it does not belong to either of these buckets and result in a not found error.

There are three ways to resolve this issue. The choices below are in listed in increasing complexity.

  1. Make sure the internal URL is a root that contains all the relevant links for the application. This allows all links to be resolved as content published within the same application.

    If you change the internal URL but don’t want to change the landing page for users, change the Home page URL to the previously published internal URL. This can be done by going to “Azure Active Directory” -> App Registrations -> select the application -> Branding. In the branding section, you see the field “Home Page URL”, which you can adjust to be the desired landing page. If you are still using the legacy App registrations experience the properties tab would show the "Home Page URL" details.


    In order to make the above changes you require rights to modify application objects in Azure AD.The user needs to be assigned Application Administrator role which grants application modificaion rights in Azure AD to the user.

  2. If your applications use fully qualified domain names (FQDNs), use custom domains to publish your applications. This feature allows the same URL to be used both internally and externally.

    This option ensures that the links in your application are externally accessible through Application Proxy since the links within the application to internal URLs are also recognized externally. All links still need to belong to a published application. However, with this option the links do not need to belong to the same application and can belong to multiple applications.

  3. If neither of these options are feasible, there are multiple options for enabling inline link translation. These options include using the Intune Managed Browser, My Apps extension, or using the link translation setting on your application. To learn more about each of these options and how to enable them, see Redirect hardcoded links for apps published with Azure AD Application Proxy.

Next steps

Work with existing on-premises proxy servers