GitHub Copilot model deprecation: required policy updates and workflow impact

GitHub will retire several Copilot models on 2 Oct 2026, directing users to newer Gemini, Kimi, and Claude models. The shift requires administrators to adjust model policies and developers to update any automation that references the removed models.

What changed?

The following models will stop being available across all Copilot experiences (Chat, inline edits, ask/agent modes, and code completions):

• Gemini 3.5 Flash – deprecated 2026‑10‑02, replace with Gemini 3.8 Flash
• Gemini 3.6 Flash – deprecated 2026‑10‑02, replace with Gemini 3.8 Flash
• Kimi K2.7 Code – deprecated 2026‑10‑02, replace with Kimi K3
• Claude Opus 4.7 – deprecated 2026‑10‑02, replace with Claude Opus 5

GitHub recommends the listed alternatives for continued use.

Why it matters to AI and platform teams

AI engineers and platform teams that embed Copilot into CI/CD pipelines, IDE extensions, or custom agents will see failures if they request a deprecated model. Switching to the suggested alternatives preserves the same integration points while ensuring that generated code, suggestions, or chat responses remain available.

For DevOps/SRE and security engineers, the change can affect audit trails and compliance reporting that reference specific model versions. Updating the model reference eliminates gaps in traceability and avoids unexpected “model not found” errors during automated runs.

Operational considerations

Copilot Enterprise and Business administrators must verify that the replacement models are enabled in their organization’s model policy settings. The steps are:

1. Open the Copilot model settings for the organization or enterprise.
2. Confirm that the alternative model (e.g., Gemini 3.8 Flash) is listed and the policy toggle is on.
3. Save the changes; users will then see the new model in the Copilot Chat selector.

No manual removal of the deprecated models is required after the cut‑off date. Enterprise customers with concerns can reach out to their account team for assistance.

Related CloudNinjas coverage: AI engineering.

What This Means For Practitioners

Action items:

• Audit any scripts, CI jobs, or API calls that specify a now‑deprecated model and replace the identifier with the recommended alternative.
• Review and, if necessary, update Copilot model policies to grant access to the new models before 2 Oct 2026.
• Test the updated model in a staging environment to confirm that output quality meets expectations.
• Document the change in your team’s tooling guide to avoid future surprises.

By completing these steps ahead of the deprecation date, teams can maintain uninterrupted Copilot functionality and keep their development workflows stable.