> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/roadmap/bevica-roadmap/business-central-resource-hub/what-is-a-wave-update.md).

# What is a Wave Update

Microsoft’s long‑term goal for Dynamics 365 Business Central is to make it the **default cloud ERP for small and mid‑sized businesses (SMBs)**—by turning it into a continuously evolving, AI‑assisted, industry‑ready business platform.

Business Central is the long‑term successor and consolidation point for all SMB ERP on Microsoft’s platform.

A **wave update** is a scheduled release cycle during which Microsoft ships a bundle of new capabilities over several months rather than all at once.

Instead of big, disruptive upgrades, Microsoft delivers continuous innovation in planned waves.

***

### When Do Waves Happen?

Microsoft runs **two major waves per year**:

* **Wave 1** (April-September)
* **Wave 2** (October - March)

Each wave:

* Is announced in advance
* Has release plans published months ahead
* Rolls out gradually, not all on day one

***

### How the Rollout Works (Step‑by‑Step)

{% stepper %}
{% step %}

### Public Announcement & Release Plans

Before a wave starts, Microsoft publishes release notes, feature lists and early previews

These plans explain:

* What’s coming
* When features are expected
* Whether features are preview or GA (generally available)

This allows organisations and product teams to plan changes, training, and comms.
{% endstep %}

{% step %}

### Early Access & Preview Features

Some features are released first as private preview, public preview and early access.

This is how Microsoft:

* Reduces risk
* Gets real-world usage data
* Adjusts before full rollout
  {% endstep %}

{% step %}

### Staggered Deployment (Phased Rollout)

Microsoft does not update everyone at the same time.

Instead:

* Tenants are updated in batches
* Regions may receive updates at different times
* Some users see features weeks before others
  {% endstep %}

{% step %}

### Feature Controls & Admin Settings

Admins usually retain control over:

* Whether some features are enabled
* When users see UI changes
* Whether previews are allowed
  {% endstep %}

{% step %}

### Automatic Adoption (Evergreen Model)

Unlike old “upgrade projects” you cannot skip waves indefinitely, features eventually become mandatory and deprecations are announced well in advance

Microsoft follows an evergreen SaaS model:

* Continuous improvement
* Backward compatibility wherever possible
* Long notice periods for removals
  {% endstep %}
  {% endstepper %}

***

### What Gets Updated in a Wave?

A wave can include:

* New features
* Performance improvements
* Security enhancements
* UI/UX changes
* API and platform capabilities
* Feature deprecations (with warnings)

Not every tenant gets every feature—some depend on:

* License type
* Region
* Product SKU
* Admin configurations

***

### Why Microsoft Uses Wave Updates

Microsoft uses waves to:

* Reduce disruption
* Deliver innovation faster
* Allow customer feedback before GA
* Avoid “big bang” upgrades
* Keep the platform secure and modern

Waves balance predictability with continuous delivery.

***

### What You Should Do

**Best practices**

* Review release plans at the start of every wave
* Identify features that impact users or processes
* Decide which previews to test early
* Plan communications and training
* Monitor Message Center and admin notifications
* Liaise with the Support Desk to plan the wave's testing and rollout.

***

### Release Notes & Update Resources

#### What’s New in Business Central

Latest features by release wave: [What's new and planned in Business Central](https://learn.microsoft.com/dynamics365/business-central/product-news)

#### Major / Minor Update Cycles

Update schedule for major and minor updates that are rolled out in between Wave updates [Update Rollout Timeline](https://learn.microsoft.com/en-gb/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/roadmap/bevica-roadmap/business-central-resource-hub/what-is-a-wave-update.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.