An Azure service that provides a general-purpose, serverless container platform.
The supported next step is to capture the deployment operation’s response payload with ARM debug logging, because the documented configuration supports an internal Workload Profiles environment with Consumption and disabled public access, while ValidationForResourceFailed alone does not identify the rejected condition.
Capture the underlying Microsoft.App response
Since ordinary validation and Activity Log output did not expose the nested error, submit the same template as a named deployment with response logging enabled. Debug logging can record secrets, including the Log Analytics shared key, so restrict access to the deployment history and delete it afterward. ^1^
New-AzResourceGroupDeployment `
-Name aca-env-debug `
-ResourceGroupName '<resource-group>' `
-TemplateFile '<template.json-or-main.bicep>' `
-TemplateParameterFile '<parameters.json>' `
-DeploymentDebugLogLevel ResponseContent
PowerShell does not display the recorded request and response properties. Retrieve them with Azure CLI:
az deployment operation group list \
--resource-group <resource-group> \
--name aca-env-debug \
--query "[?properties.provisioningState=='Failed'].properties.{
status:statusCode,
message:statusMessage,
response:response
}" -o jsonc
Also capture the correlation ID:
az deployment group show \
--resource-group <resource-group> \
--name aca-env-debug \
--query properties.correlationId -o tsv
ARM deployment history exposes failed operation messages and correlation IDs used by Azure Support to trace provider-side operations. ^2^
If the environment is inside a nested ARM deployment, add debugSetting.detailLevel to that nested Microsoft.Resources/deployments resource; top-level debug logging does not populate the nested deployment’s request and response. ^1^
After collecting the result, remove the debug deployment history:
az deployment group delete \
--resource-group <resource-group> \
--name aca-env-debug
Configuration restrictions relevant to this topology
There is no documented incompatibility among the settings listed:
- Workload Profiles is the default environment type and includes a built-in Consumption profile. ^3^
- An internal environment supports only
publicNetworkAccess: Disabled; therefore, that combination is valid rather than contradictory. ^4^ -
Microsoft.App/managedEnvironments@2025-07-01is a documented resource version and includespublicNetworkAccess,vnetConfiguration,workloadProfiles, andzoneRedundant. ^5^
The networking requirements that can produce provider validation failures are:
- A dedicated subnet used exclusively by the Container Apps environment.
- At least
/27for a Workload Profiles environment. - Delegation to
Microsoft.App/environments. - No overlap with the documented AKS-reserved and Container Apps platform-reserved ranges. ^6^
Your subnet delegation check covers one of these requirements, but not necessarily subnet size, exclusivity, or address-range overlap. Use the nested error before changing any of them.
For Log Analytics, when destination is log-analytics, the payload must contain logAnalyticsConfiguration.customerId and sharedKey; the shared key should be passed as a secure parameter. The Log Analytics object must not be supplied for another destination. ^5^ Merely confirming that the workspace exists does not confirm that these two submitted values are populated correctly.
Region and API-version checks
The available evidence does not establish a 2025-07-01 compatibility defect specific to Sweden Central. Confirm what the Microsoft.App provider advertises to this subscription:
az provider show --namespace Microsoft.App \
--query "resourceTypes[?resourceType=='managedEnvironments'].
{locations:locations, apiVersions:apiVersions}" -o jsonc
Provider metadata is the documented way to inspect valid locations and API versions for a resource type. Subscription restrictions can still prevent deployment in an otherwise supported region. ^7^
Treat regional capacity as the cause only if the nested response identifies capacity. Capacity is distinct from quota; the documented responses are to use another supported region or retry later. If Sweden Central is mandatory, open a Container Apps support request with the UTC timestamp, full nested response, region, environment name, correlation ID, and operation ID. ^8^
If debug logging still returns only the wrapper error, provider-side telemetry is required; the correlation and operation IDs are then the decisive artifacts for Support.
References
- Enable debug logging
- View deployment history with Azure Resource Manager
- Workload profiles in Azure Container Apps
- Networking in an Azure Container Apps environment
- Microsoft.App managedEnvironments 2025-07-01 (deployment-language-arm-template)
- Virtual network configuration
- Azure resource providers and types
- Troubleshoot environment capacity errors in Azure Container Apps ...