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, westus3 was one of the accepted regions for the Microsoft.Edge/disconnectedOperations resource type. After the service reached general availability, Microsoft narrowed the list of supported regions for this resource type down to eastus2, westeurope, uksouth, southeastasia, and australiaeast. Your resource still physically exists with westus3 as 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 the NoRegisteredProviderFound error 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 az command set for this resource type.
az resource delete --ids /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Edge/disconnectedOperations/AlexALdoAppliance02 --api-version 2026-03-01-preview
If 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-wait
Only 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.