The Code Nobody Owns: 7 Business Central Support Customization Fixes Before Your Next Update
Business Central Support Customization Snapshot
Microsoft updates Business Central twice a year (April and October) and ships minor updates most other months. Each one is a compatibility test for your custom code.
Extensions made upgrades far safer than old Dynamics NAV code changes, yet an incompatible extension can still be uninstalled during Microsoft's enforced update period.
The real cost of Business Central support customization is ownership: source code you control plus a team that tests before every update.
A BC Consulting Group pairs MVP-led developers with US-based support plans and a continuous maintenance add-on that tests your code against future upgrades.
It's the last business day of the month. Your AP clerk clicks Post on a batch of vendor payments, and Business Central throws an error nobody has seen before. The custom approval extension your old partner built two years ago stopped behaving the night Microsoft pushed an update. The developer who wrote it moved on. And your controller wants to know when payments go out.
Business Central support customization is the ongoing work of keeping your custom extensions and integrations compatible and owned after go-live, through every Microsoft update. Most companies budget for building a customization. Few budget for living with it, and that gap breeds month-end fire drills.
Once you see the mechanism, the fix is predictable. Let's walk through it like friends at a whiteboard.
What Is Business Central Support Customization, and Why Does Custom Code Break?
Short answer: Business Central support customization exists because your ERP never stands still, and your custom code has to keep pace with every Microsoft update.
How do extensions sit on top of Business Central?
Back in the Dynamics NAV and GP days, customizations were tangled into the base code, and every upgrade meant untangling them by hand. If you're still there, start with Dynamics GP end of life: your migration options explained.
Business Central changed the model. Custom features now live in extensions written in Microsoft's AL programming language. They sit in a separate layer on top of the base application and plug into it through events and published APIs. You'll usually run two kinds:
Per-tenant extensions (PTEs): built for your company alone, like a custom approval workflow or a special pick ticket for Business Central warehouse management.
AppSource apps: commercial add-ons from ISVs, like Avalara for sales tax or Binary Stream for multi-entity management.
Our breakdown of Business Central extensions vs. customizations goes deeper on when each fits. That separate layer made upgrades much safer. It's also why buyers hear "update-proof" and stop asking questions, which is exactly where Business Central support customization starts.
What Happens to Your Custom Code Every April and October?
This is the mechanism most quotes skip. Based on Microsoft's Business Central update rollout timeline, each major release follows the same path:
1. Preview (March and September)Preview sandboxes open about a month before release so you can test your extensions early. | 2. Release (April and October)The update reaches existing environments roughly a week after general availability. | 3. Update window (five months)Your admin can reschedule inside this window. If an extension makes the update fail, Microsoft rolls back and retries seven days later. | 4. Grace period (one month)Postponing is no longer an option. | 5. Enforced updateExtensions that block the update might be uninstalled automatically so it can finish. Your data stays, but the feature disappears until someone installs a compatible version. |
Step five is the one that wrecks a month-end close, and a failed close can snowball into Business Central GAAP compliance and audit headaches. Business Central 2026 release wave 2 (BC29) arrived this October, so its update window closes in early March 2027 and the enforced period follows in April, right as Q1 closes.
Our original insight: every customized Business Central tenant faces 12 compatibility checkpoints a year, two major releases and ten monthly minor updates. Extensions lowered the risk at each checkpoint. They never removed the checkpoints. Good Business Central support customization plans for all 12.
Is Your Custom Code Ready for Its Next Update?
Book a free call with our MVP-led team and learn where your extensions stand before Microsoft's next deadline.
7 Business Central Support Customization Risks Hiding in Your ERP
These are the problems we see most after an update goes sideways, each with a fix you can start this week.
1. Who owns your custom code today?
Most custom code is born during Business Central implementation services, and plenty of it was built by a freelancer or partner who has moved on. Code with no owner gets no one reading Microsoft's release notes for it.
Fix: Name one owner for every extension in production and write it down. These signs you've found the right Business Central consultant help if you're hiring that owner.
2. Do you have the source code, or only the app file?
An installed .app file runs fine until it needs a change. Without the AL source, a small fix becomes a rebuild. This is one of the most expensive Business Central support customization surprises we run into.
Fix: Ask your current partner for the full source repository. A BC Consulting Group delivers code and PTE files through GitHub, so the repository stays yours.
3. Is anyone testing in the preview sandbox?
The preview sandbox gives you about a month to catch problems before release day. Most teams never open it. You can also update a copy of your existing sandbox to the preview version, so the test runs against your real extensions and settings.
Fix: Put a recurring March and September test on the calendar. Run your critical flows (posting, approvals, integrations and key reports) in preview and log anything that breaks.
4. Is Microsoft retiring code your extension depends on?
Microsoft marks older objects and APIs as obsolete before removing them in a later release. Code that compiles cleanly today can fail a couple of releases from now, and the warnings show up in compiler output long before the failure does.
Fix: Have a developer recompile your extensions against each new version and clear obsolete warnings while they're still only warnings.
5. Are your integrations still talking to each other?
Your tenant probably connects to a tax engine, an ecommerce site, a bank feed and a handful of Power Automate flows. Any one of them can quietly stop syncing, and the real cost of a broken Business Central CRM integration adds up fast.
Fix: Keep a simple integration map listing what connects, which way data flows, who owns it and how you'll know it failed. Our post on Business Central integrations shows which connections to prioritize. Then turn on Business Central telemetry in Azure Application Insights so failures reach a person before they reach the general ledger.
6. Are your users drowning in workarounds?
Sometimes nobody uses the customization as designed. Users export to Excel, fix things by hand and re-import. That spreadsheet layer is invisible support debt.
Fix: Pair recurring tickets with short refresher sessions. These Business Central training fixes for the day-two spreadsheet relapse often clear a whole category of tickets.
7. Are you customizing what you could configure?
Not every request needs AL code. Some of the smartest Business Central support customization decisions are the extensions you never build. Before approving new code, climb this ladder from lightest upkeep to heaviest:
Personalization by each user
Role profiles set by an admin for a whole team
Power Automate flows for approvals and alerts, with help from our Power Automate consulting team
AppSource apps maintained by an ISV
Custom AL extensions for logic that truly makes your business unique
Fix: Ask for a one-line reason why configuration won't do the job before anyone opens a code editor.
Do Two or More of Those Risks Look Familiar?
Let's talk. We'll review your extensions and map a Business Central support customization plan in plain English.
How Much Does Business Central Support Customization Cost?
Answer first: Business Central support customization usually costs a monthly support plan plus a separate budget for code changes. The second number is the one most companies forget, much like the Microsoft Business Central pricing costs hiding behind $80 a user.
At A BC Consulting Group, our published Business Central support plans start here:
Basic, $1,250/month ($15,000 a year)
Suited for 10 users or fewer, with unlimited functional support, a discounted technical rate, an 8-hour non-emergency SLA and a 2-hour emergency SLA.
Premium, $2,500/month ($30,000 a year)
Suited for 10 users or more, with unlimited functional support, 8 hours of technical support each month, a 4-hour non-emergency SLA, a 1-hour emergency SLA, a dedicated account manager, one hour of new-feature training each release and one free onsite day per year.
Your custom code bill depends on four drivers:
How many per-tenant extensions you run in production
How many integrations touch those extensions
Whether you hold the source code (no source usually means rebuild costs)
How much of your testing is automated versus manual
Your support plan pays for the people who answer tickets. Your code budget pays for the developers who keep extensions current. Put both lines of your Business Central support customization budget on the same spreadsheet.
What Should a Business Central Support Customization Plan Include?
Before you sign anything, check that your plan covers each of these:
Named ownership of every extension, with source code stored in a repository you can reach.
Preview testing every March and September against your critical business flows.
Recompiles and obsolete-code cleanup for each major release.
Written SLAs with an emergency tier that covers month-end posting and payment failures.
Integration monitoring through telemetry, with alerts going to a real person.
Ticket management with Microsoft and ISVs, so your partner chases third parties for you.
Release training so users learn new Copilot Business Central features instead of inventing new workarounds.
If your current Business Central support customization arrangement misses more than two of these, it leaves your month-end exposed. Watch for these Business Central implementation partner red flags too, and review your Business Central security features, since permission sets often change alongside extensions.
Why A BC Consulting Group Is Built for Business Central Support Customization
We're a boutique, Microsoft MVP-led Dynamics 365 partner in Nashville, Tennessee. Business Central support customization sits exactly where our two strongest teams meet: Business Central development services and post-go-live support.
Here's what Business Central support customization looks like with us:
|
|
|
|
|
|
|
For orphaned builds, a round of ERP discovery maps what you have before anyone writes new code. And if you're still comparing firms, here's how to choose a Microsoft Dynamics 365 partner.
When an implementation goes sideways, speed is what clients remember most. John, Director of Operations, brought us in after his Business Central project stalled:
"Shannon was able to quickly assess the situation and come up with a game plan to get us back on track. She is a consummate professional and her knowledge of Business Central is truly impressive. Thanks to her we were put back on track within days."
John, Director of Operations
Your Next Move for Business Central Support Customization
Back to that AP clerk staring at the posting error. Every part of that story traces back to a predictable checkpoint that nobody owned.
Business Central support customization gives every extension an owner and a test date on the calendar. With that in place, April and October become ordinary months again, and month-end belongs to your finance team instead of your error log.
Make Your Next Release Wave a Non-Event
Talk with A BC Consulting Group's MVP-led team about Business Central support customization that keeps your code tested and ready before Microsoft's deadline.
Business Central Support Customization FAQ
What is Business Central support customization?
Business Central support customization is the ongoing maintenance of custom extensions and integrations after go-live. It covers testing against Microsoft updates, fixing errors, managing source code and adjusting features as your processes change.
Will Microsoft updates break my Business Central customizations?
Usually not, since extensions sit in a separate layer from the base application. Still, extensions that rely on retired code or untested integrations can fail an update, and during Microsoft's enforced update period an incompatible extension might be uninstalled automatically.
How much does Business Central support customization cost?
Expect a monthly support plan plus a budget for code changes. A BC Consulting Group's plans start at $1,250 per month for Basic and $2,500 per month for Premium, with custom development quoted based on how many extensions and integrations you run.
Can a new partner support customizations another partner built?
Yes, as long as you can get the AL source code. A new partner reviews the code, recompiles it against the current version and documents ownership. Without source code, the extension often has to be rebuilt.
Should I customize Business Central or use Power Automate and AppSource apps?
Start with the lightest option. Personalization, role profiles, Power Automate and AppSource apps cover many needs with less upkeep. Save custom AL extensions for logic that sets your business apart.
Comments