We’re thrilled to announce that Azure DevOps Server is now generally available (GA)! This release marks the transition from the Release Candidate (RC) phase to full production readiness, delivering enterprise-grade DevOps capabilities for organizations that prefer self-hosted solutions.
You can upgrade directly from Azure DevOps Server RC or any supported version of Team Foundation Server (TFS 2015 and newer). Head over to the release notes for a complete breakdown of changes included with this release.
Note: Team Foundation Server 2015 reached the end of Extended Support on October 14, 2025. We strongly recommend upgrading to Azure DevOps Server to maintain security and compliance.
Here are some key links:
We’d love for you to install this release and provide any feedback at Developer Community.
Hi Gloridel
Can you also enlighten us if the PublishPipelineArtifact/DownloadPipelineArtifact will finally be supported by Azure DevOps Server?
https://github.com/microsoft/azure-pipelines-tasks/issues/19698
Hi Tore
At this time, PublishPipelineArtifact are not supported on Azure DevOps Server. This capability has an architectural dependency on Azure Storage, which isn’t compatible with on-premises deployments.
Hi Gloridel
Would it then be possible to get someone to look at the issue with current versions of UploadBuildArtifacts/DownloadBuildArtifacts
https://github.com/microsoft/azure-pipelines-tasks/issues/19829
https://github.com/microsoft/azure-pipelines-tasks/issues/6830
https://github.com/microsoft/azure-pipelines-agent/issues/1480
1480 is a good example that reports of an issue being closed because there is a new taks available: PublishPipelineArtifacts, which is not supported on-prem.
Hi Gloridel
I wonder if you could push for a fix of the WMIC issue that happens when tests are rerun on Windows Server 2025:
https://github.com/microsoft/azure-pipelines-tasks/issues/21123
We try to keep our infrastructure up-to-date, so it is an inconvenience if the pipeline tasks depends on deprecated Windows features.
Thank you in advance!
Hi Tore
Thank you for flagging the WMIC issue you’re seeing when rerunning tests on Windows Server 2025. I’ve forwarded this to the engineering team so they can investigate further. We’ll follow up once we have more details or next steps.
Greetings.
Previously, we’ve had:
Is this latest new release supposed to be:
If “yes”, then I’d like to report a bug, that this release is missing “2025” from the product title.
If “no”, then could you inform us when can we expect the “Azure DevOps Server 2025” release, please?
Thank you.
Best regards.
hi Aeon,
the year is no longer part of the product name.
you can read about the renaming of Azure Devops Server in this posting:
https://devblogs.microsoft.com/devops/announcing-the-new-azure-devops-server-rc-release/
Hi Stephen, you can find the Build number in the Azure DevOps Server build documentation
What is the actual version number for this release, and why doesn’t it get a versioning label in the release documentation?
Hi Stephen, you can find the Build number in the Azure DevOps Server build documentation.
May I suggest that you make the build version as obvious and accessible as possible, so it is easy to find and track? Right now, unless users are informed already, they must do some digging. I believe all release related communications should include an obvious version label in the title, or at least in the main description somewhere. Additionally, the version history and release dates should be just one click away, with the link included on any page referring to the latest release.
They don’t publish them anymore, which is why I created a complete list with all version numbers: https://github.com/FokkoVeegens/AzureDevOpsServerVersions. Hope it helps you.
Hi there appears to be a bug in this version with the newer version of CodeSearch provided.
When running Configure-TFSSearch.ps1 and installing code search on a separate Server/Tier it gives a error as below at the high level and the service never starts.
<code>
If you dig into the elastic logs a bit further this is the actual error. It appears somewhere is setting instead of when running?
<code>
Can this be looked at and fixed/patched please.
Thanks
Hi Luke, thank you for bringing this to our attention. I wanted to let you know that I’ve shared your message and the details you provided with our engineering team for investigation. They’re currently reviewing the issue, and I’ll follow up with you as soon as we have an update or if any additional information is needed from your side.
Thanks again for flagging this, and we appreciate your patience.
Hello Gloridel
Does this version include support for VS2026 (vsbuild, vstest, mstest) in the pipelines?
and what about “Automate work item state transitions” which you stated that it will be added to the release notes (still not there….)
Hi Liran, this version does not support VS2026 (vsbuild, vstest, mstest) in pipelines. We plan to add support for on-prem once it is fully deployed in the hosted version of the product.
The release notes for Boards were updated to remove Automate Work Item State Transitions since this feature is not included in the current release.
Hi Igor
Good to hear that it will be handled.
I wonder if it would make sense to already now think of Visual Studio 2027 / 19.0 that will be release in November 2026:
https://devblogs.microsoft.com/visualstudio/visual-studio-built-for-the-speed-of-modern-development/#built-for-modern-development
this comment has been deleted.
Hi Gloridel
I am a bit curious as to how this will be done and if it will also be done for the other supported versions of Azure DevOps Server e.g. 2022.
According to this comment VSTestV2 will not be corrected, but VSTestV3 is not (currently) supported by Azure DevOps Server 2022:
https://github.com/microsoft/azure-pipelines-tasks/issues/21319#issuecomment-3636088731
Hi Tore,
The plan to patch changes to the VsTest v2 task, to support VS ’26. Sometime in the future, we will make the VsTest v3 task available in Azure DevOps Server.
Regards,
Igor