Back to Blog
Developer Tools June 2, 2026 5 min read

Microsoft Build 2026: MAI-Thinking-1, Project Polaris Cuts the OpenAI Cord, Multi-Agent VS Code

Microsoft opened Build 2026 on June 2 with three headline moves: its first in-house reasoning model MAI-Thinking-1, Project Polaris replacing GPT-4 Turbo in GitHub Copilot, and multi-agent support shipping directly inside VS Code.

Microsoft Build 2026: MAI-Thinking-1, Project Polaris Cuts the OpenAI Cord, Multi-Agent VS Code

Microsoft opened Build 2026 in San Francisco on June 2 with announcements that amount to a significant architectural shift in how the company builds AI into its developer stack. The headline: Microsoft no longer wants to depend entirely on OpenAI for the models powering its products.

MAI-Thinking-1 is Microsoft’s first dedicated reasoning model built in-house and not constructed via distillation from an OpenAI checkpoint. Announced by AI chief Mustafa Suleiman at the keynote, MAI-Thinking-1 targets enterprise customers with complex multi-step reasoning tasks — legal analysis, financial modeling, and code-heavy workflows that benefit from deliberate chain-of-thought processing. It joins the growing list of reasoning-first models competing with OpenAI’s o-series and Google’s Deep Think tier.

Project Polaris is the more disruptive announcement for most developers. Starting in August 2026, GitHub Copilot will replace GPT-4 Turbo with Polaris — Microsoft’s own mixture-of-experts coding model — as the default for all subscribers. The migration is automatic, with a three-month fallback option available for teams that need to test compatibility. Polaris was built specifically for coding and agentic coding tasks; Microsoft says it outperforms GPT-4 Turbo on internal benchmarks across code completion, test generation, and inline documentation.

The third major announcement is multi-agent VS Code. The extension now ships with an orchestrator-and-specialist architecture: a planner agent decomposes a developer’s objective, then dispatches parallel subagents for linting, test generation, documentation, and security review simultaneously. Results surface in a unified interface without requiring multiple separate prompts. Copilot Workspace also reached general availability at Build, giving GitHub Issues the ability to trigger Azure-hosted agent pipelines that write code, run tests, and open pull requests automatically.

Taken together, these moves signal that Microsoft is building a self-sufficient AI model supply chain inside its developer products. The company still sells OpenAI access through Azure OpenAI Service, but the products hundreds of millions of developers use daily — VS Code, GitHub Copilot, Copilot Workspace — are increasingly powered by Microsoft’s own models.

For developers, the immediate impact lands in August when Copilot silently switches to Polaris. The three-month fallback window exists precisely because Microsoft knows some workflows are sensitive to model-specific behavior. Teams should start evaluating Polaris in preview now rather than discovering rough edges at the August cutover.

Build 2026 also confirmed new image generation models (MAI-Image-2.5 and MAI-Image-2.5-Flash) for enterprise and developer use cases, and new Arm-native developer tooling as part of the Windows-on-Arm push. The full session recordings are available on Microsoft Developer.

Sources

Microsoft GitHub Copilot AI models developer tools