Skip to content

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

  1. Navigate to the Message center and configure notification preferences.
  2. Set up alerts for Copilot-related updates:
  3. Filter by service: Microsoft 365 Copilot
  4. Include categories: Plan for change, Stay informed, Prevent or fix issues
  5. Include tags such as Major update, Retirement, and Deferred feature where relevant
  6. Add notification recipients: IT operations, compliance team, governance committee.
  7. Configure a weekly digest email summarizing upcoming Copilot changes.
  8. 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

  1. Configure the release preferences:
  2. Targeted release for selected users — recommended for FSI environments
  3. Assign the pilot/validation group to receive new Copilot features first
  4. This allows the governance team to evaluate new features before organization-wide rollout.
  5. Document the validation period (minimum 2 weeks recommended before general release).
  6. For Copilot major updates that are deferred-capable, navigate to Copilot > Settings > All Settings > Copilot release preferences: General Availability.
  7. Choose Standard Release or Deferred Release for the default audience and configure user or security-group exceptions for the validation group.
  8. 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.
  9. 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

  1. Define the Change Advisory Board (CAB) composition for Copilot changes:
  2. IT operations representative
  3. Information security representative
  4. Compliance representative
  5. Business stakeholder representative
  6. Establish a CAB review cadence (weekly during active rollout, monthly for steady state).
  7. Define change categories and approval requirements:
  8. Standard changes — Pre-approved, documented procedures (e.g., adding users to Copilot groups)
  9. Normal changes — CAB review required (e.g., enabling new Copilot features)
  10. 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

  1. Create a standard impact assessment template for Copilot changes:
  2. Change description and business justification
  3. Regulatory impact assessment (does this change affect any compliance controls?)
  4. Security impact assessment (does this change affect data protection?)
  5. User impact assessment (training requirements, workflow changes)
  6. Rollback plan (how to revert if issues are discovered)
  7. Require completion for all Normal and Emergency changes.
  8. 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