Merge pull request #115178 from john-par/1704856-clean-up-broken-azure-docs-pr-links-05-13

1704856 clean up broken azure docs pr links 05-13

Author: ktoliver

articles/api-management/api-management-configuration-repository-git.md

@@ -169,7 +169,7 @@ These files can be created, deleted, edited, and managed on your local file syst
 >
 > * [Users](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/user)
 > * [Subscriptions](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/subscription)
-> * [Named Values](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/property)
+> * Named Values
 > * Developer portal entities other than styles
 >
 

articles/api-management/api-management-howto-properties.md

@@ -55,17 +55,13 @@ Named values can contain literal strings and [policy expressions](/azure/api-man
 
 Once the named value is created, you can edit it by clicking on it. If you change the named value name, any policies that reference that named value are automatically updated to use the new name.
 
-For information on editing a named value using the REST API, see [Edit a named value using the REST API](/rest/api/apimanagement/2019-12-01/property?patch).
-
 ## To delete a named value
 
 To delete a named value, click **Delete** beside the named value to delete.
 
 > [!IMPORTANT]
 > If the named value is referenced by any policies, you will be unable to successfully delete it until you remove the named value from all policies that use it.
 
-For information on deleting a named value using the REST API, see [Delete a named value using the REST API](/rest/api/apimanagement/2019-12-01/property/delete).
-
 ## To search and filter named values
 
 The **Named values** tab includes searching and filtering capabilities to help you manage your named values. To filter the named values list by name, enter a search term in the **Search property** textbox. To display all named values, clear the **Search property** textbox and press enter.

articles/api-management/security-baseline.md

@@ -1066,9 +1066,9 @@ The service backup and restore features of API Management provide the necessary
 
 * [How to implement disaster recovery using service backup and restore in Azure API Management](https://docs.microsoft.com/azure/api-management/api-management-howto-disaster-recovery-backup-restore#calling-the-backup-and-restore-operations)
 
-* [How to call the API Management backup operation](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/apimanagementservice/backup)
+* [How to call the API Management backup operation](/rest/api/apimanagement/2019-12-01/apimanagementservice/backup)
 
-* [How to call the API Management restore operation](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/apimanagementservice/restore)
+* [How to call the API Management restore operation](/rest/api/apimanagement/2019-12-01/apimanagementservice/restore)
 
 **Azure Security Center monitoring**: Not applicable
 

articles/azure-databricks/TOC.yml

@@ -1026,7 +1026,7 @@
         href: /azure/databricks/security/access-control/pool-acl
         maintainContext: true  
       - name: Jobs access control
-        href: /azure/databricks/security/access-control/job-acl
+        href: /azure/databricks/security/access-control/jobs-acl
         maintainContext: true
       - name: Table access control
         items:
@@ -1676,7 +1676,7 @@
           - name: SCIM API (Users)
             href: /azure/databricks/dev-tools/api/latest/scim/scim-users
           - name: SCIM API (Groups)
-            href: /azure/databricks/dev-tools/api/latest/scim/scim-group
+            href: /azure/databricks/dev-tools/api/latest/scim/scim-groups
         maintainContext: true 
       - name: Secrets
         href: /azure/databricks/dev-tools/api/latest/secrets

articles/compliance/index.yml

@@ -217,9 +217,6 @@ conceptualContent:
         - url: https://docs.microsoft.com/microsoft-365/compliance/offering-nen-7510-netherlands
           itemType: concept
           text: NEN 7510 (Netherlands)
-        - url: https://docs.microsoft.com/microsoft-365/compliance/offering-nhs-ig-toolkit-uk
-          itemType: concept
-          text: NHS IG Toolkit (UK)
 
     # Card
     - title: Media and manufacturing

articles/iot-hub/iot-hub-reliability-features-in-sdks.md

@@ -86,7 +86,7 @@ The SDKs provide three retry policies:
    |  C/iOS  | [IOTHUB_CLIENT_RESULT IoTHubClient_SetRetryPolicy](https://github.com/Azure/azure-iot-sdk-c/blob/2018-05-04/iothub_client/inc/iothub_client.h#L188)        | **Default**: [IOTHUB_CLIENT_RETRY_EXPONENTIAL_BACKOFF](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/connection_and_messaging_reliability.md#connection-retry-policies)<BR>**Custom:** use available [retryPolicy](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/connection_and_messaging_reliability.md#connection-retry-policies)<BR>**No retry:** [IOTHUB_CLIENT_RETRY_NONE](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/connection_and_messaging_reliability.md#connection-retry-policies)  | [C/iOS implementation](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/connection_and_messaging_reliability.md#)  |
    | Java| [SetRetryPolicy](https://docs.microsoft.com/java/api/com.microsoft.azure.sdk.iot.device.deviceclientconfig.setretrypolicy?view=azure-java-stable)        | **Default**: [ExponentialBackoffWithJitter class](https://github.com/Azure/azure-iot-sdk-java/blob/master/device/iot-device-client/src/main/java/com/microsoft/azure/sdk/iot/device/transport/NoRetry.java)<BR>**Custom:** implement [RetryPolicy interface](https://github.com/Azure/azure-iot-sdk-java/blob/master/device/iot-device-client/src/main/java/com/microsoft/azure/sdk/iot/device/transport/RetryPolicy.java)<BR>**No retry:** [NoRetry class](https://github.com/Azure/azure-iot-sdk-java/blob/master/device/iot-device-client/src/main/java/com/microsoft/azure/sdk/iot/device/transport/NoRetry.java)  | [Java implementation](https://github.com/Azure/azure-iot-sdk-java/blob/master/device/iot-device-client/devdoc/requirement_docs/com/microsoft/azure/iothub/retryPolicy.md) |
    | .NET| [DeviceClient.SetRetryPolicy](/dotnet/api/microsoft.azure.devices.client.deviceclient.setretrypolicy?view=azure-dotnet) | **Default**: [ExponentialBackoff class](/dotnet/api/microsoft.azure.devices.client.exponentialbackoff?view=azure-dotnet)<BR>**Custom:** implement [IRetryPolicy interface](https://docs.microsoft.com/dotnet/api/microsoft.azure.devices.client.iretrypolicy?view=azure-dotnet)<BR>**No retry:** [NoRetry class](/dotnet/api/microsoft.azure.devices.client.noretry?view=azure-dotnet) | [C# implementation](https://github.com/Azure/azure-iot-sdk-csharp) | |
-   | Node| [setRetryPolicy](/javascript/api/azure-iot-device/client?view=azure-iot-typescript-latest) | **Default**: [ExponentialBackoffWithJitter class](/javascript/api/azure-iot-common/exponentialbackoffwithjitter?view=azure-iot-typescript-latest)<BR>**Custom:** implement [RetryPolicy interface](/javascript/api/azure-iot-common/retrypolicy?view=azure-iot-typescript-latest)<BR>**No retry:** [NoRetry class](/javascript/api/azure-iot-common/noretry?view=azure-iot-typescript-latest) | [Node implementation](https://github.com/Azure/azure-iot-sdk-node/wiki/Connectivity-and-Retries#types-of-errors-and-how-to-detect-them) |
+   | Node| [setRetryPolicy](/javascript/api/azure-iot-device/client?view=azure-iot-typescript-latest) | **Default**: [ExponentialBackoffWithJitter class](https://github.com/Azure/azure-iot-sdk-java/blob/master/device/iot-device-client/src/main/java/com/microsoft/azure/sdk/iot/device/transport/NoRetry.java) | [Node implementation](https://github.com/Azure/azure-iot-sdk-node/wiki/Connectivity-and-Retries#types-of-errors-and-how-to-detect-them) |
    | Python| Not currently supported | Not currently supported | Not currently supported |
 
 The following code samples illustrate this flow:

articles/machine-learning/team-data-science-process/apps-anomaly-detection-api.md

@@ -19,7 +19,7 @@ ms.custom: seodec18, previous-author=alokkirpal, previous-ms.author=alok
 > This item is under maintenance. We encourage you to use the [Anomaly Detector API service](https://azure.microsoft.com/services/cognitive-services/anomaly-detector/) powered by a gallery of Machine Learning algorithms under Azure Cognitive Services to detect anomalies from business, operational, and IoT metrics.
 
 ## Overview
-[Anomaly Detection API](https://gallery.cortanaintelligence.com/MachineLearningAPI/Anomaly-Detection-2) is an example built with Azure Machine Learning that detects anomalies in time series data with numerical values that are uniformly spaced in time.
+[Anomaly Detection API](https://gallery.azure.ai/MachineLearningAPI/Anomaly-Detection-2) is an example built with Azure Machine Learning that detects anomalies in time series data with numerical values that are uniformly spaced in time.
 
 This API can detect the following types of anomalous patterns in time series data:
 
@@ -34,20 +34,20 @@ The Anomaly Detection offering comes with useful tools to get you started.
 * The [web application](https://anomalydetection-aml.azurewebsites.net/) helps you evaluate and visualize the results of anomaly detection APIs on your data.
 
 > [!NOTE]
-> Try **IT Anomaly Insights solution** powered by [this API](https://gallery.cortanaintelligence.com/MachineLearningAPI/Anomaly-Detection-2)
+> Try **IT Anomaly Insights solution** powered by [this API](https://gallery.azure.ai/MachineLearningAPI/Anomaly-Detection-2)
 >
 <!-- This Solution is no longer available
 > To get this end to end solution deployed to your Azure subscription <a href="https://gallery.cortanaintelligence.com/Solution/Anomaly-Detection-Pre-Configured-Solution-1" target="_blank">**Start here >**</a>
 -->
 
 ## API Deployment
-In order to use the API, you must deploy it to your Azure subscription where it will be hosted as an Azure Machine Learning web service.  You can do this from the [Azure AI Gallery](https://gallery.cortanaintelligence.com/MachineLearningAPI/Anomaly-Detection-2).  This will deploy two Azure Machine Learning Studio (classic) Web Services (and their related resources) to your Azure subscription - one for anomaly detection with seasonality detection, and one without seasonality detection.  Once the deployment has completed, you will be able to manage your APIs from the [Azure Machine Learning Studio (classic) web services](https://services.azureml.net/webservices/) page.  From this page, you will be able to find your endpoint locations, API keys, as well as sample code for calling the API.  More detailed instructions are available [here](https://docs.microsoft.com/azure/machine-learning/machine-learning-manage-new-webservice).
+In order to use the API, you must deploy it to your Azure subscription where it will be hosted as an Azure Machine Learning web service.  You can do this from the [Azure AI Gallery](https://gallery.azure.ai/MachineLearningAPI/Anomaly-Detection-2).  This will deploy two Azure Machine Learning Studio (classic) Web Services (and their related resources) to your Azure subscription - one for anomaly detection with seasonality detection, and one without seasonality detection.  Once the deployment has completed, you will be able to manage your APIs from the [Azure Machine Learning Studio (classic) web services](https://services.azureml.net/webservices/) page.  From this page, you will be able to find your endpoint locations, API keys, as well as sample code for calling the API.  More detailed instructions are available [here](/azure/machine-learning/studio/manage-new-webservice).
 
 ## Scaling the API
 By default, your deployment will have a free Dev/Test billing plan that includes 1,000 transactions/month and 2 compute hours/month.  You can upgrade to another plan as per your needs.  Details on the pricing of different plans are available [here](https://azure.microsoft.com/pricing/details/machine-learning/) under "Production Web API pricing".
 
 ## Managing AML Plans
-You can manage your billing plan [here](https://services.azureml.net/plans/).  The plan name will be based on the resource group name you chose when deploying the API, plus a string that is unique to your subscription.  Instructions on how to upgrade your plan are available [here](https://docs.microsoft.com/azure/machine-learning/machine-learning-manage-new-webservice) under the "Managing billing plans" section.
+You can manage your billing plan [here](https://services.azureml.net/plans/).  The plan name will be based on the resource group name you chose when deploying the API, plus a string that is unique to your subscription.  Instructions on how to upgrade your plan are available [here](/azure/machine-learning/studio/manage-new-webservice) under the "Managing billing plans" section.
 
 ## API Definition
 The web service provides a REST-based API over HTTPS that can be consumed in different ways including a web or mobile application, R, Python, Excel, etc.  You send your time series data to this service via a REST API call, and it runs a combination of the three anomaly types described below.

articles/marketplace/marketplace-faq-publisher-guide.md

@@ -304,7 +304,7 @@ To receive refunds, customers can cancel subscriptions within a specified time f
 
 Here are some resources to get you started:
 
-- [Introduction to the Microsoft commercial marketplace](https://docs.microsoft.com/learn/commercial-marketplace/intro-commercial-marketplace/intro-commercial-marketplace/)
+- [Introduction to the Microsoft commercial marketplace](/azure/marketplace/marketplace-publishers-guide)
 - [Microsoft commercial marketplace partner hub](https://partner.microsoft.com/asset/collection/commercial-marketplace#/)
 - [Welcome to the commercial marketplace](https://docs.microsoft.com/azure/marketplace/)
 

articles/security-center/alerts-suppression-rules.md

@@ -142,7 +142,7 @@ The relevant HTTP methods for suppression rules in the REST API are:
 
 - **DELETE**: Deletes an existing rule (but doesn't change the status of alerts already dismissed by it).
 
-For full details and usage examples, see the [API documentation](https://docs.microsoft.com/api/securitycenter/). 
+For full details and usage examples, see the [API documentation](/azure/security-center/). 
 
 
 ## Next steps

articles/synapse-analytics/sql-data-warehouse/toc.yml

@@ -366,7 +366,7 @@
     - name: Build dashboards and reports 
       items:
       - name: Visualize with Power BI
-        href: /power-bi/service-azure-sql-data-warehouse-with-direct-connect.md 
+        href: /power-bi/service-azure-sql-data-warehouse-with-direct-connect
   - name: Troubleshoot
     items:
     - name: Connectivity