Merge pull request #102591 from john-par/1668809-clean-up-broken-azure-docs-pr-links-01-27

GitHubber17 · web-flow · commit 9c117ea15f1a · 2020-01-28T19:17:01.000-08:00
1668809 clean up broken azure docs pr links 01-27
diff --git a/articles/active-directory/develop/scenario-desktop-acquire-token.md b/articles/active-directory/develop/scenario-desktop-acquire-token.md
@@ -410,7 +410,7 @@ To sign in a domain user on a domain or Azure AD joined machine, use Integrated
 
 - The authority passed in `PublicClientApplicationBuilder` needs to be:
   - Tenanted of the form `https://login.microsoftonline.com/{tenant}/`, where `tenant` is either the GUID that represents the tenant ID or a domain associated with the tenant.
-  - For any [work and school accounts](`https://login.microsoftonline.com/organizations/`).
+  - For any work and school accounts: `https://login.microsoftonline.com/organizations/`.
   - Microsoft personal accounts aren't supported. You can't use /common or /consumers tenants.
 
 - Because Integrated Windows Authentication is a silent flow:
diff --git a/articles/active-directory/saas-apps/gigya-tutorial.md b/articles/active-directory/saas-apps/gigya-tutorial.md
@@ -108,7 +108,7 @@ To configure Azure AD single sign-on with Gigya, perform the following steps:
     `https://fidm.gigya.com/saml/v2.0/<companyname>`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [Gigya Client support team](https://www.gigya.com/support-policy/) 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 [Gigya Client support team](https://developers.gigya.com/display/GD/Opening+A+Support+Incident) 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 **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
 
diff --git a/articles/azure-functions/functions-create-first-function-python.md b/articles/azure-functions/functions-create-first-function-python.md
@@ -202,7 +202,7 @@ To deploy your function code to Azure, you need to create three resources:
 
 You use Azure CLI commands to create these items. Each command provides JSON output upon completion.
 
-1. If you haven't done so already, sign in to Azure with the [az login](/cli/azure/group#az-login) command:
+1. If you haven't done so already, sign in to Azure with the [az login](/cli/azure/reference-index#az-login) command:
 
     ```azurecli
     az login
diff --git a/articles/azure-functions/functions-create-function-linux-custom-image.md b/articles/azure-functions/functions-create-function-linux-custom-image.md
@@ -285,7 +285,7 @@ To deploy your function code to Azure, you need to create three resources:
 
 You use Azure CLI commands to create these items. Each command provides JSON output upon completion.
 
-1. Sign in to Azure with the [az login](/cli/azure/group#az-login) command:
+1. Sign in to Azure with the [az login](/cli/azure/reference-index#az-login) command:
 
     ```azurecli
     az login
diff --git a/articles/azure-monitor/app/opencensus-python.md b/articles/azure-monitor/app/opencensus-python.md
@@ -133,7 +133,7 @@ Here are the exporters that OpenCensus provides mapped to the types of telemetry
 
 4. Now when you run the Python script, you should still be prompted to enter values, but only the value is being printed in the shell. The created `SpanData` will be sent to Azure Monitor. You can find the emitted span data under `dependencies`.
 
-5. For information on sampling in OpenCensus, take a look at [sampling in OpenCensus](https://docs.microsoft.com/azure/azure-monitor/app/sampling#configuring-fixed-rate-sampling-in-opencensus-python).
+5. For information on sampling in OpenCensus, take a look at [sampling in OpenCensus](sampling.md#configuring-fixed-rate-sampling-for-opencensus-python-applications).
 
 6. For details on telemetry correlation in your trace data, take a look at OpenCensus [telemetry correlation](https://docs.microsoft.com/azure/azure-monitor/app/correlation#telemetry-correlation-in-opencensus-python).
 
diff --git a/articles/azure-monitor/app/pricing.md b/articles/azure-monitor/app/pricing.md
@@ -34,9 +34,9 @@ There are two approaches to address this: use of default monitoring and adaptive
 
 ### Data collection when using sampling
 
-With the ASP.NET SDK's [adaptive sampling](https://docs.microsoft.com/azure/azure-monitor/app/sampling#adaptive-sampling-in-your-aspnetaspnet-core-web-applications), the data volume is adjusted automatically to keep within a specified maximum rate of traffic for default Application Insights monitoring. If the application produces a low amount of telemetry, such as when debugging or due to low usage, items won't be dropped by the sampling processor as long as volume is below the configured events per second level. For a high volume application, with the default threshold of five events per second, adaptive sampling will limit the number of daily events to 432,000. Using a typical average event size of 1 KB, this corresponds to 13.4 GB of telemetry per 31-day month per node hosting your application (since the sampling is done local to each node.) 
+With the ASP.NET SDK's [adaptive sampling](sampling.md#adaptive-sampling), the data volume is adjusted automatically to keep within a specified maximum rate of traffic for default Application Insights monitoring. If the application produces a low amount of telemetry, such as when debugging or due to low usage, items won't be dropped by the sampling processor as long as volume is below the configured events per second level. For a high volume application, with the default threshold of five events per second, adaptive sampling will limit the number of daily events to 432,000. Using a typical average event size of 1 KB, this corresponds to 13.4 GB of telemetry per 31-day month per node hosting your application (since the sampling is done local to each node.) 
 
-For SDKs that don't support adaptive sampling, you can employ [ingestion sampling](https://docs.microsoft.com/azure/azure-monitor/app/sampling#ingestion-sampling), which samples when the data is received by Application Insights based on a percentage of data to retain, or [fixed-rate sampling for ASP.NET, ASP.NET Core, and Java websites](https://docs.microsoft.com/azure/azure-monitor/app/sampling#fixed-rate-sampling-for-aspnet-aspnet-core-java-websites-and-python-applications) to reduce the traffic sent from your web server and web browsers
+For SDKs that don't support adaptive sampling, you can employ [ingestion sampling](https://docs.microsoft.com/azure/azure-monitor/app/sampling#ingestion-sampling), which samples when the data is received by Application Insights based on a percentage of data to retain, or [fixed-rate sampling for ASP.NET, ASP.NET Core, and Java websites](sampling.md#fixed-rate-sampling) to reduce the traffic sent from your web server and web browsers
 
 ### Learn from what similar customers collect
 
diff --git a/articles/backup/backup-afs-cli.md b/articles/backup/backup-afs-cli.md
@@ -99,7 +99,7 @@ If you want to trigger an on-demand backup for your file share instead of waitin
 
 You need to define the following parameters to trigger an on-demand backup:
 
-* **--container-name** is the name of the storage account hosting the file share. To retrieve the **name** or **friendly name** of your container, use the [az backup container list](https://docs.microsoft.com/azure/backup/container?view=azure-cli-latest#az-backup-container-list) command.
+* **--container-name** is the name of the storage account hosting the file share. To retrieve the **name** or **friendly name** of your container, use the [az backup container list](/cli/azure/backup/container?view=azure-cli-latest#az-backup-container-list) command.
 * **--item-name** is the name of the file share for which you want to trigger an on-demand backup. To retrieve the **name** or **friendly name** of your backed-up item, use the [az backup item list](https://docs.microsoft.com/cli/azure/backup/item?view=azure-cli-latest#az-backup-item-list) command.
 * **--retain-until** specifies the date until when you want to retain the recovery point. The value should be set in UTC time format (dd-mm-yyyy).
 
diff --git a/articles/cognitive-services/LUIS/luis-tutorial-review-endpoint-utterances.md b/articles/cognitive-services/LUIS/luis-tutorial-review-endpoint-utterances.md
@@ -43,7 +43,7 @@ Use the following steps to import an app.
 
 1.  Download and save [app JSON file](https://github.com/Azure-Samples/cognitive-services-language-understanding/blob/master/documentation-samples/tutorials/custom-domain-sentiment-HumanResources.json?raw=true).
 
-1. On the [preview LUIS portal](https://preview.luis-ai), import the .json file into a new app.
+1. On the [preview LUIS portal](https://preview.luis.ai), import the .json file into a new app.
 
 1. From the **Manage** section, on the **Versions** tab, clone the version, and name it `review`.
 
diff --git a/articles/cognitive-services/personalizer/what-is-personalizer.md b/articles/cognitive-services/personalizer/what-is-personalizer.md
@@ -95,6 +95,6 @@ Since Personalizer uses collective information in near real-time to return the s
 * [What is Reinforcement Learning?](concepts-reinforcement-learning.md)
 * [Learn about features and actions for the Rank request](concepts-features.md)
 * [Learn about determining the score for the Reward request](concept-rewards.md)
-* [Quickstarts]()
-* [Tutorial]()
+* [Quickstarts](sdk-learning-loop.md)
+* [Tutorial](tutorial-use-azure-notebook-generate-loop-data.md)
 * [Use the interactive demo](https://personalizationdemo.azurewebsites.net/)
diff --git a/articles/migrate/how-to-discover-applications.md b/articles/migrate/how-to-discover-applications.md
@@ -23,7 +23,7 @@ App discovery using Azure Migrate: Server Assessment is agentless. Nothing needs
 2. Make sure you've [added](how-to-assess.md) the Azure Migrate: Server Assessment tool to a project.
 4. Check the [VMware requirements](migrate-support-matrix-vmware.md#vmware-requirements) for discovering and assessing VMware VMs with the Azure Migrate appliance.
 5. Check the [requirements](migrate-appliance.md) for deploying the Azure Migrate appliance.
-6. [Verify support and requirements](/migrate-support-matrix-vmware.md#application-discovery) for application discovery.
+6. [Verify support and requirements](migrate-support-matrix-vmware.md#application-discovery) for application discovery.
 
 ## Prepare for app discovery
 
diff --git a/articles/site-recovery/vmware-azure-mobility-install-configuration-mgr.md b/articles/site-recovery/vmware-azure-mobility-install-configuration-mgr.md
@@ -14,7 +14,7 @@ This article describes how to automate installation and updates for the Mobility
 When you deploy Site Recovery for disaster recovery of on-premises VMware VMs and physical servers to Azure, you install the Mobility service agent on each machine you want to replicate. The Mobility service captures data writes on the machine, and forwards them to the Site Recovery process server for replication. You can deploy the Mobility Service in a couple of ways:
 
 - **Push installation**: Let Site Recovery install  the Mobility service agent when you enable replication for a machine in the Azure portal.
-- **Manual installation**: Install the Mobility service manually on each machine. [Learn more](/vmware-physical-mobility-service-overview.md) about push and manual installation.
+- **Manual installation**: Install the Mobility service manually on each machine. [Learn more](vmware-physical-mobility-service-overview.md) about push and manual installation.
 - **Automated deployment**: Automate installation with software deployment tools such as Microsoft Endpoint Configuration Manager, or third-party tools such as Intigua JetPatch.
 
 Automated installation and updating provides a solution if:
diff --git a/articles/virtual-machines/workloads/sap/sap-hana-availability-one-region.md b/articles/virtual-machines/workloads/sap/sap-hana-availability-one-region.md
@@ -106,7 +106,7 @@ In this scenario, data that's replicated to the HANA instance in the second VM i
 
 ### SAP HANA system replication with automatic failover
 
-In the standard and most common availability configuration within one Azure region, two Azure VMs running SLES Linux have a failover cluster defined. The SLES Linux cluster is based on the [Pacemaker](http://www.linux-ha.org/wiki/Pacemaker) framework, in conjunction with a [STONITH](http://linux-ha.org/wiki/STONITH) device. 
+In the standard and most common availability configuration within one Azure region, two Azure VMs running SLES Linux have a failover cluster defined. The SLES Linux cluster is based on the [Pacemaker](http://www.linux-ha.org/wiki/Pacemaker) framework, in conjunction with a [STONITH](http://www.linux-ha.org/wiki/STONITH) device. 
 
 From an SAP HANA perspective, the replication mode that's used is synced and an automatic failover is configured. In the second VM, the SAP HANA instance acts as a hot standby node. The standby node receives a synchronous stream of change records from the primary SAP HANA instance. As transactions are committed by the application at the HANA primary node, the primary HANA node waits to confirm the commit to the application until the secondary SAP HANA node confirms that it received the commit record. SAP HANA offers two synchronous replication modes. For details and for a description of differences between these two synchronous replication modes, see the SAP article [Replication modes for SAP HANA system replication](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/c039a1a5b8824ecfa754b55e0caffc01.html).
 
diff --git a/articles/virtual-network/virtual-network-vnet-plan-design-arm.md b/articles/virtual-network/virtual-network-vnet-plan-design-arm.md
@@ -35,7 +35,7 @@ All Azure resources are created in an Azure region and subscription. A resource
 
 ## Subscriptions
 
-You can deploy as many virtual networks as required within each subscription, up to the [limit](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#networking-limits). Some organizations have different subscriptions for different departments, for example. For more information and considerations around subscriptions, see [Subscription governance](/azure/architecture/cloud-adoption-guide/subscription-governance#define-your-hierarchy).
+You can deploy as many virtual networks as required within each subscription, up to the [limit](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#networking-limits). Some organizations have different subscriptions for different departments, for example. For more information and considerations around subscriptions, see [Subscription governance](/azure/cloud-adoption-framework/reference/migration-with-enterprise-scaffold#define-your-hierarchy).
 
 ## Segmentation
 
