Azure DevOps
AI in Azure DevOps: Copilot, Pipelines & AIOps
9 Jul 2026·10 min read
Read →#Azure DevOps#GitHub Actions#Azure Pipelines#CI/CD#Migration#DevOps
A question we hear a lot from teams: “Is Azure DevOps going away — will everything move to GitHub Actions?” The honest answer, based on Microsoft’s own documentation, is more nuanced than a simple yes or no. Azure DevOps is not deprecated and continues to receive updates. At the same time, Microsoft is clearly steering new investment and new-project guidance toward GitHub, with GitHub Actions positioned as its flagship CI/CD platform. This article separates fact from rumour, flags the one firm date you need to know, and shows the official path if and when you decide to migrate.
Note: Azure DevOps is not being retired
There is no announced end-of-life for Azure DevOps Services or Azure Pipelines. Microsoft maintains a public, actively updated Azure DevOps roadmap, and much of Microsoft’s own internal engineering still runs on Azure DevOps. Treat GitHub Actions as the strategic direction for new work — not as a forced, dated migration of everything you already run.
2027
Public projects retire
Not
Deprecated
Official
Migration tooling
GitHub Actions
Recommended CI/CD
What Microsoft has actually said
Microsoft’s position, stated across its documentation, is twofold. First, Azure DevOps remains supported and on the roadmap. Second, for public and open-source scenarios — and for greenfield projects — Microsoft now explicitly recommends GitHub: the docs state plainly that “Microsoft recommends using GitHub for all your public project needs.” GitHub Actions is the CI/CD engine in that world, and Microsoft builds first-class Azure deployment actions for it. So the direction is real, even though the rip-and-replace is not.
Official sources
The one firm date: public projects retire in 2027
If there is a concrete “Azure DevOps moving to GitHub” signal, this is it. Azure DevOps public projects are retired: you can no longer create new public projects or make a private project public, and starting in 2027 existing public projects automatically convert to private. When that conversion happens, anonymous access stops, your free Microsoft-hosted pipeline capacity drops to the standard allotment (1,800 minutes per month, or your purchased amount), status badges stop rendering for anonymous viewers, and public package feeds require authentication. If you rely on a public Azure DevOps project — common for open-source — Microsoft’s recommended destination is GitHub.
Plan the move
Azure Pipelines vs GitHub Actions — the mental model
The two systems map onto each other cleanly, which is what makes migration tractable. Here is the core translation, straight from Microsoft’s migration guidance.
How to migrate your pipelines
You do not convert YAML by hand. Microsoft and GitHub provide GitHub Actions Importer, a CLI extension that works in four phases: audit (inventory your existing pipelines and see how complete a conversion will be), forecast (estimate the runner usage and effort), dry-run (generate the workflow files without committing), and migrate (open a pull request with the converted workflow). Run the audit first to understand scope, then migrate pipeline by pipeline.
Warning: Not everything migrates automatically
Importer handles most pipeline syntax, but complex or custom tasks may need manual fixes, and there is no built-in tool to move Azure Boards work items to GitHub Issues (community scripts and CSV export/import exist). Repositories are a separate step — use GitHub Enterprise Importer (gh gei) to bring across Git history, pull requests, and branch policies.
Migration tooling
Should you move now?
There is no urgency to abandon Azure Pipelines if it serves you well — it is supported and improving. Be deliberate instead of reactive: migrate public and open-source projects ahead of the 2027 conversion; default new projects to GitHub if your organisation is GitHub-centric or wants tighter Copilot and Advanced Security integration; and pilot GitHub Actions on one non-critical pipeline using the Importer before committing the rest. For most teams, the right answer this year is to learn both and plan the transition on your own timeline.
Learn both with us
Our DevOps and Azure programmes cover Azure Pipelines and GitHub Actions side by side — YAML pipelines, runners, secrets and OIDC, and a hands-on Importer migration — so you are fluent whichever way your organisation leans. If you are planning a pipeline migration or want a structured path into modern CI/CD, reach out and we will help you map it.
Ready to Start Your Cloud Journey?
Live batches Mon–Sat — Azure 9–10 AM IST (started 3 august 2026 — join in progress) · AWS 10:30–11:45 AM IST (starts 31 august 2026). Hands-on labs, exam prep, and community support.
