Azure AI Foundry
phi-4 model retirement
Stops workingSubscribe to Azure AI FoundryShare
On January 17, 2027, model phi-4 will be retired. Calls targeting this model will fail after that day. This retirement affects all requests sent to model phi-4 on Azure AI Foundry.
What to use instead of phi-4
Move to microsoft--phi-4 (Foundry Managed Compute), as recommended by Microsoft.
In Azure AI Foundry's words
Model: Phi-4; Version: —; Lifecycle: GA; Retirement date: 2027-01-17; Replacement: microsoft--phi-4 (Foundry Managed Compute)
Facts
- API
- Azure AI Foundry
*.services.ai.azure.com - Model
phi-4- Released
- December 11, 2024 (models.dev)
- Kind
- Model retirement
- Takes effect
- January 17, 2027
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Azure AI Foundry's own pages
Questions
When does phi-4 shut down?
Calls to the model phi-4 on Azure AI Foundry stop working on January 17, 2027.
What happens to calls after January 17, 2027?
They fail from that day.
When was phi-4 released?
phi-4 was released on December 11, 2024, 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.
More from Azure AI Foundry 10
-
gpt-4oModel retirement Stops workingin 69 days -
claude-opus-5-5-fastModel retirement Stops workingin 70 days -
phi-4-mini-instructModel retirement Stops workingin 72 days -
phi-4-mini-reasoningModel retirement Stops workingin 72 days -
phi-4-multimodal-instructModel retirement Stops workingin 72 days -
phi-4-reasoningModel retirement Stops workingin 72 days -
flux.2-flexModel retirement Stops workingin 75 days -
flux.2-proModel retirement Stops workingin 75 days -
gpt-realtime-2Model retirement Stops workingin 75 days -
kimi-k2.5Model retirement Stops workingin 81 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 January 17, 2027.