Connect to services in Azure Container Apps (preview)
Article
As you develop applications in Azure Container Apps, you often need to connect to different services. Rather than creating services ahead of time and manually connecting them to your container app, you can quickly create instances of development-grade services that are designed for nonproduction environments known as add-ons.
Add-ons allow you to use OSS services without the burden of manual downloads, creation, and configuration.
Once you're ready for your app to use a production level service, you can connect your application to an Azure managed service.
This command features the typical Container App create with the --bind argument. The bind argument tells the Container Apps runtime to connect a service to the application.
The --bind argument is available to the create or update commands.
To disconnect a service from an application, use the --unbind argument on the
update command
The following example shows you how to unbind a service.
az containerapp update --name myapp --unbind myredis
For more information on the service commands and arguments, see the
az containerapp reference.
Limitations
Add-ons are in public preview.
Any container app created before May 23, 2023 isn't eligible to use add-ons.
Add-ons come with minimal guarantees. For instance, they're automatically restarted if they crash, however there's no formal quality of service or high-availability guarantees associated with them. For production workloads, use Azure-managed services.
If you use your own VNET, you must use a workload profiles environment. The Add-ons feature is not supported in consumption only environments that use custom VNETs.
This module guides users through creating, configuring, and managing Container Apps and their environments. It also explores ingress options, scaling, instance management, and security considerations with best practices for configuring Azure Container Apps.