If Copilot image generation stopped working for you sometime around mid-April 2026, you almost certainly don’t have a bug. You have a billing change. On April 15, 2026, Microsoft quietly removed in-app Copilot features — including image generation — from anyone without a paid Microsoft 365 Copilot Premium licence. There was no in-product announcement, no email warning, and no farewell tour. One day the Copilot button worked. The next day it produced nothing, or it appeared to work but never rendered an image.

That single change accounts for the majority of the “Copilot stopped generating images” search traffic in 2026. If your subscription is Microsoft 365 Personal, Family, Business Basic, Business Standard, or Business Premium without a separate Copilot add-on, that’s the answer. The fix is either to add the Copilot licence at roughly $30 per user per month or to use Copilot Chat at copilot.microsoft.com instead, where free users still get a daily image generation allowance.

For everyone who does hold a paid Copilot licence and is still seeing failures, the actual technical causes are below — in order of how often they’re actually the problem, not in order of how often Microsoft’s troubleshooting docs mention them.

A moving target — verified for May 2026

Copilot is changing every month. Features rolling out in March were not present in January. The April 15 licensing cliff reshaped the entire surface area of who has access to what. This article is verified against Copilot behaviour as of May 2026, but specific menu paths, feature names, and error messages may shift within a quarter. The structural causes of failure — licensing, account context, file location, content policy, region — are stable, and those are what this article focuses on.

Cause one: the licence isn’t what you think it is

Microsoft has multiple Copilot licences and product names that are easy to confuse. As of May 2026:

  • Microsoft 365 Copilot (Premium) — the paid enterprise/business add-on, roughly $30/user/month, required for in-app image generation in Word, Excel, PowerPoint, and OneNote.
  • Copilot Pro — the consumer-tier paid add-on for Microsoft 365 Personal and Family subscribers.
  • Microsoft 365 Copilot Chat — the free chat experience at copilot.microsoft.com, with a daily image generation allowance for commercial users.

Until April 15, 2026, the chat-tier experience also produced an in-app Copilot pane in the desktop apps. After that date, the chat tier is browser-only. The Copilot pane in your desktop Word or PowerPoint, if you don’t have a paid Premium or Pro licence, will either be gone entirely or will appear but refuse to generate.

To check what you actually have: in Word, click File → Account, and look at the Subscription Product line. If it says “Microsoft 365” without “Copilot” appearing alongside it, you don’t have the in-app generation feature. Your subscription page at account.microsoft.com or your tenant admin panel will confirm.

If you have multiple accounts signed in to Word — a personal account and a work account, for instance — the active account matters. Word generates images using whichever account is active in the document, not whichever account has the Copilot licence. Switch the active account to the licensed one. This single fix resolves a meaningful percentage of “Copilot accepted my prompt but never produced an image” complaints.

There is one additional licensing wrinkle that catches educators specifically: Microsoft Education tenants retain free access to a portion of the Microsoft 365 Copilot app, including a Teach module with classroom-specific tools like Align to Standards, Modify Reading Level, and Differentiate Instructions. That free access does not extend to in-app image generation in Word or PowerPoint for general use. The Education exemption is narrower than the marketing suggested, and the April 15 cliff applied to Education tenants for non-Teach features in the same way it applied everywhere else.

Cause two: the file isn’t saved to OneDrive

Copilot’s image generation features in the desktop apps require the document to be saved in OneDrive, OneDrive for Business, or SharePoint. Not “saved to a local OneDrive folder that is currently syncing.” Saved as a cloud-resident document.

If you opened Word, started a new blank document, and started prompting Copilot without saving first, the generation will fail. Sometimes silently — the prompt is accepted, the spinner appears, and then nothing happens. Sometimes with an error that doesn’t mention the cause.

The fix: File → Save As → OneDrive or SharePoint → save with a name. Then try the prompt again. This requirement is documented but easy to miss because the error is often presented as a generic Copilot failure rather than “this document needs to be in the cloud.”

This is also one of the easiest causes to verify yourself — try the same prompt on a freshly saved cloud document, in a fresh session, with no prior failures. If it works, the original document’s storage location was the issue.

Cause three: your tenant admin disabled it

In a managed Microsoft 365 environment, the tenant administrator controls whether Copilot’s generative features are enabled, which users can access them, and whether features like image generation specifically are permitted.

Common tenant-side restrictions:

  • The Copilot licence isn’t assigned to your account. The tenant has Copilot licences but hasn’t allocated one to you.
  • Connected experiences are disabled. Copilot image generation requires connected experiences that analyse content; if your tenant has disabled this category, generation will fail.
  • Image generation is specifically restricted as a content policy. Some regulated industries — finance, healthcare, government — have disabled image generation while permitting text features, on the grounds that generated images are harder to audit.

You can’t fix tenant-level restrictions yourself. The action is to ask IT what your tenant’s Copilot configuration permits. If image generation is restricted and you have a legitimate work case, that conversation is the only way through.

Cause four: content policy refusals

Even with everything correctly licensed and configured, Copilot’s image generation will refuse certain prompt categories. The refusal is sometimes explicit — “I can’t generate that image” — and sometimes silent, where the prompt is accepted and the generation completes without producing anything visible.

Categories that trigger refusals:

  • Real, named public figures or celebrities. Copilot will not generate images of specific real people by name.
  • Trademarks, branded products, and copyrighted characters. Disney, Marvel, Nike-branded items, recognisable franchise characters — all refused.
  • Violence, weapons used aggressively, gore, or graphic content.
  • Sexual or suggestive content.
  • Children in scenarios that approach the above categories, including ambiguous ones — Copilot’s safety filtering is more restrictive than the underlying DALL-E 3 model.
  • Political content that could be interpreted as advocacy.
  • Some medical imagery, particularly anything involving injury or disease states.

Silent refusals are the frustrating ones — you get no error, just no image. If your prompt is close to any of those categories, rewriting in more abstract language often works. “A photo of a corporate leader speaking at a podium” succeeds where “a photo of [specific CEO name]” fails.

Cause five: regional availability

Copilot’s image generation is not universally available in every Microsoft 365 region. As of May 2026, the feature has rolled out to most major markets, but a small set of countries either don’t have it yet or have it gated behind tenant configuration. China-based tenants in particular have a different Copilot offering. Some EU jurisdictions had a delayed rollout for AI features pending DSA and AI Act compliance work, and a handful still have restricted feature sets.

If you’re outside the US, UK, and major EU/APAC markets, check Microsoft’s current Copilot availability documentation before assuming a bug. The product page lists currently available regions and excluded ones.

Cause six: the prompt accepted but never rendered

This is the most reported failure mode in 2026: you write a prompt, click generate, the UI shows some indication of work happening, and then… nothing. No image. No error. The prompt is left in the chat history with no result attached.

This usually means one of the previous causes — wrong account active, document not in OneDrive, tenant restriction, content policy refusal — but the UI failed to surface a useful error. The diagnostic sequence:

  1. Close Word or PowerPoint completely and reopen. Not “close the document” — close the entire application. Reopen, sign back in if prompted, try again.
  2. Sign out and sign back in. File → Account → Sign Out, then re-add the account.
  3. Try the simplest possible prompt on a freshly saved cloud document. “Create an image of a blue circle on a white background” — something with no possible content policy trigger.
  4. Test outside the Office app. Go to copilot.microsoft.com in a browser, sign in with the same account, and ask for the same image. If it works there, the issue is in the desktop app, not the image service. If it fails there too, the issue is licensing, region, or content policy.
  5. Try a different network. Some corporate proxies and SSL-inspecting security tools interfere with Copilot’s calls in ways that cause silent failures. Test on a different network (mobile hotspot is the quickest A/B).

If steps 1 through 4 all fail on a properly licensed account with a known-good prompt, the issue is almost certainly account-level on Microsoft’s side and requires a support ticket. There is no client-side fix.

Workarounds that work today

If you need an image immediately and Copilot won’t produce one in Word or PowerPoint:

  • Copilot Chat at copilot.microsoft.com. Free, browser-based, has a daily image generation allowance for commercial users. Generate the image there, save it locally, insert it into your document. Slower than in-app generation but bypasses every desktop-app failure cause.
  • Microsoft Designer (designer.microsoft.com) for image generation — same DALL-E 3 backend, different surface, often more permissive UI for iterating on prompts and styles before committing.
  • The PowerPoint Designer Editor for image editing — added across March and April 2026 — which provides AI-powered editing of existing images (resolution improvement, background removal, generative element moves) inside PowerPoint without requiring image generation specifically. If your need is to refine an existing image rather than generate a new one, this path works on licences and configurations where pure generation fails.
  • Generate elsewhere, refine in Designer Editor. A practical hybrid for organisations whose tenants have generation disabled but image editing permitted: produce the base image at copilot.microsoft.com or designer.microsoft.com, drop it into PowerPoint, then use the Designer Editor for in-context refinement. This pattern is now the most reliable workflow for organisations in regulated industries where generative content has been restricted but editing of existing images hasn’t.

The Designer-pane behaviour and the PowerPoint Designer Editor failures each have their own specific failure patterns, covered in detail in the PowerPoint-specific Copilot failures guide. When the issue is specifically that generated images look wrong or don’t match the prompt rather than failing to generate at all, the diagnosis for Word’s image generation quality issues is different and worth checking. And if you’re hitting Copilot image features specifically in Outlook — Classic or the New Outlook — the AI image features there are a separate moving target.

The honest summary as of May 2026: Copilot image generation works reliably when you have a Premium licence, an active account that holds that licence, a cloud-saved document, a content-policy-safe prompt, and a permissive tenant configuration. The number of independent things that have to be true is the reason failure cases are so common. None of them are bugs in the strict sense. They are configuration boundaries, and once you know what the boundaries are, the failures become predictable.

Expect the boundaries themselves to shift over the next several quarters. Microsoft’s roadmap suggests further consolidation of in-app and chat surfaces, additional Anthropic-model agents arriving across Word, PowerPoint, and Excel, and ongoing regional rollout work. The structural causes covered here — licensing, account, file location, policy, region — are the durable ones. The specific menu paths and feature names will move.