Merge pull request #91646 from jaszperez/patch-65

updated where logs are and how to test ports

Author: PRMerger20

articles/active-directory/manage-apps/application-proxy-connector-installation-problem.md

@@ -34,13 +34,16 @@ When the installation of a connector fails, the root cause is usually one of the
 
 3.  **Authentication of the admin** – during installation, the user must provide admin credentials to complete the Connector installation.
 
+> [!NOTE]
+> The Connector installation logs can be found in the %TEMP% folder and can help provide additional information on what is causing an installation failure.
+
 ## Verify connectivity to the Cloud Application Proxy service and Microsoft Login page
 
 **Objective:** Verify that the connector machine can connect to the AAD Application Proxy registration endpoint as well as Microsoft login page.
 
-1.  Open a browser and go to the following web page: <https://aadap-portcheck.connectorporttest.msappproxy.net> , and verify that the connectivity to Central US and East US datacenters with ports 80 and 443 is working.
+1.  On the connector server, run a port test by using [telnet](https://docs.microsoft.com/windows-server/administration/windows-commands/telnet) or other port testing tool to verify that ports 443 and 80 are open.
 
-2.  If any of those ports is not successful (doesn’t have a green checkmark), verify that the Firewall or backend proxy has \*.msappproxy.net with ports 80 and 443 defined correctly.
+2.  If any of those ports is not successful, verify that the Firewall or backend proxy has access to the required domains and ports see, [Prepare your on-premises environment](application-proxy-add-on-premises-application.md#prepare-your-on-premises-environment).
 
 3.  Open a browser (separate tab) and go to the following web page: <https://login.microsoftonline.com>, make sure that you can login to that page.
 
@@ -49,7 +52,7 @@ When the installation of a connector fails, the root cause is usually one of the
 **Objective:** Verify that the connector machine, backend proxy and firewall can support the certificate created by the connector for future trust.
 
 >[!NOTE]
->The connector tries to create a SHA512 cert that is supported by TLS1.2. If the machine or the backend firewall and proxy does not support TLS1.2, the installation fail.
+>The connector tries to create a SHA512 cert that is supported by TLS1.2. If the machine or the backend firewall and proxy does not support TLS1.2, the installation fails.
 >
 >