Microsoft’s MAI Routing Is a Signal for How Model Selection Settles

Microsoft’s MAI Routing Is a Signal for How Model Selection Settles 图片 1
Microsoft’s MAI Routing Is a Signal for How Model Selection Settles 图片 2
Microsoft’s MAI Routing Is a Signal for How Model Selection Settles 图片 3
Microsoft’s MAI Routing Is a Signal for How Model Selection Settles 图片 4

Satya Nadella published a post this week about Microsoft’s MAI model family, and the part worth reading closely isn’t the benchmarks. It’s the operational decision behind them.

Microsoft is now routing production traffic in GitHub Copilot, Excel, and Outlook to its own smaller models whenever those models match or beat frontier alternatives on the specific task at hand. Frontier models from OpenAI and Anthropic stay in the mix for the work that needs them.

His framing: “using the right model for each task, and optimizing the context, skills, tools, and agent harness around it.”

That’s almost the exact thesis we built Kilo’s Auto Efficient router around, so I want to walk through what Microsoft announced, why I think the routing decision matters more than the models, and where the parallels to our own approach are real versus where they aren’t.

What Microsoft announced

The MAI team built smaller specialized models and post-trained them against actual product workloads. The Excel team reports parity with GPT-5.6 on the most common customer tasks, running on H100- and A100-class GPUs rather than requiring the newest accelerators. In VS Code, MAI-Code-1-Flash shows higher accept rates and lower token burn than the frontier minis it replaced.

The routing mechanics are the more interesting layer. Microsoft built per-task evals, established a quality floor for each workload, and now sends requests to the cheapest model that clears that floor. Harder cases still escalate to frontier models. Nadella also argued that your evals should keep improving even if any given model is removed from the stack, which is a quieter point than the benchmark numbers but probably a more important one. If your quality depends on one provider’s roadmap, you don’t really control your own cost or capability curve.

When routing matters more than the models

Very few companies can train a custom model family against their own product harness. Microsoft can, and the results are impressive. But the part of…

添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论