Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into aoaif

Author: dlepow

.openpublishing.redirection.azure-monitor.json

@@ -6893,6 +6893,11 @@
           "source_path_from_root": "/articles/azure-monitor/essentials/private-link-data-ingestion.md",
           "redirect_url": "/azure/azure-monitor/containers/kubernetes-monitoring-private-link",
           "redirect_document_id": false
+        },
+        {
+          "source_path_from_root": "/articles/azure-monitor/containers/container-insights-custom-metrics.md",
+          "redirect_url": "/previous-versions/azure/azure-monitor/containers/container-insights-custom-metrics",
+          "redirect_document_id": false
         }
     ]
 }

.openpublishing.redirection.json

@@ -1,5 +1,195 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/kinect-dk/index.yml",
+      "redirect_url": "/previous-versions/azure/kinect-dk/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/about-azure-kinect-dk.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/about-azure-kinect-dk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/about-sensor-sdk.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/about-sensor-sdk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/access-data-body-frame.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/access-data-body-frame",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/access-mics.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/access-mics",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/add-library-to-project.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/add-library-to-project",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/azure-kinect-firmware-tool.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/azure-kinect-firmware-tool",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/azure-kinect-recorder.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/azure-kinect-recorder",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/azure-kinect-viewer.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/azure-kinect-viewer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/body-index-map.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/body-index-map",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/body-joints.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/body-joints",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/body-sdk-download.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/body-sdk-download",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/body-sdk-setup.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/body-sdk-setup",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/build-first-app.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/build-first-app",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/build-first-body-app.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/build-first-body-app",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/capture-device-synchronization.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/capture-device-synchronization",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/coordinate-systems.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/coordinate-systems",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/depth-camera.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/depth-camera",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/find-then-open-device.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/find-then-open-device",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/get-body-tracking-results.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/get-body-tracking-results",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/hardware-specification.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/hardware-specification",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/multi-camera-sync.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/multi-camera-sync",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/record-external-synchronized-units.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/record-external-synchronized-units",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/record-file-format.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/record-file-format",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/record-playback-api.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/record-playback-api",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/record-sensor-streams-file.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/record-sensor-streams-file",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/reset-azure-kinect-dk.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/reset-azure-kinect-dk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/retrieve-images.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/retrieve-images",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/retrieve-imu-samples.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/retrieve-imu-samples",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/sensor-sdk-download.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/sensor-sdk-download",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/set-up-azure-kinect-dk.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/set-up-azure-kinect-dk",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/support.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/support",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/system-requirements.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/system-requirements",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/troubleshooting.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/troubleshooting",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/update-device-firmware.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/update-device-firmware",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/use-calibration-functions.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/use-calibration-functions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/use-image-transformation.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/use-image-transformation",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/kinect-dk/windows-comparison.md",
+      "redirect_url": "/previous-versions/azure/kinect-dk/windows-comparison",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/public-multi-access-edge-compute-mec/considerations-for-deployment.md",
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/considerations-for-deployment",
@@ -4561,4 +4751,4 @@
       "redirect_document_id": false
     }
   ]
-}
+}

.openpublishing.redirection.sentinel.json

@@ -1,5 +1,15 @@
 {
     "redirections": [
+        {
+            "source_path": "articles/sentinel/best-practices-workspace-architecture.md",
+            "redirect_url": "/azure/azure-monitor/logs/workspace-design",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/sentinel/design-your-workspace-architecture.md",
+            "redirect_url": "/azure/azure-monitor/logs/workspace-design",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/sentinel/notebooks-troubleshoot.md",
             "redirect_url": "/azure/sentinel/notebooks-hunt",

articles/api-center/enable-managed-api-analysis-linting.md

@@ -14,8 +14,9 @@ ms.custom:
 
 This article explains how to enable API analysis in [Azure API Center](overview.md) without having to manage it yourself (preview). API analysis offers linting capabilities to analyze API definitions in your organization's API center. Linting ensures your API definitions adhere to organizational style rules, generating both individual and summary reports. Use API analysis to identify and correct common errors and inconsistencies in your API definitions.
 
-> [!NOTE]
-> With managed linting and analysis, API Center sets up a linting engine and any required dependencies and triggers. You can also enable linting and analysis [manually](enable-api-analysis-linting.md). 
+> [!IMPORTANT]
+> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) using a custom Azure function. **Disable any function used for manual linting before enabling managed API analysis.**
+
 
 In this scenario:
 
@@ -29,6 +30,9 @@ In this scenario:
 * Currently, only OpenAPI specification documents in JSON or YAML format are analyzed.
 * By default, you enable analysis with the [`spectral:oas` ruleset](https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules). To learn more about the built-in rules, see the [Spectral GitHub repo](https://github.com/stoplightio/spectral/blob/develop/docs/reference/openapi-rules.md). 
 * Currently, you configure a single ruleset, and it's applied to all OpenAPI definitions in your API center.
+* The following are limits for maximum number of API definitions linted per 4 hours:
+    * Free tier: 10
+    * Standard tier: 100
 
 ## Prerequisites
 

articles/api-center/includes/api-center-service-limits.md

@@ -23,6 +23,7 @@ ms.custom: Include file
 | Maximum number of custom metadata properties per entity<sup>3</sup> | 10 | 20 |
 | Maximum number of child properties in custom metadata property of type "object" | 10 |10 | 
 | Maximum requests per minute (data plane) | 3,000 | 6,000  |
+| Maximum number of API definitions [linted](../enable-managed-api-analysis-linting.md) per 4 hours | 10 | 100  |
 
 <sup>1</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>
 <sup>2</sup> In the Free plan, use of full service features including API analysis and access through the data plane API is limited to 5 APIs.<br/>

articles/api-management/breaking-changes/overview.md

@@ -26,7 +26,7 @@ The following table lists all the upcoming breaking changes and feature retireme
 | [API version retirements][api2023] | June 1, 2024 |
 | [Workspaces preview breaking changes][workspaces2024] | June 14, 2024 |
 | [stv1 platform retirement - Global Azure][stv12024] | August 31, 2024 |
-| [stv1 platform retirement - Azure Government, Azure in China][stv1sov2025] | February 28, 2025 |
+| [stv1 platform retirement - Azure Government, Azure in China][stv1sov2025] | February 25, 2025 |
 | [Git repository retirement][git2025] | March 15, 2025 |
 | [Direct management API retirement][mgmtapi2025] | March 15, 2025 |
 | [Workspaces preview breaking changes, part 2][workspaces2025march] | March 31, 2025 |

articles/api-management/breaking-changes/stv1-platform-retirement-august-2024.md

@@ -16,7 +16,7 @@ ms.author: danlep
 As a cloud platform-as-a-service (PaaS), Azure API Management abstracts many details of the infrastructure used to host and run your service. **The infrastructure associated with the API Management `stv1` compute platform version will be retired effective 31 August 2024 in the global Microsoft Azure cloud.** A more current compute platform version (`stv2`) is already available, and provides enhanced service capabilities.
 
 > [!NOTE]
-> For API Management instances deployed in Microsoft Azure Government cloud or Microsoft Azure operated by 21Vianet cloud (Azure in China), the retirement date for the `stv1` platform is 28 February 2025. [Learn more](stv1-platform-retirement-sovereign-clouds-february-2025.md)
+> For API Management instances deployed in Microsoft Azure Government cloud or Microsoft Azure operated by 21Vianet cloud (Azure in China), the retirement date for the `stv1` platform is 24 February 2025. [Learn more](stv1-platform-retirement-sovereign-clouds-february-2025.md)
 
 The following table summarizes the compute platforms currently used for instances in the different API Management service tiers. 
 

articles/api-management/breaking-changes/stv1-platform-retirement-sovereign-clouds-february-2025.md

@@ -1,6 +1,6 @@
 ---
 title: Azure API Management - stv1 platform retirement - Azure Government, Azure in China (February 2025)
-description: In Azure Government and Azure operated by 21Vianet, API Management will retire stv1 platform effective 28 February 2025. Instances must be migrated to stv2 platform.
+description: In Azure Government and Azure operated by 21Vianet, API Management will retire stv1 platform effective 24 February 2025. Instances must be migrated to stv2 platform.
 services: api-management
 author: dlepow
 ms.service: azure-api-management
@@ -13,7 +13,7 @@ ms.author: danlep
 
 [!INCLUDE [api-management-availability-premium-dev-standard-basic](../../../includes/api-management-availability-premium-dev-standard-basic.md)]
 
-As a cloud platform-as-a-service (PaaS), Azure API Management abstracts many details of the infrastructure used to host and run your service. **The infrastructure associated with the API Management `stv1` compute platform version will be retired effective 28 February 2025 in Microsoft Azure Government and in Microsoft Azure operated by 21 Vianet (Azure in China).** A more current compute platform version (`stv2`) is already available, and provides enhanced service capabilities.
+As a cloud platform-as-a-service (PaaS), Azure API Management abstracts many details of the infrastructure used to host and run your service. **The infrastructure associated with the API Management `stv1` compute platform version will be retired effective 24 February 2025 in Microsoft Azure Government and in Microsoft Azure operated by 21 Vianet (Azure in China).** A more current compute platform version (`stv2`) is already available, and provides enhanced service capabilities.
 
 > [!NOTE]
 > For API Management instances deployed in global Microsoft Azure, the retirement date for the `stv1` platform is 31 August 2024. [Learn more](stv1-platform-retirement-august-2024.md)
@@ -36,11 +36,11 @@ If the value of the `platformVersion` property of your service is `stv1`, it's h
 
 ## What is the deadline for the change?
 
-In Azure Government and Azure operated by 21Vianet, support for API Management instances hosted on the `stv1` platform will be retired by 28 February 2025.
+In Azure Government and Azure operated by 21Vianet, support for API Management instances hosted on the `stv1` platform will be retired by 24 February 2025.
 
 ## What do I need to do?
 
-**Migrate all your existing instances hosted on the `stv1` compute platform to the `stv2` compute platform by 28 February 2025.**  
+**Migrate all your existing instances hosted on the `stv1` compute platform to the `stv2` compute platform by 24 February 2025.**  
 
 If you have existing instances hosted on the `stv1` platform, follow our **[migration guide](../migrate-stv1-to-stv2.md)** to ensure a successful migration. 
 

articles/automation/automation-create-alert-triggered-runbook.md

@@ -3,7 +3,7 @@ title: Use an alert to trigger an Azure Automation runbook
 description: This article tells how to trigger a runbook to run when an Azure alert is raised.
 services: automation
 ms.subservice: process-automation
-ms.date: 12/15/2022
+ms.date: 08/28/2024
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell
 #Customer intent: As a developer, I want to trigger a runbook so that VMs can be stopped under certain conditions.
@@ -102,7 +102,7 @@ To use Automation with alerts, you need a runbook that manages the alert JSON pa
 
 As described in the preceding section, each type of alert has a different schema. The script takes the webhook data from an alert in the `WebhookData` runbook input parameter. Then, the script evaluates the JSON payload to determine which alert type is being used.
 
-This example uses an alert from an Azure virtual machine (VM). It retrieves the VM data from the payload, and then uses that information to stop the VM. The connection must be set up in the Automation account where the runbook is run. When using alerts to trigger runbooks, it's important to check the alert status in the runbook that is triggered. The runbook triggers each time the alert changes state. Alerts have multiple states, with the two most common being Activated and Resolved. Check for state in your runbook logic to ensure the runbook doesn't run more than once. The example in this article shows how to look for alerts with state Activated only.
+This example utilizes an alert from an Azure virtual machine (VM). It extracts the VM data from the payload, specifically from the target resource of the triggered alert, and then utilizes that information to stop the VM. The connection must be set up in the Automation account where the runbook is run. When using alerts to trigger runbooks, it's important to check the alert status in the runbook that is triggered. The runbook triggers each time the alert changes state. Alerts have multiple states, with the two most common being Activated and Resolved. Check for state in your runbook logic to ensure the runbook doesn't run more than once. The example in this article shows how to look for alerts with state Activated only.
 
 The runbook uses the Automation account [system-assigned managed identity](./automation-security-overview.md#managed-identities) to authenticate with Azure to perform the management action against the VM. The runbook can be easily modified to use a user-assigned managed identity.