Current behavior Today, Microsoft Fabric controls item creation through a single tenant or capacity‑level setting: “Users can create Fabric items.” This setting works on an all‑or‑nothing basis: When enabled, users can create all Fabric item types in a workspace. When disabled, users cannot create any Fabric items. There is currently no supported way to selectively allow or block specific Fabric item types (for example, allowing users to create only reports but not Lakehouses, Warehouses, Pipelines, etc.). Problem / customer impact Many organizations have strong governance and separation‑of‑duties requirements. Common scenarios include: Allowing report developers to create only Power BI reports Allowing data engineers to create data engineering objects only Preventing accidental creation of high‑impact objects (e.g., Warehouses, Lakehouses, Pipelines) Because item creation is all‑or‑nothing, admins are forced to: Over‑restrict users (Viewer role), or Over‑expose capabilities that users should not have This creates friction, governance risk, and additional administrative overhead through workarounds such as multiple workspaces per persona. Requested enhancement Provide granular creation controls that allow admins to: Enable or disable specific Fabric item types per tenant, capacity, or security group Align Fabric permissions more closely with real‑world organizational roles Improve governance without limiting adoption or usability Benefits Stronger security and governance Better role separation without workspace sprawl Reduced risk of unintentional resource creation Improved admin and customer experience ... View more

Currently, the “Apply to entire organization” option is not enabled in Copilot Capacity Settings. As a result, to restrict Copilot CU usage to a specific capacity, administrators are required to create and maintain a group that includes all users in the organization. From an admin and UX perspective, this introduces unnecessary overhead and ongoing maintenance. Enabling the “Apply to entire organization” option would significantly simplify configuration, reduce operational effort, and improve the overall administrator experience. I’ve already discussed this topic with the PM responsible for Power BI Copilot, and I understand the design considerations behind the current approach. That said, I would like to encourage the team to reconsider the factors leading to this restriction, as the current setup adds complexity without clear value for administrators. Allowing Copilot to be applied to the entire organization at the capacity level would be: Easier to configure Easier to govern Less error‑prone More intuitive for Fabric administrators I hope other Fabric admins find this improvement valuable and can vote to support this idea. Thank you for considering this feedback. ... View more

Currently, Microsoft Fabric (and Power BI) does not provide a tenant setting to restrict workspace app creation to specific security groups.   The available controls are:   Workspace roles: Member role includes the ability to publish apps and manage permissions. Contributor role removes app publishing rights but also removes the ability to manage permissions on reports/models. Tenant settings: You can restrict workspace creation to specific security groups. You can control whether users can publish apps to the entire organization, but not who can create apps in general. There is no built-in setting today to allow Members to manage permissions but block app creation.   The only way to achieve this currently is: Use Contributor role for self-service workspaces (blocks app creation). Grant item-level permissions on reports/models to allow sharing without giving full Member rights.   Could I please ask for a tenant setting that would allow me to control who can create workspace apps, regardless of their workspace roles?   Thank you. ... View more

If you like me started with working with notebooks in Fabric and have company policy that dictate using private links you will have discovered Microsoft “starter pools” are no longer an option. The startup time goes from below 10 seconds to  3-5 minutes. Microsoft have luckily decided to do something about this and have now introduced custom live pool in public preview. This is a great first step for customers – however it has one very limiting factor – it only work with workspace pools. These sessions will “only” be available on one given workspace and not across multiple workspaces. My proposal is to introduce custom live pools on capacity level. I want to be able to define environments on capacity level and share custom live pools on any workspace connected to this capacity. This will have the following benefits: Much easier for the admin to administrate custom live pools Cost effective – we would max want to pay for X custom live pools and spread them between all of the workspace for a given capacity – we cannot/“will not” set this up pr. workspace and have idle custom clusters across many workspaces. Link to current configuration on custom live pools on learn: Configure custom live pools in Microsoft Fabric - Microsoft Fabric | Microsoft Learn ... View more

Idea Provide an option in Microsoft Fabric Oracle database mirroring to skip or exclude specific columns during replication, especially Oracle system-generated hidden columns (SYS_NC*). Problem Oracle mirroring fails during the initial load when tables contain hidden SYS_NC columns, raising ORA-00904. Currently, users must modify source Oracle databases (for example, drop extended statistics), which is not always acceptable in production environments. Benefit Enables mirroring without source-side schema or statistics changes Improves compatibility with enterprise Oracle databases Reduces onboarding blockers and support escalations Suggested Solution Allow column-level exclusion (or automatic exclusion of hidden columns) during initial load and ongoing replication. ... View more

Scheduling Hub   It would be great to to be able to see which items in your fabric workspace (and capacity) have schedules and if they are on or off. A bonus feature would allow you to enable and disable the schedules right from the list view (editing could still open the item in the editor and open the scheduling pane).   Being able to manage schedules from a central location is helpful in 'emergency' scenarios where you need to turn off all the pipelines and notebooks for a workspace. It could also be useful to ensure developers are not mismanaging schedules in Dev or Feature Branch workspaces (where we might typically not want them running). A whole set of useful columns are possible: Item Name  <click on the name to go to the item!> Item Type Workspace Schedule Type Next Scheduled Run Last Scheduled Run   Icons.. Edit Pencil, Enable/Disable, Trash Can The possibilities are endless!   ... View more

Scenario summary The customer initially encountered a refresh failure with the following error: To resolve this, the customer modified the Power Query (M) code to make it more robust, primarily by improving error handling and attempting to remove or handle blank values. Original M code was working but failed on refresh due to the error above. Updated M code successfully handled the error and allowed the refresh to complete. Observed behavior After applying the updated M code, the existing relationship between the RLS (Row-Level Security) table and the MOA table was automatically removed without any warning or notification. As a result, the semantic model was left in a vulnerable state until the customer manually identified and fixed the broken relationship. During this period, RLS behavior was impacted.   Customer understanding The customer understands why this happened from a technical perspective: The M code changes affected the underlying data shape (rows / key values). This caused the relationship to be invalidated. However, the customer expressed concern that no warning was shown before or after applying the change, especially given the impact on RLS and model security.   Feedback / Feature consideration The customer would have expected some form of safeguard, such as: A warning when applying query changes that affect columns or keys used in relationships (especially RLS-related relationships), or A notification indicating that model relationships were removed or invalidated as a result of the change, or A rollback or review mechanism when model-impacting changes are detected. A warning or validation step when working with semantic models—particularly when changes affect relationships or RLS dependencies—could help prevent similar issues and reduce the risk of production-impacting scenarios. ... View more

Power BI currently does not provide any native method for administrators to track where organisational visuals are being used across the tenant. The following limitations create significant governance and compliance challenges: Activity Logs / Audit Logs record high‑level actions (e.g., ViewReport, ExportData) but do not log which organisational visuals appear in a report.  The only current method to identify uncertified visuals is to manually or programmatically inspect report definitions / PBIX files, which is impractical for large organizations.  When an uncertified visual is added to Organizational Visuals, it becomes available to the entire tenant, with no ability to restrict usage at a granular (e.g., to security groups) level, complicating governance. This gap makes it difficult for administrators to ensure compliance, manage third‑party risks, and perform internal audits. Enhancement:  Ability to track organisational visuals in Activity Logs / Audit Logs. Ability to restrict the usage of organisational visuals through security groups. ... View more

At present, anyone who wants to build a custom capacity monitoring dashboard relies on querying the Fabric Capacity Metrics report semantic model. Instead, it would be beneficial to have an admin monitoring eventhouse, similar to the workspace monitoring eventhouse, where raw capacity metrics data is made available for admins to build solutions on top of.   The same eventhouse could also host raw data for Fabric activity logs and workspace artifact catalog data (Scanner API extracts). This would make it much easier for admins to access these logs, rather than building complex solutions just to extract the data. ... View more

Use case: We have one particular capacity where we want to allow only ad hoc refreshes, but not schedules. We can audit that with semantic models but not with dataflows.  Request to expose the dataflow refresh type in the Capacity Metric App. ... View more

I am consultant for many customers and we use our b2b Users for Support and we receive mails to our own E-Mails.    Semantic Model refresh failue mails do not contain the ?ctid= and this causes that if i click the mail it ends in nowhere. Even if i copy the link in a webbroser which is in context of my customer it brings me back to my own tenant where this Data Model doesn't exitst.    This is very anoying and make our professional work harder and response time longer.    In general i would prefer that all Links always contain ?ctid=   Additional all Mails should contain information about the Tenant.    Current Subject: Refresh failed: [Model] has failed to refresh Prefered Subject: Refresh failed: <Model> has failed to refresh at <Tenant Name>   Current Link https://app.powerbi.com/groups/<Workspace>/settings/datasets/<Dataset> Prefered Link https://app.powerbi.com/groups/<Workspace>/settings/datasets/<Dataset>?tid=<ClientId> ( please test that it is working with B2B )   Technical Information     Activity Id: <Activity Id>   Request Id: <Request Id>   Please add Tenent Name and Tenant URL  and Workspace Name (Workspace Name often contains something like Dev Test which helps to prioritize or whom to talk)   Please add all notification recipents (if someone fixes, then you might want to inform them that you start inventigations or that the Issue has been fixed).    Cluster Name: WABI-NORTH-EUROPE-O-PRIMARY-redirect.analysis.windows.net   Refresh Start Time: February 28, 2026 13:03 UTC   Refresh End Time: February 28, 2026 15:18 UTC     Would be great if this would be changed! ... View more

Buenas tardes a todos, me gustaria tener un reporte de uso modificacion y creacion de algun archivo de BI ... View more

Similar to the Monitor page, where we can see what has run and what is currently running, it would be useful to see what's scheduled to run in the future. This to check that all schedules are set up as expected.   Reason: Easy and conveniently verify that all schedules are configured as expected. ... View more

To make it easy to filter workspaces, and also enable cost chargeback scenarios, it should be possible to apply Tags to workspaces. ... View more

We have quite a few data factory jobs that run today and we want to move them to fabric but we have some large data factory reservations that lock us in for a period time and it would be great if we could exchange those for Fabric reservations.  ... View more

In one of the projects I'm involved in, we found out that deleting an item is irreversible. When you hit delete, the item is gone and all the data in it as well. There is a retention period for workspace deletion but, unless I've missed something, not for items. In the discussion with the client, we found that a very elegant solution would be to create a separate role that allows for deletion of items. Or, as an alternative, introduce the delete locks as seen within Azure.  In both cases, deleting items will become harder and that is the exact point. I think the option to enable delete protection is something for the admin portal. It should only apply to non-personal workspaces and, from the admin portal, workspaces can be exempted from delete protection. This way, dev workspaces can be a 'free for all' whereas QA and Production are heavily protected against accidental deletes. If you want to go really granular, there could be an option to select Lakehouses to be protected, but notebooks can be deleted. ... View more

Hello Team  Please find the below sugguation where there is no option to monitor the Gateway Usage  Current Gap Fabric admins cannot easily see how many datasets are using a specific On‑premises Data Gateway connection or which datasets/workspaces depend on it. This information is not available in the UI and requires manual correlation using audit logs or APIs. Proposed Enhancement Add a Gateway Usage view in Fabric that shows: Number of datasets using each gateway connection List of dependent datasets and workspaces Last usage / refresh activity Value This improves monitoring, impact analysis, and capacity planning, especially during gateway maintenance, troubleshooting, or scaling decisions. ... View more

When a user opens a report and selects the File dropdown, they see the “Embed report” option with the following choices: SharePoint Website/Portal Developer Playground So the Customer wants to Disable “Embed report” for View-only users in power bi ... View more

Currently, Microsoft Fabric provides the ability to manage access to Copilot and Azure OpenAI-powered features at the Tenant and Capacity levels using the following setting: “Users can use Copilot and other features powered by Azure OpenAI” As a Fabric Administrator, I’m requesting an enhancement to allow Copilot access control at the Domain level. This additional layer of granularity would empower organizations to roll out Copilot features in a more secure, targeted, and manageable way—especially in environments with multiple business units or domains that have varying readiness levels or compliance requirements. Implementing domain-level controls would help accelerate adoption while maintaining governance and minimizing risk. ... View more