Database export as an environment operation
Database export as an environment operation
An export appears on the operations page with status, times, who triggered it and the error on failure. It uses the same filters and details flyout as other operations.
Area: Admin and platform. Status: GA. Developer relevance: low. Airtime: 1 min across 1 video, demoed.
Status evidence
- 1:44 in "What's new: Database Export Enhancements": "From this release, an export is an environment operation like any other."
Where they talk about it
Quotes
- 1:44 "From this release, an export is an environment operation like any other." - Describes the main design change: exports join the standard operations model.
- 1:55 "Once an expert starts, you can see it on the operations page with a status, start and end time" - Lists the tracking information that is now visible for each export.
- 2:18 "export database is now a single button. It used to be a dropdown that had the export history option" - Shows the UI change admins will notice right away.
- 3:03 "Firstly, the database expert history page is retiring." - Admins who used the history page need to use the operations page instead.
Prerequisites mentioned
- Azure storage account SAS URI to receive the export
Documented features match
- No documented item matched. Not documented
- Product documentation: Export databases in the admin center, checked 2026-10-02. The system logs all database export activity as environment operation for progress tracking and auditing purposes. Note: Also says history is viewed on the Operations page.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: admin, operations, database-export, ux
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.