Update March 13, 2026: We have released a patch that resolves the issue introduced in the original Azure DevOps Server release that, under certain conditions, could cause group memberships to become deactivated.
Who should install Azure DevOps Server Patch 2
- This patch applies to customers who installed Azure DevOps Server prior to the March 13, 2026 re‑published release. If you previously applied the mitigation described in earlier guidance, installing Patch 2 completes the remediation. Customers who have not run the mitigation script do not need to do so, installing Patch 2 is sufficient.
Who does not need this patch
- Customers performing new installations or upgrades using the re‑published release available as of March 13, 2026.
Update March 13, 2026: Azure DevOps Server Issue Resolved and Release Re‑Published
We’re happy to share that the previously identified issue affecting Azure DevOps Server has been resolved, and the corrected release is now available. You can now proceed with new installations or upgrades using the previously published links. If you delayed upgrading due to the earlier issue, you can now safely move forward.
If you previously installed Azure DevOps Server before the re‑published release, please ensure you follow the mitigation instructions shared in our prior update to prevent additional impact. Those steps remain the recommended guidance for affected environments.
We appreciate your patience while we addressed this issue.
Update February 25, 2026: We have identified an issue affecting Azure DevOps Server that, in certain scenarios, may result in group memberships becoming deactivated.
We are actively investigating the root cause and working on a permanent fix. As an immediate precaution, we have temporarily removed Azure DevOps Server download links to prevent additional impact. If you have already upgraded, we recommend applying a mitigation step to stop further impact while we finalize the resolution. This mitigation involves running a vetted SQL script against the configuration database to prevent additional data from being affected.
- Mitigation Script: IdentityPatch4ConfigDB.sql.txt
- SHA-256: D462BA1C8789456CF62805398A4957E9270EB9BDE00EFA5BEBEF5FE2DE1D12B0
We will share detailed guidance, next steps, and an updated release as soon as they are available. In the meantime, support remains fully available if you need assistance. We will continue to update this blog post as more information and guidance become available.
Thank you for your patience while we work to address this issue.
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,
I’m in the process of planning a migration from Azure DevOps Server to Azure DevOps. However I find that the migration tool for 25H2 has not yet been published. Do you have an ETA for when we can expect this to be released? The old tool is at Azure DevOps Server to Azure DevOps Services Data Migration Tool.
Cheers,
Dave
Hi Dave,
We don’t have an ETA to share yet, migration support for Azure DevOps Server is still being tested.
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.
this comment has been deleted.
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/