Control 4.12: Change Management for Copilot Feature Rollouts — Portal Walkthrough
Step-by-step portal configuration for establishing change management processes governing the rollout of new Copilot features, updates, and configuration changes in financial services environments.
Prerequisites
- Role: Global Administrator for legacy Targeted release; Office Apps Admin, Security Admin, or AI Admin for Copilot Standard/Deferred release preferences; Message center reader or another eligible Microsoft 365 admin role for Message Center monitoring. Verify role availability and tenant UI access in the target tenant.
- License: Microsoft 365 E5 with Copilot add-on
- Access: Microsoft 365 Admin Center, Microsoft 365 Message Center
Steps
Step 1: Configure Microsoft 365 Message Center Monitoring
Portal: Microsoft 365 Admin Center Path: Health > Message center > Preferences
- Navigate to the Message center and configure notification preferences.
- Set up alerts for Copilot-related updates:
- Filter by service: Microsoft 365 Copilot
- Include categories: Plan for change, Stay informed, Prevent or fix issues
- Include tags such as Major update, Retirement, and Deferred feature where relevant
- Add notification recipients: IT operations, compliance team, governance committee.
- Configure a weekly digest email summarizing upcoming Copilot changes.
- Verify in your tenant that Message center preferences, weekly digest settings,
Status for your org, and Deferred feature tags are visible to the intended admin roles.
Step 2: Configure Release Preferences for Change Validation
Portal: Microsoft 365 Admin Center Path: Settings > Org Setting > Organization profile > Release preferences
- Configure the release preferences:
- Targeted release for selected users — recommended for FSI environments
- Assign the pilot/validation group to receive new Copilot features first
- This allows the governance team to evaluate new features before organization-wide rollout.
- Document the validation period (minimum 2 weeks recommended before general release).
- For Copilot major updates that are deferred-capable, navigate to Copilot > Settings > All Settings > Copilot release preferences: General Availability.
- Choose Standard Release or Deferred Release for the default audience and configure user or security-group exceptions for the validation group.
- Document whether the validation group receives Copilot deferred-capable updates through Standard Release while production users remain Deferred, or through Targeted Release where modern release preferences do not apply.
- Verify in your tenant that these paths and controls are available for the cloud environment and roles used for evidence collection.
Step 3: Establish Change Advisory Board Process
Portal: Internal governance documentation Path: Change management procedures
- Define the Change Advisory Board (CAB) composition for Copilot changes:
- IT operations representative
- Information security representative
- Compliance representative
- Business stakeholder representative
- Establish a CAB review cadence (weekly during active rollout, monthly for steady state).
- Define change categories and approval requirements:
- Standard changes — Pre-approved, documented procedures (e.g., adding users to Copilot groups)
- Normal changes — CAB review required (e.g., enabling new Copilot features)
- Emergency changes — Expedited approval path (e.g., disabling a feature due to compliance concern)
Step 4: Create Change Impact Assessment Template
Portal: Internal documentation Path: Change management templates
- Create a standard impact assessment template for Copilot changes:
- Change description and business justification
- Regulatory impact assessment (does this change affect any compliance controls?)
- Security impact assessment (does this change affect data protection?)
- User impact assessment (training requirements, workflow changes)
- Rollback plan (how to revert if issues are discovered)
- Require completion for all Normal and Emergency changes.
- Archive completed assessments for audit evidence.
FSI Recommendations
| Setting | Baseline | Recommended | Regulated |
|---|---|---|---|
| Release channel | Standard | Targeted release or Copilot Standard/Deferred validation group | Targeted release or Copilot Standard/Deferred with CAB |
| Change review process | Ad hoc | Weekly CAB review | CAB review per change |
| Validation period | None | 2 weeks | 4 weeks |
| Impact assessment | Optional | Required for feature changes | Required for all changes |
Regulatory Alignment
- FFIEC Operations Booklet — Supports compliance with change management requirements for IT systems
- 12 CFR part 30, appendix D (OCC Heightened Standards) — Helps meet expectations for controlled technology changes
- SOX Section 404 — Supports change management controls for systems affecting financial reporting
Next Steps
- Proceed to PowerShell Setup for change management automation
- See Verification & Testing to validate change management processes
- Back to Control 4.12