M
Microsoft
2026-06-18
Architecture Shift Impact: Major Conf: 85%

Microsoft Shifts Copilot Cowork to Usage-Based Pricing, Eyes DeepSeek for Cost-Efficiency

Summary

Microsoft transitions Copilot Cowork to usage-based billing (Copilot Credits) and considers integrating fine-tuned DeepSeek V4 or open-source models as low-cost alternatives, hosted on Azure. This move addresses high costs from intensive usage and signals a multi-model strategy.

Key Takeaways

Microsoft transitions its enterprise Agentic AI tool Copilot Cowork from unlimited subscription to usage-based billing via Copilot Credits, with pricing dynamically calculated from model usage, context retrieval, tool calls, and runtime. Executive VP Charles Lamanna cited uncontrolled costs from users running hundreds of tasks weekly. More critically, Microsoft is exploring integration of fine-tuned DeepSeek V4 or an open-source model as a low-cost alternative, fully hosted on Azure with enterprise security and data residency controls. This signals a multi-model strategy and acknowledges Chinese LLM cost advantages.

Why It Matters

Ostensibly a cost move, this is Microsoft's defense against OpenAI pricing and encirclement of Anthropic/Claude Code. By adopting DeepSeek, it reduces dependency on OpenAI while locking customers into Azure via data residency. The hidden trap: Copilot Credits billing is opaque, making cost unpredictable. Fine-tuning DeepSeek V4 may require data sharing, deepening Azure lock-in. Performance limitations (e.g., tail latency, lower accuracy in complex tasks) compared to GPT-4o/Claude 3.5 pose engineering trade-offs. Future model switching incurs high migration costs and redundant fine-tuning.

PRO Decision

【Vendors】Google Cloud and AWS should launch multi-model agentic AI services emphasizing cross-cloud portability and open-source neutrality to counter Azure lock-in. Anthropic must improve Claude Code pricing transparency and highlight tail latency advantages in code generation. 【Enterprises】CIOs should independently audit Copilot Credits billing models and demand historical cost simulations. Benchmark DeepSeek model accuracy and latency for critical tasks. Establish a model exit strategy to avoid Azure toolchain lock-in. 【Investors】See this as Microsoft's defensive move to reduce OpenAI dependency, but introducing DeepSeek may shift vendor concentration risk to Chinese models. Monitor Azure AI revenue volatility from model switching and compliance hurdles (e.g., data sovereignty).

Source: 智东西/36氪
View Original →

Get 3-5 key AI infrastructure signals weekly →

💬 Comments (0)