App Registration Issues
App Registration problems typically manifest as authentication failures when connecting to Dataverse or Azure SQL. Common issues include:
| Issue | Solution |
| Expired Client Secret | Client Secrets have expiration dates. Check Azure Portal → App Registrations → Your App → Certificates & Secrets. Create a new secret and update it in Data Mission Sync. |
| Wrong Client ID | Verify the Client ID (Application ID) matches exactly. Find it in Azure Portal → App Registrations → Your App → Overview. |
| Wrong Tenant ID | Ensure you're using the correct Tenant ID for your organization. Multi-tenant apps may require specific tenant configuration. |
| Secret copied incorrectly | Client Secrets are only shown once when created. If you copied it incorrectly, create a new secret. Watch for leading/trailing spaces. |
| App Registration deleted | If the App Registration was deleted in Azure, you'll need to create a new one and update all configurations. |
Rotating Client Secrets
Client Secrets should be rotated before they expire. To rotate a secret:
1. Create a new secret in Azure Portal (before the old one expires)
2. Update the secret in Data Mission Sync via Edit Source
3. Test the connection to verify the new secret works
4. Delete the old secret from Azure Portal
| ⚠ Important: Set a calendar reminder 2-4 weeks before your secret expires. Expired secrets will cause all synchronizations to fail. |
SQL Authentication Issues
Azure SQL authentication problems occur when the App Registration hasn't been properly configured as a database user:
| Error Message | Solution |
| Login failed for user | The App Registration hasn't been added as a database user. Connect to your database and run: CREATE USER [YourAppName] FROM EXTERNAL PROVIDER; |
| User does not have permission | The user exists but lacks permissions. Run: ALTER ROLE db_owner ADD MEMBER [YourAppName]; to grant required permissions. |
| Cannot find user in database | You may be connected to the wrong database. Ensure you run the CREATE USER command in your target database, not master. |
| The server principal already exists | A user with this name already exists. This is usually fine — just ensure the user has the correct permissions. |
| 💡 Note: Data Mission Sync uses Microsoft Entra (Azure AD) authentication exclusively. SQL Server username/password authentication is not supported. | |