The Synchronization Process
Data Mission Sync uses a profile-based approach to manage your data synchronization. Each profile represents one complete sync configuration — connecting one Dataverse environment to one Azure SQL database.
A profile contains three core components:
| Component | Description |
| Source | Your Microsoft Dataverse environment. Data Mission Sync connects using your App Registration credentials and pulls data via the Dataverse API. |
| Target | Your Azure SQL database. This is where synchronized data is written, in tables that mirror your Dataverse structure. |
| Tables (Routes) | The specific Dataverse tables you choose to synchronize. Each table becomes a 'route' — the path data takes from source to target. |
Initial Sync vs. Incremental Sync
Data Mission Sync uses two types of synchronization to keep your data current efficiently:
| Sync Type | Description |
| Initial Sync (Full) | The first time a table is synchronized, all records are extracted from Dataverse and loaded into Azure SQL. This establishes the baseline dataset. |
| Incremental Sync | After the initial sync, only records that have changed (created, updated, or deleted) since the last sync are processed. This is faster and uses fewer resources. |
Incremental sync is powered by Dataverse change tracking, which identifies exactly which records have changed since the last synchronization.
Data Flow
When a sync runs, data flows through the following stages:
| Step | Stage | What Happens |
| 1 | Extract | Data Mission Sync calls the Dataverse API to retrieve changed records for each selected table. |
| 2 | Stage | Records are processed and staged in temporary tables in your Azure SQL database. |
| 3 | Apply | Staged data is merged into your target tables — inserting new records, updating changed ones, and handling deletes based on your delete mode setting. |
| 4 | Checkpoint | The sync position is recorded so the next run knows where to continue from. |
Important: Your business data flows transiently through Data Mission Sync infrastructure but is never stored at rest. Only configuration and sync metadata are retained by Mission Impact Partners.
Regions & Data Residency
Data Mission Sync operates in multiple Azure regions. When you create a profile, you select the region where sync processing will occur:
| Region | Azure Name | Location |
| Canada Central | canadacentral | Toronto, Ontario, Canada |
| US West 2 | westus2 | Washington State, USA |
| US East 2 | eastus2 | Virginia, USA |
| UK South | uksouth | London, England, UK |
| North Europe | northeurope | Dublin, Ireland |
Choose the region closest to your Azure SQL database for best performance, or based on your data residency requirements.
Security & Compliance
Data Mission Sync is designed with security as a priority:
| Security Feature | Description |
| Transient Data Processing | Your business data is processed in memory and written directly to your database. It is never stored at rest in our systems. |
| Credential Security | Your connection credentials (client secrets) are stored securely in Azure Key Vault, never in application databases. |
| Encrypted Connections | All data transfer uses TLS 1.2+ encryption in transit. |
| Your Database, Your Control | Synchronized data lives in your Azure SQL database. You control access, backups, and retention. |
| Static IP Addresses | Each region has dedicated NAT IP addresses, allowing you to configure strict firewall rules on your Azure SQL database. |