Merge pull request #282469 from mohitp930/mp7302024-validation

Bulk update: Global effort to fix validation errors

Author: JamesJBarnett

articles/ai-services/custom-vision-service/index.yml

@@ -101,9 +101,9 @@ landingContent:
       - linkListType: reference
         links:
           - text: Training API
-            url: https://go.microsoft.com/fwlink/?linkid=865446
+            url: /rest/api/customvision/train-project
           - text: Prediction API
-            url: https://go.microsoft.com/fwlink/?linkid=865445
+            url: /rest/api/customvision/operation-groups
           - text: .NET SDK
             url: /dotnet/api/overview/azure/custom-vision
           - text: Python SDK

articles/azure-government/documentation-government-csp-list.md

@@ -329,7 +329,7 @@ Below you can find a list of all the authorized Cloud Solution Providers (CSPs),
 |[Perizer Corp.](https://perizer.com)|
 |[Perrygo Consulting Group, LLC](https://perrygo.com)|
 |Phacil (By Light) |
-|[Pharicode LLC](https://pharicode.com)|
+|[Pharicode LLC](https://glidefast.com/)|
 |Philistin & Heller Group, Inc.|
 |[Picis Envision](https://www.picis.com/en/)|
 |[Pinao Consulting LLC](https://www.pcg-msp.com)|

articles/azure-monitor/essentials/activity-log.md

@@ -23,7 +23,7 @@ For details on how to create a diagnostic setting, see [Create diagnostic settin
 > [!TIP]
 > * Sending logs to Log Analytics workspace if free of charge for the default retention period.
 > * Send to Azure Monitor Logs for more complex querying and alerting and for longer retention of up to 12 years.
-> * Logs exported to a Log Analytics workspace can be [shown in Power BI](https://learn.microsoft.com/power-bi/transform-model/log-analytics/desktop-log-analytics-overview)
+> * Logs exported to a Log Analytics workspace can be [shown in Power BI](/power-bi/transform-model/log-analytics/desktop-log-analytics-overview)
 > * [Insights](./activity-log-insights.md) are provided for Activity Logs exported to Log Analytics.
 
 > [!NOTE]

articles/azure-vmware/azure-vmware-solution-horizon.md

@@ -217,4 +217,4 @@ To understand the Azure virtual machine sizes that are required for the Horizon
 
 
 ## Next steps
-To learn more about VMware Horizon on Azure VMware Solution, read the [VMware Horizon FAQ](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/horizon/vmw-horizon-on-microsoft-azure-vmware-solution-faq.pdf).
+To learn more about VMware Horizon on Azure VMware Solution, read the [VMware Horizon FAQ](https://www.vmware.com/docs/vmw-horizon-faqs).

articles/data-factory/connector-quickbooks.md

@@ -4,7 +4,7 @@ description: Learn how to copy data from QuickBooks Online to supported sink dat
 titleSuffix: Azure Data Factory & Azure Synapse
 author: jianleishen
 ms.author: jianleishen
-ms.service: data-factory
+ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
@@ -112,7 +112,7 @@ The following properties are supported for QuickBooks linked service:
 
 When you use the QuickBooks Online connector in a linked service, it's important to manage OAuth 2.0 refresh tokens from QuickBooks correctly. The linked service uses a refresh token to obtain new access tokens. However, QuickBooks Online periodically updates the refresh token, invalidating the previous one. The linked service does not automatically update the refresh token in Azure Key Vault, so you need to manage updating the refresh token to ensure uninterrupted connectivity. Otherwise you might encounter authentication failures once the refresh token expires.
 
-You can manually update the refresh token in Azure Key Vault based on QuickBooks Online's refresh token expiry policy. But another approach is to automate updates with a scheduled task or [Azure Function](/samples/azure/azure-quickstart-templates/functions-keyvault-secret-rotation) that checks for a new refresh token and updates it in Azure Key Vault.
+You can manually update the refresh token in Azure Key Vault based on QuickBooks Online's refresh token expiry policy. But another approach is to automate updates with a scheduled task or [Azure Function](https://github.com/Azure-Samples/serverless-keyvault-secret-rotation-handling) that checks for a new refresh token and updates it in Azure Key Vault.
 
 ## Dataset properties
 

articles/digital-twins/concepts-event-notifications.md

@@ -7,7 +7,7 @@ author: baanders
 ms.author: baanders # Microsoft employees only
 ms.date: 11/10/2022
 ms.topic: conceptual
-ms.service: digital-twins
+ms.service: azure-digital-twins
 
 # Optional fields. Don't forget to remove # if you need a field.
 # ms.custom: can-be-multiple-comma-separated
@@ -379,7 +379,7 @@ An example message body, populated in AMQP's *data* section:
 
 ## Digital twin telemetry messages
 
-Digital twins can use the [SendTelemetry API](/rest/api/digital-twins/dataplane/twins/digitaltwins_sendtelemetry) to emit *telemetry messages* and send them to egress endpoints.
+Digital twins can use the [SendTelemetry API](/rest/api/digital-twins/dataplane/twins/digital-twins-send-telemetry) to emit *telemetry messages* and send them to egress endpoints.
 
 ### Properties
 

articles/digital-twins/concepts-query-units.md

@@ -7,7 +7,7 @@ author: baanders
 ms.author: baanders # Microsoft employees only
 ms.date: 03/01/2022
 ms.topic: conceptual
-ms.service: digital-twins
+ms.service: azure-digital-twins
 
 # Optional fields. Don't forget to remove # if you need a field.
 # ms.custom: can-be-multiple-comma-separated
@@ -46,6 +46,6 @@ To learn more about querying Azure Digital Twins, visit:
 
 * [Query language](concepts-query-language.md)
 * [Query the twin graph](how-to-query-graph.md)
-* [Query API reference documentation](/rest/api/digital-twins/dataplane/query/querytwins)
+* [Query API reference documentation](/rest/api/digital-twins/dataplane/query/query-twins)
 
 You can find Azure Digital Twins query-related limits in [Azure Digital Twins service limits](reference-service-limits.md).

articles/digital-twins/how-to-create-endpoints.md

@@ -6,7 +6,7 @@ author: baanders
 ms.author: baanders # Microsoft employees only
 ms.date: 02/08/2023
 ms.topic: how-to
-ms.service: digital-twins
+ms.service: azure-digital-twins
 ms.custom: devx-track-azurecli
 
 # Optional fields. Don't forget to remove # if you need a field.
@@ -301,7 +301,7 @@ Next, create a SAS token for your storage account that the endpoint can use to a
 
 # [Portal](#tab/portal)
 
-To create an endpoint with dead-lettering enabled, you must use the [CLI commands](/cli/azure/dt) or [control plane APIs](/rest/api/digital-twins/controlplane/endpoints/digitaltwinsendpoint_createorupdate) to create your endpoint, rather than the Azure portal.
+To create an endpoint with dead-lettering enabled, you must use the [CLI commands](/cli/azure/dt) or [control plane APIs](/rest/api/digital-twins/controlplane/endpoints/digital-twins-endpoint-create-or-update) to create your endpoint, rather than the Azure portal.
 
 For instructions on how to create this type of endpoint with the Azure CLI, switch to the CLI tab for this section.
 
@@ -318,7 +318,7 @@ The value for the parameter is the dead letter SAS URI made up of the storage ac
 >[!TIP]
 >To create a dead-letter endpoint with identity-based authentication, add both the dead-letter parameter from this section and the appropriate [managed identity parameter](#3-create-the-endpoint-with-identity-based-authentication) to the same command.
 
-You can also create dead letter endpoints using the [Azure Digital Twins control plane APIs](concepts-apis-sdks.md#control-plane-apis) instead of the CLI. To do so, view the [DigitalTwinsEndpoint documentation](/rest/api/digital-twins/controlplane/endpoints/digitaltwinsendpoint_createorupdate) to see how to structure the request and add the dead letter parameters.
+You can also create dead letter endpoints using the [Azure Digital Twins control plane APIs](concepts-apis-sdks.md#control-plane-apis) instead of the CLI. To do so, view the [DigitalTwinsEndpoint documentation](/rest/api/digital-twins/controlplane/endpoints/digital-twins-endpoint-create-or-update) to see how to structure the request and add the dead letter parameters.
 
 ---
 

articles/digital-twins/how-to-create-routes.md

@@ -6,7 +6,7 @@ author: baanders
 ms.author: baanders # Microsoft employees only
 ms.date: 1/3/2024
 ms.topic: how-to
-ms.service: digital-twins
+ms.service: azure-digital-twins
 ms.custom: devx-track-azurecli
 
 # Optional fields. Don't forget to remove # if you need a field.
@@ -16,7 +16,7 @@ ms.custom: devx-track-azurecli
 
 # Create event routes and filters in Azure Digital Twins
 
-This article walks you through the process of creating *event routes* using the [Azure portal](https://portal.azure.com), [Azure CLI az dt route commands](/cli/azure/dt/route), [Event Routes data plane APIs](/rest/api/digital-twins/dataplane/eventroutes), and the [.NET (C#) SDK](/dotnet/api/overview/azure/digitaltwins.core-readme).
+This article walks you through the process of creating *event routes* using the [Azure portal](https://portal.azure.com), [Azure CLI az dt route commands](/cli/azure/dt/route), [Event Routes data plane APIs](/rest/api/digital-twins/dataplane/event-routes), and the [.NET (C#) SDK](/dotnet/api/overview/azure/digitaltwins.core-readme).
 
 Routing [event notifications](concepts-event-notifications.md) from Azure Digital Twins to downstream services or connected compute resources is a two-step process: create endpoints, then create event routes to send data to those endpoints. This article covers the second step, setting up routes to control which events are delivered to which Azure Digital Twin endpoints. To proceed with this article, you should have [endpoints](how-to-create-endpoints.md) already created.
 
@@ -60,7 +60,7 @@ If there's no route name, no messages are routed outside of Azure Digital Twins.
 If there's a route name and the filter is `true`, all messages are routed to the endpoint. 
 If there's a route name and a different filter is added, messages will be filtered based on the filter.
 
-Event routes can be created with the [Azure portal](https://portal.azure.com), [EventRoutes data plane APIs](/rest/api/digital-twins/dataplane/eventroutes), or [az dt route CLI commands](/cli/azure/dt/route). The rest of this section walks through the creation process.
+Event routes can be created with the [Azure portal](https://portal.azure.com), [EventRoutes data plane APIs](/rest/api/digital-twins/dataplane/event-routes), or [az dt route CLI commands](/cli/azure/dt/route). The rest of this section walks through the creation process.
 
 # [Portal](#tab/portal2)
 
@@ -143,7 +143,7 @@ To create an event route with advanced filter options, toggle the switch for the
 
 # [API](#tab/api)
 
-You can use the [Event Routes data plane APIs](/rest/api/digital-twins/dataplane/eventroutes) to write custom filters. To add a filter, you can use a PUT request to `https://<Your-Azure-Digital-Twins-host-name>/eventRoutes/<event-route-name>?api-version=2020-10-31` with the following body:
+You can use the [Event Routes data plane APIs](/rest/api/digital-twins/dataplane/event-routes) to write custom filters. To add a filter, you can use a PUT request to `https://<Your-Azure-Digital-Twins-host-name>/eventRoutes/<event-route-name>?api-version=2020-10-31` with the following body:
 
 :::code language="json" source="~/digital-twins-docs-samples/api-requests/filter.json":::
 

articles/digital-twins/how-to-manage-model.md

@@ -7,7 +7,7 @@ author: baanders
 ms.author: baanders # Microsoft employees only
 ms.date: 06/11/2024
 ms.topic: how-to
-ms.service: digital-twins
+ms.service: azure-digital-twins
 
 # Optional fields. Don't forget to remove # if you need a field.
 # ms.custom: can-be-multiple-comma-separated
@@ -261,7 +261,7 @@ To decommission a model, you can use the [DecommissionModel](/dotnet/api/azure.d
 
 :::code language="csharp" source="~/digital-twins-docs-samples/sdks/csharp/model_operations.cs" id="DecommissionModel":::
 
-You can also decommission a model using the REST API call [DigitalTwinModels Update](/rest/api/digital-twins/dataplane/models/digitaltwinmodels_update). The `decommissioned` property is the only property that can be replaced with this API call. The JSON Patch document will look something like this:
+You can also decommission a model using the REST API call [DigitalTwinModels Update](/rest/api/digital-twins/dataplane/models/digital-twin-models-update). The `decommissioned` property is the only property that can be replaced with this API call. The JSON Patch document will look something like this:
 
 :::code language="json" source="~/digital-twins-docs-samples/models/patch-decommission-model.json":::
 
@@ -297,7 +297,7 @@ To delete a model, you can use the [DeleteModel](/dotnet/api/azure.digitaltwins.
 
 :::code language="csharp" source="~/digital-twins-docs-samples/sdks/csharp/model_operations.cs" id="DeleteModel":::
 
-You can also delete a model with the [DigitalTwinModels Delete](/rest/api/digital-twins/dataplane/models/digitaltwinmodels_delete) REST API call.
+You can also delete a model with the [DigitalTwinModels Delete](/rest/api/digital-twins/dataplane/models/digital-twin-models-delete) REST API call.
 
 #### After deletion: Twins without models