AzureFunction@0 is retired: replace it with AzureFunction@2
The short answer
- Retirement date
- Removal date
- . Pipelines that still use it fail after removal.
- Replacement
AzureFunction@2- Kind of migration
- replacement with input changes
- Automatic rewrite
- Not yet. Automatic rewrite is planned for this kind of task (replacement with input changes). Today, trasloco modernize --check finds the step and you change it by hand.
- Recommended action
- Replace AzureFunction@0 with AzureFunction@2 and review the replacement inputs before updating the pipeline.
Official sources
- Official task retirement announcement
- Task definition: AzureFunction (task.json)
- Task definition: AzureFunctionV2 (task.json)
Last verified:
Why does my pipeline show a retirement error for AzureFunction@0?
On , Azure Pipelines shows a retirement error for AzureFunction@0, but the run does not fail. On , pipelines that still use AzureFunction@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 'AzureFunction@0' --include='*.yml' --include='*.yaml' .
How to migrate
Replace AzureFunction@0 with AzureFunction@2 and review the replacement inputs before updating the pipeline.
The task definition of the replacement is linked under official sources above.
AzureFunction@0 retirement FAQ
Is AzureFunction@0 deprecated?
Yes. AzureFunction@0 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does AzureFunction@0 stop working?
AzureFunction@0 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of AzureFunction@0?
Replace AzureFunction@0 with AzureFunction@2.
Related retired tasks
- ArchiveFiles@1 — replacement with input changes
- CacheBeta@0 — replacement with input changes
- cURLUploader@1 — replacement with input changes
- DotNetCoreCLI@0 — replacement with input changes
- DotNetCoreCLI@1 — replacement with input changes