interesting links
1046 TopicsBest Practices for Automating Power BI Dataset Refresh and Monitoring Failures
Hi everyone, I'm exploring different approaches to managing automated semantic model refreshes and monitoring failures across multiple Power BI workspaces. For organizations managing several reports and data sources, maintaining reliable refresh schedules and identifying failures can become challenging as the environment grows. I'm particularly interested in how teams are approaching the following: Are you primarily using Power BI's native scheduled refresh capabilities, Power Automate, or REST APIs for refresh orchestration? How are you implementing centralized monitoring and automated notifications when refreshes fail? What strategies work best for handling refresh dependencies and retries without triggering duplicate executions? Are there recommended approaches for integrating Power BI refresh monitoring with existing enterprise automation workflows? I'm interested in understanding which approaches are most practical for environments with multiple workspaces, particularly when reliability, maintainability, and operational visibility are priorities. Would appreciate any recommendations, architecture patterns, or real-world implementation experiences. Thanks in advance!33Views2likes4CommentsSelect Entire Hierarchies in Power BI Personalize Visuals
Feature Request: Select Entire Hierarchies in Power BI Personalize Visuals Hi Power BI Team, I'd like to suggest an enhancement to Personalize Visuals that allows users to select an entire hierarchy from a semantic model instead of adding each level individually. For example, my semantic model contains this hierarchy: Responsible Division Hierarchy Responsible Division Responsible Cost Center Currently, when users open Personalize this visual, Power BI correctly displays the hierarchy in the field picker. However, selecting the parent hierarchy does not add the complete hierarchy to the visual. Users must expand it and add each level individually in the correct order. Expected Behavior Users should be able to select Responsible Division Hierarchy and have Power BI automatically add the complete hierarchy to the visual, preserving the order defined in the semantic model. Individual hierarchy levels should remain selectable for users who only want a specific field. Why This Matters Personalize Visuals is designed to enable self-service reporting without requiring report editing permissions. Requiring users to manually reconstruct existing hierarchies creates unnecessary friction and assumes they understand the underlying data model. Since the hierarchy is already defined in the semantic model and recognized by the field picker, Power BI should leverage that metadata. Suggested Enhancement Allow users to select either: The parent hierarchy to add the complete hierarchy in its predefined order. An individual hierarchy level to add only that field. This would make Personalize Visuals more intuitive for business users while preserving flexibility for advanced users. Thanks for considering this enhancement!67Views2likes2CommentsFabric 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 issueSolved135Views0likes13CommentsPower 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.Solved169Views1like4CommentsDeployment pipelines
Hi community , in this time, I would like to know if there is a way to rollback a deployment pipeline? I mean. I have a 1SM and 1 report A to deploy from devel to test enviroment, but I have to restoration a previous version en test. before the deploy pipeline it had made. e.g. Deploy devel -> test it going to previous version test -> devel thanks in advance.Solved4.1KViews0likes4CommentsHow to get the internal Page Name and Visual Name for Power Automate
Hi everyone, I am trying to automate a daily Power BI report email using Power Automate. My requirement is: Power BI Report ↓ Power Automate ↓ Export a specific Power BI visual as PNG ↓ Embed the image in an HTML email ↓ Send the email daily I already have an existing Power Automate flow that sends an HTML table successfully. Now I also want to include a Power BI chart below the table in the same email. I am using the Power BI action: "Export To File for Power BI Reports" I have selected: - Workspace - Report - Export Format = PNG The action provides the following fields under Pages: - Pagename - Visualname - Bookmark Name - Bookmark State The Power BI report has a page called "X" and the visual I want to export is called "Y". The problem is that I don't know the INTERNAL page name and INTERNAL visual name required by the Power Automate export action. My Power BI Service URL follows this format: https://app.powerbi.com/groups/<workspace-id>/reports/<report-id>/<some-id>?experience=power-bi Unlike some examples I have seen, the URL does not contain something like: ReportSection123abc I understand that the Power BI API uses an internal page name that is different from the visible page name. My questions are: 1. How can I retrieve the internal page name for page "X" in the current Power BI Service experience? 2. How can I retrieve the internal visualName for visual "Y"? 3. Is there a recommended way to get these values without manually inspecting browser/developer tools? 4. Can I use the Power BI REST API / Get Pages API to retrieve the internal page name and then use that value in Power Automate? 5. Is there a Power BI/Power Automate connector or API that can retrieve the visual names using getVisuals or another method? Any guidance would be greatly appreciated. Thanks!Solved244Views0likes6CommentsUnderstanding Power BI B2B Licensing and Embedded Scenarios
Understanding Power BI B2B Licensing and Embedded Scenarios I'm trying to understand how Power BI licensing, Microsoft Entra B2B, and Power BI Embedded work together. I'd appreciate clarification on the following scenarios. Scenario Tenant A owns the Microsoft Entra tenant, Power BI tenant, workspace, semantic model, reports, dashboards, and apps. [email protected] is an external user. Question 1 – B2B Guest + Pro Workspace Assume [email protected] is invited as a B2B guest into Tenant A. The workspace is a Power BI Pro workspace (not Premium Capacity or Fabric Capacity). What are the exact checks Power BI performs before allowing access? Are the checks performed in this order? User authentication B2B guest validation Tenant settings Power BI license validation Workspace/App permissions Semantic model permissions RLS Is this the complete authorization flow, or are there additional checks? Question 2 – Cross-Tenant Licensing If the external user has a Power BI Pro license assigned in their home tenant (Tenant B): Can that license be used to access reports hosted in Tenant A? If yes, how does Microsoft validate the license across tenants? Does the guest require a Pro license assigned in Tenant A, or is the home tenant license sufficient? Question 3 – User Owns Data vs App Owns Data I'm trying to understand the architectural difference. User Owns Data Who authenticates to Power BI? Does Power BI evaluate the end user's identity? Is a Pro/PPU license required? What happens if the user has no Power BI license? App Owns Data Who authenticates to Power BI? Does Power BI evaluate the end user's identity or only the application/service principal? Why is Embedded Capacity required? Why doesn't the end user need a Pro license? Question 4 – Embedded with Existing B2B Users Suppose the external user is already a B2B guest in Tenant A. Instead of accessing reports through Power BI Service, they access them through a secure web application using Power BI Embedded. Is this a supported architecture? Should this use User Owns Data or App Owns Data? Which approach is recommended and why? Question 5 – Recommended Architecture For each of the following scenarios, what is the recommended architecture and licensing model? Internal employees External partners (B2B guests) Customers using a secure web portal Public-facing dashboards When should I choose: Power BI Service B2B Guest Access Power BI Embedded (User Owns Data) Power BI Embedded (App Owns Data) Publish to Web I'm looking for the recommended architecture along with the licensing requirements for each scenario. amitchandak Ashish_Mathur superSolved360Views2likes9CommentsValidation of my understanding of Fabric Semantic Models, Power BI Desktop, and Workspace Scenarios.
Validation of Microsoft Fabric Semantic Model Architecture, Connection Modes, and Power BI Desktop Behavior Hi everyone, I've been exploring different Microsoft Fabric and Power BI integration scenarios and would like to validate my understanding. I'd also appreciate clarification on a few concepts related to Semantic Models, connection modes, and Power BI Desktop. 1. End-to-End Fabric Architecture Data Sources ↓ Fabric Lakehouse / Warehouse ↓ Centralized Semantic Model ↓ Power BI Reports / Paginated Reports My understanding is: Data is ingested into Fabric Lakehouse or Warehouse. A centralized Semantic Model is created on top of the data. Multiple reports can consume the same Semantic Model. This is the recommended enterprise architecture for governance, scalability, and reusable business logic. Is this correct? 2. Fabric Semantic Model → Power BI Desktop Fabric Semantic Model ↓ Power BI Desktop ↓ Report My understanding is: Power BI Desktop connects to the published Semantic Model using a Live Connection. Reports can be developed in Power BI Desktop. The Semantic Model itself cannot be modified because it is centrally managed in Fabric. However, whenever I connect to a Fabric Semantic Model from Power BI Desktop, Desktop opens in Semantic Model editing mode, and I don't see the Report View. My questions are: Is this expected behavior? Why is Report View not available? Is there a way to create reports directly from the same Power BI Desktop session after connecting to a Fabric Semantic Model, or is this by design? What is the recommended workflow for report developers in this scenario? 3. Power BI Pro Workspace and Fabric My understanding is: A standard Power BI Pro workspace cannot host Fabric artifacts such as Lakehouses, Warehouses, Notebooks, or Pipelines because they require Fabric capacity. However, a Pro workspace can consume an existing Semantic Model published from a Fabric workspace (subject to permissions and licensing). Reports can then be created using that Semantic Model. Is this correct? 4. Connecting Power BI Desktop to a Fabric Warehouse I believe there are two approaches. Approach 1 – Semantic Model Development Fabric Warehouse Tables ↓ Semantic Model ↓ Power BI Desktop Used for Semantic Model development. Opens in Semantic Model editing mode. Report View is not available. Approach 2 – Direct Connection Fabric Warehouse Tables / SQL Objects (Tables, Views, etc.) ↓ Power BI Desktop ↓ Semantic Model ↓ Report Connect directly to the Fabric Warehouse. Use Warehouse tables or SQL objects such as views. Power BI Desktop provides the normal report authoring experience. Semantic Model and reports are developed together. Is this understanding correct? 5. Connection Modes within a Fabric Semantic Model I'm also trying to understand how the following storage/connection modes work in Fabric Semantic Models. Import DirectQuery Direct Lake My questions are: Can all three connection modes be used when creating a Semantic Model in Fabric? What are the recommended scenarios for each mode? Are there any limitations depending on whether the Semantic Model is built from a Lakehouse or a Warehouse? Can these modes be mixed within a single Semantic Model? 6. Refresh Behavior and Data Pipeline I'd also like to understand how Semantic Model refresh works in a complete Microsoft Fabric solution. Assuming data is loaded into a Lakehouse or Warehouse through any Fabric ingestion mechanism, such as: Dataflow Gen2 Notebooks Pipelines Mirroring Shortcuts Other supported Fabric ingestion methods My understanding is that all of these eventually populate the Lakehouse or Warehouse, which is then consumed by the Semantic Model. My questions are: Is this understanding correct? Does the Semantic Model refresh behavior remain the same regardless of whether the data was loaded using Dataflow Gen2, Notebooks, Pipelines, or any other Fabric ingestion process? How does Semantic Model refresh work for each storage mode: Import DirectQuery Direct Lake Is a scheduled Semantic Model refresh always required, or does it depend on the storage mode? For Direct Lake, when new data is written into the Lakehouse or Warehouse, does the Semantic Model automatically reflect those changes, or is some form of model refresh still required? Are there any best practices for orchestrating data refresh and Semantic Model refresh within Microsoft Fabric? 7. Cross-Workspace Scenarios Is my understanding correct? Fabric Workspace Semantic Model → Fabric Report → Supported Fabric Workspace Semantic Model → Power BI Desktop Report (Live Connection) → Supported Power BI Workspace Semantic Model → Fabric Report → Supported Power BI Workspace Semantic Model → Power BI Report → Supported 8. Semantic Model Terminology One area I'm still trying to clarify. Is there technically any difference between a Fabric Semantic Model and a Power BI Semantic Model, or are they actually the same Semantic Model artifact, with the only difference being where they are created or hosted? I'd appreciate any corrections or clarifications. My goal is to build a solid conceptual understanding of Microsoft Fabric architecture, Semantic Models, and the recommended enterprise development workflow. Thank you!Solved199Views0likes4Comments