Power BI Subscriptions enhancements sorely needed
I believe there are several updates needed to Power BI subscriptions: Gate subscription ability. Right now, this is all-on/all-off feature. I would like this feature to be gated for users/security groups like almost every other setting in MS Fabric (e.g. allow only certain users/groups to create subscriptions). Zero visibility. Need to see subscriptions on monitor tab Need to know impact on CUs from these subscriptions Need to know everyone reports were sent to (E.g. if we have one subscription is sent to 5 people, we would need 5 records) Need to know when upcoming subscriptions are going to be run Purview labels are not respected in subscriptions. If someone sets up a label for the data in a report, the subscription does not ensure that the user(s) on the subscription are allowed to actually see that data; and since we have not gating by security group (see first bullet), they cannot be controlled that way either No dynamic data for "standard" subscriptions. It would be great to have the ability to have dynamic data input into the email subject or body. Right now the only option is static text. No CC or BCC settings. It would be great to have CC and BCC options. All emails get sent from PowerBI service. It would be great if we could use another SMTP server (set at tenant and/or workspace level) All emails get sent with the same template. It would be great if we could use a custom template (set at tenant and/or workspace level) Fabric semanitc model w/ all Fabric users/groups. There should be a native Fabric semantic model that contains all of the objects (workspaces, reports, users, groups, etc...) that could be leveraged by all who select "Dynamic subscription". I have put these in my priority order DataZoeDataZoeMS
Reintroduce Tenant/Capacity Switch to Control "Users can create Plan items" Post-GA
During the Preview phase of Fabric Plan items, administrators had access to a dedicated tenant/capacity setting: "Users can create Plan items". With General Availability (GA), this granular administration toggle was removed, enabling the capability broadly. Business & Governance Impact Plan items require an underlying SQL Database and consume additional Capacity Units (CUs). In enterprise environments, allowing all users to freely create Plan items creates significant operational and financial risks: Uncontrolled CU Consumption: Unrestricted creation leads to unexpected spikes in Capacity Unit utilization, impacting high-priority workloads across shared capacities. Database Sprawl: Automatic provisioning of underlying SQL DB dependencies without administrative oversight creates governance, compliance, and management overhead. Lack of Cost Allocation: Administrators cannot enforce least-privilege access or limit Plan item creation to authorized departments/workspaces. Proposed Solution Re-introduce the tenant-level and capacity-level governance setting under the Fabric Admin Portal: Tenant-Level Toggle: Allow Fabric Admins to enable/disable Plan item creation globally or restrict it to specific Security Groups. Capacity-Level Override: Allow Capacity Admins to turn off Plan item creation on specific capacities where CU consumption needs to be strictly budgeted or reserved for core analytics pipelines.
Can't Tell Which Reports an Audience Has Access To
I'm an admin of a Power BI environment. We need to know exactly who has access to all reports through workspace membeship, shared links and Apps. We have all the APIs that can show who has access through workspaces and shares, but there seems to be a huge flaw when it comes to App Audiences. For example: An App has two reports (R1 and R2) and two audiences (A1 and A2) A1 can see R1 but not R2 A2 can see R2 but not R1. Although we will be able to list the members of A1 and A2, we won't be able to tell which audiences they were in and therefore won't know if they have access to R1 or R2. This has potential audit repercussions as we can't know for sure who has access to R1 or to R2.
Unified Metadata Explorer Across All Microsoft Fabric Artifacts
Fabric should provide a centralized metadata repository similar to Purview but built into Fabric. Features Automatic metadata collection. Lineage across all artifacts. Search by column, table, report, notebook, measure. Impact analysis. Version history. Benefit Reduces the need for custom metadata solutions and Lakehouse-based metadata frameworks.
Fabric free trial blocks new personal tenants without warning users beforehand
Microsoft actively promotes free certification vouchers (e.g., for DP-700) and free learning paths on Microsoft Learn, but individuals studying independently — without a work/school organization backing them — currently have no reliable free way to get hands-on Fabric access: New tenants are silently ineligible. Following the official guide "Start a Microsoft Fabric free trial with a personal email" leads users to create a new Azure/Entra ID tenant, but new tenants appear to be blocked from Fabric trials (reportedly for ~90 days), based on unofficial support forum replies. This restriction isn't mentioned anywhere in the official article or in-product error message, so users only discover it after completing the entire setup. In-product error message doesn't explain the real cause. The message "A Fabric trial isn't available for your account. See the Microsoft documentation for eligibility requirements" links to generic documentation that doesn't state the actual reason or resolution path. Microsoft Learn exercises assume trial access exists. Hands-on exercises for certification paths (e.g., DP-700 modules like "Use Dataflow Gen2 in Fabric") require an active Fabric trial and don't provide a sandbox, so users who can't get a trial can't complete the practical exercises needed to prepare for a certification Microsoft is actively encouraging them to pursue via free vouchers. Ask: Provide a genuinely reliable free path (or at least clear upfront guidance) for individuals studying independently to get real hands-on Fabric access for certification prep — whether that's fixing sandbox availability for relevant Learn modules, clarifying trial eligibility rules before users start the setup flow, or improving the in-product error message to state the actual cause and next steps.Notify Subscription Owners About Invalid Email Recipients in Power BI
Power BI should automatically notify subscription owners whenever one or more recipient email addresses are invalid or undeliverable. Currently, report subscriptions may silently fail for specific recipients without providing clear feedback to the person who created and manages the subscription. A notification should identify which email addresses could not receive the subscription and explain the reason, such as an invalid address, deleted user account, or external recipient restriction. This would allow subscription owners to quickly update the recipient list instead of assuming that reports are being delivered successfully. Providing proactive notifications for failed deliveries would improve reliability, reduce support requests, and ensure that important reports reach their intended audience. It would also enhance the overall user experience by making subscription management more transparent and easier to maintain.Improve Power BI Error Messages with Root Cause Diagnostics
Power BI should provide more accurate and actionable error messages by identifying the actual root cause of a failure instead of displaying generic messages. Today, users may see an error such as, "This may be caused by a capacity or licensing issue," even when the real problem is related to the semantic model, such as invalid relationships, duplicate keys, or data model inconsistencies. These generic messages often lead users to troubleshoot the wrong area, wasting time investigating licensing, capacity, or service availability when the issue actually lies within the data model. Power BI could improve the troubleshooting experience by analyzing the failure and presenting more specific guidance. For example, if the error is caused by duplicate keys, invalid relationships, or model validation issues, the message should clearly indicate this and provide recommendations on how to resolve it. Providing root cause diagnostics would reduce troubleshooting time, improve the user experience, and help both business users and developers identify and fix issues more efficiently.
Add a built-in Fabric Reader role for read-only access to the admin portal and tenant settings
Currently, viewing Fabric tenant settings and Admin portal configuration requires the Fabric Administrator role (or Power Platform / Global Administrator). There is no read-only equivalent — the Entra Global Reader role does not reliably surface Fabric tenant settings in the portal, and Entra custom roles cannot include Fabric admin permissions. The only programmatic alternative, the read-only Admin APIs via a service principal, is all-or-nothing: adding an SP to the allowed security group grants read access to ALL current and future admin APIs tenant-wide (user details, semantic model and report metadata, activity data), with no ability to scope it to tenant settings only. This creates a real problem for regulated organisations. As a government department subject to NIS2, ISO 27001, and GDPR, we have legitimate needs for read-only visibility of tenant configuration — security reviews, audit evidence, compliance reporting, configuration drift monitoring — but the only way to meet them today is to grant full administrative privileges or over-broad API access. Both conflict with least-privilege principles and inflate our privileged-access footprint purely for viewing purposes. Request: 1. A built-in "Fabric Reader" Entra role with read-only access to the Fabric Admin portal, tenant settings, and admin views — mirroring how Global Reader complements Global Administrator. 2. Alternatively (or additionally), scoped permissions for the Admin APIs so a service principal can be granted access to specific API areas (e.g. tenant settings only) rather than the entire read-only admin API surface. This would materially improve least-privilege governance for enterprise and public-sector customers and reduce the number of standing Fabric Administrator assignments across tenants. Thanks Sateesh
