If authentication succeeds but data isn't returned, or if you encounter errors when trying to access metadata or workspaces, check the following:

Blank Dataset Previews or No Tables Returned

• Ensure your AzureTenant value is correct — it must match the tenant ID (GUID or verified domain) where your Power BI workspace resides.
• Confirm that the Power BI workspace is backed by a Premium capacity. Non-premium workspaces are not accessible over the XMLA endpoint.
• If using a Service Principal, it must be assigned as an admin to the workspace. Viewer or Contributor roles are not sufficient.

OAuth Token Refresh Issues

• If you receive token expiration errors, confirm that InitiateOAuth is set to REFRESH after the initial token exchange.
• Check that OAuthSettingsLocation points to a file the driver can read and write, especially in headless environments.
• Refresh tokens may expire or be revoked; if this occurs, you must repeat the full OAuth flow.

Missing Admin Consent or Misconfigured Permissions

• Review your application's permissions under API Permissions in the Entra admin center.
• If your app uses Application permissions, an administrator must grant tenant-wide consent.
• Missing permissions (Dataset.Read.All) or incorrect permission types (Delegated vs. Application) can cause silent failures.

AzureTenant Issues

• If the tenant ID is missing or incorrect, authentication may succeed but no data will be available.
• You can use either the GUID or the verified domain name of the tenant, but they must match the tenant where your workspace is hosted.

Delays in Permission Propagation

• After assigning a role (for example, Service Principal access to a workspace), it may take several minutes for permissions to propagate.
• If your app was just registered or updated, wait a few minutes and retry the connection.