Portal Walkthrough: Control 2.10 - Patch Management and System Updates
Last Updated: January 2026 Portal: Microsoft 365 Admin Center, Azure Portal Estimated Time: 2-3 hours for setup
Prerequisites
- Microsoft 365 Admin role
- Power Platform Admin role
- Azure Service Health access (if using Azure services)
Step-by-Step Configuration
Step 1: Subscribe to Message Center
- Open Microsoft 365 Admin Center
- Navigate to Health > Message center
- Configure preferences:
- Email notifications for Power Platform updates
- Email notifications for Copilot Studio updates
- Add AI Governance Lead and Power Platform Admin to recipients
Step 2: Configure Azure Service Health Alerts
- Open Azure Portal
- Navigate to Service Health > Health alerts
- Create alert:
- Services: Power Platform, Azure Key Vault, Application Insights
- Event types: Service issues, Planned maintenance
- Notification: Operations team email and SMS
Step 3: Establish Test Environment
- Create non-production environment in PPAC:
- Name:
FSI-Update-Testing - Type: Sandbox
- Mirror production configuration
- Deploy production agent copy for testing
- Create baseline test suite
Step 4: Define Maintenance Windows
- Document maintenance windows by zone:
- Zone 1: Anytime with notification
- Zone 2: Weekends preferred, 48-hour notice
- Zone 3: Scheduled windows only, change approval required
- Communicate windows to stakeholders
Step 5: Create Patch Documentation Process
- Create SharePoint library for patch documentation
- Create template for patch assessment:
- Update description
- Impact assessment
- Test results
- Rollback plan
- Approval
Configuration by Governance Level
| Setting | Baseline (Zone 1) | Recommended (Zone 2) | Regulated (Zone 3) |
|---|---|---|---|
| Auto-Updates | Enabled | Controlled | Change-controlled |
| Testing | Optional | Critical updates | All updates |
| Documentation | Basic | Tracked | Full change control |
| Maintenance Window | Flexible | Defined | Strict |
| Rollback Plan | None | Critical updates | All updates |
Validation
After completing these steps, verify:
- Message Center notifications configured
- Service Health alerts trigger correctly
- Test environment mirrors production
- Maintenance windows documented
- Patch history log maintained
Back to Control 2.10 | PowerShell Setup | Verification Testing | Troubleshooting