Pattern
ALM ritual for solution export and import
Solution exports that fail and imported agents that arrive broken, because components, authentication, and channels do not travel automatically.
Last reviewed 8 July 2026
The pattern
Treat every Power Platform solution export and import as a fixed ritual with a before part and an after part. Before every export, clean up topic names and run "Add Required Objects". A dot in a topic name blocks the export of the whole solution. Knowledge sources, agent flows, prompts, and connected agents are not added automatically. Export unmanaged from your development environment; import managed toward test and production. After every import: reconfigure authentication, check the channels, publish, and only then share.
When to use it
- Before every solution export, however small the change.
- After every solution import into a test or production environment.
- When an imported agent opens fine but answers nothing.
Steps
- Rename topics so that no topic name contains a dot.
- Open the solution and run "Add Required Objects".
- Verify that knowledge sources, agent flows, prompts, and connected agents are listed in the solution.
- Export the solution as unmanaged from development, as managed toward test and production.
- Keep the unmanaged original in development; a managed solution cannot be exported again.
- After the import, reconfigure the user authentication.
- Check every channel; icon and channel details can get lost on import.
- Publish the agent.
- Share the agent only after the publish succeeded.
- Ask one test question the agent must answer from its knowledge. Uploaded knowledge does not travel with the solution and must be reprocessed in the target environment.