Azure DevOps Server: What It Is & How to Use It

Azure DevOps Server is Microsoft’s self-hosted, on-premises version of the Azure DevOps suite, providing source control, work tracking, build automation, and release management without sending data to the cloud. You install it on your own hardware or virtual machines, manage it with your own administrators, and pay for it through a license rather than a monthly subscription. This article explains what it includes, how it differs from the cloud service, what it costs, and who should choose it.

Background: From Team Foundation Server to Azure DevOps Server

Azure DevOps Server was previously called Team Foundation Server (TFS). Microsoft introduced TFS in 2005 as an on-premises application lifecycle management platform, and it became the standard tool for many enterprises that could not or would not move their code and work items to the cloud. In 2018, Microsoft renamed the entire product family to Azure DevOps and split the cloud offering into five separate services: Azure Boards, Azure Repos, Azure Pipelines, Azure Test Plans, and Azure Artifacts. The on-premises product was rebranded to Azure DevOps Server in 2019, with version 2019 being the first release under the new name. Since then, Microsoft has continued to release regular updates, with the latest major version being Azure DevOps Server 2022.

The core architecture has remained consistent: a central SQL Server database stores all work items, source code metadata, and build records, while web services and client tools connect to it. This design allows for deep integration with Active Directory, SQL Server reporting, and other enterprise systems.

What’s Included in Azure DevOps Server

Azure DevOps Server bundles the same five services as the cloud version, but they run entirely on your infrastructure:

Azure Repos – Git repositories and Team Foundation Version Control (TFVC) for source code management. You can host unlimited private repositories on your own servers.
Azure Boards – Work item tracking with Kanban boards, Scrum sprints, and customizable processes. You can create your own process templates or use the built-in Agile, Scrum, and CMMI templates.
Azure Pipelines – Build and release automation. You can build .NET, Java, Python, C++, and many other projects, and deploy to on-premises servers, virtual machines, or cloud targets.
Azure Test Plans – Manual and exploratory testing tools, including test case management and rich client test runner.
Azure Artifacts – Hosting for NuGet, npm, Maven, and Python packages, so your teams can share code libraries internally.

All of these are accessed through a web portal, Visual Studio, Visual Studio Code, or command-line tools. The server also includes a REST API for automation and integration with other systems.

How Azure DevOps Server Works: Architecture and Deployment

Azure DevOps Server is built on a three-tier architecture. The data tier is a SQL Server database (or a cluster of databases) that stores everything. The application tier runs the web services, job agents, and build controllers. The client tier consists of the web browser, Visual Studio, and other tools that connect to the application tier.

To deploy it, you typically install the server on a Windows Server machine (2019 or 2022 are supported for the latest versions), configure SQL Server (either on the same machine or a separate one), and then use the installation wizard to create the deployment. You can choose a basic installation (single server) or an advanced installation with separate application and data tiers for scale.

After installation, you create project collections, which act as containers for teams and projects. Each project collection has its own set of work item types, build definitions, and permissions. You then create projects within those collections, add users from Active Directory, and assign licenses.

Build and release agents run on separate machines that you configure. These agents poll the server for jobs, pull the source code, run your build scripts, and publish the results. You can have multiple agents to scale out builds.

Azure DevOps Server vs. Azure DevOps Services (Cloud)

The most common question is which version to choose. Here’s a direct comparison:

Hosting: Server is on-premises; Services is Microsoft-hosted in the cloud.
Updates: Server receives major releases roughly every year; Services gets new features continuously, often monthly.
Licensing: Server requires a one-time license fee per user plus SQL Server licenses; Services is subscription-based (free for up to 5 users, then per user per month).
Security: Server keeps all data behind your firewall; Services relies on Microsoft’s cloud security and compliance certifications.
Integration: Server integrates tightly with Active Directory and on-premises systems; Services works best with Azure AD and cloud services.
Scale: Server can handle large teams but requires careful capacity planning; Services scales automatically with no infrastructure to manage.

If you have strict data residency requirements, regulatory compliance demands, or unreliable internet connectivity, the server version is often the right choice. If you want the latest features and don’t want to manage infrastructure, the cloud version is simpler.

Licensing and Costs of Azure DevOps Server

Azure DevOps Server licensing is based on user access. You need a license for every user who accesses the server, including stakeholders who only view work items. The two main license types are:

Basic: For developers, testers, and others who need full access to all features. This is the standard license.
Stakeholder: A free license for users who only need to view work items, approve releases, and track progress. They cannot edit code or create work items.

There is also a Basic + Test Plans license that adds access to Azure Test Plans. The server software itself is free to download; you only pay for user licenses and SQL Server. Microsoft offers a free tier for up to 5 users, and you can buy additional licenses through volume licensing or retail. The exact price varies by region and agreement, so you should check Microsoft’s official pricing page or contact a reseller.

In addition to user licenses, you must have a SQL Server license for the database tier. If you use the free SQL Server Express edition, you are limited to 5 users and 10 GB of data, which is fine for small teams but not for production use.

Common Problems and How to Solve Them

Even with proper setup, users run into issues. Here are the most frequent ones:

Slow performance: This is often caused by an underpowered SQL Server, missing indexes, or a large database. Monitor your SQL Server’s CPU and I/O, and consider moving the data tier to a dedicated machine with fast SSDs.
Build agents going offline: Agents can stop responding due to network issues, permission problems, or the agent service crashing. Check the agent logs (typically in the _diag folder) and restart the agent service.
Authentication failures: If users can’t log in, check that they are in the correct Active Directory group and that the server’s application pool identity has access to the database.
Backup failures: Azure DevOps Server has a built-in backup tool, but it requires SQL Server Agent to be running. Ensure the SQL Server Agent service is started and that the backup job has the right credentials.
Upgrade issues: Upgrading from TFS 2018 or older versions can be complex. Always take a full backup of the databases before upgrading, and run the upgrade wizard in a test environment first.

Alternatives to Azure DevOps Server

While Azure DevOps Server is a strong choice, it’s not the only on-premises ALM tool. Here are some alternatives:

GitLab Self-Managed: A popular alternative that offers source control, CI/CD, and issue tracking in a single application. It has a strong free tier and supports both single and multi-machine deployments.
Jenkins: An open-source automation server that focuses on CI/CD. It’s not a full ALM suite; you’d pair it with a separate issue tracker like Jira.
Jira + Bitbucket: Atlassian’s on-premises stack (Jira Server/Data Center and Bitbucket Server) provides project tracking and Git hosting, but you need to integrate them for a complete solution.
Gitea or Gogs: Lightweight, open-source Git servers that are easy to set up but lack the full project management features.

Your choice depends on your team’s specific needs: if you want a single integrated suite from Microsoft, Azure DevOps Server is ideal; if you prefer open-source flexibility, GitLab is a strong contender.

Frequently Asked Questions

Is Azure DevOps Server free?

The server software itself is free to download and install, but you must purchase user licenses for each person who accesses it. There is a free tier for up to 5 users, and stakeholders (read-only users) are always free. You also need a SQL Server license, which can be costly.

Can I migrate from Azure DevOps Server to the cloud?

Yes. Microsoft provides the Azure DevOps Migration Tool (a third-party open-source tool) and a built-in data migration service for moving from Server to Services. The process involves exporting your collections and importing them into the cloud service. It’s not trivial, and you should plan carefully, but it’s supported.

What is the difference between Azure DevOps Server and Team Foundation Server?

They are the same product. Microsoft renamed TFS to Azure DevOps Server in 2019. The last version under the TFS name was TFS 2018, and the first Azure DevOps Server version was 2019. The functionality is essentially the same, with some feature additions and improvements.

Does Azure DevOps Server require internet access?

No. The server runs entirely on your network and does not require internet access for daily use. However, you may need internet for initial installation (to download components), for licensing activation, and if you want to use extensions from the Visual Studio Marketplace.

Can I use Azure DevOps Server with Visual Studio Community Edition?

Yes. Visual Studio Community Edition can connect to Azure DevOps Server, but you need a Basic license for the user account. The Community Edition itself is free for small teams, but the server license still applies.

How often does Microsoft release updates for Azure DevOps Server?

Microsoft typically releases a new major version every 1-2 years, and within each major version, there are periodic updates (e.g., 2022.0.1, 2022.1). These updates include bug fixes and new features. The cloud version gets updates much more frequently, often weekly.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →