Paginated Reports with PowerQuery - Cloud connections for Snowflake connector
Current situation: Power BI report builder used to build a report using Power Query dataset. Report builder picked the right cloud snowflake DB connection (created in Power BI service portal - app.powerbi.com) However, once we deployed / published the report into power bi service portal (workspace), we are not able to see the connection it uses in the background. We only see the disabled connection settings. Refer the screenshot. It would be great if we display the cloud connection information just like how we display for semantic models. Otherwise, we have to download the rdl file from the portal and check the connection ID from the report file and fetch the connection detail from the "Manage Connections and Gateways" page from the portal settings.
Allow multi-column conditions /output in Power BI Activator rules (Power BI visual-based alerts)
Description: When I create an Activator alert from a Power BI report visual, the rule can only evaluate the single column or measure it was created from, and the alert can only reference that same value. This blocks common governance and monitoring scenarios. Example scenario: I wanted an alert for Dev workspaces that sit on a billable (Premium/Fabric) capacity. That needs a condition on both Workspace Name (contains “Dev”) and Capacity/Billing type (not blank). Activator can’t combine the two in one rule, so I had to build the alert in Power Automate with a DAX query instead. Limitations: A condition can use only one column or measure, with no AND/OR across several attributes. The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner. There’s no way to run a DAX query as the rule logic. Requested improvements: Conditions across multiple columns/measures (AND/OR). Selectable output fields, so the Teams or email action can include several columns, and dynamic links. Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does. Impact: Without this, governance and monitoring alerts need a separate Power Automate flow, which is harder to build and maintain than a native Activator rule.Fabric Workspace Operator Role for Pipeline Monitoring and Rerun Operations
Many organizations have dedicated production support and operations teams responsible for monitoring Microsoft Fabric pipelines and responding to failures. Currently, the available workspace roles are Admin, Member, Contributor, and Viewer. While Viewers can monitor content, they cannot rerun failed pipelines. Contributors can rerun pipelines, but they also have permissions to modify pipeline definitions and other workspace artifacts. This creates a governance gap for enterprises that require segregation of duties between development and operations teams. Proposed Solution Introduce a new built-in Operator workspace role with permissions such as: Allowed View pipeline definitions Monitor pipeline runs and run history View execution logs and error details Manually trigger pipeline execution Rerun failed pipeline runs Cancel running pipeline executions Access workspace monitoring capabilities Not Allowed Create, edit, or delete pipelines Create, edit, or delete Fabric artifacts Modify notebooks, lakehouses, warehouses, or dataflows Manage workspace access or permissions Change workspace settings Connect/disconnect Git repositories Business Value This role would: Support enterprise segregation of duties requirements. Enable production support teams to resolve operational issues without granting development permissions. Reduce the risk of accidental changes in production workspaces. Improve governance and compliance. Align Microsoft Fabric with operational models commonly used in enterprise data platforms. Many organizations need a role that sits between Viewer and Contributor, providing operational control without development privileges. An Operator role would significantly improve security, governance, and supportability for Fabric Data Factory workloads. Use Case: Production support team monitors Fabric pipelines, investigates failures, and reruns failed executions, but should not be able to modify pipeline definitions or other workspace assets.
More Granular Workspace Permissions (RBAC)
Allow Workspace Admins to assign more granular permissions and create custom roles based on atomic permissions, following the principle of least privilege. Examples of possible atomic permissions: Read workspace settings Manage workspace settings Read workspace role assignments Manage workspace role assignments Read OneLake security access role assignments Read workspace activity logs Read data Write data Share read data permissions Share write data permissions Create and edit workspace items Delete workspace items Share create and edit workspace items Share delete workspace items etc. This would enable Workspace Admins to automate auditing and governance, delegate specific responsibilities, and follow least-privilege principles without granting unnecessarily broad workspace roles.Disable App Sharing Notification to Audience
Can we have the option to turn off the notification when we add people to an audience in Power BI Apps? Sometimes, I want to share an app with a wider group of people, but I don't want to notify all of them. I just want to make sure they can access the app when they need to. We've been trying to get viewers in our organization out of workspaces, but we've been having to give viewer access to workspaces as a workaround when we are sharing with a large group.Overview of all Item permissions in a Workspace
We need a single page overview where we can see a complete list of which users and security groups have item permissions on any Item in the workspace. Today, we need to click on every single Item to see who has access to that item. We need a complete overview to easily spot if someone has a permission that they should not have.
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI deployments, this creates navigation and discoverability challenges. **Current Behavior:** Org Apps appear mixed with regular apps in a single list, making it difficult for end-users to distinguish and locate organizational-level content, especially in environments with dozens of apps. **Requested Behavior:** Add the ability to display Organizational Apps in a separate, dedicated section within the Get Apps experience (similar to how Featured and Recommended apps are organized separately). This would: - Improve discoverability for org-level content - Create clear visual separation between user-scoped and organization-scoped apps - Enhance the app navigation experience at scale **Business Impact:** Organizations deploying large numbers of apps (particularly during migrations and multi-tenant rollouts with 100+ apps) would benefit significantly from dedicated Org Apps visibility. This is especially valuable for external-facing platforms serving multiple client organizations, where organizational apps serve as the primary content distribution mechanism. **Suggested Implementation:** Add a new collapsible "Organizational Apps" section in the Get Apps experience that displays all Org Apps separately from regular workspace-published apps. Admins should have the option to control this visibility via tenant or workspace settings. **Workaround:** Currently unavailable.📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regions, products, customers, time periods, and key business metrics, raw data can reveal the root cause behind the numbers. Good data analysis turns numbers into decisions. 📊 #DataAnalysis #BusinessIntelligence #PowerBI #MicrosoftFabric #DataAnalytics
EntraID for ORG Apps?!
Hi. I am maintaining about 45+ different Dashboards with different audiences and currently planning to switch from Workspace Apps to Org Apps as it seems like this will be the "more" actively developed feature in the future? This is "necessary" as i currently have to use two Prod Workspaces in order to deliver dashboards via Apps (as i need at least more than 25 Audience Groups) - a real pain and probably i will go to engineer's hell for this. Hence i was quite happy when Org Apps were made available and i could get rid of this debt. However, setting up the migration and plan for doing this, I realized that currently its not possible to add EntraID Groups to Org App Audiences?! As entraid groups play an essential part in our governance workflows, i quite rely on them. So is there any technical reason for not allowing EntraID groups in Audiences of Org Apps as it is possible for Workspace Apps?? So: Please allow to add ADD EntraID Groups to Org App Audiences! Best, Max
