Merge pull request #114699 from DCtheGeek/dmc-brokenlinks-20200511

Broken links from OPS: 2020-05-11

Author: itechedit

articles/azure-functions/functions-kubernetes-keda.md

@@ -24,7 +24,7 @@ To run Functions on your Kubernetes cluster, you must install the KEDA component
 
 ### Installing with Helm
 
-There are various ways to install KEDA in any Kubernetes cluster including Helm.  Deployment options are documented on the [KEDA site](https://keda.sh/deploy/).
+There are various ways to install KEDA in any Kubernetes cluster including Helm.  Deployment options are documented on the [KEDA site](https://keda.sh/docs/deploy/).
 
 ## Deploying a function app to Kubernetes
 

articles/azure-monitor/app/profiler.md

@@ -54,8 +54,8 @@ If you want to enable the profiler for other clouds, you can use the below app s
 
 |App Setting    | US Government Values| China Cloud |   
 |---------------|---------------------|-------------|
-|ApplicationInsightsProfilerEndpoint         | https://agent.serviceprofiler.azure.us    | https://profiler.applicationinsights.azure.cn |
-|ApplicationInsightsEndpoint | https://dc.applicationinsights.us | https://dc.applicationinsights.azure.cn |
+|ApplicationInsightsProfilerEndpoint         | `https://agent.serviceprofiler.azure.us`    | `https://profiler.applicationinsights.azure.cn` |
+|ApplicationInsightsEndpoint | `https://dc.applicationinsights.us` | `https://dc.applicationinsights.azure.cn` |
 
 ## Disable Profiler
 

articles/azure-monitor/app/sdk-connection-string.md

@@ -63,10 +63,10 @@ Connection string consists of a list of settings represented as key-value pairs
    Setting the endpoint suffix will instruct the SDK which Azure cloud to connect to. The SDK will assemble the rest of the endpoint for individual services.
 - Explicit Endpoints.
   Any service can be explicitly overridden in the connection string.
-   - `IngestionEndpoint` (ex: https://dc.applicationinsights.azure.com)
-   - `LiveEndpoint` (ex: https://live.applicationinsights.azure.com)
-   - `ProfilerEndpoint` (ex: https://profiler.applicationinsights.azure.com)
-   - `SnapshotEndpoint` (ex: https://snapshot.applicationinsights.azure.com)
+   - `IngestionEndpoint` (ex: `https://dc.applicationinsights.azure.com`)
+   - `LiveEndpoint` (ex: `https://live.applicationinsights.azure.com`)
+   - `ProfilerEndpoint` (ex: `https://profiler.applicationinsights.azure.com`)
+   - `SnapshotEndpoint` (ex: `https://snapshot.applicationinsights.azure.com`)
 
 #### Endpoint schema
 
@@ -105,10 +105,10 @@ In this example, only the Instrumentation Key has been set.
 - Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on the [SDK defaults](https://github.com/microsoft/ApplicationInsights-dotnet/blob/e50d569cebf485e72e98f4a08a0bc0e30cdf42bc/BASE/src/Microsoft.ApplicationInsights/Extensibility/Implementation/Endpoints/Constants.cs#L6) and will connect to the public global Azure:
-   - Ingestion: https://dc.services.visualstudio.com/
-   - Live metrics: https://rt.services.visualstudio.com/
-   - Profiler: https://agent.azureserviceprofiler.net/
-   - Debugger: https://agent.azureserviceprofiler.net/  
+   - Ingestion: `https://dc.services.visualstudio.com/`
+   - Live metrics: `https://rt.services.visualstudio.com/`
+   - Profiler: `https://agent.azureserviceprofiler.net/`
+   - Debugger: `https://agent.azureserviceprofiler.net/`
 
 
 
@@ -121,10 +121,10 @@ In this example, this connection string specifies the endpoint suffix and the SD
 - Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on provided endpoint suffix: 
-   - Ingestion: https://dc.ai.contoso.com
-   - Live metrics: https://live.ai.contoso.com
-   - Profiler: https://profiler.ai.contoso.com 
-   - Debugger: https://snapshot.ai.contoso.com   
+   - Ingestion: `https://dc.ai.contoso.com`
+   - Live metrics: `https://live.ai.contoso.com`
+   - Profiler: `https://profiler.ai.contoso.com`
+   - Debugger: `https://snapshot.ai.contoso.com`  
 
 
 
@@ -137,10 +137,10 @@ In this example, this connection string specifies explicit overrides for every s
 - Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on the explicit override values: 
-   - Ingestion: https:\//custom.com:111/
-   - Live metrics: https:\//custom.com:222/
-   - Profiler: https:\//custom.com:333/ 
-   - Debugger: https:\//custom.com:444/   
+   - Ingestion: `https://custom.com:111/`
+   - Live metrics: `https://custom.com:222/`
+   - Profiler: `https://custom.com:333/`
+   - Debugger: `https://custom.com:444/`  
 
 
 ## How to set a connection string

articles/azure-monitor/platform/collect-custom-metrics-guestos-resource-manager-vmss.md

@@ -247,7 +247,7 @@ To deploy the Resource Manager template, use Azure PowerShell:
    ```
 
    > [!NOTE]  
-   > Remember to use an Azure region that's enabled for custom metrics. Remember to use an [Azure region that's enabled for custom metrics](https://github.com/MicrosoftDocs/azure-docs-pr/blob/master/articles/azure-monitor/platform/metrics-custom-overview.md#supported-regions).
+   > Remember to use an Azure region that's enabled for custom metrics. Remember to use an [Azure region that's enabled for custom metrics](./metrics-custom-overview.md#supported-regions).
 
 1. Run the following commands to deploy the VM:  
 

articles/event-grid/receive-events.md

@@ -46,7 +46,7 @@ Click on the "View Files" link in your Azure Function (right most pane in the Az
 
 ## Endpoint validation
 
-The first thing you want to do is handle `Microsoft.EventGrid.SubscriptionValidationEvent` events. Every time someone subscribes to an event, Event Grid sends a validation event to the endpoint with a `validationCode` in the data payload. The endpoint is required to echo this back in the response body to [prove the endpoint is valid and owned by you](webhook-event-delivery.md). If you're using an [Event Grid Trigger](../azure-functions/functions-bindings-event-grid.md) rather than a WebHook triggered Function, endpoint validation is handled for you. If you use a third-party API service (like [Zapier](https://zapier.com) or [IFTTT](https://ifttt.com/)), you might not be able to programmatically echo the validation code. For those services, you can manually validate the subscription by using a validation URL that is sent in the subscription validation event. Copy that URL in the `validationUrl` property and send a GET request either through a REST client or your web browser.
+The first thing you want to do is handle `Microsoft.EventGrid.SubscriptionValidationEvent` events. Every time someone subscribes to an event, Event Grid sends a validation event to the endpoint with a `validationCode` in the data payload. The endpoint is required to echo this back in the response body to [prove the endpoint is valid and owned by you](webhook-event-delivery.md). If you're using an [Event Grid Trigger](../azure-functions/functions-bindings-event-grid.md) rather than a WebHook triggered Function, endpoint validation is handled for you. If you use a third-party API service (like [Zapier](https://zapier.com/home) or [IFTTT](https://ifttt.com/)), you might not be able to programmatically echo the validation code. For those services, you can manually validate the subscription by using a validation URL that is sent in the subscription validation event. Copy that URL in the `validationUrl` property and send a GET request either through a REST client or your web browser.
 
 In C#, the `DeserializeEventGridEvents()` function deserializes the Event Grid events. It deserializes the event data into the appropriate type, such as StorageBlobCreatedEventData. Use the `Microsoft.Azure.EventGrid.EventTypes` class to get supported event types and names.
 

articles/lab-services/classroom-labs/class-type-big-data-analytics.md

@@ -98,7 +98,7 @@ In this section, you will deploy HDP Sandbox and then also access HDP Sandbox us
 1. Once the Docker containers for HDP Sandbox are deployed and running, you can access the environment by launching your browser and following Cloudera's instructions for opening the [Sandbox Welcome Page](https://www.cloudera.com/tutorials/learning-the-ropes-of-the-hdp-sandbox.html#welcome-page) and launching the HDP Dashboard.
 
     > [!NOTE] 
-    > These instructions assume that you have first mapped the local IP address of the sandbox environment to the sandbox-hdp.hortonworks.com in the host file on your template VM.  If you do **not** do this mapping, you can access the Sandbox Welcome page by navigating to [http://localhost:8080](http://localhost:8080).
+    > These instructions assume that you have first mapped the local IP address of the sandbox environment to the sandbox-hdp.hortonworks.com in the host file on your template VM.  If you do **not** do this mapping, you can access the Sandbox Welcome page by navigating to `http://localhost:8080`.
 
 ### Automatically start Docker containers when students log in
 

articles/lab-services/classroom-labs/how-to-prepare-windows-template.md

@@ -206,7 +206,7 @@ If you need additional languages installed on the virtual machine, you can add t
 2. Search for "language pack"
 3. Choose language to install
 
-If you are already logged on to the template VM, use ["Install language pack" shortcut](ms-settings:regionlanguage?activationSource=SMC-IA-4027670) to go directly to the appropriate settings page.
+If you are already logged on to the template VM, use "Install language pack" shortcut (`ms-settings:regionlanguage?activationSource=SMC-IA-4027670`) to go directly to the appropriate settings page.
 
 ## Remove unneeded built-in apps
 

articles/media-services/azure-media-player/azure-media-player-plugin-gallery.md

@@ -21,7 +21,7 @@ ms.date: 04/20/2020
 | Frame rate and Timecode  calculator | [Demo](http://mconvertitest001.blob.core.windows.net/public/example.html)                        | [GitHub](https://github.com/mconverti/media-services-javascript-azure-media-player-framerate-timecode-calculator-plugin)                     | This plugin calculates the frame rate of video based on the `tfhd`/`trun` MP4 boxes of the first MPEG-DASH video fragment, parses the time scale value from the MPEG-DASH client manifest, and also provides a way to generate the timecode for a given absolute time from the player (as well as provides the player absolute time given the timecode) |
 | <strike>Playback Speed</strike>                      | [Demo](https://azure-samples.github.io/media-services-javascript-Azure-Media-Player-playback-rate-plugin/)                        | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-time-tip-plugin)                     | This plugin enables viewers to control what speed of the video. *Note, this functionality is automatically available in version AMP v2.0.0+ but disabled by default.* To learn how to enable it, check out our samples [here](https://github.com/Azure-Samples/azure-media-player-samples) |
 | Hover Time Tip                      | [Demo](http://sr-test.azurewebsites.net/Tests/Plugin%20Gallery/plugins/timetip/example.html)                        | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-time-tip-plugin)                     | Displays a time tip over the progress bar on mouse hover for time accurate seeking. *Note: This plugin is already integrated into AMP* but if you're interested in seeing how it's programmed feel free to take a look.                                                                                                                       |
-| Title Overlay                       | [Demo](https://azure-samples.github.io/media-services-javascript-azure-media-player-title-overlay-plugin/")                        | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-title-overlay-plugin)                     | Overlays configurable video title over screen |
+| Title Overlay                       | [Demo](https://azure-samples.github.io/media-services-javascript-azure-media-player-title-overlay-plugin/)                        | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-title-overlay-plugin)                     | Overlays configurable video title over screen |
 | Timeline Markers                    | [Demo](http://sr-test.azurewebsites.net/Tests/Plugin%20Gallery/plugins/timelinemarkers/example.html)                        | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-timeline-markers-plugin)                     | This plugin takes in an array of times and overlays tiny markers over the progress bar at those times. |
 | Analytics                           | | | |
 | Application Insights                | [Blog Post](https://azure.microsoft.com/blog/player-analytics-azure-media-player-plugin/)                   | [GitHub](https://github.com/Azure-Samples/media-services-javascript-azure-media-player-application-insights-plugin)                     | Plugin that tracks your player metrics and ports it to Power BI for an intuitive graphical representation of your viewers' player experience. |

articles/media-services/video-indexer/release-notes.md

@@ -54,7 +54,7 @@ For paid accounts the `Url` field is currently pointing to an internal URL inste
 In the coming weeks we will change it and return the [Video Indexer website](https://www.videoindexer.ai/) URL for all accounts (trial and paid).
 
     Do not use the internal URLs, you should be using the [Video Indexer public APIs](https://api-portal.videoindexer.ai/).
-* If you are embedding Video Indexer URLs in your applications and the URLs are not pointing to the [Video Indexer website](https://www.videoindexer.ai/) or the [Video Indexer API endpoint](https://api.videoindexer.ai) but rather to a regional endpoint (for example, `https://wus2.videoindexer.ai`), regenerate the URLs.
+* If you are embedding Video Indexer URLs in your applications and the URLs are not pointing to the [Video Indexer website](https://www.videoindexer.ai/) or the Video Indexer API endpoint (`https://api.videoindexer.ai`) but rather to a regional endpoint (for example, `https://wus2.videoindexer.ai`), regenerate the URLs.
 
    You can do it it by either:
 

articles/storage/common/monitor-storage-reference.md

@@ -137,7 +137,7 @@ The following table lists the properties for Azure Storage resource logs when th
 |**correlationId** | The ID that is used to correlate logs across resources. For example: `b99ba45e-a01e-0042-4ea6-772bbb000000`. |
 |**location** | The location of storage account. For example: `North Europe`. |
 |**protocol**|The protocol that is used in the operation. For example: `HTTP`, `HTTPS`, `SMB`, or `NFS`|
-| **uri** | Uniform resource identifier that is requested. For example: http://myaccountname.blob.core.windows.net/cont1/blobname?timeout=10. |
+| **uri** | Uniform resource identifier that is requested. For example: `http://myaccountname.blob.core.windows.net/cont1/blobname?timeout=10`. |
 
 ### Fields that describe how the operation was authenticated