This is a ridiculous change... if you're going to implement this, at least default the premium request paid usage policy to "Disabled" for those of us with $0/month budgets. I shouldn't have to dig through settings menus to avoid overage bills.

"What this means for your account:

Your current $0 budget prevents premium request overages. Once removed, your configured premium request paid usage policy will control paid usage beyond your included requests."

uhhh.. I thought having a $0 budget meant I didn't want to be charged any overages as I have $0 budget dollars allocated for this. I have no idea what a "premium request overage" is but this sounds like a 'you' problem, not a 'me' problem. If I have $0 budget then you should not be allowing me any kind overage, right? So, now you are inventing a process of obfuscation to get paid for a mistake you were already making instead of preventing the overage in the first place.

This is not enterprise or team org friendly at all. It's a money grab at its core.

Heads up that this link 404's if you have an enterprise - looks like it's using the enterprise display name instead of the enterprise slug.

And setting this dropdown to "disabled" 500s (presumably because I should control this setting at the Enterprise level, not the Organization level).

Sometimes I think to myself - is the lost goodwill worth whatever spare change you're going to make from users who fall for this?
TLDR: Some users disable extra budget -> you decide to rename the setting and enable it for them

I have it set to $0

Do I see an alert here? Anywhere? Nope.

Oh here's an alert! Right in the billing tab, because yes, we visit that page every day (:

Nice new setting which is enabled by default:

Now, the email to me says "your current" - so you know I have this disabled, why not retain this in the new setting? :)

This reminds me of Cursor pricing changes in July. I am wondering what is the strategy with these changes considering the backlash we already witnessed.

@Akash1134 when you say "your account's" in the following sentence, do you mean my individual account, or my organization account?:

August 22, 2025. As a result, premium request paid usage will be governed by your account’s premium request paid usage policy, not a static $0 budget.

How can I set budgets for individual users in my organization?

Just to get some confirmation:

• Now we have an Enterprise Budget: Copilot Premium Request = $0
• The new setting "Premium request paid usage" which is "Enabled" by default

And this is the new way to achieve the same?

• Set the new setting "Premium request paid usage" to "Disabled".
• Removing the "Enterprise Budget: Copilot Premium Request" Budget

Correct?

Unverified - ChatGPT explanation of Premium Requests...
⚙️ What Counts as a Premium Request?
Premium requests are consumed when using advanced features or models beyond the included GPT-4.1 and GPT-4o. Examples include:
Feature Premium Request Usage
Copilot Chat 1 per prompt × model multiplier
Copilot Coding Agent 1 per step (can be multiple per session)
Copilot Code Review 1 per comment posted
Copilot Extensions/Spaces 1 per prompt × model multiplier
Spark 4 per prompt
Example: Using Claude Opus 4 (10× multiplier) for one chat prompt = 10 premium requests.
2

🧠 Model Multipliers (Paid Plans)
Model Multiplier
GPT-4.1 / GPT-4o 0 (free)
GPT-5 1
Claude Sonnet 3.7 1
Claude Opus 4 10
Gemini 2.0 Flash 0.25
Using GPT-4.1 or GPT-4o does not consume premium requests on paid plans.

🛡️ Budget Controls
You can set a monthly spending limit for premium requests.
Default budget is $0, so overages are blocked unless you raise it.
Usage can be monitored in your IDE or GitHub billing settings.
📊 Example Cost Calculation
If a Copilot Pro user uses:
500 premium requests in a month (300 included)
200 overage × $0.04 = $8 extra
Total monthly cost = $10 (base) + $8 (overage) = $18

Even though this post is about Enterprise accounts and explicitly says Pro+ accounts will not be affected, my Coding Agent chats started using 3 Premium Requests each this morning. I just upgraded precisely to get 5x more Premium Requests and so this is very frustrating. See here for details.