This page covers authentication issues with Microsoft Entra ID (Azure AD) and SQL Server credentials.
Microsoft Entra Authentication Issues
Error: "AADSTS700016: Application with identifier 'X' was not found"
Cause: The Client ID (Application ID) is incorrect or the App Registration doesn't exist
Solutions:
1. In Azure Portal, go to Azure Active Directory → App registrations
2. Find your app and copy the Application (client) ID
3. Paste the correct value in the Client ID field
Error: "AADSTS90002: Tenant 'X' not found"
Cause: The Tenant ID (Directory ID) is incorrect
Solutions:
1. In Azure Portal, go to Azure Active Directory → Overview
2. Copy the Tenant ID (Directory ID) from the Essentials section
3. Paste the correct value in the Tenant ID field
Error: "AADSTS7000215: Invalid client secret provided"
Cause: The client secret is incorrect or has expired
Solutions:
1. In Azure Portal, go to your App Registration → Certificates & secrets
2. Check if the secret has expired (look at the Expires column)
3. Create a new client secret and copy the Value (not the Secret ID)
4. Update the Client Secret field in DvSchemaSync
⚠ Important: Client secret values can only be viewed once when created. If you didn't save it, you must create a new secret.
Dataverse Permission Errors
Error: "403 Forbidden" or "Insufficient permissions"
Cause: The Application User doesn't have the required security role
Solutions:
1. In Power Platform Admin Center, go to your environment → Settings → Users
2. Find the Application User for your App Registration
3. Assign the System Administrator security role (for sync operations)
4. For dummy data generation, also ensure the user has Create permissions on target entities
SQL Server Authentication Issues
Error: "Login failed for user 'X'"
Possible Causes:
• Incorrect username or password
• User doesn't have access to the specified database
• Azure AD authentication required but SQL auth attempted
Solutions:
1. Verify credentials are correct
2. Ensure the user has been granted access to the database
3. Try switching to Microsoft Entra authentication if available