Dynamics 365 Business Central Sign-In & Authentication Errors, Complete Fix Guide 2026
Why This Is Happening
I've seen this exact situation play out hundreds of times: you open Dynamics 365 Business Central on a Monday morning, you're staring at a blank screen or a broken interface, and your day is already derailed before it starts. Maybe the icons are missing, just empty boxes where your New and Edit buttons should be. Maybe personalization stopped working entirely and now every click on "Start Personalizing" returns a frustrating generic error. Or you pulled up the tablet client on your desktop, then opened the phone client in another tab, and now both are reporting the same client type, which is breaking your custom AL code in strange, hard-to-diagnose ways.
Here's the thing: Dynamics 365 Business Central sign-in and client authentication errors almost always come down to one of three root causes. Browser security settings are blocking resources the client needs to load. Profile or personalization configuration records have hit a compilation error, often silently, often after an update. Or the client session state is getting confused because Business Central relies heavily on browser session context to identify client types, and browsers don't always cooperate.
Microsoft's error messages don't help. "Sorry, something went wrong and personalization could not be started" tells you absolutely nothing actionable. Neither does a blank icon bar. The error message was written to avoid exposing internal system details, which makes sense from a security standpoint, but leaves you completely in the dark as an administrator or end user trying to fix the problem at 8 AM before a meeting.
Who runs into these issues most? In my experience, it's three groups. First, administrators who've recently pushed a Business Central update and didn't test profile configurations afterward. Second, developers running multiple Business Central client types simultaneously in the same browser for testing, a completely understandable workflow that causes a real client-type bug. Third, end users in organizations where internet security policies are locked down tight, blocking font downloads from external domains.
Business Central is a browser-dependent application. Unlike older Dynamics NAV deployments running thick clients on-premises, Business Central in the cloud lives inside your browser. That means browser settings, security zones, font permissions, and session handling all directly affect how the application behaves. When any one of those layers misbehaves, Business Central's error surface is surprisingly unhelpful.
The good news: every single one of these problems is fixable without a support ticket, as long as you know where to look. This guide walks you through all of them, in order from fastest to most complex. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into profile troubleshooting or browser configuration, try this. It resolves the majority of Dynamics 365 Business Central client issues I see, particularly the icon font problem and session-related client type errors.
Step 1: Clear your browser session and add Business Central to Trusted Sites. Open Control Panel in Windows 10 or Windows 11. Navigate to Network and Internet > Internet Options > Security > Trusted Sites. Click the Sites button. Add your Business Central web address, it typically follows the pattern https://businesscentral.dynamics.com. Click Close, then OK.
Step 2: Force-refresh the Business Central client. Close all browser tabs running Business Central. Open a new window, not a new tab, a new window, and navigate directly to your Business Central URL. If you were seeing missing icons before, they should now be visible.
Step 3: If you're testing tablet and phone clients simultaneously, stop doing it in the same browser. Open each client type in a completely separate browser window. Business Central uses the browser session to determine the current client type, and two clients in the same session will return the same ClientType. This is expected behavior, not a bug, it's how the platform works. Separate windows, separate sessions, correct client type detection.
That combination, trusted site fix plus separate browser windows, resolves a significant chunk of Business Central client authentication and display issues right away. If you're still stuck after that, keep reading.
This step directly addresses the missing icon font issue in Dynamics 365 Business Central. The icon font, the one that renders UI elements like the plus sign on the New action button, is a web font that needs to download from the Business Central server. When your browser's security settings block font downloads, you get a broken, icon-free interface.
Here's exactly how to fix it on Windows 10 and Windows 11:
1. Open the Start menu and search for "Control Panel"
2. Click Control Panel → Network and Internet → Internet Options
3. Click the Security tab
4. Select "Trusted sites" from the zone list
5. Click the Sites button
6. In the "Add this website to the zone" field, enter:
https://businesscentral.dynamics.com
7. Click Add
8. Click Close, then click OKIf your Business Central instance is hosted on a custom domain, common in on-premises or private cloud deployments, add that domain instead. The domain you're looking for is whatever appears in your browser's address bar when you're logged into Business Central.
After you've done this, close all your Business Central browser tabs. Open a fresh browser window and log back in. You should see the full icon set restored, the plus signs, edit icons, search icons, all of it. If the icons are still missing after adding the site to Trusted Sites, check whether your browser has font download explicitly disabled in its advanced settings. In Internet Explorer's Internet Options, under Advanced > Security, make sure "Download fonts" is enabled.
On Microsoft Edge specifically, Trusted Sites settings from Internet Options do carry over, but Edge's own content blocking settings can override them. If you're on Edge, also check edge://settings/content/fonts and make sure font loading isn't blocked.
This fix is specifically for developers and testers who run the Dynamics 365 Business Central tablet client and phone client at the same time. The symptom is clear: you call CurrentClientType in your AL code, and both clients return the same value. That breaks any logic that branches on client type, screen layouts, action visibility, mobile-specific workflows.
Why does this happen? Business Central determines the current client type from the browser session context. When you open two different client URLs in the same browser session, even in separate tabs, they share session state. Business Central reads that shared state and returns the same ClientType for both. It's a session architecture limitation, not a code bug.
The fix is to isolate each client into its own browser window:
Tablet client: Open in Window 1 (e.g., Chrome Window 1)
Phone client: Open in Window 2 (e.g., Chrome Window 2, or a
separate browser entirely like Edge)Each browser window maintains its own session. With separate sessions, CurrentClientType correctly identifies each client type independently.
If you need to test both simultaneously as part of an automated or repeatable workflow, consider using browser profiles. Chrome and Edge both support multiple profiles, each with their own isolated session storage. Create a dedicated browser profile for tablet testing and another for phone testing. That way you don't need to manage separate windows manually, each profile keeps its client context clean.
For your AL code, make sure you're also evaluating DefaultClientType alongside CurrentClientType if you need to understand the default context for a given deployment. These two methods serve different purposes and understanding both helps you write more accurate client-aware logic. More on the distinction in the FAQ section below.
If profile configuration in Dynamics 365 Business Central won't start and you're getting the "personalization could not be started" error, this is your entry point. You need tenant administrator permissions in Business Central to perform these steps.
Here's how to get the full picture of what's broken:
1. In Business Central, open the Tell Me box (use the search icon
or press Alt+Q)
2. Type "Profiles" and select the related link
3. On the Profiles page, find and open the profile card for the
profile that's failing
4. Choose "Manage customized pages" from the profile card
5. Click the "Troubleshoot" buttonThe Troubleshoot button is the key diagnostic tool here. It generates a list of all configuration records associated with that profile that contain compilation errors. This is information Business Central has all along but doesn't surface through the normal error message. Once you can see the specific records causing failures, you have two paths forward: delete those records or export and fix the underlying AL code.
Before you do either, take a screenshot of the current configuration. The official guidance is clear on this, once you delete a profile configuration record, that customization is gone. Screenshots give you a manual reference if you need to rebuild it. I've seen teams skip this step and spend hours recreating lost configurations. Don't skip it.
If the Troubleshoot button shows only one or two failing records and they're minor tweaks, deletion is often the fastest path. If the errors are extensive or involve important customizations, use the export approach described in Step 4.
This approach is available from Business Central version 16.2 onward and is the right move when you want to preserve your profile customizations rather than delete them. It lets you extract the AL code, fix the compilation error, and reimport a clean version.
1. In the Tell Me box, type "Profiles" and open the Profiles page
2. Click the "Export Profiles" button
3. A message will appear warning you that there are errors in some
profiles, click Yes to proceed with the export anyway
4. This downloads a .zip file containing the AL code for all
profiles on your tenant
5. Unzip the downloaded file and locate the AL file for the
specific page customization with errorsThe AL files follow a consistent naming pattern that makes it easy to find the right one:
PageCustomization.<target-page-name>.Configuration<id>.alOpen that file in a text editor or, better yet, in VS Code with the AL Language extension installed. The extension gives you proper compiler diagnostics, which means it highlights exactly where the broken code is, much easier than reading raw error messages. Cross-reference the error details from the Troubleshoot page you used in Step 3. Locate the code block causing the issue and remove or correct it.
Once the fix is in place:
1. Repack the fixed AL file into a new .zip archive
2. Return to the Profile List page in Business Central
3. Click "Import Profiles"
4. Follow the import wizard and select the fixed profile
when prompted
5. After import, go back to "Manage customized pages" for that
profile and confirm no errors are listedA clean list in that final step means the profile is healthy again. Profile configuration should now start without errors.
User personalization errors in Dynamics 365 Business Central are a close cousin to profile configuration errors, but they affect individual users rather than shared profiles. The same "personalization could not be started" message appears, but the fix path is different because the records live in a different part of the system.
You still need tenant administrator permissions. Here's the process:
1. Open the Tell Me box and type "Personalized Pages"
2. Select the related link
3. On the Personalized Pages page, open the filter pane
(use the funnel icon or press Shift+F3)
4. Filter by the impacted user, filter on the User Name column
to narrow down to just that user's records
5. With the filtered records visible, click the "Troubleshoot"
buttonYou'll get a list of all personalization records for that user that contain compilation errors. This is exactly the same diagnostic surface as the profile troubleshooting path, it just applies to user-level records instead of profile-level records.
From here, use the Manage action to delete the specific records with errors. Yes, this removes those personalizations for the user, they'll need to redo any layout changes they made. That's not ideal, but it's the supported path when personalization records hit compilation failures.
Brief the affected user before you delete anything. Tell them what customizations will be lost and give them time to document what they want to preserve. A two-minute conversation saves a frustrated support ticket the next day.
After deletion, have the user log out of Business Central completely, close their browser, reopen it, and log back in. Personalization should now start cleanly. They can then rebuild any customizations they need on the freshly cleared slate.
Advanced Troubleshooting
If you've worked through all five steps above and Dynamics 365 Business Central is still misbehaving, you're likely dealing with a more complex environment. Let's go deeper.
Enterprise Environments: Group Policy and Browser Restrictions
In domain-joined machines managed by Active Directory or Azure AD, your browser security zone settings may be locked by Group Policy. You can add Business Central to your Trusted Sites all day in Internet Options, but if a GPO is enforcing those settings, your change will be reverted at the next policy cycle, typically every 90 minutes in most enterprise environments.
To check if this is happening, open the Registry Editor (regedit.exe) and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\
CurrentVersion\Internet Settings\ZoneMap\DomainsIf your Business Central domain appears here, it's being managed by policy. The fix needs to happen in Group Policy, not on the local machine. Contact your domain administrator and request that the Business Central domain be added to the Trusted Sites zone via GPO, specifically under Computer Configuration > Windows Settings > Security Settings > Internet Explorer Maintenance > Security > Security Zones and Content Ratings, or the equivalent user configuration path for user-scoped policies.
Checking the Event Viewer for Business Central-Related Errors
For on-premises deployments or hybrid setups, the Windows Event Viewer on the Business Central server can surface errors that the client-side interface completely hides. Open Event Viewer on the server, navigate to Windows Logs > Application, and filter by Source for entries from the Business Central service. Event ID ranges in the 40000s and 50000s are particularly relevant for session and authentication failures.
Look for entries timed close to when users report the authentication error. Common patterns include credential validation failures from the NST (NAV Server tier) and errors in the tenant context resolution that cause client type detection to fall back to default values.
Microsoft 365 Integration Permission Errors
If your users can see Business Central but are hitting a permissions error despite having Microsoft 365 access enabled, that's a distinct issue from the personalization and icon problems. The Business Central and Microsoft Teams integration requires specific permission assignments in the Business Central admin center, not just in Azure AD. Make sure the user's Business Central license assignment is correct and that they haven't been inadvertently removed from the relevant permission sets during a recent update cycle.
Profile Configuration in Version-Specific Scenarios
The Export Profiles fix for profile compilation errors is only available from Business Central version 16.2 onward. If your tenant is on an older version and you can't upgrade immediately, your only recourse for profile compilation failures is the Delete path, there's no export-fix-reimport option. This is a strong argument for keeping your Business Central version current. Microsoft's SaaS release cadence means most cloud tenants should be on a recent enough version, but if you're on-premises, version lag is a real risk.
Prevention & Best Practices
The best Business Central support ticket is the one you never have to open. Most of the sign-in and authentication issues covered in this guide are preventable with a little upfront configuration discipline. Here's what I'd tell every admin deploying Dynamics 365 Business Central for the first time, or inheriting a deployment that someone else set up and walked away from.
Test profile configurations after every update. Business Central updates can introduce AL compiler changes that break previously valid profile customizations. After any major update, run through the Troubleshoot step on your critical profiles before end users hit work in the morning. A five-minute check during the off-peak window is far better than a Monday morning incident.
Document profile customizations proactively. Maintain a written or screenshot-based record of every customization applied to your key profiles. When you need to delete and rebuild a broken configuration, this documentation is the difference between a 10-minute recovery and an hours-long reverse-engineering session.
Standardize your testing workflow for AL client-type code. If your developers are writing code that checks CurrentClientType or DefaultClientType, establish a written convention: tablet client testing in one dedicated browser profile, phone client testing in another, always separate. Put it in your team's development standards document so new developers don't discover the same-session issue the hard way during a release window.
Push Business Central to Trusted Sites via Group Policy, not manually. If you have more than a handful of users, manual browser configuration doesn't scale and creates inconsistency. Add the Business Central domain to Trusted Sites through GPO so every domain machine gets the right configuration automatically, regardless of who set up the machine or what browser they're using.
- Add
https://businesscentral.dynamics.comto Trusted Sites via Group Policy before rollout, eliminates the icon font problem entirely for all users - Schedule a monthly profile health check: run Troubleshoot on all critical profiles and catch compilation errors before they affect users
- Keep your Business Central tenant updated, version 16.2+ export/import for profile fixes saves enormous time compared to manual deletion and rebuild
- Train your help desk to ask "which browser and are multiple BC clients open?" as their first two questions, solves the client type issue in 30 seconds
Frequently Asked Questions
Why does Business Central return the wrong client type when I open the tablet and phone clients at the same time?
Business Central identifies the current client type from the browser session context, not from the URL alone. When you open both the tablet client and the phone client in the same browser session, even in separate tabs, they share that session state, so CurrentClientType returns the same value for both. The fix is simple: run each client in a completely separate browser window, which creates separate sessions. If you test client types regularly, set up dedicated browser profiles for each client type so you never accidentally run them in the same session again. This applies to any code you write that checks CurrentClientType, always test it in an isolated window.
What's the difference between CurrentClientType and DefaultClientType in Business Central?
CurrentClientType returns the client type of the active session, the one currently running in the browser. DefaultClientType returns the client type that the Business Central deployment is configured to serve by default, independent of any active session. For most conditional display logic, showing or hiding UI elements based on whether someone is on a phone versus a tablet, you want CurrentClientType. DefaultClientType is more relevant when you need to know the deployment's intended context, such as during server-side logic that runs outside an active user session. If you're branching your AL code based on mobile versus desktop context for a specific user's active interaction, always use CurrentClientType.
The icon font is missing in Business Central, I can see blank boxes instead of icons. How do I fix it?
This is a browser font download restriction issue. Business Central loads its UI icon set as a web font, and if your browser's security settings block font downloads, the icons won't render. The fix is to add your Business Central web address to your browser's Trusted Sites zone: open Control Panel, go to Network and Internet > Internet Options > Security > Trusted Sites, click Sites, add your Business Central URL, and click OK. After that, close all Business Central tabs and reopen them fresh. If you're in a corporate environment, this setting may be controlled by Group Policy, in that case, ask your IT admin to add the domain to Trusted Sites via GPO, because your manual change will be overwritten at the next policy refresh.
How do I find out which profile customization record is causing the "personalization could not be started" error?
Business Central has a built-in diagnostic tool for this, though it's not obvious from the error message. As a tenant administrator, go to the Tell Me box, search for "Profiles," open the profile card for the affected profile, choose "Manage customized pages," and click the Troubleshoot button. This surfaces a list of all configuration records for that profile that contain compilation errors, the exact records responsible for the failure. Once you can see them, you have two options: delete them (which removes those customizations permanently) or export the profile, fix the AL code, and reimport it. The export-fix-reimport path is available from version 16.2 onward and is the better choice when the customizations are important to preserve.
Can I recover customizations I deleted when fixing a Business Central profile configuration error?
Not automatically, which is why Microsoft's own documentation recommends taking screenshots before deleting any profile configuration records. Once you delete a profile configuration record through the Manage action, that specific customization is gone from the database. If you have screenshots, you can manually rebuild the customizations on the now-clean profile. If you have a recent database backup of your Business Central tenant (more relevant for on-premises deployments), it may be possible to restore individual records, but that's a complex operation that typically requires Microsoft support or a DBA. For cloud tenants, the export-fix-reimport workflow in version 16.2+ is specifically designed to help you avoid the delete-and-lose scenario, use it whenever possible.
What do I do if user personalization won't start for a specific user but works fine for everyone else?
This is a user-specific personalization record compilation error, not a system-wide profile issue. As a tenant administrator, open the Tell Me box and search for "Personalized Pages." On that page, use the filter pane to show only records belonging to the affected user. Then click the Troubleshoot button to see exactly which of that user's personalization records are failing. Use the Manage action to delete the records with errors, this clears the bad data and lets personalization start again. The user will lose the specific personalizations tied to the deleted records, so give them a heads-up beforehand and ask them to document what they had customized. After deletion, have the user fully close and reopen their browser before logging back in to ensure the session state is fresh.