Your reading of the documentation is correct, and unfortunately there's no native Microsoft mechanism to export a PPAC Sandbox backup as a BAK/BACPAC file or retain it natively beyond the documented window. Per your own screenshot, Sandbox is fixed at 7 days, only Production supports extension (up to 28 days), and that extension isn't available for Sandbox regardless of environment type.
Answering your questions directly:
1. Can PPAC Sandbox backups be exported and stored externally? No. PPAC system/manual backups are Microsoft-managed snapshots used only for restore-in-place within the same PPAC restore workflow (per your screenshot's "Supported Environments" table: Production→Sandbox, Sandbox→Sandbox, Developer→Sandbox/Developer). They are not downloadable artifacts like classic LCS BACPAC exports.
2. Is there an Azure-based archival solution Microsoft supports? Not as a native backup export, but there are supported data-level (not full environment) options:
- Azure Synapse Link for Dataverse – continuous export of table data to Azure Data Lake/Synapse, giving you long-term historical data retention outside the 7-day window. This covers data, not full environment/config state.
- Dataverse-to-Azure export tools (Export to Data Lake, or Fabric Link if you're on Fabric) – similar concept, ongoing data replication rather than point-in-time environment snapshots.
3. Practical workarounds others use:
- Periodically copy the Sandbox to a new temporary Sandbox environment (Copy feature in PPAC) at whatever cadence you need (e.g., monthly), and just retain the temporary environments as your "point in time" archive for as long as your capacity allows. This is effectively your question 4, and yes, it's currently the most common workaround.
- Some organizations solve this by keeping a small number of long-lived named Sandbox environments (e.g., "Sandbox-Monthly-Jan", "Sandbox-Monthly-Feb") populated via Copy, then decommissioning older ones on a rolling basis to manage capacity/cost.
- If your real requirement is data recovery rather than full environment/config recovery, Synapse Link is generally more efficient than spinning up full environment copies every month.
4. Is periodic Sandbox-to-Sandbox copy the only real option? Effectively, yes, for full environment/config-level point-in-time recovery beyond 7 days. There's no supported export-and-store-externally path for full backups today.
One more consideration since you're on UDE specifically: confirm with your Microsoft account team/FastTrack whether UDE environments have any different backup/export capability roadmap planned, since UDE is a newer environment model and retention tooling parity with classic LCS-managed F&O environments has been evolving. Worth explicitly asking rather than assuming current PPAC limitations are permanent for this environment type.
Capacity note: if you go the periodic-copy route, remember each retained Sandbox copy consumes your tenant's database capacity allocation, factor that into your 2-3 month retention plan before committing to a specific number of rolling copies.
Share
Report
All responses (
Answers (
205
