Azure Local 24H2 - Microsoft.Edge.DeviceManagementExtension won't deploy

Question

Hey All -

We're trying to build a fresh 24H2 - AzureLocal24H2.26100.1742.LCM.12.2504.0.3142.x64.en-us - cluster (we actually had to reload our 23H2 cluster because the storage broke majorly) and now the 24H2 cluster won't deploy successfully.

Basically, after running:
Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud “AzureCloud” -ArmAccessToken $ARMtoken -AccountID $id

No extensions show up on the servers.

This page gave some commands to deploy the extensions manually:
https://learn.microsoft.com/en-us/azure/azure-local/known-issues?view=azloc-2504

$Settings = @{ "CloudName" = $Cloud; "RegionName" = $Region; "DeviceType" = "AzureEdge" }
New-AzConnectedMachineExtension -Name "AzureEdgeTelemetryAndDiagnostics" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Observability" -Settings $Settings -ExtensionType "TelemetryAndDiagnostics" -EnableAutomaticUpgrade
New-AzConnectedMachineExtension -Name "AzureEdgeDeviceManagement" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.Edge" -ExtensionType "DeviceManagementExtension"
New-AzConnectedMachineExtension -Name "AzureEdgeLifecycleManager" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Orchestration" -ExtensionType "LcmController"
New-AzConnectedMachineExtension -Name "AzureEdgeRemoteSupport" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Observability" -ExtensionType "EdgeRemoteSupport" -EnableAutomaticUpgrade

I am having issues with the "AzureEdgeDeviceManagement" extension, however.

It gave me the following error when trying to deploy that extension. The other 4 are working fine. Has anyone else seen this issue and is there a fix? I'm really trying to not open our 3rd ticket in 5 months on Azure Local...

New-AzConnectedMachineExtension : Extension returned non-zero exit code for Install: 1. Extension error output: std error: .  Extension Message: Failed to install the Device Management Extension probably because the Resource Provider (Microsoft.AzureStackHCI) is not yet registered in the subscription. Error Details = {"status":"Failed","error":{"code":"InternalHttpClientError","message":"Could not make the dp call with inner error = ","target":"https://dp.stackhci.azure.com/centralus/edgeDevices?api-version=2024-12-01-preview","details":[{"code":"InternalServerError","message":"Endpoint not found for put edge devices call, endpoint = https://dp.stackhci.azure.com/centralus/edgeDevices?api-version=2024-12-01-preview with details = "}]}} Extension Error: Status   Name               DisplayName ------   ----               ----------- Stopped  DeviceManagemen... DeviceManagementService 2025-05-01 19:34:06Z : INFO : Install-Extension.ps1 : Failed to install the Device Management Extension probably because the RP is not yet registered 2025-05-01 19:34:06Z : INFO : ReportStatus.ps1: Name: Install-Extension, Operation: Failed to install the Device Management Extension probably because the Resource Provider (Microsoft.AzureStackHCI) is not yet registered in the subscription, Status: error, Code: 500, Message: Failed to install the Device Management Extension probably because the Resource Provider (Microsoft.AzureStackHCI) is not yet registered in the subscription. Error Details = {"status":"Failed","error":{"code":"InternalHttpClientError","message":"Could not make the dp call with inner error = ","target":"https://dp.stackhci.azure.com/centralus/edgeDevices?api-version=2024-12-01-preview","details":[{"code":"InternalServerError","message":"Endpoint not found for put edge devices call, endpoint = https://dp.stackhci.azure.com/centralus/edgeDevices?api-version=2024-12-01-preview with details = "}]}} 2025-05-01 19:34:06Z : INFO : ReportStatus.ps1 : Attempt #1 : Writing to status file at C:\Packages\Plugins\Microsoft.Edge.DeviceManagementExtension\1.2504.0.3002\status\0.status

And, yes, before anyone asks, I checked that the Microsoft.AzureStackHCI provider is registered on the subscription (like it says).

Thank you.

Answer 1

Vaughn DeFouw,

Sorry for the delayed response! Thank you for your patience and understanding!

You're running into a known issue with Azure Local 24H2 (build 26100.1742) where the AzureEdgeDeviceManagement extension fails to install due to a bad or uninitialized DP (Data Plane) endpoint for the Microsoft.AzureStackHCI resource provider (RP), even though the RP itself is already registered.

The key error is:

Endpoint not found for put edge devices call, endpoint = https://dp.stackhci.azure.com/centralus/edgeDevices?api-version=2024-12-01-preview

This typically means the Resource Provider's data plane endpoint isn’t fully provisioned or not yet responding as expected.

The data plane endpoint (https://dp.stackhci.azure.com/centralus/edgeDevices) is used by the DeviceManagementExtension to perform registration and lifecycle operations. The error you're getting is from an internal HTTP client within the extension that fails to reach a valid endpoint.

This suggests one of the following:

• The DP endpoint for your region (centralus) is misconfigured or not yet live for the 24H2 build.
• The required internal setup for HCI Arc-enabled devices has not fully completed, even if the RP is registered.

Try the following ordered steps:

1. Double-check RP status and available features. Ensure you see Registered, and inspect the ResourceTypes list for: clusters, edgeDevices,provisioningRequests.

If edgeDevices is not listed, the backend rollout may not be complete in your region.

2. Re-register the RP (forces re-init of DP endpoints)

3 Test another region to check if the issue is region specific:https://learn.microsoft.com/en-us/azure/azure-local/deploy/deployment-arc-register-server-permissions?view=azloc-2504&tabs=powershell
https://learn.microsoft.com/en-us/azure/azure-local/concepts/system-requirements-23h2?view=azloc-2504&tabs=azure-public#azure-requirements

Similar scenario: https://github.com/microsoft/azure_arc/issues/2705 where one user stated when he moved the deployment to different region resolved this issue!

Hope it helps!

Let me know if you have any further queries!

If the comment is helpful, please click "upvote" to let us know!