{"title":"Managing updates in the Business Central admin center","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/tenant-admin-center-update-management/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-update-management, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-update-management","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Use the Business Central administration center to manage environment updates, including setting update windows and update dates.","date":"2026-11-13","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Managing updates in the Business Central admin center","slug":"managing-updates-in-the-business-central-admin-center","at":0,"chars":11731},{"level":2,"title":"Set the update window for each environment","slug":"set-the-update-window-for-each-environment","at":1111,"chars":1774},{"level":2,"title":"Schedule an update","slug":"schedule-an-update","at":2885,"chars":5415},{"level":3,"title":"Schedule an update to an available version","slug":"schedule-an-update-to-an-available-version","at":4165,"chars":2564},{"level":3,"title":"Schedule an update to a planned version","slug":"schedule-an-update-to-a-planned-version","at":6729,"chars":1571},{"level":2,"title":"Cancel a running update","slug":"cancel-a-running-update","at":8300,"chars":940},{"level":2,"title":"Get notified of updates","slug":"get-notified-of-updates","at":9240,"chars":595},{"level":2,"title":"Environments that can't get updated","slug":"environments-that-cant-get-updated","at":9835,"chars":1397},{"level":2,"title":"Related information","slug":"related-information","at":11232,"chars":499}],"text":"# Managing updates in the Business Central admin center\nBusiness Central environments follow a set update schedule to deliver new functionality, improvements, and bug fixes. There are two major update cycles each year, starting in April and October, with minor updates in other months. See Major Updates and Minor Updates<update-rollout-timeline>. Refer to the Microsoft Copilot Roadmap<https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=%5B%22Dynamics+365+Business+Central%22%5D#Roadmap> for an overview of new and upcoming functionality. To learn about new functionality, bug fixes, and improvements in recent versions, see What's new or changed<../whatsnew/overview>.\nMicrosoft manages updates for the application and platform. As an internal admin or partner, use the Business Central administration center to specify the timing of updates for each environment and identify who receives notifications when an update is available<#notify>. Prepare your solution and users by creating preview environments to get familiar with new product functionality. See Update cycles<update-rollout-timeline>.\n## Set the update window for each environment\nThe update window for an environment defines the hours during the day for the selected time zone in which the environment can be updated. When an update is rolling out, it's applied to an environment within the time frame that the update window defines.\n> IMPORTANT\n> Updates always start during the update window specified for the environment, but not necessarily right at the start of the update window. Updates that fail to complete before the end of the update window are canceled to ensure the environment is operational during business hours. The update is automatically rescheduled seven days later and notification recipients<#notify> are informed.\nThis window helps ensure updates are applied outside of the normal business hours of the organization. Every environment has a default update window that's between 8:00 PM and 6:00 AM local time for the environment's country/region. In countries/regions that have multiple time zones, the system sets a time zone that's close to the geographic center of the country/region as default.\n> NOTE\n> Desktop users who are signed in to the environment during the update receive an alert in Business Central before the update starts.\nTo change the update window for an environment:\n1. On the Environments tab of the Business Central administration center, select the Name of the relevant environment to open the environment details.\n1. Under Update Settings, select Modify next to Update window.\n1. In the Set update window pane, specify the time zone, start time, and end time, for the update window for the environment. The update window must be a minimum of six hours.\n1. Select Save.\nThis timeslot now becomes the default window when updates are applied to this environment.\n## Schedule an update\nAdmins can schedule environment updates to any version higher than the current environment version within the environment's current or next major version from the Business Central administration center, even if the chosen version isn't available yet.\nThe following fields on the environment page can help you plan the update:\nField|Description\nLatest Available Version|Specifies the latest version you can update your environment to.\nNext Update|Specifies the target version and date for the environment's next update. If the target version isn't available, the date is scheduled when the target version becomes available.\nUpdate window (time zone + UTC offset)|Specifies the hours of the day when an update runs. The time zone and its offset from UTC are indicated in parentheses.\nWhen the scheduled update date arrives, the update runs automatically within the update window you specify for this environment. During the update, all users and sign-in attempts to the environment are blocked with the message `Service is under maintenance`.\n> IMPORTANT\n> The update duration differs depending on the environment. We strongly recommend scheduling the update for a date when it's acceptable for the environment to be inaccessible until the update window ends.\n### Schedule an update to an available version\nAvailable versions are versions released by Microsoft and ready for environments to update to. Notification recipients<tenant-admin-center-notifications> get an email notification when a new version is available.\nTo schedule an update:\n1. On the Environments tab of the Business Central administration center, select the Name of the relevant environment to open the environment details.\n1. Under Update Settings, select the Modify action for Next Update.\n1. In the Schedule Environment Update pane, select target version marked as Available.\n> NOTE\n> During preview periods, a target version marked as Preview appears in the list of available versions for sandbox environments. Ensure you're familiar with the limitations of preview-environments before scheduling an update to a preview version.\n> Notification recipients registered in the Business Central administration center don't receive email notifications regarding availability of a new preview version or execution of an environment update to a preview version (scheduled, succeeded, or failed update). Use the Operations page in the Business Central administration center to view details on an environment update to a preview version.\n1. Pick a date within the update-rollout-timeline#update-period for the environment's current major version to schedule the update for.\n> NOTE\n> If today's update window already ended, you can't schedule an update for today while keeping that window. Select a later date or adjust the update window.\n> For example, at 6 PM, you can't schedule an update for today with an update window of 1 AM-7 AM. Select tomorrow to use the next day's window.\n> To start an update immediately, schedule it for the current date and set Allow the update to run outside the update window to Yes. If an update is scheduled for the same day, this option lets the update start immediately and allows large updates to run for longer than 24 hours if needed. Updates running in this mode aren't automatically canceled when the update window ends. Avoid using this setting for environments that must be available for users by a specific time.\n1. Select Schedule Update.\n> NOTE\n> The chosen date for a target version remains the same even if the target version and date for an environment's next update change later. If an update succeeds and the next update scheduled by Microsoft is for a target version with a previously selected date, that date is used for the next update instead of the default seven days after the previous update finishes.\n### Schedule an update to a planned version\nPlanned versions are versions that Microsoft didn't release yet. Administrators can select planned versions within the current and next major version of the environment as the next update. This way, Microsoft doesn't schedule updates on the environment until the chosen planned version is available. A few days after the chosen version is available, the update is scheduled for a date at least seven days later automatically. Notification recipients<tenant-admin-center-notifications> receive an email notification when a new version is available and another when the update is scheduled for the environment. Administrators can change the update date after it's scheduled by following the instructions under Schedule an update to an available version.\nTo schedule an update to a planned version:\n1. On the Environments tab of the Business Central administration center, select the Name of the relevant environment to open the environment details.\n1. Under Update Settings, select the Modify action for Next Update.\n1. In the Schedule Environment Update pane, select the planned target version. Each planned version indicates the month when the version is expected to be available.\n1. Select Schedule Update.\n> NOTE\n> Only versions planned for release during the update-rollout-timeline#update-period of the environment's current major version can be selected. For example, you can't select planned version 26.5 for an environment on 25.x, because 26.5 releases in September 2025 and the 25.x update period ends in August 2025.\n## Cancel a running update\nRunning updates are canceled automatically if the update doesn't succeed before the end of the update window set for the environment. If you need to cancel an update before the end of the update window or an update that can run outside the environment's update window, you can do so manually. To cancel a running update, navigate to the Operation Details pane from the Environment Details or Operations page and select the Cancel update button next to the operation status.\nCanceling a running update stops the update process and restores the environment to its state immediately before the update started. Depending on the size of the environment database, this process might take more than an hour, during which the environment isn't accessible.\n> NOTE\n> Updates can't be canceled on environments that are in the Enforced Update Period<update-rollout-timeline> for the source version of the environment update.\n## Get notified of updates\nA notification is sent to all notification recipients that are listed on the Notification recipients tab of the Business Central administration center whenever a new version becomes available and whenever an update is scheduled for your environment. See Managing Tenant Notifications<tenant-admin-center-notifications>.\n> IMPORTANT\n> To not miss update notifications from Microsoft, you must verify that the emails are not redirected to a spam folder by your email software. The notifications are sent from the Microsoft account, `no-reply-dynamics365@microsoft.com`.\n## Environments that can't get updated\nSometimes an environment can't get the new update. For example, a per-tenant extension might conflict with the changes in the new version of the base application.\nBefore a major update, Microsoft routinely checks per-tenant extensions in all existing environments for compatibility with the next major update. If we detect compatibility issues with the upcoming version, we send email notifications that describe the detected issues to the notification recipients. We warmly encourage all admins to review these emails and take action as soon as possible.\nIf you discover any such problems, apply the changes to your solution as usual by using Visual Studio Code. Test the new app in a sandbox environment that runs on the new major version, either in preview or the official version. If tests complete successfully, upload the new PTE version for your environment, setting the Deployment Schedule field to Next major. This way, the compatible version of your app is used when your environment is updated. See ../developer/devenv-deploy-tenant-customization.\nIf there's a conflict between a per-tenant extension and a Marketplace app, you might need to clear the schema of the PTE to allow the Marketplace app to take over. See ../upgrade/upgrade-pte-merge-conflict#clashes-between-a-pte-and-a-marketplace-app.\nSee update-rollout-timeline#completed-updates.\n## Related information\nWhat's new or changed in Business Central<../whatsnew/overview>\nMajor Updates of Business Central Online<update-rollout-timeline>\nPrepare for major updates with preview environments<preview-environments>\nWorking with Administration Tools<administration>\nThe Business Central Administration Center<tenant-admin-center>\nManaging Environments<tenant-admin-center-environments>\nManaging Tenant Notifications<tenant-admin-center-notifications>\nitpro-introduction-to-automation-apis"}