Showing results for 
Search instead for 
Did you mean: 
Advocate II
Advocate II

Formula.Firewall: Query references other queries, so it may not directly access a data source.

I am getting the following error:



Formula.Firewall: Query 'Query1' (step 'Added Custom') references other queries or steps, so it may not directly access a data source. Please rebuild this data combination.


In my first query I am accessing an API to get a list of URLs. In the second query it uses this list of URLs to then go back to the API and request all of the data.


I understand what the complaint is, but how do I get around it? I am actually always hitting the same domain for both queries, but maybe it doesn't know that. I suppose it wouldn't know that until runtime.


I have read that in Excel PowerQuery you can go to:


File=>Options and Settings=>Options and set the Ignore Privacy Levels option.


But no such option seems to exist in Powe BI Desktop. Does anyone know what I'm doing wrong or how I can get around this restriction, it seems like a common usage scenario?






Ken Puls blogged about this here

* Matt is a Microsoft MVP (Power BI) and author of the Power BI Book Supercharge Power BI.

View solution in original post

New Member

Excelente respuesta, a mi me funcionó dando clic en esa ruta: File=>Options and Settings=>Options and set the Ignore Privacy Levels option.

Regular Visitor

Regular Visitor

Thank you...

This sorted it for me.

Method 1: Ignore Privacy Levels

Advocate II
Advocate II

Six years later and the Privacy Option is still the (only) necessary fix to solve this issue. 😏

Is it going to cause any problem if the privacy level setting is turned off?? 

Yes it is a big superproblem, as it will not refres in webservices if you disabling privacy level

The privacy settings are designed to prevent accidentally sending sensitive data somewhere you shouldn't. Eg.  Imagine you have a table in SQL with staff details including salaries. You write a query that joins this data to Facebook data (for some reason). The privacy settings will stop the private data in SQL being sent to the open data source, Facebook. As long as you don't have any such queries, turning off the privacy settings will have no impact. Eg, as long as all your data sources are internal to your organisation. 

* Matt is a Microsoft MVP (Power BI) and author of the Power BI Book Supercharge Power BI.


Thanks Matt!! That is very clear explanation!! 

Helper IV
Helper IV

Hi @markive , I had the same issue as you in 2016. Fortunately in 2020 there is Privacy Levels option which can be changed. If set it to "Ignore the Privacy Levels and potentially improve performance" the issue becomes resolved.

Advocate III
Advocate III

For anyone still experiencing this issue, under File > Options, select Privacy, and if it's appropriate, select Ignore privay levels.  Even after following all the other suggestions referenced in this thread, I still got an error when refreshing.  It worked when I was in the Query Editor just fine (no errors), but refreshing from the regular report view would fail.

thank you

I can not believe this do work, and no failure rasied after clicking apply change. thanks, buddy!

Not applicable

The advice provided in this blog post now appears to be running contrary to experience in Power BI.


A query that contains all the Web.Contents calls a query needs leads it to function correctly. The splitting of the different Web.Contents calls into seperate queries before being merged into one final query leads an error to be thrown.

Not applicable

In case it helps others I ran into this issue after adding a non-supported/unofficial custom connector into PBI desktop and then trying to run queries against SharePoint files. 

Removing the custom connector from the local Documents > Power BI Destop > Custom Connectors folder got rid of the issue for me. (Note I didn't have any quries using the custom connector, just the fact it was there seemed to trigger the firewall thing).

Frequent Visitor

Thanks for the solution, I was struggling to solve this and now it works

Advocate I
Advocate I

Please try the following in Power BI Desktop:

File -> Options -> Privacy -> Select “Ignore Privacy Levels…”

It helped me.

Fantastic! This saved my day (and most of yesterday 🙂 )



I did this privacy level change, it solved for Power BI Desktop refreshes, but web refresh is still failing due to the same error.

This is the article previously referenced in this thread:

I confess I had to read it a few times to get it.


from the article by Ken Pulsfrom the article by Ken Puls

Basically, each query needs to be loaded into a staging query first. Then, you can combine these staging queries.




You wrong it not working like you think, separated queries still show error firewall

Helpful resources


2023 Release Wave 1 Plans

Power BI release plans for 2023 release wave 1 describes all new features releasing from April 2023 through September 2023.

Power BI Summit Carousel 2

Global Power BI Training

Make sure you register today for the Power BI Summit 2023. Don't miss all of the great sessions and speakers!

Thank you 2022 Review

2022 Monthly Feature Releases

We had a great 2022 with a ton of feature releases to help you drive a data culture.