Business Central Support Services: What Good Help Looks Like After Go-Live
Business Central support services are the ongoing help a company gets after Microsoft Dynamics 365 Business Central goes live. That means a help desk for users, troubleshooting when something breaks, planned maintenance around Microsoft’s update cycle, and steady improvements so the system keeps up with the business. In my experience, the quality of your Business Central support services matters more to long-term ERP success than the implementation itself, because go-live is the day real usage starts.
I see the same story play out again and again. The team celebrates go-live, the consultants move on, and three weeks later finance is stuck on a posting error at 4:45 p.m. on the last day of the month. Nobody owns the problem. That gap is exactly what Business Central support services exist to close.
In this guide, I’ll walk you through what Business Central support services should include, how Microsoft and partners split the work, what to put in an SLA, how to plan maintenance, and how to budget.
Key Takeaways
- Business Central support services cover the help desk, troubleshooting, update management, extension and integration upkeep, reporting, training, and ongoing optimization.
- Microsoft runs the cloud platform, but your partner is the first line of support for your specific environment.
- Business Central online gets two major updates a year (April and October) plus monthly minor updates, so maintenance never stops.
- A written Business Central SLA should define severity levels, response times, and resolution targets.
- The right model for Business Central support services depends on your users, your customizations, and whether you have an in-house admin.
What Are Business Central Support Services?
Business Central support services are a set of ongoing services that keep Dynamics 365 Business Central stable, current, and useful after implementation. They usually include a help desk for daily questions, technical troubleshooting, environment and update management, maintenance of extensions and integrations, and functional guidance on finance, inventory, sales, and purchasing processes.
Support is one piece of the wider set of Business Central services a company uses across the ERP lifecycle, alongside implementation, customization, integration, and reporting. I like to split Business Central support services into two layers.
Reactive support is what most people picture. A user raises a ticket, someone investigates, and the issue gets fixed: error messages, failed postings, or a report that won’t run.
Proactive support separates good providers from average ones. It covers testing updates before they reach production, watching telemetry, cleaning up permissions, and fixing small annoyances before they become spreadsheet workarounds.
Most companies buy only the reactive side of Business Central support services and assume they’re covered. Then an extension fails after a major update, and they find out nobody was testing anything.
Business Central support services are also very different from general IT support. Your IT provider can reset a password and fix a laptop. They usually can’t tell you why a general ledger account doesn’t match its subledger. Real Business Central support needs people who understand both the technology and the accounting logic underneath it.
Why Post-Implementation Support Matters More Than You Think
Post-implementation support is the help a business receives in the weeks and months after Business Central goes live, while users are learning the system under real pressure. It matters because most problems don’t show up during testing. They show up during the first month-end close, the first big purchasing run, or the first busy sales week.
The first 90 days usually unfold like this:
- Weeks 1 to 2: A flood of “how do I” questions as users adjust.
- Weeks 3 to 6: The first month-end close exposes setup gaps in posting groups, dimensions, number series, and approval workflows.
- Weeks 6 to 12: Integrations meet real volume and hit edge cases nobody tested.
Many projects include a short “hypercare” period to cover this stretch. The problem is that hypercare ends on a calendar date, and issues don’t. That’s why I always tell clients to arrange ongoing ERP support before the implementation contract closes, not after the first crisis. Treat ongoing ERP support as a line in the budget, like the license itself.
If you’re still early in your journey, picking the right Business Central implementation partner makes post-implementation support far smoother, because the people who configured your system understand why it was built that way. The same goes for companies that migrate to Business Central from QuickBooks. QuickBooks users are used to a much simpler tool, so the learning curve in the first few months is steeper and the demand for Business Central support services is usually higher.
How Business Central Support Works: Microsoft vs. Your Partner
Business Central support services follow a partner-led model. Microsoft maintains the cloud platform, infrastructure, and core product, while your reselling or support partner handles everything specific to your environment, such as configuration, users, extensions, integrations, and troubleshooting. When a partner can’t solve a problem, the partner escalates it to Microsoft.
Microsoft treats the reselling partner as the frontline for each customer, and this partner-led Business Central support model shapes how every ticket gets handled. In practice, the split looks like this:
| Responsibility | Microsoft | Your support partner |
|---|---|---|
| Cloud hosting, uptime, platform security | Yes | Monitors and keeps you informed |
| Major and minor product updates | Releases them | Tests, schedules, and fixes what breaks |
| Your configuration and setup | No | Yes |
| Per-tenant extensions and customizations | No | Yes |
| Third-party apps and integrations | No | Yes, together with app publishers |
| User training and process questions | No | Yes |
| Bugs in standard Business Central | Fixes them | Reproduces, reports, and escalates |
This is why the partner behind your Business Central support services shapes your whole experience. Microsoft runs the platform well, but it doesn’t know your chart of accounts, your warehouse layout, or the custom approval flow your CFO asked for last spring. Business Central support services fill that gap.
What Should Business Central Support Services Include?
Complete Business Central support services should include a help desk, troubleshooting, update management, extension and integration maintenance, reporting support, user training, security and permissions management, and continuous optimization.
Here’s what each part of Business Central support services should look like in practice.
1. Business Central Help Desk
A Business Central help desk is the single point of contact where users log questions and issues. It should offer a ticket portal and email, plus phone or chat for urgent cases, and every ticket should get a severity level and an owner. Ticket history should be visible, so recurring problems don’t get solved quietly five times.
2. Business Central Troubleshooting
Business Central troubleshooting means diagnosing and fixing errors: posting failures, document release problems, data inconsistencies, slow performance, and integration sync errors. Strong Business Central support services don’t just patch the symptom. They find the root cause and write it down so it doesn’t come back next month.
3. Update and Release Management
Microsoft follows a fixed Business Central major and minor update cycle for the online version: two major releases each year starting in April and October, and minor updates in the other months. Your provider of Business Central support services should test each major release in a sandbox, check every extension for compatibility, and schedule the production update for a quiet time.
4. Extension and Integration Maintenance
Most Business Central systems run several extensions and connectors to online stores, banks, shipping carriers, or payroll tools. Each one is a moving part. Business Central support services should cover monitoring these connections and repairing them when an update or an outside API change breaks something. If you sell online, your Business Central eCommerce integrations deserve extra attention, since a failed order sync hits revenue the same day.
5. Reporting and Power BI Support
Business Central support services should include fixing report layouts, adjusting financial reports, and keeping Power BI dashboards that pull from Business Central accurate.
6. User Training and Onboarding
New people join, roles change, and Microsoft adds features twice a year. Training delivered through Business Central support services keeps your team using the system properly instead of building shadow spreadsheets.
7. Security, Users, and Permissions
Permissions drift. Someone gets extra access “just for this week” and keeps it for two years. Good Business Central support services include a regular review of users, licenses, and permissions, especially before an audit.
8. Continuous Optimization
This is where Business Central support services really earn their fee. Someone should be looking at slow processes, manual steps that job queues or workflows could automate, and new features from recent releases that could replace an old workaround.
Business Central Help Desk vs. Managed Services: Which Model Fits?
Business Central support services usually come in three models: ad hoc support billed by the hour, a help desk retainer with a block of prepaid hours, or Business Central managed services, where the partner takes ongoing responsibility for the health of your system. The best fit depends on your size, your level of customization, and whether you have an internal admin.
| Model | How it works | Best for | Watch out for |
|---|---|---|---|
| Ad hoc (pay as you go) | Hourly billing when you need help | Small teams with simple setups and an in-house power user | No guaranteed response times |
| Help desk retainer (block hours) | Prepaid hours each month with defined response targets | Growing companies with a steady flow of questions | Unused hours may expire, so check rollover rules |
| Business Central managed services | Fixed monthly fee, proactive monitoring, update management, and an SLA | Companies with integrations, customizations, or no internal admin | Make sure “proactive” is defined in the contract |
Business Central managed services treat your system as something the partner actively runs, not just fixes. That usually means monthly health checks, update testing, telemetry monitoring, a named consultant who knows your setup, and regular reports on tickets and trends.
My honest take? If you have fewer than 10 users, a fairly standard setup, and someone in-house who enjoys the admin side, ad hoc Business Central support services or a small block of hours is usually enough. Once you add integrations, custom extensions, multiple companies, or warehouse management, managed services almost always cost less than the downtime they prevent.
What to Include in a Business Central SLA
A Business Central SLA (service level agreement) is the written contract that defines how quickly your provider of Business Central support services responds to and resolves issues based on severity. A solid SLA spells out severity definitions, response times, resolution or workaround targets, support hours, escalation paths, and how performance gets reported to you.
Here’s an example structure. Numbers vary between providers, so treat it as a starting point, not an industry standard.
| Severity | Example situation | Typical response target | Typical resolution or workaround target |
|---|---|---|---|
| P1: Critical | Nobody can sign in, posting is blocked company-wide, invoicing has stopped | 1 hour or less | Same business day |
| P2: High | A key process is down for one department, or an integration stopped syncing | 2 to 4 hours | 1 to 2 business days |
| P3: Medium | An error with a workaround, or a report showing wrong totals | 1 business day | 3 to 5 business days |
| P4: Low | How-to questions, small change requests, cosmetic issues | 2 business days | Scheduled together with you |
When I review a Business Central SLA for a client, these are the points I check first:
- Clear severity definitions. “Critical” should be defined by business impact, not by how loudly someone complains.
- Response vs. resolution. A response is an acknowledgment; a resolution is a fix.
- Support hours and time zones. A night shift needs coverage that matches it.
- Escalation path. You need a name to call when a P1 sits too long.
- Monthly reporting. Ticket counts, targets met, recurring issues, and open items.
- Exclusions. Know what’s billed separately, such as new development.
Building a Business Central Maintenance Plan
A Business Central maintenance plan is a schedule of routine tasks that keeps your system healthy between tickets, including update testing, environment checks, data cleanup, permission reviews, and performance monitoring. It turns Business Central support services from reactive firefighting into routine care.
The backbone of any maintenance plan is Microsoft’s update calendar. Once a new major version becomes available, the update period lasts five months, followed by a one-month grace period. After that comes the enforced update period, when extensions that block the upgrade can be uninstalled so the update succeeds. That’s exactly the kind of surprise Business Central support services should prevent. Admins can control timing by setting a Business Central update window for each environment in the admin center, which keeps updates outside working hours.
Here’s the maintenance rhythm I recommend:
Every month
- Confirm the latest minor update applied cleanly
- Check failed job queue entries and recurring errors
- Review integration logs for sync failures
Every quarter
- Review users, licenses, and permission sets
- Check database capacity and clear old data with retention policies
- Look at slow pages and slow reports
Twice a year, around each major release
- Create a sandbox on the new version and test critical processes
- Test every extension and integration against the new version
- Train users on the new features that matter to them
- Schedule the production update inside your update window
Always
- Know your recovery options. Business Central online supports Business Central point-in-time restore of an environment to any moment within the past 28 days, with up to 10 restores per environment in a calendar month. Anyone delivering Business Central support services should know how to use it, and when not to.
Telemetry is the piece most maintenance plans skip. Business Central telemetry can be sent to Azure Application Insights, where it records signals like long-running SQL queries, database lock timeouts, job queue activity, and web service requests. You can also set alerts on those signals. With telemetry in place, proactive Business Central support services can spot a slow integration or a failing job before your users notice anything.
Business Central Troubleshooting: The Problems I See Most Often
Most Business Central troubleshooting falls into a handful of categories: posting and setup errors, permission problems, failed job queues, integration sync failures, slow performance, and extensions that break after updates. Knowing these patterns helps you describe issues clearly and helps whoever provides your Business Central support services fix them faster.
Posting errors caused by missing setups
Messages saying a General Posting Setup doesn’t exist are among the most common tickets after go-live. They usually mean a combination of business and product posting groups was never configured, and they block invoices until someone fixes it.
Dimension and approval problems
Documents that won’t post because a mandatory dimension is missing, or that sit in approval limbo because the approver left the company. These are process problems as much as technical ones, and good Business Central support services fix the process, not just the document.
Permission errors
A user can’t open a page or post a document because their permission set doesn’t cover it. The lazy fix is giving everyone full access. The right fix, and the one good Business Central support services deliver, is a proper role-based permission set.
Job queue failures
Job queues run the automated tasks in Business Central, such as batch posting, integration syncs, and payment reminders. When an entry fails and your Business Central support services don’t include monitoring, you find out days later when the numbers are wrong.
Integration sync failures
Orders that don’t import or stock levels that don’t update. These usually come from an API change, expired credentials, or data that fails validation.
Slow performance
Pages that load slowly and reports that time out. Common causes include heavy custom code, missing keys on custom tables, and large reports running during peak hours.
Extensions breaking after an update
A per-tenant extension written for an older version may fail against a new release. Strong Business Central support services catch this in a sandbox weeks before it reaches production.
Whenever you raise a ticket, include the exact error message, the page or document number, the steps to reproduce it, the user affected, and when it started. The Help and Support page inside Business Central also shows your environment version, which is worth passing along.
How Much Do Business Central Support Services Cost?
The cost of Business Central support services depends on the support model, the hourly rate, the number of users, how customized the system is, and the hours of coverage you need. Rates vary a lot by region and provider, so I always suggest comparing the scope included rather than the hourly number alone.
The main pricing models are hourly billing, prepaid block hours (often at a lower rate), a fixed monthly fee for managed services, and per-user monthly pricing.
For a concrete reference point, at New Wiz Tech we price our Business Central work at $20 to $50 per hour, and we publish that openly so you can budget before you ever get on a call.
Cheap support that responds slowly or keeps fixing the same issue is expensive in disguise. Before you compare quotes for Business Central support services, ask each provider:
- How many hours or tickets are included each month?
- Is update testing included or billed separately?
- Are integrations and third-party apps covered?
- What happens when the SLA is missed?
How to Choose the Right Business Central Support Partner
The right partner for Business Central support services understands the product both functionally and technically, offers a clear SLA, can support your specific extensions and integrations, overlaps with your working hours, and is transparent about pricing. Experience with businesses like yours matters more than the size of the firm.
Here are the questions I’d ask any provider of Business Central support services before signing:
- Who will work on our tickets, and will we have a named consultant?
- How do you handle major updates? Walk me through the process.
- Can you support our current extensions and integrations, even if you didn’t build them?
- Can you show me a sample monthly support report?
- What hours do you cover, and what happens with urgent issues outside them?
- Do you also handle development work if a ticket turns into a project?
That last question matters. Plenty of tickets start as “this doesn’t work” and end as “we need a small customization.”
Switching providers of Business Central support services is also easier than most owners assume. For Business Central online, the new partner is usually granted delegated admin access, reviews your environments and extensions, documents what it finds, and takes over the help desk once the handover is complete.
Signs Your Current Business Central Support Isn’t Working
You probably need better Business Central support services if tickets wait days for a first reply, the same issues keep coming back, updates break things in production, or nobody can explain how your system is configured.
Watch for these red flags:
- Your team has stopped logging tickets because “it won’t get fixed anyway”
- Users rely on spreadsheets to work around Business Central
- Major updates arrive as surprises
- You never receive reports on ticket volume or trends
- Every small request turns into a project quote
If three or more of those sound familiar, it’s time to compare other Business Central support services. Your ERP should make work easier, not harder.
Final Thoughts
Business Central is a strong ERP, but it isn’t set-and-forget. Microsoft improves it twice a year and your business keeps changing. Good Business Central support services keep all of those parts aligned so your team can focus on their real jobs instead of fighting the software.
If you want one partner for the help desk, troubleshooting, update testing, and ongoing improvements, take a look at our Business Central support services at New Wiz Tech. We’ve worked with Business Central since 2019, we support clients remotely across North America, Europe, and the Middle East, and our pricing is published upfront. Tell us what’s slowing your team down, and I’ll show you how we’d fix it.
Frequently Asked Questions
1. What are Business Central support services?
Business Central support services are ongoing services that keep Microsoft Dynamics 365 Business Central running smoothly after go-live. They typically include a help desk, troubleshooting, update testing, extension and integration maintenance, reporting fixes, user training, and permission reviews. Most companies get them from a Microsoft partner, either on an hourly basis or through a monthly support plan with an agreed SLA.
2. What is the difference between Business Central support and managed services?
Standard Business Central support services are mostly reactive: you raise a ticket and the partner fixes it. Business Central managed services add proactive ownership, such as monitoring, update testing, health checks, telemetry alerts, and regular reporting, usually for a fixed monthly fee. Managed services suit companies with integrations, customizations, or no internal admin, while ad hoc support suits smaller, simpler setups.
3. Does Microsoft provide direct support for Business Central?
Microsoft runs the Business Central online platform and fixes product bugs, but day-to-day technical support comes from your partner. The partner is the first line of contact, has delegated admin access to your environment, and escalates issues to Microsoft when they involve the platform or standard product. That’s why choosing the right partner for Business Central support services matters so much.
4. What should a Business Central SLA include?
A Business Central SLA should define severity levels with clear business-impact descriptions, response and resolution targets for each level, support hours and time zones, contact channels, an escalation path, monthly performance reporting, and a list of exclusions. It should separate response time, which is an acknowledgment, from resolution time, which is an actual fix or workaround.
5. How often does Business Central get updated?
Business Central online gets two major updates a year, starting in April and October, plus minor updates in the remaining months. After a major version is released, companies have a five-month update period and then a one-month grace period. After that, Microsoft enforces the update and may uninstall extensions that block it, so testing ahead of time is essential.
6. What does a Business Central maintenance plan include?
A Business Central maintenance plan usually includes monthly checks on updates, job queues, and integration logs, quarterly reviews of users, permissions, data growth, and performance, and twice-yearly sandbox testing ahead of each major release. A strong plan also covers telemetry monitoring and a clear process for restoring an environment if data ever gets damaged.
7. How much do Business Central support services cost?
Costs depend on the support model, hourly rate, number of users, level of customization, and coverage hours. Common options include hourly billing, prepaid block hours, fixed monthly managed services, and per-user pricing. Rates vary widely by region and provider. New Wiz Tech publishes its Business Central rates at $20 to $50 per hour so you can budget upfront.
8. Can I switch Business Central support partners?
Yes. Switching providers of Business Central support services is common and usually straightforward. Your new partner is granted delegated admin access, reviews your environments, extensions, and integrations, documents the current setup, and then takes over the help desk. Ask the outgoing partner for source code of any per-tenant extensions and any documentation they hold, so nothing important gets lost in the handover.
9. What are the most common Business Central troubleshooting issues?
The most common issues are posting errors from missing posting setups, missing dimensions, approval workflows stuck on absent users, permission errors, failed job queue entries, integration sync failures, slow pages or reports, and extensions that break after a major update. Most can be resolved quickly when the ticket includes the exact error message and steps to reproduce it.
10. How long should post-implementation support last?
Intensive post-implementation support, often called hypercare, usually runs for the first few weeks to three months after go-live, covering at least one full month-end close. After that, companies should move straight into ongoing Business Central support services rather than stopping, because updates, new users, and business changes keep creating new support needs.
