I worked through an internal contact to re-enable my Azure subscription for westus3 region for resource provider that provides Microsoft.Edge/disconnectedOperations. I was then able to successfully delete the resource in the Azure portal.
Failed to delete Microsoft.Edge/disconnectedOperations resource, no registered resource provider found for location 'westus3'
I have an Azure Local disconnected operations resource (Microsoft.Edge/disconnectedOperations) that was created during public preview with- https://learn.microsoft.com/en-us/azure/azure-local/manage/disconnected-operations-acquire
However, after GA, the region it was deployed to (westus3) is not valid, and the overview page doesn't even load. When I try to delete the resource, it fails with an API error. How can I clean up this resource?
Here is the error when trying to delete from the Azure Portal:
Delete Azure Local - disconnected operations resource.
There was some error while deleting Azure Local - disconnected operations resource: AlexALdoAppliance02
400: No registered resource provider found for location 'westus3' and API version '2026-04-01-preview' for type 'disconnectedOperations'. The supported api-versions are '2026-04-01-preview, 2026-03-15, 2026-03-01-preview'. The supported locations are 'eastus2, westeurope, uksouth, southeastasia, australiaeast'.
Azure Local
2 answers
Sort by: Most helpful
-
Alex Smith 1 Reputation point Microsoft Employee2026-08-13T17:49:55.2033333+00:00 -
Jerald Felix 18,680 Reputation points Volunteer Moderator2026-08-06T02:14:55.9533333+00:00 Hello Alex Smith,
Greetings! Thanks for raising this question in the Q&A forum.
The root cause here is not a resource provider registration problem, it is a region deprecation problem. When you created this Azure Local disconnected operations resource during public preview,
westus3was one of the accepted regions for theMicrosoft.Edge/disconnectedOperationsresource type. After the service reached general availability, Microsoft narrowed the list of supported regions for this resource type down toeastus2,westeurope,uksouth,southeastasia, andaustraliaeast. Your resource still physically exists withwestus3as its location value, but Azure Resource Manager now validates every operation against the current supported locations list for the resource type, including delete calls, so both the portal and the standard API version reject the request with theNoRegisteredProviderFounderror even though you are only trying to remove it.Since the note in Microsoft's own documentation confirms Azure CLI is not supported for this resource type and only the REST API or portal can be used, here is the path to try, in order.
Try deleting with an older preview API version
Attempt a generic resource delete using an API version that predates the GA region cutover, since ARM's location validation logic is sometimes tied to the API version's provider manifest rather than the current one. Run this from Azure CLI, which still supports generic ARM operations even though it doesn't support a dedicated
azcommand set for this resource type.az resource delete --ids /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Edge/disconnectedOperations/AlexALdoAppliance02 --api-version 2026-03-01-previewIf that fails with the same location error, try each of the other listed supported API versions in turn, and also try any earlier preview version you recall using at creation time (for example one dated before GA).
Try deleting the entire resource group
If the individual resource delete keeps failing, attempt to delete the resource group that contains this resource. Resource group deletion sometimes routes through a different cleanup path that is not blocked by the same per-resource location validation.
az group delete --name <resourceGroupName> --yes --no-waitOnly do this if the resource group contains nothing else you need to keep.
Escalate to Azure Support if both attempts fail
If neither approach clears the resource, this is a backend cleanup issue that needs the Azure Local / disconnected operations service team to force-delete the orphaned metadata record, since the region it lives in is no longer in the resource type's supported list under any client-facing API version. Open a new support request in the Azure portal:
- Issue type: Technical
- Service: Azure Local
- Problem type: Disconnected operations
- Problem subtype: Resource management / deletion
- In the ticket description, include:
-
-
- Resource name:
AlexALdoAppliance02- Resource type:
Microsoft.Edge/disconnectedOperations- Region:
westus3- The exact error text you posted, including the API version
2026-04-01-preview- A note that the resource was created during public preview before the GA region list was finalized
- The exact error text you posted, including the API version
- Region:
- Resource type:
-
Best Regards,
Jerald Felix.