BC Observatoryunofficial, made by waldo
community postAdministration & Setupcommunity - not Microsoftreviewed - checked by Opus

Quick Tip: Almost Every BC Major Release Gets Paused. Are Your Environments Ready?

Business Central major release rollouts get paused frequently due to discovered issues, and this is normal process design since 2020. Environments already upgraded before a pause cannot be rolled back, but those not yet upgraded get rescheduled safely. Partners should schedule production updates late in the window, configure notification recipients, and test in sandboxes to manage the risk effectively.

Open in Claude7930.md

post think about IT

Steven Renders · 2026-05-20 · 965 words · about 4 min

"The question is not whether a pause will happen, but whether your environments are in a good position when it does."
Show the post hereRead on think about IT

Key points

  • Rollout pauses have occurred with nearly every BC major release since BC17, including BC28, BC25, BC24, BC23, and BC22.
  • Environments upgraded before a pause remains on the new version with the issue, while unupgraded environments are held and rescheduled without losing time.
  • Common problems occur when partners schedule production early, skip notification configuration, or omit sandbox testing before the production update.
  • Configuring notification recipients and testing in sandbox copies beforehand are the key preventative practices available to partners.

Quotes

  • “The question is not whether a pause will happen, but whether your environments are in a good position when it does.” (This frames the rollout pause as inevitable, shifting focus to preparation rather than prevention.)
  • “Environments already upgraded before the pause was called are not rolled back. They stay on the new version with whatever issue triggered the pause.” (This is the critical risk: early adopters cannot be protected after a pause is declared, making scheduling timing essential.)

Context

  • Features: staged rollout, update postponement, admin center notifications, sandbox testing, update scheduling, notification recipients
  • Versions: BC28, BC25, BC24, BC23, BC22, BC17

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.