Currently for customers who purchased Azure from CSP provideres need to reach out to the provider to get the emission information.    https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-to-emissions-impact-dashboard But the options for the CSP provider to share the data are below: Providing customer‑specific exports or reporting packs from EID visuals and reports ·   Using exported EID data to create offline or downstream customer‑specific reports   We would request either one of the below solution to be implemneted so that the CSP providers can share the emissions to the individual customers .  OPTION 1 (preferred option) As a CSP, we are in need of a filter in the Emissions Impact Dashboard (EID) by specific customers/tenants. At the moment, there is no option to apply such a customer/tenant filter. While we could add a Tenant–Subscription mapping to the semantic model to enable this, the model would need to be updated. Since the EID is delivered as a template app, it’s not possible to download (see screenshot) or modify the semantic model to include this mapping. Allowing this option would give us what we need to help our customers in most simple way.       OPTION 2  An alternative solution would be to let you add a customer/tenant filter directly to the report. Our preference, however, is to gain access = have to ability to click"Open" to both the semantic model and the report so we can customize them as needed. This would also allow us to share the report with our customers without manually applying filters and exporting it to PDF or PowerPoint for distribution.         ... 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

Hi all, I would like to submit a feature request regarding the Microsoft Fabric Eventstream REST API. Currently, it is possible to programmatically: Create an Eventstream Update its definition Configure an Eventhouse destination (including database and table mapping) However, there is a missing step that cannot be performed via API: After publishing the Eventstream topology, the final step "Configure KQL Data Connection" (available in the UI) is required to fully enable ingestion into the Eventhouse table. At the moment: This step is only available through the UI There is no documented or supported API to complete this configuration This creates a blocker for full automation and CI/CD scenarios   For teams working with Infrastructure as Code and automated deployments, the inability to configure the KQL Data Connection programmatically means: Eventstream deployments cannot be fully automated Manual intervention is required after each deployment CI/CD pipelines are incomplete Requested enhancement Provide an official and supported way to: Configure KQL Data Connection via REST API Or include this configuration within the Eventstream definition payload This could be implemented as: A new API endpoint for managing Eventhouse ingestion connections or Extending the Eventstream definition schema to include this configuration This capability would significantly improve automation scenarios and align Eventstream with other Fabric resources that already support full API-based deployment. Thanks for considering this request. ... View more

Hello team, I would like to propose an improvement regarding item management within Microsoft Fabric workspaces. Currently, it is possible to select multiple items and move them into a folder, which is very helpful for organizing content. However, this same multi-selection capability is not available for deleting items, meaning users must delete them one by one. Proposal Enable bulk deletion of items using the same multi-selection mechanism that is already available for moving items. Motivation In real-world scenarios, especially during development and iterative workflows: Users often create multiple versions of assets (e.g., notebooks, pipelines, etc.) while refining solutions. Once a final or optimized version is achieved, previous iterations need to be cleaned up. Performing this cleanup item by item is inefficient and time-consuming. While it is technically possible to automate this via code or APIs, having this functionality directly in the UI would significantly improve usability and productivity. Risk considerations I understand that bulk deletion can introduce risks. To mitigate them, an approach similar to Azure could be followed: Confirmation prompts (e.g., typing the item name or workspace name). Soft delete or recovery mechanisms, where applicable. Role-based restrictions (e.g., allowing bulk delete only for specific roles such as Admin or Contributor). Suggested approach Extend the existing multi-selection UI to support a “Delete” action. Apply appropriate safeguards (confirmation steps, role validation). Optionally, provide visibility of affected items before confirmation. Expected benefits Faster cleanup of development artifacts Improved user experience and productivity Consistency with existing multi-selection capabilities Reduced friction in iterative development workflows Closing This enhancement would align perfectly with how users already interact with items in Fabric and would remove a small but meaningful point of friction in daily usage. I would be happy to share more detailed scenarios if helpful. Thank you for your continued innovation.   ---------------   Hola, equipo, Me gustaría proponer una mejora en lo que respecta a la gestión de elementos dentro de los espacios de trabajo de Microsoft Fabric. Actualmente, es posible seleccionar varios elementos y moverlos a una carpeta, lo cual resulta muy útil para organizar el contenido. Sin embargo, esta misma función de selección múltiple no está disponible para eliminar elementos, por lo que los usuarios deben eliminarlos uno por uno. Propuesta Permitir la eliminación masiva de elementos utilizando el mismo mecanismo de selección múltiple que ya está disponible para mover elementos. Motivación En situaciones reales, especialmente durante el desarrollo y los flujos de trabajo iterativos: Los usuarios suelen crear varias versiones de los activos (por ejemplo, cuadernos, flujos de trabajo, etc.) mientras perfeccionan las soluciones. Una vez que se alcanza una versión final u optimizada, es necesario limpiar las iteraciones anteriores. Realizar esta limpieza elemento por elemento resulta ineficiente y consume mucho tiempo. Si bien técnicamente es posible automatizar esto mediante código o API, disponer de esta funcionalidad directamente en la interfaz de usuario mejoraría significativamente la usabilidad y la productividad. Consideración de riesgos Entiendo que la eliminación masiva puede conllevar riesgos. Para mitigarlos, se podría seguir un enfoque similar al de Azure: Mensajes de confirmación (por ejemplo, escribir el nombre del elemento o el nombre del espacio de trabajo). Mecanismos de eliminación lógica o de recuperación, cuando corresponda. Restricciones basadas en roles (por ejemplo, permitir la eliminación masiva solo para roles específicos como Administrador o Colaborador). Enfoque sugerido Ampliar la interfaz de usuario de selección múltiple actual para que admita una acción de "Eliminar". Aplicar las medidas de seguridad adecuadas (pasos de confirmación, validación de roles). Opcionalmente, proporcione visibilidad de los elementos afectados antes de la confirmación. Beneficios esperados Limpieza más rápida de los artefactos de desarrollo Mejora de la experiencia del usuario y de la productividad. Coherencia con las capacidades de selección múltiple existentes Menor fricción en los flujos de trabajo de desarrollo iterativo. Cierre Esta mejora encajaría perfectamente con la forma en que los usuarios ya interactúan con los elementos en Fabric y eliminaría un pequeño pero significativo punto de fricción en el uso diario. Con gusto compartiré escenarios más detallados si resulta útil. Gracias por su continua innovación. ... View more

Trying to assign Fabric capacity to over 25,000+ My Workspace in organization. Assiging manully is not feasible. Requesting an automatic feature to enable bulk assignment to users instaed of manual as it is time consuming. ... 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

Working scenario: In an existing report the matrix Bold formatting worked as expected. After selecting/unselecting bold in row headers works as expected. When opened a new page and created a new matrix visual selecting bold/unbold in row header and row sub totals work as expected. However when created a new report with the same model and exact same columns the matrix visual automatically bolds the first column. When additional column is added it appears has bold but only the last column works as expected. If row header is toggled between bold or unbold, it just bolds/unbolds the last column . If additional column is added and select row subtotals it bolds the total along with the first column. We received an update from Engineering team informing that it is by design as of now "The subtotal row headers are always rendered with the bold font family regardless of the 'Row Headers' bold toggle. The toggle doesn't control subtotal row header font which has its own forced bold styling". The working and non working has a different theme which explains why the old/new PBIX are behaving the way they are. This needs to be changed and bold formatting should work as expected in the existing report. ... View more

Currently, Excel workbooks connected to a Power BI / Microsoft Fabric semantic model (for example, via Analyze in Excel or Power BI dataset connections) do not automatically refresh when the underlying semantic model is updated. Users must manually open the Excel file and trigger a refresh for the latest data to be reflected.   Current Behavior The semantic model refreshes successfully in Power BI / Fabric. Data refresh occurs only when: The Excel file is opened in Excel Desktop, or A manual refresh is triggered. Expected / Desired Behavior Provide an option to automatically refresh Excel workbooks when the connected semantic model completes a refresh, especially for files stored in OneDrive or SharePoint while opening a report in Excel web. ... View more

Want to download reports that are created in the Power BI service or Power BI Desktop and based on a semantic model in My Workspace in live connected mode.     ... 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

Hello. Could you add an "Ends with" filter option, in the advanced options of the filter menu, just like in Excel : Hopefully this is understandable, I'm not sure of the names in english. Thank you. ... View more

In complex models with many tables, when several have fields with common names but that do not represent relationships, automatic detection creates the links incorrectly, which forces the developer to delete them all in order to do it correctly, or remember to disable this feature in new project files BEFORE connecting to the tables. In any case, it involves some kind of rework for the developer. Why, similar to Column Type detection, can we simply disable relationship detection in the global settings?   ... View more

Currently, the only available authentication method is the Organizational Account. Service Principal and Workspace Identity authentication methods are required.   Lakehouse connector overview - Microsoft Fabric | Microsoft Learn ... View more

OpenLineage lets you trace a large number of ETL jobs that mutates tables, letting you trace changes to tables significantly easier. Databricks Unity Catalog has support for Column Level Lineage and it's highly useful: View data lineage using Unity Catalog - Azure Databricks | Microsoft Learn Databricks Demo   AWS also supports OpenLineage:  Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog It's actually quite easy to get OpenLineage working in Fabric Spark since you already have the JAR pre-installed: Column level lineage in Fabric Spark with OpenLineage and stashing the lineage in Delta Lake | Raki Rahman   All we need is a way to store and query historical state (e.g. in Delta Lake), and a UI component that hooks into the Lakehouse catalog and offers an API on top of OpenLineage schema. The OneLake Catalog UI could look like this:   To prove this can be fairly easily achieved since the OpenLineage events are robust with a stable schema, I vibe-coded this little static site that works with the default Fabric Spark OpenLineage events: Marquito — OpenLineage Visualizer       ... View more

Scenario: User have embedded Power BI reports into a Dynamics 365 portal using secure embedding. When users access the portal for the first time, they are prompted to sign in to Power BI. After authentication, the embedded report loads successfully. However, if the user refreshes the browser or opens the portal in a new tab, the embedded Power BI report again prompts for sign-in, even though the user is already authenticated in the Dynamics 365 portal session. Current Behavior / Limitation: This behavior aligns with the current design of secure embedding, where Power BI authentication is handled separately and does not persist across browser refreshes or new tabs. This limitation is documented in Microsoft Learn: Embed a report in a secure portal or website - Power BI | Microsoft Learn As a result, users are required to repeatedly authenticate to Power BI, leading to a suboptimal user experience. Idea: The user expects a seamless single sign-on (SSO) experience, where users who are already authenticated into the Dynamics 365 portal can view the embedded Power BI report without being prompted to sign in again, even after refreshing the page or opening a new tab. ... View more

The request is to ensure Schedules are not included in the definition of a Data Pipeline for purposes of Deployment Pipelines.   Today, when we deploy content across environments, the item frequently appears as “different” because the schedule configuration is included in the comparison. This creates constant noise and makes it harder to identify meaningful differences.   More importantly, a schedule configured in DEV or TEST can be promoted into PROD as part of a deployment. This creates a real operational risk and is unacceptable — PROD scheduling must be managed independently and explicitly, not carried over from lower environments. ... View more

When creating a report in the service using an Excel or CSV source, it's not possible to download the report, which is a known limitation. However, it would be helpful if a banner could pop up to notify users of this while creating the report directly from the service. ... View more

Hello Microsoft Team,   Currently, Power Automate offers a trigger for Power BI dataflow refresh completion, but there is no native trigger for Power BI semantic model (dataset) refresh completion. According to community and documentation, this gap forces users to rely either on data‑driven alerts, which cannot detect failure states, or REST API polling, which requires Premium HTTP actions.   Many business workflows depend on knowing whether a dataset refresh succeeded or failed, especially when downstream automation or data quality processes rely on up‑to‑date semantic model data.   I would like to request a new built‑in trigger:  “When a Power BI semantic model (dataset) refresh completes” with outputs such as:   Refresh status (Succeeded / Failed) Error details Start and end time Workspace ID and Dataset ID This would eliminate the need for complex REST API workarounds and significantly improve automation reliability for Power BI + Power Automate users. Thank you. ... View more

Is there any way that Power BI Service provides a built‑in rule or setting to automatically stop a semantic model refresh, dataflow refresh, or paginated report execution after a custom duration such as 30 minutes. ... View more