Azure AI Foundry
grok-4-1-fast-non-reasoning model retirement
Stops workingSubscribe to Azure AI FoundryShare
Calls to the model grok-4-1-fast-non-reasoning on Azure AI Foundry stop working on May 19, 2027.
In Azure AI Foundry's words
Model: grok-4-1-fast-non-reasoning; Version: 1; Lifecycle: GA; Retirement date: 2027-05-19; Replacement: —
Facts
- API
- Azure AI Foundry
*.services.ai.azure.com - Model
grok-4-1-fast-non-reasoning- Released
- June 27, 2025 (models.dev)
- Kind
- Model retirement
- Takes effect
- May 19, 2027
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Azure AI Foundry's own pages
Questions
When does grok-4-1-fast-non-reasoning shut down?
Calls to the model grok-4-1-fast-non-reasoning on Azure AI Foundry stop working on May 19, 2027.
What happens to calls after May 19, 2027?
They fail from that day.
When was grok-4-1-fast-non-reasoning released?
grok-4-1-fast-non-reasoning was released on June 27, 2025, according to models.dev.
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.
grok-4-1-fast-non-reasoning on other APIs 1
-
xAI
grok-4-1-fast-non-reasoningModel retirement Redirected
More from Azure AI Foundry 10
-
gpt-4.1Model retirement Stops workingin 159 days -
gpt-4o-transcribe-diarizeModel retirement Stops workingin 160 days -
kimi-k2.6Model retirement Stops workingin 161 days -
kimi-k2.7-codeModel retirement Stops workingin 161 days -
gpt-5.1-codexModel retirement Stops workingin 190 days -
gpt-5.1-codex-miniModel retirement Stops workingin 190 days -
gpt-5.1-codex-maxModel retirement Stops workingin 193 days -
grok-4-1-fast-reasoningModel retirement Stops workingin 194 days -
embed-v-4-0Model retirement Stops workingin 207 days -
gpt-5.2Model retirement Stops workingin 214 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before May 19, 2027.