Merge pull request #277917 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: PhilKang0704

articles/certification/program-requirements-edge-secured-core.md

@@ -1,7 +1,7 @@
 ---
 title: Edge Secured-core Certification Requirements
 description: Edge Secured-core Certification program requirements
-author: sufon
+author: sufenfong
 ms.author: sufon
 ms.topic: conceptual 
 ms.date: 02/20/2024
@@ -16,9 +16,9 @@ zone_pivot_groups: app-service-platform-windows-linux-sphere-rtos
 
 ## Windows IoT OS Support
 Edge Secured-core requires a version of Windows IoT that has at least five years of support from Microsoft remaining in its support lifecycle, at time of certification such as:
-* [Windows 10 IoT Enterprise Lifecycle](/lifecycle/products/windows-10-iot-enterprise)
 * [Windows 10 IoT Enterprise LTSC 2021 Lifecycle](/lifecycle/products/windows-10-iot-enterprise-ltsc-2021)
 * [Windows 11 IoT Enterprise Lifecycle](/lifecycle/products/windows-11-iot-enterprise)
+* [Windows 11 IoT Enterprise LTSC 2024](/windows/iot-enterprise/whats-new/windows-11-iot-enterprise-ltsc-2024)
 
 ## Windows IoT Hardware/Firmware Requirements
 > [!Note]

articles/service-health/overview.md

@@ -2,7 +2,7 @@
 title: What is Azure Service Health?
 description: Personalized information about how your Azure apps are affected by current and future Azure service problems and maintenance. 
 ms.topic: overview
-ms.date: 05/10/2019
+ms.date: 06/11/2024
 ---
 # What is Azure Service Health?
 
@@ -22,4 +22,4 @@ Together, these experiences provide you with a comprehensive view into the healt
 
 >[!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE2OgX6]
 
-[!INCLUDE [azure-lighthouse-supported-service](~/reusable-content/ce-skilling/azure/includes/azure-lighthouse-supported-service.md)]
+[!INCLUDE [azure-lighthouse-supported-service](~/reusable-content/ce-skilling/azure/includes/azure-lighthouse-supported-service.md)]

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md

@@ -35,7 +35,7 @@ Automatic OS upgrade has the following characteristics:
 
 An upgrade works by replacing the OS disk of a VM with a new disk created using the  image version. Any configured extensions and custom data scripts are run on the OS disk, while data disks are retained. To minimize the application downtime, upgrades take place in batches, with no more than 20% of the scale set upgrading at any time.
 
-You can integrate an Azure Load Balancer application health probe or [Application Health extension](virtual-machine-scale-sets-health-extension.md) to track the health of the application after an upgrade. We recommend incorporating an application heartbeat to validate upgrade success.
+You must integrate an Azure Load Balancer application health probe or [Application Health extension](virtual-machine-scale-sets-health-extension.md) to track the health of the application after an upgrade. This allows the platform to validate the VM health to ensure updates are applied in a safe manner. We recommend incorporating an application heartbeat to validate upgrade success.
 
 ### Availability-first Updates
 The availability-first model for platform orchestrated updates described below ensures that availability configurations in Azure are respected across multiple availability levels.