Skip to main content

Business Central Environment Blinking after update to v20


Business Central Updates after updating to version 20.x, there is a common problem which is observed.
The Business Central environment starts blinking as per the video below -


  • Business Central Online  v20


1. Restart the Business Central Environment:

Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment.

2. Ensure that your URL contains Tenant ID:

When you login into the Business Central Environment, make sure that your links are in the following formats

Sandbox :<SandboxEnvironmentName>/?sandbox=true

If you URL like or any other format without Tenant ID, chances are that you will end up with the issue.

Also, you can login through Admin Center URL - 

Connect from URL in BC Admin Center

3. Check the status if the installed or dependent apps are updated:

Go to Admin Center > Select Environment > Apps

If any app is in Install Update or Updating then ensure that they are Up to Date. 

4. Login into Environment through

I have observed that sometimes irrespective of all these steps being followed or not, the issue still does not resolve it self.
Hence, you can go to  > Select Chocolate Button on Top Left > Select the Environment you want to login

5. Login through Incognito Mode:

If nothing works, its possibly the browser cache. A best way to avoid browser cache is use Incognito Mode.
Use Incognito Mode > Login with your Office 365 Account > Open Business Central from Office 365

If the environment is still blinking after trying to login through all the above methods, try to login after 30mins

Note: If you are having this issue in Production and is not resolved after the steps provided, I recommend raising a Production Down [RED FLAG].


This issue has probably effected multiple Customers. I had few customers unable to login into Business Central, and with almost all of them the issue was resolved with above steps.
Let me know if you have any other resolution if you have found so we can share it together.

Hope this helps!!

Feel free to either drop comments or email me on for any suggestions.


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: Demonstration: 1. Install Business