Share via

We deleted our Azure Local 24H2 resource bridge vm

CDA 20 Reputation points
2026-04-22T13:08:52.8266667+00:00

Our arc resource bridge, custom location, and arc-bridge vm were deleted. There was an issue with the vm that was causing it to exhaust memory, and after troubleshooting we decided to delete the vm and redeploy it. Unfortunately, we are running Azure Local 24H2 and the docs we were following were for 22H2 and earlier. We did not realize how integrated that vm was as the information we found suggested performing this deletion and redeploy, but I guess that is not a documented process for this build. We do have the previous resource id, custom location, and other useful information available, so before I open a ticket with support I figured I would check here if to see if this issue has been addressed before with a workable solution.

Azure Local

Answer accepted by question author

  1. Q&A Assist
    2026-04-22T13:09:13.38+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    For Azure Local 24H2, Azure Arc resource bridge is a critical, tightly integrated component and must not be deleted or redeployed without direct guidance from Microsoft. The documented self-service recovery and redeployment procedures in the public docs apply to Arc-enabled VMware and Arc-enabled SCVMM, not to Azure Local.

    The Azure Local guidance is explicit:

    • Arc resource bridge is a critical component of Azure Local and should not be deleted without guidance from Microsoft Support.
    • For Azure Local, recovery of the Arc resource bridge must be done only with Microsoft Support involvement because incorrect actions can cause irrecoverable damage to the Azure Local environment.

    In the specific scenarios described in the documentation:

    • If the Azure Arc resource bridge is removed only from the Azure portal (Azure projection deleted, on-premises appliance VM still present), it can be restored with az arcappliance create using the existing on-premises appliance VM.
    • If the on-premises appliance VM itself is deleted, the ability to manage VMs from Azure is lost, but workloads continue to run locally. In that case, the documented path is to redeploy the Arc resource bridge with assistance from Microsoft Support.

    In this situation, both the Azure Arc resource bridge resource and the underlying VM have been deleted in an Azure Local 24H2 environment. That matches the disaster scenario where self-service recovery is not documented or supported. Even though the previous resource IDs and custom location details are available, the guidance is to:

    1. Do not attempt to recreate or redeploy the Arc resource bridge or custom location independently using VMware/SCVMM-style disaster recovery scripts or procedures; those are not applicable to Azure Local.
    2. Open a support ticket with Microsoft Support for Azure Local and provide:
      • Confirmation that the Azure Local version is 24H2.
      • Details of what was deleted (Arc resource bridge Azure resource, custom location, and the Arc bridge VM).
      • Any saved resource IDs and configuration information.
    3. Follow the recovery steps provided by Microsoft Support only; do not delete or recreate additional Azure Local components (such as the custom location) unless explicitly instructed, as this can cause irrecoverable damage.

    Until the Arc resource bridge is restored, existing workloads should remain accessible and manageable through local tools (for example, Hyper-V, Windows Admin Center, and PowerShell), but Azure-based management and lifecycle operations will be unavailable.

    References:

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ankit Yadav 14,165 Reputation points Microsoft External Staff Moderator
    2026-04-22T14:44:47.93+00:00

    Hello CDA,

    For Azure Local 24H2, the Azure Arc resource bridge and its appliance virtual machine are treated as core, tightly integrated components of the Azure Local platform. They enable the projection and management of Azure Local virtual machines from Azure and are not designed to be independently deleted and redeployed in the same manner as Arc-enabled VMware vSphere or Arc-enabled System Center Virtual Machine Manager (SCVMM).

    In Azure Local, we support the following behaviors and recovery expectations:

    • If only the Azure-side resources were deleted (for example, the Azure Arc resource bridge or custom location in Azure), and the on-premises resource bridge appliance VM is still present and operational, the Azure projection can be restored by reconnecting to the existing appliance using the same resource identifiers.
    • If the on-premises resource bridge appliance VM itself was deleted, Azure Local workloads continue to run locally, but Azure-based management through Azure Arc is lost. At this point, we do not offer a supported self-service procedure to independently recreate the appliance VM and safely reattach it to an existing Azure Local instance.

    The recovery procedures and disaster recovery scripts documented for Arc-enabled VMware vSphere and Arc-enabled SCVMM are platform-specific and are not supported for Azure Local. Applying those procedures to Azure Local environments is not supported and can lead to further inconsistencies.

    This scenario is not a known Azure Local 24H2 service incident. Instead, it falls under a recovery situation where the supported path is to work directly with Microsoft to ensure the Azure Local environment is brought back to a supported and consistent state.

    References:

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.