Since I haven't used another solution, my ability to suggest improvements for Microsoft Azure DevOps Server is limited. From my experience, the operating and server handling aspects are very easy, so there isn't much need for improvement in those areas. While the solution performs well overall, it would be beneficial if they provided quick links for immediate access to support when queries arise. The improvement needed is primarily in the speed of resolution.
The UI itself is not always intuitive, often requiring extra steps. The entire UI appears to be designed from an engineer's standpoint, which can make it challenging to navigate without spending time learning the system. Regarding metrics, we aim to measure delivery speed, but the Azure Pipelines functionality is not always comprehensive. For example, measuring delivery time from pull request creation to production deployment requires extra configuration steps that are not available out of the box. The DORA metrics tracking requires building a custom solution as it's not available in the Microsoft Azure DevOps Server suite by default. A significant challenge is that GitHub Copilot is not integrated with Microsoft Azure DevOps Server directly. Microsoft recommends switching to GitHub repositories to use Copilot, which means losing the benefit of having everything in one place. This requires using two tools, enabling integration, and dealing with different UIs and workflows. The Microsoft Azure DevOps Server team doesn't always address community requests promptly. Some simple requests remain unaddressed for up to five years, such as the ability to configure commit prefix behavior on pull request closure. Certain elements are hardcoded in the planning tool. For instance, while user stories work and track progress correctly, custom item types such as technical debt or technical work do not calculate properly.
The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with internal and external processes.
Accessibility switches available on the desktop should also be available on mobile devices for coding or developing on the go. Technical support is a bit lagging so could be improved.
Learn what your peers think about Microsoft Azure DevOps Server. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
Process Manager at a marketing services firm with 201-500 employees
Real User
2021-09-03T09:39:37Z
Sep 3, 2021
It would be nice to see some of the authentications compacted to the solution which are done with Nudi. Support response time could stand improvement. The price could be better.
I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see.
The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved. This includes assigning tasks, as well as reviewing those that are pending or ongoing. For example, Jira has an excellent user experience, and it should be more like that. We would like to see better integration of documentation.
We are looking forward to the new Blazer system that is coming out soon. It is currently in beta on the service side, so we are looking forward to the new version that will be on the client side too. I also would like to see an improvement in the technical support.
.Net and MES Architect at a manufacturing company with 1,001-5,000 employees
Real User
2019-09-10T09:04:00Z
Sep 10, 2019
I would say compared to some more modern tools which are made to work offline, with this solution you have to be connected all of the time and with a central server. In our case, it's not a big problem because we all work on-premises, but it can be an issue if you have teams in different locations. Then you don't have synchronization. I would say it's the main problem - I would love to see a better way to work offline. I think the new version allows you to choose to have different source control. But we use VPN, so we can bypass and still be connected to the company. So it's okay for us and we are on a very small scale, only ten users. So it's easy to manage.
Microsoft Azure DevOps Server is a comprehensive platform for managing software development processes, offering tools for code management, lifecycle development, and project tracking, supporting remote repositories and continuous integration.Azure DevOps Server is known for its scalability, robust framework, and efficient version control. It enhances usability through features like campaign boards, sprint planning, and project status tracking graphics. Users appreciate its source control and...
Since I haven't used another solution, my ability to suggest improvements for Microsoft Azure DevOps Server is limited. From my experience, the operating and server handling aspects are very easy, so there isn't much need for improvement in those areas. While the solution performs well overall, it would be beneficial if they provided quick links for immediate access to support when queries arise. The improvement needed is primarily in the speed of resolution.
The UI itself is not always intuitive, often requiring extra steps. The entire UI appears to be designed from an engineer's standpoint, which can make it challenging to navigate without spending time learning the system. Regarding metrics, we aim to measure delivery speed, but the Azure Pipelines functionality is not always comprehensive. For example, measuring delivery time from pull request creation to production deployment requires extra configuration steps that are not available out of the box. The DORA metrics tracking requires building a custom solution as it's not available in the Microsoft Azure DevOps Server suite by default. A significant challenge is that GitHub Copilot is not integrated with Microsoft Azure DevOps Server directly. Microsoft recommends switching to GitHub repositories to use Copilot, which means losing the benefit of having everything in one place. This requires using two tools, enabling integration, and dealing with different UIs and workflows. The Microsoft Azure DevOps Server team doesn't always address community requests promptly. Some simple requests remain unaddressed for up to five years, such as the ability to configure commit prefix behavior on pull request closure. Certain elements are hardcoded in the planning tool. For instance, while user stories work and track progress correctly, custom item types such as technical debt or technical work do not calculate properly.
The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with internal and external processes.
The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms.
Improvement-wise, I would like customer support to be more friendly. The overall customer support needs to improve.
Accessibility switches available on the desktop should also be available on mobile devices for coding or developing on the go. Technical support is a bit lagging so could be improved.
It would be nice to see some of the authentications compacted to the solution which are done with Nudi. Support response time could stand improvement. The price could be better.
I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see.
The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved. This includes assigning tasks, as well as reviewing those that are pending or ongoing. For example, Jira has an excellent user experience, and it should be more like that. We would like to see better integration of documentation.
I would like to see the inclusion of more programming languages, especially better support for Java.
We are looking forward to the new Blazer system that is coming out soon. It is currently in beta on the service side, so we are looking forward to the new version that will be on the client side too. I also would like to see an improvement in the technical support.
I would say compared to some more modern tools which are made to work offline, with this solution you have to be connected all of the time and with a central server. In our case, it's not a big problem because we all work on-premises, but it can be an issue if you have teams in different locations. Then you don't have synchronization. I would say it's the main problem - I would love to see a better way to work offline. I think the new version allows you to choose to have different source control. But we use VPN, so we can bypass and still be connected to the company. So it's okay for us and we are on a very small scale, only ten users. So it's easy to manage.