Reference Source

Kimi-K2.7-Code — Preview — shutdown 2026-10-03

For Kimi-K2.7-Code, provider is Microsoft Azure / Foundry; lifecycle status is Preview; shutdown / retirement date is 2026-10-03; platform / deployment scope is Azure / Microsoft Foundry, recorded from its source on 2026-08-28; source re-checked 2026-09-16.

Provider
Microsoft Azure / Foundry our reading
Model ID / API name
Kimi-K2.7-Code verified
Human-readable model name
Kimi-K2.7-Code verified
Lifecycle status
Preview verified
Shutdown / retirement date
2026-10-03 verified
Platform / deployment scope
Azure / Microsoft Foundry our reading
Recommended replacement
Kimi K3 per github.blog
Sourceraw.githubusercontent.com
Verified
Review by
DatasetAI model deprecation and retirement dates by provider

Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.

What the source says

| Kimi-K2.7-Code | 2026-06-12 | Preview | 2026-10-03 | — |

— raw.githubusercontent.com, retrieved 2026-08-28

Sources disagree

More than one authority states this, and they do not state the same thing. Both are reproduced with the source each came from — deciding between them is yours, not ours.

Provider

raw.githubusercontent.com says provider is Microsoft Azure / Foundry, as of 2026-08-28.

| Kimi-K2.7-Code | 2026-06-12 | Preview | 2026-10-03 | — |

https://raw.githubusercontent.com/MicrosoftDocs/azure-ai-docs/main/articles/foundry/openai/includes/concepts-model-retirement-schedule-content.md

github.blog says provider is GitHub Copilot, as of 2026-09-09.

Kimi K2.7 Code | 2026-10-02 | Kimi K3 |

https://github.blog/changelog/2026-09-03-upcoming-deprecation-of-selected-github-copilot-models

docs.together.ai says provider is Together AI, as of 2026-09-15.

| 2026-08-27 | `moonshotai/Kimi-K2.7-Code` | Yes |

https://docs.together.ai/docs/deprecations.md

Lifecycle status

raw.githubusercontent.com says lifecycle status is Preview, as of 2026-08-28.

| Kimi-K2.7-Code | 2026-06-12 | Preview | 2026-10-03 | — |

https://raw.githubusercontent.com/MicrosoftDocs/azure-ai-docs/main/articles/foundry/openai/includes/concepts-model-retirement-schedule-content.md

docs.together.ai says lifecycle status is Removed, as of 2026-09-15.

| 2026-08-27 | `moonshotai/Kimi-K2.7-Code` | Yes |

https://docs.together.ai/docs/deprecations.md

Shutdown / retirement date

raw.githubusercontent.com says shutdown / retirement date is 2026-10-03, as of 2026-08-28.

| Kimi-K2.7-Code | 2026-06-12 | Preview | 2026-10-03 | — |

https://raw.githubusercontent.com/MicrosoftDocs/azure-ai-docs/main/articles/foundry/openai/includes/concepts-model-retirement-schedule-content.md

github.blog says shutdown / retirement date is 2026-10-02, as of 2026-09-09.

Kimi K2.7 Code | 2026-10-02 | Kimi K3 |

https://github.blog/changelog/2026-09-03-upcoming-deprecation-of-selected-github-copilot-models

docs.together.ai says shutdown / retirement date is 2026-08-27, as of 2026-09-15.

| 2026-08-27 | `moonshotai/Kimi-K2.7-Code` | Yes |

https://docs.together.ai/docs/deprecations.md

Platform / deployment scope

raw.githubusercontent.com says platform / deployment scope is Azure / Microsoft Foundry, as of 2026-08-28.

| Kimi-K2.7-Code | 2026-06-12 | Preview | 2026-10-03 | — |

https://raw.githubusercontent.com/MicrosoftDocs/azure-ai-docs/main/articles/foundry/openai/includes/concepts-model-retirement-schedule-content.md

github.blog says platform / deployment scope is GitHub Copilot, as of 2026-09-09.

Kimi K2.7 Code | 2026-10-02 | Kimi K3 |

https://github.blog/changelog/2026-09-03-upcoming-deprecation-of-selected-github-copilot-models

docs.together.ai says platform / deployment scope is Together AI serverless inference, as of 2026-09-15.

| 2026-08-27 | `moonshotai/Kimi-K2.7-Code` | Yes |

https://docs.together.ai/docs/deprecations.md

Sources

Last verified against source: . Due for re-check by . This page as Markdown · OKF bundle · full dataset as JSON.

This one changes, and we watch it.AI model deprecation and retirement dates by provider is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.