How Do I: Manage and Postpone BC Updates in the Admin Center
Managing Business Central SaaS updates in the Admin Center allows you to schedule, delay, and respond to rollout pauses. This matters because environments upgraded to a problematic version cannot be rolled back, while postponement controls and notification setup help you avoid becoming the test cohort for production issues.
post think about IT
Key points
- Two major updates a year plus monthly minor ones roll out in stages, and Microsoft pauses the rollout when a critical issue appears
- Environments upgraded before a pause stay on the faulty version; held environments are rescheduled seven days after their original date
- Configure notification recipients to get emails about new versions, schedules, failures, pauses and per-tenant extension compatibility
- Set an update window of at least six hours outside business hours and pick the update date deliberately, near the end of the allowed period
- Updates can be delayed but not skipped; Microsoft-localized environments get up to five months, partner-localized about 60 days
Context
- Features: Update scheduling, Update window configuration, Notification recipients setup, Rollout pause handling, Version targeting, Update postponement, Environment update control
- Versions: BC28, BC25
Source: think about IT - Steven Renders, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.