Merge pull request #115357 from craigcaseyMSFT/vcraic0514

fix broken links from OPS report

Author: Court72

articles/active-directory/develop/tutorial-v2-aspnet-daemon-web-app.md

@@ -232,8 +232,8 @@ Visual Studio will publish the project and automatically open a browser to the p
 1. Go back to the [Azure portal](https://portal.azure.com).
 1. In the left pane, select the **Azure Active Directory** service, and then select **App registrations**.
 1. Select the **dotnet-web-daemon-v2** application.
-1. On the **Authentication** page for your application, update the **Logout URL** fields with the address of your service. For example, use [https://dotnet-web-daemon-v2-contoso.azurewebsites.net](https://dotnet-web-daemon-v2-contoso.azurewebsites.net).
-1. From the **Branding** menu, update the **Home page URL** to the address of your service. For example, use [https://dotnet-web-daemon-v2-contoso.azurewebsites.net](https://dotnet-web-daemon-v2-contoso.azurewebsites.net).
+1. On the **Authentication** page for your application, update the **Logout URL** fields with the address of your service. For example, use `https://dotnet-web-daemon-v2-contoso.azurewebsites.net`.
+1. From the **Branding** menu, update the **Home page URL** to the address of your service. For example, use `https://dotnet-web-daemon-v2-contoso.azurewebsites.net`.
 1. Save the configuration.
 1. Add the same URL in the list of values of the **Authentication** > **Redirect URIs** menu. If you have multiple redirect URLs, make sure that there's a new entry that uses the app service's URI for each redirect URL.
 

articles/active-directory/hybrid/reference-connect-government-cloud.md

@@ -36,7 +36,7 @@ Before you deploy the Pass-through Authentication agent, verify whether a firewa
 |URL |How it's used|
 |-----|-----|
 |&#42;.msappproxy.us</br>&#42;.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Azure AD cloud service. |
-|mscrl.microsoft.us:80 </br>crl.microsoft.us:80 </br>ocsp.msocsp.us:80 </br>www.microsoft.us:80| The agent uses these URLs to verify certificates.|
+|`mscrl.microsoft.us:80` </br>`crl.microsoft.us:80` </br>`ocsp.msocsp.us:80` </br>`www.microsoft.us:80`| The agent uses these URLs to verify certificates.|
 |login.windows.us </br>secure.aadcdn.microsoftonline-p.com </br>&#42;.microsoftonline.us </br>&#42;.microsoftonline-p.us </br>&#42;.msauth.net </br>&#42;.msauthimages.net </br>&#42;.msecnd.net</br>&#42;.msftauth.net </br>&#42;.msftauthimages.net</br>&#42;.phonefactor.net </br>enterpriseregistration.windows.net</br>management.azure.com </br>policykeyservice.dc.ad.msft.net</br>ctdl.windowsupdate.us:80| The agent uses these URLs during the registration process.
 
 ### Install the agent for the Azure Government cloud

articles/active-directory/manage-apps/application-proxy-configure-connectors-with-proxy-servers.md

@@ -159,7 +159,7 @@ Now you should see all traffic flowing through the proxy. If you have problems,
 
 The best way to identify and troubleshoot connector connectivity issues is to take a network capture while starting the connector service. Here are some quick tips on capturing and filtering network traces.
 
-You can use the monitoring tool of your choice. For the purposes of this article, we used Microsoft Message Analyzer. You can [download it from Microsoft](https://www.microsoft.com/download/details.aspx?id=44226).
+You can use the monitoring tool of your choice. For the purposes of this article, we used Microsoft Message Analyzer.
 
 The following examples are specific to Message Analyzer, but the principles can be applied to any analysis tool.
 

articles/active-directory/saas-apps/apptio-tutorial.md

@@ -127,11 +127,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure Apptio SSO
 
-To configure single sign-on on **Apptio** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Apptio support team](https://www.apptio.com/about/contact). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Apptio** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Apptio support team](https://www.apptio.com/resources/customer-support/). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create Apptio test user
 
-In this section, you create a user called B.Simon in Apptio. Work with [Apptio support team](https://www.apptio.com/about/contact) to add the users in the Apptio platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called B.Simon in Apptio. Work with [Apptio support team](https://www.apptio.com/resources/customer-support/) to add the users in the Apptio platform. Users must be created and activated before you use single sign-on.
 
 ## Test SSO 
 

articles/active-directory/saas-apps/awardspring-tutorial.md

@@ -157,7 +157,7 @@ To configure single sign-on on **AwardSpring** side, you need to send the downlo
 In this section, a user called B.Simon is created in AwardSpring. AwardSpring supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in AwardSpring, a new one is created after authentication.
 
 > [!Note]
-> If you need to create a user manually, contact [AwardSpring support team](maito:[email protected]).
+> If you need to create a user manually, contact [AwardSpring support team](mailto:[email protected]).
 
 ## Test SSO
 

articles/active-directory/saas-apps/cornerstone-ondemand-provisioning-tutorial.md

@@ -34,7 +34,7 @@ The scenario outlined in this tutorial assumes that you have:
 * A user account in Cornerstone OnDemand with admin permissions.
 
 > [!NOTE]
-> The Azure AD provisioning integration relies on the [Cornerstone OnDemand web service](https://help.csod.com/help/csod_0/Content/Resources/Documents/WebServices/CSOD_-_Summary_of_Web_Services_v20151106.pdf). This service is available to Cornerstone OnDemand teams.
+> The Azure AD provisioning integration relies on the [Cornerstone OnDemand web service](https://www.cornerstoneondemand.com/). This service is available to Cornerstone OnDemand teams.
 
 ## Add Cornerstone OnDemand from the Azure Marketplace
 

articles/active-directory/saas-apps/cylanceprotect-tutorial.md

@@ -145,7 +145,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure CylancePROTECT SSO
 
-To configure single sign-on on **CylancePROTECT** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [CylancePROTECT support team](https://www.cylance.com/resources/support/support-overview.html). They set this setting to have the SAML SSO connection set properly on both sides. For more information, use Cylance documentation: [https://support.cylance.com/s/article/Use-Microsoft-Azure-with-CylancePROTECT4](https://support.cylance.com/s/article/Use-Microsoft-Azure-with-CylancePROTECT4).
+To configure single sign-on on **CylancePROTECT** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [CylancePROTECT support team](https://www.cylance.com/en-us/resources/support/support-overview.html). They set this setting to have the SAML SSO connection set properly on both sides. For more information, use Cylance documentation: [https://support.cylance.com/s/article/Use-Microsoft-Azure-with-CylancePROTECT4](https://support.cylance.com/s/article/Use-Microsoft-Azure-with-CylancePROTECT4).
 
 ### Create CylancePROTECT test user
 

articles/active-directory/saas-apps/juno-journey-provisioning-tutorial.md

@@ -36,7 +36,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 * [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) 
 * A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
-*  A [Juno Journey tenant](https://www.junojourney.com/getstartedwithjuno).
+*  A [Juno Journey tenant](https://www.junojourney.com/blank).
 *  A user account in Juno Journey with Admin permissions.
 
 ## Step 1. Plan your provisioning deployment

articles/active-directory/saas-apps/panopto-tutorial.md

@@ -107,7 +107,7 @@ To configure Azure AD single sign-on with Panopto, perform the following steps:
     `https://<tenant-name>.panopto.com`
 
 	> [!NOTE]
-	> The value is not real. Update the value with the actual Sign-On URL. Contact [Panopto Client support team](mailto:[email protected]%E2%80%8E) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+	> The value is not real. Update the value with the actual Sign-On URL. Contact [Panopto Client support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 5. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Federation Metadata XML** from the given options as per your requirement and save it on your computer.
 

articles/active-directory/saas-apps/performancecentre-tutorial.md

@@ -108,7 +108,7 @@ To configure Azure AD single sign-on with PerformanceCentre, perform the followi
     `http://<companyname>.performancecentre.com`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [PerformanceCentre Client support team](https://www.performancecentre.com/contact-us/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+	> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [PerformanceCentre Client support team](https://www.performio.co/contact-us) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 4. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Federation Metadata XML** from the given options as per your requirement and save it on your computer.