Forum Discussion
Issue while report embed to local intrahub
- Anonymous1 year ago
Hi aliaa ,
HTTP 403 errors in Power BI Service often occur due to missing dataset permissions, RLS blocking all data, expired credentials, gateway issues, or tenant and region restrictions.Troubleshooting & Fix Steps:
Check Dataset Permissions
In your Power BI workspace, find the dataset used by your report.
Ensure your account has both Read and Build permissions.
If Row-Level Security (RLS) is set up, confirm your account is assigned to the correct role and can access at least one row of data.
Verify Data Source Credentials
Go to Settings - Datasets - Data source credentials.
If there’s a yellow warning icon, update or re-enter your credentials.
For on-premises data sources, make sure the gateway is online and using valid credentials.
Check Tenant & Security Group Restrictions
Ask your Power BI admin to review Admin Portal - Tenant settings to confirm no policies are blocking your dataset access, such as cross-workspace usage or regional restrictions.
Refresh Authentication
Sign out of Power BI, clear your browser’s cache and cookies, then sign back in.
Try using an InPrivate/Incognito browser window to avoid cached token issues.
Validate Gateway & Refresh Status
If an on-premises gateway is used, check it’s running and connected.
Make sure the last dataset refresh was successful, as failed refreshes can prevent visuals from loading.
Check Service Status
Your cluster URI is wabi-australia-east-b. Visit Power BI Service Status to ensure there are no outages affecting the Australia East region.
Hi aliaa ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
Hi aliaa ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions