Control 4.14: Copilot Studio Agent Lifecycle Governance - Portal Walkthrough
Step-by-step governance workflow for operating the five Copilot Studio agent lifecycle stages: authoring, testing, publishing, versioning, and deprecation. This playbook governs the lifecycle wrapper; intake (Control 1.10), tuning (Control 1.16), and embedded extensibility (Control 4.13) remain owned by their respective controls.
Prerequisites
- Control 1.10 Vendor Risk Management intake gate has cleared the use case before authoring begins.
- Control 4.13 Extensibility Governance covers connectors and plugins embedded in the agent.
- A documented agent register exists, with the inventory fields listed in Control 4.14.
- Approved Copilot Studio environments separated by lifecycle stage (e.g., dev, test, prod) are in place.
Access Paths
| Portal | Path | Why it matters |
|---|---|---|
| Microsoft Copilot Studio | Solutions > Agents | Authoring, testing, publishing, and versioning surface |
| Microsoft Copilot Studio | Agent > Overview > Model | Primary-model selection and release-status evidence |
| Microsoft 365 Admin Center | Agents > All Agents > Registry | Tenant view of available agents, ownership, and governance exceptions |
| Microsoft 365 Admin Center | Copilot > Settings > View all | External AI provider approval |
| Microsoft 365 Admin Center | Copilot > Settings > All Settings > Copilot release preferences: General Availability | Standard/Deferred release assignment for deferred-capable Copilot major updates |
| Power Platform admin center | Environment > Settings > Features | Environment permission for preview/experimental and external models |
| Microsoft AI at Work Roadmap | Copilot Studio / Microsoft Copilot roadmap filters | Forward-looking source for new agent-platform capabilities after the September 2026 release-plan migration |
| Microsoft Purview portal | Audit | Captures publishing, version, and lifecycle events |
| Governance evidence repository | Workspace of record | Stores the agent register and stage-by-stage evidence |
Steps
Step 1: Confirm intake clearance before authoring
Authoring begins only after the Control 1.10 intake decision is recorded. Capture the decision identifier in the agent register so each agent's lifecycle has a documented origin.
Step 2: Operate testing as a gate, not a checkbox
Functional, prompt-injection, content-safety, and connector-boundary tests run in a non-production environment with a test plan and exit criteria. Tests passing is the entry condition for publishing — failing tests block the stage transition.
Step 3: Review the Primary Model Before Publishing
Open the agent's Overview page and record the effective primary model, release type, and cross-geo designation. As of September 22, 2026, GPT-5.5 Chat is the standard-harness default, but the Default alias can be upgraded over time.
- Use a generally available model for production; experimental and preview models are for non-production evaluation.
- Route any cross-geo model through the Control 2.7 residency review.
- For external models, verify the Power Platform environment permits external models and the provider is enabled in the Microsoft 365 admin center.
- Treat a selected-model or default-model change as a lifecycle change requiring risk review and regression testing.
- Verify whether any pending agent-platform capability is a major Copilot update tagged as deferred-capable; if so, record whether the validation group receives it through Standard Release while production remains Deferred.
Step 4: Run the publishing approval workflow
A named approver validates that testing exited cleanly, that an owner of record is named, that audience scope is appropriate, and that any embedded extensibility components are governed under Control 4.13. The approval record enters the agent register.
Before approving availability, review the Agent registry detail page and the AI at Work Roadmap entry for any release-timing, owner, or lifecycle signal that changes the validation plan. Do not rely on historical release-plan pages for new Copilot Studio or Power Platform roadmap items after the September 2026 migration.
Step 5: Apply a versioning policy
Subsequent changes follow a documented versioning policy (recommended: semantic versioning). Each version produces a change-log entry, an approval entry, and a re-test result. Skipping the version record is a supervisory gap under FINRA Rule 3110.
Step 6: Run a deprecation playbook at end of life
Agents reaching end of life follow a deprecation playbook covering user notice, migration guidance, impact assessment, and a final retirement record. Deprecated agents must be removed from runtime surfaces, not left dormant.
Step 7: Periodic lifecycle attestation
Schedule a periodic attestation that every agent in the register has a current owner, a current lifecycle stage, and an in-period review record. Stale attestations are themselves an evidence gap.
FSI Recommendations
| Tier | Recommendation |
|---|---|
| Baseline | Maintain an agent register and capture publishing approval per agent. |
| Recommended | Operate stage-separated environments, require versioned change logs, and run the deprecation playbook for retired agents. |
| Regulated | All Recommended controls plus: independent reviewer sign-off on publishing for high-impact agents, quarterly lifecycle attestation, and a tested deprecation drill. |
Next Steps
- Proceed to PowerShell Setup to inventory agents and pull lifecycle audit evidence.
- Use Verification & Testing to validate stage transitions, approvals, and deprecation.
- Keep Troubleshooting available for register, approval, and deprecation issues.
FSI Copilot Governance Framework v1.8.0 - July 2026 - Back to Control 4.14