In addition to major and minor upgrades, service upgrades can be performed without a planned date or time.

The service components apply to multiple environments, such as all tenants in a region. So Microsoft schedules those updates to a time when traffic is lower in each region, typically during the evening or night. Typically, these service updates are transparent to any users, as the service is designed to manage traffic in a way that any users still working in Business Central aren't affected by these service updates. These updates don't add or remove functionality, and they're transparent to business users.

However, these updates have an impact on night work businesses as users may receive messages informing them that an administrator has updated the application and that they should restart the application. This can even occur several times in the same night with the resulting impact on user performance and productivity.

The proposal is to establish a specific configuration per customer to implement these updates in a customer specific low traffic time window and not general as it is currently the case. In this way each business can define these specific low traffic hours. Another alternative option would be to create a dual region or group of tenants for companies with night work where the update rules are adapted to this type of business.