PowerLeap Logo

Copilot Studio Friction

Get notified when this record changes

One email when the status or the fix changes — double opt-in, no tracking, unsubscribe in every email.

Solution export fails or misses components

Mitigatedsince 8 July 2026

Last verified

Details & related

Assessment

Confidence
Confirmed officialConfirmed by Microsoft documentation or an official statement.
Severity
Blocking
Typical time lost
Hours

Identification

ALM & deployment

Verification & changes

  1. Verified

    Doc check by human: Official solution export/import documentation and practitioner deep dive re-read during seed migration; export blockers and non-auto-added components still documented.

  2. Change

    Provisionally approved by the Product Owner; external LLM quality review pending.

  3. Change

    Initial record created from the seed dossier (migration wave 1).

Related

Are you in the right place?

  • You export your agent as a Power Platform solution, and the export fails with an error.
  • Or the export succeeds, but the imported agent is missing knowledge, flows, or prompts.
  • One or more of your topic names contain dots.
  • The solution looks complete at export time but arrives incomplete in the target environment.

If instead the import succeeded but the agent answers nothing → see Import succeeded — but the agent answers nothing. If instead authentication, icon and channels are missing after import → see After import: authentication, icon and channels are gone. If you can't export at all because the solution is managed → (record planned).

What's happening

Cause 1: A dot in a topic name. One dot blocks the whole solution's export (documented as of 2026-07-08). Nothing warns you while naming the topic. The failure only appears at export time, and the error does not point at the topic.

Cause 2: Components don't add themselves. Copilot Studio adds topics, entities, and connector references to your solution automatically. Knowledge sources, agent flows, prompts, connected agents, and evaluation test sets are not added automatically (documented as of 2026-07-08). The export then succeeds — and ships a torso. Think of a moving company that loads the furniture but leaves every unlabeled box behind. The "Add Required Objects" command exists exactly for this, and it must run before every export.

For technicians

The distinction is between components Dataverse tracks as solution dependencies and components it does not. Removing an agent from a solution does not remove the agent's components either. Managed solutions cannot be exported at all — that is by design; keep an unmanaged solution in development.

How to fix it

Solution 1

Official workaround

Clean topic names, then run "Add Required Objects"

  1. Open the solution that contains your agent.
  2. Rename every topic whose name contains a dot.
  3. Select the agent inside the solution.
  4. Run "Add Required Objects".
  5. Check that knowledge sources, agent flows, prompts, and connected agents now appear as solution components.

✅ You should now see: the previously missing components listed inside the solution.

  1. Export the solution again.

✅ You should now see: the export completing without errors.

Check that it worked

Import the exported solution into your test environment. Compare the imported agent against the source: knowledge, flows, prompts, connected agents. Expected: every component is present by name. Presence by name is not the whole story for knowledge. Run the check in Import succeeded — but the agent answers nothing too.

If it didn't work

  • The export still fails. Search every topic name again for dots, including copied and disabled topics.
  • Components went missing again. "Add Required Objects" is not remembered; run it before every export.
  • Knowledge arrived by name but answers nothing. See Import succeeded — but the agent answers nothing.
  • The solution is managed. Managed solutions can't be exported by design; create a new unmanaged solution (record planned).

Prevent it next time

  • Adopt a topic naming convention without dots from day one.
  • Make "Add Required Objects" a non-negotiable step of the ALM ritual before every export.
  • Keep development unmanaged; deploy managed only toward test and production.

Evidence

  • Official documentationlearn.microsoft.com

    The official solution documentation lists export blockers, including dots in topic names preventing the export of the whole solution.

  • Official documentationlearn.microsoft.com

    Official guidance covers which components belong to a solution and how required objects must be added.

  • MVP blogharrytraynor.io

    A practitioner documents that knowledge sources, agent flows, prompts, connected agents, and evaluation test sets are not added to a solution automatically.