Today I received the following mail for every cloud customer we :
Subject: We’re temporarily postponing updates to version 23
We’re temporarily postponing updates to version 23.0, and your tenant has one or more environments currently scheduled to receive this update.
If you have an environment scheduled to receive an update while updates are postponed, your environment will not be updated automatically, but will be rescheduled to seven days after the originally scheduled date.
You can manage the scheduling of environment updates from the Dynamics 365 Business Central admin center.
I checked my mailbox and also found
- We are temporarily postponing updates to version 22.0
- We are temporarily postponing updates to version 21.0
- We are temporarily postponing updates for version 20.5
To avoid problems with upgrades, you should test your upgrades before releasing them to the general public. You don't specify why this is happening and taking our customer, I notice that leaves a bad impression of Business Central and how Microsoft handles quality of major updates.
How about take a copy 10% of cloud databases, put them in an isolated service tier so that nothing can communicate to the outside? And only if all succeed, release this update in 3 update rings (First < 20%, Fast < 40% and Broad 100% (=all) ).