Forum Discussion
Issue while report embed to local intrahub
I can see report on Power bi desktop & Fabric worksapce.
When i try to embed the HTML code to local intrahub it gives error mentioned below.
Http Status Code: 403
Activity ID: b003c78d-3c36-4233-85f9-2a9360ccac0f
Correlation ID: 1ea405ac-dce6-3da4-3b2d-dc4389b1ee68
Request ID: a21cb4ed-f287-4351-b0b9-2280447e002a
Time: Tue Aug 05 2025 12:50:57 GMT+1000 (Australian Eastern Standard Time)
Service version: 13.0.26369.35
Client version: 2507.3.25169-train
Cluster URI: https://wabi-australia-east-b-primary-api.analysis.windows.net/
Activity ID: b003c78d-3c36-4233-85f9-2a9360ccac0f
Request ID: a21cb4ed-f287-4351-b0b9-2280447e002a
Time: Tue Aug 05 2025 12:50:57 GMT+1000 (Australian Eastern Standard Time)
Service version: 13.0.26369.35
Client version: 2507.3.25169-train
Cluster URI: https://wabi-australia-east-b-primary-api.analysis.windows.net/
Http Status Code: 403 Activity ID: b003c78d-3c36-4233-85f9-2a9360ccac0f Correlation ID: 1ea405ac-dce6-3da4-3b2d-dc4389b1ee68 Request ID: a21cb4ed-f287-4351-b0b9-2280447e002a Time: Tue Aug 05 2025 12:50:57 GMT+1000 (Australian Eastern Standard Time) Service version: 13.0.26369.35 Client version: 2507.3.25169-train Cluster URI: https://wabi-australia-east-b-primary-api.analysis.windows.net/ Activity ID: b003c78d-3c36-4233-85f9-2a9360ccac0f Request ID: a21cb4ed-f287-4351-b0b9-2280447e002a Time: Tue Aug 05 2025 12:50:57 GMT+1000 (Australian Eastern Standard Time) Service version: 13.0.26369.35 Client version: 2507.3.25169-train Cluster URI: https://wabi-australia-east-b-primary-api.analysis.windows.net/
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.
7 Replies
Hi aliaa ,
The HTTP 403 error you're seeing typically indicates a permission or access issue when trying to embed the Power BI report outside of the Power BI service, such as in a local intranet or custom application.
Here are a few common reasons and suggestions:
Embedding Type - Make sure you're using the correct embedding method. Power BI supports:
Publish to Web (public, not secure)
Embed for your organization (requires user login)
Embed for applications (App Owns Data) using embed tokens
If you're using a simple iframe without proper tokens, the report may fail to load with a 403 error.
Permissions - Ensure the user or service principal used for embedding has:
Access to the report
Access to the dataset
The required permissions in the Power BI workspace
Authentication
If you're using secure embedding, you need to pass a valid access token (Azure AD or embed token) in your embedding code.
Network Access
If you're embedding within a local intranet, make sure the environment can reach Power BI endpoints like:
https://*.analysis.windows.net/https://*.powerbi.com/
Firewall or proxy restrictions could block these, causing errors.Recommended Approach
For secure and reliable embedding, it’s recommended to use the Power BI JavaScript SDK and generate tokens programmatically. Embedding through plain HTML may not be sufficient unless using a public "Publish to Web" link (which is not recommended for sensitive data).
Summary
The 403 error usually comes down to missing permissions, incorrect embedding method, or lack of a valid token. Please check these areas to resolve the issue.
Best regards,
Sreeteja.- Tutu_in_YYC
Super User
what does it say here?
A network error was encountered check your connection to the internet. See details
When you ckeck on see details
Error fetching data for this visual
Couldn't retrieve the data for this visual. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.See details- Http Status Code403
- Activity ID792e29fb-6274-42d4-ba8e-8bf80f9c2367
- Correlation IDdfed07fa-1641-1898-3694-add4565e245f
- Request IDb19abfcd-ccbe-c6cc-9eb3-5ef67eafa3e7
- TimeThu Aug 07 2025 07:51:22 GMT+1000 (Australian Eastern Standard Time)
- Service version13.0.26414.36
- Client version2507.4.25234-train
- Cluster URIhttps://wabi-australia-east-b-primary-api.analysis.windows.net/
- Activity ID792e29fb-6274-42d4-ba8e-8bf80f9c2367
- Request IDb19abfcd-ccbe-c6cc-9eb3-5ef67eafa3e7
- TimeThu Aug 07 2025 07:51:22 GMT+1000 (Australian Eastern Standard Time)
- Service version13.0.26414.36
- Client version2507.4.25234-train
- Cluster URIhttps://wabi-australia-east-b-primary-api.analysis.windows.net/
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.
