Unable to delete container instances

Question

Unable to delete container instances

Ilham Izzuddin 20

Hi guys,i have an issue with ACI cannot be deleted.Already tried with Portal,bash and RestAPI currently stuck with 2 ACI. anyone from microsoft can help to remove it from backend.thx

Error: Encountered an internal server error. The

tracking activity id is ********, correlation id is '$$$$'.

DEV'. Error: Encounter an Interna server error. e

tracking activity id is '&&&', correlation id is '&&'.

Himanshu Shekhar 1,935 Reputation points Microsoft External Staff Moderator

2025-10-31T07:13:44.3533333+00:00
Hello @Ilham Izzuddin - Thank you for reaching Microsoft QnA

What specific error message or status code do you receive when attempting to delete the container instance, and does it include any additional diagnostic information? (This helps identify if the issue is permission-related, resource lock-related?

Have you verified whether there are any active locks (such as ReadOnly or CanNotDelete) set on the container instance or its resource group that might prevent deletion?

What is the current state of the container instance (e.g., Running, Stopped, Deleting, or Failed), and are there any ongoing operations that could be blocking the deletion process?

Do you have sufficient permissions (Owner or Contributor role) on both the container instance and its resource group, and have you tried deleting the container instance using different methods, such as Azure CLI, PowerShell, or REST API?

Is the container instance attached to other resources like virtual networks, load balancers, or storage accounts, and could dependencies or resource linkage be preventing the deletion

Regards

Himanshu
Ilham Izzuddin 20 Reputation points

2025-10-31T07:20:07.3266667+00:00

1.The error is internal server on portal and bash

2.I have checked there is no lock,i can create others new aci using portal successfull and also can be deleted.

3.Currently stopped

4.I have contributor roles on this RG.

5.It attached to VNET,other normal aci also attached to the VNET but can be deleted.how to verify if this aci attached to Storage account.
Ilham Izzuddin 20 Reputation points

2025-11-03T03:23:24.55+00:00

Hi Manish

It still shows an error internal server

Answer accepted by question author

0 additional answers

Your answer

Himanshu Shekhar 1,935 Reputation points Microsoft External Staff Moderator

2025-10-31T07:13:44.3533333+00:00

Hello @Ilham Izzuddin - Thank you for reaching Microsoft QnA

What specific error message or status code do you receive when attempting to delete the container instance, and does it include any additional diagnostic information? (This helps identify if the issue is permission-related, resource lock-related?

Have you verified whether there are any active locks (such as ReadOnly or CanNotDelete) set on the container instance or its resource group that might prevent deletion?

What is the current state of the container instance (e.g., Running, Stopped, Deleting, or Failed), and are there any ongoing operations that could be blocking the deletion process?

Do you have sufficient permissions (Owner or Contributor role) on both the container instance and its resource group, and have you tried deleting the container instance using different methods, such as Azure CLI, PowerShell, or REST API?

Is the container instance attached to other resources like virtual networks, load balancers, or storage accounts, and could dependencies or resource linkage be preventing the deletion

Regards

Himanshu
Ilham Izzuddin 20 Reputation points

2025-10-31T07:20:07.3266667+00:00

1.The error is internal server on portal and bash

2.I have checked there is no lock,i can create others new aci using portal successfull and also can be deleted.

3.Currently stopped

4.I have contributor roles on this RG.

5.It attached to VNET,other normal aci also attached to the VNET but can be deleted.how to verify if this aci attached to Storage account.
Ilham Izzuddin 20 Reputation points

2025-11-03T03:23:24.55+00:00

Hi Manish

It still shows an error internal server

Answer 1

Hello @Ilham Izzuddin

We have reviewed the issue where the customer was unable to delete Azure Container Instances (ACI) due to an “Internal Server Error” observed across Portal, Bash, and REST API.

Troubleshooting and actions performed:

Verified there were no resource locks or permission issues at the subscription and resource group level.

Confirmed that the ACI was in a Stopped state and not in the middle of any active operations.

Attempted deletion using multiple methods — Azure Portal, Azure CLI, and REST API — but the deletion continued to fail with the same internal server error.

Checked for attached dependencies such as Network Profiles and VNET associations.

Identified that the container instances were stuck in an inconsistent backend state, causing the deletion requests to fail.

Engaged the Azure Backend Team, who performed a backend cleanup to remove the stale container instances successfully.

The backend team has deleted the stuck container instances, and the issue is now resolved. The customer confirmed that the container groups are no longer visible in the resource group.

If issue resolved. Could you please accept the answer and upvote it

Share via

Unable to delete container instances

0 additional answers

Your answer