System Requirements
This page outlines the requirements for running Cloud Replicator in your Business Central environment and the Azure resources needed for cloud destinations.
Business Central Requirements
Platform Version
Cloud Replicator requires Microsoft Dynamics 365 Business Central version 18.0 or later. The extension is designed for the Business Central cloud (SaaS) environment.
| Requirement | Specification |
|---|---|
| Minimum Version | Business Central 18.0 |
| Platform | Business Central Online (SaaS) |
| Region | Any supported Business Central region |
Licensing
Cloud Replicator requires a valid license for production environments. Sandbox environments can be used without a license for evaluation and testing purposes.
| Environment | License Required |
|---|---|
| Production | Yes |
| Sandbox | No (full functionality available) |
| On-Premises | Yes |
Azure Requirements
To replicate data, you need at least one Azure cloud destination configured. Each destination has specific requirements.
Azure Table Storage
To use Azure Table Storage as a destination:
| Requirement | Details |
|---|---|
| Azure Subscription | Active Azure subscription |
| Storage Account | General-purpose v2 storage account |
| Access Key | Storage account access key with Table service permissions |
| Network Access | Storage account accessible from Business Central (default public access or configured firewall rules) |
Azure Portal Path: Storage accounts > [Your Account] > Access keys
Azure Cosmos DB (NoSQL)
To use Cosmos DB Core/NoSQL API:
| Requirement | Details |
|---|---|
| Azure Subscription | Active Azure subscription |
| Cosmos DB Account | Account with Core (SQL) API |
| Database | A database created within the account |
| Access Key | Primary or secondary key from the account |
| Network Access | Cosmos DB accessible from Business Central |
Azure Portal Path: Azure Cosmos DB > [Your Account] > Keys
Azure Cosmos DB (Table API)
To use Cosmos DB Table API:
| Requirement | Details |
|---|---|
| Azure Subscription | Active Azure subscription |
| Cosmos DB Account | Account with Table API |
| Access Key | Primary or secondary key from the account |
| Network Access | Cosmos DB accessible from Business Central |
Azure Portal Path: Azure Cosmos DB > [Your Account] > Keys
Azure AI Search
To use Azure AI Search:
| Requirement | Details |
|---|---|
| Azure Subscription | Active Azure subscription |
| Search Service | Azure AI Search service (any tier) |
| Admin Key | Admin API key for index management |
| Network Access | Search service accessible from Business Central |
Azure Portal Path: Search services > [Your Service] > Keys
Network Requirements
Business Central Online connects to Azure services over the internet using HTTPS. Ensure your Azure resources allow connections from Microsoft's Business Central IP ranges or are configured for public access.
Required Endpoints
| Destination | Endpoint Format |
|---|---|
| Azure Table Storage | https://{account}.table.core.windows.net/ |
| Cosmos DB (Table) | https://{account}.table.cosmos.azure.com/ |
| Cosmos DB (NoSQL) | https://{account}.documents.azure.com/ |
| Azure AI Search | https://{service}.search.windows.net/ |
Firewall Considerations
If you have configured firewall rules on your Azure resources:
- Azure Table Storage / Cosmos DB: Add Business Central service IPs to allowed list, or enable "Allow Azure services" option
- Azure AI Search: Configure network access to allow connections from Business Central
User Permissions
Users who configure and run Cloud Replicator need appropriate permissions in Business Central:
Required Permissions
- Read access to all tables being replicated
- Modify access to Cloud Replicator configuration tables
- Execute permission on Cloud Replicator codeunits
- Job Queue administration (for scheduled replication)
Recommended Setup
Assign users who manage Cloud Replicator the following:
- SUPER user role, or
- A custom permission set with Cloud Replicator table and codeunit access
Performance Considerations
Business Central
- Replication runs in background sessions, minimizing impact on interactive users
- Large table replications may consume session capacity
- Consider running during off-peak hours for initial full replications
Azure Resources
| Resource | Sizing Consideration |
|---|---|
| Table Storage | Scales automatically, pay-per-use |
| Cosmos DB | Provision adequate RU/s for write throughput |
| AI Search | Choose tier based on document count and index size |
Replication Engine Settings
The default settings work well for most scenarios:
| Setting | Default | Impact |
|---|---|---|
| Replication Engine Count | 10 | More engines = faster replication, more resource usage |
| Maximum Records per Engine | Varies | Affects table splitting granularity |
| Connection Retry Count | 10 | Higher values handle transient failures better |
| Engine Timeout | 24 hours | Maximum duration for a single replication job |
Change Log Requirements
If you plan to use the "Replicate Deletions" feature:
- Enable Change Log in Business Central
- Configure Change Log Setup to log deletions for tables you want to track
- Ensure Change Log entries are retained long enough for replication
Navigation: Search for "Change Log Setup" in Business Central