## TL;DR

Upgrading the CLI (2.78.0 confirmed by reporters) also resolved it. Look past it for the actual cause: parameter mismatches between template and parameters file, unresolved env placeholders like ${AZURE_ENV_NAME}, wrong resource-name casing, wrong SKU names, or blocked policy actions.

## Steps

1. '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 ${AZURE_ENV_NAME}, wrong resource-name casing, wrong SKU names, or blocked policy actions. Upgrading the CLI (2.78.0 confirmed by reporters) also resolved it.

## When to use

You are seeing this: 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". Use this skill when you run into "Deploy Bicep template returns error "The content for this response was already consumed"".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: v1.0, 2.78.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.