Fix Dynamics 365 Business Central Errors (2026)

Microsoft Fix Intermediate 14 min read Official Docs Grounded Updated April 20, 2026
What's in This Guide
  1. Why This Happens
  2. The Quick Fix
  3. Step-by-Step Solution
  4. Advanced Troubleshooting
  5. Prevention & Best Practices
  6. FAQ

Why This Is Happening

Picture this: it's end-of-month, your finance team is trying to post the general journal, and Business Central either refuses to load, throws a cryptic permission error, or just spins indefinitely at the login screen. I've seen this exact scenario on dozens of deployments , and the maddening part is that Microsoft's own error messages rarely tell you why. You get something like "You do not have the following permissions on TableData" and no indication of which permission set you're actually missing.

Dynamics 365 Business Central is a cloud-first business management platform built for small and mid-sized organizations. It handles finance, sales, purchasing, inventory, warehouse management, project management, service management, manufacturing, and more , which means there are a lot of moving parts. More moving parts means more ways things can go sideways.

The most common root causes I see break down into four buckets:

  • Permission and license mismatches, A user has an Essentials license but is trying to access Premium-tier features like Service Management or Manufacturing. Business Central will block them at the table-data level, and the error message won't explicitly say "wrong license tier."
  • Environment and tenant configuration issues, Sandbox environments that have gone stale, production environments pointing to the wrong company, or a freshly created environment that hasn't fully propagated through Microsoft's infrastructure yet.
  • Extension and app conflicts, Third-party extensions from Microsoft AppSource, or AL customizations deployed by a partner, that conflict with a recent Business Central platform update. Microsoft pushes updates to Business Central online on a rolling schedule, and sometimes an extension built against an older API surface breaks silently.
  • Integration failures, Broken connections to Power Automate flows, Power BI datasets that won't refresh, or Shopify sync jobs that stall mid-run. These almost always trace back to expired OAuth tokens or misconfigured app registrations in Entra ID (formerly Azure Active Directory).

What makes Business Central troubleshooting particularly tricky is that the platform surfaces errors at multiple layers simultaneously, the browser client, the server-side AL runtime, and the underlying Azure infrastructure, and those layers don't always agree on what went wrong. I've spent hours chasing what looked like a network issue that turned out to be a job queue entry stuck in a "In Process" state that was blocking everything downstream.

The good news: most of these issues are fixable without calling Microsoft Support, and this guide walks through every major category. Browse all Microsoft fix guides →

The Quick Fix, Try This First

Before you go deep on diagnostics, run through this 90-second checklist. I'd estimate it resolves about 40% of Business Central issues without any further work.

Step 1, Hard refresh the browser. Business Central is a web application, and cached JavaScript or session state causes a surprising number of "broken" experiences. In Chrome or Edge, press Ctrl + Shift + R (or Cmd + Shift + R on Mac) to force a full reload bypassing cache. If you're using the Business Central desktop app, close it entirely and relaunch.

Step 2, Sign out and sign back in. Go to businesscentral.dynamics.com, click your profile avatar in the top-right corner, and choose Sign out. Clear your browser cookies for the dynamics.com domain, then sign back in. This forces a fresh token exchange with Microsoft Entra ID and fixes a large class of authentication-related errors.

Step 3, Confirm you're in the right environment and company. Business Central supports multiple environments (Production, Sandbox) and multiple companies within each environment. In the top-right corner, you'll see the environment name and company name displayed. Click the company name to open the Switch environment or company panel. More than once I've found a user insisting Business Central is "broken" when they were just looking at an empty sandbox instead of their live production company.

Step 4, Check Microsoft's service health dashboard. Go to the Microsoft 365 Admin Center, navigate to Health > Service health, and filter by Dynamics 365. If there's an active incident, the fix is simply waiting, no amount of local troubleshooting will help if Microsoft's infrastructure is degraded.

If none of those resolved the issue, keep reading. The step-by-step section covers every major failure category in order from most to least common.

Pro Tip
Always test in an InPrivate or Incognito browser window before doing anything else. Business Central issues caused by browser extensions (ad blockers, password managers, corporate proxy injectors) disappear immediately in private mode, saving you from chasing a ghost for two hours.
1
Diagnose and Fix Business Central Login & Sign-In Errors

The Business Central login process runs through Microsoft Entra ID (formerly Azure Active Directory), and when it breaks, users typically see one of three errors: a generic "We're having trouble signing you in" page, an error code like AADSTS50076 (MFA required), or they get past login but land on a blank white page at businesscentral.dynamics.com.

For MFA-related errors, the fix is on the Entra ID side. As an admin, go to the Microsoft 365 Admin Center, navigate to Users > Active users, find the affected user, and under the Account tab, check their MFA registration status. If they haven't completed MFA setup, Business Central will block them even if their license is active.

For blank white page issues after login, this is almost always a license assignment problem. Navigate to:

Microsoft 365 Admin Center
→ Users → Active users
→ [Select the user]
→ Licenses and apps tab

Confirm the user has either a Dynamics 365 Business Central Essentials or Dynamics 365 Business Central Premium license assigned. If the license is assigned but the user still can't access Business Central, scroll down in the same panel and make sure the Dynamics 365 Business Central app under that license is toggled on, licenses can be assigned while individual apps within them are disabled.

After fixing license assignments, allow 5–10 minutes for propagation, then have the user sign out completely, clear browser cookies, and sign back in. You should see the Business Central home page load with their role center.

2
Resolve Permission Set Errors Blocking Pages or Actions

This is the single most common Business Central error category I deal with. The typical symptom is a user can log in fine, but when they try to open a specific page, say, the General Journals list, or the Purchase Orders page, they get a dialog that says something like: "You do not have the following permissions on TableData 'Purchase Header': Read".

Here's the thing about that error: it tells you the table name but not which permission set is supposed to grant access. To diagnose properly, go to:

Search (Alt + Q) → "Permission Sets"
→ Find the set assigned to the user
→ Click the set name → view individual permissions

A faster method is to use the built-in permission troubleshooter. In Business Central, search for "Effective Permissions". Enter the affected user's name and the table or page ID they're being blocked from. The tool shows exactly which permission sets are granting or denying access, far more useful than guessing.

Business Central ships with a library of predefined permission sets (like D365 BUS FULL ACCESS, D365 BASIC, D365 JOURNALS, POST) that map to common job roles. To assign them to a user:

Search → "Users"
→ Select the affected user
→ User Permission Sets section
→ Add Line → choose the appropriate permission set

One important nuance: users on an Essentials license cannot be granted permission sets that expose Premium-only features (Manufacturing, Service Management). If you try, Business Central will silently ignore those permissions. Verify the user's license tier matches the functionality they need, this is documented in the official Business Central licensing guide and determines the ceiling of what any permission set can actually do.

After saving the permission changes, have the user refresh their browser. They should be able to access the previously blocked page immediately, no sign-out required for permission set changes.

3
Fix Job Queue Entries That Are Stuck "In Process"

Job queues in Business Central handle background processing, recurring tasks like posting sales orders in batch, running MRP/MPS planning routines, syncing data with Shopify, or triggering Power Automate flows on a schedule. When a job queue entry gets stuck in "In Process" status, it doesn't just sit there harmlessly. It blocks other entries in the same job queue category and can bring automated workflows to a halt.

I've seen this happen most often after an unplanned server-side restart or a Business Central platform update that terminates background sessions mid-execution. The session dies, but the job queue entry never gets updated back to "Ready" or "Error."

To find and fix stuck entries:

Search → "Job Queue Entries"
→ Filter by Status = "In Process"
→ Select the stuck entry
→ Actions → Set Status to On Hold
→ Then: Actions → Set Status to Ready

This manually resets the entry and releases the lock. If the entry immediately goes back to "In Process" without doing any visible work, you likely have a code error in the codeunit or report that the job queue is trying to run. In that case, set the entry to On Hold, check the Job Queue Log Entries page for error messages from recent runs, and address the underlying code or configuration problem before re-enabling it.

For scheduled jobs that run critical financial processes, like automatic posting of recurring journal lines or automatic cost adjustment, set the Rerun Delay (sec.) field on the job queue entry. A value of 60 means if the job fails, it automatically retries after 60 seconds rather than requiring manual intervention. This alone has saved several of my clients from overnight processing failures they didn't discover until morning.

When everything is working correctly, you'll see the job queue entry status cycle through "Ready" → "In Process" → "Ready" (or "Finished" for one-time jobs) on its defined schedule.

4
Repair Broken Extension Installations and App Conflicts

Business Central's extension system, built on Microsoft's AL language and distributed through Microsoft AppSource, is one of its most powerful features. It's also a reliable source of headaches after platform updates. When Microsoft updates the Business Central runtime (which happens automatically for online tenants), extensions compiled against older platform versions can break in ways that range from cosmetic (a page action disappears) to catastrophic (the entire company fails to open).

As an admin, your diagnostic starting point is the Extension Management page:

Search → "Extension Management"
→ Review the Status column for each installed extension
→ Any extension showing "Failed" or without a green checkmark needs attention

For a failed extension, try uninstalling and reinstalling it:

Extension Management
→ Select the problematic extension
→ Manage → Uninstall
→ Wait for confirmation
→ Manage → Install (if available) or reinstall from AppSource

If an extension can't be uninstalled because it's locked by another extension that depends on it, you'll need to uninstall the dependent extensions first, working backwards through the dependency chain. The Extension Management page shows publisher information, use that to contact the extension vendor if the issue persists after reinstall, since the fix may require a new version of their app compiled against the current platform.

For extensions developed in-house or by a partner using AL, the extension needs to be recompiled against the current application and platform versions specified in the app's app.json file and redeployed. The partner should be running the current version of the AL Language extension in VS Code and targeting the correct target runtime before publishing the fix.

Once a healthy extension version is installed, navigate to the affected pages to confirm they load correctly. If users had personalized those pages before the extension broke, their personalizations may need to be cleared via Search → "Personalization" and selecting Clear Personalized Pages.

5
Restore Power BI, Power Automate, and Shopify Integration Connections

Business Central's integrations with Power BI, Power Automate, and Shopify are genuinely powerful, but they all rely on OAuth 2.0 tokens that expire, and service-to-service connections that break when passwords change or app registrations are modified in Entra ID. When they break, the symptoms vary: Power BI reports show "Credentials expired" or just refuse to refresh; Power Automate flows fail with a 401 Unauthorized or Connection expired error; Shopify sync jobs log errors like "Authentication failed for store."

Fixing Power BI connections: In Business Central, search for "Report Layout Selection" or go to the Power BI-embedded reports directly. If you see a yellow banner saying the connection is broken, click Fix Connection and sign in with the account that owns the Power BI workspace. For admin-level fixes, go to the Power BI Service, navigate to Settings → Connections & Gateways, find the Business Central data source, and refresh the credentials there.

Fixing Power Automate flows: Open Power Automate, go to My Connections, find the Business Central connector, and click Fix Connection. Re-authenticate. Then go to My Flows and manually run the failed flow once to confirm the connection works before relying on it for scheduled triggers.

Fixing Shopify sync:

Search → "Shopify Shops"
→ Select your shop record
→ Actions → Test Connection

If the test fails, the Shopify access token has likely been revoked (this happens if someone regenerated the API key in the Shopify admin). You'll need to go to your Shopify admin, generate a new private app API key, and update the Shopify Access Token field in Business Central's Shopify Shops page accordingly. After saving, run Synchronize Customers and Synchronize and Fulfill Sales Orders to verify the connection is live.

A successful connection test shows a green "Connection successful" confirmation dialog. If you see that, your integration pipelines are healthy and scheduled sync jobs will resume on their next trigger.

Advanced Troubleshooting

If the steps above haven't resolved your issue, it's time to go deeper. This section covers the diagnostic tools that most Business Central admins don't know exist, and they're genuinely powerful.

Reading the Business Central Telemetry and Event Log

Business Central supports Azure Application Insights telemetry, which gives you server-side visibility into errors, slow queries, and failed background operations. If your organization has telemetry configured, go to your Azure portal, find the Application Insights resource linked to your Business Central environment, and run this KQL query to surface recent errors:

traces
| where customDimensions.eventId startswith "AL"
| where severityLevel >= 3
| order by timestamp desc
| take 50

This surfaces AL runtime errors with the exact error message, the codeunit and line number where it occurred, and the user session that triggered it. It's night-and-day better than trying to reproduce issues manually.

To enable telemetry for your environment if it isn't already configured: go to the Business Central Admin Center at https://businesscentral.dynamics.com/[tenant-id]/admin, select your environment, and under the Application Insights Key field, paste your Azure Application Insights instrumentation key. Microsoft documents this capability under their telemetry overview guidance, it's free to configure (you pay for Azure ingestion, which is minimal for most tenants).

Auditing Changes with Change Log

Business Central has a built-in change log that tracks who changed what and when, at the record and field level. If data looks wrong, a vendor payment was applied to the wrong invoice, a customer's credit limit was changed without authorization, the change log is your first stop:

Search → "Change Log Entries"
→ Filter by Table Name and/or Date
→ Review the "Changed By" and "Old Value" / "New Value" columns

If the change log isn't capturing the tables you care about, set it up via Search → "Change Log Setup". You can enable logging for individual tables and specify whether to log insertions, modifications, deletions, or all three.

Environment-Level Issues in the Admin Center

Some problems aren't fixable from within Business Central itself, they require the Business Central Admin Center. Access it at https://businesscentral.dynamics.com/[your-tenant-id]/admin. From there you can:

  • Check environment status (Active, Updating, Error)
  • Review scheduled update windows and defer updates if an extension isn't compatible yet
  • Create a new sandbox environment copied from Production for safe testing
  • Restore a Production environment to a point-in-time backup (up to 30 days back)

The point-in-time restore capability is something many admins don't know about until they desperately need it. If a bad data import or a runaway customization has corrupted your production data, you can restore to a prior state without losing more than a few hours of transactions.

When to Call Microsoft Support
Escalate to Microsoft Support when: your environment shows a persistent "Error" status in the Admin Center that doesn't self-resolve within 2 hours; you need a point-in-time restore beyond what the Admin Center self-service allows; you're seeing data-loss symptoms that aren't explained by change log entries; or a platform update has broken core functionality in a way that's not tied to any extension. For license and billing issues, escalate through the Microsoft 365 Admin Center support channel, not the technical support path, they're routed differently and the billing team resolves them faster.

Prevention & Best Practices

Every Dynamics 365 Business Central issue I've ever diagnosed could have been caught earlier, or avoided entirely, with a handful of proactive habits. Here's what separates organizations that have smooth Business Central operations from ones that are constantly fighting fires.

Manage your update schedule deliberately. Business Central online receives major updates twice a year (Wave 1 in April, Wave 2 in October) plus monthly minor updates. You can defer a major update by up to 30 days from the Admin Center. Use that window. Coordinate with your extension vendors to confirm compatibility before applying the update to Production. Test the update in a Sandbox copy of Production first, this is exactly what the Sandbox environment type is designed for.

Audit permissions quarterly. User roles change. Employees leave. Job responsibilities shift. A quarterly review of permission set assignments, especially for users who have accumulated permissions over years, prevents both security exposure and the confusion of users having access to functionality that's irrelevant to their current role. Business Central's built-in User Security Status report (search for it) gives you a clean overview of every user's permission sets and license tier.

Enable telemetry before you need it. Configuring Application Insights telemetry when everything is working means you have historical data available when something breaks. Trying to enable it after an incident means you have no data from when the incident actually occurred. Takes 10 minutes to set up; saves hours of blind debugging.

Document your extension inventory. Keep a simple record of every extension installed in your Production environment, publisher name, version number, and the purpose it serves. When a platform update causes a problem, you'll know immediately which extensions to investigate. Without that record, you're starting from zero.

Quick Wins

Frequently Asked Questions

Why does Business Central say I don't have permission even though I'm an admin?

Being a Microsoft 365 admin doesn't automatically make you a Business Central admin. Business Central has its own permission system separate from Microsoft 365 roles. You need the SUPER permission set assigned to your user within Business Central itself, not just an admin role in Entra ID. Have an existing Business Central admin go to Search → Users, find your account, and add the SUPER permission set. If no one has that access, you can assign it from the Microsoft 365 Admin Center by navigating to Admin Centers → Business Central and using the Manage User option there.

Business Central is taking forever to load, how do I speed it up?

Slow loading in Business Central online is usually caused by one of three things: a slow internet connection (Business Central is very latency-sensitive, it makes dozens of round-trips per page load), an overloaded browser with too many tabs or extensions, or a specific page that has too many lines in a list and is loading without filters. Start by testing in an InPrivate window to rule out browser extensions. Then check if the slowness is on all pages or just one specific page, if it's one page, add filters to reduce the dataset it's loading. For company-wide slowness, check Microsoft's service health dashboard in the Microsoft 365 Admin Center to see if there's an active infrastructure issue in your region.

How do I fix "The record in table 'Sales Header' is currently locked by another user" error?

This error means another active session is holding a database lock on that record, typically because someone else has it open in edit mode, or a background job (like a posting routine) is mid-process on it. Go to Search → Sessions in Business Central to see all active user sessions. If you can identify the session holding the lock (look for sessions with the same user who reported opening that record), you can end it from there, but only do this if you're sure the session isn't in the middle of a critical posting operation, as terminating an active posting can leave partial data. In most cases, waiting 2–3 minutes for the other user to finish and close the record resolves it naturally.

My Power BI reports embedded in Business Central stopped working after a password change, how do I fix it?

When the account used to connect Business Central to Power BI changes its password (or is subject to a Conditional Access policy change), the OAuth token becomes invalid and the embedded reports break. In Business Central, search for Power BI Reports and look for a yellow "Fix Connection" banner, click it and re-authenticate with the correct account. If that prompt doesn't appear, go to the Power BI Service directly, navigate to Settings → Connections & Gateways → Data Sources, find the Business Central data source, and click Edit Credentials to refresh them. The connection typically restores within a few minutes after re-authentication.

Can I roll back Business Central to before a bad update was applied?

For Business Central online, you cannot roll back the platform version itself, Microsoft controls that. But you can restore your environment's data to a point in time before the update caused problems, up to 30 days back, using the point-in-time restore feature in the Business Central Admin Center at businesscentral.dynamics.com/[tenant-id]/admin. Select your environment, click Restore, and choose a restore point from before the issue began. Keep in mind this restores all data, so any transactions posted after that point will need to be re-entered. For extension-related breakage, the right fix is usually updating the extension to a compatible version rather than restoring the environment.

How do I move data from our old on-premises Dynamics NAV to Business Central online?

Microsoft provides a built-in cloud migration tool for moving from on-premises Dynamics NAV, Dynamics GP, and earlier Business Central versions to Business Central online. In your online Business Central environment, search for Cloud Migration Setup and run the assisted setup wizard. It installs a data replication pipeline that connects to your on-premises database over a self-hosted integration runtime (a small agent you install on a server that has database access). The tool migrates your historical data without requiring downtime on the on-premises side, and you control the cutover. Microsoft's official guidance recommends doing a test migration to a Sandbox environment first to validate data integrity before running the production cutover.

Related Microsoft Fix Guides

Microsoft Fix
How to Fix Windows Update Errors (Error 0x80070003 & More)
Microsoft Fix
Fix Microsoft 365 Sign-In Problems, Complete Guide
Microsoft Fix
Azure Active Directory Troubleshooting Guide
Browse All
5,000+ Microsoft Fix Guides →
H
Sai Kiran Pandrala
Our team includes certified Microsoft engineers, Azure architects, and system administrators with 10+ years of enterprise IT experience. Every guide is written from hands-on troubleshooting, not guesswork. We test every fix before publishing.