Kimi-K2.7-Code retires from Microsoft Foundry on 2026-10-03
Foundry only · the replacement column is empty
Microsoft's Foundry retirement schedule dates the Kimi-K2.7-Code row (version 2026-06-12, lifecycle Preview) for 2026-10-03, with "—" in the suggested-replacement column. There is no silent upgrade: after that date a request hitting the entry gets 410 Gone, and the replacement is yours to pick. This page covers the Foundry face only - Moonshot's own API docs (captured 2026-09-20) still list the id.
Updated 2026-09-20
Four key points
Retirement date on the Foundry table
The row reads: model Kimi-K2.7-Code, version 2026-06-12, Preview, retirement date 2026-10-03, replacement "—". The document carries ms.date 2026-09-02 and the page updated_at 2026-09-14; our check date is 2026-09-20.
Suggested-replacement column
The table states that it publishes lifecycle stage, retirement date and suggested replacement - and the suggested-replacement cell for this row is empty. Nothing in the source supports "Microsoft will move you up to K3": you choose the target and run the regression.
What the call returns after the date
For a Preview entry with no replacement, the official sentence contains two things: notice before retirement, and 410 Gone from inference afterwards. We do not quote a notice period here - our two research passes disagreed on the number, so it stays out until re-checked against the live page.
To the retirement date (our arithmetic)
From our check date 2026-09-20 to 2026-10-03 is 13 days. That count is ours: Microsoft publishes no countdown, and the row can move, so finish the change before the date.
What this is
The row governs one model entry inside Microsoft Foundry: Kimi-K2.7-Code, version 2026-06-12, lifecycle Preview, retirement 2026-10-03. It does not reach Moonshot's own endpoint or any other cloud - the same family has its own lifecycle per access point (K3 on Bedrock, for instance, is documented as "no sooner than" plus at least 45 days of EOL notice, a different clause that does not transfer here). The reader's job is one thing: before 2026-10-03, no live request should still land on that Foundry entry.
What happened
Re-checked 2026-09-20: on the Foundry retirement schedule (ms.date 2026-09-02, updated_at 2026-09-14) the row for Kimi-K2.7-Code is still Preview + 2026-10-03 + empty replacement. On the same day Moonshot's Chat Completions reference still carries kimi-k2.7-code and kimi-k2.7-code-highspeed as model values and states the two are the same model.
Timeline
2026-06-12: the version field of the Kimi-K2.7-Code row, with lifecycle marked Preview. The table publishes no availability date, so this page does not read that field as a launch day.
2026-09-20 re-check: document ms.date 2026-09-02, page updated_at 2026-09-14 - the row is unchanged; and the id is still in Moonshot's own docs the same day.
2026-10-03: the retirement date on the Foundry side. With no replacement listed, requests still reaching the entry afterwards return 410 Gone. Rows can move, so land the change before the date rather than on it.
Confirmed vs caution
Officially confirmed
Only four things match word for word: the row on the Foundry schedule (version 2026-06-12, Preview, retirement 2026-10-03, replacement "—"); the table's own statement that it publishes lifecycle stage, retirement date and suggested replacement; the clause that inference returns 410 Gone after a Preview entry without replacement retires; and Moonshot's docs describing kimi-k2.7-code and its high-speed variant as one and the same model.
⚠️ Caution
Not facts, and not written here: "K2.7-Code is shut down everywhere" (the table governs Foundry Models only); "Microsoft upgrades you to K3 automatically" (the replacement column is empty); "the same id also retires on Bedrock or Vertex on 2026-10-03" (no such row was found); applying the at-least-45-day K3 EOL clause from Bedrock to this Preview entry; or quoting any Foundry notice period.
Same vs differs
Same
Both routes call the same Moonshot coding model; in both, a model / deployment value in the request decides which entry you land on; either way you re-run one prompt set after the change, because swapping a string is not verification.
Differs
The Foundry row has a hard date: retirement 2026-10-03, then 410 Gone, replacement column empty. Moonshot's own endpoint appears on no retirement table we checked (it is still a listed model value in the docs captured 2026-09-20), but base_url, auth, rate limits, billing and logging all get configured again on your side.
What to do
Four steps. 1) Grep every repo and config store for Kimi-K2.7-Code and for the version string 2026-06-12 - application config, IaC, gateway model maps, eval sets, alert rules; it is never in one place. 2) Choose the target: the official replacement column is empty, so it is either "same model, other endpoint" (Moonshot's docs still list the id) or "other model", and the second one is a model change, not a string edit. 3) Canary both paths on one fixed prompt set and compare completion plus reasoning behaviour. 4) Verify: first work out which field selects the entry for you (model id or deployment name), then put a counter on 410 Gone and watch it stay at zero - any hit is a path you did not switch.
On QCode
Let us draw the line first: QCode's /models catalog does not carry kimi-k2.7-code (checked 2026-09-20), so this page offers no "move to us instead" shortcut. The only Kimi in the public /models list we captured is kimi-k3 (850 priced calls over 30 days); kimi-k2.6 shows 21 in the priced ledger but is not in that public list - a different choice inside the family that needs its own regression. Prices and limits come from /pricing and the live catalog.
FAQ
Is this Moonshot retiring K2.7-Code?
No. The retirement schedule is Microsoft's list of entries on its own cloud, and the row it dates is Kimi-K2.7-Code. Moonshot's platform docs on 2026-09-20 still carry kimi-k2.7-code as a Chat Completions model value.
Did Microsoft name a replacement?
The suggested-replacement cell for that row is "—", so nothing was named. For a Preview entry without a replacement the official wording is 410 Gone from inference after retirement - no silent switch, and no automatic move to K3.
Is changing the model string enough?
Start from how your request selects the entry - a model id or a deployment name - and change that line. Then grep Kimi-K2.7-Code and 2026-06-12 out of application config, IaC and gateway maps, and watch traffic: nothing should still land on the old entry, and a single 410 Gone means a path you left behind.
Is the same K2.7-Code id retired on Bedrock or Vertex on 2026-10-03?
We found no such row, so this page says nothing about other clouds. Do not merge calendars: the K3 entry on Bedrock is documented as EOL undated with at least 45 days of notice, which is another platform's clause.
Can I keep using kimi-k2.7-code through QCode?
No. QCode's /models list does not carry it (checked 2026-09-19) and this page promises nothing. The public /models list carries kimi-k3 (850 priced calls over 30 days); kimi-k2.6 appears in the priced ledger with 21 - and moving to either is a model change, not a rename.
How much time is left?
From our check date 2026-09-20 to 2026-10-03 is 13 days - our arithmetic, since no countdown is published. Watch the live page instead: the document we read stops at ms.date 2026-09-02.
Sources
Microsoft Foundry, "Model retirement schedule", https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule (document ms.date 2026-09-02, page updated_at 2026-09-14, re-fetched directly on 2026-09-21) and "Foundry Models lifecycle and support policy", https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirements (ms.date 2026-07-24; the "Retired = Removed from service. All inference requests return 410 Gone." definition is from this policy page, not from the Kimi row). Moonshot, "Chat Completions API", https://platform.kimi.com/docs/api/chat, captured 2026-09-20. The Bedrock clause for K3 is at https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-moonshot-ai-kimi-k3.html (captured 2026-09-20; our /kimi-k3-amazon-bedrock-guide page cites the same model card). Catalog listing and 30-day priced usage are our own checks.
Move the config before the 410 Gone
Retirement 2026-10-03 covers that single Microsoft Foundry entry; QCode does not list it (checked 2026-09-20), so this page promises no fix by switching here.
Related
Kimi K3 on Amazon Bedrock
The same family's lifecycle and price terms on another cloud - a different calendar from this one.
Kimi K2.6: The Complete Guide
Another Kimi guide, covering sale status and how 30-day real usage was verified.
Kimi K3 Status Tracker
What is confirmed about K3 and what is still rumour, before you call it a replacement.
This page restates public Microsoft and Moonshot documentation and is affiliated with neither. Every external date follows the version checked on 2026-09-20 and can move. QCode does not provide Microsoft Foundry and does not quote on its behalf; the 13-day figure is our own arithmetic.