Merge pull request #95327 from JasonWHowell/securelinks

Fixing http hyperlinks

Author: PMEds28

articles/active-directory/manage-apps/application-proxy-faq.md

@@ -91,7 +91,7 @@ The PrincipalsAllowedToDelegateToAccount method is used when connector servers a
 If the connector servers and the web application service account are in the same domain, you can use Active Directory Users and Computers to configure the delegation settings on each of the connector machine accounts, allowing them to delegate to the target SPN.
 
 If the connector servers and the web application service account are in different domains, Resource-based delegation is used. The delegation permissions are configured on the target web server and web application service account. This method of Constrained Delegation is relatively new. The method was introduced in Windows Server 2012, which supports cross-domain delegation by allowing the resource (web service) owner to control which machine and service accounts can delegate to it. There's no UI to assist with this configuration, so you'll need to use PowerShell.
-For more information, see the whitepaper [Understanding Kerberos Constrained Delegation with Application Proxy](http://aka.ms/kcdpaper).
+For more information, see the whitepaper [Understanding Kerberos Constrained Delegation with Application Proxy](https://aka.ms/kcdpaper).
 
 ## Pass-through authentication
 

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -327,7 +327,7 @@ At the bottom of the page, the root virtual directory `/` points to `site\wwwroo
 
 ![Customize virtual directory](./media/app-service-web-tutorial-custom-domain/customize-virtual-directory.png)
 
-Once the operation completes, your app should return the right page at the root path (for example, http://contoso.com).
+Once the operation completes, your app should return the right page at the root path (for example, `http://contoso.com`).
 
 ## Automate with scripts
 

articles/application-gateway/application-gateway-create-multisite-azureresourcemanager-powershell.md

@@ -256,7 +256,7 @@ Get-AzPublicIPAddress -ResourceGroupName myResourceGroupAG -Name myAGPublicIPAdd
 
 ## Test the application gateway
 
-Enter your domain name into the address bar of your browser. Such as, http://www.contoso.com.
+Enter your domain name into the address bar of your browser. Such as, https://www.contoso.com.
 
 ![Test contoso site in application gateway](./media/application-gateway-create-multisite-azureresourcemanager-powershell/application-gateway-iistest.png)
 

articles/application-gateway/application-gateway-multi-site-overview.md

@@ -17,9 +17,9 @@ Multiple site hosting enables you to configure more than one web application on
 > [!IMPORTANT]
 > Rules are processed in the order they are listed in the portal. It is highly recommended to configure multi-site listeners first prior to configuring a basic listener.  This will ensure that traffic gets routed to the right back end. If a basic listener is listed first and matches an incoming request, it gets processed by that listener.
 
-Requests for http://contoso.com are routed to ContosoServerPool, and http://fabrikam.com are routed to FabrikamServerPool.
+Requests for `http://contoso.com` are routed to ContosoServerPool, and `http://fabrikam.com` are routed to FabrikamServerPool.
 
-Similarly two subdomains of the same parent domain can be hosted on the same application gateway deployment. Examples of using subdomains could include http://blog.contoso.com and http://app.contoso.com hosted on a single application gateway deployment.
+Similarly two subdomains of the same parent domain can be hosted on the same application gateway deployment. Examples of using subdomains could include `http://blog.contoso.com` and `http://app.contoso.com` hosted on a single application gateway deployment.
 
 ## Host headers and Server Name Indication (SNI)
 

articles/application-gateway/create-multiple-sites-portal.md

@@ -215,7 +215,7 @@ After the application gateway is created with its public IP address, you can get
 
 ## Test the application gateway
 
-1. Enter your domain name into the address bar of your browser. Such as, http://www.contoso.com.
+1. Enter your domain name into the address bar of your browser. Such as, `http://www.contoso.com`.
 
     ![Test contoso site in application gateway](./media/create-multiple-sites-portal/application-gateway-iistest.png)
 

articles/application-gateway/migrate-v1-v2.md

@@ -151,7 +151,7 @@ Here are a few scenarios where your current application gateway (Standard) may r
 
   * If you use public IP addresses on your application gateway, you can do a controlled, granular migration using a Traffic Manager profile to incrementally route traffic (weighted traffic routing method) to the new v2 gateway.
 
-    You can do this by adding the DNS labels of both the v1 and v2 application gateways to the [Traffic Manager profile](../traffic-manager/traffic-manager-routing-methods.md#weighted-traffic-routing-method), and CNAMEing your custom DNS record (for example, www.contoso.com) to the Traffic Manager domain (for example, contoso.trafficmanager.net).
+    You can do this by adding the DNS labels of both the v1 and v2 application gateways to the [Traffic Manager profile](../traffic-manager/traffic-manager-routing-methods.md#weighted-traffic-routing-method), and CNAMEing your custom DNS record (for example, `www.contoso.com`) to the Traffic Manager domain (for example, contoso.trafficmanager.net).
   * Or, you can update your custom domain DNS record to point to the DNS label of the new v2 application gateway. Depending on the TTL configured on your DNS record, it may take a while for all your client traffic to migrate to your new v2 gateway.
 * **Your clients connect to the frontend IP address of your application gateway**.
 

articles/application-gateway/multiple-site-overview.md

@@ -18,9 +18,9 @@ Multiple site hosting enables you to configure more than one web application on
 > [!IMPORTANT]
 > Rules are processed in the order they are listed in the portal. It is highly recommended to configure multi-site listeners first prior to configuring a basic listener.  This will ensure that traffic gets routed to the right back end. If a basic listener is listed first and matches an incoming request, it gets processed by that listener.
 
-Requests for http://contoso.com are routed to ContosoServerPool, and http://fabrikam.com are routed to FabrikamServerPool.
+Requests for `http://contoso.com` are routed to ContosoServerPool, and `http://fabrikam.com` are routed to FabrikamServerPool.
 
-Similarly two subdomains of the same parent domain can be hosted on the same application gateway deployment. Examples of using subdomains could include http://blog.contoso.com and http://app.contoso.com hosted on a single application gateway deployment.
+Similarly two subdomains of the same parent domain can be hosted on the same application gateway deployment. Examples of using subdomains could include `http://blog.contoso.com` and `http://app.contoso.com` hosted on a single application gateway deployment.
 
 ## Host headers and Server Name Indication (SNI)
 

articles/application-gateway/redirect-internal-site-powershell.md

@@ -292,11 +292,11 @@ Get-AzPublicIPAddress -ResourceGroupName myResourceGroupAG -Name myAGPublicIPAdd
 
 ## Test the application gateway
 
-Enter your domain name into the address bar of your browser. Such as, [http://www.contoso.com](http://www.contoso.com).
+Enter your domain name into the address bar of your browser. Such as, [https://www.contoso.com](https://www.contoso.com).
 
 ![Test contoso site in application gateway](./media/redirect-internal-site-powershell/application-gateway-iistest.png)
 
-Change the address to your other domain, for example http://www.contoso.org and you should see that the traffic has been redirected back to the listener for www.contoso.com.
+Change the address to your other domain, for example https://www.contoso.org and you should see that the traffic has been redirected back to the listener for `www.contoso.com`.
 
 ## Next steps
 

articles/application-gateway/self-signed-certificates.md

@@ -82,7 +82,7 @@ Use the following command to generate the key for the server certificate.
 The CSR is a public key that is given to a CA when requesting a certificate. The CA issues the certificate for this specific request.
 
 > [!NOTE]
-> The CN (Common Name) for the server certificate must be different from the issuer’s domain. For example, in this case, the CN for the issuer is www.contoso.com and the server certificate’s CN is www.fabrikam.com
+> The CN (Common Name) for the server certificate must be different from the issuer’s domain. For example, in this case, the CN for the issuer is `www.contoso.com` and the server certificate’s CN is `www.fabrikam.com`.
 
 
 1. Use the following command to generate the CSR:

articles/application-gateway/troubleshoot-app-service-redirection-app-service-url.md

@@ -71,7 +71,7 @@ Set-Cookie: ARRAffinity=b5b1b14066f35b3e4533a1974cacfbbd969bf1960b6518aa2c2e2619
 
 X-Powered-By: ASP.NET
 ```
-In the previous example, notice that the response header has a status code of 301 for redirection. The location header has the app service’s host name instead of the original host name www.contoso.com.
+In the previous example, notice that the response header has a status code of 301 for redirection. The location header has the app service’s host name instead of the original host name `www.contoso.com`.
 
 ## Solution: Rewrite the location header
 
@@ -92,9 +92,9 @@ You must own a custom domain and follow this process:
 
     ![App service custom domain list](./media/troubleshoot-app-service-redirection-app-service-url/appservice-2.png)
 
-- Your app service is ready to accept the host name www.contoso.com. Change your CNAME entry in DNS to point it back to the application gateway's FQDN, for example, appgw.eastus.cloudapp.azure.com.
+- Your app service is ready to accept the host name `www.contoso.com`. Change your CNAME entry in DNS to point it back to the application gateway's FQDN, for example, `appgw.eastus.cloudapp.azure.com`.
 
-- Make sure that your domain www.contoso.com resolves to the application gateway's FQDN when you do a DNS query.
+- Make sure that your domain `www.contoso.com` resolves to the application gateway's FQDN when you do a DNS query.
 
 - Set your custom probe to disable **Pick Hostname from Backend HTTP Settings**. In the Azure portal, clear the check box in the probe settings. In PowerShell, don't use the **-PickHostNameFromBackendHttpSettings** switch in the **Set-AzApplicationGatewayProbeConfig** command. In the host name field of the probe, enter your app service's FQDN, example.azurewebsites.net. The probe requests sent from the application gateway carry this FQDN in the host header.
 
@@ -105,7 +105,7 @@ You must own a custom domain and follow this process:
 
 - Associate the custom probe back to the back-end HTTP settings, and verify that the back end is healthy.
 
-- The application gateway should now forward the same host name, www.contoso.com, to the app service. The redirection happens on the same host name. Check the following example request and response headers.
+- The application gateway should now forward the same host name, `www.contoso.com`, to the app service. The redirection happens on the same host name. Check the following example request and response headers.
 
 To implement the previous steps using PowerShell for an existing setup, use the sample PowerShell script that follows. Note how we haven't used the **-PickHostname** switches in the probe and HTTP settings configuration.