Target Configuration
The Target section displays your connected Azure SQL database with the following information:
| Field | Description |
| Type | Always 'AzureSql' for Azure SQL Database targets. |
| Server | Your Azure SQL server address. |
| Database | The name of the target database. |
| Created | When this target configuration was created. |
| Connection Status | Success or Failed, based on the most recent connection test. |
| Last Test | Timestamp of the most recent connection test. |
| Next Sync | Countdown to the next scheduled synchronization. |
Testing the Target Connection
Click 'Test Connection' to verify Data Mission Sync can connect to your Azure SQL database. A green 'Connection successful' banner confirms connectivity.
| 💡 Note: If your Azure SQL database uses the Serverless compute tier and has auto-paused due to inactivity, the first connection test may fail with 'Request failed with status code 504'. Wait a few seconds for the database to wake up, then click 'Test Connection' again. |
Entering Connection Details
Configure your Azure SQL database connection with the following fields:
| Field | Description |
| Use source client ID | Optional checkbox. Copies the Client ID from your Dataverse source. Useful if one App Registration has access to both. You still need Tenant ID and Client Secret. |
| Tenant ID | Your Azure AD (Entra ID) tenant ID. |
| Client ID | The Application (client) ID with access to your Azure SQL database. |
| Client Secret | The client secret for the App Registration. Stored securely in Azure Key Vault. |
| Server | Your Azure SQL server address (e.g., yourserver.database.windows.net). |
| Database | The name of the database where synchronized data will be written. |
| Schema Name | The database schema to use for synchronized tables (default: dbo). |
| ⚠ Important: The target server, database, and schema name cannot be changed after the first synchronization. Ensure these settings are correct before running the initial sync. | |
Editing Target Credentials
While the target database location (server, database, schema) is locked after the first sync, you can update the authentication credentials at any time. This is useful when:
• Your Client Secret is expiring and needs to be rotated
• You need to switch to a different App Registration
• Your Tenant ID has changed due to organizational restructuring
To update target credentials:
1. Open your profile and navigate to the Target section
2. Click 'Edit Target' (pencil icon)
3. Update the Tenant ID, Client ID, or Client Secret as needed
4. Click 'Test Connection' to verify the new credentials work
5. Click 'Update Target' to save your changes
| 💡 Tip: Rotate your Client Secrets before they expire. Set a calendar reminder 2-4 weeks before expiration to update credentials without service interruption. |
Target Connection Troubleshooting
If the connection test fails, verify:
• The server address is correct (format: yourserver.database.windows.net)
• The database name exists and is spelled correctly
• The Data Mission Sync static IP address has been added to your Azure SQL firewall
• The App Registration has been granted db_owner permissions on the database
• If using Azure SQL Serverless: the database may be auto-paused — wait a moment and retry