Copilot in Microsoft 365 typically shows “Something went wrong” or similar errors when there are licensing, sign-in, or connectivity issues rather than an installation problem.
Use these checks and fixes:
- Confirm Copilot license and propagation
- Copilot requires a supported Microsoft 365 Copilot license.
- If a license was just assigned or changed, it can take time to propagate. During this period Copilot may not validate and can show generic errors such as “Something went wrong” or license-related messages.
- If the issue persists after some time, contact the Microsoft 365 admin to verify that a license that supports Microsoft 365 Copilot is correctly assigned and active.
- Check for account conflicts
- Being signed in with both a personal Microsoft account and a work/school account can cause Copilot validation failures.
- Sign out of all accounts in the Microsoft 365 apps and browser, then sign back in with only the account that has the Copilot license.
- Verify network and browser settings (for web apps)
- Copilot requires specific network access. If network requirements are not met, Copilot can fail with generic errors. See the network requirements in Microsoft 365 Copilot requirements.
- In the browser, blocked third‑party cookies can prevent license validation and cause Copilot to fail. Enable third‑party cookies and refresh the page, as described in the Copilot button troubleshooting guidance.
- Refresh the Office/Copilot license in the apps
- If Office was recently reset or updated, activation status can be affected and Copilot may stop working.
- On Mac, for example:
- In any Microsoft 365 app, open the app menu (such as Word).
- Select About <app name> → More Info... → Refresh License.
- Close all documents and restart the apps so the refresh takes effect.
- Similar license refresh steps are available per the “How to find and enable missing Copilot button in Microsoft 365 apps” article.
- Check privacy/connected experiences settings
- Copilot can be blocked by privacy settings:
- Ensure Experiences that analyze your content is turned on.
- Ensure All connected experiences is turned on.
- If Microsoft 365 is managed by an organization, these settings may be controlled by admin policies; the admin must allow Copilot and connected experiences.
- Confirm environment and update channel support
Copilot will not work in these cases:
- Device‑based licensing is used instead of user‑based licensing for Microsoft 365 Apps.
- The Semi‑Annual Enterprise Channel is used as the update channel; Copilot requires Current Channel or Monthly Enterprise Channel.
- Shared Computer Activation (SCA) is used; Copilot is not supported in SCA environments.
- If the error is a sign‑in error like “Something went wrong [1001]”
- Some “Something went wrong” errors are sign‑in issues rather than Copilot itself. For example, error [1001] can be caused by:
- Security software impacting the WAM plug‑in (AAD.BrokerPlugin).
- User profile management issues (for example, in virtual desktop environments).
- Mitigations include:
- Rebooting the device.
- Repairing WAM via the documented PowerShell commands in the “Error ‘Something Went Wrong [1001]’ signing in to Microsoft 365 Desktop Applications” article.
- Reviewing device identity and profile configuration in virtual desktop scenarios.
- If Copilot still will not work
- For home users: after checking the above, contact Support using the Copilot license validation article’s support link.
- For business users: ask the Microsoft 365 admin to:
- Confirm the Copilot license assignment.
- Ensure Copilot is not blocked by organizational policies (for example, app settings in Teams Admin Center, DLP policies, or privacy controls).
- Open a support ticket with Microsoft if the problem persists.
References: