Business Central Health Check: What the Free Snapshot Covers
The eight areas a one-hour Business Central environment review examines, a check you can run on each, what the written report contains, and how it compares with the paid BC Health Check.

On this page
- Three questions to prepare for an environment review
- What a Business Central environment review covers
- Version and update posture
- Extension and customization inventory
- Integration map
- Data integrity signals
- Performance red flags
- Permissions and access
- Deployment discipline
- Support and knowledge risk
- What the written summary contains
- What the Snapshot deliberately leaves out
- Snapshot or Health Check: choosing the right Business Central audit
- Current Snapshot availability
- How to prepare for the hour
A Business Central health check is a structured review of how your environment is updated, extended, integrated, secured and supported. Bitta Apps runs it at two depths: the free BC Environment Snapshot, one hour on a screen share followed by a written two to three page summary within five business days, and the paid BC Health Check, a ten business day architecture review.
This article is for finance leads, controllers, operations managers and IT owners who run Business Central today and want an outside view of it. It covers the eight areas the Snapshot examines, a check you can run yourself in each area, what the written summary contains, what it leaves out, and how it compares with the paid Health Check.
Already running Business Central? Book the free BC Environment Snapshot: one hour on a screen share with a Business Central consultant, then a written summary of your environment within five business days.
Three questions to prepare for an environment review
Start by recording your Business Central version, the custom code installed and its owner, and the outside systems that send data into the environment. Mark any unknowns rather than treating an incomplete list as a complete inventory.
Use those questions to prepare for possible update conflicts, an integration failure or a support handover. These are review prompts, not findings about your environment. The Microsoft admin-center checks below apply to Business Central online.
What a Business Central environment review covers
The Snapshot terms on the pricing page list eight areas: version and update posture, extension and customization inventory, integration map, data integrity signals, performance red flags, permissions and access, deployment discipline, and support and knowledge risk. The table summarizes each one and the first thing you can check before anyone else looks.
Published review area | Questions to prepare | A check you can run first |
|---|---|---|
Version and update posture | Current version, update window, next scheduled update | Environment details in the admin center |
Extension and customization inventory | Installed apps, per-tenant extensions, who owns the source | The Extension Management page |
Integration map | What writes into Business Central, how, and who owns each connection | Job queue entries in Error status |
Data integrity signals | Stuck jobs, unposted backlogs, reconciliation gaps | Job Queue Log Entries |
Performance red flags | Slow reports, overlapping jobs, heavy code in the posting path | Recurring job schedules |
Permissions and access | Who holds SUPER and why | The Effective Permissions page |
Deployment discipline | Sandbox, testing, who can publish | When production was last copied to a sandbox |
Support and knowledge risk | Who understands the system and what is written down | Whether a failed job can be traced to its publisher |
The checks below are general preparation guidance. Examples from the published sample report are identified explicitly; they are not findings about your environment.
Version and update posture
Microsoft ships two major updates a year, starting in April and October, with minor updates in other months. According to Microsoft's guide to managing updates in the admin center, the default update window is 8:00 PM to 6:00 AM in the default time zone for the environment's country or region. Normally, an update that does not finish inside the window is canceled and rescheduled seven days later. An update explicitly allowed to run outside the window is not automatically canceled when the window ends. Before a major update, Microsoft checks per-tenant extensions for compatibility and emails the issues it finds to the notification recipients. Check who is on that recipient list and who will act on a compatibility warning.
Extension and customization inventory
The Extension Management page shows every installed app, including apps from Microsoft Marketplace (formerly AppSource) and per-tenant extensions built for you. The useful question is who holds the source code for each one. For each custom extension, record its maintainer and whether you can obtain the source code under your agreement. An unresolved ownership question is a reason to investigate before the next update. The article on how one small customization becomes technical debt traces that path step by step.
Integration map
For the integration map, list what connects to Business Central, by what method, and who owns each connection when it fails. Check whether authentication ownership and failure notifications are documented. Microsoft documents a Set Up Job Queue Notifications assisted setup in its guide to scheduling jobs with the job queue, which notifies the person who started a job, a job queue administrator, or both when an entry fails.
Data integrity signals
For data integrity signals, prepare any known stuck job queue entries, unposted document backlogs or reconciliation gaps. The same Microsoft guide explains that job queue entries stop running when there is an error and must be restarted manually, unless the Maximum No. of Attempts and Rerun Delay (sec.) fields allow retries. Compare the log with the transactions expected from a failed run. Treat any missing transactions as a question to investigate rather than assuming a restart recovered them.
Performance red flags
Slow reports and overlapping jobs show up here. Microsoft advises setting the largest interval you can for recurring job queue entries, because frequent recurring jobs can affect performance. Where the environment sends telemetry to Azure Application Insights, long-running SQL queries and job queue activity can be analyzed instead of guessed at. Compare recurring job schedules with the times users report delays. Investigate scheduling and telemetry before choosing a remedy.
Permissions and access
Microsoft's article on defining granular permissions states that the SUPER permission set lets a user access all objects specified in their license. The Effective Permissions page shows where each of a user's permissions comes from. Review whether each SUPER assignment is still needed. The published sample Snapshot report lists twenty-three users holding SUPER; that figure belongs to the sample, not to a typical environment.
Deployment discipline
This area asks whether a sandbox resembles production, what is tested before go-live, and who can publish. Microsoft lets admins copy a production environment to a sandbox. In the copy, job queue tasks are stopped and outbound HTTP calls from extensions are blocked by default. Check whether your test environment represents the configuration and workflows affected by the proposed change. See how to keep sandbox and production visibly different for controls that help distinguish the environments.
Support and knowledge risk
The last area asks who understands the customizations, what is written down, and what happens to the monthly close if that person is away for a month. Microsoft notes that the publisher of failing code can be found in the AL stack trace in the job queue log. For each customization and report, record a support owner and where its documentation is kept. Flag any item that depends on undocumented knowledge. The guide to a job queue support handoff shows how to write that knowledge down for each scheduled job.
What the written summary contains
The Snapshot report runs two to three pages, carries your company name, and arrives within five business days of the session. According to the pricing page, it contains:
Your top five findings, ranked by risk.
What each finding means for the business rather than for the code.
An effort range for each finding, not a single number.
The three things Bitta Apps would do first.
The report is yours to keep, to forward to your CFO, and to act on with any partner, including the one you work with today. The redacted sample Snapshot report illustrates how findings and scope are presented. Its five findings include an undefined order between two extensions subscribing to the same posting event, a per-tenant extension that fails Microsoft's compatibility check for the next major version, and a nightly integration that failed silently. It closes with a scope section that states what the one-hour review did and did not cover. Judge the offer on the deliverable rather than on the description.
What the Snapshot deliberately leaves out
The Snapshot does not include fixing anything, writing code, changing data, or a fixed-price migration plan. Those are paid engagements, and Bitta Apps says so before the session begins. The sample report describes the review as read-only.
Snapshot or Health Check: choosing the right Business Central audit
A Business Central audit in this sense is a technical and operational review of the system, not a financial statement audit. The Business Central health check page compares the two published options.
BC Environment Snapshot | BC Health Check | |
|---|---|---|
Cost | No cost | From $4,750; larger environments quoted up to $6,500 |
Duration | One hour on a screen share, report in five business days | Ten business days |
Scope | Eight areas, top five findings ranked by risk | Architecture review across configuration, extensions, integrations, performance, permissions and update risk |
Deliverable | Two to three page written summary with effort ranges | Written findings plus a prioritized remediation roadmap: what to fix now, next, and never |
Commitment | None | Fee agreed in writing before work starts; no further commitment required |
Choose the Snapshot for an initial written view of the environment. Choose the Health Check when you need a deeper architecture assessment and a remediation roadmap. Configuration changes, AL fixes, integration repair, data correction and ongoing support are separately agreed work.
Current Snapshot availability
Every Snapshot is run by a senior Business Central consultant, so spots are limited. Check the current Snapshot terms before booking. The offer has no cost and no obligation, and the report remains yours whether or not you hire Bitta Apps.
How to prepare for the hour
The session takes 60 minutes on Microsoft Teams. Mention the Snapshot in the booking note so the consultant can prepare. Three things make the hour more useful:
Bring two or three examples of work your team cannot complete reliably, such as a delayed close or a recurring job failure.
Bring the known owners of each app and integration, even if the list is incomplete.
If possible, have an administrator on the call who can open the admin center and the Extension Management page. Your administrator approves any access before the review.
Do not send passwords or confidential financial records through the booking form. If a specific problem is already visible, the support ticket checklist shows what to capture so the issue can be reproduced.
Next step. If you cannot answer the three questions at the top of this article, book the free BC Environment Snapshot: one hour on a screen share with a Business Central consultant, then a written summary of your environment within five business days. The report is yours, whatever you decide next.
FAQ
Frequently asked questions
What is a Business Central health check?
A Business Central health check is a structured review of how an environment is updated, extended, integrated, secured and supported. Bitta Apps offers it at two depths. The free BC Environment Snapshot is a one-hour screen share with a written summary within five business days. The paid BC Health Check is a ten business day architecture review with a prioritized remediation roadmap.
Is the Business Central health check free?
The BC Environment Snapshot from Bitta Apps is free and has no obligation. It includes a one-hour screen share and a written two to three page summary within five business days. The deeper BC Health Check is paid, starting at $4,750, with larger environments quoted up to $6,500 and the fee agreed in writing before work starts.
How long does a Business Central environment review take?
The BC Environment Snapshot takes one hour on a screen share, and the written summary arrives within five business days of the session. The paid BC Health Check runs for ten business days. Any fixes it recommends are separately scoped work.
What does a Business Central audit include?
A Business Central audit in this sense is a technical and operational review, not a financial statement audit. The BC Environment Snapshot looks at version and update posture, extensions and customizations, integrations, data integrity signals, performance, permissions, deployment discipline, and support and knowledge risk. The report ranks the top five findings by risk and gives an effort range for each.
Does a Business Central health check change anything in my environment?
The BC Environment Snapshot does not fix anything, write code, change data or produce a fixed-price migration plan. The published sample report describes the review as read-only. Configuration changes, AL fixes, integration repair and data correction are separately agreed work.
What should I prepare for a Business Central health check?
Bring two or three examples of work your team cannot complete reliably, the business impact, and the known owners of each app and integration. The access needed depends on the review, and your administrator approves it first. Do not send passwords or confidential financial records through the booking form.
Sources
Claims in this article were checked against the following on Nov 11, 2026.
- bittaapps.com/pricing
- bittaapps.com/contact?intent=snapshot
- bittaapps.com/connect/business-central-health-check
- bittaapps.com/downloads/bc-environment-snapshot-sample.pdf
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-update-management
- learn.microsoft.com/en-us/dynamics365/business-central/ui-extensions
- learn.microsoft.com/en-us/dynamics365/business-central/admin-job-queues-schedule-tasks
- learn.microsoft.com/en-us/dynamics365/business-central/ui-define-granular-permissions
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-environments-copy
- learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-overview