Azure Local arc bridge status offline

If the Azure Local instance runs version 23H2 or later, restart the Arc Resource Bridge appliance VM once; if it remains offline, run the Azure Local Support Tool locally, collect diagnostics, and open a Microsoft Support case rather than rebuilding or manually repairing the bridge.^1^

1. Restart the appliance once

Because basic network connectivity has already been checked, move to the appliance health path:

1. Confirm the Azure Local version is 23H2 or later.
2. Locate the Arc Resource Bridge appliance VM in Windows Admin Center or Failover Cluster Manager.
3. Confirm whether it is stopped, failed, or running.
4. Perform one graceful restart.
5. Allow the bridge to initialize, then check its status in the Azure portal.

A running VM does not necessarily mean that its appliance services are healthy. If it returns offline, repeatedly restarts, or its console shows emergency mode or mount failures, stop there rather than attempting Linux or filesystem repairs.^2^

2. Run the supported Azure Local remediation tool

For Azure Local 2311.2 or later, run the Support Tool directly on a client connected to Azure Local. Do not run these commands through a remote PowerShell session.^3^

Start with diagnostics:

Test-SupportAksArcKnownIssues

If the test reports known issues, run the supported remediation and retest:

Invoke-SupportAksArcRemediation

Test-SupportAksArcKnownIssues

The expected result is that the checks return Passed and the bridge heartbeat returns online. The tool specifically covers Azure Local infrastructure conditions where the Arc Resource Bridge is offline.

If the system is older than 2311.2, do not use this remediation branch; proceed to log collection and Support.

3. Collect diagnostics if it stays offline

If portal-based collection is available:

1. Azure portal → Azure Local instance.
2. Under Settings, select Diagnostics and Remote Support.
3. Select Send logs.
4. Choose a narrow interval covering the restart and failed reconnection.
5. Select Collect and upload logs.
6. Record the resulting Correlation ID for the support case.

This requires the Azure Stack HCI Administrator role and the AzureEdgeTelemetryAndDiagnostics extension. The feature is currently in preview.^4^

Alternatively, from an Azure Local node:

$from = (Get-Date).AddHours(-2)
$to   = Get-Date

Send-DiagnosticData -FromDate $from -ToDate $to
Get-LogCollectionHistory

If collection cannot reach the appliance, include that failure in the case. It can indicate that the management path to the appliance VM is unavailable even when general node-to-Azure connectivity works.

Important recovery boundaries

Do not:

• Delete and redeploy the appliance VM.
• Delete the Azure Arc Resource Bridge resource.
• Run filesystem repair inside the Linux appliance.
• Restore the appliance from a VM snapshot or backup.
• Manually upgrade it with az arcappliance.

For Azure Local, the bridge is an integrated critical component. Recovery must be performed with Microsoft Support guidance; deleting or independently recovering it can cause irrecoverable damage or leave existing resources without their original management state.^5^

Also escalate promptly if the bridge has been offline for close to 45 days. Beyond 45 days, its appliance security key might no longer be valid or refreshable.^1^

References

1. Troubleshoot Azure Arc resource bridge issues
2. Azure Local Warning: Arc Resource Bridge is offline - Microsoft Q&A
3. Use the Support tool to troubleshoot and fix Azure Local infrastructure problems
4. Collect diagnostic logs for Azure Local
5. Azure Arc resource bridge maintenance