Dark Mode for Power BI Service and Fabric. ... View more

Description: Microsoft Fabric currently provides a REST API to retrieve metadata about cloud connections (GET /v1/connections/{connectionId}), but it lacks two critical capabilities for administrators: Live connection status (e.g., online/offline) Tenant-wide visibility of all cloud connections without requiring explicit access to each individual connection These limitations hinder proactive monitoring, automation, and governance in enterprise environments.   Proposed Enhancements: Extend the Fabric REST API to include: Connection health status (online/offline) Introduce a new admin-level endpoint to: List all cloud connections across the tenant Include health status Benefits: Enables automated monitoring of cloud connection health Supports CI/CD pipelines with pre-deployment checks Reduces manual effort in troubleshooting refresh failures Improves governance and observability for platform teams Empowers admins to audit and manage connections centrally   Use Case Example: As a Fabric Platform Lead, I want to periodically check the status of all gateway / cloud connections used in semantic models and dataflows across the tenant. If any are offline or misconfigured, I can proactively alert owners or reauthenticate the connections managed by myself— all without relying on manual UI checks or refresh failure logs. This capability is essential for maintaining reliability and performance in large-scale deployments. ... View more

It can be confusing to have multiple tabs or browser windows open at the same time.   Sometimes we think we are working in a development workspace, but suddenly we notice that we are actually editing a notebook in a prod workspace.   Please make a visible indicator that alerts us that we are now inside a production workspace or editing an item in a production workspace.   (This means we would also need a way to tag a workspace as being a production workspace. That could for example be a toggle in the workspace settings.) ... View more

Bookmarks are currently not supported in PowerBI org apps. Could this feature please be added? ... View more

Currently Dataverse is not available to use as a real-time data source. Adding Dataverse will allow dashboards for real-time views of Dataverse and other Power Platform data natively. Real-time dashboards previously supported dataverse data with power automate pushing to streaming datasets. This capability is now deprecated but not replaced.   ... View more

Make it possible to change owner on all Fabric items types. Both through API and in user interface (UI). Otherwise, we will get issues when the item owner leaves the organization. ... View more

Description: Currently, when using Shortcuts in a Lakehouse, the Analytical (SQL) Endpoint automatically infers schema from Delta/Parquet and exposes all string columns as VARCHAR(8000). This creates friction in real-world scenarios where data engineers need consistent, strongly typed schemas for downstream processes (e.g., Warehouse loading, Power BI models). Problem: In multi-layer architectures (Bronze → Silver → Gold), the same Bronze object often appears in multiple ETL pipelines. Without a way to define or persist casts at the Lakehouse level, type enforcement must be repeated in every ETL. This increases maintenance overhead and risk of schema drift. Current workaround: materialize new Delta tables in Silver with Spark, but this adds unnecessary duplication and complexity. Proposed Solution: Introduce a Type Conversion Layer in the Lakehouse Analytical Endpoint for Shortcuts: Allow users to configure column-level type overrides (e.g., VARCHAR(200), DECIMAL(18,2)) when exposing data via the SQL Endpoint. If schema drift occurs (source type changes), the system should: Raise an error during refresh, OR Create a secondary object (e.g., a managed view) to preserve the original schema. The original, uncasted object should always remain available for full flexibility. Benefits: Reduces repetitive casting logic across ETL pipelines. Improves governance and consistency in Silver/Gold layers. Aligns Lakehouse with Warehouse capabilities (e.g., VARCHAR(MAX) support).  Considerations: Acknowledge that this introduces complexity for schema evolution. Provide clear UI/UX for managing type overrides and handling drift. ... View more

Problem: Currently, when a dataset is connected to a Lakehouse as a datasource in Power BI Fabric, it defaults to a cloud connection mapped to SSO. In embedded mode, reports built on these datasets fail due to a lack of identity, as they do not inherit authentication from the service principal. To resolve this, users must manually adjust the datasource settings via the Power BI service https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-fixed-identity   Proposed Solution: Introduce a new REST API or extend the current API functionality to allow programmatic setting (or re-setting) of the connection to the service principal, including updating datasources. Benefits: Automates the process, reducing manual intervention Minimizes downtime for embedded reports Enhances developer experience and deployment efficiency Ensures consistency in authentication settings across different environments Impact: This feature will significantly improve the workflow for organizations embedding Power BI reports using service principals, ensuring seamless and automated datasource authentication. ... View more

When filtering by Keyword in Monitor it only filters on the current page view.  If there are items within the time period that are not in the current page view due to the page loading limits it does not show them. The only way currently to see these is to keep scrolling down to increase the items in the view for the whole time period and then apply the filter. This is much better in ADF or Syanpse as the filter by Keyword searches all the items not just those on the page view. Can we have this work the same way in Fabric Monitor. ... View more

One of the most commonly used features when building pipelines from scratch in ADF or Synapse is 'debug until', which is surprisingly missing in Fabric data pipelines. Why deactivate all the activities to test the first 2 activities? Kindly enable this option as soon as possible, which makes data engineers' work a little easier. ... View more

We have an Azure Blob Storage account with multiple containers. We use SAS tokens to give access to specific containers—not the whole storage account. When we use these container-level SAS tokens in Power BI Desktop to build reports, everything works fine. However, after publishing the report to the Power BI Service (app.powerbi.com), the data refresh fails. Power BI says the credentials are invalid. If we use a SAS token that gives access to the entire storage account, the refresh works. It would be helpful if Power BI Service supported SAS tokens scoped to individual containers. It is currently not possible to use container-level SAS tokens in Power BI Service. But,we couldn’t find any official documentation confirming this. ... View more

Ability to take ownership of items as a Service Principal with the Fabric APIs. The functionality is available for Fabric data warehouses. ... View more

With the rising adoption of Multi-Factor Authentication (MFA) across our organization and industry best practices, we are seeking a more robust and streamlined authentication method for connecting Power BI to Snowflake. Currently, Power BI primarily relies on username/password or OAuth 2.0 via Microsoft Entra ID. While these methods are functional, they can become cumbersome and less secure in MFA-enabled environments. We propose the implementation of RSA key pair authentication for Snowflake connections within Power BI. ... View more

Problem: Copilot controls are still too broad (tenant, capacity and workspace, AD group). Even with a separate smaller Copilot capacity to redirect compute away from main capacity, individual heavy models can still drive compute and cost inside that capacity leading to rejection states. Large or sensitive models feel this the most, especially when chat and prompts hit DirectQuery or composite designs. If we turn Copilot off at the org, workspace, or AD-group level, we also lose useful features like AI summaries in subscriptions. We need guardrails that protect fabric capacity during peak periods without shutting Copilot off everywhere.   Suggestion: Add a per semantic model setting that lets model owners enable or disable specific Copilot capabilities for that model, independent of tenant or workspace defaults. This allows precise control where compute and cost or performance constraints are highestwhile keeping benefits like AI summaries available even if chat is turned off.   Examples: Semantic Model A: turn Copilot off completely. Semantic Model B: keep AI summaries for subscriptions but disable Copilot chat. We should expose Copilot only on models that have been prepared and performance validated, and keep it off by default for everything else. ... View more

Make the Workspace the owner of all the Fabric items inside the workspace. So we don't need to worry about what happens to the items when a user owning an item leaves the organization. ... View more

Customer need "Users can work with variable libraries" in admin portal settings as shown in below image:   This variable library has become generally available and will no longer have these settings in the admin portal. However, customers need this feature to allow certain users to access it by using specific security groups and adding users into security groups.   This ensures that only the specified security groups will have access to use the artifact.     ... View more

Please make it possible to use Azure Key Vault Reference to fetch Service Principal secret for Fabric Lakehouse connector and Fabric Warehouse connector. ... View more

At present, the only supported method to access Customer Insights data within Microsoft Fabric is by creating a Dataverse shortcut. This shortcut establishes a connection to the underlying Dataverse environment where Customer Insights stores its data. However, this integration currently supports only delegated permissions through OAuth2 with user credentials.  This means that access is tied to an individual user's identity and session, which introduces several limitations. Security and Operational Limitations No support for service principals: Prevents the use of managed identities or Azure AD app registrations, which are essential for secure, automated, and scalable enterprise integrations. Tight coupling to individual users: If the user who created the shortcut is removed or disabled, the connection breaks, potentially disrupting critical data flows and processes. Increased risk and complexity: Delegated access increases the risk of credential exposure and complicates access management, especially in environments with strict compliance or auditing requirements. Suggested Enhancement Enable Dataverse shortcuts to support service principal authentication using the client credentials flow, allowing secure and automated access without relying on individual user accounts. ... View more

Possibility to split an F64 capacity into smaller sub-capacities, while retaining F64 benefits (e.g. Power BI free readers can read content). The capacity admin should be able to set a "ceiling" on how much compute each sub-capacity is allowed to use. This will help to avoid compute consumption getting out of hand. The sum of the max limits ("ceilings") for each sub-capacity could exceed the max limit of the original capacity. So we could be "optimistic" when assigning limits to sub-capacities, if we choose. However, if the actual combined consumption of the sub-capacities hits the limits of the original capacity, then we would of course be throttled just like today. The purpose would be the ability to limit the resource consumption of some workspaces, by assigning them to a limited sub-capacity, while also keeping the benefits of being on an F64+ capacity. ... View more