Misleading Error Messages

“`-o tsv` emits CRLF on Windows, breaking `for x in $(az ... -o tsv)` shell loops with misleading 400 errors ### Describe the bug On Windows, `az ... --output tsv` writes each row terminated by **CRLF** (`\r\n`) instead of LF (`\n`). When that output is consumed by a POSIX shell (Git Bash / MSYS2 / WSL-on-Windows-files / bash-from-PowerShell) via `for x in $(...)`, every token except the last carries a stray `\r`. That `\r` gets interpolated into the URL path of the next `az` call, and ARM responds with `HTTP 400 Bad Request`. The CLI's error message — `Operation returned an invalid status 'Bad Request'` — does not reveal the underlying cause. Net effect: a common shell pattern shown in many Microsoft Learn tutorials silently fails on Windows for every iteration **except the last one** in the loop. ### To Reproduce Any namespace/topic combination works. Example using Service Bus: ```bash RG=<your-rg> NS=<your-namespace> for topic in $(az servicebus topic list --resource-group "$RG" --namespace-name "$NS" --query "[].name" -o tsv); do count=$(az servicebus topic subscription list --resource-group "$RG" --namespace-name "$NS" --topic-name "$topic" --query "length(@)" -o tsv 2>&1) printf "%-40s %s\n" "$topic" "$count" done ``` Actual output (14 topics, only the alphabetically last works): ``` topic1 ERROR: Operation returned an invalid status 'Bad Request' topic2 ERROR: Operation returned an invalid status 'Bad Request' ``` ### Environment summary ``` azure-cli 2.80.0 core 2.80.0 telemetry 1.1.0 Extensions: account 0.2.5 authV2 1.0.1 azure-devops 1.0.2 redisenterprise 1.4.0 subscription 0.1.3 Dependencies: msal 1.34.0b1 azure-mgmt-resource 23.3.0 Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe' OS: Windows 11 Pro 10.0.26200 Shell: Git Bash (MSYS2 / mintty); also reproducible from PowerShell-invoked bash subshells ``` ### Proof of root cause `az ... -o tsv` writes CRLF row terminators on Windows: ```bash The bash `$(...)` substitution then carries `\r` on every token except the last (bash strips a trailing `\n` and the `\r` just before it in that single edge case — the other tokens keep their `\r` because the `\r` precedes a non-terminal `\n`). When the next `az` call receives `--topic-name "$topic"`, the inner CLI inserts the `\r` into the ARM REST URL path. ARM responds 400. The CLI surfaces only `Operation returned an invalid status 'Bad Request'` and does not echo the ARM error body, so the cause is invisible to the user. ### Workaround Strip `\r` from the captured output: ```bash for topic in $(az servicebus topic list --resource-group "$RG" --namespace-name "$NS" --query "[].name" -o tsv | tr -d '\r'); do count=$(az servicebus topic subscription list --resource-group "$RG" --namespace-name "$NS" --topic-name "$topic" --query "length(@)" -o tsv) printf "%-40s %s\n" "$topic" "$count" done ``` ### Proof of root cause `az ... -o tsv` writes CRLF row terminators on Windows: ```bash $ az servicebus topic list --resource-group "$RG" --namespace-name "$NS" --query "[].name" -o tsv | head -3 | od -c 0000000 t o p i c 1 \r \n t o p i c 2 \r \n 0000020 t o p i c 3 \r \n 0000030 ``` After applying `| tr -d '\r'` the loop returns the expected counts for all 14 topics. ### Comparison of output formats on Windows | Output mode | Line ending | Safe in shell `for` loops? | |---|---|---| | `-o tsv` | **CRLF** | **No — this bug** | | `-o json` | LF | n/a (not row-delimited) | | `-o jsonc` | LF | n/a | | `-o yaml` | LF | n/a | | `-o table` | CRLF (decorative) | n/a | Only the **machine-parseable, row-delimited** format `tsv` is affected. `csv` likely has the ”