When you set up Master Data Synchronization across multiple Business Central environments, you cannot rely on a direct database connection. If the subscriber lives in a separate database or environment, you exchange the data through Azure Blob Storage instead. This means you create a partner record configured for blob storage rather than for an internal database.
To configure the partner, you set the data exchange type to Azure Blob Storage and provide the storage account name, the SAS token for that account, and the name of the container. The company name field is not relevant in this scenario because the exchange does not go through the database.
You can test the connection directly from the partner card. Use the Test Blob Storage Connection action to upload a test file, view it in the blob storage, download it to confirm the content, and then delete it again. Once the test file is gone and the list of files is empty, the connection works.
The final step is to take the partner off hold so it can start synchronizing.
Setting up Master Data Synchronization across separate environments
Master Data Synchronization in Business Central lets you keep data consistent between environments. When the subscriber is just another company in the same database, the sync is straightforward. But when the new subscriber is a separate database or a different environment entirely, you cannot exchange data directly. In that case, you route the data through Azure Blob Storage, and that requires setting up a dedicated partner.
Creating a partner for Azure Blob Storage data exchange
Go to the partners list and create a new partner. Fill in the following:
- Unique ID for the partner
- Description
- Data exchange type set to Azure Blob Storage
- Company name – type in any value here. It is not relevant in this scenario because the exchange does not go through the database
- Account name for the blob storage
- SAS token for that account name
- Container name
With these details in place, the partner is technically ready to be used.
Testing the Azure Blob Storage connection
Before you rely on the partner, confirm that the connection to Azure Blob Storage actually works. From the Action menu, choose Test Blob Storage Connection. This uploads a test file to the blob storage.
You can then press Show Blob Storage Files to see that a text file now exists in the Azure Blob Storage. Download the file to verify its content. In the test, the file contains the text “hello world”, which confirms it was downloaded from the storage as expected.
Finally, delete the test file from the Azure Blob Storage and test again. When the list of files is empty, you know the upload, download, and delete operations all work correctly.
Activating the partner for synchronization
Once you have confirmed the connection and the subscriber is ready to synchronize, uncheck the On Hold field on the partner. The partner is now ready to perform the master data synchronization.
Q&A
When do I need Azure Blob Storage for Master Data Synchronization?
You need Azure Blob Storage when the subscriber is in a separate database or a different environment. A direct database connection only works when the subscriber is part of the same database, so for cross-environment sync you exchange the data through blob storage instead.
What information do I need to configure an Azure Blob Storage partner?
You need the storage account name, the SAS token for that account, and the container name. You also set the data exchange type to Azure Blob Storage. The company name field can hold any value because it is not used in this scenario.
How do I test that the blob storage connection works?
Use the Test Blob Storage Connection action to upload a test file. Then use Show Blob Storage Files to confirm the file exists, download it to verify the content, and delete it afterwards. When the file list is empty again, the connection is working correctly.
How do I activate the partner once everything is set up?
Uncheck the On Hold field on the partner. After that, the partner is ready to start synchronizing.