Debug Application Proxy application issues
This article helps you troubleshoot issues with Azure Active Directory (Azure AD) Application Proxy applications. If you're using the Application Proxy service for remote access to an on-premises web application, but you're having trouble connecting to the application, use this flowchart to debug application issues.
Before you begin
When troubleshooting Application Proxy issues, we recommend you start with the connectors. First, follow the troubleshooting flow in Debug Application Proxy Connector issues to make sure Application Proxy connectors are configured correctly. If you're still having issues, return to this article to troubleshoot the application.
For more information about Application Proxy, see:
- Remote access to on-premises applications through Application Proxy
- Application Proxy connectors
- Install and register a connector
- Troubleshoot Application Proxy problems and error messages
Flowchart for application issues
This flowchart walks you through the steps for debugging some of the more common issues with connecting to the application. For details about each step, see the table following the flowchart.
|1||Open a browser, access the app, and enter your credentials||Try using your credentials to sign in to the app, and check for any user-related errors, like This corporate app can't be accessed.|
|2||Verify user assignment to the app||Make sure your user account has permission to access the app from inside the corporate network, and then test signing in to the app by following the steps in Test the application. If sign-in issues persist, see How to troubleshoot sign-in errors.|
|3||Open a browser and try to access the app||If an error appears immediately, check to see that Application Proxy is configured correctly. For details about specific error messages, see Troubleshoot Application Proxy problems and error messages.|
|4||Check your custom domain setup or troubleshoot the error||If the page doesn't display at all, make sure your custom domain is configured correctly by reviewing Working with custom domains.
If the page doesn't load and an error message appears, troubleshoot the error by referring to Troubleshoot Application Proxy problems and error messages.
If it takes longer than 20 seconds for an error message to appear, there could be connectivity issue. Go to the Debug Application Proxy connectors troubleshooting article.
|5||If issues persist, go to connector debugging||There could be a connectivity issue between the proxy and the connector or between the connector and the back end. Go to the Debug Application Proxy connectors troubleshooting article.|
|6||Publish all resources, check browser developer tools, and fix links||Make sure the publishing path includes all the necessary images, scripts, and style sheets for your application. For details, see Add an on-premises app to Azure AD.
Use the browser's developer tools (F12 tools in Internet Explorer or Microsoft Edge) and check for publishing issues as described in Application page does not display correctly.
Review options for resolving broken links in Links on the page don't work.
|7||Check for network latency||If the page loads slowly, learn about ways to minimize network latency in Considerations for reducing latency.|
|8||See additional troubleshooting help||If issues persist, find additional troubleshooting articles in the Application Proxy troubleshooting documentation.|