First, make sure the private network connectors are configured correctly. For more information, see Debug private network connector issues and Debug application proxy application issues.
If errors occur in accessing a published application or in publishing applications, check the following options to see if Microsoft Entra application proxy is working correctly:
You have problems with your application rendering or functioning incorrectly without receiving specific error messages. The problem occurs if you published the article path, but the application requires content that exists outside that path.
For example, if you publish the path https://yourapp/app but the application calls images in https://yourapp/media , they aren't rendered. Make sure that you publish the application using the highest level path you need to include all relevant content. In this example, it would be http://yourapp/ .
Applications can be functional but experience a long latency. Network topology tweaks can make improvements to speed. For an evaluation of different topologies, see the network considerations document.
When you publish an application proxy app, only pages under your root are accessible when accessing the application. If the page isn’t displaying correctly, the root internal URL used for the application may be missing some page resources. To resolve, publish all the resources for the page as part of your application.
Verify if missing resources is the issue. Opening your network tracker, such as Fiddler, or F12 tools in Microsoft Edge. Load the page, and looking for 404 errors. The errors indicate the pages can't be found and that you need to publish them.
As an example, assume you published an expenses application using the internal URL http://myapps/expenses , but the app uses the stylesheet http://myapps/style.css . The stylesheet isn't published in your application, so loading the expenses app throws a 404 error trying to load style.css . In this example, resolve the problem by publishing the application with the internal URL http://myapp/ .
If it isn't possible to publish all resources within the same application, you need to publish multiple applications and enable links between them.
To do so, we recommend using the custom domains solution. However, this solution requires that you own the certificate for your domain and your applications use fully qualified domain names (FQDNs). For other options, see the troubleshoot broken links documentation.
