Test image generation through Copilot’s dedicated Create interface; this determines whether the supported image workflow behaves differently from image generation in Copilot Chat.
1. Test the dedicated Create workflow
Access requires an eligible Microsoft 365 subscription, and availability can depend on the account’s license and tenant configuration.^1^
- Open What do you want to create? in a supported browser.
- In the Copilot app, the equivalent path is Apps and more → Create.
- Select Create an image.
- Enter a simple description, such as:
Create a watercolor image of a red bicycle beside a lake.
- Select the right-arrow (➜) button.
- Repeat the test while signed into each account separately.
Interpret the result:
- Create works, but Copilot Chat fails: report the problem specifically as a Copilot Chat image-generation failure.
- Create is missing: for the business account, have the Microsoft 365 administrator verify that the account has the required subscription/license and that tenant configuration permits the feature. Microsoft documents that Copilot experiences vary by license and tenant configuration.^2^
- Create displays the same “Generation stopped” error: continue with the connectivity test below.
Microsoft notes that image-generation performance for users without a Copilot license depends on service availability and can vary during the day, so an intermittent service-side failure remains possible.^1^
2. Run the Copilot connectivity checks
Since reinstalling the app and using the web version did not help, do not reinstall again.
- Open Windows Start → Get Help.
- Search for Copilot connectivity troubleshooter.
- Run it and review its findings. This checks for firewall rules and other connection blockers.^3^
- Also run Microsoft’s Copilot connectivity test.
- Test once using a different connection, such as a mobile hotspot:
- If it works there, the normal network’s firewall, proxy, filtering, or TLS inspection is implicated.
- If it fails on both networks and for both accounts, that suggests—but does not prove—an account, device-wide, or service-side problem.
For the business network, ask the administrator to verify:
-
*.cloud.microsoft and Microsoft Copilot endpoints are allowed.
- Secure WebSocket connectivity is permitted to
*.office.com, *.cloud.microsoft, and copilot.cloud.microsoft.
- Proxies, firewalls, Conditional Access, tenant restrictions, and app-control policies are not blocking Copilot.
Microsoft documents that blocked WebSockets, interfering TLS inspection, and aggressive proxy timeouts can cause Copilot integrations to fail.^2^
3. Isolate the personal-account session
As a lower-probability check, personal accounts can be at different stages of migration to the updated Copilot experience.
- Start an InPrivate/Incognito browser window.
- Go to
copilot.microsoft.com.
- Sign in only with the affected personal account and test again.
Microsoft recommends this process when a personal account may be moving to the updated Copilot app.^4^
4. Report and escalate if all tests fail
In Copilot, select … → Send feedback → Report a problem. Include:
- The exact text: “Generation stopped — Something went wrong”
- When the failure began
- Windows version and browser
- Whether both Chat and Create an image fail
- Whether it fails on a second network
- The screenshot, with personal or organizational information removed
These details help Microsoft investigate and correlate the failure.^4^
Feedback is not a support case:
- Personal account: contact Microsoft Support after the tests above.
- Business account: ask the Microsoft 365 administrator to verify the license and open a Microsoft support request through the Microsoft 365 admin center.^5^
References
- Create AI-Generated Images With the Microsoft Copilot App
- Microsoft Copilot requirements
- Copilot troubleshooters | Microsoft Support
- Troubleshoot Your Content in the Updated Copilot App | Microsoft Support
- I am getting license validation errors with Copilot | Microsoft Support