A short list of the errors users hit most often, with the cause and the recovery path. For refresh performance (slow refreshes that succeed eventually) see Why is my data refresh slow or taking a long time?.
401 Unauthorized in Power BI Desktop or Power BI Service #
Cause. Power BI is sending credentials that the connector doesn’t recognise. The most common reason is that the personal access token bound to this data source has been revoked, has expired (if your HubSpot account enforces an expiry policy), or was never re-entered in Power BI after being rotated.
Fix. In the connector, open Access Tokens and check the row for the token you’re using. If it is Revoked or Expired, create a new token. Then update the credentials in Power BI:
- Power BI Desktop — File → Options and settings → Data source settings, find the OData URL, edit its permissions, and re-enter your HubSpot username + the new token.
- Power BI Service — on the dataset, Settings → Data source credentials → Edit credentials, same fields. Note that Desktop credentials and Service credentials are stored separately; re-entering them in Desktop does not propagate to Service.
403 Forbidden after the data source worked before #
Cause. The token is still valid, but the data source is no longer accessible to the user behind that token. This usually happens because the data source was deleted, you were removed from its sharing list, or ownership was transferred to a user you don’t share with.
Fix. In the connector, switch to the Shared with me filter on the Data Sources page and look for the row. If it’s missing, ask the owner (or a HubSpot Admin) to re-share it with you, or re-create the data source in your own account. If the data source was deleted, re-create it — the original OData URL cannot be recovered.
Still stuck? #
Reach out via Contact Support.
