BC Backup - Setup
This document describes how to configure and use BC Backup to initiate Business Central environment database backups via the Admin Center API.
The solution supports manual execution, automated execution via Job Queue, and notifications when a backup is initiated.
1. Purpose
BC Backup allows administrators to:
-
Trigger environment database backups directly from Business Central
-
Schedule backups using Job Queue
-
Store backups in the customer’s own Azure Blob Storage
-
Receive notifications when a backup is started
The solution uses secure service-to-service authentication and the official Business Central Admin Center API.
2. Setup Page Overview
The setup page is divided into the following sections:
-
General
-
Blob Storage
-
Notification
-
App Registration
-
License
All required fields must be configured before backups can be executed.
3. General
Active
Enables or disables the BC Backup functionality.
When enabled, backups can be initiated manually or automatically.
When disabled, no backups can be started.
API Url
The base URL for the Business Central Admin Center API.
Typical value: https://api.businesscentral.dynamics.com
API Version
Specifies the Admin Center API version to use.
Example: v2.28
The default value should normally be used unless otherwise instructed.
4. Blob Storage
This section defines where the backup file is stored.
File Name
The name of the backup file (.bacpac) that will be created in Azure Blob Storage.
Example: prodbackup.bacpac
The file name can be static or dynamically generated (for example with date/time) depending on how the backup is triggered.
Storage Account
The name of the Azure Storage Account where backups are stored.
Example: scxdevstorage
Container Name
The name of the Blob container within the storage account.
Example: bcbackup
The container must exist in advance.
SAS Token
A Shared Access Signature (SAS) that grants Business Central permission to write the backup file to Blob Storage.
The SAS must allow write/create permissions
The SAS must be valid at the time the backup is executed
SAS Status
Displays the validity period and permissions of the configured SAS token.
This helps verify that the SAS is still valid and correctly configured.
Last Run
Shows the date and time of the most recent backup execution.
5. Notification
Mail Recipients
Specifies one or more email recipients who will receive a notification when a backup is initiated.
Multiple recipients can typically be separated by semicolons
Notifications are sent for both manual and scheduled executions
6. App Registration
This section configures the Microsoft Entra ID (Azure AD) app registration used for authentication.
Tenant Id
The Entra ID tenant ID where the app registration exists.
Client Id
The application (client) ID of the registered app.
Client Secret
The client secret used for service-to-service authentication.
Important:
The app registration must be added to the Business Central environment and assigned the permission set:
D365 BACKUP/RESTORE
Without this permission, backups cannot be initiated.
7. License
License Code
The license key for the BC Backup extension.
Status / Expires
Shows the current license status, including trial information and expiration date if applicable.
8. Using BC Backup
Manual Backup
Use the Start backup action to initiate a backup immediately.
Test Backup
Use Test backup to verify that:
Authentication works
Storage access is valid
Configuration is correct
Backup History
Use Backup history to view initiated backups and their status.
Automated Backup
Backups can be scheduled using Job Queue, allowing unattended execution (for example nightly or weekly).
9. Security Notes
Backups are stored only in the customer’s Azure Blob Storage
No backup files or download links are sent by email
Authentication is handled via secure service-to-service credentials
Access to backup execution is controlled via Business Central permissions
10. Summary
BC Backup provides a secure and automated way to manage Business Central environment backups directly from within Business Central, reducing dependency on manual Admin Center operations while keeping full control of data storage and access.
