We are releasing patches for our self‑hosted product, Azure DevOps Server. We strongly recommend that all customers remain on the latest, most secure version to ensure optimal protection and reliability. The latest release of Azure DevOps Server is available from the download page.
This patch applies to the most recent version, Azure DevOps Server, and includes the following updates:
- Fixed an issue where completing a pull request could fail due to a null reference exception during work item auto-completion.
- Improved validation during sign out to prevent potential malicious redirects.
- Fixed creating PAT connection to GitHub Enterprise Server.
⬇️Azure DevOps Server Patch Download
| Version | Patch Download | Release Notes |
|---|---|---|
| Azure DevOps Server | Download Patch 3 | Release notes |
✅Verifying Installation
To verify that the patch is installed, run the following command on the Azure DevOps Server machine using the patch installer you downloaded:
<patch-installer>.exe CheckInstall
Replace <patch-installer> with the name of the patch file you downloaded. The command output will indicate whether the patch is installed.
Hi Gloridel,
We upgraded from Azure Devops 2022.2 patch 7 to Azure Devops server in our acceptance environment and Team Calendar and Retrospectives extentions from Microsoft DevLabs stopped functioning.
The calendar page would load forever and the Retrospectives page would display the following error.
"We are unable to retrieve the list of teams for this project. Try reloading the page."
Uninstalling and installing both plugins fixed the issue however we lost all our data in Retrospectives extention.
Is this something you can reproduce at your end and what is the recommended fix as we would not like to lose our retrospectives data in production for...
Hi Pål Aslan, our team doesn’t support the Retrospectives extension, so we’re unfortunately unable to validate or reproduce the behavior directly on our side. I’d recommend opening an issue directly with the extension owners so they can help investigate the upgrade compatibility scenario and provide guidance on data preservation or recovery options.
Hi,
We have upgraded to Azure DevOps Server 25H2 and applied Patch 3. Despite the update, we are still facing a critical regression when creating new SSH Service Connections.
The process fails with the following error:
Method not found: ‘System.String Microsoft.VisualStudio.Services.ServiceEndpoints.Common.EndpointStringResolver.ResolveVariablesInMustacheFormat(System.String)’
This seems to be a mismatch in the internal assemblies of the 25H2 release. This issue is already documented on the Developer Community (Ticket #11058132), but it remains unresolved even with the latest April patches.
This is a blocking issue for our teams as we cannot create new connections for our pipelines. Could you please confirm if this fix is scheduled for the May...
Hi Quentin, just following up to check whether you’re still experiencing this issue after upgrading to Azure DevOps Server 25H2 Patch 3, or if there have been any changes/workarounds identified on your side since the original DevComm ticket was closed. If the issue is still occurring and blocking your teams, please open a support ticket so the support team can help investigate further and engage engineering as needed.
Hi Gloridel,
We are currently running Azure DevOps Server 2022.2 Patch 7 and are planning to upgrade to the latest Generally Available version. I haven’t been able to locate clear guidance in the documentation, so I’d appreciate your advice on a few points:
Upgrade approach: Is an in-place upgrade from 2022.2 Patch 7 supported, or should we plan for a side-by-side installation alongside the existing environment?
Server setup: Would you recommend performing the upgrade on the current Windows Server, or is it better practice to deploy the new version on a separate server?
Pipeline agents: Will our existing agents remain compatible after...
Hi Magnus, you can upgrade directly in‑place from Azure DevOps Server 2022.2 Patch 7 to the latest GA version, but a side‑by‑side upgrade on a new server is often preferred for lower risk, testing, and rollback flexibility.
In‑place upgrades are simpler and preserve your existing configuration, while side‑by‑side deployments allow validation before cutover.
Existing pipeline agents will continue to work but updating them after the upgrade is recommended to ensure compatibility with newer capabilities. Here are a few links to documentation:
* Upgrade your deployment to the latest version of Azure DevOps Server
* Configure a backup schedule and plan
Hi Gloridel,
Apologies for raising this directly here, but we have now been waiting months on one of these issues, and progress continues to loop without resolution.
Is there any way you can escalate the following two critical Azure DevOps Server 25H2 issues below to the Product Group, given that both remain unresolved even after Patch 3?
Bug/Issue 1: was reported and triaged and "This issue has been reported to the Product Group. Updates will be shared as soon as they are available." on Feb 16, 2026.
Since then, the issue has been reset back to “New”, and there have been no...
Hi Luke, thanks for raising this and I completely understand the frustration given the timelines and impact you’ve described. I’ve captured both issues and will escalate them to the engineering team with the latest context. I’ll follow up as soon as I have an update.
Appreciate your continued patience and willingness to help drive this to resolution.