Deployment Stack failed to be deleted.

Hello JSevillano,

When you are trying to delete a deployment stack created at subscription scope level, first delete the resource groups or resources existed in it through portal or any other script.

And if a lock is active on any resource within the group, the delete operation fails.

To allow the delete resource operations in the stack, make sure that the DenySettingsMode is set to None and delete it accordingly. because, DenySettingsMode defines the operations that are prohibited on the managed resources to safeguard against unauthorized security principals attempting to delete.

So, check the deny settings at the subscription scope, if the settings set as below make it None.

New-AzSubscriptionDeploymentStack `
  -Name "<deployment-stack-name>" `
  -Location "<location>" `
  -TemplateFile "<bicep-file-name>" `
  -ActionOnUnmanage "detachAll" `
  -DenySettingsMode "denyDelete" `
  -DenySettingsExcludedAction "Microsoft.Compute/virtualMachines/write Microsoft.StorageAccounts/delete" `
  -DenySettingsExcludedPrincipal "<object-id>,<object-id>"

as said, ensure to set the Deny setting and ActionOnUnmanage as below

-DenySettingsMode "none" ` 
-ActionOnUnmanage "deleteAll"

And to delete the deployment stack at subscription level, you need to use az stack sub delete AZCLI command as detailed in below MS Doc. Link: https://learn.microsoft.com/en-us/cli/azure/stack/sub?view=azure-cli-latest#az-stack-sub-delete

If still the issue persists and to apply force delete on the deployment stack deletion operation, there is a relevant Az PowerShell command called Remove-AzSubscriptionDeploymentStack with stack name and force arguments.

MS Doc: https://learn.microsoft.com/en-us/powershell/module/az.resources/remove-azsubscriptiondeploymentstack?view=azps-13.0.0#examples

If the command helpful, please click Upvote it.

Thanks

Hi,

I ran this command:

az stack mg delete --id /providers/Microsoft.Management/managementGroups/58b16003-1ebb-4e2c-97a5-13b63f56a93b/providers/Microsoft.Resources/deploymentStacks/cs-managementgroup-stack --management-group-id 58b16003-1ebb-4e2c-97a5-13b63f56a93b --action-on-unmanage deleteAll --bypass-stack-out-of-sync-error

After a long time running, we got this error:

(DeploymentStackDeleteResourcesFailed) One or more resources could not be deleted. Correlation id: '5f5bf6a2-26cf-4afb-90d5-7bc2fa227df4'.

Code: DeploymentStackDeleteResourcesFailed

Message: One or more resources could not be deleted. Correlation id: '5f5bf6a2-26cf-4afb-90d5-7bc2fa227df4'.

Exception Details: (DeploymentStackDeleteResourcesFailed) An error occurred while deleting resources. These resources are still present in the stack but can be deleted manually. Please see the FailedResources property for specific error information. Deletion failures that are known limitations are documented here: https://aka.ms/DeploymentStacksKnownLimitations

    Code: DeploymentStackDeleteResourcesFailed

    Message: An error occurred while deleting resources. These resources are still present in the stack but can be deleted manually. Please see the FailedResources property for specific error information. Deletion failures that are known limitations are documented here: https://aka.ms/DeploymentStacksKnownLimitations

Is ther a way to delete manually the resources that are still present in the stack?