Practical guides · Practical guide

How to maintain the validated state of Business Central after updates

An announced Business Central update, a sandbox on another version and a new partner extension can all affect the same workflow. IT and QA need to agree which quality-relevant processes change, what evidence is outstanding and when the solution must be ready. The SME planning example connects Microsoft's update mechanisms with controlled change in human medicinal product GMP.

Table of contents

At a glance

How do you keep Business Central suitable for GMP use after an update?

Record the target version, extensions and affected processes. Assess the impact and test relevant workflows in a suitable environment. Resolve open errors before deciding on operational use, then document the version actually installed. For Business Central Online, plan this work within the available update deadlines. Keeping a cloud version frozen indefinitely is not a viable approach.

  • Online deadlines, maintenance windows, and on-premises installations require different planning.
  • A production copy requires controlled data, test connections, and a verified target state.
  • Compatible apps and a technically successful update do not constitute an appropriate business process.
  • The operational decision includes test results, open defects, limitations, and follow-up inspections.

1. Define operating procedure and specify the exact scope of changes

Start with clear system identity: Online or On-Premises, environment, country version, application version, installed apps, and relevant interfaces. Additionally, note which quality-related tasks occur there. An update may, for example, involve a documented material status, a batch assignment, or handover to a warehouse management system. These examples are test cases for your process, not a guarantee of a specific standard function.

Microsoft manages the update process for online environments. On-premises environments and partners are responsible for organizing the installation. The Microsoft guide for version 28 differentiates between platform and application changes, along with the associated data and extension steps. As a result, there is no general upgrade path applicable to all previous versions. Key considerations remain the starting state, supported target state, and the appropriate installation procedure.

The regulatory reference here is its use in human medicinal product manufacturing. Annex 11 is the GMP guideline for computerised systems and requires controlled changes and risk-based justification. Part 11 must also be assessed when the relevant electronic records or signatures fall within its FDA jurisdiction. An ERP update alone does not establish this jurisdiction.

Sources: [7] [8] [9] [10] [11]

2. Maintain the online calendar with actual deadlines

Microsoft releases two primary versions annually in April and October, along with smaller updates throughout the remaining months. The exact tenant-specific release date cannot be inferred from this schedule. Prepare a calendar outlining available target versions, planned updates, allowable deviation periods, test completion dates, and representation for decision-making. Responsible parties must actually receive and process the notifications.

The documented update cycle for a main version includes five calendar months, followed by a one-month grace period. During this grace period, the date cannot be deferred further. After this period, Microsoft may uninstall incompatible extensions to enable the required update; according to documentation, associated data are not deleted. However, the absence of a branch function remains a significant operational issue.

Therefore, plan an internal decision date before the last technical scope. For critical corrections and underlying service components, additional operating mechanisms apply; not every maintenance waits for your project plan. In the change process, it should be determined who evaluates the impact of short-term information and which minimum controls are required before further use.

Sources: [1] [2] [8]

3. Align maintenance windows and operational interruptions

The online update window is defined per environment with a specified time zone and must encompass a minimum of six hours. It represents an allowable period, not a guaranteed start minute or a committed duration. During the update, user login is disabled. Therefore, shift handovers, ongoing bookings, background technical processes, and partner accessibility must align with the actual update window.

An update not completed within the window will be terminated in the described normal case and rescheduled. The option to allow an update to run outside the window modifies this limitation. It constitutes a deliberate operational decision, particularly when a follow-up step must be available immediately the next morning.

Describe the transition in detail: Until when will new orders be accepted? Which interfaces will be monitored and held in check? Who will verify pending transfers after the update? Document essential backup procedures and subsequent alignment. A telephone on-call support without access, authorization, and clear action instructions does not constitute a valid solution.

Sources: [2] [8]

4. Translate release information into a justified test selection

An impact assessment links every relevant change to a requirement and a potential error. Utilize release information, partner notifications, configuration comparisons, and known incidents. The following work matrix serves as an independent planning aid. It neither specifies a generic test volume nor mandates a complete repetition of all prior inspections.

The selection should also take into account existing control points. If the process remains unchanged and has credible supporting evidence with no affected dependencies, a justified document assessment may suffice. However, if the change affects critical data or a lockout decision, appropriate functionality and failure scenario testing is required. A technical compatibility assessment alone does not address this technical question.

Own work matrix for selection of update reviews
Change or alertPotential impactReasonable demonstration
Altered booking logic Incorrect quantity or assignment in the subsequent process Representative booking with target values and alignment of the receiving system
New app dependency Branch function is missing or operates differently Compare versions and dependencies; fully execute the affected process.
Altered authorization Unauthorized modification of a critical status Positive and negative role verification using standard user accounts
Altered interface Dataset missing, received duplicate or late Review transfer, interruption, repetition, and professional coordination
Only documented surface change Operator error or altered work instructions Justify the impact; targeted operational checks and, if necessary, training
Open error from the previous release A known limitation remains. Record a correction notice or a further valid, assessed alternative control.

Sources: [8] [6]

5. Prepare a robust sandbox environment

An online environment copy launches on the same application version and inherits installed apps. The copy therefore does not yet update the solution to the target state. Microsoft temporarily halts order queues, simplifies certain integration configurations, and blocks outgoing HTTP calls from extensions. Linked Power Platform environments are not copied. Document which test connections you intentionally establish thereafter.

A production copy is not an anonymized dataset. Access, personal data, and data cleansing actions related to the copy must be handled separately. Post-hoc data protection measures applied to the original do not automatically synchronize to the copy. Use appropriate test data, restricted authorizations, and clearly identifiable test recipients. The release of an HTTP connection must not permit accidental communication with a production service.

The specific Microsoft Preview documentation allows updating an existing Sandbox to a Preview version. However, Preview environments are provisional and will be deleted after the end of the intended period; ensure that required validation evidence is preserved outside of this environment. Independently verify the final released target state. Furthermore, a Sandbox, due to its different performance tier, is not a reliable benchmark for production performance.

Sources: [3] [4] [5]

6. Freeze and synchronize App statuses and dependencies together

Before each test run, document the actually installed App versions including libraries. During a major version update, marketplace apps may also be updated. For minor version changes, the setting "Apps Update Cadence" controls part of this behavior; required compatibility updates remain relevant. This setting does not control updates to customer-specific per-tenant extensions.

Application dependencies may require additional installations or updates. Consult with the industry partner to determine which combination has been validated and what correction is planned for your target environment. Only a complete version set enables a traceable comparison between sandbox and production. If a library change occurs after testing, evaluate this additional difference.

Special attention should be given to development extensions: Sandbox apps directly published from the development environment can be removed during environment updates, while their data is retained. Therefore, validate the intended deployment pathway and not any randomly existing developer snapshot. The partner documentation required for the industry module is detailed in the separate extension guide; here, the use of such documentation in the specific update is relevant.

Sources: [6] [5] [8]

7. Example: Material status and warehouse transfer

The following example describes an operation featuring a customer-specific material release extension and an interface to the warehouse. It does not describe the unaltered Business Central standard. The requirement is: A locked material must not be made available to the warehouse; a legitimate release must arrive with the correct batch and quantity.

The test owner prepares two predefined material data sets and documents the initial state, app versions, roles, and interface endpoints. The expected status values and messages are derived from the own specification. An update is only professionally evaluated when both discontinued and aborted processes can be traced and understood.

Example: Regression tests following the update
Test caseExecutionExpected evidence
Blocked material Attempt transfer with locked output status No available inventory on hand; clear rejection and appropriate documentation
Authorized Release Change the status and transfer with approved role assigned. Correct batch, quantity and status in the target; unique assignment to the initial process
Unauthorized release Try the same action with normal bearing role Action remains locked according to the authorization concept.
Communication interrupted Intentionally interrupt test connection during transfer handover Errors detectable; defined retry without silent loss
Repetition Resend a failed process upon retry No unintentional double booking; voting on both sides possible
Historical dataset Review completed activities prior to the update Key contents and assignments remain correct and traceable.
Follow-up inspection After a production update, verify the approved control procedure. Installed system and operational functionality align with the decision.

Sources: [8] [3] [6]

8. Upon encountering errors, know the allowable action space

Distinguish a technical error during testing, a failed update implementation, and an error occurring after a successful update. For a test error, document reproduction steps, data, versions, and impact. In consultation with QA and process responsibility, determine whether a correction, a justified delay, or a reviewed limitation is required. The statement "Partner is informed" is insufficient as a decision.

A failed or interrupted online update, according to Microsoft's description, rolls back to the previous application version; the next attempt will be scheduled again. Manual aborts have limitations, particularly during forced update periods. This is different from an arbitrary rollback following a previously successful update. Restoration options are also version-dependent and restricted.

In the event of a failure in the production process, document the incident and define the affected time period, data set, and subsequent process. Hold critical procedures pending if necessary and verify already transferred data. For technical escalation, leverage operational data and clear error references. A retry must be based on a verifiable criterion, such as corrected data transfer and completed inventory reconciliation.

Sources: [1] [2] [8]

9. Release and follow-up as a joint decision

A meaningful update closure identifies the installed version, evaluated changes, performed assessments, deviations, and the decision regarding continued use. Maintain restrictions such that the operation can actually implement them: affected process, approved alternate procedure, responsible point of contact, and review date. An undefined list of remaining actions hinders daily application.

Microsoft provides the service and product information; the industry partner supplies its agreed share of applications, analysis, and corrections. The end user retains knowledge of the intended use and responsibility for evaluating their own processes. Define clearly who manages schedules, assesses impacts, conducts tests, and makes technical decisions. In small teams, tasks may be combined; however, authorities and appropriate controls must remain clearly defined.

The effort primarily depends on variations, interfaces, app dependencies, and the quality of existing regression tests. Reusable test data and traceable target values reduce alignment efforts, without guaranteeing a specific time savings. Include recurring defects, manual workarounds, and overdue actions in the periodic system assessment.

Sources: [8] [1]

10. Checklist for the next update cycle

Use this checklist as a reference tool for the joint meeting involving IT, QA, process responsibility holder, and partner. A missing item requires a determination of its significance; not every empty field triggers the same test scope.

  • Operating mode, environment, source and target versions, as well as point of contact, are clearly documented.
  • Update period, time zone, maintenance window, and internal decision deadline are known.
  • Alerts are communicated to a designated employee and their authorized representative.
  • Release information, partner changes, and known defects were referenced in relation to own usage.
  • Sandbox, data access, test recipient, and interfaces are controlledly established.
  • The verified version set includes all relevant applications and dependencies.
  • Tests cover critical process pathways as well as appropriate negative and interrupted workflows.
  • Open errors have an impact assessment and a specific corrective action.
  • Operational decision, potential restrictions, and follow-up inspection are documented.
  • Evidence remains available regardless of the termination of a Sandbox or Preview.

Sources: [8] [2] [3] [4]

Project experience and collaboration

Manage a cloud update through a controlled release process

Before a Business Central update, we compare the target version, installed extensions and processes actually used. We select tests that answer the open questions on an appropriate test version. A small change may need a limited package. For frequent similar updates, we establish a reusable test basis with IT and process owners. Before the operating decision, we assess results, open defects and necessary restrictions. We then check the version actually installed.

Frequently asked questions about Business Central updates

Do we need to perform a complete revalidation of Business Central after each update?

No. Assess the change against your documented baseline state and the relevant requirements. Derive appropriate additional evidence as needed. A minor technical version increment may impact a critical process; a larger release may include many features you have not previously utilized. What is decisive is understandable impact and remaining uncertainties, not merely the version number or a generic repeat plan.

Sources: [8]

Can we keep Business Central Online on our validated system?

Not unlimited. The online update policy includes defined time periods, followed by mandatory updates. Align your change management process to these timeframes. If a critical industry function remains incompatible, engage the supplier early to establish a robust solution and obtain a business decision. Permanent postponement does not constitute a substitute for resolving the conflict.

Sources: [1]

Are six-hour update windows considered an agreed downtime period?

No. Six hours is the documented minimum width of the configurable window. The actual start time and duration depend on the update and the environment. Plan for potential unavailability due to operations and assess the impact on interfaces. An option for updates outside the window must not inadvertently result in a promised operational readiness being missed the following morning.

Sources: [2]

Does a test conducted in a Preview Sandbox serve as a basis for production decision-making?

A preview test provides early indications but does not replace the comparison with the final target state. Apps, error fixes, and configurations may differ. Document which evidence remains valid and which additional checks are required. Store results outside of the preview environment, as these environments are temporary and not intended as a permanent audit trail.

Sources: [4] [8]

Is a copied production environment immediately usable as a test system?

It must be first validated and controlled. Microsoft modifies certain background and integration functionalities during copying. Therefore, test connections, recipients, roles, and required data should be verified. The copy retains relevant business data and is not automatically anonymized. Furthermore, it neither replicates an attached Power Platform environment nor fully reproduces the end-to-end landscape without additional effort.

Sources: [3]

Are successful Microsoft compatibility tests sufficient?

You provide useful product evidence, but they do not address all questions related to the intended use. An app may be installable and yet incorrectly transmit a business status to a connected system. Assess supplier and partner evidence for alignment and gaps. The remaining evaluations should cover your critical processes with the actual intended app combination.

Sources: [6] [8]

Why might the test setup appear different from expectations after the update?

In addition to changes to Business Central itself, apps and dependencies may have been updated. Furthermore, development extensions are deployed differently in a sandbox environment compared to regularly installed packages. Therefore, after an update, compare the actual versions in place against the test planning. A successful execution on a previously manually enhanced developer environment does not automatically translate to the future production combination.

Sources: [6] [5]

Can we simply revert to the previous version in case of an issue?

Do not rely on it. Reverting a failed or interrupted update differs from restoring after a successful update. Microsoft documents limitations that depend in part on the update period. Identify a recovery route beforehand and account for new postings and data in connected systems. Technical restoration does not reconcile those transactions.

Sources: [1] [2] [8]

What is different with on-premises?

The installation and operational window periods are determined by your operation or service provider. This includes version-specific platform, database, and extension steps; online deadlines are not automatically transferred. Use the guide for your specific source and target states and assess backup, recovery, and the affected business processes. Greater schedule control does not imply that changes can be implemented without evaluation.

Sources: [7] [8]

Which documents should a small and medium-sized enterprise prepare first for the next cycle?

Start with environment and versions, application list, interface overview, critical process requirements, and the latest test results. Include update announcements, partner notifications, and open defects. These documents make visible what is changing and who is responsible. From this, a concrete review and decision plan emerges. Generic daily rate estimates, test quantities, or time commitments provide little value without this level of detail.

Sources: [8] [2]

Sources and review date

Source date: 6 October 2026. The online mechanisms are described according to current Microsoft documentation; specific tenant schedules and app statuses remain to be verified. Regulatory reference: Human medicinal product GMP, FDA requirements applicable only within their respective scope of application. Matrices, example, and checklist are standalone work aids.

  1. Microsoft Learn: Update cycles
  2. Microsoft Learn: Managing updates in the Business Central admin center
  3. Microsoft Learn: Copy an environment
  4. Microsoft Learn: Prepare for major updates with preview environments
  5. Microsoft Learn: Managing production and sandbox environments
  6. Microsoft Learn: Managing apps
  7. Microsoft Learn: Install a Business Central 2026 Release Wave 1 Update
  8. European Commission: EU GMP Annex 11, January 2011 revision
  9. European Commission: EudraLex Volume 4
  10. eCFR: 21 CFR Part 11
  11. FDA: Part 11 – Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Prepare for the next Business Central update cycle

We link your change information to quality-related processes and existing validation evidence. Daniel Herrmann Consulting supports you in making open decisions prior to update visibly and actionable.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →