We have been observing that Power BI semantic models are automatically triggering a refresh immediately after being republished to the Power BI Service. In the refresh history, this is tagged as "On-demand", even though no manual action was performed. Upon reaching out to Microsoft, we received the following confirmation: “This is the expected behavior from the Power BI Service once a semantic model is republished. The behavior is by design and applies to all semantic models in Import mode (or those using auto-aggregations). This behavior has been consistent for several years, and there are currently no plans to change it in the product roadmap.”   While this behavior can be beneficial in certain scenarios—particularly for smaller models that complete refreshes within seconds—it introduces challenges in the following cases: Incremental Refresh Models:  In some situations, the refresh may process more data than expected, leading to longer execution times. Large or Complex Models: Models with sizes exceeding 5–10 GB or with high complexity may require several minutes to refresh, increasing resource consumption.   This behavior can significantly impact capacity resources, especially in Fabric capacity-enabled workspaces, where such unintended refresh activity may lead to unnecessary resource utilization and potential performance issues.   It would be highly beneficial if this behavior could be controlled at the user level or at least at the tenant level, allowing organizations to prevent unintended refreshes and better manage capacity consumption. ... View more

Dataverse Virtual Tables currently do not support File, Attachment, or Image data types. When binary content (for example images, videos, ZIP files, or documents) is exposed from external sources such as Microsoft Fabric Lakehouse, Azure Blob Storage, or SQL, Dataverse treats the data as text and applies strict character-size limits. This results in truncated Base64 content and prevents proper rendering or access to the original files.   Solution: Allow virtual tables to reference externally stored binary data via streaming Enable secure rendering or download via Dataverse  This enhancement would allow customers to: Keep binary data in Fabric or Blob Storage Render images and access files directly in Dataverse apps Avoid duplication, reduce storage costs, and simplify architecture ... View more

Description Hi community, I’d like to raise a feature request related to governance and connection management in Microsoft Fabric, specifically for Email (Office 365 Outlook) and Microsoft Teams connectors used in Data Factory pipelines. Scenario In enterprise environments, it is common to require: Centralized management of connections (e.g., Email / Teams) Reuse of the same connection across multiple workspaces (Dev/Test/Prod, or multiple domains) Consistent governance, including credential lifecycle management and auditing However, when working with Fabric pipelines that use Outlook or Teams activities, we observed the following behavior: When deploying a pipeline to another workspace, the activity becomes inactive A new user authentication connection must be created in the target workspace If the connection is not recreated, deployment fails or the activity cannot run This behavior is documented here: Outlook activity → Microsoft Learn Teams activity → Microsoft Learn Current Behavior (Documented Limitation) As per official documentation: Outlook / Teams connections are tied to user authentication When moving pipelines across workspaces: “The activity will be inactive in the target workspace until you create a new user authentication connection there” [learn.microsoft.com] Same behavior applies to Teams activity [learn.microsoft.com] This effectively means: Connections are scoped to the workspace Connections are not reusable across workspaces Each workspace requires manual reconfiguration Expected Behavior From an enterprise governance perspective, we would expect: Ability to define centralized, reusable connections Secure sharing of those connections across multiple workspaces Support for CI/CD scenarios without manual re-authentication Reduced duplication of connections and credentials Why this matters Other connection types in Fabric (e.g., cloud connections) are moving toward shared and governed models, but Email and Teams connectors still require per-workspace authentication. This creates an inconsistency in the platform’s governance model, especially for enterprise adoption. Feature Request We would like to request support for: Secure, reusable Email and Teams connections Cross-workspace connection sharing Centralized management (similar to cloud connections / gateways) CI/CD-friendly connection lifecycle ... View more

We would like to have a Date selection slicer which allows the report viewer to decide which type of slicer to use: relative/between/etc. Nowadays I have both users who like 'relative' slicer and users who like 'between' slicer. Because of that I have to waste space on my reports by including both types of slicers, only because there is no option for end user to manually change it: Instead I would like the end user to decide, some sugestions how it could look like:         ... View more

Description: Currently, export format settings for paginated reports can only be controlled at the tenant level or security group level via admin portal settings. There is no way to restrict export formats (e.g., allow only PDF) on a per-report or per-workspace basis.   Business Scenario: For compliance and audit purposes, some reports must be exported only in specific formats (e.g., PDF only). With the current design, disabling Excel export applies to all paginated reports in the tenant, which is too broad and impacts other use cases.   Requested Feature: Please add the ability to configure allowed export formats at the report level or at minimum at the workspace level, so that specific reports can be locked to PDF-only export for audit/compliance purposes. ... View more

Since today, the subject of email sent based on subscriptions has changed and includes a static prefix "Power BI report subscription delivery", even if I set a particular subject for that email. I would like to have the option to disable that prefix. ... View more

  Description / Problem Our organization has fully enforced phishing‑resistant authentication methods for all employees and administrative accounts, in line with Microsoft security best practices. These include passkeys and FIDO2 hardware security keys (for example, YubiKey). However, we currently need to maintain Power BI on‑premises data gateway (February 2026 version) as an exception to these policies. The reason is that the embedded web authentication engine used by the gateway does not support FIDO2 authentication. Because of this limitation, we are unable to enforce phishing‑resistant authentication methods for gateway sign‑in and administration. Current Behavior The Power BI on‑premises data gateway currently supports: Password‑based authentication, or Passwordless authentication using number matching While number matching improves security, it does not meet the definition of phishing‑resistant authentication required by many enterprise security and compliance standards. Impact Forces organizations to maintain authentication exceptions Creates a security gap in otherwise fully phishing‑resistant environments Prevents full alignment with Zero Trust and passwordless‑first strategies Affects enterprises with strict regulatory, compliance, or security mandates Requested Enhancement Please add FIDO2 authentication support (passkeys and hardware security keys) to the Power BI on‑premises data gateway in a future update. This would allow organizations to: Fully enforce phishing‑resistant authentication across all Fabric and Power BI components Eliminate password‑based authentication for gateway administration Align the gateway with Microsoft’s broader identity and security roadmap ... View more

Currently, sending email subscriptions to external recipients is supported only when the workspace is backed by a paid Premium capacity, and not in trial or non‑Premium environments [Email subs...soft Learn | Learn.Microsoft.com] This limits customers from validating external reporting and collaboration scenarios during trials.   Allow external email subscriptions in: Trial environments Non‑Premium (Pro/PPU) workspaces (with controlled limits) Impact Enables proper feature evaluation during trial Improves adoption for external collaboration scenarios ... View more

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... View more

Please could we have Prefix/Suffix option on all visual titles with Conditional Formatting. Example: Visual Title "Variance to Budget - " and Suffix (measure) "MTD" (MTD, QTD, YTD). This way we'd only need to have one resuable measure for time period and not one for every title. ... View more

Make T‑SQL notebook execution fully compatible with Service Principals by removing or replacing internal OBO calls that reject SPNs.   When pipelines or automated runs execute Fabric notebooks using a Service Principal (SPN), T‑SQL notebook cells can fail because internal Fabric calls use an on‑behalf‑of (OBO) authentication flow that does not accept SPNs. This breaks CI/CD, scheduled jobs, and automation that must run under non‑user identities.   Request: Ensure T‑SQL notebook execution does not rely on OBO flows that reject Service Principals. Make notebook runtime APIs and internal calls accept Service Principals consistently. Publish clear documentation listing required permissions and recommended configuration for Service Principals when running notebooks. See error here: (Moving to Stored procedures is step backwards we want move forward with -t-sql notebooks for enterprise scale usage ) https://community.fabric.microsoft.com/t5/Data-Engineering/Fabric-Pipeline-T-SQL-Notebook-and-Service-principal/m-p/5139358#M15589 ... View more

Hi all,    For a lot of my customers I am looking for a better way to replicate data from Dynamics 365 F&O to OneLake. I know about Link To Fabric, and to be blunt, it's not a viable option for most companies. It relies on Dataverse tables and those are way too expensive (think tens of thousands USD/EUR per month, just for replication).   The alternative solution via Synapse Link, which was described in great detail by @Reitse on his blog, technically works, and is much more cost effective, however, it is a pain to set it up.    My request would be, please make something that allows Dynamics data admins to directly push data into Fabric, without Dataverse in between, like we can already with Dynamics 365 CE.    This will:  Lower cost for customers Increase adoption by removing barriers Increase Microsoft's credibility. Because honestly, I cannot explain to my customers why Microsoft invests a lot into third-party integrations to OneLake, but Dynamics F&O is still not truly solved (while CE is!). ... View more

In need to programmatically retrieve the status of all gateways in a cluster, not just the primary. Specifically, require status per gateway, detection of states like 'Partially offline', and alerting when any gateway becomes unavailable. Currently, APIs seem to return only the primary gateway status, with no visibility into secondary nodes and also alerting options, such as triggering alerts if a threshold of refresh failures is exceeded, for example, 20% failures within the last hour to ensure high availability and monitoring. ... View more

Please allow more than the max of 20 bookmarks. ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

When visiting the monitor page, not all refresh events appear. Monitor page does not show all semantic model refresh failures. The failed refresh events shows in refresh history of semantic models. Even the details are available in onelake catalog when searched for the semantic model -> monitor -> we could see the failures events but in monitor hub the details are not available. The Engineering team confirmed it by design but however the monitor hub should provide all the details so that it provides a centralized view of job execution health, progress, and outcomes to quickly identify problems and take action. ... View more

Today, Workspace Monitoring is configured separately per workspace, which introduces maintenance overhead and likely also a repeated baseline CU cost for each workspace.   Please make it possible to create Workspace Monitoring instances that cover multiple workspaces.   Users should be able to decide how many monitoring instances to configure and which workspaces each instance covers.   This would allow the baseline monitoring cost to be shared rather than incurred separately per workspace, reducing overall cost while also simplifying configuration and ongoing maintenance. In addition, it would enable a more centralized and flexible monitoring setup across workspaces. ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Snowflake as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Snowflake break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Snowflake Semantic Views   This idea is copy/pasted from @dhaneswara's submission for integration with Databricks Metric Views as I was surprised to not see the Snowflake equivalent represented.  ... View more

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