Forum Discussion
Question about Query activity and security issue with Datasets with Execute Query REST API
- 2 years ago
Would a user (accidentally) be able to use this process to circumvent the procedures to share protected internal use only data with external email addresses when running a query against a Power BI dataset?No, but they can - accidentally, of course - download the data (or make a screenshot) and send an email to the external contact. Nothing you can prevent technically - this needs to be covered by SBC (standard of business conduct) rules.
I assume I'm going to see "Analyzed by External application" as the query activity for these Power Automate flows the user has for this REST API, is this correct?No, that is separate. MDX queries ("Analyze in Excel") are audited different than DAX queries, and different than XMLA queries.
The data extraction limits per call are quite murky. A ballpark number is 1 million data points (rows times columns) for DAX - but that is only a guidance.
Not sure where your 120 requests per minute limit comes from? Not aware of such a thing. Are you on a P1/F64 ?
- 2 years ago
There's a limit of 120 query requests per minute per user, regardless of the dataset that's queried.That's a bit of a fluff - I don't think it is related.
You use the Premium Capacity metrics app to gauge how healty your capacity is. For reference - we have P3 capacities with well over 100K queries per minute doing just fine.
Thank you lbendlin for the reply. The 120 requests per minute is from the Limitations section of this page Datasets - Execute Queries - REST API (Power BI Power BI REST APIs) | Microsoft Learn. I actually was concerned that so many queries could be run in such a short time, because I was concerned about the capacity CU impact. Yes, we are on P1.
There's a limit of 120 query requests per minute per user, regardless of the dataset that's queried.
That's a bit of a fluff - I don't think it is related.
You use the Premium Capacity metrics app to gauge how healty your capacity is. For reference - we have P3 capacities with well over 100K queries per minute doing just fine.