fabric data agent access issue in M365 copilot
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 issueFabric 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 issue
Power BI M-Query with TVF execution issue
Dear Team, I have designed a report in Power BI it is art of a Tableau to Power BI migration. I have separated the visuals among three pages with drill through option. It is working as expected but facing a slowness. So I think to use a benefit of M-Query with TVF passing parameter values to make pushdown query. parameter value is a single parameter and accept a comma separated values from 1st page visual. However I have created TVF. TVF is executing properly in DB side. But when I create a bind parameter and associated with my column make it text and enable multi option to get multiple values . Now I write a code snippet let VP=if P_param= null or P_param= "" or P_param= "XXXX" then "ALL" else if Value.Is(P_param, type list) then Text.Combine(List.Transform(P_param, Text.From), ",") else Text.From(P_param), SQL_Query = "SELECT * FROM MY_TVF('" & VP & "')", Source = #table({"Generated_SQL"}, {{SQL_Query}}) in Source This code has been written to check whether the selected parameter from visual VP=1001 is passing properly in TVF. Objective: 1. SELECT * FROM MY_TVF('1001,1002') (if multiple value selected from visual) 2. SELECT * FROM MY_TVF('1001') (if single value is sent) But when I click from visual using drill through feature the TVF is showing always SELECT * FROM MY_TVF('ALL') - The drill through fields when I put in the 2nd page then it is showing proper values . but it is not passing in the TVF so query is not executed it returns blank. My objective is from 1st page matrix visual when I select record one by one accordingly the value will pass and show the result. In matrix 1st column is A1 and A2 is the second column. A1 & A2 are also in drillthrough bucket. A1 can contain multiple A2. so when one A1 is selected then multiple comma separated A2 has been passed in TVF. A2 is an id field. and when A2 column it self selected then single value will pass. But value is not passing and I am not getting the benefit of query pushdown by M-Parameter. The A2 column is parameter binded. it is a text field. P_Param= A2. (bind to A2) . multiple accepted. could you please check and provide any assistance? I have tried all possible options but no results has been encountered. Regards Jishnu Bhattacharya
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.
Support needed with the calculated column
Using Power Query, I have loaded the data to the data model. I need support with a couple of questions How can I create a cumulative calculated column For the Qty at SKU, Date Level, and Sorted by Date Date SKU QTY 4/26/2025 B 54 4/4/2025 C 12 1/23/2025 A 57 5/18/2025 B 61 1/23/2025 C 79 3/20/2025 B 37 1/3/2025 C 86 4/27/2025 C 67 3/14/2025 A 93 1/3/2025 B 51 1/3/2025 A 11 2/17/2025 A 95 2/25/2025 C 32 4/5/2025 A 25 2/11/2025 B 76Power BI Field Parameters with Paginated Reports – Looking for Guidance
Power BI Field Parameters with Paginated Reports – Looking for Guidance Hi everyone, I am trying to understand the best approach for using Power BI Field Parameters with Paginated Reports. I understand that Power BI Field Parameters allow users to dynamically switch between fields or measures in a Power BI report. My question is whether similar functionality can be achieved when working with Paginated Reports. For example, I am looking for something like: Power BI Report → Field Parameter → Paginated Report → Dynamically change the field/column displayed or used by the Paginated Report Specifically: Can a Power BI Field Parameter be passed to a Paginated Report? Can a Paginated Report consume a Power BI Field Parameter directly? Can a Field Parameter be used to dynamically determine which column/field is used in a Paginated Report query? If Power BI Field Parameters are not supported for this scenario, is there an equivalent out-of-the-box feature in Power BI Report Builder / Paginated Reports? Can this be achieved using standard Paginated Report Parameters, expressions, or dynamic query logic? Is the Paginated Report visual in Power BI the recommended way to achieve this type of interaction? For example, the desired experience would be: User selects: Customer Name OR Product Name OR Supplier Name and the Paginated Report dynamically uses the selected field/column. I understand that Power BI Field Parameters and Paginated Report Parameters are different concepts, so I am specifically trying to understand whether there is a supported way to achieve the same dynamic field-selection experience in Paginated Reports. If anyone has implemented this scenario, I would appreciate guidance on the supported approach and any limitations. Thanks!
Is creating an Azure Key Vault reference supported through REST API?
I'm trying to automate the creation of an Azure Key Vault reference I can list existing key vault connncections created through the portal using: GET https://api.fabric.microsoft.com/v1/connections However, I have not been able to create one using: POST https://api.fabric.microsoft.com/v1/connections The supported connection types response lists AzureKeyVault with OAuth2 and service-principal authentication, but I cannot find a documented working example. OAuth2 creation appears to use undocumented Power BI endpoints through the portal, while service-principal creation returns an invalid credentials error (valid credentials, rbac assigned, public open key vault..). is creating an Azure Key Vault connection/reference currently supported through a public API? If so, could someone share a working request example? Or must these connections currently be created manually through the portal?How are teams automating Power BI development workflows using AI agents?
I am exploring how AI agents can help automate repetitive tasks in Power BI development and data workflows. Some possible use cases: Automatically generating reports from business requirements Triggering data preparation workflows through APIs Validating datasets before publishing dashboards Detecting anomalies and suggesting improvements Automating documentation for datasets and reports I am interested in learning how developers are currently combining Microsoft Fabric, Power BI APIs, notebooks, and AI agents. What architecture patterns or best practices are you using for AI-driven BI automation?
