Azure Arc or Azure Stack HCI

Hello Sreedhar Poli, Thanks for follow-up

1. The deployment validation can fail if the DeviceManagementExtension VM switch state is out of sync. The validation tries to create a VM switch for network tests, which is deleted after tests. If the extension does not detect the deletion correctly, the validation fails.
2. Resource locks on the connected machines can block updates or deletions of extensions or underlying resources. The extension might be in a failed or outdated state requiring removal and reinstallation

Recommended Approach:

• Remove resource locks on nodes (look for DoNotDelete locks under Settings > Locks in Azure portal). Connect to nodes and remove any stray VM switches created by previous validation attempts

PS C:\> Get-VMSwitch

Refer document: https://learn.microsoft.com/en-us/powershell/module/hyper-v/get-vmswitch?view=windowsserver2025-ps

PS C:\> Remove-VMSwitch

Refer document: https://learn.microsoft.com/en-us/powershell/module/hyper-v/remove-vmswitch?view=windowsserver2025-ps

• Remove the validation error and resync by deleting and re-adding the edge device resource using PowerShell or portal. Restart the deployment validation in the Azure portal after cleaning up. Recreate the DoNotDelete locks once the validation succeeds.

Refer document: Troubleshoot deployment validation issues in Azure Local, version 23H2 via Azure portal - Azure Loc…

• If stuck, remove the Device Management Extension on nodes and manually reinstall/extensions. Remove:

Remove-AzConnectedMachineExtension -Name "AzureEdgeDeviceManagement" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME

Re-install:

New-AzConnectedMachineExtension -Name "AzureEdgeDeviceManagement" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.Edge" -ExtensionType "DeviceManagementExtension"

These steps address common validation failures from Device Management extension discrepancies and resource locking issues.

I hope this helps do let me know if you have any questions on this.

I’ve successfully installed all required extensions across our Arc-connected hosts, including AzureEdgeTelemetryAndDiagnostics. The provisioning state shows Succeeded, and the extension version is 2.0.30.0.

However, Azure Local validation continues to fail for hosts xxxxxxxxxx.

One consistent observation:

Immediately after installing the extension, the AzureEdgeMonitoringPlatform service shows as running.

But after a short time, it transitions to not running, even though other services like FleetDiagnosticsAgent, MonAgentHost, and AzureStack Observability Agent remain active.

I’ve tested multiple reinstall cycles (2–3 times), and the behavior persists. This intermittent failure of AzureEdgeMonitoringPlatform may be the root cause of validation failure.

Extension ID: /subscriptions/xxxxxxxxxxxx/resourceGroups/xxxxxxxxxx-rg/providers/Microsoft.HybridCompute/machines/xxxxxxx-

/extensions/AzureEdgeTelemetryAndDiagnostics

Could you help investigate why AzureEdgeMonitoringPlatform service fails to persist and whether additional permissions, dependencies, or telemetry configurations are required to stabilize it?

I’ve followed all documented test cases and deployment steps but haven’t succeeded in resolving this.

Errors while validating the hosts from azure local
Still hosts validations failing with errors.
Could not complete the operation. 200: Could not retrieve Microsoft.AzureStackHCI.ServiceCommon.Models.HybridComputeExtension resource, resourceId: /subscriptions/xxxxxxxxx/resourceGroups/xxxxxxxxxx/providers/Microsoft.HybridCompute/machines/sxxxxxxxxx/extensions/AzureEdgeTelemetryAndDiagnostics.

Assign required roles to install extensions.

Failed to assign install extension permissions. Error:

Hello Sreedhar Poli,

The issue with the AzureEdgeMonitoringPlatform service intermittently stopping and the Azure Local host validation failing due to errors related to the AzureEdgeTelemetryAndDiagnostics extension likely stems from either permission issues, dependency failures, or corrupted extension state.

Permissions for Extension Installation

• The error Failed to assign install extension permissions suggests the Azure Active Directory principal (user or service principal) used to deploy the extension lacks the required IAM roles.
• The deployer must have Contributor role on the subscription or resource group.
• Additionally, assign the built-in role Azure Stack HCI Device Administrator or equivalent custom roles that grant access to manage Hybrid Compute machine extensions.

Service Dependencies and Stability of AzureEdgeMonitoringPlatform

• This service depends on underlying infrastructure components and network access to Azure endpoints. Check for any network, proxy, firewall, or DNS blocking issues that could cause the service to stop.

Review the event logs and Azure diagnostic logs on the host in the directory %programdata%\mochostagent\logs for failures.

• Restart the mochostagent service as it hosts Azure Edge telemetry:

    text
    Restart-Service mochostagent
  

Extension State and Validation Errors

• The combined issues with extension installation and validation may require removing the failed extension from the Arc-connected machine, cleaning up state, and reinstalling.
• Follow steps in Azure Arc extension management on Azure Stack HCI for managing, removing, and reinstalling extensions.

https://docs.azure.cn/en-us/azure-local/manage/arc-extension-management?tabs=azureportal

• Also check the cluster and node readiness in Azure Local if out of sync, repairs or node reimaging might be required

I hope this helps do let me know if you have any questions on this.

Hello Sreedhar Poli, just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. 

Hello Sreedhar Poli, following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.