Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Deprecation notice: This article is deprecated and is no longer being updated. To ensure only the best guidance is surfaced, this article will be deleted in May 2026.
For alternative guidance, see Azure Container Apps architecture guidance in the Azure Architecture Center.
If you would like to save this guidance, you can select Download a PDF at the bottom left of this page or download the files from GitHub.
Azure Container Apps landing zone accelerator is your resource as you prepare to build and deploy applications in a typical enterprise landing zone design.
What's in the accelerator
The landing zone accelerator is a set of design considerations and reference architecture backed by a specific implementation. Design areas cover considerations and recommendations for common technical areas that integrate with the centralized services.
Integration with platform landing zones
The platform landing zones have shared services that centralized teams manage, so you can focus on application development and workload resources.
As you integrate a landing zone, make sure you have a strong understanding of the integration points between the shared resources and workload resources. If the platform requires changes, work with the centralized team to implement changes together. For example, communicate the expected potential of the workload early so that the central networking team can allocate a virtual network with address space that's large enough to accommodate that growth.
Deploy Azure Container Apps landing zone accelerator
The Azure Container Apps landing zone accelerator reference implementation with infrastructure-as-code templates is available on GitHub.