This reference lists common error messages you may encounter in Data Mission Sync, along with their causes and solutions.
Connection Errors
| Error Message | Solution |
| Request failed with status code 401 | Authentication failed. Check your Client ID and Client Secret are correct and the secret hasn't expired. |
| Request failed with status code 403 | Access denied. Verify the Application User has appropriate security roles in Dataverse. |
| Request failed with status code 404 | Resource not found. Check the environment URL is correct and the environment exists. |
| Request failed with status code 504 | Gateway timeout. For Azure SQL Serverless, the database may be waking up. Retry after a few seconds. |
| Unable to connect to remote server | Network connectivity issue. Check firewall rules and ensure the server address is correct. |
| A network-related or instance-specific error | Cannot reach Azure SQL. Verify the server name, firewall settings, and that the database is online. |
Authentication Errors
| Error Message | Solution |
| AADSTS7000215: Invalid client secret | The Client Secret is incorrect or has expired. Create a new secret in Azure Portal. |
| AADSTS700016: Application not found | The Client ID doesn't exist. Verify the Application (Client) ID from Azure Portal. |
| AADSTS90002: Tenant not found | The Tenant ID is incorrect. Check your tenant ID in Azure Portal → Azure Active Directory → Overview. |
| Login failed for user 'NT AUTHORITY\ANONYMOUS' | Microsoft Entra authentication failed. Ensure your App Registration is properly configured for Azure SQL. |
| Cannot open database requested by the login | Database doesn't exist or user lacks access. Verify database name and user permissions. |
Sync Operation Errors
| Error Message | Solution |
| Change tracking is not enabled | Enable change tracking on the table in Dataverse: Tables → Properties → Track changes. |
| The request was throttled | Dataverse rate limit hit. Data Mission Sync will automatically retry with backoff. |
| Delta link expired | Too long between syncs. A full sync will be triggered automatically to re-establish the delta. |
| String or binary data would be truncated | Data exceeds column size. Contact support — schema evolution may be needed. |
| Violation of PRIMARY KEY constraint | Duplicate key detected. This is rare and may indicate a data issue. Contact support. |
| The database is currently paused | Azure SQL Serverless is paused. The sync will auto-retry as the database wakes up. |
Need More Help?
If you encounter an error not listed here, or the suggested solution doesn't resolve the issue:
1. Check the full error details in Run History by clicking on the failed run
2. Search the Help Center for related articles
3. Contact Support with the error message and your Profile ID