Pricing overview

Azure DevOps Health, a suite of developer services from Microsoft, employs a multi-faceted pricing structure designed to accommodate teams of varying sizes and operational demands. The core pricing model is based on user count for access to essential features, supplemented by consumption-based or licensed pricing for advanced capabilities and resources. This approach allows organizations to scale their usage and associated costs in alignment with their development activities. The foundational offering includes a generous free tier for small teams, after which charges apply per user per month for basic access.

Beyond user licenses, additional services like continuous integration/continuous delivery (CI/CD) parallel jobs, Azure Test Plans, and Azure Artifacts storage incur separate costs. Parallel jobs, crucial for concurrent build and release pipelines, are billed based on the number of concurrent jobs and the type of agent (Microsoft-hosted or self-hosted). Azure Test Plans, which offers comprehensive test management capabilities, is licensed per user. Azure Artifacts, for package management, is primarily consumption-based, charging for storage used. This modular pricing ensures that users only pay for the specific services and scale they require, as detailed on the Azure DevOps Services pricing page.

Plans and tiers

Azure DevOps Health offers a tiered structure, primarily distinguishing between free access and various levels of paid user access, alongside individually priced add-on services. The fundamental components are:

  • Free Tier: Provides access to core features for up to 5 users.
  • Basic Plan: For teams exceeding five users, this plan provides access to Azure Boards, Azure Repos, and Azure Pipelines (with included parallel job time).
  • Basic + Test Plans: Builds upon the Basic Plan by adding full access to Azure Test Plans for comprehensive manual and exploratory testing.
  • Stakeholder Access: A free, limited access level for non-technical users to view backlogs, work items, and dashboards.

Additional services are typically billed separately:

  • Azure Pipelines: Beyond the included free minutes, additional Microsoft-hosted parallel jobs are billed per job per month. Self-hosted parallel jobs are also available for purchase.
  • Azure Artifacts: Storage is free up to a certain limit, then billed per GB per month.
  • Azure Test Plans: Requires specific user licenses.

A summary of the primary plans and their characteristics is provided below:

Plan/Service Price Key Limits / Features Best For
Stakeholder Access Free View backlogs, work items, dashboards; no code access or CI/CD. Project managers, business analysts, external collaborators needing read-only access.
Free Tier Free (up to 5 users) 5 users, 1 Microsoft-hosted parallel job (30 hours/month), 1 self-hosted parallel job, 2 GB Azure Artifacts storage. Small teams, startups, personal projects, proof-of-concept development.
Basic Plan $6 per user/month (for 6+ users) Access to Azure Boards, Azure Repos, Azure Pipelines. Development teams needing core DevOps features without advanced test management.
Basic + Test Plans $52 per user/month Includes Basic Plan features plus full access to Azure Test Plans. Teams requiring integrated manual, exploratory, and user acceptance testing capabilities.
Additional Microsoft-hosted Parallel Job $40 per job/month Enables one additional concurrent CI/CD pipeline run. Teams with frequent builds, multiple active projects, or lengthy pipeline runs.
Additional Self-hosted Parallel Job $15 per job/month Enables one additional concurrent CI/CD pipeline run on your own infrastructure. Organizations optimizing for specific environments, custom build agents, or cost control.
Azure Artifacts Storage First 2 GB free, then $0.25 per GB/month Stores packages (NuGet, npm, Maven, Python, Universal Packages). Teams managing internal package feeds for dependency management.

Free tier and limits

Azure DevOps Health provides a comprehensive free tier designed to support small teams and individual developers. This tier includes access for up to five users to the core services: Azure Boards for agile planning, Azure Repos for Git repository management, and Azure Pipelines for CI/CD automation. For CI/CD, the free tier includes one free Microsoft-hosted parallel job, limited to 30 hours of execution time per month, and one free self-hosted parallel job, which allows teams to run pipelines on their own infrastructure without additional cost for the job slot itself. Additionally, users receive 2 GB of free storage for Azure Artifacts to manage their package feeds. Beyond these limits, standard paid rates apply for additional users, parallel jobs, or storage. This free offering allows teams to fully explore the capabilities of Azure DevOps Health before committing to paid plans, as detailed in the Azure DevOps pricing documentation.

The free tier is particularly beneficial for startups and open-source projects, enabling them to implement robust DevOps practices without initial investment. However, as teams grow beyond five members or require more concurrent pipeline executions, they will need to upgrade to paid plans or purchase additional resources. For example, if a team of eight developers needs to use Azure Boards, Repos, and Pipelines, the first five users are free, and the additional three users would be billed at the basic user rate. Similarly, if multiple CI/CD pipelines need to run concurrently beyond the single free Microsoft-hosted job, additional parallel jobs would need to be purchased.

Real-world cost examples

To illustrate Azure DevOps Health's pricing, consider the following scenarios (prices are approximate and subject to change; refer to official Azure DevOps pricing for current rates):

  • Scenario 1: Small Startup Team (5 users)

    • Team Size: 5 developers
    • Needs: Agile planning (Boards), code hosting (Repos), basic CI/CD (Pipelines), minimal package management (Artifacts).
    • Cost Breakdown:
      • 5 users: Free (within the free tier limit)
      • 1 Microsoft-hosted parallel job: Free (30 hours/month)
      • 1 self-hosted parallel job: Free
      • Azure Artifacts storage: Free (up to 2 GB)
    • Total Monthly Cost: $0
    • Note: If this team consistently exceeds 30 hours of Microsoft-hosted pipeline usage, they might consider optimizing pipelines or purchasing an additional parallel job.

  • Scenario 2: Growing Development Team (10 users)

    • Team Size: 10 developers
    • Needs: All core features, plus more robust CI/CD capacity.
    • Cost Breakdown:
      • 5 users: Free
      • 5 additional users (Basic Plan): 5 users * $6/user = $30
      • 1 Microsoft-hosted parallel job: Free (30 hours/month)
      • 1 additional Microsoft-hosted parallel job (for increased concurrency): $40
      • Azure Artifacts storage: Free (up to 2 GB)
    • Total Monthly Cost: $30 (users) + $40 (parallel job) = $70

  • Scenario 3: Enterprise Team with Advanced Testing (25 users)

    • Team Size: 25 developers, 5 dedicated testers
    • Needs: Core DevOps, advanced test management, high CI/CD concurrency, significant artifact storage.
    • Cost Breakdown:
      • 5 users: Free
      • 20 additional developers (Basic Plan): 20 users * $6/user = $120
      • 5 testers (Basic + Test Plans): 5 users * $52/user = $260
      • 3 Microsoft-hosted parallel jobs (2 additional): 2 jobs * $40/job = $80
      • Azure Artifacts storage: 10 GB used (8 GB over free limit) = 8 GB * $0.25/GB = $2
    • Total Monthly Cost: $120 (devs) + $260 (testers) + $80 (pipelines) + $2 (artifacts) = $462

  • Scenario 4: Hybrid Environment with Self-Hosted Agents (15 users)

    • Team Size: 15 developers
    • Needs: Core DevOps, custom build environments, moderate CI/CD concurrency.
    • Cost Breakdown:
      • 5 users: Free
      • 10 additional users (Basic Plan): 10 users * $6/user = $60
      • 1 Microsoft-hosted parallel job: Free (30 hours/month)
      • 2 self-hosted parallel jobs (1 additional): 1 job * $15/job = $15
      • Azure Artifacts storage: Free (up to 2 GB)
    • Total Monthly Cost: $60 (users) + $15 (self-hosted job) = $75

How the pricing compares

Azure DevOps Health's pricing model, particularly its per-user licensing for core features and consumption-based billing for specific services, aligns with common practices in the CI/CD and DevOps platform market. However, there are distinctions when comparing it to alternatives like GitHub Actions, GitLab CI/CD, and Jenkins.

  • GitHub Actions: GitHub Actions often uses a consumption-based model for CI/CD minutes and storage, with private repositories incurring charges beyond free limits. For public repositories, GitHub Actions are generally free. Unlike Azure DevOps Health's per-user model for core services, GitHub's pricing for private repositories is often tied to the number of users in an organization's plan (e.g., Team or Enterprise plans), which bundle Actions minutes. This means that for CI/CD, GitHub's focus is on resource consumption rather than per-user access for the CI/CD runners themselves. Organizations heavily invested in the GitHub ecosystem for code hosting might find the integrated pricing simpler, while those needing a broader suite of DevOps tools might prefer Azure DevOps Health's consolidated offering. More details can be found on GitHub Actions billing documentation.

  • GitLab CI/CD: GitLab offers a comprehensive DevOps platform, with CI/CD being a core component. Its pricing is primarily tiered per user per month (Free, Premium, Ultimate). The free tier provides baseline CI/CD minutes, with higher tiers offering more minutes and advanced features. Similar to Azure DevOps Health, GitLab bundles CI/CD runners and features within its user-based subscriptions. However, GitLab's tiers encompass a broader range of features (e.g., security scanning, portfolio management) that might be separate add-ons or considered distinct services in Azure DevOps Health. This integrated approach can simplify budgeting for teams that leverage the full GitLab platform. Refer to GitLab's pricing page for detailed tier comparisons.

  • Jenkins: Jenkins is an open-source automation server, meaning the core software itself is free to download and use. The primary costs associated with Jenkins are infrastructure (servers, virtual machines, containers) to host the Jenkins controller and agents, as well as the operational overhead for maintenance, plugin management, and scaling. There are no direct per-user or per-job costs for using Jenkins itself. This makes Jenkins a potentially more cost-effective option for organizations with significant existing infrastructure and in-house expertise to manage it. However, the total cost of ownership (TCO) can be higher due to labor and infrastructure expenses compared to managed services like Azure DevOps Health or GitHub Actions, which abstract away much of the infrastructure management. For organizations evaluating open-source vs. managed services, the Jenkins installation guide provides insights into self-hosting requirements.

In summary, Azure DevOps Health provides a balance between a feature-rich, integrated platform and flexible pricing. Its free tier is competitive for small teams, and its modular billing for add-on services allows for granular cost control. Teams primarily focused on CI/CD within a GitHub ecosystem might lean towards GitHub Actions, while those seeking a fully integrated, single-vendor DevOps platform with extensive features might consider GitLab. Jenkins remains a strong contender for organizations prioritizing open-source control and willing to manage their own infrastructure.