Azure Container Apps frequently asked questions (FAQs)

A list can be generated by running the following Azure CLI command:

```azurecli
az provider show \
--namespace Microsoft.App \
--query "resourceTypes[?resourceType=='managedEnvironments'].locations"
```

No, there's no access to the Kubernetes API.

Yes.

Refer to the billing page for details.

Yes. Using Azure CLI, run az containerapp github-action -h to see the options. Using Azure portal, go to the "Continuous deployment" window under your container app.

Azure Container Apps decodes the URL to protect your app against URL confusion attacks. A request URL that has encoded portions, such as http://mysite.com/archive/http%3A%2F%2Fmysite.com%2Farchive%2F123, is sent to your app as http://mysite.com/archive/http%3A/mysite.com/archive/123.

For Consumption only environments, express routes are unsupported, and limited UDR when configured as follows is supported. The UDR configuration must have a route configured for Azure.<REGION_NAME> Service tag with Next Hop = "Internet". In addition, the rules in the NSG documentation must be configured for the Consumption only environment to be operational. These limitations do not apply for workload profiles, and for full featured UDR and Express Route support, use workload profile environments.

Azure Container Apps doesn't move or store customer data out of the deployed region.

Request a quota increase in the Azure portal with Azure Container Apps selected as the provider.

Keep in mind the following when it comes to quota increase requests:

• Scaling apps vs environments: There are many different quotas available to increase. Use these descriptions to help identify your needs:

  • Increase apps and cores per environment: Allows you to run more apps within an environment and/or more intensive apps. Recommended if your workloads can deploy within the same network and security boundaries.
  • Increasing environments: Recommended if your workloads need network or security boundaries. Note: A detailed business context might be required if your request involves increasing environment-level quotas. When you request a change to your regional environment quota, you should request a corresponding change to your global environment quota.

• Regions: Approvals for increase requests vary based on compute capacity available in Azure regions.

• Specific compute requirements: The platform supports 4 GB per container app. Memory limits overrides are evaluated on a per-case basis.

• Business reasoning for scaling: You might be eligible for a quota increase request if the platform limits are blocking your workload demands. Scale limits overrides are evaluated on a per-case basis.

Each Dapr capability undergoes thorough evaluation to ensure it positively impacts customers running microservices in the Azure Container Apps environment, while providing the best possible experience.

The availability of Dapr's alpha APIs is not guaranteed or Microsoft-supported.

While Tier 1 components are fully supported, Tier 2 components are supported with best effort. Learn more.

Dapr's typical release timeline is up to six weeks after the Dapr OSS release. The latest Dapr version is made available in Azure Container Apps only after rigorous testing. Rolling out to all regions can take up to two weeks or longer.

You can submit a feature request via the Azure Container Apps GitHub repository. Make sure to include "Dapr" in the feature request title.

A Docker-less deployment allows you to deploy your application without defining a Dockerfile in your code. Instead, the Container Apps cloud build functionality uses Buildpacks to turn source code on your local machine into a container image. This option uses the Azure Container Apps default registry.

You are experiencing a known issue with Docker-less deployments. Retrying might resolve this for you. If you run into this issue, open a GitHub issue so our team can investigate.

You need to enable data protection for all .NET apps on Azure Container Apps. See Deploying and scaling an ASP.NET Core app on Azure Container Apps for details.

Container Apps supports four LTS JDK versions: JDK 8, JDK 11, JDK 17 and JDK 21. For source code build, the default version is JDK 17. For a JAR file build, the JDK version is read from the file location META-INF\MANIFEST.MF in the JAR, but uses the default JDK version 17 if the specified version isn't available.

You can configure JDK version to override the default version via build environment variables.

Maven

You can customize a Java image build via build environment variables.

When using containerapp up in combination with a Docker-less code base, use the --location parameter so that application runs in a location other than US East.