Dynamics 365 Business Central: Database exports are now significantly faster and more reliable

Hi, Readers.
Dynamics 365 Business Central 2026 wave 1 (BC28.4) is generally available. More details: Cumulative Update Summary for Microsoft Dynamics 365 Business Central (August, 2026)

Today, I would like to share an update from Microsoft, sourced from the BC Viva Engage.

Joost Bulsink on Viva Engage: This week we’re rolling out updates to the Database Export functionality in the Business Central Admin Center. Most importantly, database exports are … Announcement posted in BC Partners | Governance, Administration, and Security on Aug 19, 2026

This week we’re rolling out updates to the Database Export functionality in the Business Central Admin Center. Most importantly, database exports are now significantly faster and more reliable, with a failure rate below 1% even for environments with large databases and a high number of companies/tables.

We’re also changing how database export operations are managed. The dedicated Export History page in the Admin Center is being removed, and export progress can now be tracked from the Operations page, alongside other environment operations. The Operations page also provides detailed error information if an export fails.

If you’re using Admin Center APIs to get database export history, please migrate to the environment Operations endpoints instead. These endpoints provide status and diagnostic information for database export operations and will replace export history as the supported way to monitor exports.

If you work for a Microsoft partner and still don’t have access to the Viva Engage links above, then submit your application here: aka.ms/BCVivaSignUp.

From the Business Central administration center, you can export the database for Business Central online environments as BACPAC files to an Azure storage container. We have briefly discussed this before. More details: Dynamics 365 Business Central SaaS: How to Export Database and Restore it on Local SQL Server. Below are a few excerpts from the post, please note that the operation method remains unchanged.

Setting up Azure storage

Before you can export the file, you must first set up the Azure storage account container that the BACPAC file will be exported to.

1. Sign into Azure Portal.

2. Enter Storage Accounts in search, and then choose the related link.

3. Choose Add.

4. Create a new Resource group.

5. Enter Storage account name, and then choose Review + create
For example: zybusinesscentralbackup(The field can contain only lowercase letters and numbers. Name must be between 3 and 24 characters)

6. After reviewing, choose Create.

Created successfully

7. Choose Go to resource.

8. Choose Shared access signature.

9. The options in the red box is required, you can cancel the other options, or ignore it.

10. Choose Generate SAS and connection string.

11. URLs will be automatically generated under the button. To save a Backup file from Business Central SAAS you need to copy the Blob service SAS URL key.

Creating the database export

1. Sign into Business Central Admin Center

2. Choose the Environment you want to backup.

3. Create database export.

4. Enter Blob service SAS URL, then choose Create.

Wait for completion…

5. Return to Storage account, and then choose Containers.

6. You can find the Container Name set when exported, then click the Container Name.

7. Click the file name.

8. Choose Download.

Backup file will be downloaded.

Update Summary

1. Most importantly, database exports are now significantly faster and more reliable, with a failure rate below 1% even for environments with large databases and a high number of companies/tables.

2. The dedicated Export History page in the Admin Center is being removed, and export progress can now be tracked from the Operations page, alongside other environment operations. The Operations page also provides detailed error information if an export fails.

3. If you’re using Admin Center APIs to get database export history, please migrate to the environment Operations endpoints instead.

GET /admin/{apiVersion}/applications/{applicationType}/environments/{environmentName}/operations

Great, give it a try!!!😁

PS:
1. Export databases in the admin center

2. Upload, install, and manage PTEs in the admin center (Remove ability to upload and install PTEs from Extension Management page)

END

Hope this will help.

Thanks for reading.

ZHU