If Microsoft Copilot tells you it can't take questions for an hour, you're almost certainly hitting a temporary service-side limit, not a problem with your account or your typing. The usual causes are a usage cap on the model you've selected, a short outage, or a regional capacity squeeze. The "hour" wording is a countdown to a reset window, and the fix is usually to wait, switch modes, or sign in with a different account.
What the "Can't Take Questions for an Hour" Message Actually Means
That message is a service response, not a device error. Copilot is telling you the request never reached the model — it was declined at the gate before processing. That distinction matters because device-level troubleshooting (clearing cache, reinstalling the app) won't move a service gate.
Microsoft runs Copilot on shared capacity across its consumer and business tiers, and it meters requests per account, per model, and per time window. When a meter trips, the system holds you out until the window rolls over. The app then displays a wait estimate, and an hour is one of the standard reset intervals.
The message is imperfect. It often appears as a generic banner rather than explaining which limit fired, so two users seeing identical text can be in completely different situations: one capped on a premium model, one caught in a partial outage, one on a work account that an administrator has throttled. Treat the text as "come back later," then narrow down which of those three you are.
Four Causes Ranked by How Often They Actually Cause This
Most reports trace back to the same short list. Start at the top and work down.
| Cause | What you'll notice | Typical wait | How to confirm |
|---|---|---|---|
| Premium model usage cap | Fails only when you pick a newer or "Think Deeper"-style mode | Minutes to about an hour | Switch to the standard quick mode and retry |
| Short service outage | Fails on every prompt, every mode, every browser | Minutes to a few hours | Check Microsoft's service health page for Copilot |
| Regional capacity squeeze | Fails at peak local hours, works late at night | Until off-peak | Retry at a different time of day |
| Account or tenant throttle | Personal account works, work account doesn't | Set by your admin | Sign in with a personal account to compare |
The first row is the most common and the most misunderstood. Copilot's consumer tiers include a free level and paid subscriptions, and the paid levels grant access to more capable models with their own usage ceilings. Those ceilings are real and they reset on a schedule, but Microsoft has changed the exact numbers repeatedly since launch. Check the plan comparison on Microsoft's own Copilot site for the current allowance rather than trusting a figure from an old blog post.
The middle rows explain the stubborn cases. If every mode fails at once, the problem isn't yours. Peak-hour congestion in a region can hold requests even when the status page shows green for other services, because Copilot capacity is provisioned differently from Outlook or Teams.
The Fastest Fixes to Try in Order
Work through these before assuming you're locked out for the full hour. Each step isolates one cause.
1: Switch from the premium model to the standard mode. If the standard mode answers, your paid-model allowance is spent and the wait is the reset timer. 2: Open Copilot in a private browser window. This rules out a stale session or a cached sign-in state. 3: Sign in with a second account. A personal Microsoft account and a work account have separate meters. If one works, the other is throttled. 4: Retry on a different network. A corporate proxy or a VPN exit in a congested region can be the blocker. 5: Check Microsoft's service health dashboard. Look specifically for Copilot entries, not a general "all systems normal" banner.
If steps 1 through 4 all fail, stop troubleshooting and treat it as an outage. Repeatedly hammering the prompt doesn't shorten a service-side wait and can extend a rate-limit hold if your account is flagged for rapid retries.
Why an Hour Specifically — and Why the Number Isn't Fixed
The hour is a window, not a rule. Copilot's limits operate on rolling or fixed reset schedules depending on the tier and the model, and the displayed wait is an estimate of when your specific meter clears. Two people capped at the same moment can see different countdowns.
Here's where the published information gets thin. Microsoft has never committed to a single public reset interval for every Copilot surface, and the limits differ across the consumer app, the Windows integration, Microsoft 365 Copilot for work, and Copilot in Edge. Any article quoting one exact number for all of them is guessing. The defensible statement is that usage resets happen on a schedule tied to your plan, and the app surfaces its own estimate.
A second reason the number drifts: model choice. Selecting a heavier reasoning model consumes more of your allowance per prompt than a quick answer does. A dozen hard prompts on a premium model can exhaust an allowance that would have absorbed a hundred simple ones. If your hour arrives after a burst of demanding questions, that's the pattern to recognize — and the practical lesson is to save heavy prompts for when you actually need them.
When It's a Genuine Outage, Not Your Limit
An outage looks different from a cap, and telling them apart saves you an hour of pointless waiting. The signature of an outage is that everything fails simultaneously: new chats, old chats, every model, every device, signed in or out.
Outages at this scale happen. Major cloud providers, including the infrastructure behind Microsoft's AI services, have suffered regional incidents that took assistants offline for stretches measured in hours. When that occurs, no amount of account switching helps, because the failure is upstream of your account entirely.
During an outage, watch two things: Microsoft's official service health page and the company's public status communications. Consumer Copilot outages are sometimes acknowledged there and sometimes only surfaced through press coverage, which is why checking both is worth thirty seconds. If the health page shows an active incident, close the tab and come back when it clears. If it shows nothing and your prompts still fail across every mode, the likeliest explanation is a capacity squeeze that hasn't been publicly flagged yet.
Work Accounts Behave Differently From Personal Ones
This is the cause most people miss. If Copilot is provisioned through your employer, the limits aren't the consumer ones. Your organization's IT administrator controls which models are enabled, whether usage is capped, and whether certain data types are blocked from prompts.
When a work account reports a wait, the reset schedule may be set by tenant policy rather than by Microsoft's consumer meter. That means the standard advice — wait an hour and it'll clear — can be wrong. A tenant-level restriction might hold until an administrator changes a setting, and no amount of waiting fixes it.
Here's the practical test. Sign out and try the same prompt with a personal Microsoft account. If the personal account answers and the work account doesn't, the block is organizational. From there, the correct move is a ticket to your IT help desk describing the exact message and the time it appeared, because your admin can see policy state that you cannot. If both accounts fail, it's a service issue after all, and you're back to waiting.
Edge Cases That Produce the Same Message
A handful of less common situations surface the identical banner, and each has a different remedy.
Education and nonprofit tenants. Copilot access through a school or nonprofit is often provisioned on restricted licensing, with tighter caps than either consumer or enterprise plans. A student who hits a wall mid-assignment may be on a license with a deliberately small allowance.
Regional previews and rollouts. Features that reach some markets first can carry trial capacity that runs out faster under demand. If a mode works for a colleague in another country and not for you, rollout stage is a plausible explanation.
Browser extension conflicts. Aggressive content blockers and privacy extensions occasionally break Copilot's session handling inside Edge or a browser with the Copilot sidebar. Disabling extensions for one test session is a quick way to eliminate it.
Stale sign-in tokens. An expired session can produce service-style errors rather than a clean sign-out prompt. Fully signing out and back in clears this, which is why the private-window test sits high in the fix order.
None of these are common, but they explain the cases where the standard advice fails twice in a row.
What to Do If the Hour Passes and It Still Won't Answer
The reset window came and went and the message is unchanged. At that point the working assumption should flip: you're probably not rate-limited anymore. Something structural is holding the request.
Start by capturing specifics — the exact wording, the timestamp, the model selected, the account type, and whether anything else in Microsoft's ecosystem (Outlook, Teams) is also misbehaving. Pattern-matching is how support teams diagnose these, and a vague "Copilot is broken" report wastes the first exchange.
Then escalate through the right channel. Consumer accounts go through Microsoft's support options for the Copilot app. Work accounts go through your IT help desk, because tenant-level settings are invisible to consumer support. Include the account-type finding from the previous section; it routes the ticket correctly the first time.
One behavior worth avoiding: cycling through dozens of retries in a short span. Rapid repeated requests can trigger additional rate-limit protection on top of whatever started the problem, and some users report the wait estimate growing rather than shrinking after a refresh storm. Patience is genuinely the faster path here.
How to Stop This From Costing You an Hour Again
The disruption is mostly about lost momentum, so the fix is about planning rather than prevention. You can't eliminate service-side limits, but you can stop them from landing mid-task.
Match model to task. Reserve the heavier modes for questions that truly need reasoning, and let quick answers handle lookups, rewrites, and simple drafts. A single demanding session on a premium model can burn allowance that a week of ordinary use wouldn't touch.
Keep a fallback. If Copilot is your drafting tool, know your second option before you need it — another assistant, a search engine, or the offline notes you already have. The cost of an hour's lockout isn't the hour; it's the ten minutes of scrambling while you decide what to do instead.
Front-load deadlines. If a deliverable depends on a tool with metered access, do that work earlier in the day and earlier in the week, and treat peak evening hours as a bad time to start anything dependent on it. Time-shifting costs nothing and sidesteps the congestion that produces most of these messages.
And when the wait does arrive, use it as a signal rather than an emergency. It usually means you've been working the tool hard, which is a reasonable moment to step back, and it almost always clears.
FAQ
Does the hour-long lockout mean my Copilot account is suspended?
No. A suspension blocks access entirely, including sign-in and settings, while this message only blocks new questions. Your history, settings, and subscription remain intact, and the standard modes often keep working while a premium mode is capped. If you can still open the app and see your past chats, your account is fine.
Can I get around the wait by creating a new Microsoft account?
Technically yes, and practically it's a poor trade. A fresh account starts with a fresh allowance, but you lose your chat history, your preferences, and any files you've connected, and creating accounts repeatedly to dodge limits can itself trigger abuse detection. For a one-off deadline it might bridge the gap; as a habit it costs more than it saves.
Why does Copilot work on my phone but not my laptop?
Copilot's consumer app and the web or desktop integrations can sit behind different service endpoints and session handling, so one can recover while the other is still held out. Check whether the laptop is signed into a work profile that the phone isn't using — that account difference explains the split more often than device type does.
Is the one-hour estimate always accurate?
Treat it as an estimate, not a countdown. The displayed wait is derived from your specific meter and can shrink or extend depending on how much other activity shares the window. Users on premium models often see it clear earlier than shown, while users in a congested region can see it extend past the estimate.
Does Microsoft 365 Copilot for work have the same limits as the consumer app?
No, and this trips people up constantly. The commercial product is licensed per seat through an organization, and usage policies, enabled models, and any caps are governed by the tenant's administrator. A work account's wait may reflect company policy rather than a consumer usage meter, which is why re-testing with a personal account is the fastest way to tell them apart.
What's the real cost of hitting the limit during a workday?
Count the recovery, not just the wait. Estimating an hour of blocked access plus roughly ten minutes of switching tools and rebuilding context, a single lockout can consume about seventy minutes of a working day — and that calculation assumes the estimate is accurate, which it often isn't at peak hours. Doing deadline-critical Copilot work in the morning avoids most of it.
Can a VPN cause the message to appear?
It can contribute. A VPN routes your requests through an exit in a different region, and if that region's Copilot capacity is strained, requests can be declined even though your home connection would succeed. Disconnecting the VPN for one test, or switching to a nearby exit, is a fast way to rule it in or out.