Copilot Studio Friction
After import: authentication, icon and channels are gone
Last verified
Details & related
Assessment
- Confidence
- Confirmed officialConfirmed by Microsoft documentation or an official statement.
- Severity
- Blocking
- Typical time lost
- Hours
Identification
Verification & changes
Verified
Doc check by human: Official solution and authentication documentation plus MVP analysis re-read during seed migration; documented import gaps unchanged.
Change
Provisionally approved by the Product Owner; external LLM quality review pending.
Change
Initial record created from the seed dossier (migration wave 1).
Are you in the right place?
- You imported your agent as a Power Platform solution, and the import reported success.
- The agent's user authentication settings are empty or back to defaults.
- The agent's icon is gone, and its channel list is empty.
- You can't share the agent with users.
- The agent itself opens and answers in the test pane.
If instead the imported agent answers nothing at all → see Import succeeded — but the agent answers nothing. If instead the export already failed or shipped incomplete → see Solution export fails or misses components.
What's happening
The solution format does not carry everything your agent needs in order to run for real users. Microsoft's solution documentation lists the gaps openly (documented as of 2026-07-08). Imported agents can lose their icon and channel details. User authentication must be reconfigured after import. And the agent must be published again in the target environment before it can be shared. The import is like moving a shop into a new building. The shelves arrive, but the keys, the sign, and the opening hours need setting up again. None of this is announced during the import — the pieces are silently missing until a user hits them.
For technicians
The documented post-import sequence is fixed: authentication → channels → publish → share. Sharing stays blocked until the agent has been published in the target environment. Related documented mines: removing an agent from a solution does not remove its components, and managed solutions cannot be exported. An MVP analysis adds the framing: publish is a channel push, not a deployment. It carries no release management of its own.
How to fix it
Solution 1
Official workaroundRun the post-import sequence — auth, channels, publish, share
- Open the imported agent in the target environment.
- Reconfigure user authentication in the agent's settings, using the target environment's own values.
✅ You should now see: your authentication provider saved without validation errors.
- Restore the agent's icon and display details.
- Open the channel configuration and reconnect every channel you used before.
- Publish the agent.
✅ You should now see: a publish confirmation with a fresh timestamp.
- Share the agent with your users.
✅ You should now see: the share dialog completing without errors.
Check that it worked
Ask a colleague from the target audience to open the agent in the shared channel. Expected: sign-in works, and the agent answers.
If it didn't work
- The channel serves an old version. Propagation delay is suspect number one. See Teams answers with an old version of your agent.
- Sharing is still blocked. Sharing requires a successful publish in the target environment; verify the publish status first.
- Authentication errors persist. Check that you entered the target environment's own credentials, not values copied from development.
- Knowledge answers are missing too. See Import succeeded — but the agent answers nothing.
Prevent it next time
- Treat "auth → channels → publish → share" as a fixed checklist, part of the ALM ritual.
- Never sign off a deployment on the import success message; verify the runtime pieces yourself.
- After the post-import publish, follow the publish ritual before judging channel behavior.
Evidence
Official documentationlearn.microsoft.com
The official solution documentation states imported agents can lose icon and channel details, and that authentication must be reconfigured and the agent republished before sharing.
Official documentationlearn.microsoft.com
Official guidance for configuring end-user authentication, the step that must be repeated in the target environment after import.
MVP blogm365princess.com
An MVP analysis frames the underlying issue: publish is a channel push, not a deployment, so makers must not treat import plus publish as a finished release.