HI @Anusha66
You can’t configure a Fabric workspace so that it behaves exactly like a traditional “Power BI-only” workspace if it also contains Lakehouses or other Fabric items because Admin, Member, and Contributor roles can see and modify all items in that workspace.
However, there are a few approaches to hide or limit access to Fabric items while still hosting and sharing reports:
Use a separate workspace for sensitive Fabric items. Keep your Lakehouse or other Fabric objects in one workspace and store only Power BI reports (or a shared dataset reference) in a second workspace. Give your business users permissions only in the second “reports” workspace. As a result, they’ll see and interact with the reports without having any access to the Lakehouse.
Publish an app (instead of granting workspace roles). If you only need end users to view published reports, put the reports in the workspace, but don’t assign them a workspace role. Instead, publish the workspace as an app and share that app. App viewers won’t see other workspace items (like a Lakehouse), and they won’t be able to open or edit those items.
Give item-level permissions where needed.
If you must keep Lakehouses and reports in the same workspace, you can share only the report with users (either via Share > Manage Permissions or using the app) and avoid granting them a Viewer role on the Lakehouse. As long as you don’t grant “Read all” or “Build” permissions on the Lakehouse item, they won’t have direct data access
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
