Azure DevOps Services

Azure DevOps Services Reviews

Customer Verified

Do you work for this company? Learn how we help vendors

Ratings and Reviews
(1-25 of 338)

Companies can't remove reviews or game the system. Here's why
July 23, 2021

Azure= Agile

Score 10 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps [Services (formerly VSTS)] is being used to facilitate our sprint ceremonies and is our home to all user stories, features, epic, tasks and bugs. We use it to track our team's performance. We also use it to deploy c# code and is our code repository. Teams are able to access at any time.
  • Layout
  • Easy to access/navigate
  • Very intuitive
  • Rearrangement of features
  • More verbiage around burn down chart
  • Deployment
[Azure DevOps Services (formerly VSTS)] is well suited for agile teams. It is a digital kanban for teams to access anywhere at any time. Especially during covid when most companies are still remote, it allows teams to fully perform and still be functional in operating within an agile methodology. It also gives visibility to teams capacity.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Our organization is using Azure DevOps for a SaaS-based code repository and we also use it for tracking our Agile/Scrum processes in our Application Development and IT Operations departments. It allows a central, cloud-based solution for our tracking our CI/CD pipelines and simplifies tracking our stories and features during our two-week Sprint cycles. It is also well used by the QA for their test cases and testing.
  • Project code pipeline service.
  • Good tool for Agile practices
  • Test Plans
  • Clean n clear UI
  • Board could be more advanced
  • Pipelines should support advance tasks like database migration
  • Merging conflicts in tool
Azure DevOps is well suited as a single platform for all DevOps processes. It has everything for a product from the repository, work items board, pipelines, test plans and execution, artifacts, etc. It has also a range of project numbers and pipeline execution time for free each month to help new developers or startups. It is appropriate for teams without DevOps members and standards.
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are new to using Azure DevOps Services, we use a different tool for DevOps. This year, we have started the implementation of Azure DevOps for some applications, especially D365 applications. At the moment, we use it only for Development, QA and UAT, we haven't done any Production deployment yet, however, early next year we are going to start doing it.
  • Easy to create pipelines
  • Intuitive
  • Pipelines sometimes are really slow
  • Support needs to be improve
In our case, Azure DevOps services is well suited with applications hosted on Azure, such as D365, on-premises or custom Applications are hard to implement, different aspects won't work properly. We are still new to using it, maybe we haven't found the best way to apply it.
October 05, 2021

Azure DevOps

Score 10 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps is used by the development department, is used by the management department and quality assurance department. We are using Azure DevOps for code repository, building code, releasing code, project management, testing platform. We use Azure DevOps as a DevOps platform for continuous integration and deployment. It helps us to build and release software automatically on each made to it. It helps us in managing projects. It helps for tests (manual and automated). And does all the above integrations in one place and allows tracking.
  • Repository
  • Build Pipelines
  • Release Pipelines
  • Test Plans
  • Work Items Tracking
  • Board could be more advanced
  • Merging conflicts tool
  • Pipelines should support advance tasks like db migration for AWS
Azure DevOps is well suited as a single platform for all DevOps processes. It has everything for a product from the repository, work items board, pipelines, test plans and execution, artifacts etc. It has also a range of project numbers and pipeline execution time for free each month to help new developers or startups. It is appropriate for teams without DevOps members and standards.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps Services as our main DevOps platform for our IT projects.
The product usage changes from a project to another.
The most used capability is the agile planning tool, for Dev and non dev IT projects management.
We also use the GIT code versioning tools, along with DevOps build/deployment pipelines, in Microsoft technologies based Dev projects.
We are now planning trainings so that we can use the testing tools properly as well
  • makes Agile collaboration easy
  • DevOps made "easy" (after a learning time)
  • very clear and intuitive UI
  • very large set of connectors/integrations/extensions
  • Office 365 integration (Teams and Sharepoint)
  • plenty of training/documentation resources, and large community of users
  • the online documentation on Microsoft Developer Network should be clearer and easier to read, even for senior users
  • advanced configuration is hard to understand
  • product features changes can sometimes surprise you
You can find the whole IT project lifecycle management in one place, including project management, code versioning, build and CI-CD pipelines, alongside with testing features and bug tracking.
You also have very useful out of the box dashboards that can also easily be customized, so that you can follow your project insights.
I also used - and recommend - another Microsoft product, built on Azure DevOps services, that is dedicated to Mobile Apps DevOps management, and that is really useful : AppCenter.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps offers a wide variety of tools for a CI/CD environment and it's really useful. We are moving from a static build model to an automated one and so VSTS has the tools we need to continue growing in the future. We started using VSTS, now Azure DevOps, as a code repository only and that's the main use within our organization.
  • Private repositories
  • User management
  • Security
  • Extensions
  • Some integration with 3rd party tools or services could be better
  • Has a lot of options, but sometimes are hard to find
  • Non standard build/test workflows could be problematic
Azure DevOps Services is a great service. Its function as a code repository is great, and its integration with Visual Studio and Visual Studio Code lets you work in a natural way from these tools. MS Teams integration exists as far as we test it requires an Azure subscription, so it does not apply to the free 5 user tier.

We have been using it for at least 5 years and it's rock-solid in its function and always adds new options and features. We started using it because of its free 5 user private repositories function. Now GitHub does the same (and it's also from Microsoft) but Azure DevOps Services offers more options and tools, so we will stick with this service.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps is used for project management of our sprint tickets to assign within team and provide the dashboard information to our project managers. The user story is easy to create and assign to the owner and then create the sub-task to assign within the user for different tasks like (Development, Peer QA, Final QA e.t.c)
  • User Story
  • Dashboard
  • Sub Task Creation
  • Reporting
  • Divide sub task and timings
  • Time divide between each task
  • Integration with other tools is difficult
As the other project tool management it is good because of the part of Azure family. Being a Microsoft tools it is quite compatible with the other azure products. Azure DevOps is very useful for the operational project to create all the user stories with the same task including various ad-hoc tasks
Score 9 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps Services (formerly VSTS) is our entire enterprise deployment strategic platform. Coming from a VSTS/TFS background, it's a natural choice. Azure DevOps Services (formerly VSTS) is used for scrum product backlog management, task assignment, test case management, bug tracking, source version management, change review, and continuous integration and deployment. It's a great ecosystem and with git hub acquisition, the product is very versatile and future proof.
  • Microsoft ecosystem with one-stop solution for Agile/CICD
  • Easier integration with IDE
  • UI-based/YAML both pipeline formats supported
  • Very flexible and supports all kind of deployment
  • Should support non-Microsoft and open-source ecosystems in an easier way
  • License costs
  • Scrum boards and sprint analytics can be improved to be on par with the market
  • Notification and workflow customization should be flexible
All Microsoft ecosystem products are well integrated and support easier build automation. Especially if you use TFS and Visual Studio, this is very well suited. They are flexible in bringing open-source software build supports and have a great marketplace with lots of Azure DevOps Services (formerly VSTS) extensions available.
The support team is well trained to help with troubleshooting issues and responds quickly but generally couldn't influence much to bring feature enhancement to their roadmap as we need.
Mark McCully | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Our company is using Azure DevOps for a SaaS based code repository and we also use it for tracking our Agile/Scrum workflows in our Application Development and IT Operations departments. It allows a central, cloud-based solution for our tracking our CI/CD pipelines and simplifies tracking our stories and features during our two week Sprint cycles.
  • Highly customizable
  • SaaS platform - so no infrastructure maintenance needed
  • Easy to use
  • We have encountered a few bugs and issues while using ADO.
  • Features can be added or removed without customer input.
  • We have seen some of our stories and bug tracking issues mysteriously disappear in ADO.
Azure DevOps is an excellent option for companies looking to streamline their development pipeline and code repository. It is highly collaborative and extremely easy to use. Our company is also using it within our IT Operations department to track infrastructure related work efforts as well and it has been very successful for that as well. Smaller companies may be able to use GitHub and other cheaper solutions for this type of work.
Sean Patterson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps internally to manage some of our hardware projects, leveraging the project management and resource sharing features of the platform. With various clients, we leverage the code repository and pipeline features in addition to project management to provide a full fledged CI/CD development workflow for new and continued work.
  • Full project pipeline service.
  • Good story/task management.
  • Robust pipeline.
  • Pipeline configuration.
  • Multiple-repository management per project.
  • Permissions management.
Azure DevOps provide a great resource when you want a "soup to nuts" approach to building software and tracking its deployments and updates. Using the project board to create stories and tasks, you can easily create code branches in which to do the work, which provides a great audit trail to when bugs were fixed or features completed. By using the pipelines, you can allow automation to deploy completed work, track its history, and easily roll back if needs be.
Score 10 out of 10
Vetted Review
Verified User
Review Source
I utilize many of AzureDevops features:

1) Repos
2) Boards
3) Pipelines
4) Artifacts

It is being used Organization wide and helps us solve with our software development and deployment.
  • Azure DevOps is great at managing and securing git repos. Reviewing pull requests and seeing diffs is great. You can even communicate back and forth with your team members right there in the code review screen.
  • Pipelines is a powerful feature for allowing you to deploy to anywhere (cloud, on prem, etc.) You can secure your pipelines and track your artifacts with ease.
  • Boards is a great tool for managing your work task as well as associating your commits with the work item.
  • I love Azure DevOps. I can't think of anything that requires improvement.
It is well suited for managing software development. Code management, deployment, work item tracking. It allows remote teams to work together easily.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps Services (formerly VSTS) is being used by the entire company to provide a solution to continuous integration and continuous delivery. We host our code base on Azure DevOps Services (formerly VSTS) and build delivery pipelines with it. It shortens our software development cycle and helps ensure the quality of our deployment. We are very happy with it.
  • Rich features
  • Powerful tools
  • Integrations with different kinds of tools
  • Clearer logic for each component
  • Provide more example pipelines
  • More detailed documentation
if you need a CI/CD pipeline for your company, especially if you have already been using Microsoft Software Development Suite, Azure DevOps Services (formerly VSTS) is a very good choice. You can build a release pipeline very easily and deploy your applications very quickly. They are also easy to maintain, especially if you are a big company.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps or ADO (as we call it) is used by the IT department in developing and also transforming multiple legacy applications to Modern Microservices based applications and architecture. It enables seamless development by offering multiple tools that are required to develop modern applications in Agile-based methodologies. It enables seamless Continuous Integration, Continuous Deployment (CI/CD) process, and everything is bundled in a user-friendly manner.
  • Azure DevOps bundles all the useful tools together in a seamless way.
  • Sprint boards, Code repositories, Pipelines etc. all can be managed from a single application.
  • Facilitates easy collaboration between technical members and business or product owners.
  • Facilitates parity between different environments by providing a single source of truth for all pipelines.
  • Azure DevOps Sprint boards can be improved, similar to Jira (this can be my bias).
  • Teams and Azure DevOps integration can be improved in-terms of updates of stories or tasks.
  • Pipeline job logs and their web console views can be improved.
It is well suited for large and distributed teams, developing cloud-native applications in a fast fail-fast approach. It will enable seamless development and support different platforms in integrations. It is of less value if the teams are small and located together and also in cases where the application runs on legacy software.
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps/VSTS for the entire agile approach to software development at the organization I work for. We use Azure Boards for managing work in sprints, providing us with live features for planning & retrospectives. We use the Azure Repos feature for Git version control of our code and for PR processes, and pipelines & releases for building, linting, and testing code & deploying code to multiple environments via a continuous integration approach. We use Azure Artifacts to host our NuGet packages to be used by multiple projects for code reusability.
  • Git repositories feature is fully featured with a friendly web interface.
  • Azure pipelines & releases are very flexible for CI/CD practices.
  • Azure Boards allows linking work items to code and for a closer relationship between code & the sprint rather than using a secondary piece of software like JIRA/Trello.
  • User interface looks nice but it can often be quite hard to find things that you need.
  • Many features are now being ported over to GitHub, in a more fleshed-out way (e.g. GitHub Actions), after the Microsoft acquisition.
  • Documentation can be limited.
Primarily best for Microsoft dev houses (C#/.NET, TypeScript/JavaScript). Provides all the features you'd expect for an agile development workflow all in one package.
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using Azure DevOps across most teams, leveraging both Kanban and Scrum methodologies. The tool is used for SDLC workflow, source control, and documentation.
  • Source control integration.
  • Templates for multiple Agile types.
  • Document management (implement something similar to Sharepoint libraries).
  • Streamlined permissions structure.
Azure DevOps, on the whole, is very easy to set up and use if you have any experience with Agile processes. The initial barriers to entry are extremely low as the first 5 users can leverage the tool for free. I found the overall feature/functionality easier to use and more approachable than similar tools. It is also leaps and bounds better than TFS if you haven't looked at it in a while. If you are already a git user, this is directly integrated with git repos, making the transition easy. The tool is also integrated with many other Microsoft products, so if you are a Microsoft-centric shop, you can leverage the broader ecosystem.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Amy Liston | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We are using Azure DevOps to manage the workflow for all of our software development teams. We use this software to provide team metrics, identify team dependencies and manage agile boards. We also use the software to manage pull requests.
  • Agile Management.
  • Metrics.
  • Customized Reporting.
  • Scaleable Team Projects.
  • Column sorting when in filtered states.
  • A way to show cross-team dependencies.
  • A customized "From" field for notifications. Sometimes when a mail comes from Azure DevOps the teams do not realize that I am sending it
  • A way to do online poker that doesn't require a plug-in.
Before using Azure DevOps, the department was calculating metrics by hand. It was a very tedious process that, at times required duplicate effort. Once we added the online boards, we were able to let the cards automatically calculate dates and provide us with team metrics instantly. It is also great for being able to easily move features from one team to another. Before we added all teams in the same project, it would require us to re-enter the features. We move features around a lot so that has been a big help. I also like the board customization, not all of our teams follow the exact same Agile flow, so allowing each board to have its own columns, states, and notifications give flexibility to each team.
I have had to reach out to tech support a few times and I always received a quick response that answered my question. Everyone was very knowledgeable and courteous when they were trying to help me through my problems.
Kyle Kochtan | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Azure DevOps is currently used across the organization. Currently not all groups and departments are utilizing it however we are in the process of rolling out to these groups. Azure DevOps has become our go to application for development. We are using it for full development life cycle, code repository, testing, deployment and verification.
  • Once set up it makes deployments to various environments a breeze
  • YAML backend is a huge plus
  • Large groups can work on the same solution seamlessly
  • More streamlined set up of CI/CD
  • Better error messaging to explain why sometimes a build is successful and sometimes not
  • Easier set up of deployment tools
Azure DevOps is by far the leader out there. If you are a Microsoft shop there is no need to look elsewhere. This will handle everything you have with ease and then some. If you have older code then you may need to build some customizations to make it work but anything recent is seamless.
Azure DevOps has both excellent paid support from Microsoft and plentiful support online. Microsoft has plentiful sites that show step by step how to do many functions and features. The forums are well stocked with lots of useful information and there are many third-party sites that can easily be found to help out as well.
Vinicius Lima | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Azure DevOps to manage all our projects across the whole organization. The project manager usually translates all software requirements to Azure DevOps and assign appropriate tasks to programmers. It is a very flexible tool to implement DevOps methodology. The project development is followed through the platform, as well as the team performance.
  • Easy representation of software requirements in user stories and tasks.
  • It allows the tracking of activities and team performance
  • It allows interaction between team members in a specific task
  • You can use only a few tools to complement your existent workflow
  • There is a free version for small teams (up to 5 users)
  • Some small improvements could be done in the user interface.
  • Sometimes the performance is low (some requests/queries are slow)
Azure DevOps allows you to start with DevOps methodology in a fast and easy way. The graphical interface is great and it is suitable to small and big teams. It really helps you to manage projects, tasks and teams.
The support is great. Attendants are very friendly and, so far, all requests and responses were satisfactory.
Maria Sousa | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We're implementing entire product workflows with Azure DevOps: building, testing, staging and deploying. It's the perfect companion for Visual Studio and Git, so everyone just loves using it. It's a dream come true not having to switch to different front-ends to get our job done throughout the day, while keeping an amazing user experience.
  • Unified environment for all DevOps tasks and procedures
  • Amazing User Experience within a beautiful UI
  • Great marketplace extensions collection
  • Code merging has room for improvement
  • Such a broad set of features can become confusing for the novice user
It's a great way to normalize DevOps wokflows, allowing you to replace lots of different tools and get the job done with a unified package. Testing support is second to none. If you're just focusing on development with version control, than Visual Studio packed with Git will probably cover all your needs.
Agenor Roris Filho | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
It is being used by the IT Department to manage all steps of the main software development project, and the improvement and integration of the internal TMS (Transportation Management System). Consultants, analysts, developers, the Scrum Master, and the product owner can collaborate and control all their activities, with high visibility of the progress and particular issues. Enabling the Scrum work item template allowed the use of agile techniques and control over a highly demanded product backlog.
  • It offers an easy relationship between product backlog items, development tasks, and the source code changes.
  • No overhead management tasks, people keep focused on product development and it reduces work time.
  • Dashboards show the summary of the most important indicators, and offer different views for distinct professional roles, keeping people in touch with entire progress.
  • Full support for Scrum artifacts and processes.
Team System is the best solution if you use Visual Studio Professional or Enterprise as your main development platform, especially if you have a Microsoft Enterprise Agreement. Even though it can be used with any development project management framework it is better in an informal environment using Scrum.
AMANDEEP KUNDRAO | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using Microsoft VS (2010,2013,2017) with the integration of Team Foundation Server(TFS) with it. We are using it to keep track of the whole software development life cycle. Each developer regularly checks code changes with the addition of Visual Studio to the TFS. As for the integration side, we are using it to clean , build, and deploy the code changes to different servers to upgrade them to the latest version.
  • Visual Studio supports many languages like C#,HTML.C++ and many others. We can also make Visual Studio to support other different languages with the help of plugins, like for Java, Python, etc.
  • We are using TFS with the VS, so it makes it easy to track the code and project changes, and if required we can also track the code of every single line to see what it means, by whom this code is written, and for which problem.
  • A unique work item change order number is assigned to the changes that you are making, apart from your shelveset creation
  • We can create the build definition through which we can automate the deployment and upgrade processes.
  • It provides a lot of menus and options/templates through which we can make our computer application for enterprise or for non-enterprise
  • We can easily integrate our customized/required menu in the VS through registry files or through deployment of the code
  • Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
  • Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
  • Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
  • With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
  • If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
It has been a great tool when comes to code compilation. As a developer, it helps a lot for us to find issues in the code, as Microsoft Visual Studio Team System has the best debugging tools. We can also check the code line by line to find the exact line where the error is. Developers can also place their important code at their shelveset and can easily get it from there when they need to. As for integration, it helps us to compile large code and deploy the changes with a single GO.
Glenn Jones | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source
VSTS is currently being used by one department at work but was I brought it into the company about six years ago. We currently use VSTS as a building and testing tool. We set up the builds and create tests to run after a build is successful. When I first started with VSTS I set it up to run on a daily basis and then had the developers correct the problems that were shown by the tests. This works very well and the developers like using it since they did not have to keep on integrating their changes together.
  • VSTS has a wonderful integration with Team Foundation Source control and Git. This is good because these were two source control systems that we used.
  • VSTS can be scheduled to run its builds and test at various times of the day. This means it can in the middle of the night and be ready for the developers when they get in in the morning.
  • VSTS handles Microsoft builds very easily. Building a .Net application can be set up with almost no work. You just have to use the Visual Studio solution that was used by the developers to create the application.
  • VSTS is very Microsoft centric. If the application you want to build is not based on Microsoft items such as C#, or Visual Basic it is very difficult to use.
  • If you are using the latest version of VSTS then you will find a documentation problem. It can be very hard to find methods and help trying to get something running.
  • Passing data between VSTS build steps is not easy. It can be done, but it is not a normal thing that you would Microsoft would have put into their product.
If you are building a build system for a Microsoft product that doesn't have a lot of steps, VSTS is something that should be looked at. If you want to deploy your application to Azure it is even better. Running Visual Studio to build, run tests and perform load and performance tests works very well. Just be prepared to have your initial setup take some time.
Gordon Lo | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Microsoft Visual Studio Team System (VSTS) is being used currently only by IT and a few select people in the business unit. The main goal of using VSTS from the business perspective was to improve communication, work item management, improve planning and increase visibility into product management. For the developers in IT, it was imperative to have more integration between business requirement and code, moreover, it also expedited development workflow (code reviews, etc).
  • Work item management is fantastic and easy to use. It can be used as simply just tracking tasks, or as complex as tracing work items from multiple projects being assigned to a single developer. Work items can be customized easily to meet the needs of your organization as well, and it isn't difficult to manage the customization.
  • Source code management is excellent and tied directly into VSTS. You have a choice of TFVC or GIT management options - we've switched to git and have not looked back. It is fully featured and commits can be tied directly to a work item using # tags.
  • Metrics/dashboard - being able to write simple queries and move them to a dashboard in a few minutes is great. It enables team managers a quick board to review the status of a project and quickly act on any issues cropping up.
  • Build and release management - if you don't have this... you'll want it. The integration is magic, the interface is easy, and to setup an automated build using the hosted agent was a breeze. We did have to purchase an additional license because of the number of builds we had, but it was worth it.
  • VSTS has a log of flexibility... almost too much. It's hard to actually decide how best to use it until you just set it up and try it out.
  • Currently getting a list of work items on the main home page is messy. There's no hierarchy so it can sometimes be just a blast of work without any sorting or prioritization settings. There's a simple work-around to simply create a query for yourself and enable "search across multiple projects". That works alright, but it would be a better experience if the home page had this already covered.
  • Teams management could be better. It's a little confusing, and not easy to setup. Our specific use case of having some teams able to only see their backlog and nothing else was not achievable in the current implementation of VSTS. As a result, whenever we have to contract out work, we end up creating a new Team Project. It's not all bad, because team project contents can be easily migrated to another project, but it's still a bit annoying.
Anyone who is currently using TFS should migrate to VSTS immediately. Having maintained TFS servers in the past, this is substantially easier. Additionally, the web interface has gotten easier to use and features to move work items between projects has improved greatly. We're also in the process of migrating away from our Atlassian toolset - so it gives you an idea of how versatile the product really is.
Rahul Kumar Singh | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Microsoft Visual Studio Team System is being used by the dev team in the organization. As every developer is a part of a project, every developer has to access the TFS (team foundation server) in order to contribute to the project. MVSTS is solving some major business problems. For example, it allows version control of a file as the whole team is working on the project. TFS provides each developer a local copy of the file, as well as the server version. Developers can make the changes to their local file and test it and if everything goes well, then they can update it on the server for the customer.
  • Version control of the files: each developer has access to the server and regularly gets the latest server changes in his local box. The local file is maintained and also remains updated with the server version. The program also provides a different copy of a file so that it can be recovered in case of a failure from any individual developer box.
  • Some features like shelveset creation, work item monitoring, and publishing the project database.
  • I can access any developer's local box and see what changes he is doing if he has shared the shelveset with me.
  • Applying any new changes and undoing them using the pending changes feature.
  • Once, I added a PDF file to my shelveset so that I could share my changes with my team, but they were unable to unshelve my changes. This is because PDFs cannot be opened in more than one box, and it was locked on my box. So, I had to undo it from my box, and even then it was only accessible to one person at a time. It was problematic. They should at least be able to open it in read-only mode.
  • Lots of settings are necessary. However, if you accidentally uninstall one, instead of having to install it again, there should be a backup kind of thing for my profile settings in Visual Studio.
  • The default compare and merge tool provided by Visual Studio does not fill our needs, and we need to install other products like Delta Walker or Araxis Merge.
For large project or a large team, the product is well suited when this technology is already implemented, because nowadays for version control there are products like GitHub. For a company who is concerned about security, this is a way to make their projects accessible from their TFS, and no one can use it for personal use. This is also useful for maintaining a site that a group of developers are working on, where their work items need to change, like peer test, peer review etc.
Carlos Alberto Pedron Espinett | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
VSTS is being used in our organization as the IDE standard of the development team, allowed thanks to its provision team foundation a better organization and delegation of functions in the work team. Visual Studio has allowed an efficient and effective organization and delegation of the work assigned to the development department, which has triggered a significant diversification in the market occupied by the company I represent.
  • It allows you to incorporate different languages, or written code in different encoding to the workflow without affecting the development to which it is oriented
  • By using the Entity Framework you can establish the database design of the system in a correctly standardized and highly efficient way
  • The debugging options allow you to have control of the code that is being made, in addition to having a large amount of plugins that allow to use this feature in different languages
  • There are few things that we can say in a negative way because a pending issue was the license and Visual Studio has a lite option that although it does not have all the features of the full version, allows you to fulfill the work planned
  • The download size of the full version is usually very long and can take a long time to get it
  • In case of applying the entity framework in non-standardized tables (already existing projects) it generates inconveniences in the creation of the entities
VSTS is a software that can be used by advanced programmers, and it is also an excellent option in a team of developers that begin to train and become familiar with an IDE. It can be used in large development teams or in particular developments is perfectly adapted to the needs of the developer.

Azure DevOps Services Scorecard Summary

What is Azure DevOps Services?

Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities, along with the basic plan which includes:
  • Azure Pipelines: automatically builds and tests code, combines continuous integration (CI) and continuous delivery (CD)
  • Azure Boards: Work item tracking and Kanban boards
  • Azure Repos: Unlimited private Git repos
  • Azure Artifacts: 2 GB free per organization
The Basic + Azure Test Plans bundle can be used to allow users to test and ship with confidence using manual and exploratory testing tools.

Azure DevOps Services Video

Introduction to Azure DevOps

Azure DevOps Services Competitors

  • CA Agile Central (formerly Rally)

Azure DevOps Services Pricing

More Pricing Information

SaaS Editions Pricing
Pricing DetailsTerms
Basic Plan$6per user per month (first 5 users free)
Basic + Test Plan$52per user per month
Azure Artifacts$2per GB (first 2GB free)
Azure Pipelines - Microsoft Hosted$40per parallel job (1,800 minutes free with 1 free parallel job)
Azure Pipelines - Self-Hosted$15per extra parallel job (1 free parallel job with unlimited minutes)

Azure DevOps Services Technical Details

Deployment TypesSaaS
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

What is Azure DevOps Services?

Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.

What is Azure DevOps Services's best feature?

Reviewers rate Support Rating highest, with a score of 8.7.

Who uses Azure DevOps Services?

The most common users of Azure DevOps Services are from Enterprises and the Information Technology & Services industry.