GitHub closes its Models playground to new customers and routes new work to Azure AI Foundry

GitHub is retiring GitHub Models, the free in-platform AI playground it introduced in 2024, and any pipeline or experiment wired through its API now has a migration path attached to it. Per DevOps.com, the feature is closed to new customers as of June 16: organisations that have not used it before cannot start. Existing customers with active usage "can continue using the playground, API, and models as usual," and GitHub is directing developers who need model access for new projects to Azure AI Foundry.

What is closed and what is not

The cutoff is on enrolment, not on running workloads. New customers are out. Existing customers keep playground, API and model access, the wording DevOps.com pulls is "as usual," which is the part to read carefully. As-usual coverage carries no end date in what is reported, and no parallel commitment that the underlying models, rate limits or routing stay frozen. A grandfathered surface that works today is not the same as a surface a platform team can safely build a new pipeline against.

GitHub Models gave a single API key access to Meta's Llama 3.1, OpenAI's GPT-4o and GPT-4o mini, Cohere's Command, and Mistral Large 2, a deliberately broad menu through one credential. That convenience is what disappears for new starters. Azure AI Foundry, the recommended next step per DevOps.com, is a different surface: separate account path, separate billing and a different operational model from "the key already lives in my GitHub org."

The operational read

For teams already pulling models through that single key in CI, release-note drafting, PR summarisation, test triage, the immediate task is an inventory of where the credential is referenced and what would break if "as usual" stops being literally true. There is no published timeline tying that surface to an end date. There is also no commitment that the model menu behind it stays the same. For teams that were planning to start, the door is already shut and the work to evaluate Azure AI Foundry has effectively moved up the backlog.

The retirement is signposted. The deadline is not.