You are working in a Microsoft 365 app and Copilot suddenly stops generating a response. The error message says “Response was stopped” or the output simply cuts off mid-sentence. This usually happens because of a network interruption, a content filter trigger, or a temporary service limit on Copilot’s side. This article explains the root causes of the stopped-response error and provides step-by-step fixes to restore normal Copilot behavior.
Key Takeaways: Fixing the Copilot Response Stopped Error
- Copilot response timeout (30-second limit): Long prompts or complex queries can exceed Copilot’s processing window and trigger a stop.
- Microsoft 365 service health dashboard: Check if Copilot services have an active advisory or outage before troubleshooting locally.
- Content filtering by Microsoft Purview: Certain words or data patterns can cause Copilot to halt mid-response to avoid policy violations.
Why Copilot Stops Responding Mid-Generation
Copilot generates responses in real time by streaming tokens from Microsoft’s cloud infrastructure. If the stream is interrupted for more than a few seconds, the client app displays “Response was stopped” and the partial output remains. Three main factors cause this interruption:
Network Latency and Packet Loss
Copilot requires a stable HTTPS connection to Microsoft Graph and the large language model endpoint. When packet loss exceeds 2 percent or latency spikes above 500 milliseconds, the streaming connection can drop. This is especially common on VPNs, public Wi-Fi, or corporate networks with strict traffic shaping.
Content Moderation Triggers
Microsoft 365 applies content safety filters through Microsoft Purview. If Copilot detects a potentially sensitive term, a personal data pattern like a Social Security number, or a phrase that matches a blocked keyword list, it stops the response immediately. The user does not see a separate warning — only the stopped response message.
Service-Side Rate Limits
Each Microsoft 365 tenant has a per-user rate limit for Copilot requests. When a user sends multiple long prompts within a short window, the service may throttle or stop the response to protect overall capacity. The exact limits vary by license type, but the error appears the same regardless of the cause.
Steps to Fix the Copilot Response Was Stopped Error
Follow these steps in order. Test Copilot after each step to see if the error clears.
- Verify service health in the Microsoft 365 admin center
Go to Microsoft 365 admin center > Health > Service health. Look for any advisory with the title “Copilot” or “Microsoft 365 Copilot”. If a service degradation is listed, wait for Microsoft to resolve it before proceeding. - Restart the Microsoft 365 app
Close Word, Excel, or Outlook completely. Reopen the app and try the same Copilot prompt again. This clears any temporary client-side state that may be holding a broken stream connection. - Disconnect and reconnect your VPN
If you use a VPN, disconnect it and test Copilot. If the response completes, your VPN is causing packet loss or latency. Reconnect and try a different VPN server or switch to a direct connection. - Shorten your prompt and remove sensitive terms
Edit your original prompt. Remove any full names, email addresses, phone numbers, or financial identifiers. Keep the prompt under 200 words. A shorter prompt reduces the chance of a content filter trigger and stays within the streaming timeout window. - Clear the Microsoft 365 cache
In Windows 11 or Windows 10, press Ctrl + Shift + Esc to open Task Manager. End all Microsoft 365 processes like WINWORD.EXE and EXCEL.EXE. Then press Windows key + R, type %appdata%\Microsoft\Office\16.0, and delete the Cache folder. Restart the app and try again. - Check Copilot data source settings
Open the Copilot pane in any Microsoft 365 app. Click Settings then Plugins. Ensure that only the plugins you need are enabled. Disable third-party plugins temporarily. Too many active plugins can slow response generation and cause a timeout. - Sign out and sign back in
Click your profile picture in the top-right corner of the Microsoft 365 app. Select Sign out. Close the app, reopen it, and sign in again. This refreshes your authentication token and reestablishes the Copilot session. - Contact your IT administrator
If the error persists, ask your admin to check the Microsoft Purview compliance portal > Data loss prevention > Policies. A DLP rule may be blocking Copilot responses that contain certain data types. The admin can create an exception for your user group or adjust the sensitivity labels.
If Copilot Still Has Issues After the Main Fix
Copilot Returns Generic Output Instead of Tenant-Specific Data
If the response completes but contains only general information, Copilot may have lost access to your Microsoft Graph data. Go to Microsoft 365 admin center > Settings > Copilot > Data sources. Ensure that Microsoft Graph is enabled and that your tenant allows Copilot to read files from SharePoint and OneDrive. This setting controls grounded responses.
Copilot Works in One App but Not Another
Copilot is available in Word, Excel, PowerPoint, Outlook, Teams, and the Microsoft 365 web apps. If it works in Word but fails in Outlook, the issue is usually an Outlook add-in conflict. Go to Outlook > File > Options > Add-ins. Disable all non-Microsoft add-ins, restart Outlook, and test Copilot again.
Copilot Shows Error Code “CopilotResponseInterrupted”
This specific error code appears when the streaming connection times out. It is most common on networks with high latency. Run a continuous ping to graph.microsoft.com from a Command Prompt window. If you see “Request timed out” or latency above 1000 ms, the network is the root cause. Contact your network team to optimize the route to Microsoft’s endpoints.
Copilot Response Stopped vs Copilot Not Available: Key Differences
| Item | Response Was Stopped | Copilot Not Available |
|---|---|---|
| User message | “Response was stopped” appears mid-generation | Copilot pane shows “Copilot is not available right now” |
| Root cause | Stream interruption, content filter, or rate limit | License validation failure or service outage |
| Partial output | Yes — partial text remains visible | No — no output appears |
| Primary fix | Shorten prompt, check network, clear cache | Verify license assignment in admin center |
| Time to resolve | Usually within 5 minutes | May require admin action or service restoration |
Understanding this difference helps you choose the correct troubleshooting path. If you see “Copilot is not available right now,” skip the cache-clearing steps and go directly to the Microsoft 365 admin center to confirm that the user has an active Copilot license assigned.
You can now identify the cause of a stopped Copilot response and apply the correct fix in under five minutes. Start by checking service health, then shorten your prompt and clear the app cache. If the error persists, ask your admin to review Purview DLP policies. For ongoing reliability, keep your Microsoft 365 apps updated through the Microsoft 365 Apps admin center and use a wired network connection when working with long prompts.