RETIRING IN 78 DAYS

Sunset scheduled for 2027-01-17, reported by a third-party catalog. The identifier still resolves today. Sources disagree on: input_price_per_mtok, max_output_tokens, output_price_per_mtok.

state=dying sunset=2027-01-17 days_remaining=78 severity=high sources=litellm,openrouter evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=yes divergent_fields=input_price_per_mtok,max_output_tokens,output_price_per_mtok checked=2026-10-31 05:09Z

microsoft/phi-4

Q: Is phi-4 deprecated?

Not yet, but retirement is scheduled. Sunset scheduled for 2027-01-17, reported by a third-party catalog. The identifier still resolves today.

Vendor: microsoft. Tracked by 2 of 5 sources.

What each source reports

**endpoint** = the provider's own machine-readable API, the strongest evidence. **provider docs** = the provider's own documentation, read by a model — first-party content, inferred reading. Unlabelled rows are third-party catalogs. Where sources disagree both values are shown rather than silently reconciled.
Source	ID	Context	Max out	In $/Mtok	Out $/Mtok	Sunset
litellm	azure_ai/Phi-4	16,384	16,384	$0.125	$0.5	2027-01-17
openrouter	microsoft/phi-4	16,384	14,745	$0.07	$0.14	—

Change history

Severity	Change	What	Detected
high	deprecated	azure_ai/Phi-4: deprecation announced for 2027-01-17 — in 86 days	2026-10-23
high	deprecated	azure_ai/Phi-4: retires 2027-01-17 (in 86 days)	2026-10-23
medium	removed	[one catalog only — litellm, openrouter still list it] openrouter/microsoft/phi-4 is no longer listed by this source — calls to it are expected to fail	2026-10-10
low	added	new model openrouter/microsoft/phi-4 (16,384 ctx)	2026-09-18
high	modified	microsoft/phi-4: max_output_tokens cut 16,384 to 14,745	2026-08-25