Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I am trying to figure out whether Publish to Web can be used to display aggregate results to the public based on confidential row-level data.
The publish to web documentation states that "ensure you have the right to share the data and visualizations publicly. Do not publish confidential or proprietary information." It also states that "Power BI caches the report definition and the results of the queries required to view the report."
Does data/results of the queries mean data accessible within the report, or the underlying row-level-data present in the data model? Does publishing to web expose the underlying data in some way, or does it remain secured?
Solved! Go to Solution.
@chrisu In my experience using publish to web only for aggregrates has worked fine without exposing underlying data. There was particular feature I was concerned about which is 'See Records' and 'See Data' whereas in power bi service it will let you see underlying row level data for the selected visual for a report. That doesn't happen when report is published to web ie underlying row level data is not seen by the user in anyway and that meet my requirements.
However if your data is too sensitive I would suggest using against it or another possible solution is to aggregrate at the data source level and import that into power bi so power bi doesn't have your row level data.
@chrisu In my experience using publish to web only for aggregrates has worked fine without exposing underlying data. There was particular feature I was concerned about which is 'See Records' and 'See Data' whereas in power bi service it will let you see underlying row level data for the selected visual for a report. That doesn't happen when report is published to web ie underlying row level data is not seen by the user in anyway and that meet my requirements.
However if your data is too sensitive I would suggest using against it or another possible solution is to aggregrate at the data source level and import that into power bi so power bi doesn't have your row level data.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.