Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hello. I have a deployment pipeline in Power BI.
I want to give end users access to the Exploratory Workspace, however, i want to ensure they dont use the reports in this workspace for 'real reporting'. i need to way to ensure that users are aware Exploratory and that ANYTHING in this workspace is not supported.
What is the best way to acheive this?
Solved! Go to Solution.
Hi @PPStar
Thanks for the clarification, makes sense. In that case, I suggest the following approaches:
1) Use Dataset Endorsement -> In Power BI Service, datasets can be endorsed as "Promoted" or "Certified." Use these flags for production-ready data, and ensure that this dataset is not endorsed, so users know it's not an official or approved dataset.
2) Define and communicate a Dataset Expiry date -> If the dataset is temporary, consider setting an expiration date for it. State that after this date, the dataset can/will be automatically removed or flagged for review.
Hi @PPStar
If you aim to grant access to both datasets and existing reports but ensure they are not used for production purposes, my suggestion is to flag existing artifacts:
If you aim to grant access just to reports, you might consider granting access exclusively via APP.
If you aim to grant access just to datasets, you might consider disabling build permissions and/or having a separate workspace outside the deployment pipeline as a sandbox for the users.
Thank you so much for your response.
Whilst i agree with all of the above, this will work for the actual report.
However, once they have access to the dataset, nothing stops the users from connecting to the dataset using a Live Connection and then build their own reports.
How can we ensure the dataset in EXP is clearly states that data is not production ready.
Hi @PPStar
Thanks for the clarification, makes sense. In that case, I suggest the following approaches:
1) Use Dataset Endorsement -> In Power BI Service, datasets can be endorsed as "Promoted" or "Certified." Use these flags for production-ready data, and ensure that this dataset is not endorsed, so users know it's not an official or approved dataset.
2) Define and communicate a Dataset Expiry date -> If the dataset is temporary, consider setting an expiration date for it. State that after this date, the dataset can/will be automatically removed or flagged for review.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.