Microsoft Foundry / Azure OpenAI · model
grok-4-fast-non-reasoning deprecation: shutdown date & replacement
Shut down May 1, 2026
All providers: Grok 4 Fast Non Reasoning deprecation status →
- Provider
- Microsoft Foundry / Azure OpenAI
- Type
- model
- Announced
- —
- Shutdown
- Replacement
grok-4-1-fast-non-reasoning- Source
- Official Microsoft Foundry / Azure OpenAI notice
Azure lifecycle stage: Retired. Version 1.
How to migrate off grok-4-fast-non-reasoning
- Find every place that references it:
grep -rn --exclude-dir={node_modules,.git,dist} "grok-4-fast-non-reasoning" . - Replace the model ID:
- model: "grok-4-fast-non-reasoning" + model: "grok-4-1-fast-non-reasoning" - 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 May 1, 2026, and add the CI scanner so it cannot come back.
Same model on other platforms
- xAI — May 15, 2026
Also shutting down on May 1, 2026 (Microsoft Foundry / Azure OpenAI)
Questions
Is grok-4-fast-non-reasoning deprecated?
Yes. Microsoft Foundry / Azure OpenAI has deprecated grok-4-fast-non-reasoning. It was shut down on May 1, 2026.
When does grok-4-fast-non-reasoning shut down?
May 1, 2026, according to Microsoft Foundry / Azure OpenAI's official deprecation notice.
What should I use instead of grok-4-fast-non-reasoning?
Microsoft Foundry / Azure OpenAI recommends grok-4-1-fast-non-reasoning. Switch the model ID and re-test your prompts, since outputs, pricing and limits can differ.
What happens to requests to grok-4-fast-non-reasoning 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.