Microsoft Foundry / Azure OpenAI · model
MAI-Transcribe-1 deprecation: shutdown date & replacement
- Provider
- Microsoft Foundry / Azure OpenAI
- Name
- MAI-Transcribe-1 (2026-01-23)
- Type
- model
- Announced
- —
- Shutdown
- Replacement
MAI-Transcribe-1.5- Source
- Official Microsoft Foundry / Azure OpenAI notice
Azure lifecycle stage: Preview. Version 2026-01-23.
How to migrate off MAI-Transcribe-1
- Find every place that references it:
grep -rn --exclude-dir={node_modules,.git,dist} "MAI-Transcribe-1" . - Replace the model ID:
- model: "MAI-Transcribe-1" + model: "MAI-Transcribe-1.5" - Re-run your evals or a sample of real prompts — output style, token usage and pricing can change between models.
- Check config outside code too: environment variables, feature flags, prompt-management tools, and fine-tuned model references.
- Deploy before September 15, 2026, and add the CI scanner so it cannot come back.
Questions
Is MAI-Transcribe-1 deprecated?
Yes. Microsoft Foundry / Azure OpenAI has deprecated MAI-Transcribe-1. It was shut down on September 15, 2026.
When does MAI-Transcribe-1 shut down?
September 15, 2026, according to Microsoft Foundry / Azure OpenAI's official deprecation notice.
What should I use instead of MAI-Transcribe-1?
Microsoft Foundry / Azure OpenAI recommends MAI-Transcribe-1.5. Switch the model ID and re-test your prompts, since outputs, pricing and limits can differ.
What happens to requests to MAI-Transcribe-1 after the shutdown?
Requests using the retired model ID fail with an error, so any code still calling it breaks. Update and deploy before the shutdown date.