Premium models locked even with active budget — Copilot stuck in legacy “included-only” mode #181634
Unanswered
CostaTech
asked this question in
Copilot Conversations
Replies: 1 comment 3 replies
-
|
I have the same problem. Got any solution? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
VS Code
Body
i everyone, I’m experiencing a persistent issue with Copilot Pro that seems related to backend entitlement configuration. I want to share the full details here in case others are affected, or if a GitHub engineer can take a look.
Problem Summary
I have an active Copilot Pro subscription purchased directly through GitHub.com.
My included 300 premium requests have been consumed, and I have configured a $10 monthly budget for All Premium Request SKUs with “stop usage” disabled.
However, Copilot completely blocks premium models after the included quota, and always shows:
Despite:
Premium models like GPT-4.1 Pro, GPT-5.1, Claude Sonnet, etc. are not usable at all.
What I Have Already Checked
Billing and Budget
VS Code troubleshooting
{})Technical Indicators (from logs and Copilot Chat diagnostics)
From Copilot Chat diagnostics and behavior, my account seems to be stuck in legacy “included-only” quota mode.
Specifically, the backend fields required for metered billing appear missing:
MeteredBillingEnabled→ missingPremiumRequestMeteredQuota→ not attachedCostCenternot mapped to premium metered SKUVS Code logs also show:
commandEmbeddings.jsonpersisting from previous provisioningThese are signs that Copilot’s entitlement token does not include premium metered capabilities.
Expected Behavior
After the 300 included premium requests, Copilot should:
This is not happening.
Actual Behavior
Suspected Root Cause
This appears to be an entitlement migration failure at the account backend level.
Based on similar cases, the following backend updates are typically required:
MeteredBillingEnabledfor my userPremiumRequestMeteredQuotabucketThis matches every symptom I’m seeing.
Request
If possible, could this be forwarded to the Copilot Billing Engineering team?
This issue blocks all premium usage even though everything is correctly configured on my side.
If anyone else has experienced this problem or found additional clues, your feedback would be extremely helpful.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions