Errors in "az deployment group create" not helpful

[jspaith]

Describe the bug

Summary

Errors returned from az deployment are not helpful, even with --debug enabled it requries a lot of digging.

Using the PowerShell equivalent New-AzResourceGroupDeployment gave me great errors including a fix. It'd help for az deployment to follow more closely the PS1 convention.

Details
I ran az deployment group create --resource-group $RESOURCE_GROUP --template-file df.bicep --parameters @bb.parameters.json, where it turned out that I was referencing an invalid version of the RP.

The only output is "The content for this response was already consumed".

If I enable --debug I actually do get this as a warning

Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]

It turns out that PowerShell being more helpful here is a well known issue - see the thread here.

When I did New-AzResourceGroupDeployment -ResourceGroupName $resourceGroup , I was told that my RP version was invalid AND it even told me what valid versions were for me to update to. And that was all that it had - it didn't require enabling a debug option and it wasn't an overwhelming amount of spew.

Requests:

• Replace the error message "The content for this response was already consumed" with something more meaningful in the standard case.
• These don't feel like Warning level issues in the --debug but rather errors.

Version of az cli -

Related command

az deployment group create --resource-group $RESOURCE_GROUP --template-file df.bicep --parameters @bb.parameters.json

Errors

The content for this response was already consumed

Issue script & Debug output

az deployment group create --resource-group $RESOURCE_GROUP --name "df-test-$(date +%H%M%S)" --template-file df.bicep --parameters @bb.parameters.json --parameters useDataflowGraph=false
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(40,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(44,26) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowProfiles@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(49,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(53,25) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(58,30) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(63,35) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/registryEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-graph.bicep(68,24) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowProfiles/dataflowGraphs@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventgrid.bicep(25,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventgrid.bicep(33,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventgrid.bicep(123,28) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventhub.bicep(28,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventhub.bicep(36,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-eventhub.bicep(81,27) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-mqtt.bicep(16,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-mqtt.bicep(20,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-mqtt.bicep(31,34) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-otel.bicep(13,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-otel.bicep(17,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-endpoint-otel.bicep(22,23) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/dataflowEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-registry.bicep(22,22) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-registry.bicep(30,25) : Warning BCP081: Resource type "Microsoft.ExtendedLocation/customLocations@2025-11-01-preview" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-registry.bicep(71,35) : Warning BCP081: Resource type "Microsoft.IoTOperations/instances/registryEndpoints@2025-10-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]
/home/john/iot/one-connector2/dev/deploy-scripts/bicep/bugbash/df-registry.bicep(83,28) : Warning no-hardcoded-env-urls: Environment URLs should not be hardcoded. Use the environment() function to ensure compatibility across clouds. Found this disallowed host: "management.azure.com" [https://aka.ms/bicep/linter-diagnostics#no-hardcoded-env-urls]

The content for this response was already consumed

Expected behavior

As called out in the bug, I'd prefer a meaningful error about the version mismatch without having to dig through the --debug logs (which were a bit misleading since they were "only" warn).

Environment Summary

john@jspaith:~/iot/one-connector2/dev/deploy-scripts/bicep/bugbash$ az --version
azure-cli 2.77.0 *

core 2.77.0 *
telemetry 1.1.0

Extensions:
azure-devops 1.0.2
azure-iot-ops 2.0.0b4.dev4
connectedk8s 1.10.10
eventgrid 1.0.0b2
k8s-extension 1.7.0
kusto 0.5.0

Dependencies:
msal 1.34.0b1
azure-mgmt-resource 23.3.0

Python location '/opt/az/bin/python3'
Config directory '/home/john/.azure'
Extensions directory '/home/john/.azure/cliextensions'

Python (Linux) 3.13.7 (main, Aug 26 2025, 08:46:54) [GCC 11.4.0]

Additional context

No response

[azure-client-tools-bot-prd]

Hi @jspaith,

2.77.0 is not the latest Azure CLI(2.78.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

[yonzhan]

Thank you for opening this issue, we will look into it.

[lucasbrynte]

I have the same experience, also using version 2.77.0.

[torreymicrosoft]

Thanks for your patience — this was recently picked up as an outstanding open issue for the ARM Deployments team to review.

@jspaith — thanks, and the PowerShell comparison is a fair one. There are really two things here:

1. The The content for this response was already consumed message that masked your real error — that's the same regression as Deployment validation fails with 'content already consumed' error #32149 / Deploy Bicep template returns error "The content for this response was already consumed" #31581, and it was fixed in CLI 2.78.0. I verified on 2.85.0 that the underlying ARM error now surfaces directly (a missing RG / invalid input comes back as a proper error rather than "content already consumed"). Upgrading should restore meaningful errors here.

2. Making az deployment errors as actionable as PowerShell's (which listed the valid API versions) — that's a legitimate quality gap. The valid-versions hint is in the ARM error payload; surfacing it as cleanly as New-AzResourceGroupDeployment does, and at error (not just --debug warning) level, is a CLI UX improvement we can track on this issue.

Could you confirm on a current CLI (≥ 2.78) that the invalid-API-version case now returns a real error? I'll keep this open re-scoped to the "match PowerShell's helpfulness" part. Thanks for the clear write-up.