Five services on one platform
Boards, Repos, Pipelines, Test Plans, and Artifacts all share identity, permissions, and work-item context. Customers can adopt all five or pick the ones that fit.
Microsoft • Application lifecycle management
Microsoft Azure DevOps
Azure DevOps is Microsoft's enterprise ALM and CI/CD platform.
Merito delivers Azure DevOps Services and Azure DevOps Server rollouts, migrations, pipeline design, Test Plans configuration, and the GitHub coexistence work that Microsoft's "better together" strategy now expects. We do not sell Microsoft licenses; we deliver the work around them.
- Best for
- DevOps engineering leaders and platform owners, Azure DevOps Server administrators planning Server to Services migration, Release managers rationalizing pipelines across multiple teams
- Hosting
- SaaS / On-prem
- Time to value
- Team-level Services rollouts are live in two to four weeks. Estate-scale rollouts with Boards process customization, pipeline standards, and Test Plans run four to twelve weeks. Server to Services migrations run eight to twenty-four weeks depending on footprint size, customization depth, and pipeline complexity.
- Security posture
- ISO 27001, 27017, 27018, SOC 1 and SOC 2 Type II, HIPAA, HITRUST
- Last reviewed
- 2026-05-01
What it is
Microsoft Azure DevOps in the enterprise stack
Azure DevOps ships as five services on one platform: Azure Boards (work tracking and agile planning), Azure Repos (Git source control), Azure Pipelines (CI/CD), Azure Test Plans (manual and exploratory testing), and Azure Artifacts (package feeds). Customers can adopt all five or pick the ones that fit alongside GitHub, Jira, or other tooling.
The product runs in two forms. Azure DevOps Services is the Microsoft-hosted SaaS and the default go-forward SKU. Azure DevOps Server is the self-managed on-prem variant following Microsoft's 10-year lifecycle: Server 2020 mainstream support ended October 14, 2025 and Server 2022 mainstream support ends January 11, 2028. Customers still running on-prem should be planning their path, whether that is Server 2022 upgrade, migration to Services, or a GitHub-centric consolidation.
Microsoft's current stance is "better together" with GitHub. The roadmap pushes repos toward GitHub while keeping Boards, Pipelines, and Test Plans as the work and delivery layer. That shape makes Azure DevOps a coexistence platform, not a standalone choice. Merito's rollouts plan that explicitly: what stays in Azure DevOps, what moves to GitHub, and how the two integrate on a single delivery signal.
Merito's Azure DevOps work covers greenfield rollouts for teams new to the platform, on-prem Server to Services migrations, pipeline design for real release cadence (not demo YAML), Test Plans configuration for manual and UAT flows, Azure Artifacts feeds for internal packages, and the GitHub coexistence work that most Microsoft customers now need. Merito does not sell Microsoft licenses; Azure DevOps runs on Microsoft agreements, MCA, EA, or CSP. Our role is delivery.
Ideal use cases
- Greenfield Azure DevOps Services rollouts with Boards, Repos, Pipelines, Test Plans, and Artifacts configured for the real team
- Azure DevOps Server on-prem rollouts where regulated hosting is required
- Azure DevOps Server to Services migrations on Microsoft's lifecycle timeline
- GitHub and Azure DevOps coexistence patterns (GitHub for code, Azure Boards for work, Azure Pipelines for CI/CD)
- Pipeline rationalization and YAML standardization across teams
- Test Plans rollouts for manual, exploratory, and UAT testing integrated with Boards
What it is best at
Where Microsoft Azure DevOps earns its seat
SaaS and on-prem parity
Azure DevOps Services and Azure DevOps Server share a feature set, so regulated customers on Server are not on a separate product.
GitHub coexistence by design
Microsoft's "better together" strategy positions Azure DevOps and GitHub as complementary. Boards, Pipelines, and Test Plans work cleanly with GitHub repos.
Mature CI/CD at enterprise scale
Azure Pipelines covers Windows, Linux, macOS, containers, Kubernetes, and every major cloud. Self-hosted agents unlock customer-owned infrastructure.
Test Plans earns its seat for manual and UAT
Few other platforms have native manual test management tied to work items. Test Plans is the right tool for structured manual, exploratory, and UAT flows.
Core capabilities
Microsoft Azure DevOps capabilities, grouped by outcome
Azure Boards (work management)
Agile planning, backlogs, and delivery tracking tied to source, pipelines, and tests.
Work items and process templates
Agile, Scrum, CMMI, and custom process templates with configurable work-item types, states, and rules.
Boards, backlogs, and sprints
Team and cross-team boards, sprint planning, capacity, and taskboard execution.
Delivery Plans
Cross-team portfolio views with dependency mapping and release-level visibility.
GitHub integration
Connect GitHub repos to Boards for commit, PR, and issue linking. First-class coexistence path.
Azure Pipelines (CI/CD)
Cloud-hosted or self-hosted CI/CD with YAML pipelines and classic release flows.
YAML multi-stage pipelines
Declarative CI/CD with build, test, and deployment stages, environment approvals, and branch policies.
Microsoft-hosted and self-hosted agents
Windows, Linux, and macOS runners in the Microsoft cloud, plus customer-hosted agents for regulated or air-gapped builds.
Deployment targets
Azure, AWS, GCP, Kubernetes, Azure App Service, Azure Functions, virtual machines, and on-prem targets.
Approvals, gates, and release governance
Environment-level approvals, check-gated deployments, and audit trails for regulated release flow.
Azure Test Plans (manual and exploratory testing)
Native manual test management integrated with Boards and Pipelines.
Test suites and test plans
Static, query-based, and requirement-based test suites tied to user stories and release scope.
Manual execution and exploratory runs
Step-by-step manual execution in-browser with screenshot and system capture, plus time-boxed exploratory runs.
UAT and stakeholder testing
Stakeholder-friendly runs via web portal; works well for UAT, business-user testing, and regulated sign-off.
Traceability to work items
Two-way link between test cases, user stories, bugs, and runs. Coverage surfaces naturally inside Boards.
Azure Repos and Artifacts
Source control and package feeds, often coexisting with GitHub.
Azure Repos (Git)
Enterprise Git hosting with branch policies, PR workflows, and Azure AD integration. Often paired with or replaced by GitHub in new footprints.
Azure Artifacts (package feeds)
Private feeds for NuGet, npm, Maven, Python, and universal packages, with upstream sources and retention policies.
Pull request and policy controls
Required reviewers, build validation, work-item linking, and merge strategies enforced at the branch level.
Administration and governance
Identity, permissions, and audit controls at enterprise scale.
Azure AD and Entra ID integration
Enterprise identity, group mapping, and conditional access for organization and project membership.
Project and process customization
Inherited or hosted XML processes for custom work-item types, states, and rules.
Audit log and compliance
Organization-level audit log with configurable retention and SIEM streaming.
Where it fits in the stack
How Microsoft Azure DevOps connects to the rest of your landscape
Native Microsoft integrations
NativeFirst-party Microsoft integrations in and around Azure DevOps.
- GitHub and GitHub EnterpriseRepos and Actions coexist with Azure Boards, Pipelines, and Test Plans. Microsoft's strategic coexistence path.
- GitHub CopilotAI-assisted coding across Repos, GitHub repos, and IDE.
- AzureNative deployment targets (App Service, Functions, AKS, VMs, Azure SQL, and the rest of Azure).
- Microsoft Entra IDEnterprise identity, SSO, conditional access, and group-based permissions.
- Visual Studio and VS CodeTight IDE integration for Boards, Repos, and Pipelines.
- Microsoft TeamsWork item notifications, pipeline approvals, and PR updates in Teams channels.
Certified and partner integrations
CertifiedWidely adopted Azure DevOps extensions for enterprise footprints.
- Tricentis Tosca, qTest, and NeoLoadTest automation and performance testing wired to Azure Pipelines and Boards.
- TestRailTest management integrated with Azure Boards and Pipelines.
- Checkmarx, Black Duck, Snyk, Sonatype, SemgrepApplication security scanning stages in Azure Pipelines.
- SonarQube / SonarCloudCode quality gates enforced at PR and pipeline stages.
- Terraform, Ansible, Bicep, ARMInfrastructure-as-code deployed through Azure Pipelines tasks.
Custom and toolchain integrations
CustomCustom integrations Merito commonly builds around Azure DevOps.
- Jira / Jira Service ManagementBidirectional sync when Jira is the business-side work system and Azure DevOps is the engineering system.
- ServiceNowChange and incident sync between Azure DevOps Boards and ServiceNow, including change-gated deployments.
- Power BI and custom dashboardsAzure DevOps Analytics exposed via Power BI or custom dashboards for release and quality reporting.
- On-prem build/test systemsSelf-hosted agents wired into mainframe, embedded, or regulated build environments.
Deployment and implementation
How it rolls out
- Hosting
- SaaS / On-prem (Azure DevOps Services: North America, EU, UK, Australia, Asia Pacific, Brazil (by organization), Azure DevOps Server: customer-operated in any region (on-prem, Azure VM, AWS, GCP))
- Implementation complexity
- Moderate
- Typical time to value
- Team-level Services rollouts are live in two to four weeks. Estate-scale rollouts with Boards process customization, pipeline standards, and Test Plans run four to twelve weeks. Server to Services migrations run eight to twenty-four weeks depending on footprint size, customization depth, and pipeline complexity.
- Prerequisites
- Microsoft Entra ID (Azure AD) for enterprise identity
- Azure DevOps Server: Windows Server, SQL Server, supported CPU and memory for expected concurrency
- Self-hosted agents if builds need on-prem or regulated environments
- What Merito usually handles
- Azure DevOps Services is Microsoft-hosted SaaS. Azure DevOps Server is customer-operated on Windows Server with SQL Server. Both forms share the same feature set.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- Azure DevOps Services is user-subscription licensed through Microsoft agreements (EA, MCA, or CSP). First 5 users are free on Basic. Paid users are Basic per user per month, with Basic + Test Plans per user per month for QA roles. Stakeholder access is free and read-oriented. Azure DevOps Server is licensed through Visual Studio subscriptions or Server+CAL, with the on-prem lifecycle cap (10 years). Merito does not sell Microsoft licenses; procurement runs through your Microsoft channel.
- Editions and modules
Azure DevOps Services (SaaS)
Microsoft-hosted; default go-forward SKU. Tiers: Stakeholder (free), Basic, Basic + Test Plans.
Best for: Most enterprises; all new rollouts.
Azure DevOps Server 2022 (on-prem)
Self-managed on Windows Server and SQL Server. Mainstream support through January 11, 2028.
Best for: Regulated, sovereign, or air-gapped footprints still requiring on-prem hosting.
Azure DevOps Server 2020
Mainstream support ended October 14, 2025. In extended support for security-only updates.
Best for: Only appropriate as a migration source, not a go-forward target.
- Common expansion areas
- GitHub Enterprise coexistence for repos while keeping Boards and Pipelines
- Azure Test Plans for manual and UAT testing
- GitHub Advanced Security scanning in Pipelines
- Self-hosted agents for regulated build environments
- Azure DevOps Analytics feeding Power BI dashboards
Merito services
How Merito helps you win with Microsoft Azure DevOps
Pick the engagement that matches where you are in the lifecycle.
01
Azure DevOps Implementation
Greenfield Services rollouts and Server rollouts with Boards, Pipelines, Test Plans, and Artifacts configured for the real team, not a template.
Explore service02Server to Services Migration
Azure DevOps Server to Azure DevOps Services migrations using Microsoft's Data Migration Tool, with process and pipeline rationalization.
Explore solution03DevOps Consulting
Pipeline design, YAML standardization, branch policies, release governance, and the GitHub coexistence pattern that most footprints now need.
Explore service04Training and Enablement
Role-based training for Azure DevOps admins, pipeline authors, Boards owners, and Test Plans leads.
Explore service05Staff Augmentation
Merito-placed Azure DevOps engineers, pipeline architects, and platform owners embedded with your team.
Explore service06Signature Support
Ongoing admin support for Azure DevOps footprints, including pipeline audits, Test Plans oversight, and extension governance.
Explore serviceAzure DevOps delivery
Boards, Pipelines, Test Plans. Configured for your release cadence, not a demo.
Rollout, migration, or rescue. Merito delivers the Azure DevOps work so Boards, Pipelines, Test Plans, and GitHub coexistence produce one delivery signal, not five.
Merito point of view
Azure DevOps is a coexistence platform now. Plan the split with GitHub up front.
Microsoft's current Azure DevOps direction is "better together" with GitHub: source and security shift toward GitHub while Boards, Pipelines, and Test Plans stay in Azure DevOps. That is a healthy strategy, but only if the split is planned. The failure mode is organizations that adopt both, never decide who owns what, and end up with two Boards, two pipelines, and two PR review surfaces for the same codebase.
On-prem Azure DevOps Server is not dead, but the clock is clear. Server 2020 is past mainstream. Server 2022 mainstream ends January 11, 2028. Customers still on Server should know what their path is: upgrade to 2022, migrate to Services, or consolidate to GitHub-plus-Pipelines. The evaluation is not complicated, but it has to be done.
Pipeline quality is where most Azure DevOps rollouts underdeliver. YAML pipelines copied from a demo repo do not survive real release cadence. Merito's standard engagement starts with pipeline templates, branch policies, and release environments, then adds Test Plans, Artifacts, and analytics. That ordering matters: the pipeline is the contract between engineering and release.
What buyers usually underestimate
- Adopting Azure DevOps and GitHub without deciding who owns repos, Boards, and PR review.
- Running Azure DevOps Server 2020 past October 14, 2025 without a migration plan.
- Using Azure Pipelines YAML as "copy from the demo" instead of organization-level templates.
- Leaving Test Plans turned off because "we use Tosca" — Test Plans is the right tool for manual and UAT, not automation.
- Skipping self-hosted agents for regulated builds and fighting the cloud-hosted agent image instead.
- Running Azure DevOps Services on personal Microsoft accounts instead of Entra ID.
Related from Merito
Continue exploring Microsoft Azure DevOps on Merito
Related solutions
- DevOps ToolchainRelease governance across Boards, Repos, GitHub, Pipelines, and test management.
- Data Migration SolutionAzure DevOps Server to Services migration, plus Jira DC to Azure DevOps coexistence patterns where relevant.
- Software Delivery AccelerationPipeline, quality, and deployment acceleration across Azure DevOps and GitHub footprints.
Related services
Related products
- Atlassian Jira CloudAlternative ALM platform. Common coexistence case when Jira owns business work and Azure DevOps owns engineering.
- TestRailAlternative test management when Test Plans is not the right shape for your QA team.
- Tricentis qTestEnterprise test management integrated with Azure DevOps for scaled QA programs.
Frequently Asked Questions
Azure DevOps FAQs
Consultation request
Talk to Merito about Azure DevOps
Share your current state (greenfield, on-prem Server, existing Services footprint, GitHub coexistence) and what you are trying to change. A Merito Microsoft specialist follows up within one business day.
Services or Server
We deliver both hosting models
Microsoft's lifecycle forces a choice for Server customers. We plan the right path and deliver it.
Coexist with GitHub
Design the split once
Who owns source, who owns Boards, who owns PR review. We design it once and configure both platforms around the answer.
Next step
Design the pipeline contract. Then fill in the tools.
A Merito Azure DevOps engagement starts with release contract design: what a build gate is, what a deployable is, who owns what. Then Boards, Pipelines, Test Plans, and GitHub get configured around it.