Windows Admin Center for Azure Local - Registration warning

Question

Windows Admin Center for Azure Local - Registration warning

Pn 5

How can I resolve an issue with the following warning displayed at WAC?

User's image

Tried registering stack again using "-RepairRegistration" parameter. Everything seems registered correctly. Uninstalled WAC extensions, reinstalled multiple times and still getting the same error.

Now for the interesting part - if I hit "Refresh" the error goes away and I can complete setup. Tried with different user accounts and browsers and behavior is the same.

After the extension is installed and setup completed, the same warning persists but "Set up" changes to "Connect".

User's image

Refreshing this screen results in another warning:

User's image

And refreshing once more, the warning goes away. This happens every time when navigating to "Windows Admin Center" in azure portal for Azure Local cluster.

Don't see this behavior for individual nodes.

User's image

The actual connection works randomly. Sometimes throws an error saying it cannot connect, sometimes gets stuck in "Starting Windows Admin Center" and sporadically the connection goes through without issues. At the same time, Azure WAC connection to individual nodes of the cluster works as expected, every single time.

1 answer

Your answer

Answer 1

Alex Burlachenko 5,040

Hi Pn,
thank you for posting your question on the Microsoft Q&A platform the community is always happy to help.

Based on your description, the issue seems to stem from the registration process of Windows Admin Center (WAC) with Azure Stack HCI (Azure Local), particularly regarding Azure Arc integration. Although you've used the RepairRegistration parameter and reinstalled extensions, the warning persists, likely due to inconsistent or incomplete Arc registration, or a delay in status synchronization.

In simple terms, what's going on Azure Stack HCI requires a successful registration with Azure Arc. If that process isn’t fully completed or if the WAC interface doesn’t correctly reflect the current state, you’ll see a warning message. The fact that refreshing the page temporarily removes the warning suggests either session caching issues or delays in status propagation.

Check whether Azure Arc is truly enabled. Use PowerShell

Get-AzStackHCIArcSetting

or

Get-AzureStackHCI

Ensure that ConnectedToAzure is True.

Re-register the cluster using the latest Az.StackHCI module

Register-AzStackHCI -SubscriptionId <ID> -ResourceGroupName <Name> -Name <ClusterName> -Region <Region> -UseDeviceAuthentication

Update the PowerShell module

Update-Module -Name Az.StackHCI

Try configuring from the local instance of Windows Admin Center.

Some configuration steps especially initial Azure Arc setup may require using the local WAC portal. See https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/overview

Clear browser cache or try incognito mode. Since the issue disappears on refresh, this may be a browser-side caching issue.

Microsoft Docs of that issue Enable Azure Arc on Azure Stack HCI and Register-AzStackHCI PowerShell Reference and Troubleshoot Windows Admin Center in Azure and last on is Azure Stack HCI Registration Explained

If needed, you can also check the even viewer on your management node and review the WAC logs located at %ProgramData%\Windows Admin Center\Logs.

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer.
PSS That is my answer, but not a comment

Pn 5 Reputation points

2025-04-30T16:53:59.49+00:00

Hi Alex,

Updated the module, registered the stack again. Shows connected but the issue persists. Ruled-out browser issues too. Tried multiple browsers and devices with same result.

Now another question I have - Does WAC in Azure for Azure Local require a WAC installation on-prem to function?

My understanding was, that it should not but the documentation isn't clear. If I understand correctly, I should be able to deploy a stack, install WAC extension and it should work in Azure WAC without any local instances of WAC present. Am I wrong here?
Alex Burlachenko 5,040 Reputation points

2025-05-05T15:35:41.39+00:00
Hi Pn again, sorry for delay... Based on your screenshot showing +azure-local Connected status and your follow-up question, let me clarify the Windows Admin Center (WAC) architecture for Azure Stack HCI, and Your Understanding is Correct

No, you do not need an on-premises WAC gateway installation when using Azure-hosted Windows Admin Center to manage Azure Stack HCI. The proper deployment should work exactly as you described:

Deploy Azure Stack HCI cluster

Install the WAC extension on nodes (automatically handled during Azure Arc onboarding)

Manage directly through Azure Portal's WAC interface

Why You Might See Confusing Behavior

The persistent warning you're seeing (despite Connected status) could be caused by Extension Installation Gap. While the cluster shows connected, individual nodes might have incomplete WAC extension installation. Check with

Get-AzureStackHCINode | ForEach-Object { Write-Output "Checking $($_.Name)" Invoke-Command -ComputerName $_.Name -ScriptBlock { Get-WindowsFeature -Name WindowsAdminCenter | Where-Object Installed } }

Network Requirements. Azure-hosted WAC requires these endpoints accessible from your HCI cluster: https://*.windowsadmincenter.azure.com

TCP 443 outbound to Azure

Azure Arc connectivity endpoints

Registration Timing: There can be a 15-30 minute delay after registration before all components sync.

and I would recommended next

verify extension health on all nodes

Get-AzureStackHCINode | ForEach-Object { $extStatus = Get-AzConnectedMachineExtension -ResourceGroupName YourRG -MachineName $_.Name [PSCustomObject]@{ Node = $_.Name WACExtension = ($extStatus | Where-Object {$_.Name -eq 'WindowsAdminCenter'}).ProvisioningState } }

next check for hidden registration errors

Get-AzureStackHCI | Get-AzStackHCIRegistrationStatus -Debug

and consider full re-onboarding (if issues persist)

# Remove current registration Unregister-AzStackHCI # Full re-registration Register-AzStackHCI -SubscriptionId "..." -ResourceGroupName "..." -Region "..." -TenantId "..." -ComputerName "ClusterNode1" -RepairRegistration

and last one - the architecture you described is correct - Azure-hosted WAC should work without on-prem WAC installations when properly configured. The warning you're seeing likely indicates a component-level issue rather than architectural misunderstanding.

rgds,

Alex P.S. If my answer help to you, please Accept my answer PPS That is my Comment and not a Answer but if its helpful pls accept my answer :)))

Share via

Windows Admin Center for Azure Local - Registration warning

1 answer

Your answer