Accidentally deleted Container App in resource group

Meetup pvt ltd 0 Reputation points
2026-08-22T05:08:44.57+00:00

We accidentally deleted and redeployed a Container App named "litellm" in resource group "infinall-litellm-rg" on Azure subscription 5b3b50f9-34a2-4b29-b802-76787942ec14. The app had a postgres container running as a sidecar with no persistent volume mount. All database data including model configurations and RAG agent setup was lost when the container was deleted.

We need to know: Does Azure Container Apps retain any internal snapshots or backups of ephemeral container storage that Microsoft support can use to restore the data? The deletion happened on 2026-08-22 around 03:00 UTC.

Resource group: infinall-litellm-rg Container App: litellm Region: East US 2

Azure Container Apps
Azure Container Apps

An Azure service that provides a general-purpose, serverless container platform.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Allan Solomon Mejia 5,420 Reputation points
    2026-08-22T22:39:00.5866667+00:00

    Hello @Meetup pvt ltd

    Unfortunately, based on the architecture you described, I don't believe you can recover the PostgreSQL data from Azure Container Apps.

    The key detail is that PostgreSQL ran as a sidecar without persistent storage mounted for its data directory.

    Azure Container Apps provides container-scoped and replica-scoped ephemeral storage. Microsoft documents that container-scoped storage disappears when the container shuts down or restarts, while replica-scoped storage exists only for the lifetime of that replica.

    Deleting the Container App shuts down its containers. Microsoft also explicitly advises that applications shouldn't expect state stored inside containers to persist because containers can be restarted as part of their normal lifecycle.

    Therefore, if PostgreSQL's /var/lib/postgresql/data was stored only in the sidecar's local filesystem, deleting the Container App would remove the storage containing that database.

    Azure Container Apps doesn't provide a customer-accessible backup or snapshot mechanism for that ephemeral container filesystem. The platform's reliability documentation also distinguishes ephemeral application data from control-plane metadata: the platform can replicate configuration and related metadata, but it deletes application data stored in ephemeral storage when the container or replica shuts down.

    Redeploying another Container App with the same name won't reconnect it to the previous container filesystem; it's a new workload with new ephemeral storage.

    Before assuming the data is permanently lost, I would verify that PostgreSQL truly has no external persistence configured. Check the previous deployment/IaC configuration for:

    • an Azure Files volume mounted to PostgreSQL;
    • an external Azure Database for PostgreSQL instance;
    • application-level PostgreSQL backups/dumps;
    • backup copies in Azure Storage;
    • CI/CD artifacts or configuration exports containing the model/RAG configuration.

    If none of those existed, I wouldn't expect Microsoft Support to restore the deleted PostgreSQL filesystem from an internal Container Apps snapshot.

    You can still open a Microsoft support request and provide the resource ID, region, deletion timestamp (2026-08-22 around 03:00 UTC), and Activity Log correlation information so Microsoft can confirm whether anything remains recoverable on the backend, but I would set expectations that ephemeral storage isn't a supported recovery source.

    For the rebuilt application, PostgreSQL shouldn't use the Container Apps local filesystem for durable database data. Microsoft recommends external persistent storage for stateful workloads; Azure Container Apps supports permanent storage through Azure Files, while a managed database such as Azure Database for PostgreSQL would generally be a better architecture for production PostgreSQL data.

    Sharing these references with you:

    Use storage mounts in Azure Container Apps

    Application lifecycle management in Azure Container Apps

    I would also recommend removing the subscription ID from the public post. It isn't needed for community troubleshooting; provide it privately only if Microsoft Support requests it.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.