{"title":"Export databases in the admin center","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/tenant-admin-center-database-export/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-database-export, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-database-export","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to export production environment data as BACPAC files to Azure storage. Start your export today.","date":"2026-07-28","meta":{"topic":"how-to"},"outline":[{"level":2,"title":"Considerations before you begin","slug":"considerations-before-you-begin","at":165,"chars":980},{"level":2,"title":"Set up Azure storage","slug":"set-up-azure-storage","at":1145,"chars":2202},{"level":3,"title":"Create the storage account","slug":"create-the-storage-account","at":1266,"chars":611},{"level":3,"title":"Generating a shared access signature (SAS)","slug":"generating-a-shared-access-signature-sas","at":1877,"chars":1470},{"level":4,"title":"To generate a shared access signature (SAS)","slug":"to-generate-a-shared-access-signature-sas","at":2134,"chars":1213},{"level":2,"title":"Creating the database export","slug":"creating-the-database-export","at":3347,"chars":1639},{"level":2,"title":"Viewing the export history","slug":"viewing-the-export-history","at":4986,"chars":239},{"level":2,"title":"Users who can export databases","slug":"users-who-can-export-databases","at":5225,"chars":523},{"level":2,"title":"Using the exported data","slug":"using-the-exported-data","at":5748,"chars":1718},{"level":2,"title":"Restoring the exported data to Business Central online","slug":"restoring-the-exported-data-to-business-central-online","at":7466,"chars":585},{"level":2,"title":"Restoring the exported data to a container","slug":"restoring-the-exported-data-to-a-container","at":8051,"chars":287},{"level":2,"title":"Related information","slug":"related-information","at":8338,"chars":649}],"text":"From the Business Central administration center, you can export the database for Business Central online environments as BACPAC files to an Azure storage container.\n## Considerations before you begin\n You can only request a database export if the customer has a paid Business Central subscription.\n You must have explicit permission to export databases. Learn more in the #users-who-can-export-databases section.\n You can't export your database to an Azure premium storage account. The steps in this article only support Azure standard storage accounts.\n You can export the database of an environment that's encrypted with a ../security/security-online#customer-managed-encryption-key. The BACPAC files in the storage account are encrypted with the encryption key applied to the storage account<https://learn.microsoft.com/azure/storage/common/customer-managed-keys-overview>, not the environment's encryption key.\n> NOTE\n> For each environment, you can export the database a maximum of 10 times per month. You can see the number of exports still remaining for the current month in the Create Database Export pane when creating the export file.\n## Set up Azure storage\nBefore you can export the file, set up the Azure storage account container that the BACPAC file.\n### Create the storage account\nThe first step is to create a Standard general-purpose v2 Azure storage account, if you don't already have one. To set up the export, you must first have a subscription to Microsoft Azure and access to the https://portal.azure.com.\n> IMPORTANT\n> Exporting an environment database to a storage account that isn't a Standard general-purpose v2 Azure storage account, such as V1 or Premium storage accounts, isn't supported.\nLearn more about setting up an Azure storage account in https://learn.microsoft.com/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal.\n### Generating a shared access signature (SAS)\nThe next step is to generate a shared access signature (SAS) that provides secure delegated access to your storage account. Business Central uses the signature to write the BACPAC file to your storage account.\n#### To generate a shared access signature (SAS)\n1. On the Azure storage account, choose Shared access signature in the navigation pane.\n1. In the Allowed services section of the shared access signature pane, select Blob, and clear the other options.\n1. In the Allowed resource types section, select Container and Object, and clear the other options.\n1. In the Allowed permissions section, select Read, Write, Delete, and Create, and clear the other options.\n1. Select a start and end date and time for the SAS. The SAS requires a minimum expiration window of 72 hours from the initiation of the export.\n> TIP\n> Use near-term expiration for the account's SAS. To reduce risk of a compromised storage account, set the end date and time no later than what you need to complete the database export operation. However, the SAS must be valid for a minimum of 72 hours.\n1. In the Allowed protocols section, select HTTPS only.\n1. Select Generate SAS and connection string.\n1. Copy the Blob service SAS URL.\nFor more information on generating and using a SAS, see Grant limited access to Azure Storage resources using shared access signatures (SAS)<https://learn.microsoft.com/azure/storage/common/storage-sas-overview>.\n## Creating the database export\nAfter you create the Azure storage account and generate the SAS URI, you can create the export file from the Business Central administration center.\n1. On the Environments list page, choose the relevant environment to view the environment details.\n1. On the action ribbon of the environment details, choose Database, and then choose Create Database Export.\n1. In the File Name field, enter a name for the export file, or accept the default value.\n1. In the SAS URI field, enter the Blob service SAS URL value that you copied in the previous section.\n1. In the Container Name field, enter the name of the container in the Azure storage account where you want to export the BACPAC file. If you already created a container in your Azure storage account, enter the name of that container. Otherwise, if the name you specify in the Container Name field doesn't exist in the Azure storage account, the portal creates it for you.\nWhen the export operation starts, the BACPAC file is generated and exported to the specified Azure storage account. The operation might take several minutes to several hours depending on the size of the database. You can close the browser window with the Business Central administration center during the export. When the export finishes, you can access the export file in the defined container in your Azure storage account. Optionally, you can import the data into a new database in Azure SQL Database or SQL Server for further processing. See Quickstart: Import a BACPAC file to a database in Azure SQL Database<https://learn.microsoft.com/azure/sql-database/sql-database-import>.\n## Viewing the export history\nThe system logs all database export activity as environment operation for progress tracking and auditing purposes. To view the history, go to the Operations page in the Business Central administration center.\n## Users who can export databases\nOnly specific types of users can export databases: internal and delegated administrators. The following users can export databases.\nIn addition to an Entra role that grants access to the Business Central administration center, these users must have the D365 BACKUP/RESTORE permission set assigned to their user account in the environment they're trying to export.\nLearn more about permission sets and user groups in Assign Permissions to Users and Groups</ui-define-granular-permissions>.\n## Using the exported data\nThe BACPAC file contains data that's customer-specific business data. Technically, Business Central online is a multitenant deployment, which means that each customer tenant has their own business database while the data that defines the application is in a shared application database.\nTo export data when moving the customer's Business Central from an online to an on-premises deployment, get the application data from the installation media for the same version as the online tenant. You find the version number in the Business Central administration center or on the Help and Support page in client.\n> IMPORTANT\n> While you can import the downloaded BACPAC file into your own SQL Server instance, Microsoft doesn't provide support for creating a working on-premises environment from the BACPAC that you download from Business Central online.\nSee Quickstart: Import a BACPAC file to a database in Azure SQL Database<https://learn.microsoft.com/azure/sql-database/sql-database-import>, Migrating to Single-Tenancy From Multitenancy<../deployment/merging-an-application-database-with-a-tenant-database>, and ../deployment/deployment#when-to-choose-on-premises-deployment.\n> NOTE\n > If you're getting an error saying your file contains corrupted data when importing the bacpac file, make sure you're using the .NET Core version of SqlPackage.exe<https://learn.microsoft.com/sql/tools/sqlpackage/sqlpackage-download>.\n > When importing the exported database by using SQL Server Management Studio (SSMS), use the latest version. Earlier versions might not support all scenarios. Learn how to update SSMS in Update SQL Server Management Studio<https://learn.microsoft.com/ssms/install/update>.\n## Restoring the exported data to Business Central online\nIf you decide at some point that you want to restore the exported data to a new environment in Business Central online, you must go through the same steps as you went through to migrate from on-premises to Business Central online. This way, you can prepare the database so that it's ready to migrate to the latest version of Business Central. For example, you could choose to replicate the data to a sandbox environment for further testing and training. See Migrating on-premises data to Business Central online<migrate-data>.\n## Restoring the exported data to a container\nIf you want to use the exported data in a container-based developer environment, you can use Windows PowerShell scripts to help you do that, including the BCContainerHelper PowerShell module<https://github.com/Microsoft/navcontainerhelper>.\n## Related information\nSQL Server technical documentation<https://learn.microsoft.com/sql/sql-server/>\nQuickstart - import a BACPAC file to a database in Azure SQL Database<https://learn.microsoft.com/azure/sql-database/sql-database-import>\nDelegated administrator access to Business Central online<delegated-admin>\nWorking with administration tools<administration>\nThe Business Central administration center<tenant-admin-center>\nManaging environments<tenant-admin-center-environments>\nUpdating environments<tenant-admin-center-update-management>\nManaging tenant notifications<tenant-admin-center-notifications>\nitpro-introduction-to-automation-apis"}