What's new: Database Export Enhancements (2026 release wave 2)
Database export enhancements in the 2026 release wave 2: export failure rate is under 1%, exports now appear on the admin center operations page as environment operations, the export history page is retiring, and the admin center API export history endpoint is deprecated (works on API 2.29 and earlier).
- Introduction and context
- What database export is and two headlines
- Reliability improvements
- Visibility: exports as environment operations
- Demo: export button and flyout
- Demo: operations page tracking
- Breaking changes and migration guidance
Overview
The video covers two changes to database export in Business Central administration: reliability and visibility. A database export gives the whole environment database as a bacpac-style backup file in the customer’s own Azure storage account. Microsoft states that fewer than 1% of exports fail today, with many weeks having no failures, because common failures across the export pipeline were removed so large environments can be exported reliably.
Exports are now environment operations. They show on the admin center operations page next to renames, updates and copies, with progress, status, start and end time, who triggered the export, and the error message on failure. The video demos the export button and flyout and the operations page tracking. The database export history page is retiring, and the export history endpoint in the admin center API is deprecated, so automations should move to the environment operations API.
Key points
- Fewer than 1% of database exports fail today, and many weeks have no failures.
- Reliability work removed common failures across the export pipeline, so large environments can be exported reliably.
- Exports now appear on the admin center operations page alongside renames, updates and copies.
- The operations page shows progress, status, start and end time, who triggered the export, and the error message if it fails.
- The dedicated database export history page is retiring; its information, plus more, is on the operations page.
- The admin center API export history endpoint is deprecated: it works on API versions 2.29 and earlier and is not carried forward to newer versions.
- Automations that use the export history endpoint should migrate to the environment operations API.
Features
| Feature | Status | At |
|---|---|---|
| Database export reliability improvements | status not stated | 0:57 |
| Exports on operations page | status not stated, demoed | 1:34 |
| Database export history page retirement | status not stated | 3:03 |
| Admin center API export history endpoint deprecation | status not stated | 3:15 |
Quotes
- 0:33 “A database export gives you the whole environment database as a backpack file in your own Azure storage account.”
- 0:45 “Fewer than 1% of exports are failing today.”
- 0:57 “Every expert turns up on the operations page right right next to your other environment operations such as renames, updates, and copies.”
- 1:44 “From this release, an export is an environment operation like any other.”
- 3:03 “the database expert history page is retiring.”
- 3:15 “the expert history endpoint is deprecated. It keeps working on API versions 2.29 and earlier, but it is not carried forward to newer versions.”
Disclaimers in the video
- 3:15 subject-to-change: expert history endpoint is deprecated. It keeps working on API versions 2.29 and earlier, but it is not carried forward to newer versions.
Presenters (as heard): Ehor Hanzuk.