Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
Hello,
Recently I'm playing Power BI with data and reports,
This is a general question:
From Security point of view, is there any advantage or disadvantage, between using DirectQuery or Import?
What I mean is I understand when using import security can be filtered at Power BI level,
and if use DirectQuery security setting goes to Data Source level,
but cannot see further if there's any functional difference between those 2(in security).
Anyone have any best practice or thoughts are appreciated.
Thanks!
Solved! Go to Solution.
As you said, using import security can be filtered at Power BI level since the data has been loaded into Power BI Desktop. And for direct query, the security is controlled on data source side. There's no other functional different on security aspect. For choosing direct query or import, you need to consider the data amount (1GB limit for dataset size) and refresh frequency. Please refer to a blog below:
Power BI – Live connection vs. Import, comparison and limitations
Regards,
As you said, using import security can be filtered at Power BI level since the data has been loaded into Power BI Desktop. And for direct query, the security is controlled on data source side. There's no other functional different on security aspect. For choosing direct query or import, you need to consider the data amount (1GB limit for dataset size) and refresh frequency. Please refer to a blog below:
Power BI – Live connection vs. Import, comparison and limitations
Regards,
Taking this question a bit further. As an admin I would like to prevent end users from importing data directly via the "get data".
1. Is there any way to secure the Import vs. Direct Query functionality? In other words can I disable "import"?
2. Are there other methodologies for achieving the same end? In other words can we prevent specific types of data sources at the Power BI level - or (in a simple scenario) do we modify the DB security to prevent direct connection to underlying tables and only allow access to views in a DB or a tab / olap model in SSAS...?
Thanks for any advice around security concerns between developers and users. Our goal is to give the user as much self-service functionality as possible without constantly "importing" the same or similar data sets in an enterprise implementation.
Thanks again,
Nick
1. Is there any way to secure the Import vs. Direct Query functionality? In other words can I disable "import"?
Has this question been answered in the meantime?
Would be also relevant for me.
Thanks,
Bettina
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 9 | |
| 8 | |
| 8 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 37 | |
| 29 | |
| 26 | |
| 19 | |
| 19 |