data protection
1343 Topics
Why does AD group need access to underlying dataset, but direct access user doesn't?
I have a personal MS List and a personal Power BI Service dashboard. All stored in my JohnDoe personal account. If I share the dashboard with JaneDoe, then she can view the dashboard without issue, even though she doesn't have access to the underlying MS list. But if I share the dashboard with a DivisionManagement Active Directory group, then a manager who is in that group gets an error message when opening the dashboard link: Permission required. You cannot see the content of this report because you do not have permissions to the underlying dataset. Please contact the dataset owner to request access. Why does an Active Directory group need access to the underlying dataset, but a direct access user doesn't?34Views0likes2Comments
Right-sizing Fabric capacity with 11 models and 47 dataflows: where do you stop?
Hi all, I'd like to ask how you'd approach a Power BI and Fabric environment that has grown past what the capacity can comfortably handle, because I'm not sure we found the best way through it. The environment has been growing since 2021 and now has 11 complex semantic models (sales, production, job costing and finance) fed by 47 dataflows. Sources are an Odoo ERP hosted on AWS, Google Sheets and Google Drive, with ingestion through Power Automate. Over time the symptoms piled up: slow refreshes, heavy load on the server, and Fabric consumption that was higher than it should have been. On the governance side there were shared logins, weak role-based controls and unstructured workspaces. We started with an audit of every model, dataflow, governance setting and the Fabric usage. Then we consolidated fragmented models to cut redundancy, redesigned the dataflows, and moved to incremental refresh with query folding where possible. For governance we added RBAC, a Dev/Test/Prod workspace structure, sensitivity labels and lineage tracking, plus a certified semantic model and quarterly audits. After the optimization, we were able to bring capacity down from 64 CU to 16 CU, and in some cases 8 CU. What I'm curious about is how you decide where to stop. How do you know how far you can go on right-sizing before refresh windows or interactive queries start to suffer? Do you look at the Capacity Metrics app over a few weeks, or do you test by dropping the SKU and watching? And how much do you rely on smoothing and bursting? With 47 dataflows, would you keep them as dataflows, or move some of the heavier logic into a Lakehouse or Warehouse? And with sources like Google Sheets and an ERP, how do you confirm query folding is actually happening and not silently falling back? On model consolidation, did you go for fewer, bigger models or a central certified model with thin reports? What did that do to refresh times and to your DAX? Last one: for the Dev/Test/Prod setup, are you using deployment pipelines, or something else? Has anyone found a way to keep dataset and dataflow parameters from breaking between stages? Would love to hear how you've handled this.Solved64Views0likes7Comments
Need to implement - 1 semantic data model - 2 reports (1 with rls and 1 without rls)
Hi, I have created a common semantic data model. On this data model we are creating 2 power bi reports. Report 1 - needs to have RLS. Report 2 - Should be without RLS. We initially thought we will built a common semantic data model and then tie Report 1 with an RLS excel file. But we are unable to filter rows from common semantic data model in Report 1. Now, we are thinking of putting RLS in common semantics data model, which makes Report 1 as expected, but then we are unable to bypass RLS in Report 2. Can anyone please help me with this issue? How can i design the data model and report to acheive my goal?Solved1.5KViews0likes8Comments
Fabric Data Agent Access issue
I have created a fabric data agent using semantic model of a published report, It is working fine but I'm not able to share it with others I published the agent in M365 copilot and share with my teams of 100 people only 4 or 5 people can go to M365 copilot and search the agent and added the agent to their agent tab others are not even seeing the agent but if I share the agent link from M365 copilot then they see the agent but agent is not answering the questions but it's perfectly answering for me and other 4 to 5 people who see the agent when I surfed it said it said there are 2 level of access to get answer from the agent 1. agent level access 2. underlying data level access I have workspace contributor access for workspace, read, write, reshare permission for the agent. most of them share the same access but there are not able to see the only difference I found is I'm having premium per user license and most of other have pro license so I doubted it but internet says license is not an issue can anyone pls help me with this issue96Views0likes13CommentsMoving finance Excel reporting to Power BI: how would you handle versioning and RLS?
Hi all, I’d like to ask how you’d handle a finance reporting setup where the source is still Excel, because I’m not sure we landed on the best design. The sources are multiple Excel files with budget, cost and revenue data, maintained separately for different regions. The problems were the usual ones: combining the files led to duplication and inconsistencies, several versions of the same file were circulating, and reconciling everything took a lot of manual effort. Budget vs. actuals and profitability trends were hard to track, and sensitive financial data was being shared without any role-based access. For the fix, we set up predefined formats, validation checks and version control on the Excel inputs, then used Power Query for the ETL, with dataflows handling integration and versions. The financial datasets are stored in SharePoint/Cloud behind role-based access, with the Data Gateway for connectivity. In Power BI we used hybrid data modeling with automated refreshes, row-level security, deployment pipelines and audit logs for governance. The reports cover variance analysis, KPIs and trend lines across regions. So here’s what I keep wondering. When the inputs are still Excel files owned by finance teams, how strictly do you enforce a template at the source? Do you reject files that fail validation, or clean them up downstream in Power Query? For version control, are you relying on SharePoint versioning, dataflow versions or something else? And how do you stop someone from still emailing around a “final_v3” file next to the governed report? On the model side, we went with hybrid modeling. How do you decide what to import and what to leave in DirectQuery or a composite model, especially for budget vs. actuals? And with RLS across regions, how do you manage the roles as the number of regions and stakeholders grows? Do you map roles through security groups, or maintain a mapping table in the model? Last one: deployment pipelines work fine for the reports, but has anyone found a clean way to handle dataflow and parameter changes between stages without breaking the gateway connections? Would love to hear how you’d approach it.Solved86Views1like5Comments
Power BI Report Usage Metrics – Workspace-Level and Organization-Level Usage
Power BI Report Usage Metrics – Workspace-Level and Organization-Level Usage Hi everyone, I am working on a Power BI governance requirement around report usage metrics, and I am trying to understand the recommended approach at both the workspace level and organization/tenant level. I have some initial understanding of the available options, but I would like to get confirmation from the community and understand if there are better/native approaches. Workspace-Level Report Usage If I have multiple reports within a single workspace, I would like to see the usage metrics for ALL reports in that workspace in one place. For example: Workspace A Report 1 → Views / Unique Viewers / Last Viewed Report 2 → Views / Unique Viewers / Last Viewed Report 3 → Views / Unique Viewers / Last Viewed Instead of opening Usage Metrics separately for each report. My understanding is that the Usage Metrics semantic model can potentially be used to create a custom usage report for the workspace. However, I would like to confirm: How exactly can we get usage metrics for all reports within a single workspace? Is there a supported way to remove/modify the report-level filtering so that the Usage Metrics semantic model covers all reports in that workspace? Is this the recommended approach for workspace-level usage reporting? Are there any limitations with this approach? Organization-Level Report Usage The next requirement is to go beyond a single workspace. I would like to build a centralized view such as: Organization → Workspace → Report → Views → Unique Viewers → Last Viewed → Other Usage Metrics For example: Organization Workspace A Report 1 Report 2 Report 3 Workspace B Report 4 Report 5 Workspace C Report 6 Report 7 All of this should ideally be available in one centralized Power BI governance report. For this requirement, I know there are some possible approaches, such as: Using Power BI/Fabric Admin Portal capabilities with the required admin access Using Power BI Admin APIs Using Power BI Activity Log APIs Building a custom data collection process and storing the information in a Fabric Lakehouse/Warehouse/SQL database But my questions are: Are these the only practical/supported ways to achieve organization-wide report usage? Is there any native Power BI/Fabric feature that already provides tenant-level usage metrics across all workspaces? Can the standard Usage Metrics semantic model be consolidated across multiple workspaces? Is there another Microsoft-supported API or Fabric capability that is better suited for this requirement? What permissions/admin roles are actually required for the different approaches? Workspace-Level vs Organization-Level I am particularly interested in understanding whether the recommended architecture is different for these two scenarios: Scenario A: Single Workspace → All Reports → Usage Metrics Scenario B: Entire Organization → All Workspaces → All Reports → Usage Metrics Would we use the Usage Metrics semantic model for Scenario A and Admin APIs/Activity Logs or another centralized source for Scenario B? Or is there a common approach that can handle both? Historical Usage Another concern is data retention. My understanding is that the current Usage Metrics experience has a limited historical window, with the new Usage Metrics experience retaining 30 days of data. If we need to retain usage information for: 6 months 1 year Multiple years what is the recommended approach? Would this be the appropriate architecture? Power BI / Fabric Usage Data → API / Activity Log / Other Source → Fabric Lakehouse / Warehouse → Historical Usage Table → Centralized Governance Dashboard Or is there a Microsoft-native approach that can retain this historical information without building our own storage layer? Final Architecture Question Ultimately, I am trying to determine the recommended approach for: Organization ↓ Workspace ↓ Report ↓ Usage Metrics ↓ Historical Usage I would appreciate guidance on: How to achieve workspace-level usage for all reports How to achieve organization-wide usage across all workspaces Whether Admin Portal/API/Activity Log approaches are the only options Whether there is a native Fabric/Power BI capability I may be missing How to handle the 30-day Usage Metrics retention limitation Recommended architecture for long-term Power BI governance and usage tracking Thanks in advance to anyone who can share their experience or recommended approach.Solved124Views1like4Comments
How to avoid view count on Audit Data of unauthorized person in Usage metrics
Hi My name is Haris, I have a Power BI app link which I share with someone who does'nt have access to it. But when he clicks the app link, the usage metrics or audit data still captures it has 1 view count since he clicked that link. Since he does'nt have access to that app, the usage metrics should not include the count of that person who does'nt have access to it. Please help me to relsolve this issue or help with the work around. Thanks in advanceSolved101Views0likes7Commentswhat’s the most cost-effective option?
Hi everyone, I’m currently working as a Data Analyst for a BPO company, where we still rely heavily on traditional Excel dashboards and tables to share weekly performance. At the moment, I have to prepare and send separate reports to each Supervisor by email. We have 12 Supervisors, 3 ACMs and 1 Manager so this process is becoming quite time-consuming and repetitive. I brought an idea to my manager about creating a Power BI dashboard that centralizes all the data in one place. The idea is that Supervisors, ACMs, Managers, and Agents would be able to access the dashboard and see the data relevant to them, along with additional insights and interactive analysis. For example: Agents → only see their own performance Supervisors → only see their assigned agents ACMs → see the Supervisors/teams under them Managers → see the relevant overall hierarchy I’m planning to use Row-Level Security (RLS) to control access. However, my main concern now is architecture and licensing cost. Since this is for a BPO account with potentially a large number of Agents giving every user an individual Power BI license could become expensive. So I’m looking for a cost-effective architecture using Power BI. A few questions I have: Do I actually need Microsoft Fabric for this scenario, or can Power BI Pro handle it? What would be the most cost-effective architecture for a large number of users with RLS? Would Power BI Pro licenses for users be better, or would Fabric capacity make more sense as the number of viewers grows? Since the source data is currently Excel files would you recommend keeping Excel + Power Query or moving the data into Fabric/OneLake Is there a better architecture that would reduce both licensing and maintenance costs? I’d really appreciate advice from anyone who has implemented a similar BPO performance dashboard with hierarchical RLS and had to deal with a large number of users.Solved82Views0likes3CommentsOAuth token refresh fails intermittently when pbi on server refrehses
Situation: Data source connection failed and visuals doesn't work as expected in pbi on Server. Root causes: OAuth token refresh fails intermittently on PBI server. Questions: how do I get UAuth token expiration in advance? Do we have a workaround to avoid it?Solved75Views0likes4Comments
