Merge pull request #108197 from craigcaseyMSFT/vcraic0318a

tfosmark · web-flow · commit 02edcb83fde6 · 2020-03-18T13:52:20.000-07:00
fix warnings in the AM build report
diff --git a/articles/active-directory/saas-apps/toc.yml b/articles/active-directory/saas-apps/toc.yml
@@ -1666,7 +1666,7 @@
       - name: Airstack
         href: airstack-provisioning-tutorial.md
       - name: Amazon Web Services (AWS) - Role Provisioning
-        href: amazon-web-service-tutorial.md#configure-azure-ad-single-sign-on
+        href: amazon-web-service-tutorial.md#configure-azure-ad-sso
       - name: Asana
         href: asana-provisioning-tutorial.md
       - name: Atlassian Cloud
diff --git a/articles/app-service/containers/toc.yml b/articles/app-service/containers/toc.yml
@@ -176,7 +176,7 @@
     - name: Clone an app
       href: ../app-service-web-app-cloning.md?toc=%2fazure%2fapp-service%2fcontainers%2ftoc.json
     - name: Move resources
-      href: ../../azure-resource-manager/management/move-resource-group-and-subscription.md?toc=%2fazure%2fapp-service%2fcontainers%2ftoc.json#app-service-limitations
+      href: ../../azure-resource-manager/management/move-resource-group-and-subscription.md?toc=%2fazure%2fapp-service%2fcontainers%2ftoc.json#checklist-before-moving-resources
 - name: Reference
   items:
   - name: Azure CLI
diff --git a/articles/app-service/toc.yml b/articles/app-service/toc.yml
@@ -214,7 +214,7 @@
     - name: Move between regions
       href: manage-move-across-regions.md
     - name: Move subscriptions
-      href: ../azure-resource-manager/management/move-resource-group-and-subscription.md?toc=%2fazure%2fapp-service%2ftoc.json#app-service-limitations
+      href: ../azure-resource-manager/management/move-resource-group-and-subscription.md?toc=%2fazure%2fapp-service%2ftoc.json#checklist-before-moving-resources
   - name: Run background tasks
     items:
     - name: Create WebJobs
diff --git a/articles/availability-zones/TOC.yml b/articles/availability-zones/TOC.yml
@@ -23,7 +23,7 @@
     - name: Managed disks
       items:
       - name: Add a managed disk in Availability Zones with CLI
-        href: ../virtual-machines/linux/add-disk.md#use-managed-disks
+        href: ../virtual-machines/linux/add-disk.md#attach-a-new-disk-to-a-vm
       - name: Add a managed disk in Availability Zones with PowerShell
         href: ../virtual-machines/windows/attach-disk-ps.md#add-an-empty-data-disk-to-a-virtual-machine
     - name: Virtual machine scale sets
@@ -68,11 +68,11 @@
     - name: Event Hubs
       items:
       - name: Event Hubs geo-disaster recovery
-        href: ../event-hubs/event-hubs-geo-dr.md#availability-zones-preview
+        href: ../event-hubs/event-hubs-geo-dr.md#availability-zones
     - name: Service Bus
       items:
       - name: Service Bus geo-disaster recovery
-        href: ../service-bus-messaging/service-bus-geo-dr.md#availability-zones-preview
+        href: ../service-bus-messaging/service-bus-geo-dr.md#availability-zones
     - name: VPN Gateway
       items:
       - name: Create a zone-redundant virtual network gateway
diff --git a/articles/azure-cache-for-redis/TOC.yml b/articles/azure-cache-for-redis/TOC.yml
@@ -48,7 +48,7 @@
   - name: Plan
     items:
     - name: Choose a cache tier
-      href: cache-faq.md#what-redis-cache-offering-and-size-should-i-use
+      href: cache-faq.md#what-azure-cache-for-redis-offering-and-size-should-i-use
     - name: Distribute your cache with clustering
       href: cache-how-to-premium-clustering.md
     - name: Persist your cache with Redis data persistence
diff --git a/articles/azure-monitor/toc.yml b/articles/azure-monitor/toc.yml
@@ -641,7 +641,7 @@
       - name: General Availability FAQ
         href: insights/vminsights-ga-release-faq.md  
       - name: FAQ
-        href: faq.md#azure-monitor-for-vms-preview
+        href: faq.md#azure-monitor-for-vms
       - name: Enable monitoring
         items:
         - name: Enable monitoring overview
diff --git a/articles/azure-signalr/signalr-tutorial-diagnostic-logs.md b/articles/azure-signalr/signalr-tutorial-diagnostic-logs.md
@@ -1,7 +1,7 @@
 ---
 title: Diagnostic Logs for Azure SignalR Service
 description: Learn how to set up diagnostic logs for Azure SignalR Service and how to utilize it to self-troubleshoot.
-author: wanl
+author: wanlwanl
 ms.service: signalr
 ms.topic: conceptual
 ms.date: 12/17/2019
@@ -26,22 +26,22 @@ You can view diagnostic logs for Azure SignalR Service. These logs provide riche
 
 Diagnostic logs are disabled by default. To enable diagnostic logs, follow these steps:
 
-1.	In the [Azure portal](https://portal.azure.com), under **Monitoring**, click **Diagnostic settings**.
+1.    In the [Azure portal](https://portal.azure.com), under **Monitoring**, click **Diagnostic settings**.
 
     ![Pane navigation to diagnostic settings](./media/signalr-tutorial-diagnostic-logs/diagnostic-settings-menu-item.png)
 
-1.	Then click **Add diagnostic setting**.
+1.    Then click **Add diagnostic setting**.
 
-	![Add diagnostic logs](./media/signalr-tutorial-diagnostic-logs/add-diagnostic-setting.png)
+    ![Add diagnostic logs](./media/signalr-tutorial-diagnostic-logs/add-diagnostic-setting.png)
 
-1.	Set the archive target that you want. Currently, we support **Archive to a storage account** and **Send to Log Analytics**.
+1.    Set the archive target that you want. Currently, we support **Archive to a storage account** and **Send to Log Analytics**.
 
 1. Select the logs you want to archive.
 
-	![Diagnostics settings pane](./media/signalr-tutorial-diagnostic-logs/diagnostics-settings-pane.png)
+    ![Diagnostics settings pane](./media/signalr-tutorial-diagnostic-logs/diagnostics-settings-pane.png)
 
 
-1.	Save the new diagnostics settings.
+1.    Save the new diagnostics settings.
 
 New settings take effect in about 10 minutes. After that, logs appear in the configured archival target, in the **Diagnostics logs** pane.
 
diff --git a/articles/batch/batch-ci-cd.md b/articles/batch/batch-ci-cd.md
@@ -1,7 +1,7 @@
 ---
 title: Use Azure Pipelines to build & deploy HPC solutions - Azure Batch
 description: Learn how to deploy a build/release pipeline for an HPC application running on Azure Batch.
-author: christianreddington
+author: chrisreddington
 ms.author: chredd
 ms.date: 03/28/2019
 ms.topic: conceptual
diff --git a/articles/iot-central/core/howto-create-analytics.md b/articles/iot-central/core/howto-create-analytics.md
@@ -1,7 +1,7 @@
 ---
 title: Analyze device data in your Azure IoT Central application | Microsoft Docs
 description: Analyze device data in your Azure IoT Central application.
-author: ankitgup
+author: ankitscribbles
 ms.author: ankitgup
 ms.date: 11/27/2019
 ms.topic: conceptual
diff --git a/articles/machine-learning/how-to-version-track-datasets.md b/articles/machine-learning/how-to-version-track-datasets.md
@@ -7,7 +7,7 @@ ms.service: machine-learning
 ms.subservice: core
 ms.topic: conceptual
 ms.author: sihhu
-author: sihhu
+author: MayMSFT
 ms.reviewer: nibaccam
 ms.date: 03/09/2020
 ms.custom: 
diff --git a/articles/stream-analytics/stream-analytics-javascript-user-defined-aggregates.md b/articles/stream-analytics/stream-analytics-javascript-user-defined-aggregates.md
@@ -1,7 +1,7 @@
 ---
 title: JavaScript user-defined aggregates in Azure Stream Analytics
 description: This article describes how to perform advanced query mechanics with JavaScript user-defined aggregates in Azure Stream Analytics.
-author: rodrigoamicrosoft
+author: rodrigoaatmicrosoft
 ms.author: rodrigoa
 ms.reviewer: mamccrea
 ms.service: stream-analytics
@@ -113,7 +113,7 @@ For JavaScript UDA data types, refer to section **Stream Analytics and JavaScrip
 
 Below we walk through the process of creating a UDA from Portal. The example we use here is computing time weighted averages.
 
-Now let’s create a JavaScript UDA under an existing ASA job by following steps.
+Now let's create a JavaScript UDA under an existing ASA job by following steps.
 
 1. Log on to Azure portal and locate your existing Stream Analytics job.
 1. Then click on functions  link under **JOB TOPOLOGY**.
diff --git a/articles/stream-analytics/stream-analytics-javascript-user-defined-functions.md b/articles/stream-analytics/stream-analytics-javascript-user-defined-functions.md
@@ -1,7 +1,7 @@
 ---
 title: Azure Stream Analytics JavaScript user-defined functions
 description: In this tutorial, you perform advanced query mechanics with JavaScript user-defined functions
-author: rodrigoamicrosoft
+author: rodrigoaatmicrosoft
 ms.author: rodrigoa
 ms.service: stream-analytics
 ms.topic: tutorial
@@ -23,7 +23,7 @@ In this tutorial, you learn how to:
 > * Add the function to the portal
 > * Define a query that runs the function
 
-If you don’t have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
 ## JavaScript user-defined functions
 JavaScript user-defined functions support stateless, compute-only scalar functions that do not require external connectivity. The return value of a function can only be a scalar (single) value. After you add a JavaScript user-defined function to a job, you can use the function anywhere in the query, like a built-in scalar function.
@@ -47,15 +47,15 @@ To create a simple JavaScript user-defined function under an existing Stream Ana
 > [!NOTE]
 > These steps work on the Stream Analytics jobs configured to run in the cloud. If your Stream Analytics job is configured to run on Azure IoT Edge, instead use Visual Studio and [write the user-defined function using C#](stream-analytics-edge-csharp-udf.md).
 
-1.	In the Azure portal, find your Stream Analytics job.
+1.    In the Azure portal, find your Stream Analytics job.
 
 2. Under the **Job topology** heading, select **Functions**. An empty list of functions appears.
 
-3.	To create a new user-defined function, select **+ Add**.
+3.    To create a new user-defined function, select **+ Add**.
 
-4.	On the **New Function** blade, for **Function Type**, select **JavaScript**. A default function template appears in the editor.
+4.    On the **New Function** blade, for **Function Type**, select **JavaScript**. A default function template appears in the editor.
 
-5.	For the **UDF alias**, enter **hex2Int**, and change the function implementation as follows:
+5.    For the **UDF alias**, enter **hex2Int**, and change the function implementation as follows:
 
     ```javascript
     // Convert Hex value to integer.
@@ -64,16 +64,16 @@ To create a simple JavaScript user-defined function under an existing Stream Ana
     }
     ```
 
-6.	Select **Save**. Your function appears in the list of functions.
-7.	Select the new **hex2Int** function, and check the function definition. All functions have a **UDF** prefix added to the function alias. You need to *include the prefix* when you call the function in your Stream Analytics query. In this case, you call **UDF.hex2Int**.
+6.    Select **Save**. Your function appears in the list of functions.
+7.    Select the new **hex2Int** function, and check the function definition. All functions have a **UDF** prefix added to the function alias. You need to *include the prefix* when you call the function in your Stream Analytics query. In this case, you call **UDF.hex2Int**.
 
 ## Testing JavaScript UDFs 
 You can test and debug your JavaScript UDF logic in any browser. Debugging and testing the logic of these user-defined functions is currently not supported in the Stream Analytics portal. Once the function works as expected, you can add it to the Stream Analytics job as mentioned above and then invoke it directly from your query.
 
 ## Call a JavaScript user-defined function in a query
 
 1. In the query editor, under the **Job topology** heading, select **Query**.
-2.	Edit your query, and then call the user-defined function, like this:
+2.    Edit your query, and then call the user-defined function, like this:
 
     ```SQL
     SELECT
@@ -85,8 +85,8 @@ You can test and debug your JavaScript UDF logic in any browser. Debugging and t
         InputStream
     ```
 
-3.	To upload the sample data file, right-click the job input.
-4.	To test your query, select **Test**.
+3.    To upload the sample data file, right-click the job input.
+4.    To test your query, select **Test**.
 
 
 ## Supported JavaScript objects
