Business Central version guide: waves, numbers and updates

From Navision to Business Central: a version guide

Business Central is the current form of a product with a long history. It began as Navision, then became Microsoft Dynamics NAV when Microsoft bought the company. Later it was renamed Dynamics 365 Business Central, when Microsoft launched it as a cloud service. Each stage carried the business logic forward and added to it.

Two technical changes mark the move from NAV. First, a browser client replaced the Windows client. Second, the AL language and its extension model replaced C/AL. The earliest on-premises Business Central versions still supported the old approach next to the new one. Later versions use AL and the web client only.

Release waves in the Business Central version guide

Microsoft ships two major releases each year. Release wave 1 begins in April and release wave 2 begins in October. As of the 2026 release wave 2 plan, the newest major release is version 29. Check Microsoft's current release plan before you schedule work. Before each wave, Microsoft publishes a release plan. It lists planned features by area, so customers and partners can see what is coming and decide what to adopt.

New features in a major release are often optional at first. The Feature Management page lists them with a switch. So an administrator can turn a feature on in a sandbox, try it, and enable it for everyone when ready. Eventually Microsoft makes each feature standard, and the page shows when.

How Business Central version numbers are built

A Business Central version has a major number, a minor number and a build. The major number goes up by one with each release wave. The minor number counts the monthly updates inside that wave, starting at zero. So a version with a major number followed by .3 is the third monthly update of that release.

You also need to watch two numbers: the platform version and the application version. The platform is the server and client software. The application is the business features. Online they move together. On-premises you see both, and each extension states the minimum versions it needs in its manifest.

How to find your Business Central version

In the client, select the question mark, then Help and Support. The Troubleshooting section at the bottom shows the version, the build and the tenant and environment details a support engineer will ask for. You can copy it with one action and paste it into a support request.

Admins see more in the Business Central admin center. The Environments list shows the version of each production and sandbox environment. It also shows whether an update is available and the scheduled date. Meanwhile, Extension Management lists each installed extension and its version. That helps when you diagnose an issue.

What your Business Central version means for support

Microsoft keeps online environments current. When a major update arrives, admins pick a date inside the allowed period and set a daily update window. If nobody picks a date, the service applies the update. Monthly updates follow the same window. So staying many versions behind is not an option online.

On-premises versions get support for a fixed period under Microsoft's lifecycle policy, with cumulative updates along the way. After that, fixes and regulatory changes stop. If you run an older on-premises version, check where it stands in that policy. Our consultants can confirm your position and outline your upgrade options.

Questions about the Business Central version guide

Is Business Central the same product as Dynamics NAV?

It is the successor. Business Central carries forward the business logic and data model of NAV. It adds a new web client, the AL extension model and a cloud service run by Microsoft. People who know NAV recognize the concepts at once, although the tools around them have changed. This Business Central version guide helps you map old terms to new ones.

Can we skip a release wave online?

No. You can postpone a major update within the period Microsoft allows, which gives you time to test. But every online environment is updated in the end. That is why testing extensions in a sandbox or preview environment before each wave is a routine task. It turns a release wave into a planned event, not a surprise.

Why does support ask for our version and build?

Because behavior and known issues differ between updates. The exact build tells an engineer which fixes your environment already has. So copy it from the Help and Support page when you raise a request. Add the environment name and the time of the problem as well. That saves a round of questions and gets you to the cause faster.

Do extensions depend on a particular version?

Yes. Every extension states the minimum application and platform version it needs. When Microsoft removes or changes something an extension relies on, the publisher must release a compatible version. Microsoft warns about obsolete code in advance, so publishers have time to adapt. Keep a list of your extensions and who supports each one.

How do we know what is new in each release?

A good Business Central version guide starts with the release plan on Microsoft Learn, sorted by area, and the What's New articles for each update. We also summarize the features worth adopting for our support clients in plain language. Then we help them try the relevant ones in a sandbox. That way, nobody has to read every release note alone.

Related Business Central version guide topics

Versions lead naturally to upgrades and testing. This Business Central version guide links to the pages on upgrade steps from older systems and sandbox environments. It also covers how our support team handles update testing for clients, so you know who checks each release before your users see it. For the product detail, see Microsoft's update rollout timeline for Business Central online.