Microsoft launches $2.5B AI implementation subsidiary with 6,000 embedded engineers

Microsoft has formally incorporated a new subsidiary, Microsoft Frontier Co., funded with $2.5 billion and staffed by 6,000 employees who will sit inside enterprise client organizations to guide AI selection and deployment. The company announced the move on July 2, according to Reuters, naming Unilever and Novo Nordisk among its initial clients.

The unit brings together existing Microsoft forward deployed engineers, technical consultants, industry-specialist salespeople, and support staff. Rodrigo Kede Lima, who previously led Microsoft's Asia business, will serve as president, CNBC reported.

Why enterprises need an intermediary now

The core problem Frontier Co. is designed to solve is a familiar one for anyone running enterprise technology: large organizations are no longer anchoring to a single AI provider. Reuters reported that companies are increasingly mixing open-source models with commercial offerings from providers like Anthropic and OpenAI, and the cost and complexity of managing that portfolio is extending the time it takes to generate a return.

Judson Althoff, CEO of Microsoft's commercial business, told Reuters that the new entity grew partly from lessons learned building Microsoft's own Copilot product. When Copilot launched, it was tied exclusively to OpenAI models, and the arrival of competing models from DeepSeek and Google's Gemini exposed how risky that dependency was. "Three years ago, when we built Copilot, we made a mistake by binding it to OpenAI models only," Althoff told Reuters. "You wanted models to amplify your intelligence and be able to have that sort of swappability for state-of-the-art and fine-tuning."

Althoff told CNBC that enterprise clients are genuinely uncertain about which AI path to take. He described customers wrestling with whether to standardize on a single model, adopt a family of models, or rethink existing business processes before touching AI at all. Frontier Co. is positioned to answer those questions from inside the client's own environment, using the client's proprietary data.

Client data stays with the client

One design decision that will matter to procurement and legal teams: clients own the outputs. According to Reuters, Microsoft Frontier Co. will not take back the results of its integration work. That stands in contrast to arrangements where a vendor retains rights to model-training data derived from customer engagements, a concern that analyst Patrick Moorhead of Moor Insights and Strategy flagged to Reuters. Moorhead noted that large enterprises increasingly worry that training frontier AI labs on their workflows could eventually give those labs the expertise to compete in fields like coding and law.

Frontier Co. will also integrate tools from outside Microsoft's own portfolio. Althoff told CNBC that relative to Palantir, which popularized the forward deployed engineering title, Frontier Co. supports more models, more data connectors, and more integrations with open systems of record.

Forward deployed engineering goes mainstream

The launch caps a rapid industry convergence around what is now called forward deployed engineering. AWS committed $1 billion to its own embedded AI engineer unit just two days before Microsoft's announcement, Reuters noted. Anthropic and OpenAI both stood up FDE groups in May 2026, each partnering with private equity firms, banks, and consulting firms, according to CNBC. Palantir, which CNBC credits with coining the job title, has long used the model with government and defense clients.

Earlier in 2026, Accenture and EY each announced alliances with Microsoft specifically to deliver AI-focused FDE programs, CNBC reported. That signals the model is attracting a broader ecosystem of delivery partners beyond the hyperscalers themselves.

What this means for your team

• Evaluate IP ownership clauses before signing any FDE engagement: Frontier Co.'s client-retains-outputs model is not universal across competing programs, and your legal team should compare terms explicitly.
• Audit your current AI vendor mix. If your organization is already running multiple models, Frontier Co.'s multi-provider integration approach may reduce internal coordination costs compared with managing separate vendor relationships.
• Ask vendors about model portability. Althoff's public acknowledgment that single-model lock-in was a strategic mistake at Microsoft is a useful reference point when negotiating AI contracts with any provider.
• Compare the scale benchmarks: Microsoft is deploying 6,000 engineers against $2.5 billion; AWS is deploying $1 billion. These figures give procurement teams a baseline for evaluating the depth of commitment in any vendor's FDE proposal.