How can I delete an Azure Sphere that I have verified I'm the owner of (conventional "Delete" not working)?

Matthew Huntley Greetings! Could you confirm how exactly are you deleting the catalog? Using portal or CLI? I understand that you have already performed a basic troubleshooting steps and checked on the locks.

Could you also confirm if you have required access to delete a resources?

You can check if you have the required permissions by following these steps:

• In the Azure portal, navigate to the Azure Sphere Catalog resource you want to delete.
• Click on the "Access control (IAM)" tab in the left-hand menu.
• Check if you have the "Owner" or "Contributor" role assigned to your account.

See Azure Sphere pre-built RBAC roles and resource hierarchy for more details.

If not tried, use the below CLI command and let me know if that resolves. az sphere catalog delete --catalog MyCatalog --resource-group MyResourceGroup

If you have confirmed that you have the appropriate permissions and there are no locks on the resource group, but you are still unable to delete the Azure Sphere Catalog resource, it is possible that there may be an issue with the resource itself.

Hi AshokPeddakotla-MSFT, Thanks for your feedback. I've attempted to delete the resource by way of both the Portal and CLI, and in both instances, I receive the message, "The user is not authorized to delete the Catalog (Code: Unauthorized)."

I confirmed that I am the Owner of the resource, and my colleague, who's also an owner and the Azure Tenant Admin, cannot delete the resource either.I'm wondering if it has anything to do with the resource being in "preview" mode:

Hi AshokPeddakotla-MSFT, Thanks for your feedback. I attempted to delete the resource by way of the Portal and CLI, but in both instance, I get the same error message: "The user is not authorized to delete the Catalog (Code: Unauthorized)." I confirmed that I am the Owner of the resource, and I even had my colleague, who's also an Owner and the Azure Tenant Admin, attempt to delete it, but the same message appears. I'm wondering if has anything to do with the resource being in "Preview" mode:

I will keep looking into this, but any additional insight would be appreciated. Best regards,
Matthew