Agents, connectors and prompts must move safely from dev to production. What do you define?
Why D is the answer
An ALM process covering environments and deployment
ALM for Copilot Studio agents, connectors and actions is a named responsibility. Editing production directly removes testing and rollback.
In detail
- An ALM process defines how changes move through environments.
- Keep connections separate per environment.
Use case
An illustrative scenario, not a real incident.
A maker edits an agent in production and breaks it for everyone. With ALM, the change goes through test first, and rollback is possible.
See it in different ways
flowchart LR A["Dev: unmanaged solution"] --> B["Export as managed"] B --> C["Test"] C --> D["Production"]
sequenceDiagram participant D as Dev participant T as Test participant P as Production D->>D: Unmanaged solution D->>T: Export as managed T->>P: Import after approval P->>P: Audit trail of the change
flowchart LR S0["Dev"] --> S1["Test"] --> S2["Production"]
Key point: Agents need ALM like other software.
Why the other options are wrong
- A. A rule that only one agent may exist per environment
- Agent count has nothing to do with ALM.
- B. A shared login that all makers use to publish changes
- A shared login loses accountability.
- C. Direct edits in the production environment, reviewed weekly
- Direct production edits are risky and hard to trace.