Business Central Feature Management: What Version 29 Makes Mandatory and What Admins Should Review
Business Central Feature Management deserves an administrator review after every major update because some features do not stay optional forever. In version 29, Microsoft lists two features as mandatory, which means their Feature Management switches are removed and the features can no longer be disabled. The bigger lesson is more important than the two specific changes: a feature flag has a lifecycle, and administrators should treat it as part of change management rather than as a permanent safety switch.
For many U.S. companies, one of the version 29 mandatory items is likely to be more relevant than the other. Microsoft lists the Manual flushing method without requiring pick as mandatory, while the second item relates to per Activity Code VAT settlements in Italy. Not every customer will be affected in the same way, which is exactly why administrators need a repeatable review process instead of assuming every release note applies equally.
What Feature Management actually does
Feature Management gives administrators a controlled way to enable certain new or changed Business Central behaviors before Microsoft makes them standard. It creates a temporary decision window in which the company can review the change, test it in a sandbox, understand the business impact, and decide when to enable it.
That review belongs inside broader Business Central support and optimization. A feature can be technically available but still require process testing, user communication, training, or extension validation before it belongs in production.
Optional does not mean optional forever
Microsoft's documentation is clear that many optional features remain optional only for a period of time. The Feature Management page can show an approximate Automatically enabled from date for features expected to become mandatory. After the feature becomes mandatory, the switch disappears and the organization cannot simply turn the behavior off.
That changes the planning question. The question is not only whether your company wants a feature today. It is whether your company will be prepared when that behavior becomes part of the standard product.
What changed in version 29
Microsoft lists two features as mandatory in Business Central 2026 release wave 2, version 29. The first is the Manual flushing method without requiring pick. The second enables per Activity Code VAT settlements in Italy. Because the latter is localized, many organizations will have little or no impact from it.
The practical point is that version 29 continues the normal Business Central pattern of aging capabilities out of Feature Management. In prior versions, other capabilities moved from optional to default or mandatory. An administrator who never reviews Feature Management can therefore miss both opportunities to prepare early and changes that are approaching a mandatory state.
Build a quarterly feature review
A useful Feature Management review does not need to become a large governance project. Once per quarter, and again before a major update, review available optional features, automatically enabled dates, business areas affected, related extensions, related integrations, required user testing, and training or communication needs.
Classify each relevant feature into four buckets: not relevant, monitor, test, or enable. Most features should not create a major workstream. The value comes from identifying the small number that deserve attention before Microsoft removes the choice.
Test business behavior, not just the switch
A Feature Management test should prove the business outcome. Turning a feature on in a sandbox and confirming that a page opens is not enough. Run the actual business process with representative data, permissions, extensions, integrations, posting setup, and exception scenarios.
For a warehouse-related feature, test the warehouse process. For a finance feature, test posting and reconciliation. For a reporting change, validate the numbers. The objective is to prove the company's workflow, not Microsoft's menu option.
Review extensions and integrations around the affected area
Business Central rarely operates alone. When platform behavior changes, connected extensions, APIs, reports, Power BI models, Microsoft 365 workflows, and other integrations may also be affected.
This is why feature review often overlaps with Microsoft cloud and business systems rather than staying inside Business Central alone. The closer a feature sits to posting, inventory, warehousing, approvals, reporting, or an integration boundary, the more important end-to-end testing becomes.
Use the mandatory date as a deadline, not a surprise
If a feature is expected to become mandatory in a future release, treat that date as a readiness deadline. Test early enough to discover whether the company needs user training, extension changes, process updates, integration changes, documentation, or help from its Business Central partner.
Waiting until a feature becomes automatically enabled turns a controlled change into a support problem. A short review performed early is usually easier than troubleshooting the same behavior after users are already affected.
Feature Management is part of ERP governance
Feature Management looks like an administrator page, but the decisions inside it can affect finance, operations, warehouse teams, reporting, developers, and end users. That makes it a small but meaningful part of ERP governance.
The company does not need to react to every feature. It needs a repeatable way to identify which changes affect important work. That means knowing what is optional today, what becomes standard later, who owns the affected process, and how the change will be tested.
If your team is unsure which Business Central changes deserve testing, which can be ignored, or how a major update affects your environment, explore triniT Partners Business Central services.
Comments