Forum Discussion
Export failed
Solution SageHi ManasRout0396,
Echoing AvdBerg and rampie: the fact that the same export works on the office network and fails at home is the most useful clue, because it separates the account and the report (same in both places) from the environment around them. Two broad families of cause fit that pattern: something on your home connection or device is blocking part of the export, or your organization applies different access rules depending on where you sign in from. I have not seen your error text, so the table below lists what each cause looks like and how to test it.
Likely causes and how to test them
| Cause | What you would see | Quick test |
|---|---|---|
| VPN, proxy or security software at home | Error mentions network or connection; export starts then fails | Turn it off temporarily, or connect to the company VPN and retry |
| Browser extension (ad, privacy or script blocker) | Works in a private window with extensions disabled | Try a private window, or another browser |
| DNS or firewall on the home router | Other Power BI pages load but the download request fails | Try another network, such as a phone hotspot |
| Entra Conditional Access (location, device compliance) | Sign-in works but downloads are blocked or limited | Ask your admin to check sign-in logs for the failed attempt and the Conditional Access result |
| Tenant export or download setting | Same error everywhere, not only at home | Ask your admin whether export and download settings changed |
| Defender for Cloud Apps session control | Downloads blocked or forced through a proxy from unmanaged networks or devices | Ask your admin whether a session policy applies to Power BI |
A practical order
1. Retry in a private window with extensions off
2. Retry on a phone hotspot (rules out home router and ISP)
3. Retry on the company VPN (rules in an access policy tied to network location)
4. Copy the exact error text and the time of the attempt
5. Give your admin the time, your account and the error to look up in the sign-in logsIf steps 1 to 3 all fail the same way at home but work at the office, the cause is almost certainly a location-based access rule, and only an admin can confirm or change it. If only step 1 changes the result, the culprit is the browser or an extension.
So my overall approach would be:
Isolate -> browser, network, VPN in that order
Capture -> exact error text and timestamp
Escalate -> admin checks Conditional Access / Defender / export settings using the sign-in logsAI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.