Hello Microsoft Azure Container Apps team,
I am experiencing an ARM preflight validation failure when deploying an Azure Container Apps Managed Environment in Sweden Central.
Environment configuration
- Resource type:
Microsoft.App/managedEnvironments
API version: 2025-07-01
Region: swedencentral
Workload profile: Consumption
Environment type: Workload Profiles
Internal VNet integration: Enabled
Public network access: Disabled
Zone redundancy: Disabled
Infrastructure subnet: Existing subnet delegated to Microsoft.App/environments
Logging destination: Existing Azure Log Analytics workspace
Error details
The ARM deployment fails during preflight validation with:
InvalidTemplateDeployment
ValidationForResourceFailed
Resource provider: Microsoft.App/managedEnvironments
HTTP status: BadRequest
The original failure occurred on November 15, 2026, at approximately 18:02:56 UTC.
The Azure Activity Log confirms that Microsoft.Resources/deployments/validate/action failed.
Subsequent checks confirmed that the target managed environment was not created.
Troubleshooting already completed
Verified the ARM template is valid JSON.
Verified that the template uses Microsoft.App/managedEnvironments@2025-07-01.
Reviewed the configuration against the documented ARM resource schema.
Confirmed the infrastructure subnet is configured for Azure Container Apps.
Confirmed the existing Log Analytics workspace is provisioned.
Attempted ARM deployment validation, but the returned diagnostics did not expose the underlying resource provider error.
Questions
Are there known validation restrictions for creating an internal Workload Profiles environment with publicNetworkAccess=Disabled and a Consumption workload profile using API version 2025-07-01?
Are there additional networking or Log Analytics configuration requirements that could cause this preflight failure?
Is there a recommended way to retrieve the underlying Microsoft.App validation error when ARM only returns ValidationForResourceFailed?
Could this be a regional or API-version compatibility issue in Sweden Central?
I would appreciate guidance on identifying the precise root cause before making any configuration changes.
Thank you.Hello Microsoft Azure Container Apps team,
I am experiencing an ARM preflight validation failure when deploying an Azure Container Apps Managed Environment in Sweden Central.
Environment configuration
Resource type: Microsoft.App/managedEnvironments
API version: 2025-07-01
Region: swedencentral
Workload profile: Consumption
Environment type: Workload Profiles
Internal VNet integration: Enabled
Public network access: Disabled
Zone redundancy: Disabled
Infrastructure subnet: Existing subnet delegated to Microsoft.App/environments
Logging destination: Existing Azure Log Analytics workspace
Error details
The ARM deployment fails during preflight validation with:
InvalidTemplateDeployment
ValidationForResourceFailed
Resource provider: Microsoft.App/managedEnvironments
HTTP status: BadRequest
The original failure occurred on November 15, 2026, at approximately 18:02:56 UTC.
The Azure Activity Log confirms that Microsoft.Resources/deployments/validate/action failed.
Subsequent checks confirmed that the target managed environment was not created.
Troubleshooting already completed
Verified the ARM template is valid JSON.
Verified that the template uses Microsoft.App/managedEnvironments@2025-07-01.
Reviewed the configuration against the documented ARM resource schema.
Confirmed the infrastructure subnet is configured for Azure Container Apps.
Confirmed the existing Log Analytics workspace is provisioned.
Attempted ARM deployment validation, but the returned diagnostics did not expose the underlying resource provider error.
Questions
Are there known validation restrictions for creating an internal Workload Profiles environment with publicNetworkAccess=Disabled and a Consumption workload profile using API version 2025-07-01?
Are there additional networking or Log Analytics configuration requirements that could cause this preflight failure?
Is there a recommended way to retrieve the underlying Microsoft.App validation error when ARM only returns ValidationForResourceFailed?
Could this be a regional or API-version compatibility issue in Sweden Central?
I would appreciate guidance on identifying the precise root cause before making any configuration changes.
Thank you.