Azure Local 2610: Microsoft.AzureStackHCI networkProfiles reconciliation fails with NoRegisteredProviderFound due to API version mismatch

Gopi Rayachoti 0 Reputation points
2026-11-11T07:10:57.4066667+00:00

Hello Microsoft Azure Local Community,

I am experiencing repeated failures while the Microsoft.AzureStackHCI Resource Provider attempts to create or update the default network profile for my Azure Local 2610 cluster.

The cluster is operational, but Azure Activity Logs show recurring network profile provisioning failures approximately every 10 minutes.

Environment

Product: Azure Local

Version: 2610

Deployment: Three-node cluster

Azure region: Central India

Resource provider: Microsoft.AzureStackHCI

Resource type: clusters/networkProfiles

Affected resource: clusters/<cluster-name>/networkProfiles/default

Error details

Azure Activity Logs consistently show the following error:

Error Code: NoRegisteredProviderFound

No registered resource provider found for location
'centralindia' and API version '2026-03-15-preview'
for type 'clusters/networkProfiles'.

The supported api-versions are '2026-11-01-preview'.

The failing operations are initiated by Microsoft.AzureStackHCI Resource Provider, not by a manual ARM deployment.

Troubleshooting performed

1. Verified resource provider registration

Using Azure CLI:

az provider show \
  --namespace Microsoft.AzureStackHCI \
  --query "{registrationState:registrationState,networkProfiles:resourceTypes[?resourceType=='clusters/networkProfiles'].{resourceType:resourceType,apiVersions:apiVersions,locations:locations}}" \
  -o json

Result:

RegistrationState: Registered
Resource type: clusters/networkProfiles
Supported API: 2026-11-01-preview
Central India: Supported

2. Verified the supported REST API version

A GET request to the networkProfiles collection using 2026-11-01-preview succeeds but returns:

{
  "value": []
}

3. Checked the default network profile

A GET request for networkProfiles/default with the supported API returns:

ResourceNotFound

4. Reviewed Azure Activity Logs

The service repeatedly attempts to create or update the resource using 2026-03-15-preview and fails with NoRegisteredProviderFound.

These failures continue approximately every 10 minutes.

Question for the community

How can the API version used by the Azure Local network-profile reconciliation process be corrected from 2026-03-15-preview to the supported 2026-11-01-preview?

Specifically, is this a known issue with Azure Local 2610 or a resource-provider version rollout mismatch?

Is there a supported customer-side method to trigger reconciliation and automatically create the missing default network profile, or does this require a Microsoft backend correction?

I would prefer to avoid manually creating the network profile, modifying unsupported internal resources, or rebuilding the cluster.

Any guidance from Microsoft Azure Local engineers, MVPs, or community members who have encountered this issue would be appreciated.

Thank you.

Azure Local
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-11-11T07:12:12.09+00:00

    The API version used by this Microsoft-initiated reconciliation cannot be changed through a documented customer setting; open an Azure Local support case for Microsoft to correct or complete the resource-provider rollout, and do not manually create the default profile.

    What the evidence establishes

    • Microsoft.AzureStackHCI/clusters/networkProfiles is currently documented only with API version 2026-11-01-preview; 2026-03-15-preview is not listed for that child resource type.^1^
    • NoRegisteredProviderFound can mean that the API version is unsupported—not only that the provider is unregistered.^2^
    • Your successful request with 2026-11-01-preview, combined with the provider metadata showing Central India support, has already excluded the normal registration, location, and client-selected API-version remedies.
    • The published Azure Local 2610 release notes do not list this networkProfiles reconciliation failure as a known issue. They currently state that there are no known issues specific to this release.^3^

    This therefore fits an undocumented Azure Local control-plane/resource-provider rollout mismatch, but only Microsoft can confirm the backend state. The recurring operation is owned by the Azure Local cloud service’s ARM resource provider, not by your template or CLI client.^4^

    Open the support case with actionable evidence

    1. In the Azure portal, open Help + support → Create a support request.
    2. Select:
      • Issue type: Technical
      • Service: Azure Local
      • Subscription/resource: The affected cluster
      • The closest available management, deployment, or network-control-plane problem category.
    3. Use a summary such as:

      Azure Local 2610 service reconciliation uses unsupported API 2026-03-15-preview for Microsoft.AzureStackHCI/clusters/networkProfiles in Central India; only 2026-11-01-preview is advertised.

      Selecting the affected subscription and the closest matching service helps route the case correctly.^5^
    4. Include:
      • Cluster solution version and OS build.
      • Resource ID of the cluster.
      • Region: centralindia.
      • Several failed operation timestamps and Activity Log correlation IDs.
      • Caller/initiator showing Microsoft.AzureStackHCI Resource Provider.
      • The complete error showing requested and supported API versions.
      • Output proving the provider is registered and the resource type advertises 2026-11-01-preview.
      • Results showing the supported collection GET succeeds while default is absent.
      • Approximate ten-minute recurrence interval.

    Ask Support to verify:

    • The Azure Local RP deployment/ring serving the subscription and Central India.
    • Whether the reconciliation component is pinned to stale API version 2026-03-15-preview.
    • Whether backend reconciliation can be replayed after correcting that version.
    • Whether the missing default profile is expected to be service-created for this cluster configuration.

    Upload diagnostics

    From the Azure Local resource, go to Settings → Diagnostics and Remote Support → Send logs. Select a narrow interval containing several reconciliation attempts, then choose Collect and upload logs. Open the completed entry under Log activity and give Support its Correlation ID and log details. This requires the Azure Stack HCI Administrator role and the AzureEdgeTelemetryAndDiagnostics extension.^6^

    Alternatively, from any cluster node:

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

Send-DiagnosticData `
  -FromDate $from `
  -ToDate $to

    Provide Support with the resulting AEORegion, AEODeviceARMResourceUri, AEOClusterNodeArcResourceUri, and CorrelationId.^6^

    There is no published customer-side command in the available Azure Local 2610 documentation to change this service reconciliation API version or force creation of this specific profile. Manually creating it would also not correct the reconciler’s continued calls to the unsupported version, so avoiding that workaround and a cluster rebuild is appropriate.

    References

    1. Azure Resource Manager template reference for Microsoft.AzureStackHCI ...
    2. Resolve errors for resource provider registration
    3. Release notes with fixed and known issues in Azure Local - Azure Local ...
    4. Hybrid capabilities with Azure services in Azure Local
    5. Create an Azure support request
    6. Collect diagnostic logs for Azure Local
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.