| Full backup access (permission set RDN BCB FULL) is required to change credentials, manage or download backups. | The user does not have full access to the extension. | Ask an administrator to assign RdN BC Backup - Full Access (RDN BCB FULL). |
| The D365 BACKUP/RESTORE permission set is required to start database exports. Ask your administrator to assign it to user …. | The user submitting the export request lacks the required Business Central permission. | Ask an administrator to assign D365 BACKUP/RESTORE to the user or Job Queue user. |
| Configure the client secret in RdN BC Backup Setup. | The client secret is missing. | Open RdN BC Backup Setup and enter a secret for Client Credentials (App Registration). |
| Failed to acquire an access token. Check the tenant, client ID, client secret, and admin consent. | Authentication failed or consent is missing. | Verify the tenant, client ID, and secret. Ask an administrator to confirm that consent was granted for the app registration. |
| Delegated authentication failed. Details: … | The delegated authentication request failed. | Sign in again and confirm that the user is an authorized Business Central administrator. |
| Delegated authentication is for manual use only. Select Client Credentials for recurring backups. | Delegated mode cannot run in the Job Queue. | Select Client Credentials (App Registration) and enter the client secret before enabling recurring runs. |
| Admin Center API request failed (HTTP …). Check the environment, Admin Center app authorization, and D365 BACKUP/RESTORE permissions. Response: … | The Admin Center rejected the request or returned an error. | Verify the environment name, app authorization in the Admin Center, and D365 BACKUP/RESTORE. |
| The Admin Center API rejected the access token (HTTP 401). Check that: (1) Client ID … is added on the Authorized Microsoft Entra apps page in the Business Central admin center; (2) admin consent is granted for the Application permission AdminCenter.ReadWrite.All (Client Credentials), or the signed-in user is a Business Central administrator (Delegated); (3) BC Tenant ID … is the tenant that owns environment …. New permissions can take several minutes to apply. Details: … | The access token was not accepted or the app is connected to the wrong tenant. | Verify the Client ID registration, consent, authentication mode, and that BC Tenant ID owns the environment. Wait several minutes for new permissions to apply, then try again. |
| The Admin Center API denied the request (HTTP 403). Check that Client ID … is authorized in the Business Central admin center, and that in environment … the Microsoft Entra Applications page lists it as Enabled with the D365 BACKUP/RESTORE permission set. Details: … | The app is not authorized for the target environment or export. | Verify the app authorization in the Admin Center and that the app is enabled in the target environment with D365 BACKUP/RESTORE. |
| Admin Center refused the export because app registration … has no export permission inside environment …. With Client Credentials, the app registration needs this permission, not the signed-in user. Authorizing the app in the Business Central admin center is a separate step and is not enough. Sign in to environment …, open the Microsoft Entra Applications page, and add Client ID … (or open its card). Set State to Enabled and assign the D365 BACKUP/RESTORE permission set with Company left blank. Response: … | The app registration does not have export permission inside the target environment. | Ask an administrator to enable the app in the target environment and assign D365 BACKUP/RESTORE with no company specified. |
| The Admin Center API request could not be sent or its response could not be received. Check Allow HttpClient Requests in Extension Management and network connectivity. | Business Central could not send the request or receive a response. | Verify Allow HttpClient Requests in Extension Management and network connectivity. |
| The Admin Center API returned an unexpected response. Expected: …. | The Admin Center response was not in a format the extension could read. | Try again later. If the error continues, contact an administrator. |
| Azure SAS Token has not been configured. Please set up the SAS Token first. | The export SAS token is missing from setup. | Enter a token in Export SAS Token and select Validate Export SAS Token. |
| Configure the Azure SAS token in RdN BC Backup Setup. | The API request cannot find the export SAS token. | Open RdN BC Backup Setup, enter the export token, and validate it. |
| A read-only download SAS token has not been configured in RdN BC Backup Setup. | The download token is missing. | Enter a read-only token in Download SAS Token (Read-Only) and select Validate Download SAS Token. |
| The Export SAS Token must be entered again on the RdN BC Backup Setup page. It was saved by an earlier version in a format that cannot be validated or used for downloads. | An older token was saved in a format that cannot be validated. | Enter the export SAS token again in RdN BC Backup Setup. |
| The Download SAS Token (Read-Only) must be entered again on the RdN BC Backup Setup page. It was saved by an earlier version in a format that cannot be validated or used for downloads. | An older download token was saved in a format that cannot be validated or used. | Enter the read-only download SAS token again. |
| The SAS token must remain valid for at least 72 hours after starting an export. Current expiry: …. | The export token expires too soon for the export. | Enter a token that remains valid for at least 72 hours after an export starts. |
| The SAS token must include Read, Write, Delete, and Create permissions (sp= must contain r, w, d, and c). | The export token is missing one or more required permissions. | Request a Blob account SAS with Read, Write, Delete, and Create permissions, then validate it again. |
| Use an account SAS for the Blob service (ss=b) with Container and Object resource types (srt=co) and HTTPS only (spr=https). Copy the Blob service SAS URL from the storage account Shared access signature page. | The token is not a Blob account SAS with the required scope and HTTPS setting. | Obtain the correct Blob service SAS URL from the Azure administrator and validate the token again. |
| The SAS token does not contain a signed version (sv=) parameter. Ensure you have a valid SAS token, not a connection string. | The value is not a complete SAS token or is a connection string. | Obtain a valid SAS token, not a connection string, and enter it again. |
| The SAS token does not contain a signature (sig=) parameter. The token appears to be incomplete or invalid. | The token is missing its signature. | Obtain a new valid SAS token and validate it. |
| The SAS token does not contain an expiry date (se=) parameter. The token may be invalid. | The token is missing its expiry. | Obtain a new SAS token with an expiry and validate it. |
| The SAS expiry (se=) must be a valid UTC date and time. | The expiry in the SAS token is not a valid UTC time. | Obtain a new token with a valid UTC expiry. |
| The SAS start time (st=) is invalid or is in the future. | The token start time is invalid or later than the current time. | Obtain a token whose start time has passed, or omit the start time. |
| The SAS token must allow HTTPS only (spr=https). | The token does not require HTTPS only. | Obtain a new token restricted to HTTPS. |
| The download SAS token must be scoped to the backup container (sr=c). Generate it from the container's Shared access tokens page. | The download token does not apply to the container holding the backups. | Obtain a read-only token for the correct container and validate it again. |
| The download SAS token must be read-only (sp= may only contain r and l). Current permissions: …. | The download token grants too many permissions or lacks Read. | Obtain a new container-scoped token with Read and optional List, and no other permissions. |
| The download SAS token expired on …. Generate a new read-only SAS token for the container. | The download token has expired. | Obtain a new read-only token for the correct container and update setup. |