MAI (Microsoft)

MAI is a family of large language models, reasoning models, coding models, image-generation systems, speech-synthesis models, and automatic-speech-recognition models developed or adapted by Microsoft AI, an artificial-intelligence organization within Microsoft. The letters MAI are used as Microsoft's model prefix and brand; official materials generally refer to “MAI models” rather than defining a separate technical expansion of the abbreviation.

The family does not represent one shared neural architecture. It includes a 962-billion-parameter sparse Mixture-of-Experts reasoning model, a smaller MoE coding model, diffusion-based image generators, text-to-speech systems, speech-recognition models, and an earlier Microsoft post-training derivative of DeepSeek-R1.

As of 10 July 2026, the principal publicly announced MAI branches are:

• MAI-Thinking-1 — Microsoft AI's flagship general-purpose reasoning and agentic language model;
• MAI-Code-1-Flash — a lower-latency coding and software-engineering model derived from the MAI-Thinking-1 training line;
• MAI-Image-2.5 and MAI-Image-2.5-Flash — image-generation and image-editing models;
• MAI-Voice-2 — multilingual prompted text-to-speech;
• MAI-Transcribe-1.5 — multilingual speech recognition with terminology biasing;
• MAI-Voice-2-Flash — an announced lower-cost speech model that Microsoft continued to describe as “coming soon” at that date.

The MAI family is integrated with Microsoft products and infrastructure including Microsoft Copilot, GitHub Copilot, Visual Studio Code, Microsoft Foundry, Azure Speech, PowerPoint, OneDrive, Bing Image Creator, and experimental MAI Playground services. Availability differs substantially by model: MAI-Thinking-1 remained in private preview in Microsoft Foundry, MAI image models were deployable through Foundry preview endpoints, MAI-Code-1-Flash was distributed through GitHub Copilot, and most current MAI checkpoints were not available as downloadable weights.

The principal open-weight exception is MAI-DS-R1, a 671-billion-parameter Microsoft post-training derivative of DeepSeek-R1 released under the MIT License in 2025. It was not pretrained from scratch by Microsoft and is architecturally distinct from Microsoft's later in-house MAI models.

History and institutional background

Formation of Microsoft AI

Microsoft announced the formation of Microsoft AI on 19 March 2024. The organization was established under Mustafa Suleyman and Karén Simonyan to lead Microsoft Copilot, consumer artificial-intelligence products, and related model research.

Microsoft AI is not synonymous with every artificial-intelligence activity at Microsoft. The company also develops the Phi small-language-model family, healthcare models, computer-vision systems, Microsoft Research projects, Azure AI services, and product-specific models. Microsoft Foundry additionally distributes models from OpenAI, Anthropic, Meta, Mistral AI, Cohere, xAI, Moonshot AI, and other providers.

The MAI programme therefore forms one part of a broader model-routing strategy in which Microsoft products can use first-party MAI or Phi models, partner models, open-weight models, retrieval systems, and specialized tools according to workload requirements.

MAI-DS-R1

MAI-DS-R1 appeared in May 2025 as an early use of the MAI name. The checkpoint is based on DeepSeek-R1, a 671-billion-parameter MoE reasoning model, and was post-trained by Microsoft AI rather than pretrained independently.

Microsoft used:

• approximately 110,000 safety and non-compliance examples from the Tulu 3 supervised-fine-tuning dataset;
• approximately 350,000 internally developed multilingual examples covering subjects on which the original model exhibited excessive blocking or bias;
• safety evaluations based partly on HarmBench and an internal blocked-topic test set.

Microsoft reported that MAI-DS-R1 answered 99.3% of samples in its blocked-topic evaluation while retaining broadly similar general reasoning performance to DeepSeek-R1. This was a developer evaluation and did not establish that all political, cultural, or safety biases had been removed.

The checkpoint remains downloadable under the MIT License. Its managed Microsoft Foundry endpoint was later retired on 27 February 2026; retirement of the hosted endpoint did not remove the weight files from Hugging Face.

First end-to-end in-house models

On 28 August 2025, Microsoft AI announced the first two models it described as products of its new internal development stack:

• MAI-Voice-1, a prompted text-to-speech model;
• MAI-1-preview, the organization's first end-to-end in-house foundation language model.

MAI-1-preview was described as a sparse MoE model pretrained and post-trained on approximately 15,000 NVIDIA H100 GPUs. It was intended for instruction following and everyday consumer queries and was first evaluated publicly through LMArena. Microsoft did not publish its parameter count, layer configuration, context length, tokenizer, training-token count, or weights.

MAI-Voice-1 was integrated into Copilot Daily, Copilot Podcasts, and Copilot Labs. Microsoft reported that it could generate one minute of speech in less than one second on a single GPU under the company's demonstration configuration. This was a serving-speed claim for a particular system rather than a universal latency figure for every voice, prompt, region, or deployment.

MAI-Image-1 and MAI-Vision-1

Microsoft announced MAI-Image-1 on 13 October 2025 as its first image-generation model developed entirely in-house. The company reported that it entered the top ten of the LMArena text-to-image leaderboard at launch. It was subsequently added to Bing Image Creator and the visual component of Copilot Audio Expressions.

A Microsoft Copilot announcement on 23 October 2025 also named MAI-Vision-1 among the company's in-house models. Microsoft had not published a standalone model card, architecture report, public checkpoint, or detailed release specification for MAI-Vision-1 by July 2026. It is therefore more accurate to describe MAI-Vision-1 as a publicly named but sparsely documented internal vision model than to assign it an inferred parameter count or capability list.

Humanist superintelligence

In November 2025, Microsoft AI described its long-term objective as humanist superintelligence: developing advanced systems intended to remain subordinate to human purposes, avoid uncontrolled autonomy, and amplify human capabilities in areas such as education, scientific discovery, health, and work.

The phrase is an organizational and governance principle rather than a technical classification. It does not mean that an MAI model is independently certified as superintelligent, aligned in every environment, or incapable of causing harm.

Expansion during 2026

Microsoft released MAI-Image-2 in March 2026, followed by the lower-cost MAI-Image-2-Efficient in April.

On 2 April 2026, Microsoft announced expanded Foundry availability for MAI-Image-2, MAI-Voice-1, and MAI-Transcribe-1. These were the first MAI image and audio models offered as broadly deployable Microsoft Foundry services.

On 2 June 2026, Microsoft AI announced a seven-model package covering reasoning, coding, images, speech synthesis, and transcription:

• MAI-Thinking-1;
• MAI-Code-1-Flash;
• MAI-Image-2.5;
• MAI-Image-2.5-Flash;
• MAI-Transcribe-1.5;
• MAI-Voice-2;
• MAI-Voice-2-Flash.

The first six had a model page, model card, production integration, or deployment path at launch. MAI-Voice-2-Flash was announced as an upcoming low-cost, low-latency variant, but a standalone model card and general deployment endpoint had not been published by 10 July 2026.

Release chronology

Date	Model or system	Publicly disclosed scale	Principal role	Initial availability
May 2025	MAI-DS-R1	671B total; inherited DeepSeek-R1 MoE architecture	General reasoning model post-trained to reduce excessive blocking and improve safety behaviour	Open weights on Hugging Face; former Foundry endpoint
28 August 2025	MAI-Voice-1	Not disclosed	Expressive English text-to-speech with prompted voices and long-form generation	Copilot Daily, Copilot Podcasts, Copilot Labs; later Microsoft Foundry
28 August 2025	MAI-1-preview	Not disclosed; sparse MoE	First end-to-end in-house MAI foundation language model	LMArena testing and internal Copilot evaluation
13 October 2025	MAI-Image-1	Not disclosed	In-house text-to-image generation	LMArena, then Bing Image Creator and Copilot experiences
23 October 2025	MAI-Vision-1	Not disclosed	Internally developed visual model; limited public technical information	Named in Microsoft Copilot product materials
19 March 2026	MAI-Image-2	Public model card gives a 10B–50B non-embedding range	Higher-quality and faster text-to-image generation	Microsoft products; Foundry preview from April
2 April 2026	MAI-Transcribe-1	Not disclosed	Automatic speech recognition in 25 languages	Azure Speech and Microsoft Foundry
14 April 2026	MAI-Image-2-Efficient / MAI-Image-2e	Public model card gives a 10B–50B range	Lower-cost and higher-throughput image generation	Microsoft Foundry and MAI Playground
2 June 2026	MAI-Thinking-1	962B total / 34.7B active	General reasoning, mathematics, coding, tool use, and agentic tasks	Microsoft Foundry private preview
2 June 2026	MAI-Code-1-Flash	137B total / 5B active	Fast agentic coding and repository-level software engineering	GitHub Copilot for individual users in Visual Studio Code
2 June 2026	MAI-Image-2.5	20B non-embedding parameters	High-fidelity image generation and image editing	Microsoft Foundry, PowerPoint, OneDrive, MAI Playground
2 June 2026	MAI-Image-2.5-Flash	20B non-embedding parameters	Lower-cost image generation and editing	Microsoft Foundry and MAI Playground
2 June 2026	MAI-Transcribe-1.5	Not disclosed	Speech recognition in 43 languages with terminology biasing	Azure Speech and Microsoft Foundry
2 June 2026	MAI-Voice-2	Not disclosed	Prompted multilingual speech synthesis in 15 languages and 18 locales	Microsoft Foundry and selected Microsoft products
2 June 2026	MAI-Voice-2-Flash	Not disclosed	Announced low-cost, low-latency speech-synthesis variant	Announced as “coming soon”; no standalone public release by 10 July 2026

Naming and scope

The MAI name covers checkpoints, hosted services, product-integrated models, and in some cases a broader development programme. Several distinctions are necessary.

• MAI is not one architecture. MAI-Thinking-1 and MAI-Code-1-Flash are sparse text Transformers; MAI-Image models are diffusion or flow-matching systems; Voice models synthesize waveforms or acoustic representations; Transcribe models map audio to text.
• Not every MAI model was pretrained from scratch by Microsoft. MAI-DS-R1 is a post-trained DeepSeek-R1 derivative.
• “Flash” and “Efficient” denote deployment-oriented variants. They do not necessarily imply a different fundamental task or modality.
• MAI-Voice-2-Flash was an announcement rather than a completed public release as of 10 July 2026.
• MAI-DxO is a related orchestration system rather than a single foundation-model checkpoint. The Microsoft AI Diagnostic Orchestrator combines multiple agents and models for medical-diagnosis research.
• Microsoft Foundry is a platform, not an MAI model. It hosts first-party Microsoft models and third-party systems.
• Copilot is a product family, not one model. A Copilot experience can combine MAI models with OpenAI models, Phi models, retrieval, search, policy systems, and product-specific tools.

Technical foundations

Autoregressive language modelling

MAI-Thinking-1 and MAI-Code-1-Flash are autoregressive text models. For a token sequence $x_1,\dots ,x_T$, generation can be represented as:

$P_{\theta }(x_1,\dots ,x_T)=\prod _{t=1}^T{P}_{\theta }(x_t\mid x_1,\dots ,x_{t-1}),$

where $\theta$ denotes the model parameters.

A conventional scaled dot-product attention operation is:

$\mathrm{Attention}(\mathbf{𝐐},\mathbf{𝐊},\mathbf{𝐕})=\mathrm{softmax}\left(\frac{\mathbf{𝐐}{\mathbf{𝐊}}^{\mathsf{T}}}{\sqrt{d_k}}\right)\mathbf{𝐕}.$

The published MAI-Thinking-1 implementation modifies this general pattern through Grouped-Query Attention, periodic global attention, local sliding-window attention, and sparse expert feed-forward blocks.

MAI-Thinking-1 architecture

MAI-Thinking-1 is a decoder-only Transformer with approximately 962 billion total parameters and 34.7 billion activated parameters for a token. Microsoft marketing rounds these values to approximately one trillion total and 35 billion active parameters.

Architectural property	MAI-Thinking-1
Total parameters	Approximately 962B
Active parameters	Approximately 34.7B
Transformer layers	78
Hidden-state dimension	6,656
Query heads	80
Key–value heads	8
Attention-head dimension	128
Routed experts per MoE layer	512
Experts selected per token	8
Latent down-projection dimension	3,072
Expert feed-forward first-output dimension	10,240
Dense feed-forward first-output dimension	13,312
Local-attention window	512 tokens
Attention schedule	Five local-attention layers followed periodically by one global-attention layer
Tokenizer	o200k_base-derived tokenizer
Vocabulary size	200,019
Maximum published context	262,144 tokens
Normalization	RMSNorm
Embeddings	Input and output embeddings tied
Linear-layer biases	Generally omitted

The 256K context describes the supported maximum sequence configuration. It does not imply uniform retrieval accuracy at every position or that every production deployment exposes the complete context at the same latency and cost.

Local and global attention

Most MAI-Thinking-1 attention layers use a sliding local window of 512 tokens. Periodic global layers can attend across the full available context. The published pattern groups five local-attention layers with one global-attention layer.

Local attention lowers the cost of processing long sequences because most layers avoid forming a complete $L\times L$ attention matrix. Periodic global attention permits distant information to interact but retains higher computational and memory cost in those layers.

The local-attention layers use Rotary Position Embeddings with a reported base of 10,000. The global-attention layers do not use the same explicit positional encoding. This is an unusual but deliberate design choice in the published architecture.

The model uses Grouped-Query Attention with 80 query heads and eight key–value heads. Ten query heads therefore share each key–value head, reducing key–value-cache storage relative to conventional multi-head attention.

Latent Mixture-of-Experts

MAI-Thinking-1 alternates dense feed-forward computation with sparse MoE computation. A simplified expert layer for hidden representation $\mathbf{𝐡}$ is:

$\mathrm{MoE}(\mathbf{𝐡})=\sum _{i\in {𝒮}(\mathbf{𝐡})}{g}_i(\mathbf{𝐡})E_i(\mathbf{𝐡}),$

where $E_i$ is an expert network, ${𝒮}(\mathbf{𝐡})$ is the routed subset, and $g_i$ is the corresponding gate weight.

MAI-Thinking-1 has 512 routed experts and selects eight for a token. Sparse activation reduces arithmetic relative to a dense 962-billion-parameter model, but the complete expert pool must still be stored, sharded, or offloaded.

Microsoft calls the design LatentMoE. A shared learned projection first maps the token representation from the main hidden dimension into a lower-dimensional latent space. Expert routing and computation occur around this representation, after which a shared projection maps the result back to the full hidden space.

In simplified notation:

$\mathbf{𝐳}=W_{\mathrm{d}\mathrm{o}\mathrm{w}\mathrm{n}}\mathbf{𝐡},$

$\widetilde{\mathbf{𝐳}}=\sum _{i\in {𝒮}(\mathbf{𝐡})}{g}_i(\mathbf{𝐡})E_i(\mathbf{𝐳}),$

$\mathbf{𝐲}=W_{\mathrm{u}\mathrm{p}}\widetilde{\mathbf{𝐳}}.$

Routing is calculated from the original representation rather than only from the compressed latent vector. The implementation uses top-eight routing with normalized gates, global-batch load balancing, and dropless execution: tokens are not intentionally discarded merely because an expert reaches a fixed local capacity.

A ratio such as 512 experts with eight selected should not be interpreted as a 64-fold reduction in total inference cost. Attention, embeddings, dense layers, routing, communication, load balancing, memory movement, and shared projections remain active.

MAI-Code-1-Flash architecture

MAI-Code-1-Flash is also a sparse MoE Transformer. Its model card reports:

Property	MAI-Code-1-Flash
Total parameters	137B
Active parameters	5B
Input and output	Text to text
Context length	256K tokens
Architecture	Transformer with sparse MoE layers
Officially supported language	English
Training period	March–May 2026

The model begins from an MAI-Thinking-1 mid-training checkpoint. It is therefore an internally derived specialist rather than a separate model pretrained independently from random initialization.

Microsoft's statement that it was trained without third-party-model distillation means that no external provider's reasoning traces were used as the primary teacher. It does not mean that the coding checkpoint has no dependency on MAI-Thinking-1 or that its training contained no synthetic data.

Diffusion and flow matching in MAI-Image

The MAI-Image-2 line is described as diffusion-based and trained with a flow-matching objective. The precise network topology and complete noise schedule have not been disclosed publicly.

A generic linear flow-matching path can be written as:

${\mathbf{𝐱}}_t=(1-t){\mathbf{𝐱}}_0+t\mathit{ϵ},$

where ${\mathbf{𝐱}}_0$ is a data sample, $\mathit{ϵ}$ is noise, and $t\in [0,1]$. A model learns a velocity field:

$v_{\theta }({\mathbf{𝐱}}_t,t,c)\approx \mathit{ϵ}-{\mathbf{𝐱}}_0,$

conditioned on prompt or image context $c$. Inference numerically follows the learned flow from noise toward an image.

These equations illustrate the general method and are not a claim that Microsoft uses this exact interpolation, parameterization, or solver in production.

MAI-Image-2.5 has 20 billion non-embedding parameters, a 32K context setting, and supports both text prompts and image-conditioned editing. The documented maximum output area is 1,048,576 pixels, equivalent to 1024×1024, although one dimension may exceed 1024 when the other is smaller and the total-area limit is respected.

Prompted speech synthesis

MAI-Voice models use short reference recordings to condition speech generation without requiring a separate fine-tuning run for every voice. A conceptual conditional formulation is:

$P_{\theta }(\mathbf{𝐚}\mid \mathbf{𝐭},\mathbf{𝐫},\mathbf{𝐬}),$

where:

• $\mathbf{𝐚}$ is the generated audio;
• $\mathbf{𝐭}$ is the text or SSML input;
• $\mathbf{𝐫}$ is reference audio;
• $\mathbf{𝐬}$ represents style, speaker, emotion, or prosodic controls.

Microsoft has not published the parameter counts or complete acoustic architecture of MAI-Voice-1 or MAI-Voice-2. The models may contain several neural components, such as text encoders, speech-token or acoustic generators, and waveform decoders, but the exact design should not be inferred from other Microsoft speech systems.

Speech recognition and word error rate

MAI-Transcribe models map audio to text and can perform automatic language identification. The principal reported metric is Word Error Rate:

$\mathrm{WER}=\frac{S+D+I}{N},$

where $S$ is the number of substitutions, $D$ deletions, $I$ insertions, and $N$ reference words.

WER depends on text normalization, punctuation handling, language segmentation, speaker overlap, audio quality, and dataset weighting. Results from differently normalized evaluations may therefore not be directly comparable.

Pre-training and data

MAI-Thinking-1 pre-training corpus

MAI-Thinking-1 was trained on a mixture assembled by Microsoft from publicly accessible and commercially licensed sources. The report identifies web documents, source code, books, scientific papers, news, technical PDFs, mathematics, and multilingual material.

The 30-trillion-token main pre-training stage used the following approximate mixture:

Data category	Share	Approximate training tokens
Source code	54.6%	16.4T
STEM material	15.8%	4.7T
Mathematics	5.4%	1.6T
Books and journals	3.1%	0.9T
PDF documents	4.7%	1.4T
General web text	14.9%	4.5T
Other multilingual text	1.6%	0.5T

Percentages are rounded and may not sum to exactly 100%.

The technical report states that language-model-generated synthetic data was excluded from the main pre-training mixture. Microsoft attempted to identify and remove machine-generated web content and did not rely on conventional packaged open-source model-training datasets as the primary corpus. This does not mean that every source document's human authorship could be established with certainty.

Synthetic examples were used extensively later during supervised fine-tuning, reinforcement learning, environment construction, software-engineering task generation, and self-distillation.

Source-specific cutoffs

The report gives different collection cutoffs for different source families:

• web HTML — approximately September 2025;
• public GitHub code — approximately June 2025;
• web PDFs — approximately December 2025;
• books and journals — approximately March 2026.

There is therefore no single universal knowledge cutoff applying equally to every domain. Post-training environments and later specialist-model datasets can also contain material newer than the main pre-training sources.

Training stages

MAI-Thinking-1's base training used approximately 33.55 trillion tokens across three principal stages:

Stage	Tokens	Context length	Published accelerator allocation
Main pre-training	30T	16,384	8,192 NVIDIA GB200 GPUs
Long-context mid-training I	3.4T	65,536	8,192 NVIDIA GB200 GPUs
Long-context mid-training II	150B	262,144	4,096 NVIDIA GB200 GPUs

The mid-training mixture emphasized approximately:

• 55% source code;
• 35% mathematics and STEM;
• 10% general background data.

The model was trained with AdamW. Published settings include ${\beta }_1=0.95$, ${\beta }_2=0.925$, $ϵ=10^{-8}$, a peak learning rate of approximately $2\times 10^{-4}$, a minimum learning rate of approximately $2\times 10^{-5}$, gradient clipping at 1.0, and differentiated weight decay for selected components.

Hyperparameters from one training run should not be interpreted as a general optimum for every MoE model.

Training infrastructure

Microsoft developed an internal PyTorch training system referred to in the MAI-Thinking-1 report as YOLO. It implements tensor, pipeline, data, sequence, context, and expert parallelism together with fused kernels, checkpointing, fault recovery, and large-scale data streaming.

This internal framework is unrelated to the well-known YOLO computer-vision object-detection model family.

For reinforcement learning, Microsoft developed an asynchronous distributed system called Rocket. Rocket separates policy optimization from rollout inference and environment execution. Its learner uses the YOLO stack, while rollout serving uses an optimized inference system based partly on SGLang.

Asynchronous execution allows completed trajectories to enter training without requiring every worker to wait for the longest agent episode. It also introduces policy lag because some rollouts are generated by older policy versions.

The main pre-training and mid-training runs used NVIDIA GB200 systems. Microsoft reports using approximately 4,600 GB300 accelerators for large reinforcement-learning climbs. Microsoft also optimized MAI inference for its Maia 200 accelerator, but the published training report does not describe Maia 200 as the exclusive hardware for the principal pre-training run.

Post-training and the hill-climbing machine

Specialist reinforcement-learning climbs

Microsoft describes its development process as a hill-climbing machine. The phrase refers not to one algorithm or neural module but to an integrated empirical-development loop combining:

• architecture experiments;
• data construction;
• distributed training;
• executable environments;
• reward functions;
• verifiers;
• human and automated evaluations;
• safety tests;
• deployment feedback.

The MAI-Thinking-1 post-training programme used several specialist branches or “climbs”:

• mathematics, science, and competitive programming;
• software engineering, coding agents, terminals, and tools;
• general helpfulness, instruction following, dialogue, and safety.

The specialist policies were subsequently consolidated through supervised training and further reinforcement learning.

Self-distillation

Microsoft states that MAI-Thinking-1 was not distilled from third-party foundation models. The company did, however, use self-distillation: its own reinforcement-learning checkpoints and specialist policies generated or selected trajectories that were used to improve a consolidated student policy.

The distinction is important:

• Third-party distillation would use hidden reasoning or outputs from an external provider's model as the teacher.
• Self-distillation uses outputs from models or checkpoints controlled by the same developer.

Self-distillation can transfer capabilities among internal policies but can also reproduce their errors, verbosity, biases, or reward-model blind spots.

Agentic reinforcement learning

Agent-training environments included tasks in which the model had to:

• inspect repositories;
• read and modify files;
• run tests;
• execute shell commands;
• interpret failures;
• call tools;
• recover from incorrect intermediate actions;
• maintain state over multiple steps.

An agent trajectory may be represented as:

$\tau =(o_0,a_1,o_1,\dots ,a_T,o_T),$

where $o_t$ is an observation and $a_t$ an action. A simplified reinforcement-learning objective is:

$J(\theta )={\mathbb{𝔼}}_{\tau \sim {\pi }_{\theta }}[R(\tau )],$

where $R(\tau )$ can combine executable test results, task completion, policy compliance, efficiency, and model-based evaluation.

The actual Microsoft objective is more complex and was not fully disclosed.

MAI-Code-1-Flash post-training

MAI-Code-1-Flash was initialized from the MAI-Thinking-1 mid-training checkpoint and then specialized through:

1. lightweight supervised fine-tuning;
2. a code-intensive “mid2” phase containing approximately two million synthetic agentic tasks;
3. reinforcement learning across more than 150,000 executable environments;
4. direct training with the production GitHub Copilot agent harness.

Its post-training data emphasized repositories, pull requests, commits, debugging, shell scripts, code review, file question answering, instruction following, and synthetic software-engineering tasks.

The model card gives December 2025 as the training-cutoff field, while the public data summary describes some specialist data collected or generated as late as May 2026. These statements refer to different parts of the pipeline and should not be collapsed into one universal knowledge date.

Main model branches

MAI-DS-R1

MAI-DS-R1 is an open-weight DeepSeek-R1 derivative rather than an in-house base architecture. It retains DeepSeek-R1's 671-billion-parameter sparse MoE backbone and general reasoning behaviour while modifying response and safety behaviour.

The principal objectives were:

• reducing excessive refusals on historical, political, and culturally sensitive topics;
• retaining restrictions for requests assessed as genuinely harmful;
• preserving mathematics, coding, scientific reasoning, and general language performance;
• improving multilingual responsiveness.

The model inherits many limitations of DeepSeek-R1, including its architecture, original pre-training data, hardware requirements, knowledge cutoff, and potential biases. The MIT licence applies to Microsoft's distributed checkpoint, subject to other applicable rights and laws.

MAI-1-preview

MAI-1-preview was Microsoft's first end-to-end in-house foundation language model. Public information is limited to its MoE character, its use of approximately 15,000 NVIDIA H100 GPUs during pre-training and post-training, and its intended use for instruction following and everyday consumer assistance.

It was evaluated through LMArena and considered for future Copilot experiences. Microsoft did not release weights or a technical report. It should not be assigned the 962B/34.7B configuration of MAI-Thinking-1, which is a later model with its own published architecture.

MAI-Thinking-1

MAI-Thinking-1 is Microsoft AI's first fully documented in-house reasoning foundation model. It targets:

• mathematical and scientific reasoning;
• complex instruction following;
• coding;
• repository-level software engineering;
• agentic tool use;
• enterprise workflows;
• long-context processing.

The model begins without an externally supplied reasoning-trace corpus and acquires extended problem-solving behaviour through Microsoft-generated data, supervised consolidation, self-distillation, and reinforcement learning.

As of 10 July 2026, it was available through private preview in Microsoft Foundry. Microsoft announced a future public-preview path through MAI Playground, but the public Playground at that date primarily exposed image models.

MAI-Code-1-Flash

MAI-Code-1-Flash is a 137B-total, 5B-active coding model optimized for low latency and reduced serving cost.

Its documented use cases include:

• code generation and completion;
• repository question answering;
• refactoring;
• debugging;
• test execution;
• terminal use;
• multi-file modification;
• agentic tool calling;
• telemetry-grounded development tasks.

Microsoft trained it directly with the GitHub Copilot production harness so that the model learned the tool schemas, action patterns, and feedback mechanisms used by that environment.

The model uses adaptive solution-length control. Microsoft reports that it remains concise for simple requests and allocates more tokens to complex tasks, using as many as 60% fewer solution tokens than the compared Claude Haiku 4.5 configuration on selected tests.

At launch it rolled out to individual GitHub Copilot users in Visual Studio Code through the model picker and automatic routing system. GitHub Copilot CLI support was announced for a later phase. No downloadable MAI-Code-1-Flash weights or standalone general API were published.

MAI-Image-1

MAI-Image-1 is Microsoft's first fully in-house image-generation model. Microsoft emphasized photorealistic lighting, landscapes, visual diversity, and relatively fast generation.

Its exact parameter count, architecture, context limit, training-data scale, and objective were not disclosed. It entered product distribution through Bing Image Creator and Copilot Labs.

MAI-Image-2

MAI-Image-2 is a diffusion-based text-to-image model released in March 2026. Its public model card places its non-embedding parameter count in the broad 10B–50B range, rather than publishing an exact value.

The model supports:

• text-conditioned image generation;
• output up to 1024×1024 pixels;
• photorealistic and stylized content;
• product imagery;
• text rendering;
• deployment through Microsoft Foundry.

Microsoft reported at least twice the serving speed of the preceding system under selected Foundry and Copilot production workloads. Actual latency depends on resolution, prompt, deployment region, accelerator, safety processing, and service load.

MAI-Image-2-Efficient

MAI-Image-2-Efficient, exposed in Foundry under the identifier MAI-Image-2e, is a deployment-oriented derivative of MAI-Image-2.

Microsoft reported, under a specified H100 serving configuration:

• approximately 22% faster generation;
• approximately fourfold higher computational efficiency;
• approximately 41% lower price than MAI-Image-2 at launch.

The preview endpoint was scheduled for retirement on 15 August 2026, with MAI-Image-2.5-Flash listed as the recommended replacement.

MAI-Image-2.5

MAI-Image-2.5 is a 20-billion-parameter image model supporting both generation and editing.

Documented editing capabilities include:

• object replacement and removal;
• inpainting;
• background cleanup;
• text replacement;
• reduction of motion blur;
• perspective-aware insertion;
• preservation of facial identity;
• changes in pose, expression, or viewpoint;
• preservation of unaffected image regions.

Microsoft reported that the model ranked third on Arena's text-to-image leaderboard and second on its image-editing leaderboard on 1–2 June 2026.

These ranks were snapshots of human-preference voting and may change as models, evaluators, and votes are added. Human preference is also not a direct measure of factual correctness, copyright compliance, identity accuracy, or safety.

MAI-Image-2.5 was integrated into PowerPoint for presentation imagery and began rolling out to OneDrive for photo editing. It is available through Microsoft Foundry and MAI Playground.

MAI-Image-2.5-Flash

MAI-Image-2.5-Flash is a 20-billion-parameter lower-cost sibling of MAI-Image-2.5. It supports text-to-image generation and image-to-image editing with the same documented maximum output area of 1,048,576 pixels.

The Flash checkpoint trades some maximum fidelity for lower price and faster production throughput. It is a separately served model rather than merely a client-side speed setting.

MAI-Voice-1

MAI-Voice-1 is an English prompted text-to-speech model. It accepts text or SSML together with approximately five to 120 seconds of reference audio and produces a matching voice without a separate fine-tuning run.

Its capabilities include:

• single- and multi-speaker speech;
• long-form voice consistency;
• emotion and style control;
• storytelling;
• podcasts;
• meditation and educational content;
• controlled personal-voice creation.

Use of a personal voice is gated and requires recorded consent under the documented Azure Speech workflow. A short reference clip should not be treated as blanket legal authorization to reproduce another person's identity or likeness.

MAI-Voice-2

MAI-Voice-2 extends prompted speech synthesis to 15 languages across 18 locales:

• English — United States and Australia;
• Italian;
• French;
• German;
• Hindi;
• Spanish — Spain and Mexico;
• Portuguese — Brazil and Portugal;
• Korean;
• Simplified Chinese;
• Turkish;
• Russian;
• Thai;
• Dutch;
• Romanian;
• Hungarian.

The model uses approximately five to 60 seconds of reference audio and produces 24-kHz mono output. It supports emotion tags, stable long-form identity, multiple speakers, and selected code-switching combinations such as Hindi–English and Spanish–English.

In a Microsoft preference evaluation involving approximately 2,500 comparisons, raters preferred MAI-Voice-2 over MAI-Voice-1 in 72.1% of cases. In another 2,222-comparison evaluation covering 11 languages, synthetic MAI-Voice-2 speech was preferred in 45.5% of cases, human recordings in 44.0%, and 10.5% were ties.

These are subjective evaluations conducted or commissioned by Microsoft. Preference can depend on language, speaker, recording quality, content type, and rater expectations.

MAI-Voice-2-Flash

MAI-Voice-2-Flash was announced as an ultra-efficient, lower-cost speech model for latency-sensitive voice agents.

As of 10 July 2026, Microsoft continued to label it “coming soon”. No standalone public model card, parameter count, release endpoint, or supported-language table had been published. Specifications of MAI-Voice-2 should not automatically be assigned to the unreleased Flash version.

MAI-Transcribe-1

MAI-Transcribe-1 is an automatic-speech-recognition model supporting 25 languages, automatic language identification, and common audio formats including WAV, MP3, and FLAC.

At initial Foundry release, Microsoft reported batch transcription approximately 2.5 times faster than its Azure Fast Transcription comparison. MAI-Transcribe-1 did not initially support real-time streaming, speaker diarization, or explicit keyword biasing.

MAI-Transcribe-1.5

MAI-Transcribe-1.5 supports 43 languages and adds context-aware terminology biasing.

An application can supply up to approximately 200 keywords, proper names, acronyms, or domain terms. Microsoft reported as much as a 30% relative WER reduction on selected terminology-intensive tasks.

The model accepts WAV, MP3, and FLAC files up to approximately 300 MB or two hours. It performs automatic language identification but did not provide built-in speaker diarization at launch.

Microsoft reported that one hour of audio could be transcribed in approximately 15 seconds under its production test configuration, up to five times faster than selected comparison systems. Speed depends on file format, batch size, hardware, network transfer, region, and service load.

Summary of current model characteristics

Model	Modality	Total / active parameters	Context or input limit	Public distribution as of 10 July 2026
MAI-DS-R1	Text reasoning	671B / inherited DeepSeek-R1 active scale	Inherited checkpoint configuration	MIT-licensed open weights; managed Foundry endpoint retired
MAI-1-preview	Text	Not disclosed	Not disclosed	Historical LMArena and internal preview
MAI-Thinking-1	Text reasoning and tools	962B / 34.7B	256K tokens	Microsoft Foundry private preview
MAI-Code-1-Flash	Text and code	137B / 5B	256K tokens	GitHub Copilot in Visual Studio Code
MAI-Image-2	Text to image	10B–50B range	32K; up to 1024×1024	Foundry preview
MAI-Image-2-Efficient	Text to image	10B–50B range	32K; up to 1024×1024	Foundry preview; retirement scheduled for 15 August 2026
MAI-Image-2.5	Text/image to image	20B non-embedding	32K; 1,048,576 output pixels	Foundry, PowerPoint, OneDrive, Playground
MAI-Image-2.5-Flash	Text/image to image	20B non-embedding	32K; 1,048,576 output pixels	Foundry and Playground
MAI-Voice-1	Text/reference audio to speech	Not disclosed	5–120-second reference audio	Azure Speech and Foundry
MAI-Voice-2	Text/reference audio to speech	Not disclosed	5–60-second reference audio	Foundry and selected products
MAI-Voice-2-Flash	Speech synthesis	Not disclosed	Not disclosed	Announced; not independently released
MAI-Transcribe-1	Audio to text	Not disclosed	Service-specific file limits	Azure Speech and Foundry
MAI-Transcribe-1.5	Audio to text	Not disclosed	300 MB or two hours	Azure Speech and Foundry

Reported benchmark results

MAI-Thinking-1

Microsoft evaluated MAI-Thinking-1 primarily at temperature 1.0 and top-p 0.97, averaging four runs for many tasks. Agentic tests used a 256K context configuration; other reasoning tasks allowed large output budgets.

Benchmark	MAI-Thinking-1
AIME 2025	97.0%
AIME 2026	94.5%
HMMT February 2026	84.9%
GPQA-Diamond	84.2%
LiveCodeBench v6	87.7%
Terminal-Bench 2.0	46.0%
SWE-bench Verified	73.5%
SWE-bench Pro	52.8%

Selected additional developer-reported results include:

Benchmark	Score
MMLU-Pro	85
SimpleQA Verified	31
IFBench	69
AdvancedIF	85
MultiChallenge	53
GraphWalks, up to 128K	90
Berkeley Function Calling Leaderboard v3	72
LongFact	98
TruthfulQA	88
HealthBench Professional	35
MedXpertQA	43

Microsoft stated explicitly that MAI-Thinking-1 did not lead every benchmark and remained behind the strongest comparison systems on several long-horizon software-engineering and knowledge tasks.

Human preference evaluation

Microsoft and Surge AI conducted a blind evaluation containing 1,276 English-language tasks, approximately 30% of which were multi-turn.

Comparison	MAI-Thinking-1 wins	Ties	MAI-Thinking-1 losses
Claude Sonnet 4.6	49%	6%	45%
Claude Opus 4.6	43%	5%	52%

The result supports competitive general helpfulness under that evaluation but should not be described as universal user preference. The prompts, raters, system instructions, sampling settings, and model dates can materially affect pairwise results.

MAI-Code-1-Flash

Microsoft compared MAI-Code-1-Flash with Claude Haiku 4.5 using the GitHub Copilot production harness.

Benchmark	MAI-Code-1-Flash pass rate	Average solution tokens	Claude Haiku 4.5 pass rate	Average solution tokens
SWE-bench Verified	71.6%	10.8K	66.6%	27.3K
SWE-bench Pro	51.2%	28.0K	35.2%	29.8K
SWE-bench Multilingual	65.5%	15.3K	62.7%	17.2K
Terminal-Bench 2.0	54.8%	21.6K	41.6%	25.0K

Additional reported results include:

Benchmark	MAI-Code-1-Flash
AIME 2026	92.5%
GPQA-Diamond	84.6%
IFBench	75.0
AdvancedIF	71.4
RobustIF	61.2
Tau²-Bench telecommunications	71.7
Internal adversarial-reasoning set, adjusted accuracy	85.8

The comparison used a harness for which MAI-Code-1-Flash was directly trained and included only one principal competing checkpoint in the published efficiency table. It is evidence about the intended Copilot environment, not a complete ranking of all coding models.

MAI-Image

Microsoft reported that MAI-Image-2.5 improved its internal and Arena human-preference scores over MAI-Image-2 and MAI-Image-1. On 1 June 2026, the reported aggregate text-to-image Arena score was approximately 75 points above MAI-Image-2, with particularly large gains in text rendering and stylized imagery.

The launch article described MAI-Image-2.5 as:

• third on the text-to-image Arena leaderboard;
• second on the Arena image-editing leaderboard.

These positions were date-specific. Arena measures blinded human preferences rather than semantic correctness, provenance, or production reliability.

MAI-Voice

Selected Microsoft-reported preference results are:

Evaluation	Result
MAI-Voice-2 versus MAI-Voice-1	Voice-2 preferred in 72.1% of approximately 2,500 comparisons
MAI-Voice-2 versus human recordings across 11 languages	Voice-2 45.5%; human 44.0%; tie 10.5%, across approximately 2,222 comparisons

A preference for synthetic speech does not mean that the generated speech is more authentic, legally authorized, or suitable for impersonating the referenced speaker.

MAI-Transcribe

On the multilingual FLEURS evaluation, Microsoft reported the following average WER values for MAI-Transcribe-1.5 and selected comparison services:

Model	Average FLEURS WER
MAI-Transcribe-1.5	4.86%
ElevenLabs Scribe v2	5.53%
OpenAI Transcribe comparison	5.73%
Gemini Flash-Lite comparison	5.63%

Microsoft also reported 2.38% English WER on the Artificial Analysis transcription evaluation, placing the model among the top three systems at the date of release.

WER results can change with normalization and dataset revisions. A lower average does not mean the system is best for every accent, domain, language, speaker arrangement, or acoustic environment.

Applications and ecosystem

Microsoft Copilot

MAI models support parts of Microsoft's consumer-assistant strategy. MAI-Voice-1 powered Copilot Daily and podcast-style experiences, while MAI-1-preview was evaluated for everyday Copilot responses.

A Copilot answer should not automatically be attributed to one MAI model. Microsoft can route requests among first-party and partner models and combine them with search, memory, safety systems, product data, or specialized generation services.

GitHub Copilot and Visual Studio Code

MAI-Code-1-Flash was designed specifically for GitHub Copilot and Visual Studio Code. Its training harness included the same general tool interactions used by production coding agents.

Potential uses include:

• code completion;
• repository exploration;
• implementation of issues;
• refactoring;
• debugging;
• test generation;
• terminal operations;
• review of pull requests;
• migration across APIs or frameworks;
• code explanation.

Generated code can remain incorrect, insecure, inefficient, or incompatible with a project's licence and architecture. Automated edits require tests, review, permissions, and rollback mechanisms.

Microsoft Foundry

Microsoft Foundry is the principal enterprise distribution environment for current MAI image and speech models and the private-preview environment for MAI-Thinking-1.

Depending on model and region, Foundry provides:

• managed endpoints;
• Microsoft Entra authentication;
• API-key authentication;
• quota and billing;
• global, data-zone, or regional deployments;
• monitoring;
• content-safety controls;
• integration with Foundry agents;
• model lifecycle and retirement notices.

MAI image endpoints use dedicated generation and editing APIs. Wire compatibility and deployment options differ from Azure OpenAI chat models.

Microsoft Foundry advertises a catalogue containing thousands of first- and third-party models. Inclusion in the same catalogue does not imply shared weights, licences, safety policies, context limits, or service-level characteristics.

MAI Playground

MAI Playground is a limited-preview environment for experimental and newly released models. As of July 2026, its public interface prominently exposed MAI-Image-2.5-Flash.

A Playground model can change without the lifecycle guarantees associated with a production Foundry deployment.

PowerPoint, OneDrive, and Bing

MAI image models have been integrated into:

• PowerPoint for generated presentation visuals;
• OneDrive for localized photo editing;
• Bing Image Creator;
• Copilot visual storytelling and experimental creation tools.

The product interface may add prompt rewriting, safety filters, templates, metadata, provenance marks, or post-processing not present in a raw model endpoint.

Azure Speech and voice applications

MAI-Voice and MAI-Transcribe models are distributed through Azure Speech and Foundry tooling. Potential applications include:

• call-centre assistants;
• voice agents;
• accessibility;
• audiobook or educational narration;
• podcast creation;
• meeting transcription;
• media indexing;
• multilingual subtitles;
• searchable audio archives;
• terminology-sensitive transcription.

Microsoft announced MAI-Voice-2 integration work for products including Dynamics 365 Contact Center and development experiences. Availability can differ by region and product version.

Modular multimodal agents

Microsoft demonstrated DuoAI, a sample experience combining MAI-Voice-2, MAI-Transcribe-1.5, MAI-Image-2.5, and a language-model component.

This modular architecture illustrates a central MAI strategy: using specialized models for each modality rather than requiring one checkpoint to understand speech, reason, generate images, and synthesize audio.

A modular agent may contain:

1. speech recognition;
2. a reasoning or orchestration model;
3. retrieval or application tools;
4. image generation;
5. text-to-speech;
6. policy and identity controls.

System quality depends on the interactions among all components, not only on the benchmark performance of one model.

Frontier Tuning

Microsoft announced Frontier Tuning as a system for adapting advanced models to customer data, workflows, tools, and private environments.

Frontier Tuning should not be interpreted as a general public release of MAI base weights. It is a managed customization programme whose available methods, model access, data controls, and distribution rights depend on the customer agreement and supported deployment.

Licensing and availability

MAI models do not use one family-wide licence.

Model group	Distribution and governing terms
MAI-DS-R1	Downloadable weights under the MIT License
MAI-1-preview	Proprietary evaluation model; no released weights
MAI-Thinking-1	Proprietary; Microsoft Foundry private-preview terms
MAI-Code-1-Flash	Product and service terms for GitHub Copilot and Visual Studio Code
MAI image models	Microsoft Foundry and product-specific preview or service terms
MAI-Voice and MAI-Transcribe	Azure Speech, Foundry, and applicable product terms
MAI-Voice-2-Flash	No public model licence or standalone endpoint as of 10 July 2026

For most current MAI models, API access does not confer permission to copy the weights or reproduce the training system. Conversely, MAI-DS-R1's open-weight licence does not grant rights to confidential input data, third-party trademarks, personal likenesses, or every possible generated output.

Limitations and open problems

Uneven technical disclosure

MAI-Thinking-1 and MAI-Code-1-Flash have relatively detailed architecture and data disclosures. Most image and audio models disclose only broad model type, parameter range or count, inputs, outputs, supported languages, and safety information.

Undisclosed details include:

• MAI-1-preview's exact architecture;
• Voice and Transcribe parameter counts;
• voice-token or acoustic-decoder design;
• Image-1 architecture;
• MAI-Vision-1 architecture and release status;
• complete training corpora;
• complete reward functions;
• full data-deduplication and contamination controls;
• production system prompts and routing policies.

This limits independent reproduction and makes comparisons based solely on model names unreliable.

Benchmark comparability

Most MAI results are published by Microsoft. Comparisons can differ in:

• checkpoint date;
• context and output budget;
• sampling temperature;
• number of attempts;
• tool access;
• product harness;
• timeout and retry policy;
• judge model;
• text normalization;
• human-rater instructions;
• hardware and quantization.

The GitHub Copilot harness, for example, is highly relevant to MAI-Code-1-Flash's intended use but is not a neutral environment in which every competing model has necessarily received equal optimization.

Active parameters and memory requirements

A model with 34.7 billion active parameters is not stored like a dense 34.7-billion-parameter model. MAI-Thinking-1 has approximately 962 billion total parameters, all of which must be stored, distributed, or made available through expert sharding.

Ignoring metadata and runtime overhead, raw weight storage is approximately:

$\text{storage}\approx N_{\mathrm{p}\mathrm{a}\mathrm{r}\mathrm{a}\mathrm{m}\mathrm{e}\mathrm{t}\mathrm{e}\mathrm{r}\mathrm{s}}\times \frac{\text{bits per parameter}}{8}.$

At 16 bits, 962 billion parameters would require approximately 1.9 TB of raw weight storage. Quantization can reduce storage but can affect quality and requires additional scales, buffers, communication, and runtime memory.

Long-context reliability

MAI-Thinking-1 and MAI-Code-1-Flash support contexts up to 256K tokens. This does not guarantee:

• uniform recall at every position;
• correct handling of contradictory instructions;
• immunity to prompt injection in source files;
• preservation of chronology;
• exact numerical memory;
• successful reasoning across an entire large repository.

Local attention also means that information often passes through several layers before interacting globally. Periodic global layers mitigate this limitation but do not eliminate long-context retrieval errors.

Hallucination and factuality

MAI text models can produce:

• unsupported factual claims;
• fabricated citations;
• incorrect calculations;
• false statements about tool execution;
• insecure code;
• inconsistent reasoning.

Extended reasoning does not guarantee correctness. A long explanation can rationalize an incorrect premise with greater confidence.

Agentic error accumulation

Coding and enterprise agents can:

• select an incorrect tool;
• send malformed arguments;
• modify the wrong file;
• execute a destructive command;
• expose a credential;
• misunderstand a test failure;
• repeat an unsuccessful action;
• claim that work is complete without verification;
• follow malicious instructions embedded in a repository or document.

A production agent requires least-privilege permissions, isolated environments, network restrictions, audit logs, limits on irreversible actions, and human approval where appropriate.

Image-generation limitations

MAI image models can produce:

• anatomically inconsistent people;
• incorrect text;
• impossible geometry;
• misleading product details;
• inaccurate public figures;
• unintended trademarks;
• stereotypical depictions;
• visual artifacts;
• plausible but false documentary scenes.

Preserving facial identity in an editing benchmark does not establish legal authorization to edit or synthesize a person's image.

Speech-synthesis risks

Prompted voice reproduction can enable fraud, impersonation, harassment, or deceptive media. Consent gates reduce but do not eliminate misuse because reference recordings can be obtained outside the official enrolment process or generated by another system.

Synthetic speech may also alter accent, pronunciation, emotional tone, or semantic emphasis in ways not intended by the speaker.

Speech-recognition limitations

Transcription quality can degrade because of:

• background noise;
• overlapping speech;
• code-switching;
• uncommon names;
• specialized terminology;
• low-quality microphones;
• regional accents;
• music;
• reverberation;
• very long files.

Terminology biasing improves selected words but can cause incorrect insertion when supplied keywords resemble unrelated speech.

MAI-Transcribe-1.5 did not provide native speaker diarization at launch. Applications requiring attribution must use an additional diarization system, which can introduce its own errors.

Product and endpoint lifecycle

Several MAI models are preview services. Prices, regions, names, APIs, or capabilities can change. MAI-Image-2-Efficient already had a scheduled retirement only months after introduction.

Production systems should record:

• exact model identifier and version;
• deployment region;
• API version;
• prompt;
• safety configuration;
• tool versions;
• date;
• output;
• applicable retirement notice.

Reproducibility

The MAI-Thinking-1 technical report discloses architecture and major training stages, but reproducing a 962-billion-parameter model trained on more than 33 trillion tokens requires infrastructure beyond the reach of most academic groups.

The raw data, executable RL environments, reward models, internal evaluation sets, and complete distributed stack have not been released. Independent researchers can therefore study the hosted model's behaviour but cannot recreate the original training run from the publication alone.

Safety, ethics, and governance

Microsoft Responsible AI principles

Microsoft's public Responsible AI framework identifies six principal areas:

• fairness;
• reliability and safety;
• privacy and security;
• inclusiveness;
• transparency;
• accountability.

These principles guide internal development and product governance but are not an independent certification of every MAI deployment.

Humanist-superintelligence framework

Microsoft AI's humanist-superintelligence position emphasizes that powerful systems should remain tools under meaningful human direction.

In practical deployments this requires more than model alignment. It can include:

• scoped permissions;
• human review;
• reversible actions;
• provenance;
• monitoring;
• incident response;
• clear disclosure that content is generated;
• meaningful opt-out and consent mechanisms.

MAI-Thinking-1 safety work

MAI-Thinking-1's post-training jointly optimized helpfulness and policy compliance. Microsoft reports continuous red-team testing by internal teams, the Microsoft AI Red Team, and external evaluators.

The development programme expanded approximately 2,500 seed adversarial prompts into roughly 9,500 jailbreak variants. Such testing improves coverage but cannot exhaust the space of possible attacks.

The model may still be vulnerable to:

• indirect prompt injection;
• multi-turn jailbreaks;
• obfuscated harmful requests;
• tool-mediated attacks;
• malicious code or documents;
• unsafe fine-tuning;
• novel domains not represented in testing.

Coding safety

MAI-Code-1-Flash can generate commands, configuration, dependencies, and executable code. Applications should use:

• sandboxed terminals;
• secret isolation;
• dependency scanning;
• static and dynamic analysis;
• branch protections;
• code review;
• test suites;
• deployment approval gates.

A model's pass rate on SWE-bench does not establish security, maintainability, or compatibility with a specific production system.

Image safety and provenance

MAI-Image-2.5 uses layered prompt and output filters intended to block harmful or policy-violating material.

Image-generation deployments should also consider:

• disclosure of synthetic content;
• identity and likeness rights;
• political and news misinformation;
• non-consensual intimate imagery;
• depiction of minors;
• trademarks and copyrighted characters;
• training-data provenance;
• accessibility metadata;
• auditability of edits.

A visual safety filter can produce false positives and false negatives.

Voice consent and authentication

Microsoft's personal-voice workflow requires an enrolled consent recording before a custom voice is activated. This is an important control, but applications can still require:

• contractual authorization;
• account protection;
• liveness or identity verification;
• watermarking or provenance metadata;
• detection of suspicious high-volume generation;
• restrictions on public-figure impersonation;
• procedures for revoking a voice.

Synthetic voice should not be treated as proof that the referenced person made a statement.

Transcription privacy

Audio can contain biometric information, personal conversations, health data, confidential business material, or information about people who did not consent to recording.

Deployers must define:

• lawful recording basis;
• retention period;
• encryption;
• access control;
• storage region;
• whether audio is logged;
• whether transcripts are used for training;
• deletion and incident-response procedures.

Training-data transparency

Microsoft publishes technical reports, model cards, and public data summaries for several current MAI models. These describe broad source categories and data sizes but do not release document-level provenance or the complete corpus.

Consequently, unresolved questions remain concerning:

• copyrighted material;
• personal data;
• representational bias;
• language distribution;
• benchmark contamination;
• removal of machine-generated web text;
• rights attached to image, voice, and audio data.

Research directions

Published MAI work indicates several continuing directions.

Scaling sparse reasoning models

MAI-Thinking-1 demonstrates Microsoft's preference for a high-capacity expert pool with a medium active-parameter budget. Future research can explore:

• expert specialization;
• routing stability;
• load balancing;
• smaller latent dimensions;
• expert communication;
• low-precision inference;
• smaller active footprints;
• improved performance per stored parameter.

Reinforcement-learning infrastructure

The hill-climbing-machine concept depends on rapid iteration among environments, rewards, evaluations, and training. Research problems include:

• reducing asynchronous policy lag;
• preventing reward hacking;
• constructing realistic executable tasks;
• improving credit assignment across long trajectories;
• preserving capabilities when specialist models are consolidated;
• measuring generalization outside the training harness.

Efficient coding agents

MAI-Code-1-Flash emphasizes success per generated token rather than benchmark accuracy alone. Future work may optimize jointly for:

• task completion;
• latency;
• token use;
• tool calls;
• changed-line count;
• test coverage;
• security;
• maintainability;
• human-review burden.

Multimodal model orchestration

Microsoft's MAI ecosystem uses specialized models rather than one universal omni-modal checkpoint. Open questions include:

• choosing the correct model for each step;
• sharing state between speech, reasoning, image, and tool components;
• preserving identity and intent across modalities;
• handling partial failures;
• coordinating safety policies;
• reducing cumulative latency.

Frontier Tuning and customization

Customer-specific tuning can improve enterprise utility but can also reduce general safety or cause overfitting. Research is needed on:

• private-data governance;
• secure adapter training;
• evaluation under distribution shift;
• retention of base capabilities;
• rollback;
• auditing;
• prevention of cross-customer leakage.

Speech and voice agents

Future speech work is likely to target:

• lower latency;
• streaming generation;
• more languages and accents;
• speaker diarization;
• stronger code-switching;
• controllable emotion;
• reliable interruption handling;
• consent and provenance mechanisms;
• robustness in noisy environments.

Independent evaluation

Greater independent reproducibility would benefit from:

• fixed dated endpoints;
• released prompts and harnesses;
• public benchmark trajectories;
• exact sampling settings;
• evaluator disclosure;
• equalized tool access;
• external safety studies;
• stable model snapshots;
• clearer separation between model and product-layer performance.

Microsoft had not announced a binding release schedule or specification for a successor named MAI-Thinking-2, MAI-2, or another general-purpose MAI generation as of 10 July 2026.

External links

• Microsoft AI model catalogue
• MAI-Thinking-1 technical report
• MAI-Thinking-1 model page
• Microsoft Foundry
• MAI Playground
• MAI-DS-R1 on Hugging Face
• MAI Voice documentation
• MAI image-model deployment documentation

See also

• Phi (language model)
• Large language model

Literature

• The Microsoft AI Team. MAI-Thinking-1: Building a Hill-Climbing Machine. Microsoft AI, 2026.
• Vaswani, A. et al. Attention Is All You Need. Advances in Neural Information Processing Systems, 2017.
• Shazeer, N. et al. Outrageously Large Neural Networks: The Sparsely-Gated Mixture-of-Experts Layer. arXiv:1701.06538, 2017.
• Ainslie, J. et al. GQA: Training Generalized Multi-Query Transformer Models from Multi-Head Checkpoints. arXiv:2305.13245, 2023.
• Zhang, B.; Sennrich, R. Root Mean Square Layer Normalization. arXiv:1910.07467, 2019.
• Lipman, Y. et al. Flow Matching for Generative Modeling. International Conference on Learning Representations, 2023.
• Jimenez, C. E. et al. SWE-bench: Can Language Models Resolve Real-World GitHub Issues?. International Conference on Learning Representations, 2024.
• Conneau, A. et al. FLEURS: Few-shot Learning Evaluation of Universal Representations of Speech. IEEE Spoken Language Technology Workshop, 2022.
• Rafailov, R. et al. Direct Preference Optimization: Your Language Model Is Secretly a Reward Model. Advances in Neural Information Processing Systems, 2023.