Two new print statements broke the Azure CLI deployment JSON output

[rasitha1]

Describe the bug

Looks like this issue introduced two print statements causing the output of a az deployment to no longer be valid JSON.

This only happens when using the --parameters option and a .bicepparam file. Does not happen for --template-file type deployments.

`

> az deployment sub create --parameters .\test.bicepparam --location westus --name test
Bicep CLI is already installed at 'C:\Users\foo\.azure\bin\bicep.exe'. Skipping installation as no specific version was requested.
{
  "id": "/subscriptions/fb0a....

Existing pipelines that piped the output of a az deployment to convertfrom-json now fail because of this.

Related command

az deployment sub create --parameters .\test.bicepparam --location westus --name test

Errors

no errors

Issue script & Debug output

Bicep CLI is already installed at 'C:\Users\foo\.azure\bin\bicep.exe'. Skipping installation as no specific version was requested.
{
  "id": "/subscriptions/fb0a....

Expected behavior

Should not output the print statement:
Bicep CLI is already installed at 'C:\Users\foo\.azure\bin\bicep.exe'. Skipping installation as no specific version was requested.

Environment Summary

azure-cli                         2.81.0

core                              2.81.0
telemetry                          1.1.0

Dependencies:
msal                            1.34.0b1
azure-mgmt-resource               23.3.0

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Config directory 'C:\Users\foo\.azure'
Extensions directory 'C:\Users\foo\.azure\cliextensions'

Python (Windows) 3.13.9 (tags/v3.13.9:8183fa5, Oct 14 2025, 14:09:13) [MSC v.1944 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context

No response

[yonzhan]

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

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• az bicep can produce bad output when using --stdout option #27855

Powered by issue-sentinel

[rcarde]

Note that this occurs irrespective of the --output option (json, none, etc). Breaking all our pipelines that parse the output where they pipe to ConvertFrom-Json.

The same issue also reported here.

[anthony-c-martin]

Tagging @shenglol to take a look