Fix Copilot ‘Plugin Failed to Load’ Error in Microsoft 365

When you open Copilot in Microsoft 365 apps like Word, Excel, or Teams, you might see a red banner that says “Plugin failed to load.” This error stops Copilot from generating text, analyzing data, or answering questions. The root cause is usually a missing or outdated plugin, a blocked network connection, or a corrupted Copilot cache file. This article explains why the error occurs and provides step-by-step fixes to restore Copilot functionality.

Why the Plugin Failed to Load Error Occurs

Copilot in Microsoft 365 relies on a set of plugins to connect to Microsoft Graph, SharePoint, and other data sources. When a plugin fails to load, Copilot cannot authenticate or retrieve the data it needs to generate responses. The error appears in three common scenarios:

Missing or Deprecated Plugin Version

Microsoft updates Copilot plugins regularly. If your Microsoft 365 client is not on the Current Channel or Monthly Enterprise Channel, the plugin version may be outdated. The Copilot service refuses to load an incompatible plugin, resulting in the error.

Network or Proxy Blocking Plugin Endpoints

Copilot plugins must reach specific Microsoft endpoints to download their code and configuration. Corporate firewalls, VPNs, or proxy servers that block these endpoints prevent the plugin from loading. The error message appears without a detailed network error, making it hard to diagnose.

Corrupted Local Plugin Cache

Copilot stores plugin files in a local cache under the user profile. If a previous update was interrupted or the cache becomes corrupted, the plugin loader fails to read the files. This triggers the error on every Copilot session until the cache is cleared.

Steps to Fix the Plugin Failed to Load Error

Follow these steps in order. Test Copilot after each step to see if the error is resolved.

1. Check Microsoft 365 Service Health
   Go to the Microsoft 365 admin center at admin.microsoft.com. Select Health > Service health. Look for any advisory or incident under “Copilot.” If a service outage is listed, wait for Microsoft to restore the service before proceeding.
2. Run Microsoft 365 Quick Repair
   Open Windows Settings > Apps > Installed apps. Find Microsoft 365 in the list. Click the three-dot menu and select Modify. Choose Quick Repair and follow the prompts. This re-registers all Copilot components without removing your data.
3. Clear the Copilot Plugin Cache
   Close all Microsoft 365 apps. Press Windows key + R, type %localappdata%\Microsoft\Office\16.0\Lync\Plugins and press Enter. Delete all files and folders inside the Plugins folder. Restart any Microsoft 365 app and reopen the Copilot pane.
4. Verify Plugin Deployment in Admin Center
   Sign in to the Microsoft 365 admin center. Go to Settings > Integrated apps. Select Copilot and click the Deployment tab. Confirm the plugin is set to Enabled for all users. If it shows Disabled or Pending, change the status to Enabled and click Save.
5. Allow Copilot Endpoints in Firewall
   Ask your IT team to unblock the following URLs on your network firewall: copilot.microsoft.com and all subdomains, office.net and all subdomains, and graph.microsoft.com and all subdomains. Without access to these endpoints, the plugin cannot download its initialization code.
6. Update Microsoft 365 to the Current Channel
   Open any Microsoft 365 app, go to File > Account > Update Options > Update Now. If you are on a Semi-Annual channel, switch to the Current Channel or Monthly Enterprise Channel by running the Office Deployment Tool with the correct channel ID. Restart the app after the update.

If Copilot Still Has Issues After the Main Fix

Copilot Plugin Failed to Load in Teams Only

If the error appears only in Microsoft Teams, the Teams app may be using a cached version of the plugin. Clear the Teams cache by closing Teams, deleting the %appdata%\Microsoft\Teams folder, and restarting Teams. Sign in again and test Copilot.

Plugin Failed to Load After a Windows Update

A Windows update can reset registry keys that Copilot plugins depend on. Run the Microsoft 365 Quick Repair from step 2 again. If the error persists, perform an Online Repair by selecting Online Repair instead of Quick Repair in the Modify dialog. This takes longer but reinstalls all Office components.

Copilot Works in One App but Not Another

This usually indicates a per-app plugin conflict. Open the affected app, go to the Copilot pane, and click Settings. Under Plugins, disable all third-party plugins, then re-enable them one at a time. Test after each enable to identify the conflicting plugin.

Copilot Plugin Error vs Other Copilot Errors: Key Differences

Item	Plugin Failed to Load	Other Copilot Errors
Error message	“Plugin failed to load” with red banner	“Something went wrong” or “Copilot is unavailable”
Root cause	Missing, outdated, or blocked plugin	Service outage, license issue, or connectivity problem
Primary fix	Clear cache and re-register plugin	Check service health or license assignment
Admin involvement	Often required for firewall or deployment	Sometimes required for license or tenant policy
User action	Cache clear and Quick Repair	Sign out and sign in or update app

After applying the fixes in this article, you should be able to open the Copilot pane without seeing the plugin error. If the problem returns after a Microsoft 365 update, repeat the cache clear step and the Quick Repair. For recurring issues, ask your IT admin to check the Microsoft 365 admin center for any pending plugin deployment changes.