AzurePowerShell@1 is retired: replace it with AzurePowerShell@5
The short answer
- Retirement date
- Removal date
- . Pipelines that still use it fail after removal.
- Replacement
AzurePowerShell@5- 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 AzurePowerShell@5, reviewing the documented behavior and input differences.
Official sources
- Official task retirement announcement
- Task definition: AzurePowerShell (task.json)
- Task definition: AzurePowerShellV5 (task.json)
Last verified:
Why does my pipeline show a retirement error for AzurePowerShell@1?
On , Azure Pipelines shows a retirement error for AzurePowerShell@1, but the run does not fail. On , pipelines that still use AzurePowerShell@1 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 'AzurePowerShell@1' --include='*.yml' --include='*.yaml' .
How to migrate
Migrate this step manually to AzurePowerShell@5, reviewing the documented behavior and input differences.
The task definition of the replacement is linked under official sources above.
AzurePowerShell@1 retirement FAQ
Is AzurePowerShell@1 deprecated?
Yes. AzurePowerShell@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does AzurePowerShell@1 stop working?
AzurePowerShell@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of AzurePowerShell@1?
Replace AzurePowerShell@1 with AzurePowerShell@5.
Related retired tasks
- AndroidBuild@1 — manual migration
- AndroidSigning@1 — manual migration
- AndroidSigning@2 — manual migration
- AzureCLI@0 — manual migration
- AzureCloudPowerShellDeployment@1 — retired platform or external tool: no drop-in replacement
- AzureCloudPowerShellDeployment@2 — retired platform or external tool: no drop-in replacement
- AzureMonitor@0 — manual migration
- AzureNLBManagement@1 — manual migration