Britta is an ALM administrator promoting a Copilot Studio agent from the development environment to production. The team uses managed solutions for production deployments. After importing the managed solution, a developer in production reports they cannot edit the agent's system topic 'Greeting' directly in the production environment. Is this the expected behavior, and why?

Power Platform application lifecycle management distinguishes between managed and unmanaged solutions with a key design principle: managed solutions protect production environments from ad-hoc changes.

The correct explanation is that this is expected behavior. Managed solutions lock components so they cannot be edited directly in the target environment, and changes must be made in the source development environment and re-promoted through the pipeline. When a managed solution is imported into a target environment such as test or production, all components within it — including system topics, custom topics, entities, and variables — are locked for editing. This is by design. The intent is to enforce a promotion pipeline: developers make changes in the development environment, the solution is exported as managed, and then imported into downstream environments. This prevents configuration drift and ensures what's in production exactly matches what was reviewed and approved.

The claim that this is a bug is incorrect. The inability to edit managed solution components is not a bug — it is a core governance feature. If direct production editing were allowed, it would undermine the entire controlled deployment process.

The claim that this is expected behavior only for system topics is incorrect. Managed solutions lock all components, not just system topics. Custom topics are equally protected. The lock applies to anything packaged inside the managed solution.

The recommendation to convert the managed solution to an unmanaged solution in production is incorrect and dangerous. Converting a managed solution to unmanaged in production is not a supported or recommended workflow. Doing so would break the lifecycle chain, make the solution impossible to update cleanly through the pipeline, and leave production in an unmanaged state that is difficult to govern and roll back.

Exam tip: Always remember managed equals locked in target, unmanaged equals editable. Production should always receive managed solutions. Development environments use unmanaged solutions so developers can iterate freely.