Microsoft just admitted its biggest AI mistake — and spent $2.5 billion fixing it 微软刚刚承认了其最大的人工智能错误——并花费了25亿美元来修复它。
Microsoft’s latest AI services announcement suggests the era of standardizing on a single model may be ending. This week, the company launched a $2.5 billion AI adoption business designed to help enterprises customize AI deployments and use multiple models rather than lock themselves into a single provider — part of a larger shift toward systems that route each request to the model best suited to the task.微软最新的人工智能服务公告表明，标准化单一模型的时代可能即将结束。本周，该公司启动了一项价值25亿美元的人工智能采用业务，旨在帮助企业定制人工智能部署并使用多种模型，而不是将自己锁定在单一供应商上——这是朝着将每个请求路由到最适合该任务的模型的系统更大转变的一部分。
Simply put, the company that arguably has the deepest single-model partnership in the industry is now selling model swappability as the product.简而言之，这家可以说是行业内单一模型合作伙伴关系最深的公司，现在正在将模型可互换性作为产品出售。
Betting $2.5 billion on flexibility豪掷25亿美元押注灵活性
Microsoft said Thursday it is creating a new operating entity, Microsoft Frontier Company, to help corporate customers select AI technologies that actually work for their businesses and produce a return on investment, Reuters reported. The unit launches with $2.5 billion in funding from Microsoft and will work with customers including Unilever and Novo Nordisk.据路透社报道，微软周四表示，它将创建一个新的运营实体Microsoft Frontier Company，帮助企业客户选择真正适合其业务并产生投资回报的人工智能技术。该部门将获得微软25亿美元的资金，并与包括联合利华和诺和诺德在内的客户合作。
The new firm will help customers choose and integrate AI tools — from Microsoft and external providers — with each customer’s internal data. Customers will own the results of that work rather than handing it back to Microsoft. The move puts Microsoft alongside Palantir, which is doing similar work with large customers using Nvidia’s open-source models, and Amazon Web Services, which recently launched a $1 billion embedded-engineering unit of its own. 这家新公司将帮助客户选择并整合来自微软和外部供应商的人工智能工具，并与客户的内部数据相结合。客户将拥有这些工作的成果，而不是将其交还给微软。此举使微软与Palantir（该公司正在使用英伟达的开源模型与大型客户进行类似工作）以及亚马逊网络服务（近期推出了自己的10亿美元嵌入式工程部门）并驾齐驱。
What’s most telling is the reasoning. Judson Althoff, CEO of Microsoft Commercial Business, told Reuters the new firm grew partly out of Microsoft’s own experience watching models like DeepSeek and Google’s Gemini catch up to OpenAI. Referring to the original Copilot, he said, “we made a mistake by binding it to OpenAI models only.” Customers, Althoff said, care more about the combination of their data and the models than about any particular model — and they need the ability to swap models quickly as the state of the art shifts.最说明问题的是其背后的推理。微软商业业务首席执行官Judson Althoff告诉路透社，这家新公司的成立部分源于微软自身的经验，即目睹了DeepSeek和谷歌Gemini等模型追赶OpenAI的过程。在提到最初的Copilot时，他说：“我们犯了一个错误，只将它绑定到OpenAI模型上。”Althoff表示，客户更关心他们的数据与模型的结合，而不是任何特定模型——而且他们需要随着技术发展快速切换模型的能力。
“We made a mistake by binding it to OpenAI models only.”“我们犯了一个错误，只将它绑定到OpenAI模型上。”
One model no longer fits单一模型不再适用
Consider a typical customer service application that might need to summarize a support ticket, analyze a 300-page contract, generate an email, transcribe a meeting and review source code. Those aren’t necessarily the same problem. A model like Google’s Gemini, with a context window of a million tokens or more, may be the right choice for the contract. A small, fast model like OpenAI’s GPT-5.4 mini or Anthropic’s Claude Haiku may handle ticket summaries at a fraction of the cost. The transcription may go to a purpose-built model like Whisper. And if regulators require customer data to stay on-premises, an open-weight model like Meta’s Llama or Mistral is often the preferred choice.考虑一个典型的客户服务应用程序，它可能需要总结支持工单、分析一份300页的合同、生成电子邮件、转录会议和审查源代码。这些不一定都是相同的问题。像谷歌Gemini这样具有百万级令牌上下文窗口的模型可能适合处理合同。像OpenAI的GPT-5.4 mini或Anthropic的Claude Haiku这样小巧快速的模型可以以较低的成本处理工单摘要。转录任务可能由像Whisper这样的专用模型完成。如果监管机构要求客户数据保留在本地，那么像Meta的Llama或Mistral这样的开放权重模型通常是首选。
Instead of choosing a single foundation model, developers increasingly choose several — and the application decides which one handles each request.开发者不再选择单一的基础模型，而是越来越多地选择多个模型——由应用程序决定哪个模型处理每个请求。
AI gateways become core infrastructureAI网关成为核心基础设施
The model is just one component of the stack, so the decision to route the request has to live somewhere. That’s why developers are forgoing hard-coding an application to a single model and building systems that can choose among several. The routing logic might prioritize cost for one request, speed for another, or keep sensitive workloads on a local model. That way, if one provider experiences an outage, traffic can be routed elsewhere without changing the application itself.模型只是堆栈中的一个组件，因此路由请求的决策必须存在于某个地方。这就是为什么开发者放弃将应用程序硬编码到单一模型，而是构建能够在多个模型之间选择的系统。路由逻辑可能为某个请求优先考虑成本，为另一个请求优先考虑速度，或者将敏感工作负载保留在本地模型上。这样，如果某个供应商出现故障，流量可以路由到其他地方，而无需更改应用程序本身。
The company that arguably has the deepest single-model partnership in the industry is now selling model swappability as the product.这家可以说是行业内单一模型合作伙伴关系最深的公司，现在正在将模型可互换性作为产品出售。
That changes what developers build这改变了开发者的构建方式
Once companies stop relying on a single model, the challenge shifts to building the systems that decide which model to use for each request.一旦公司停止依赖单一模型，挑战就转向构建决定每个请求使用哪个模型的系统。
That means developers need tools to route requests, compare model performance, monitor reliability, control costs, enforce security policies and switch to another model if one goes down, which is a very different engineering problem, especially since deciding which model should respond to a request occurs every time someone uses your application. At enterprise scale, those decisions happen millions of times a day, so they have to be fast, reliable and easy to manage.这意味着开发者需要工具来路由请求、比较模型性能、监控可靠性、控制成本、执行安全策略，并在一个模型出现故障时切换到另一个模型，这是一个非常不同的工程问题，特别是因为每次有人使用应用程序时都需要决定哪个模型应响应请求。在企业规模下，这些决策每天发生数百万次，因此它们必须快速、可靠且易于管理。
The ecosystem is already responding生态系统已经在响应
Open-source proxies like LiteLLM and gateways like Portkey normalize APIs across providers. Orchestration frameworks such as LangChain and LangGraph assume the presence of multiple models from the start. The Model Context Protocol (MCP) is making tool integrations portable across models rather than bound to one vendor. And the cloud providers themselves — Amazon Bedrock, Azure AI Foundry, Google Vertex AI — now expose many models behind a single API.像LiteLLM这样的开源代理和像Portkey这样的网关正在标准化跨供应商的API。像LangChain和LangGraph这样的编排框架从一开始就假设存在多个模型。模型上下文协议（MCP）使工具集成可在多个模型之间移植，而不是绑定到一个供应商。云提供商本身——Amazon Bedrock、Azure AI Foundry、Google Vertex AI——现在也在单个API后面暴露多个模型。
Orchestration is the new moat编排是新的护城河
Core models will keep improving. But as performance converges for many business tasks, orchestration becomes the challenge. Microsoft’s announcement is one indication that the largest vendors believe enterprises are heading in that direction and are willing to spend billions to be the ones holding the routing layer.核心模型会不断改进。但随着许多业务任务的性能趋于一致，编排成为挑战。微软的公告表明，最大的供应商认为企业正在朝着这个方向发展，并且愿意花费数十亿美元来持有路由层。
Instead of treating the model as the platform, enterprises are consistently treating it as a replaceable component behind an orchestration layer.企业不再将模型视为平台，而是始终将其视为编排层后面的可替换组件。
The cloud era taught developers not to tie applications too tightly to one server; containerization made infrastructure portable. Now the same philosophy is being applied to AI. Instead of treating the model as the platform, enterprises are consistently treating it as a replaceable component behind an orchestration layer.云时代教会开发者不要将应用程序过于紧密地绑定到单一服务器；容器化使基础设施可移植。现在同样的理念正在应用于人工智能。企业不再将模型视为平台，而是始终将其视为编排层后面的可替换组件。
