Deploy Bicep template returns error "The content for this response was already consumed"

The problem

Issue Azure/azure-cli#31581 (closed, 89 comments): ### Describe the bug When deploying a Bicep template containing Microsoft.Graph resources, the response returns the error "The content for this response was already consumed". The expected behavior is to show the error message. The unexpected behavior also applies to deploying other Azure resources like managed identity. ### Related command az deployment group create --resource-group [resource-group] --template-file main.bicep main.bicep ```bicep extension microsoftGraphV1 resource resourceApp 'Microsoft.Graph/applications@v1.0' existing = { uniqueNam: 'ExampleResourceApp' } output app objec

What fixed it

'The content for this response was already consumed' is a misleading wrapper that hides the real Bicep deployment error. Look past it for the actual cause: parameter mismatches between template and parameters file, unresolved env placeholders like ${AZUREENVNAME}, wrong resource-name casing, wrong SKU names, or blocked policy actions. Upgrading the CLI (2.78.0 confirmed by reporters) also resolved it.

In gh:Azure/azure-cli#31581 (Microsoft Azure), the issue reported was: Issue Azure/azure-cli#31581 (closed, 89 comments): ### Describe the bug When deploying a Bicep template containing Microsoft.Graph resources, the response returns the error "The content for this response was already consumed". The expected behavior is to show the error message. The unexpected behavior also applies to deploying other Azure resources like managed identity. ### Related command az deployment group create --resource-group [resource-group] --template-file main.bicep main.bicep ```bicep extension microsoftGraphV1 resource resourceApp 'Microsoft.Graph/applications@v1.0' existing = { uniqueNam: 'ExampleResourceApp' } output app objec The verified resolution from the thread: 'The content for this response was already consumed' is a misleading wrapper that hides the real Bicep deployment error. Look past it for the actual cause: parameter mismatches between template and parameters file, unresolved env placeholders like ${AZUREENVNAME}, wrong resource-name casing, wrong SKU names, or blocked policy actions. Upgrading the CLI (2.78.0 confirmed by reporters) also resolved it. Source: mount the host path https at container path //github.com/Azure/azure-cli/issues/31581