Skip to main content
TrustRadius
Azure DevOps Server

Azure DevOps Server
Formerly Team Foundation Server

Overview

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…

Read more

Learn from top reviewers

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

38 people also want pricing

Alternatives Pricing

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 New Relic?

New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.

Return to navigation

Product Details

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Azure DevOps Server Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

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

The most common users of Azure DevOps Server are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 32)

Happy User of Azure DevOps Server

Rating: 10 out of 10
December 03, 2019
KC
Vetted Review
Verified User
Azure DevOps Server
1 year of experience
I am currently using Azure DevOps Server with a client on a scrum project to build a business application. In the company, Azure DevOps Server is mostly used by our specific project but does have other users and different projects. It helps manage the scrum process and provides organization and clarity to a project with many moving parts and members.
  • Organization of tasks per team member
  • Statistics provider for data related to capacity and output
  • Good UX/UI experience for clarity
Cons
  • Copy/Paste functionality could be improved
  • Ability to see all team members more clear visually
  • Sort feature on columns could be better
Azure DevOps Server is a great tool for keeping large projects organized. It is well suited for building large, business applications that require a lot of organization and history of the project that is accessible.
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.

Great Project Tracking Software

Rating: 9 out of 10
March 13, 2017
EH
Vetted Review
Verified User
Azure DevOps Server
4 years of experience
Team Foundation Server (TFS) is being utilized by many different departments within our organization. We personally use it to track tasks, user stories, bugs, releases, and test cases. Developers associate specific check-ins with bugs/user stories within TFS which, when pushed to our staging environments, are then assigned to QA/UAT for review. User stories and bugs are tracked as release scope for regular releases. The ability to associate releases/user stories/bugs in many different scenarios is priceless. It allows us to create different metrics/queries to measure success and potential failure, as well as to analyze what went well or what went wrong. TFS can be confusing for those new to the field or those who are older and used to other programs, but once the learning curve is achieved, the user tends to take well to the program.
  • Field customization is a feature TFS has that I particularly like. We have a very specialized customization of TFS running so that I can query for specific iteration/release paths that are relevant to our metrics. We also utilize a unique workflow structure for bugs and user stories as the process from creation to close is unique within our company.
  • TFS does their web view really well, especially with newer versions of the product. Often times, I feel that very little is lacking when I am logged into the web view of TFS. I am able to bulk edit items in the newer version of TFS, and at my old job we even set up the ability for QA to push checked in code to stage environments through TFS.
  • Finally, I feel TFS does a very good job of keeping historical track of actions performed to tickets. If someone has edited a ticket in any way, I can review and identify who made the change and when. This helps give me context when a developer contacts me to ask me a question related to the wording of a ticket. This also helps hold people accountable if tickets are written incorrectly or incompletely and prevents people from passing blame to others.
Cons
  • The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
  • VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
  • Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.
TFS is well suited for a team looking for structured requirements, projects, test cases, bugs, user stories, etc. It works well for planning things out and coordinating with others to see the "bigger view". TFS is great in scenarios where paper trails and other auditable data is needed to keep people in check and accountable. The search and query functionality allows users to search for past issues that may have been resolved previously and have crept back, and can provide history and context surrounding project functionality/decisions. TFS might not work as well for a team truly looking for a scrum experience. Although my companies have both claimed scrum, they both planned out releases at least a few weeks in advance. If you're changing things on a daily basis it might not be as great of a tool.

Team Foundation Server for R&D teams

Rating: 9 out of 10
December 01, 2015
BS
Vetted Review
Verified User
Azure DevOps Server
4 years of experience
Team Foundation Server is used by the entire company across the globe. Development uses it for obvious reasons in developing new software and fixing bugs that are found and logged into Team Foundation Server by our quality assurance analysts. Support uses Team Foundation Server to log issues from clients and professional services uses it to make minor changes while in the field with clients. Sales uses it to demonstrate new features to clients and to set up environments when holding trade shows.
  • Allows a great deal of history detail on every issue found or new feature added. It keeps a detailed history of any code changes by developers so you can always see who changed what portion or code.
  • You can adjust users permissions down to a group of users (i.e. testers vs. developers vs. managers) and can get very technical with permissions for each group. The permissions can also be set based on certain portions of the code base not just on the entire thing.
  • The information that is tracked is great. When you find an issue and you log it in Team Foundation Server you have many options for fields to utilize and edit to make sure you get the correct team of developers to look at it. You can also have different requirements for each issue or when checking in code such as changes made, priority level, area and iteration (these are used for internal development purposes usually).
Cons
  • Simplify the permissions interface and navigation. Permissions are great but sometimes finding the correct screen is difficult.
  • Make the interaction between different versions easier. Sometimes you can run into issues when trying to use an older Team Foundation Server server with a new Team Foundation Server Build server. This occurs when you don't have the resources to upgrade all servers at once.
This is more suited for a larger corporation or development team as the cost of acquiring the software/hardware might be too large for a smaller company. Setting it up can also be hard for a small team if there is no experience with it. Finding experience can be hard because of this fact but the Team Foundation Server wizards are generally helpful and provide adequate help in setup and administration.

Great system for consolidating work and information

Rating: 9 out of 10
December 03, 2018
MM
Vetted Review
Verified User
Azure DevOps Server
1 year of experience
We are currently managing a large project and we use TFS to manage bugs, code and releases. It is only being used by the technical team but others are coordinating with us to make sure their bugs make it into the system. As well, we are using data from the system to routinely give updates to management on the status of the project as well as any concerns or risks.
  • The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
  • Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
  • Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.
Cons
  • Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
  • Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
  • Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.
TFS is very good when working on a large project with a lot of moving pieces. When you have many BAs involved and a lot of user stories, it can be extremely useful to consolidate information. If you are not working on a large project with many users and developers, it may be excessive. However, in general, the tool is extremely helpful when implemented correctly.

Is TFS the right tool?

Rating: 7 out of 10
October 26, 2017
ES
Vetted Review
Verified User
Azure DevOps Server
10 years of experience
We are using TFS in our software division as a source control for code and DB objects. It allows us most importantly to keep a history of our code. Secondly, we can do deploys from this environment out to our many environments.
  • TFS has an excellent interactive UI for all users to make source control easy to use.
  • TFS has the backing of a major company, Microsoft. Updates and the way it is used gets regular updates.
  • TFS integrates into Visual Studio.
  • TFS has many tools for many different areas in the development life cycle.
Cons
  • There is no real ability to work offline. You need to be actively connected to it in order to see history.
  • Having many hands in the same project/file can cause conflicts that can be hard to resolve.
  • having a "master" branch is difficult in TFS, it can be done but it is slow and cumbersome and not an intuitive process.
I think if you work in a Microsoft exclusive environment, this is the tool for you. If you are in an arena where you might have C#, Java, or Python other tools might be better suited to your needs. TFS can be very costly but if it is instituted correctly with RM tools, it can be a wonderful thing. If you are a small shop use a free source control.
Return to navigation