An Azure service that provides a general-purpose, serverless container platform.
The original Microsoft.App inner error can only be retrieved through Azure Support’s backend telemetry; open a technical support request with the tracking ID, UTC timestamp, sanitized template, and validation response, while using another validation-only run to capture a fresh correlation ID and full CLI trace.
What is established
- This was resource-provider preflight: ARM called
Microsoft.Appto determine whether the resource was feasible without creating or modifying it. Preflight failures do not enter deployment history because deployment never starts.^1^ - Therefore,
DeploymentNotFoundis expected and does not indicate a missing deployment record.^2^ -
Microsoft.App/containerApps@2025-07-01is a documented ARM resource definition, so the API version exists for this resource type.^3^ - The available evidence does not expose the provider’s hidden inner error or identify a rejected property.
InvalidTemplateDeploymentalone can represent provider/API compatibility, naming, scope, RBAC, policy, quota, or provider-specific constraints; it is not enough to select a corrective edit.
Capture a fresh validation-only trace
Because no retry has been performed, repeat the same validation with the unchanged, hash-verified template and --debug. This still performs validation only and does not create the Container App.
Debug output can contain command arguments and parameter values; sanitize it before attaching it to a public post or ticket.
az deployment group validate \
--resource-group <RESOURCE_GROUP> \
--name aca-preflight-repro \
--template-file <TEMPLATE_FILE> \
--parameters @<PARAMETERS_FILE> \
--validation-level Provider \
--debug 2> aca-preflight-debug.log
Provider is the default full validation level. Azure CLI also supports ProviderNoRbac and Template; Template skips resource-provider preflight entirely.^4^ The debug trace includes API-call and execution details and may expose an x-ms-correlation-request-id in addition to the error’s tracking ID.^5^
Run a static-only comparison:
az deployment group validate \
--resource-group <RESOURCE_GROUP> \
--template-file <TEMPLATE_FILE> \
--parameters @<PARAMETERS_FILE> \
--validation-level Template
Interpretation:
- Template succeeds, Provider fails: the rejection is specifically in provider preflight, not ARM’s static template processing.
- Both fail: use the static error’s property path, line, or parameter details.
- ProviderNoRbac succeeds while Provider fails: investigate caller permissions. Otherwise, do not treat RBAC as the established cause.
az deployment group validate \
--resource-group <RESOURCE_GROUP> \
--template-file <TEMPLATE_FILE> \
--parameters @<PARAMETERS_FILE> \
--validation-level ProviderNoRbac
Verify API and regional exposure for this subscription
Query the subscription’s current Microsoft.App metadata rather than inferring support from another Container Apps feature’s regional list:
az provider show --namespace Microsoft.App \
--query "resourceTypes[?resourceType=='containerApps'].{apiVersions:apiVersions,locations:locations}" \
--output json
az provider show --namespace Microsoft.App \
--query "{registrationState:registrationState}" \
--output json
Confirm that:
-
2025-07-01appears underapiVersions. -
Sweden Centralappears underlocations. - Registration is not
NotRegistered.
Provider metadata is the documented mechanism for retrieving valid API versions and locations. Azure also notes that subscription restrictions can prevent use of a region even when the resource type supports it.^6^
This confirms API and location exposure independently, but it does not prove that every property combination is accepted by Microsoft.App preflight.
Escalate for the original inner error
In Azure portal, select ? → Help + support → Create a support request, choose Technical, and route it to Azure Container Apps. Creating the request requires Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.^7^
Include:
- Original tracking ID and the fresh retry’s tracking/correlation ID.
- Exact UTC timestamps; approximately 16:01 CET is approximately 15:01 UTC.
- Resource provider/type and API version.
- Azure CLI version and exact validation command.
- Sanitized ARM template and parameter file.
- SHA-256 for both the original and retry inputs.
- Complete JSON error and sanitized debug log.
- Output of the two provider-metadata queries.
- Explicit request: retrieve the Microsoft.App preflight inner error and identify its target property or provider constraint; no resource deployment is authorized or requested.
The minimum corrective action cannot be determined safely until that inner error or a new detailed validation response identifies the rejected field or provider-side condition.
References