Skip to main content

Connection Troubleshooting

Guide to solve common problems connecting AtlasData with Power BI.

Authentication Problems​

Error: "Invalid client credentials"​

Cause: Incorrect Client ID or Client Secret.

Solution:

  1. Verify that you copied the Client ID correctly (no spaces)
  2. Create a new Client Secret in Azure Portal
  3. Copy the Value (not the Secret ID)
  4. Update in AtlasData

Error: "AADSTS700016: Application not found"​

Cause: The App Registration doesn't exist or is in another tenant.

Solution:

  1. Verify the Tenant ID
  2. Confirm that the App Registration exists in Azure Portal
  3. Verify that you are in the correct tenant

Error: "AADSTS50020: User account does not exist"​

Cause: Trying to use federated corporate email with another Azure AD.

Solution:

  1. Use a personal account (Gmail, Outlook.com)
  2. Or configure federated SSO (contact support)

Permission Problems​

Error: "Unauthorized" or "403 Forbidden"​

Cause: Service Principal without sufficient permissions.

Solution:

  1. Verify that Admin Consent was granted
  2. Verify that Service Principal is enabled in Power BI Admin
  3. Wait 5-10 minutes for propagation

Error: "No workspaces found"​

Cause: Service Principal has no access to any workspace.

Solution:

  1. Add Service Principal to the desired workspaces
  2. Use Member or Viewer level
  3. Wait a few minutes

Error: "Resource not found"​

Cause: The report or dataset was deleted or moved.

Solution:

  1. Verify that the content still exists in Power BI
  2. Run new discovery in AtlasData

Network Problems​

Error: "Network error" or "Timeout"​

Cause: Connectivity issues.

Solution:

  1. Check your internet connection
  2. Verify that domains are allowed:
    • *.atlasdata.app
    • *.powerbi.com
    • *.microsoftonline.com
  3. Try again in a few minutes

Error: "CORS error"​

Cause: Browser or proxy configuration problem.

Solution:

  1. Clear browser cache
  2. Try in an incognito window
  3. Check proxy/firewall settings

Embed Problems​

Error: "Token generation failed"​

Cause: Issues with embed token generation.

Solution:

  1. Verify that the report supports embed
  2. Check embed permissions in Power BI Admin
  3. Verify that the dataset doesn't require credentials

Error: "Report loading failed"​

Cause: Report issues or RLS configuration.

Solution:

  1. Verify that the report opens normally in Power BI
  2. Check RLS settings
  3. Verify that the dataset is updated

Logs and Diagnostics​

How to get logs?​

  1. Open Developer Console (F12)
  2. Go to the Network tab
  3. Reproduce the error
  4. Export the log (HAR file)
  5. Send to suporte@atlasdata.com.br

Useful information for support​

When contacting support, include:

  • AtlasData Tenant ID
  • Complete error message
  • Screenshots of the problem
  • Steps to reproduce

Contact​

If the problem persists: