Skip to main content

Avoiding unexpected costs from GitHub Copilot premium requests

Starting from last week June 18, 2025 an important change was activated in GitHub Copilot. From that day on you need to pay extra for any premium requests that exceed your monthly allowance. This means that we should start considering more how we use Copilot and be aware of the (potential) costs.

What are premium requests?

Premium requests are requests that use more advanced processing power and apply to any request that is not using the default models (GPT-4o and GPT-4.1 at the moment of writing this post).

The number of premium requests you get out-of-the-box is different depending on the plan you are using:

Important! Be also aware that a multiplier is applied to the cost depending on the model used. For some models (e.g. GPT-4.5) this can add up quickly as the multiplier can be as high as 50!

 

Disabling premium requests

If you want to avoid unexpected costs, you can disable premium requests so that they don’t exceed your monthly allowance of premium requests.

  • Go to the settings for your GitHub organization:

https://github.com/organizations/<yourorgname>/settings/

  • Click on Copilot – > Policies:

 

  • In the billing section at the top, set Additional Copilot premium requests to Disabled:

 

More information

Understanding and managing requests in Copilot - GitHub Docs

Plans for GitHub Copilot - GitHub Docs

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more