Container Instance stopped and deleted but still running

Hello Dominik,

Thank you for reaching out and for the detailed description of the behavior you are observing. I understand how concerning it can be to see continued activity even after the container group has been deleted.

Based on your inputs, the container group is no longer visible in the Azure portal or via CLI, which indicates that it has been successfully deleted from Azure Container Instances. However, the activity you are seeing in logs can sometimes give the impression that the container is still running. In many cases, this is related to how telemetry is processed in Azure Log Analytics, where data ingestion is asynchronous. As a result, log entries may continue to appear for a short period after deletion due to ingestion latency or buffered data being flushed.

At the same time, there are rare scenarios where the underlying container process may not fully terminate even after a successful delete operation. In such cases, the resource is removed from the control plane and no longer appears in the portal or CLI, but residual execution may continue temporarily on the backend. Microsoft has documented similar behavior here: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-instances/management/aci-still-running-after-stop-delete-command

If the container group was deployed within a virtual network, please ensure there are no remaining network-related resources that might be affecting cleanup, as outlined here: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-vnet#clean-up-resources

To help us better understand the situation and proceed with further investigation or escalation if required, could you please provide the following details:

• The container group name, associated resource group, and the Azure region where it was deployed
• Confirmation on whether you are still observing any active billing for this resource in Azure Cost Management
• Whether the delete operation completed successfully in the Azure portal or CLI, or if you encountered any errors or timeouts during the process
• The Log Analytics query you are using, including the table being queried (for example, ContainerInstanceLog_CL or ContainerEvent_CL), along with an indication of how recent the latest log entries are
• Whether the container group was deployed within a Virtual Network
• A brief description of the activity being performed on your database (for example, read or write operations), and whether the activity level has changed since the container was deleted
• Whether you have already attempted to recreate the container group using the same name, resource group, and region as part of the recommended workaround

Hello Jilakara,

thank you for your fast response. I tried that workaround from the link to restart a container again and delete this one. The logs are still continuing running. So problem was not resolved. Since the container and log contains customer information i will have to create a private support request.

PS: I dont see the container in billing anymore.

Thanks for update. Could you please check private message and provide necessary details