Azure DevOps Blog
DevOps, Git, and Agile updates from the team building Azure DevOps
Latest posts
April Patches for Azure DevOps Server and Team Foundation Server
Today we are releasing patches that impact our self-hosted product, Azure DevOps Server, as well as Team Foundation Server 2018.3.2. We strongly encourage and recommend that all customers use the latest, most secure release of Azure DevOps Server. You can download the latest version of the product, Azure DevOps Server 2022.2 from the Azure DevOps Server download page. Previously, the Azure DevOps Agent used the Edgio CDN with endpoint . As part of Edgio's retirement, the domain is being decommissioned. To ensure continued availability, we have migrated to an Akamai-backed CDN with a new endpoint . This patch in...
Boards Integration with GitHub Enterprise Cloud and Data Residency (Public Preview)
Back in January, we launched a private preview of our Boards integration with GitHub Enterprise Cloud with data residency. If you're unfamiliar with GitHub's data residency option and what it means for your organization, you can learn more in the original announcement. Since the private preview launch, we’ve gathered valuable feedback from early adopters, and today, we’re excited to open up the experience to a wider audience with a public preview. How it works We’ve introduced a new option that allows you to connect an Azure Boards project to your GitHub Enterprise Cloud organization with data residency. Af...
CDN Domain URL change for Agents in Pipelines
Introduction We have announced the retirement of Edgio CDN for Azure DevOps and are transitioning to a solution served by Akamai and Azure Front Door CDNs. This change affects Azure DevOps Pipelines customers. This article provides guidance for the Azure DevOps Pipelines customers to check if they are impacted by this change in CDN and the changes required if impacted. Impacted Azure DevOps Service and Azure DevOps Server Customers should complete the suggested changes by May 1, 2025 and May 15, 2025 respectively. Why the change Azure DevOps Pipelines customers can configure various forms of self-hosted Agent ...
TFVC Policies Storage Updates
TFVC Check-In Policies TFVC projects can have check-in policies such as Build (Require last build was successful), Work Item (Require associated work item), Changeset comments policy (Require users to add comment to their check-in), etc. We are changing the way we store these policies on the server. This change will slightly affect TFVC users since they would need to initiate migration process from their side. Phase I – User opt-in (Apr 2025) This is a phase in progress. We provided means for users to start their migration process. Migration from obsolete policies to active ones should be done by the project a...
Important Update: Server Name Indication (SNI) Now Mandatory for Azure DevOps Services
Earlier this year, we announced an upgrade to our network infrastructure and the new IP addresses you need to allow list in your firewall - Update to Azure DevOps Allowed IP addresses - Azure DevOps Blog. This is our second blog post to inform you that starting from April 23rd, 2025, we will be requiring Server Name Indication (SNI) on all incoming HTTPS connections to Azure DevOps Services. SNI is an extension to the TLS protocol that allows clients to specify the hostname they are connecting to. All modern browsers and client software support SNI and use it by default, ensuring a seamless transition for most ...
New Overlapping Secrets on Azure DevOps OAuth
As you may have read, Azure DevOps OAuth apps are due for deprecation in 2026. All developers are encouraged to migrate their applications to use Microsoft Entra ID OAuth, which can access all Azure DevOps APIs and has the added benefit of enhanced security features and long-term investment. Although we are nearing Azure DevOps OAuth’s end-of-life, we remain committed to providing very critical security enhancements on Azure DevOps integration methods as they remain available. To this end, we’re introducing a new feature designed to improve security on existing apps and streamline the oft-disruptive secret rotat...
Introducing Java, JS and Python support in Test Plans
We are excited to announce new capabilities in Azure Test Plans that will enhance your testing workflows. This feature is currently available in Public Preview. You can find instructions at the end of the article on how to request it for your Azure DevOps project. With this latest release, we are introducing the ability to associate automated tests written in Java/JUnit (Maven and Gradle), JS (Jest) and Python (PyTest) with test cases and then run those tests with the new Azure Test Plan task. This is an addition to the ability to associate tests written in the majority of the .NET supported frameworks, which wa...
Upcoming Updates for Azure Pipelines Agents Images
Update: The Ubuntu-20.04 retirement date for Microsoft-hosted agents has been moved to April 30. On Managed DevOps Pools, the ubuntu-20.04 image will be available up to June 30. To ensure our hosted agents in Azure Pipelines are operating in the most secure and up-to-date environments, we continuously update the supported images and phase out older ones. In October 2024, we announced support for Ubuntu-24.04. Soon, we plan to update the ubuntu-latest image to map to Ubuntu-24.04. Additionally, MacOS 15 Sequoia and Windows 2025 images will be generally available later this year. Alongside these new releases, we...
Markdown for large text fields (private preview)
📢 As of April 15th, we are no longer accepting private preview requests. We have enough participants signed up to provide feedback. Keep an eye on the Azure DevOps release notes for the general availability announcement. Adding Markdown capabilities to the work item is a long-standing request. We introduced Markdown for comments in early 2024, but due to the rollout of the New Boards Hub, we put the feature on hold. Today, we’re excited to announce a private preview for Markdown support in large text fields! 🎉 🦄 How it works By default, all existing and new work items will continue using the HTML editor f...