Merge pull request #112269 from craigcaseyMSFT/vcraic0421

ttorble · web-flow · commit 5144eda6cffd · 2020-04-22T08:31:47.000+01:00
fix broken links from OPS report
diff --git a/articles/active-directory/saas-apps/cognidox-tutorial.md b/articles/active-directory/saas-apps/cognidox-tutorial.md
@@ -103,7 +103,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 	| Name | Namespace  |  Transformation | Parameter 1 |
 	| ---------------| --------------- | --------- |
-	| wanshort | http://appinux.com/windowsaccountname2 | ExtractMailPrefix() | user.userprincipalname |
+	| wanshort | http:\//appinux.com/windowsaccountname2 | ExtractMailPrefix() | user.userprincipalname |
 
 
 	a. Click **Add new claim** to open the **Manage user claims** dialog.
diff --git a/articles/active-directory/saas-apps/cs-stars-tutorial.md b/articles/active-directory/saas-apps/cs-stars-tutorial.md
@@ -109,7 +109,7 @@ To configure Azure AD single sign-on with CS Stars, perform the following steps:
     `https://<subdomain>.csstars.com/enterprise/`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [CS Stars Client support team](http://www.riskonnectclearsight.com/support/) 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 [CS Stars Client support team](https://riskonnect.com/support/) 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.
 
@@ -127,7 +127,7 @@ To configure Azure AD single sign-on with CS Stars, perform the following steps:
 
 ### Configure CS Stars Single Sign-On
 
-To configure single sign-on on **CS Stars** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [CS Stars support team](http://www.riskonnectclearsight.com/support/). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **CS Stars** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [CS Stars support team](https://riskonnect.com/support/). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create an Azure AD test user 
 
@@ -182,7 +182,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 ### Create CS Stars test user
 
-In this section, you create a user called Britta Simon in CS Stars. Work with [CS Stars support team](http://www.riskonnectclearsight.com/support/) to add the users in the CS Stars platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called Britta Simon in CS Stars. Work with [CS Stars support team](https://riskonnect.com/support/) to add the users in the CS Stars platform. Users must be created and activated before you use single sign-on.
 
 ### Test single sign-on 
 
diff --git a/articles/active-directory/saas-apps/hr2day-tutorial.md b/articles/active-directory/saas-apps/hr2day-tutorial.md
@@ -161,7 +161,7 @@ To configure Azure AD single sign-on with HR2day by Merces, perform the followin
 To configure single sign-on on **HR2day by Merces** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [HR2day by Merces support team](mailto:servicedesk@merces.nl). They set this setting to have the SAML SSO connection set properly on both sides.
 
 > [!NOTE]
-> Mention to the Merces team that this integration needs the Entity ID to be set with the pattern **https://hr2day.force.com/INSTANCENAME**.
+> Mention to the Merces team that this integration needs the Entity ID to be set with the pattern **https:\//hr2day.force.com/INSTANCENAME**.
 
 ### Create an Azure AD test user
 
diff --git a/articles/active-directory/saas-apps/jobscience-tutorial.md b/articles/active-directory/saas-apps/jobscience-tutorial.md
@@ -114,7 +114,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
     `http://<company name>.my.salesforce.com`
     
     > [!NOTE] 
-    > This value is not real. Update this value with the actual Sign-On URL. Get this value by [Jobscience Client support team](https://www.jobscience.com/support) or from the SSO profile you will create which is explained later in the tutorial. 
+    > This value is not real. Update this value with the actual Sign-On URL. Get this value by [Jobscience Client support team](http://www.jobscience.com/support) or from the SSO profile you will create which is explained later in the tutorial. 
  
 1. On the **SAML Signing Certificate** section, click **Certificate (Base64)** and then save the certificate file on your computer.
 
diff --git a/articles/active-directory/saas-apps/linkedinsalesnavigator-provisioning-tutorial.md b/articles/active-directory/saas-apps/linkedinsalesnavigator-provisioning-tutorial.md
@@ -96,7 +96,7 @@ The first step is to retrieve your LinkedIn access token. If you are an Enterpri
 
 11. Fill in the following fields under **Admin Credentials** :
 
-    * In the **Tenant URL** field, enter https://api.linkedin.com.
+    * In the **Tenant URL** field, enter https://developer.linkedin.com.
 
     * In the **Secret Token** field, enter the access token you generated in step 1 and click **Test Connection** .
 
diff --git a/articles/active-directory/saas-apps/mitel-connect-tutorial.md b/articles/active-directory/saas-apps/mitel-connect-tutorial.md
@@ -198,7 +198,7 @@ In this section, you'll enable Britta Simon to use Azure single sign-on by grant
 
 In this section, you create a user named Britta Simon on your MiCloud Connect account. Users must be created and activated before using single sign-on.
 
-For details about adding users in the Mitel Account portal, see the [Adding a User](https://docs.shoretel.com/connectcloud/Account/Users/AddUser) article in the Mitel Knowledge Base.
+For details about adding users in the Mitel Account portal, see the [Adding a User](https://oneview.mitel.com/s/article/Adding-a-User-092815) article in the Mitel Knowledge Base.
 
 Create a user on your MiCloud Connect account with the following details:
 
diff --git a/articles/active-directory/saas-apps/oneteam-tutorial.md b/articles/active-directory/saas-apps/oneteam-tutorial.md
@@ -117,7 +117,7 @@ To configure Azure AD single sign-on with Oneteam, perform the following steps:
     `https://<team name>.one-team.io/`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Oneteam Client support team](https://support.one-team.com/hc/requests/new) 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 Identifier, Reply URL and Sign-on URL. Contact Oneteam Client support team to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 6. 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.
 
@@ -135,7 +135,7 @@ To configure Azure AD single sign-on with Oneteam, perform the following steps:
 
 ### Configure Oneteam Single Sign-On
 
-To configure single sign-on on **Oneteam** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Oneteam support team](https://support.one-team.com/hc/requests/new). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Oneteam** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to Oneteam support team. They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create an Azure AD test user 
 
@@ -193,7 +193,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 In this section, a user called Britta Simon is created in Oneteam. Oneteam 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 Oneteam, a new one is created after authentication.
 
 >[!NOTE]
->If you need to create an user manually, you can raise the support ticket with [Oneteam support team](https://support.one-team.com/hc/requests/new).
+>If you need to create an user manually, you can raise the support ticket with Oneteam support team.
 
 ### Test single sign-on 
 
diff --git a/articles/active-directory/saas-apps/rackspacesso-tutorial.md b/articles/active-directory/saas-apps/rackspacesso-tutorial.md
@@ -184,7 +184,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 ### Set up Attribute Mapping in the Rackspace control panel
 
-Rackspace uses an **Attribute Mapping Policy** to assign Rackspace roles and groups to your single sign-on users. The **Attribute Mapping Policy** translates Azure AD SAML claims into the user configuration fields Rackspace requires. More documentation can be found in the Rackspace [Attribute Mapping Basics documentation](https://developer.rackspace.com/docs/rackspace-federation/attribmapping-basics/). Some considerations:
+Rackspace uses an **Attribute Mapping Policy** to assign Rackspace roles and groups to your single sign-on users. The **Attribute Mapping Policy** translates Azure AD SAML claims into the user configuration fields Rackspace requires. More documentation can be found in the Rackspace [Attribute Mapping Basics documentation](https://developer.rackspace.com/docs/rackspace-federation/appendix/map/). Some considerations:
 
 * If you want to assign varying levels of Rackspace access using Azure AD groups, you will need to enable the Groups claim in the Azure **Rackspace SSO** Single Sign-on settings. The **Attribute Mapping Policy** will then be used to match those groups to desired Rackspace roles and groups:
 
@@ -223,7 +223,7 @@ mapping:
 > [!TIP]
 > Ensure that you use a text editor that validates YAML syntax when editing your policy file.
 
-See the Rackspace [Attribute Mapping Basics documentation](https://developer.rackspace.com/docs/rackspace-federation/attribmapping-basics/) for more examples.
+See the Rackspace [Attribute Mapping Basics documentation](https://developer.rackspace.com/docs/rackspace-federation/appendix/map/) for more examples.
 
 ### Test single sign-on
 
diff --git a/articles/active-directory/saas-apps/splunkenterpriseandsplunkcloud-tutorial.md b/articles/active-directory/saas-apps/splunkenterpriseandsplunkcloud-tutorial.md
@@ -112,15 +112,15 @@ To configure Azure AD single sign-on with Splunk Enterprise and Splunk Cloud, pe
     `https://<splunkserver>/saml/acs`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Sign-On URL, Identifier and Reply URL. Contact [Splunk Enterprise and Splunk Cloud Client support team](https://www.splunk.com/about-us/contact.html#tabs/customer-support) 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, Identifier and Reply URL. Contact [Splunk Enterprise and Splunk Cloud Client support team](https://www.splunk.com/en_us/about-splunk/contact-us.html) to get these values. 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.
 
 	![The Certificate download link](common/metadataxml.png)
 
 ### Configure Splunk Enterprise and Splunk Cloud Single Sign-On
 
-To configure single sign-on on **Splunk Enterprise and Splunk Cloud** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Splunk Enterprise and Splunk Cloud support team](https://www.splunk.com/about-us/contact.html#tabs/customer-support). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Splunk Enterprise and Splunk Cloud** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Splunk Enterprise and Splunk Cloud support team](https://www.splunk.com/en_us/about-splunk/contact-us.html). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create an Azure AD test user 
 
@@ -175,7 +175,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 ### Create Splunk Enterprise and Splunk Cloud test user
 
-In this section, you create a user called Britta Simon in Splunk Enterprise and Splunk Cloud. Work with [Splunk Enterprise and Splunk Cloud support team](https://www.splunk.com/about-us/contact.html#tabs/customer-support) to add the users in the Splunk Enterprise and Splunk Cloud platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called Britta Simon in Splunk Enterprise and Splunk Cloud. Work with [Splunk Enterprise and Splunk Cloud support team](https://www.splunk.com/en_us/about-splunk/contact-us.html) to add the users in the Splunk Enterprise and Splunk Cloud platform. Users must be created and activated before you use single sign-on.
 
 ### Test single sign-on 
 
diff --git a/articles/active-directory/saas-apps/spring-cm-tutorial.md b/articles/active-directory/saas-apps/spring-cm-tutorial.md
@@ -199,7 +199,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 To enable Azure Active Directory users to sign in to SpringCM, they must be provisioned into SpringCM. In the case of SpringCM, provisioning is a manual task.
 
 > [!NOTE]
-> For more information, see [Create and Edit a SpringCM User](https://knowledge.springcm.com/create-and-edit-a-springcm-user). 
+> For more information, see [Create and Edit a SpringCM User](http://community.springcm.com/s/article/Create-and-Edit-a-SpringCM-User-1619481053). 
 
 **To provision a user account to SpringCM, perform the following steps:**
 
diff --git a/articles/active-directory/saas-apps/workpath-tutorial.md b/articles/active-directory/saas-apps/workpath-tutorial.md
@@ -96,7 +96,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     `https://<subdomain>.workpath.com/`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Workpath Client support team](https://help.workpath.com/) 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 Identifier, Reply URL and Sign-on URL. Contact [Workpath Client support team](https://www.workpath.com/en/company/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 1. Workpath application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
 
@@ -149,7 +149,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure Workpath SSO
 
-To configure single sign-on on **Workpath** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Workpath support team](https://help.workpath.com/). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Workpath** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Workpath support team](https://www.workpath.com/en/company/). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create Workpath test user
 
diff --git a/articles/active-directory/saas-apps/workstars-tutorial.md b/articles/active-directory/saas-apps/workstars-tutorial.md
@@ -108,7 +108,7 @@ To configure Azure AD single sign-on with Workstars, perform the following steps
     `https://<subdomain>.workstars.com/saml/login_check`
 
 	> [!NOTE]
-	> The value is not real. Update the value with the actual Reply URL. Contact [Workstars Client support team](https://support.workstars.com/) 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 Reply URL. Contact [Workstars Client support team](http://support.workstars.com/) 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 **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
 
@@ -208,7 +208,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 ### Create Workstars test user
 
-In this section, you create a user called Britta Simon in Workstars. Work with [Workstars support team](https://support.workstars.com) to add the users in the Workstars platform.
+In this section, you create a user called Britta Simon in Workstars. Work with [Workstars support team](http://support.workstars.com) to add the users in the Workstars platform.
 
 ### Test single sign-on 
 
diff --git a/articles/active-directory/user-help/my-apps-portal-end-user-access.md b/articles/active-directory/user-help/my-apps-portal-end-user-access.md
@@ -105,7 +105,7 @@ If you have permission to access and use your organization's cloud-based apps, y
 
 View and use your organization's apps from an Intune Managed Browser on your iOS and Android devices.
 
-1. On your mobile device, download and install the Intune Managed Browser app from the [Apple App Store](https://itunes.apple.com/us/app/microsoft-intune-managed-browser/id943264951?mt=8) and the [Google Play Store](https://play.google.com/store/apps/details?id=com.microsoft.intune.mam.managedbrowser).
+1. On your mobile device, download and install the Intune Managed Browser app from the Apple App Store and the Google Play Store.
 
 2. Open the Intune Managed Browser app, go to https://myapps.microsoft.com, or use the link provided by your organization if they direct you to a customized page, such as https://myapps.microsoft.com/contoso.com.
 
diff --git a/articles/app-service-mobile/app-service-mobile-cordova-get-started-users.md b/articles/app-service-mobile/app-service-mobile-cordova-get-started-users.md
@@ -43,7 +43,7 @@ Next, update the app to authenticate users before requesting resources from the
    | Facebook | facebook | https://www.facebook.com |
    | Google | google | https://accounts.google.com |
    | Microsoft | microsoftaccount | https://login.live.com |
-   | Twitter | twitter | https://api.twitter.com |
+   | Twitter | twitter | https://developer.twitter.com/en |
 
     An example Content-Security-Policy (implemented for Azure Active Directory) is as follows:
 
diff --git a/articles/app-service/faq-configuration-and-management.md b/articles/app-service/faq-configuration-and-management.md
@@ -183,7 +183,7 @@ You have two options for capturing an F12 trace:
 3. Right-click in the message area of the pane, and then select **Copy all**.
 4. Paste the copied text in a file, and then save the file.
 
-To view an HAR file, you can use the [HAR viewer](https://www.softwareishard.com/har/viewer/).
+To view an HAR file, you can use the [HAR viewer](http://www.softwareishard.com/har/viewer/).
 
 ## Why do I get an error when I try to connect an App Service web app to a virtual network that is connected to ExpressRoute?
 
diff --git a/articles/app-service/webjobs-dotnet-deploy-vs.md b/articles/app-service/webjobs-dotnet-deploy-vs.md
@@ -171,7 +171,7 @@ and stores scheduling information in a *webjob-publish-settings.json* file in th
           "runMode": "Continuous"
         }
 
-You can edit this file directly, and Visual Studio provides IntelliSense. The file schema is stored at [https://schemastore.org](https://schemastore.org/schemas/json/webjob-publish-settings.json) and can be viewed there.  
+You can edit this file directly, and Visual Studio provides IntelliSense. The file schema is stored at [https://schemastore.org](http://schemastore.org/schemas/json/webjob-publish-settings.json) and can be viewed there.  
 
 ### <a id="webjobslist"></a>webjobs-list.json
 When you link a WebJobs-enabled project to a web project, Visual Studio stores the name of the WebJobs project in a *webjobs-list.json* file in the web project's *Properties* folder. The list might contain multiple WebJobs projects, as shown in the following example:
@@ -188,7 +188,7 @@ When you link a WebJobs-enabled project to a web project, Visual Studio stores t
           ]
         }
 
-You can edit this file directly, and Visual Studio provides IntelliSense. The file schema is stored at [https://schemastore.org](https://schemastore.org/schemas/json/webjobs-list.json) and can be viewed there.
+You can edit this file directly, and Visual Studio provides IntelliSense. The file schema is stored at [https://schemastore.org](http://schemastore.org/schemas/json/webjobs-list.json) and can be viewed there.
 
 ### <a id="deploy"></a>Deploy a WebJobs project
 A WebJobs project that you have linked to a web project deploys automatically with the web project. For information about web project deployment, see **How-to guides** > **Deploy app** in the left navigation.
diff --git a/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md b/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
diff --git a/articles/azure-functions/functions-api-definition.md b/articles/azure-functions/functions-api-definition.md
diff --git a/articles/azure-government/documentation-government-services-aiandcognitiveservices.md b/articles/azure-government/documentation-government-services-aiandcognitiveservices.md
