What Are the New MAI Models?
MAI‑Transcribe‑1 (Speech‑to‑Text)
MAI‑Transcribe‑1 is Microsoft’s first‑generation in‑house speech recognition model. It supports 25 languages and is optimized for real‑world, noisy enterprise audio, such as meetings and call centers.
Key highlights
- Enterprise‑grade transcription accuracy
- Designed for multilingual and accented speech
- Lower GPU cost compared to prior Azure speech offerings
MAI‑Voice‑1 (Text‑to‑Speech)
MAI‑Voice‑1 is a high‑fidelity voice generation model capable of producing natural, expressive speech while preserving speaker identity over long‑form audio.
Key highlights
- Generates up to 60 seconds of audio in ~1 second
- Supports custom voice creation
- Optimized for voice agents and conversational systems
MAI‑Image‑2 (Text‑to‑Image)
MAI‑Image‑2 is Microsoft’s highest‑capability text‑to‑image model, already ranking among top image models used in production Copilot experiences.
Key highlights
- High‑quality photorealistic image generation
- Accurate in‑image text rendering
- Production‑ready latency and cost profile
Why This Matters for Azure Developers
For Azure developers, this launch changes three things fundamentally:
- First‑party AI stack
Developers can now build speech, voice, and image workloads without relying on external AI providers. - Enterprise‑ready by default
These models inherit Azure RBAC, Managed Identity, compliance, and governance through Microsoft Foundry. - Agent‑first design
MAI models are designed to be embedded inside AI agents, not just called as single APIs
Below is a common enterprise architecture using MAI models.
Sample Code Calling MAI‑Transcribe‑1:
What Changed with MAI Models: Before vs After (Developer Perspective)
Microsoft’s MAI models are not just new endpoints — they represent a fundamental shift in how Azure developers build multimodal and agent‑based AI solutions.
High‑Level Comparison
| Aspect | Before MAI (Azure & External Models) | After MAI (MAI‑Transcribe, Voice, Image) |
|---|---|---|
| Model Ownership | Heavy dependency on third‑party models (OpenAI, external TTS/STT providers) | First‑party Microsoft‑built models, operated and optimized by Microsoft |
| Enterprise Integration | AI models integrated into Azure | AI models native to Microsoft Foundry |
| Governance & Compliance | Mixed controls depending on model provider | Unified Azure RBAC, Entra ID, Purview, Managed Identity |
| Agent Readiness | Primarily single‑request / single‑response APIs | Designed for agent‑oriented, long‑running workflows |
| Cost Predictability | Token‑based or mixed pricing models | Enterprise‑optimized price‑to‑performance models |
| Operational Consistency | Different SDKs, APIs, quotas | Single Foundry tooling and SDK surface |
Microsoft