Microsoft launches Frontier Company with $2.5B investment to embed AI engineers inside enterprise customers

Microsoft is putting $2.5 billion and 6,000 engineers behind a new operating business called Microsoft Frontier Company, announced July 2 by Judson Althoff, CEO of Microsoft Commercial Business. The unit is built to embed AI engineering talent directly inside enterprise customer organizations, moving well past the advisory or project-based model that has defined enterprise AI services to date.

The announcement signals a structural shift in how Microsoft intends to compete for large enterprise AI budgets. Rather than selling software and leaving integration to partners, Frontier Company puts Microsoft engineers on-site to co-design, deploy, and iterate on AI systems alongside customer teams, with contracts tied to measurable business outcomes.

What the model actually looks like

Frontier Company is organized around what Microsoft describes as a continuous improvement loop between two platforms: an intelligence platform that compounds a customer's proprietary data, workflows, and decision-making over time, and a trust platform that handles governance, security, and FinOps-based ROI tracking. The engineering unit works between those two layers to fine-tune agentic business processes and ensure the system keeps improving after go-live.

That framing matters for operations leaders evaluating the engagement model. This is not a fixed-scope implementation followed by a handoff. Microsoft is positioning Frontier Company as a permanent or long-term presence, continuously refining AI models and workflows as business conditions change.

Rodrigo Kede Lima, who has led enterprise-wide transformations across the Americas and Asia during six years at Microsoft, will serve as president of the new unit. He brings three decades of industry experience to the role, according to the Microsoft Blog announcement.

Early customer deployments

Microsoft cited several live engagements. At LSEG (London Stock Exchange Group), Frontier Company engineers helped embed AI into LSEG Workspace so finance professionals can query complex structured and unstructured financial content in natural language. The system is refined iteratively through client feedback and real-time user testing, with each cycle improving model quality and scope. Additional named deployments include Land O'Lakes, Unilever, and Novo Nordisk, though Microsoft did not disclose specific outcome metrics for those accounts in the announcement.

IP protection as a hard contractual line

The most operationally significant element for procurement and legal teams may be the IP protection commitment. Microsoft is making an explicit promise that customer data, proprietary processes, and competitive intelligence will not feed shared model training. The concern, which Microsoft CEO Satya Nadella addressed publicly, is that AI vendors could effectively absorb and commoditize the institutional knowledge of the enterprises they serve. Frontier Company's model is structured to prevent that.

On the model side, Frontier Company supports a heterogeneous platform. Customers can run workloads across models from OpenAI, Anthropic, Microsoft AI, open-source projects, or industry-specific models, and are not locked into any single provider. For IT leaders managing multi-cloud or multi-model strategies, that flexibility is a practical procurement consideration.

Partner ecosystem for scale

Microsoft acknowledged it cannot staff every customer engagement directly at 6,000 engineers. To reach global scale, Frontier Company will work through its Global SI partner network. Accenture has already launched a dedicated Microsoft Forward Deployed Engineering practice. EY and Microsoft announced a joint global initiative earlier in 2026 focused on scaling AI value creation across the enterprise. Capgemini, KPMG, and PwC are also named as active FDE partners.

For enterprise buyers, this means Frontier Company engagements may be delivered in part through those SIs rather than exclusively by Microsoft staff. Procurement teams negotiating contracts should clarify which roles Microsoft fills directly and which are covered by the partner tier.

What this means for your team

• Evaluate engagement terms carefully: ask Microsoft and any SI partner which deliverables are outcome-tied and how performance is measured, since the Frontier Company model is built around measurable business outcomes rather than time-and-materials billing.
• Audit your IP and data protection clauses: request explicit contractual language confirming that proprietary data and workflows will not be used in any shared model training, and verify how that commitment extends to SI subcontractors.
• Assess model flexibility requirements before signing: confirm that your current or planned multi-model strategy (across OpenAI, Anthropic, open-source, or specialized models) is fully supported without added licensing or lock-in provisions.
• Determine SI versus direct Microsoft coverage: ask which Frontier Company roles will be staffed by Microsoft engineers versus SI partner staff, and how accountability is structured across that boundary.