Azure Pipelines Tasks

Overview

This repo contains the tasks that are provided out-of-the-box with Azure Pipelines and Team Foundation Server.

This provides open examples on how we write tasks which will help you write other tasks which can be uploaded to your account or server. See Writing Tasks below. Check Deprecation.md file for the list of task which are no longer supported.

Status

	Build & Test
Windows
macOS
Linux

How to Use Tasks

See the documentation for Continuous integration and deployment.

Writing Tasks

If you need custom functionality in your build/release, it is usually simpler to use the existing script running tasks such as the PowerShell or Bash tasks. Writing a new task may be appropriate if you need deeper integration or reusability in many build definitions

Tasks are simply tool runners. They know how to run MSBuild, VSTest, etc... in a first class way and handle return codes, how to treat std/err out, and how to write timeline records based on expected output. They also get access to credentials to write back to TFS/Azure Pipelines.

For uploading custom tasks to Azure Pipelines use the TFS Cross Platform Command Line utility.

Tasks can also be deployed with an Azure DevOps extension. See this tutorial for how to write a custom task and package it inside an extension.

Contributing

This project welcomes contributions and suggestions.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Issues

We accept issue reports both here (file a GitHub issue) and in Developer Community.

Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don't report it here - let us know by sending an email to secure@microsoft.com.

Deprecated Tasks

Some tasks in this repository have been deprecated and are no longer actively maintained. Deprecated tasks will display a warning banner when used in pipelines, and will be removed after a 90-day notice period.

If you are using a deprecated task, please migrate to the recommended replacement task as soon as possible to avoid disruption to your pipelines.

For a complete list of deprecated tasks, their deprecation dates, and migration guidance, see DEPRECATION.md.

Common reasons for deprecation:

• Retired Azure services - The underlying Azure service has been retired or replaced
• Security improvements - Newer versions use more secure authentication methods (e.g., Workload Identity Federation)
• Outdated dependencies - The task uses deprecated tools or libraries (e.g., older versions of AzCopy, PowerShell modules)
• Better alternatives available - Superseded by newer task versions with improved functionality