Microsoft launches MAI-Thinking-1 — its own reasoning model — in public preview on Azure AI Foundry
TL;DR
At Build 2026 on June 2, 2026, Microsoft launched MAI-Thinking-1, a mid-weight large language model for chat and reasoning, in public preview through Azure AI Foundry. It arrived alongside three other new MAI models (MAI-Image-2.5, MAI-Transcribe-2, MAI-Voice-2) as part of a broader first-party model push — what Microsoft's Build news framed as seven new MAI models overall.
Public preview
MAI-Thinking-1 status at launch — available to try in the Azure AI Foundry catalog as of Build 2026
4 new models
New MAI models in Foundry preview: MAI-Thinking-1 (reasoning/chat), MAI-Image-2.5, MAI-Transcribe-2, MAI-Voice-2
Mid-weight LLM
Microsoft's official description of MAI-Thinking-1 — a mid-weight large language model for chat and reasoning (no size or benchmark disclosed)
Early July 2026
Expected GA for Foundry hosted agents — the runtime layer for deploying MAI-based agents to production
At Build 2026 on June 2, 2026, Microsoft launched MAI-Thinking-1 — a mid-weight large language model for chat and reasoning — in public preview through Azure AI Foundry. It was one of four new MAI models entering the Foundry catalog, part of what Microsoft's official Build news framed as seven new MAI models overall. The launch is the latest sign of Microsoft building out first-party models alongside the OpenAI models it has historically deployed across its products.
What MAI-Thinking-1 is. Microsoft's official description is concise: MAI-Thinking-1 is "a mid-weight large language model for chat and reasoning," available to try in the Foundry catalog. Microsoft did not disclose model size, training compute, or benchmark scores in its Build announcement. Some Build coverage reported that MAI-Thinking-1 was trained from scratch without distillation from third-party frontier models such as OpenAI's — a notable claim if accurate, but one that does not appear in Microsoft's own published Build materials as of writing. We report the official framing — a first-party reasoning model in public preview — and flag the "no distillation" detail as reporting Microsoft has not confirmed.
The other MAI models. Three additional MAI models entered public preview alongside MAI-Thinking-1: MAI-Image-2.5 (an updated image generator with image-to-image editing), MAI-Transcribe-2 (a speech-to-text model with speaker diarization and content biasing), and MAI-Voice-2 (a multilingual text-to-speech model with voice cloning). Together they cover the four core generative modalities — text, image, transcription, and voice. Pricing for the new models was not announced at Build; the Foundry catalog listing is the access path for developers.
The broader Foundry positioning. The MAI family is part of Microsoft's wider "AI optionality" pitch at Build: within a single Azure AI Foundry deployment, enterprise customers can route workloads through Microsoft's own MAI models, OpenAI, or third-party model families that Foundry supports — including Claude, Llama, DeepSeek, and Mistral — under one governance and billing stack. Foundry also shipped platform updates at Build: Foundry IQ Knowledge Bases reached general availability, Voice Live became generally available for prompt agents, and hosted agents in Foundry Agent Service are expected to reach general availability by early July 2026.
For developers building on Azure. MAI-Thinking-1 is a new option in the Foundry catalog for reasoning and chat tasks, governed and billed within the same Azure stack teams already use. Public preview status means it is available to evaluate but not production-hardened — treat it as an evaluation candidate, not an immediate production replacement for an established model choice. The Foundry hosted-agents runtime (expected GA in early July 2026) is the intended deployment layer for production agentic use.
Why It Matters
Model supply-chain dependency is becoming a first-order question in enterprise AI procurement. Most AI applications, cloud platforms, and developer tools are built on one or two frontier models — heavily OpenAI's. If your stack routes entirely through one provider, you're exposed to that provider's pricing, roadmap, and availability decisions. Microsoft shipping its own reasoning model into Foundry — under the same governance and billing layer as OpenAI and third-party models — is a direct answer to that exposure: it gives Azure customers a Microsoft-native option to evaluate without leaving their existing stack. The strategic signal is broader than any one model's quality: the major platforms are each building their own model tier rather than only reselling a partner's, and 'AI optionality' (swap the underlying model, keep the governance) is becoming the enterprise default. Whether MAI-Thinking-1 is competitive on quality is a separate question that independent benchmarks, not launch framing, will answer.
Who's Affected
- — Azure developers and enterprise AI teams — MAI-Thinking-1 is a new catalog option for reasoning and chat workflows inside Azure AI Foundry. Worth evaluating where you want a Microsoft-native model under your existing Azure governance, or want to reduce single-provider dependency.
- — Teams with model-provenance or compliance requirements — A first-party Microsoft model under the Azure governance stack is worth evaluating for regulated workloads. Run your own benchmarks; Microsoft did not publish performance data at launch, and the 'no distillation' detail is unconfirmed reporting.
- — Developers building multimodal pipelines — MAI-Image-2.5 (image generation and editing), MAI-Transcribe-2 (speech-to-text with speaker diarization), and MAI-Voice-2 (multilingual TTS with voice cloning) are new first-party options if you're already on Azure and want to consolidate vendors.
- — Enterprise procurement teams — Foundry's 'AI optionality' (Microsoft, OpenAI, Claude, Llama, DeepSeek, Mistral under one stack) strengthens the case for Azure as a consolidation point — and your negotiating position on any single model provider's pricing.
What To Do Now
- 1. Evaluate MAI-Thinking-1 on your own tasks if you're already on Azure. Public preview is early access, not production readiness, and Microsoft published no benchmarks. Run it against your specific workloads rather than drawing conclusions from launch framing.
- 2. MAI-Transcribe-2's speaker diarization is the most immediately practical of the four for content, media, and meeting-transcription workflows already on Azure. Worth a focused test if you run transcription at scale.
- 3. The 'AI optionality' message matters even if you don't adopt MAI now. A credible first-party model option strengthens your leverage in pricing conversations with any single model provider. That's a procurement takeaway, not just a technical one.
More on this topic — Best AI Chatbots
Independent Review
ChatGPT
Pricing, pros and cons, real-world verdict — no affiliate spin.
Read the ChatGPT reviewMore from ToolNav News
Microsoft makes Windows the local execution layer for AI agents — Aion models, Execution Containers, and on-device AI ship at Build
2026-06-02
Anthropic Restores Claude Fable 5 Globally After 18-Day Export-Control Suspension
2026-07-01
GitHub launches the Copilot App — an agent-native desktop where every session runs in its own worktree
2026-06-02