Tuesday 30 November 2021

Copying environments of different types

Copy an Environment:

1.  We can create an environment that is a copy of an existing environment, such as a sandbox that is based on production for troubleshooting.

2.  Creating production environment that is based on a sandbox, for example. When you create an environment as a copy of another environment, the new environment is created on the same application version as the environment that you are copying. 

Note: The new environment will contain all per-tenant extensions and AppSource extensions that are installed and published in the original environment that is being copied.

To copy an environment

1.     Select Environments, then select the environment that you want to copy.

2.     On the Environment Details page, choose the Copy action.

3.     In the Copy environment pane, specify the type of environment that you want to create based on the current environment.

4.     Specify a name for the new environment.

5.     Choose the Create action.

At the different stages of implementation, testing, support, and maintenance of a Business Central tenant, Business Central online now provides admins with more flexibility when they work with multiple environments.

In earlier versions, you could copy a production environment to a sandbox environment in the Business Central admin centre.

This release wave adds support for copying the environments within and across different environment types as shown in this list:

·        Sandbox to sandbox

·        Sandbox to production

·        Production to production

a.     Sandbox to Sandbox: 





b.     Sandbox to Production:



C. Production to Production

       Similarly, we can copy Production to Production

Sunday 21 November 2021

How to Restart D365 Business Central Environment


In NAV days, we have possibility to restart service tier and there are many reasons for the need of having restart option.

How to restart D365 Business Central environment?

Navigate to Dynamics 365 Business Central.

Click on the environment that you want to restart

Environment Details page will open

Click on Sessions

Manage sessions page will open

Click on Restart Environment.

Click yes on below confirmation message

If we go to details screen of environment then we can notice the status “Restarting”

After sometime status will be changed to “Active”

Active sessions will get below notification

I would expect a different notification than the regular notification to have clear message.



Monday 15 November 2021

Application Insights instrumentation key to Application Insights connection string


Monitoring and Analyzing Telemetry is one of the powerful features of D365 Business Central.

We must enable Application Insights to Send Telemetry to Azure Application Insights.

Please go through below Microsoft Docs link for details

EnableSending Telemetry to Application Insights - Business Central | Microsoft Docs


I have noticed below Notification on my environment.

The environment uses an Application Insights instrumentation key. Change it to an Application Insights connection string. Go to Enable Sending Telemetry to Application Insights for more information.


Earlier We must have used only Application Insights instrumentation key to enable this feature to send telemetry in Dynamics 365 Business Central admin center but now we must use Application Insights connection string.


How and where to get this Application Insights connection string?


Sign in to the Azure portal

Search for Application Insights

Click on the Application Insights which we have used/created earlier.

“Connection String” will be available under the instrumentation key

Use “Copy to Clipboard” to copy full string.


Go back to Dynamics 365 Business Central admin portal and open the Environment which has this notification

Click on Modify link of Application Insights connection string

Make sure that Enable Application Insights is enabled.

Enter the Connection string that we copied from Azure portal.

Click on Save

Now the notification will be gone after refreshing the environment.