An Azure service that provides customers with a serverless container experience.
Welcome to Microsoft Q&A,
@LIGEngelsen I hope you are doing well,
What you're seeing can occur with Azure Container Instances even when there is no corresponding stop/start operation in the Activity Log.
Microsoft documents that the IP address of a container group is typically retained during updates, but it is not guaranteed to remain the same. Azure-internal events can cause the container group to be redeployed to a different underlying host, which can result in a different private IP address.Therefore, the absence of a stop/start entry in the Activity Log does not necessarily mean the underlying ACI host remained unchanged.
More importantly, a private IP address should not be treated as a permanent identity for an ACI container group. Microsoft explicitly recommends using a DNS name label to mitigate this scenario.
Also note that Azure Container Instances currently do not provide a persistent static private IP that survives redeployment/recreation of the container group.
So the behavior is not necessarily evidence of an unexpected container restart; it can be the result of Azure moving/redeploying the container group internally.
Recommended approach: treat the ACI IP as ephemeral and use DNS/service discovery instead of relying on the IP as a permanent address.
Documentation:
If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.