When you use Copilot in Microsoft 365 apps such as Word, PowerPoint, or Outlook, you may see a red error banner that reads “Generation Failed.” This message stops Copilot from producing text, slides, or email drafts. The failure usually happens because Copilot cannot reach the Microsoft 365 cloud service or because your tenant’s Copilot license is misconfigured. This article explains the technical reasons behind the error and provides a precise set of steps to restore Copilot generation.
Key Takeaways: Restoring Copilot After a Generation Failed Error
- Microsoft 365 admin center > Billing > Licenses: Verify each user has an active Copilot for Microsoft 365 license assigned.
- Windows Settings > Network & Internet > Proxy: Disable any manual proxy server that may block Copilot traffic to api.copilot.microsoft.com.
- Microsoft 365 admin center > Org Settings > Copilot: Confirm the service is enabled for your entire tenant and not restricted by conditional access policies.
Why Copilot Shows “Generation Failed”
The “Generation Failed” error appears when Copilot cannot complete a request to the Microsoft 365 AI backend. The root cause falls into one of three categories: network interruption, license or service configuration, or a temporary service outage on Microsoft’s side.
Network Interruption
Copilot requires a stable HTTPS connection to api.copilot.microsoft.com and related Microsoft endpoints. A corporate proxy, VPN, or firewall that blocks these domains prevents Copilot from sending prompts or receiving generated content. The error appears immediately after you press Enter or click Generate.
License or Service Misconfiguration
Each user must have an active Copilot for Microsoft 365 license assigned through the Microsoft 365 admin center. If the license is expired, not assigned, or if the tenant-level Copilot toggle is turned off, the service refuses all generation requests. Additionally, conditional access policies in Microsoft Entra ID can block Copilot authentication tokens.
Service Outage
Microsoft occasionally experiences service degradation or outages for the Copilot backend. These events are posted on the Microsoft 365 Service Health dashboard in the admin center. During an outage, no user-side fix will work until Microsoft resolves the issue.
Steps to Diagnose and Fix the Generation Failed Error
Follow these steps in order. After each step, test Copilot by asking a simple question such as “Summarize this document.” If the error persists, move to the next step.
- Check Microsoft 365 Service Health
Sign in to the Microsoft 365 admin center at admin.microsoft.com. Go to Health > Service Health. Look for any advisory or incident under Copilot for Microsoft 365. If an incident is active, wait for Microsoft to resolve it. Do not proceed with other steps until the incident is closed. - Verify Copilot License Assignment
In the admin center, go to Billing > Licenses. Select Copilot for Microsoft 365. Check that the number of assigned licenses matches your active users. If a user is missing a license, select the user and click Assign license. Wait 5 minutes for the change to propagate, then test Copilot. - Enable Copilot at the Tenant Level
In the admin center, navigate to Org Settings > Copilot. Ensure the toggle Allow Copilot for Microsoft 365 is set to On. If it is off, turn it on and click Save. Test Copilot after saving. - Check Conditional Access Policies
Open the Microsoft Entra admin center at entra.microsoft.com. Go to Protection > Conditional Access > Policies. Look for any policy that targets Microsoft Copilot Service or All cloud apps. If a policy blocks access, create an exclusion for the Copilot service app. Apply the change and test. - Disable Proxy or VPN
On your Windows device, open Settings > Network & Internet > Proxy. Turn off Use a proxy server if it is enabled. If you use a corporate VPN, disconnect and try Copilot without the VPN. If Copilot works, add api.copilot.microsoft.com to the VPN or proxy bypass list. - Clear Microsoft 365 Cache
Close all Microsoft 365 apps. Press Windows key + R, type %localappdata%\Microsoft\Office\16.0\OfficeFileCache, and press Enter. Delete all files in this folder. Restart Word or Outlook and test Copilot. - Repair Microsoft 365 Installation
Open Control Panel > Programs and Features. Right-click Microsoft 365 Apps for Enterprise and select Change. Choose Quick Repair and follow the prompts. After the repair completes, restart your computer and test Copilot.
If Copilot Still Shows Generation Failed After the Main Fix
Some users experience the error only in specific scenarios. The following subsections address those edge cases.
Copilot Fails Only in Word but Works in Outlook
This indicates a corrupted Word add-in or template. Open Word in safe mode by pressing Ctrl and clicking the Word icon. If Copilot works in safe mode, disable third-party add-ins under File > Options > Add-ins > COM Add-ins. Restart Word normally.
Generation Failed Error Appears After a Microsoft 365 Update
A recent update may have disabled the Copilot add-in. In Word or PowerPoint, go to File > Options > Add-ins. At the bottom, next to Manage, select COM Add-ins and click Go. Ensure Microsoft Copilot is checked. If it is missing, click Add and browse to C:\Program Files\Microsoft Office\root\Office16\Addins\CopilotAddin.dll.
Copilot Returns Generation Failed for All Users in the Tenant
This points to a tenant-level configuration problem. Verify that your tenant has not exceeded the Copilot usage quota. In the admin center, go to Billing > Subscriptions and check the Copilot for Microsoft 365 subscription status. If the subscription is expired or suspended, renew it immediately.
| Item | Cause | Fix |
|---|---|---|
| Network block | Proxy or firewall blocks api.copilot.microsoft.com | Disable proxy or add domain to bypass list |
| Missing license | User does not have Copilot for Microsoft 365 license | Assign license in admin center |
| Tenant toggle off | Copilot disabled in Org Settings | Enable Copilot toggle in admin center |
| Conditional access | Policy blocks Copilot service app | Exclude Copilot service from policy |
| Corrupted cache | Office file cache contains stale data | Delete OfficeFileCache folder |
| Service outage | Microsoft backend incident | Wait for Microsoft to resolve |
You can now diagnose and resolve the “Generation Failed” error by checking service health, licenses, tenant settings, and network configuration. Start with the Microsoft 365 Service Health dashboard to rule out a service outage. After the fix, test Copilot in a new document rather than an existing one to avoid cache-related issues. As an advanced tip, use the Microsoft 365 admin center > Reports > Copilot for Microsoft 365 page to monitor usage and identify users who frequently encounter this error.