CondaEnvironment@1 is retired: migrate off its platform or external tool
The short answer
- Retirement date
- Removal date
- . Pipelines that still use it fail after removal.
- Replacement
- No replacement task.
- Kind of migration
- retired platform or external tool: no drop-in replacement
- Automatic rewrite
- No. This task needs a manual migration. trasloco modernize --check still finds the step.
- Recommended action
- Create and manage the Conda environment from a script step.
Official sources
Last verified:
Why does my pipeline show a retirement error for CondaEnvironment@1?
On , Azure Pipelines shows a retirement error for CondaEnvironment@1, but the run does not fail. On , pipelines that still use CondaEnvironment@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 'CondaEnvironment@1' --include='*.yml' --include='*.yaml' .
How to migrate
Create and manage the Conda environment from a script step.
CondaEnvironment@1 retirement FAQ
Is CondaEnvironment@1 deprecated?
Yes. CondaEnvironment@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does CondaEnvironment@1 stop working?
CondaEnvironment@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of CondaEnvironment@1?
There is no drop-in replacement task for CondaEnvironment@1. Create and manage the Conda environment from a script step.
Related retired tasks
- AppCenterDistribute@0 — retired platform or external tool: no drop-in replacement
- AppCenterDistribute@1 — retired platform or external tool: no drop-in replacement
- AppCenterDistribute@2 — retired platform or external tool: no drop-in replacement
- AutomatedAnalysis@0 — retired platform or external tool: no drop-in replacement
- AzureCloudPowerShellDeployment@1 — retired platform or external tool: no drop-in replacement