The article explains how to implement a "build once, deploy everywhere" strategy using Azure Container Apps and the Azure Developer CLI (azd) version 1.20.0. It highlights a common issue in container deployment where the azd deploy command bundles building, pushing, and deploying into one step. This convenience can lead to complications in production environments, particularly around managing container versions and configurations. Azure Developer CLI has introduced new features that address these challenges by separating container operations and allowing for layered infrastructure deployments. Two main capabilities have been added: the azd publish command, which builds and pushes containers to a registry, and the azd deploy --from-package command, which deploys specific container versions without needing to rebuild. The layered infrastructure approach enables teams to deploy resources in a structured way, ensuring that shared resources like Azure Container Registry (ACR) are accessible across different environments while maintaining environment-specific configurations. This method also simplifies permissions management, as the necessary access rights are granted sequentially as layers are applied. The article uses a Flask-based file manager application as a practical example of this deployment strategy. It lays out a clear infrastructure organization that separates shared resources from environment-specific ones, detailing how the architecture allows for both development and production environments to operate with the same container image under different configurations. The setup ensures that development environments can push and pull images, while production environments are restricted to pulling only, enhancing security. The article concludes with a call to utilize CI/CD pipelines for production deployments while providing a step-by-step guide to setting up the development environment using the Azure Developer CLI.