trasloco

AzureCLI@0 is retired: replace it with AzureCLI@3

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
AzureCLI@3
Kind of migration
manual migration
Automatic rewrite
No. This task needs a manual migration. trasloco modernize --check still finds the step.
Recommended action
Migrate this step manually to AzureCLI@3, reviewing the documented behavior and input differences.

Official sources

Last verified:

Why does my pipeline show a retirement error for AzureCLI@0?

On , Azure Pipelines shows a retirement error for AzureCLI@0, but the run does not fail. On , pipelines that still use AzureCLI@0 fail.

Find it in your pipelines

With trasloco:

trasloco modernize --check

Install trasloco from the latest release.

With plain grep, nothing to install:

grep -rniwF 'AzureCLI@0' --include='*.yml' --include='*.yaml' .

How to migrate

Migrate this step manually to AzureCLI@3, reviewing the documented behavior and input differences.

The task definition of the replacement is linked under official sources above.

AzureCLI@0 retirement FAQ

Is AzureCLI@0 deprecated?

Yes. AzureCLI@0 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.

When does AzureCLI@0 stop working?

AzureCLI@0 is removed on 2027-03-15. Pipelines that still use it fail after removal.

What should I use instead of AzureCLI@0?

Replace AzureCLI@0 with AzureCLI@3.