When you ask Microsoft Copilot to generate an image, the prompt does not go directly to an image generator. Instead, Copilot uses a process called prompt routing to decide which service should handle your request. This routing logic determines whether your prompt is sent to the built-in Designer image generation engine or to a third-party plugin. Understanding how prompt routing works helps you get the image you want faster and avoid unexpected results. This article explains the routing mechanism, the conditions that trigger each destination, and what to do when the wrong service handles your prompt.
Key Takeaways: How Prompt Routing Controls Image Generation
- Copilot > Image generation icon: Triggers the Designer engine automatically when the prompt contains visual keywords like “draw,” “create an image of,” or “generate a picture.”
- Copilot > Plugins > Plugin name: If a third-party image plugin is enabled, Copilot routes the prompt to that plugin instead of Designer when the plugin matches the request context.
- Copilot > Settings > Plugins > Toggle off: Disabling third-party image plugins forces all image prompts to the Designer engine for consistent results.
Why Prompt Routing Exists in Copilot Image Generation
Microsoft Copilot does not have its own image generation model. Instead, it integrates with multiple image generation services through a plugin architecture. The primary service is Microsoft Designer, which uses the DALL-E model from OpenAI. Third-party plugins, such as those from Adobe or other providers, can also be connected to Copilot. Prompt routing is the logic that decides which service receives your request. The goal is to send the prompt to the service best suited for the task. For example, if you ask for a photo-realistic product shot, Designer handles it well. If you ask for a vector illustration with specific brand colors, a plugin like Adobe Firefly might be the better choice. Copilot evaluates the prompt text, the active plugins, and the user’s tenant configuration to make this decision. The routing is not visible to the user by default. You only see the final image output, not which service generated it. This can lead to confusion when the output does not match your expectation. Knowing the routing criteria helps you write prompts that reach the correct service.
When Copilot Routes to Microsoft Designer
Copilot sends prompts to the Designer engine under these conditions:
- The prompt contains explicit image generation language such as “draw,” “create an image,” “generate a picture,” or “make a photo.”
- No third-party image generation plugins are enabled in the Copilot settings.
- The prompt does not reference a specific plugin name or brand.
- The user is in a Microsoft 365 app like Word, PowerPoint, or Teams where Designer is the default image service.
Designer supports photorealistic images, digital art, and illustrations. It returns four variations per prompt by default. The output resolution is 1024×1024 pixels.
When Copilot Routes to a Third-Party Plugin
Copilot routes the prompt to a third-party plugin when:
- A plugin for image generation is enabled in Copilot settings under Plugins.
- The prompt includes the plugin name, for example “use Adobe Firefly to create.”
- The plugin is configured as the default image service by an administrator in the Microsoft 365 admin center.
Plugins have their own capabilities, licensing, and output formats. Some plugins require a separate subscription. The routing logic checks the plugin’s availability before sending the prompt. If the plugin is not available, Copilot falls back to Designer.
Steps to Control Where Your Image Prompt Goes
You can influence prompt routing by adjusting settings and writing prompts with specific instructions. Follow these steps to ensure your prompt reaches the service you want.
Force Routing to Microsoft Designer
- Open Copilot in your Microsoft 365 app
Click the Copilot icon in the ribbon of Word, PowerPoint, or Microsoft 365 Chat. The Copilot pane opens on the right side of the screen. - Open the Plugins menu
Click the Plugins icon in the Copilot pane. It looks like a puzzle piece. A list of all enabled plugins appears. - Disable third-party image plugins
Toggle off any plugin that mentions image generation, such as Adobe Firefly or any other third-party image service. Only Microsoft Designer should remain active. If you have no third-party plugins enabled, skip this step. - Write an image prompt with visual keywords
Type a prompt that starts with “Draw,” “Create an image of,” or “Generate a picture.” For example: “Create an image of a modern office with plants and natural light.” Press Enter. - Verify the output source
After the image appears, check the bottom of the image card. It should say “Generated with Microsoft Designer.” If it shows a different source, return to the Plugins menu and ensure no third-party image plugins are enabled.
Force Routing to a Third-Party Plugin
- Enable the desired plugin
Open the Plugins menu in the Copilot pane. Find the third-party image generation plugin you want to use. Toggle it on. If the plugin requires a subscription, sign in or activate it first. - Reference the plugin in your prompt
Write a prompt that includes the plugin name. For example: “Use Adobe Firefly to create a vector illustration of a mountain landscape.” Do not use visual keywords like “draw” or “create an image” without the plugin name, as Copilot may still route to Designer. - Check the output source
After the image appears, look at the bottom of the image card. It should show the plugin name as the source. If it shows Designer, the plugin did not handle the prompt. Repeat step 2 with a clearer plugin reference.
If Copilot Routes to the Wrong Service
Even with correct settings, prompt routing can fail. Here are common problems and how to fix them.
Copilot Sends the Prompt to Designer When You Want a Plugin
This happens when the prompt lacks a specific plugin reference. Copilot sees a generic image request and routes it to Designer. To fix this, rewrite the prompt to include the plugin name at the beginning. For example: “Adobe Firefly: Generate a logo for a coffee shop.” The colon or dash after the plugin name helps Copilot parse the instruction. Also confirm the plugin is toggled on and has an active subscription.
Copilot Sends the Prompt to a Plugin When You Want Designer
This happens when a third-party image plugin is enabled and the prompt contains language that matches the plugin’s trigger words. For example, the prompt “Design a brochure cover” might trigger a plugin if the plugin is configured for design tasks. To fix this, disable all third-party image plugins in the Plugins menu. Then write the prompt again. If the plugin is managed by an administrator and cannot be disabled, contact your IT admin to remove the plugin from the Copilot configuration.
Copilot Returns Text Instead of an Image
This happens when the prompt does not contain visual keywords and no image generation plugin is active. Copilot treats the request as a text query. To fix this, add a visual keyword such as “draw” or “generate an image of” at the start of the prompt. Also verify that at least one image generation service is active in the Plugins menu.
| Item | Microsoft Designer | Third-Party Plugin |
|---|---|---|
| Default routing trigger | Visual keywords like “draw” or “create an image” | Plugin name in prompt or plugin set as default |
| Requires subscription | Included with Microsoft 365 Copilot license | Often requires separate subscription |
| Output resolution | 1024×1024 pixels | Varies by plugin |
| Number of variations per prompt | Four | Varies by plugin |
| Admin control | Always available unless disabled by policy | Must be enabled in admin center |
You now understand how prompt routing works for image generation in Copilot. Use the Plugins menu to enable or disable services based on your task. Write prompts with explicit service names to bypass routing logic. For consistent results with Designer, keep third-party image plugins turned off. For advanced workflows, test both services and compare output quality before choosing a default.