3: Regions & Data Residency

Available Regions

Data Mission Sync is available in the following Azure regions. Select a region based on proximity to your Azure SQL database for optimal performance, or based on data residency compliance requirements.

Data Residency Considerations

Understanding how your data flows through Data Mission Sync is important for compliance:

Business Data:

• Your business data flows transiently through the region you select during profile setup

• Data is transferred directly from your Dataverse environment to your Azure SQL database

• Data Mission Sync does not store, retain, or examine your business data — it flows through for synchronization only

• After synchronization completes, your data resides exclusively in your Azure SQL database

Control Plane Data:

• Account information, configuration settings, and operational metadata are stored in Canada Central

• This includes profile names, table selections, schedules, and synchronization logs

• No business data is stored in the control plane

Choosing a Region:

• Select the region closest to your Azure SQL database for optimal performance

• For data residency compliance, choose a region within your required geographic boundary

• Consider where your Dataverse environment is hosted — selecting a nearby region reduces latency

Static IP Addresses

Each region has a dedicated static IP address for outbound connections. Add the appropriate IP to your Azure SQL firewall rules to allow Data Mission Sync to connect.