Profile Detail Page Overview
When you open a profile, you see the complete configuration organized into sections: Source, Source Tables, Target, and Quiet Time Periods. A Profile Setup Checklist on the right side of the page tracks your configuration progress.
Profile Setup Checklist
The Profile Setup Checklist helps you track your configuration progress. Items turn green when completed:
| Step | Description |
| Configure source | Connect your Dataverse environment. |
| Configure target | Connect your Azure SQL database. |
| Select tables to sync | Choose which Dataverse tables to synchronize. |
| Configure your quiet time | Optional. Set time windows when syncs should be paused. |
| Configure delete mode | Choose how deleted records are handled in the target. |
| Run initial sync | Execute the first synchronization to populate your target database. |
Profile Actions
The Actions menu in the profile header provides the following options:
| Action | Description |
| Edit Profile | Modify the profile name or delete mode settings. |
| Reset + Full Sync | Clear all watermarks and re-synchronize all data from scratch. Use when you need to rebuild the target data completely. |
| Delete Profile | Permanently delete this profile and its configuration. Does not delete data already synchronized to your target database. |
Edit Profile Dialog
The Edit Profile dialog allows you to modify the following settings:
| Field | Description |
| Name | The display name for this profile. |
| Region | The Azure region where sync operations execute. This cannot be changed after profile creation. |
| Delete Mode | How deleted records in Dataverse are handled in the target database. See Delete Mode options below. |
Delete Mode
Delete Mode determines how records deleted in Dataverse are reflected in your Azure SQL database. This setting affects data integrity, so choose carefully:
| Mode | Description |
| Soft Delete (Recommended) | Mark records as deleted (IsDeleted = true) but keep them in the database. Best for audit trails and historical data. |
| Hard Delete | Physically remove records from the database when they are deleted in the source. |
| ⚠ Warning: Changing the delete mode after initial sync may cause data inconsistencies. Choose your delete mode before running the first synchronization. | |
Source Configuration
The Source section displays your connected Dataverse environment with the following information:
| Field | Description |
| Type | Always 'Dataverse' for Dataverse sources. |
| Base URL | The URL of your Dataverse environment (e.g., https://yourorg.crm.dynamics.com). |
| Created | When this source configuration was created. |
| Connection Status | Success or Failed, based on the most recent connection test. |
| Last Test | Timestamp of the most recent connection test. |
Testing the Source Connection
Click 'Test Connection' to verify Data Mission Sync can connect to your Dataverse environment using the configured credentials. A green 'Connection successful' banner confirms connectivity.
If the test fails, verify that:
• The Base URL is correct and includes https://
• The Client ID matches your App Registration
• The Client Secret is valid and has not expired
• The Application User exists in Dataverse with appropriate security roles
Entering Connection Details
Click 'Edit Source' to configure or update your Dataverse connection. The following fields are required:
| Field | Description |
| Base URL | The HTTPS URL to your Dataverse API endpoint (e.g., https://yourorg.crm.dynamics.com). |
| Client ID | The Azure AD application (client) ID from your App Registration. |
| Client Secret | The Azure AD application client secret. This is stored securely in Azure Key Vault. |
Click 'Update Source' to save changes.
| 💡 Note: The source configuration cannot be deleted once created. If your Dataverse environment has been migrated and has a new URL (for example, yourorg.crm.dynamics.com became yourorg.crm6.dynamics.com), use 'Edit Source' to update the Base URL to the new address. |
| ⚠ Important: A Dataverse environment can only be used as a source in one Data Mission Sync profile due to change tracking API limitations. See Limitations & Important Notes for details. |