We have an orphaned Microsoft.Web/staticSites resource.

Pavitra Rupani (admin) 20 Reputation points
2026-08-11T01:11:22.7433333+00:00

The resource remains visible in Azure Portal and ARM inventory, but deletion through both Azure Portal and Azure CLI fails with the same NotFound error.

ARM inventory: az resource list shows the resource with provisioning state Succeeded.

Provider GET: az resource show returns: (NotFound) Cannot find StaticWebApp with name swa-ets-compass-prod.

Provider DELETE: az resource delete --ids <resource-id> returns: (NotFound) Cannot find StaticWebApp with name swa-ets-compass-prod.

Please remove/reconcile the orphaned ARM resource record for this Static Web App.

edited PII

Azure Static Web Apps
Azure Static Web Apps

An Azure service that provides streamlined full-stack web app development.


Answer accepted by question author
Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator
2026-08-12T23:02:54.2166667+00:00

Hi @Pavitra Rupani (admin)

As discussed and confirmed offline with the customer, the Azure Static Web App has now been successfully deleted. The behavior appears to have been caused by a propagation delay, and the stale reference has since been cleared. Since the requested action has been completed and no further assistance is required at this time, we will proceed with the closure of this support case.

Thank you for working with Microsoft Support. If you have any further questions or encounter any issues in the future, please feel free to reach out to us.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Allan Solomon Mejia 8,420 Reputation points
    2026-08-11T01:33:15.3566667+00:00

    Hello @Pavitra Rupani (admin)

    Based on the behavior you've documented, this does look like an orphaned/stale ARM resource record rather than a normal Static Web App deletion problem.

    The key inconsistency is:

    az resource list → resource exists / provisioningState: Succeeded

    Provider GET → NotFound: Cannot find StaticWebApp

    Provider DELETE → NotFound: Cannot find StaticWebApp

    The documented Microsoft.Web/staticSites DELETE operation should return 200 OK or 202 Accepted when the provider can locate and delete the resource.

    As one final check, you could try the resource-specific CLI command rather than the generic az resource delete:

    az staticwebapp delete \
      --name swa-ets-compass-prod \
      --resource-group rg-compass \
      --yes
    

    Microsoft documents az staticwebapp delete as the supported Azure CLI operation for deleting a Static Web App.

    However, if that also returns:

    NotFound: Cannot find StaticWebApp with name swa-ets-compass-prod

    I wouldn't recommend trying to manipulate the ARM record manually. The resource provider apparently no longer has the underlying Static Web App while ARM inventory still retains the resource.

    Similar orphaned Microsoft.Web resources have required Microsoft backend cleanup/reconciliation when normal deletion couldn't reach the underlying resource.

    =============================================================================

    Microsoft Moderator Gursimran Singh: Could you please help escalate this to the Azure Static Web Apps / Microsoft.Web resource provider team to reconcile or remove the orphaned ARM record? The control-plane inventory reports the resource as Succeeded, while both provider GET and DELETE return NotFound.

    =============================================================================

    Pavitra, keep the full resource ID, failed request/correlation ID, UTC timestamp, and CLI debug output available for the support engineer. Since the screenshot includes your Subscription ID, I'd also recommend redacting it from any additional public posts.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    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.