Azure VMware Solution: Deployed private cloud not visible in portal — Investigation of visibility issues

This is a tricky one, but the symptoms you describe line up with a known class of issues in Azure VMware Solution (AVS) where the resource exists and is queryable via CLI/ARM but doesn’t render in the portal UI.

Here are the most common causes and next steps:

Why it happens Portal UX lag or schema mismatch: The Azure portal relies on resource providers and UI schemas. If the AVS resource provider (Microsoft.AVS) hasn’t fully registered or the portal UI hasn’t been updated for your region (Australia Southeast), the resource can exist but not display.

Disabled internet access: Since you deployed with internet access disabled, some portal blades/features may not load metadata correctly, even though the CLI can still query ARM.

Subscription/resource provider registration: Even if you checked permissions, sometimes the Microsoft.AVS provider isn’t fully registered in the subscription, which blocks portal rendering.

Portal filtering: The AVS private cloud won’t appear under “VMware” unless you explicitly search for “Azure VMware Solution” or navigate via All resources. If you’re filtering by resource type or location, it can vanish from view.

Steps to resolve Confirm provider registration
Run:

bash az provider show --namespace Microsoft.AVS --query "registrationState" If not Registered, run:

bash az provider register --namespace Microsoft.AVS Check resource type visibility
In the portal, go to All resources → clear filters (subscription, resource type, location). Search for the private cloud name directly.

Verify region support in portal
Australia Southeast is supported, but portal UI rollouts can lag. Try switching to the Preview portal (https://preview.portal.azure.com) to see if the resource appears there.

Cross-check with Resource Explorer
In the portal, open Resource Explorer (search in portal). Navigate to subscriptions/{id}/providers/Microsoft.AVS/privateClouds to confirm the object exists. If it shows here but not in the resource list, it’s a portal rendering issue.

Raise a support ticket
If CLI confirms existence and Resource Explorer shows the resource, but the portal still hides it, this is a Microsoft-side portal bug. Open a support request with Azure Support referencing the deployment ID and CLI evidence.

Quick workaround: Until the portal UI catches up, you can manage AVS entirely via CLI/PowerShell/Terraform. The portal visibility issue doesn’t affect the actual functionality of the private cloud.

Hello **sachin-0048

Please informed that this is the expected result for Australia Southeast List of Azure regions | Microsoft Learn

Australia southeast doesn't support availability zones.