Skip to main content

Business Central Admin Center Upgrade with Business Central Wave 2 2020


In this blog, I'm going to demonstrate the newly available Business Central Admin Center coming up in October for the 2020 Release Wave 2 


  • Business Central Admin Center


1. Changes to Business Central Admin Center:
After you login in Business Central Admin Center, you will observe a couple of changes in the Admin Center on the Main Screen directly. The changes are missing actions, additionals sections.

2. Changes on Environment Card Page:
After selecting the environments, you will notice key things such as renaming the environment.

3. Update Settings in Business Central Environment:
When you click Update Setting, you have the ability to schedule Update Windows and Date.

4. Renaming Business Central Environment:
While this was an easy one, the best one so far is the 'Renaming' feature 

5. Delete Action feature moved to Environment Card: 
There is another one where the actions on the Environments List Page is moved to the card page.

6. Enabling Application Insight Key:
Using Application Insight Key to monitor Business Central Environment and creating reporting on basis of the data gathered.

7. Checking the status of Reported Production Outages:
Using the Reported Production Outages, you can check all Reported Issues and track it. Through the CSP Portal.

8. Checking the Database Capacity:
Business Central v17 enables you to check the Database Capacity for the Environments. Although its not possible to show it with BC v16.

From here, you can also check the size of each of the tables. This will take you to page 8700 - Table Information.

Well, I was surprised to see this feature coming up prior to release.
The best feature I really wanted was Renaming Environment, Capacity, and Report Outage.

I hope this helps 


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

Business Central Environment Blinking after update to v20

Introduction: 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 - Pre- requisites : Business Central Online  v20 Demonstration: 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 Production :<ProductionEnvironmentName>/ 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 insta