Annual subscribers to GitHub Copilot are experiencing rapid depletion of their account quotas following a recent change in Microsoft’s billing policy. While monthly users have already encountered increased costs due to the updated pricing model, those on legacy annual plans are now facing accelerated consumption of their request limits, with some seeing their quotas exhausted up to four times faster than before. This shift has occurred without advance notice or transitional measures, resulting in unexpected workspace lockouts for many users.

Policy Change and Its Effects

The change coincided with the system update launched on June 1. Although annual subscribers are not billed per token, the rate at which their premium request quotas are consumed has increased significantly. Under the new terms, 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 such as Claude Opus 4.7 would use 7.5 premium requests per prompt. This week, the same action now incurs a 27x multiplier. Similarly, requests to OpenAI’s GPT-5.4 have increased from a 1x to a 6x penalty per use.

Impact on Development Teams

As a result, many annual subscribers are using up their entire monthly quotas within just a few days, even with standard development activity. There have been no significant increases in usage or misuse of the platform—routine workflows alone are now enough to exhaust allowances.

Additional Billing Restrictions

Further complicating the situation, developers attempting to purchase additional AI credits to restore access are encountering strict spending limits. These restrictions are based on account age and verification status, and accounts with lower compliance ratings are unable to add funds without renegotiating organizational agreements.

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

Rationale and Consequences

Microsoft has stated that the changes are intended to better align costs with the actual computing resources required by advanced AI models. However, the abrupt implementation has forced engineering teams to reconsider their budgeting for developer tools, treating them as variable expenses rather than predictable costs. Teams relying on stable, quarterly budgeting for these tools are particularly affected by the new policy.