Merge pull request #3585 from MicrosoftDocs/main638792102709637546sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

azure-local/includes/hci-registration-azure-prerequisites.md

@@ -3,7 +3,7 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 03/20/2025
+ms.date: 04/02/2025
 ms.reviewer: alkohli
 ms.lastreviewed: 03/20/2025
 ---
@@ -22,7 +22,8 @@ ms.lastreviewed: 03/20/2025
    Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.KubernetesConfiguration" 
    Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ExtendedLocation" 
    Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ResourceConnector" 
-   Register-ResourceProviderIfRequired -ProviderNamespace "HybridContainerService" 
+   Register-ResourceProviderIfRequired -ProviderNamespace "HybridContainerService"
+   Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.Attestation"
    ```
 
     > [!NOTE]

azure-local/known-issues.md

@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
 description: Read about the known issues and fixed issues in Azure Local.
 author: alkohli
 ms.topic: conceptual
-ms.date: 03/31/2025
+ms.date: 04/01/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -39,6 +39,7 @@ The following table lists the fixed issues in this release:
 
 |Feature|Issue|Workaround/Comments|
 |------|------|----------|
+| Azure Local VMs | Intermittent failures or timeouts when creating or deleting Azure Local VMs due to internal service entering a deadlocked state. | You can now deploy Azure Local VMs without facing timeout issues. |
 | Azure Local VMs <!--ADO--> | Unable to delete a gallery image if the source Azure Local VM gallery image was created from, was deleted.| You can now delete a gallery image even if the source Azure Local VM the gallery image was created from, was deleted.|
 | Azure Local VMs <!--ADO--> | After Azure Arc resource bridge disaster recovery, some Azure Local VMs may lose network connectivity. | Updated Azure Arc resource bridge disaster recovery logic to ensure network configurations of Azure Local VMs persists. |
 | Azure Local VMs <!--ADO--> | Inaccurate power state reporting on Azure for Azure Local VMs when the source image for the VM is deleted from the cluster.  | Power operations shows consistent and accurate power state representation on Azure for Azure Local VMs with deleted source images.  |

azure-local/migrate/migration-options-overview.md

@@ -3,7 +3,7 @@ title: Options for migrating virtual machines to Azure Local (preview)
 description: Learn about how to choose a migration option to migrate VM workloads to your Azure Local (preview).
 author: alkohli
 ms.topic: overview
-ms.date: 11/13/2024
+ms.date: 04/02/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -51,11 +51,11 @@ Manual migration options are provided by Microsoft. These options are available
 
 The following manual migration options are available:
 
-- [Migrate VMs manually to same hardware](../deploy/migrate-cluster-same-hardware.md): This option is used when you want to migrate a Windows Server failover cluster to Azure Local using your existing hardware. This process installs the new operating system for Azure Local and retains your existing cluster settings and storage, and imports your VMs.
+- [Migrate VMs manually to same hardware](migrate-cluster-same-hardware.md): This option is used when you want to migrate a Windows Server failover cluster to Azure Local using your existing hardware. This process installs the new operating system for Azure Local and retains your existing cluster settings and storage, and imports your VMs.
 
-- [Migrate VMs manually to new hardware](../deploy/migrate-cluster-new-hardware.md): This option is used when you want to migrate VMs from an existing Windows Server 2016 or later cluster to a new Azure Local instance. You migrate the VMs to the same hardware using PowerShell and Robocopy.
+- [Migrate VMs manually to new hardware](migrate-cluster-new-hardware.md): This option is used when you want to migrate VMs from an existing Windows Server 2016 or later cluster to a new Azure Local instance. You migrate the VMs to the same hardware using PowerShell and Robocopy.
 
-    If you have VMs on Windows 2012 R2 or older that you want to migrate, see [Migrating older VMs](../deploy/migrate-cluster-new-hardware.md#migrating-older-vms).
+    If you have VMs on Windows 2012 R2 or older that you want to migrate, see [Migrating older VMs](migrate-cluster-new-hardware.md#migrating-older-vms).