Azure AI Foundry
mai-image-2e model retirement
Stopped workingSubscribe to Azure AI FoundryShare
On August 15, 2026, model mai-image-2e was retired. Calls targeting model mai-image-2e fail since that date. The model lifecycle reached retired status under version 2026-04-09.
What to use instead of mai-image-2e
The original replacement MAI-Image-2.5-Flash, also referred to as mai-image-2.5-flash, stopped working on October 1, 2026. No replacement that holds is named yet.
In Azure AI Foundry's words
Model: MAI-Image-2e; Version: 2026-04-09; Lifecycle: Retired; Retirement date: 2026-08-15; Replacement: MAI-Image-2.5-Flash
Facts
- API
- Azure AI Foundry
*.services.ai.azure.com - Model
mai-image-2e- Kind
- Model retirement
- Takes effect
- August 15, 2026
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Azure AI Foundry's own pages
Questions
When does mai-image-2e shut down?
Calls to the model mai-image-2e on Azure AI Foundry stopped working on August 15, 2026.
What happens to calls after August 15, 2026?
They have failed since August 15, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Azure AI Foundry 10
-
mistral-document-ai-2505Model retirement Stopped working -
stable-diffusion-3.5-largeModel retirement Stopped working -
stable-image-coreModel retirement Stopped working -
stable-image-ultraModel retirement Stopped working -
claude-opus-4-1Model retirement Stopped working -
deepseek-r1Model retirement Stopped working -
mai-image-2Model retirement Stopped working -
model-routerModel retirement Stopped working -
timegen-1Model retirement Stopped working -
tsuzumi-7bModel retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.