Annual subscribers to GitHub Copilot are seeing their account quotas deplete rapidly after a recent change in Microsoft’s billing policy. While monthly users have already faced higher costs due to the updated pricing model, those on legacy annual plans are now experiencing much faster consumption of their request limits—some are exhausting their quotas up to four times quicker than before. This change was introduced without prior notice or transitional support, leading to unexpected workspace lockouts for many users.

Policy Change and Its Effects

The shift coincided with a system update launched on June 1. Although annual subscribers are not charged per token, the rate at which their premium request quotas are used has increased dramatically. Under the new policy, using advanced reasoning models now deducts multiple requests from a user’s fixed monthly allowance for each interaction.

Previously, running a complex query through models like Claude Opus 4.7 would consume 7.5 premium requests per prompt. This week, the same action now applies a 27x multiplier. Similarly, requests to OpenAI’s GPT-5.4 have gone from a 1x to a 6x penalty per use.

Impact on Development Teams

As a result, many annual subscribers are burning through their entire monthly quotas in just a few days, even with normal development activity. There have been no notable increases in usage or abuse of the platform—routine workflows alone are now enough to exhaust allowances.

Additional Billing Restrictions

To make matters worse, developers trying to purchase extra AI credits to regain access are running into strict spending limits. These restrictions depend on account age and verification status, and accounts with lower compliance ratings cannot add funds without renegotiating organizational agreements.

Once users hit their credit limits, access to premium reasoning engines is immediately suspended. Development teams are left with few choices: reduce daily usage, wait for the next monthly quota reset, or upgrade to an enterprise contract.

Rationale and Consequences

Microsoft has explained that these changes are meant to better align costs with the actual computing resources required by advanced AI models. However, the sudden rollout has forced engineering teams to rethink their developer tool budgets, treating them as variable rather than fixed costs. Teams that rely on stable, quarterly budgeting for these tools are especially impacted by the new policy.