Who Daigle is and what he now runs
GeekWire profiles Daigle in its "Microsoft 2.5" series. According to that profile, Microsoft moved in August 2025 to integrate GitHub under CoreAI. GitHub had run as a quasi-independent unit since the 2018 acquisition. At the same time, then-CEO Thomas Dohmke said he would leave at the end of the year.
Daigle is a GitHub veteran of 13-plus years. He was one of the loudest advocates for "keep GitHub GitHub." In January 2026 he added a second title, Chief Marketing Officer of Developer, for all of Microsoft. He now leads developer audience marketing and developer relations across both GitHub and Microsoft.
GeekWire notes that the choice matters. Microsoft consolidated developer messaging under someone from GitHub rather than someone from its traditional DevDiv organization. That makes Daigle's claim that GitHub's influence now reaches beyond its own product set more credible. It does not prove that every Microsoft developer team has been integrated.
His stated goal has moved from "don't break GitHub" to exporting GitHub's community and developer-first approach across Microsoft. He said engineering and marketing teams that previously weren't talking are now working together. He also said teams are sharing foundations and the GitHub Copilot SDK "in a way that would have seemed improbable before." His summary of Microsoft's long-standing problem was that its challenge isn't creating products but connecting them.
These are interview statements from an executive with a stake in the story. They are not independent measurements.
The Azure migration
GitHub's infrastructure strain is the hard news in this story. Daigle said GitHub is roughly 60% through its Azure migration as of early October. He called it a major re-architecture rather than a lift-and-shift. GeekWire reports that GitHub is working with Azure storage teams to separate compute from storage for Git. The aim is to ease bottlenecks when developers and agents work in the same repositories at the same time.
Other figures reported in the story:
- Commits: the company says developers and agents made 7.38 billion commits in September. That is a monthly commit count. It doesn't separate human from agent activity and doesn't count distinct users or repositories.
- Capacity: Daigle said GitHub can ask Microsoft for very large additions, such as millions of CPUs, and that recent growth would not have been manageable without Azure support.
- Outages: GeekWire says GitHub has had significant outages in recent months, including one in August that lasted nearly eight hours.
How this fits the wider record
Outside coverage suggests the migration has been bumpy. The Register reported in June that GitHub acknowledged nine incidents in its May 2026 availability report. It said GitHub was trying to fix its availability problems by expanding capacity and migrating more workloads to Azure, but reliability remained uneven.
Secondary outlets put the migration at a lower share earlier this year. One tech site, citing a Cloud Computing News report, said 40% of core monolith traffic had moved by May 2026, with a 50% target for July. That report also said Microsoft had confirmed GitHub was using AWS capacity alongside Azure. I couldn't verify either claim against a primary source, so treat them as unconfirmed.
Daigle's 60% figure is consistent with steady progress, but the metrics may not be defined the same way. Anyone running CI/CD on GitHub Actions or relying on Copilot should still plan for degraded-service scenarios, such as retry logic, cached dependencies and a fallback path for critical releases.
GitHub as an agent platform
Daigle describes GitHub as becoming "the store for anything that needs to be coded and needs some verification." In GeekWire's framing, it is also becoming a store for agents. That would make it the developer layer of what Satya Nadella's team calls Microsoft's "agent factory" strategy. GeekWire reports more than 200 million developers on GitHub, plus an unknown but fast-growing number of agents.
For comparison, GitHub's own announcement at Universe in October 2025, written by Daigle, cited 180 million developers. The two figures suggest growth, but the counting methods may differ.
That 2025 announcement introduced Agent HQ. It described a mission control interface across GitHub, VS Code, mobile and the CLI for assigning and tracking multiple agents. It also promised that agents from Anthropic, OpenAI, Google, Cognition and xAI would arrive through paid Copilot subscriptions. It included enterprise controls too: a governance control plane, metrics and agentic code review. That history is the best evidence that "store for agents" is an extension of an existing strategy and not a surprise pivot. It doesn't show that every announced capability is available today.
Advice for building in the agent era
Daigle told GeekWire that developers should rethink several things:
- Scale APIs for agents separately from APIs for humans.
- Build APIs designed specifically for agents.
- Rewrite documentation and tooling so agents can consume them efficiently.
- Treat agent access as a fundamentally different workload from human access.
These are his suggestions, not a published GitHub checklist. They do match the operational problem GitHub describes. Agents commit and query continuously and in parallel, so they behave very differently from people at keyboards.
Longer-term vision
Daigle also said he expects AI to make software economical for very small audiences, such as a family, an individual or one team. In that world GitHub would help people discover niche software. He wants both professional and newer builders to run software and agents without managing token costs, uptime or monitoring. That is a forecast and not a product commitment.
What to watch at GitHub Universe
GitHub Universe runs October 28-29 in San Francisco. Per the event site, it is in-person and virtual, with a keynote on day one. GeekWire says Daigle expects it to cover more than code generation. He named tools across the full software lifecycle, proactive security, and ways to tell whether software is working after deployment. He said GitHub wants to fix core parts of the platform, such as Git and Actions, so people can trust it for the next decade.
Those are previews and not announcements. The test will be whether GitHub backs them with reliability data and not only with roadmap slides.
Bottom line
Microsoft's bet is that GitHub's culture and Azure's scale can strengthen each other. The skeptical view is that a half-finished migration under heavy agent load is hard to defend with vision statements alone. Daigle's account is candid about the growing pains. Developers and admins will judge the integration by uptime in the months ahead.