Hi @Alain Osorio Rodriguez Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.
The Deny Assignment
is likely created by an Azure Deployment Stack which can be associated at the subscription level to manage and protect the resources. However, the Documentation states that, despite the deny-assignment setting, it's possible to delete the resource group. However, if a lock is active on any resource within the group, the delete operation fails. Look for Lock
under the settings of your Resource Group and see if there are any locks added to the resource group. If you see any, delete the lock and then try deleting the resource group.
If you still experience an issue with deleting the resource group, you can follow the steps provided in the article Delete the deployment stacks to remove the deny assignment enforcement.
If you run into any permissions issues deleting the deployment stack, please reach out to an Admin on the subscription and have that removed.
Hope this helps! Please let us know if you have any additional questions or need further assistance.
If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.