Right now if I create a semantic model in import mode then publish it to Fabric, I have to manually change the connection.  Ideally, this would not happen, but if it must, then please allow me to reuse an existing connection instead of FORCING me to create a new connection for each semanitc model; that is idiotic.  The options below are the only ones available (Default - which doesn't even work, and "Create a connection").  I would propose that we should be able to select an existing connection that already exists in Fabric. This is a very similar experience when creating and publishing a paginated report to Fabric.  I am forced to create a connection, I would like to use existing connections.   @DataZoeMS @DataZoe  ... 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

I’d like to suggest adding the ability to configure quotas for Microsoft Fabric workspaces, applicable to both new and existing workspaces. This feature would allow administrators to set limits on compute capacity (CUs) and storage usage, helping organizations better manage resources, control costs, and prevent overconsumption. Having workspace-level quota controls—similar to those in other Azure services—would greatly enhance governance and operational efficiency across larger environments where multiple teams or departments share Fabric capacity. ... View more

The option should be visible for the admin to manage delegate settings for other admins. Currently, the Delegate settings to other admins option isn't available because it's automatically delegated to capacity admins. Enable Microsoft Fabric for your organization - Microsoft Fabric | Microsoft Learn ... View more

Many users have been actively inquiring about the availability of Microsoft Fabric in the West India region, as they are currently unable to work with Fabric-related items due to regional limitations. This has impacted their ability to fully utilize the platform's capabilities for data integration, analytics, and reporting. This feature has been requested by multiple customers, indicating a growing demand for Fabric support in West India. However, it has not yet been prioritized for implementation due to limited formal feedback and usage data from this region. ... View more

As an Associate Director in Medical Affairs, I rely heavily on Power BI to deliver secure, role-based insights across cross-functional teams. However, the current limitation that Microsoft 365 (M365) Groups are not supported for Row-Level Security (RLS) presents a significant operational challenge. Our organization has standardized on M365 Groups for collaboration and access control across Microsoft 365 services, including Teams, SharePoint, and Outlook. The inability to use these same groups for RLS in Power BI forces us to duplicate group structures using Azure Active Directory (AAD) Security Groups—introducing administrative overhead, increased risk of misalignment, and reduced agility. Request: Please prioritize support for M365 Groups in Power BI RLS. This would: Streamline access management by aligning with existing M365 governance. Reduce administrative burden and potential for error. Improve adoption of secure, scalable BI solutions across business units. Impact: This enhancement would significantly improve the efficiency and security of Power BI deployments in enterprise environments that are deeply integrated with M365. ... View more

As stated in the document below, the ViewReport event is logged even when an email is sent via the subscription service.   Title : Monitor usage metrics in the workspaces (preview) - Considerations and limitations URL : https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-modern-usage-metrics#considerations-and-limitations   Due to this default behavior, the view count increases even if the report has not actually been opened, but only the email has been received.I would like to request the implementation of a feature that only counts the number of times the report has actually been opened. ... View more

Microsoft Fabric’s Lakehouse currently offers workspace-level permissions, but many collaborative scenarios require folder or file-level access control. Introducing role-based permissions at the folder level (e.g., read-only, edit, deny) will provide better security and operational control, especially in multi-departmental projects using a shared Lakehouse environment. ... View more

Hello Dear Fabric Team,  it is very painful for all of us interoducing Microsoft Fabric in Big Enterprises where Security and Governance have a big role. My suggestion is to be transparent and clear to add in appropriate Place (Power BI / Fabric Admin Portal or in Azure Portal) just a list of needed endpoints including required Ports and a yes/no check-status if the connection to each endpoint/host:port possible or not.   if it is not possible the IT-Sec Team must setup the right Firewalls/Proxy configuration Thanks Best Regards ZN ... View more

The requirement would be to provide access to the below areas whilst not providing access to the other areas in the Admin portal:   Areas to provide access: -Tenant Settings (the only app permission provides to much access ('Tenant.ReadWrite.All' )) -Usage Metrics -Users -Premier Per User -Audit logs -Workloads ( api permissions grants access to all ) -workspaces   Whilst not providing access to the rest of the admin portal.     Currently Its not possible via custom roles as this is unsupported, and via API permissions they are not granualar enough, for example ( 'Tenant.ReadWrite.All' for tenant settings )   There is granular permissions in Fabric however to get access to all the required areas would mean granting Fabric admin which also grants access to areas that the users should not get access.   Ideally we need a way to more granually assign API permissions or enable the use of custom roles for Fabric.   ... View more

I recently created a stored procedure on a SQL analytics endpoint of a Lakehouse.  I was able to successfully create a Data Source by inputting the SQL Analytics endpoint.  I was able to reference this sproc and use it to build a report.  When I deploy that report to MS Fabric, I have to then change my connection and credentials.  The only two options I have related to the connection itself are: "Personal Cloud Connection" and "Create a connection". I would rather recycle an existing connection that I already have set-up an configured in MS Fabric in the "Manage connections and gateways" area.  Please allow this functionality. I see no logical reason why I would want to create a new connection each time I publish a Paginated report. ... View more

It should be possible for admin to monitor and manage the personal bookmark created by end users. ... View more

Currently, we are able to connect a Microsoft Fabric instance to an Azure Log Analytics Workspace in order to collect and query performance and usage logs. It would be wonderful if we could do the same with audit logs. Exporting Microsoft Fabric audit logs to an Azure Log Analytics Workspace would significantly enhance security monitoring and operational visibility. By centralizing audit data in Log Analytics, security teams could leverage powerful Kusto Query Language (KQL) to perform deep forensic investigations, detect anomalies, and correlate events across services. This setup also enables seamless integration with Microsoft Sentinel, allowing for real-time alerting, automated incident response, and advanced threat detection using built-in analytics rules and workbooks. Additionally, storing logs in Log Analytics ensures long-term retention, compliance support, and the ability to create custom dashboards that align with organizational security policies. This unified approach would empower teams to proactively monitor Microsoft Fabric environments with enterprise-grade security intelligence. ... View more

The Microsoft Fabric docs provide this guide to configuring Private Link access to a Fabric tenant. However, in testing this approach a provisioned endpoint could not be connect from a separate Azure tenant. The private endpoint could be created, but when attepting to approve the connection the following error resulted:           Upon consulting Microsoft Support they concluded that it is not supported to create Private Link endpoint connections to Fabric from a different Azure tenant, citing the following documented limitations: - Customers can't connect to Fabric resources in multiple tenants from a single virtual network, but rather only the last tenant to set up Private Link. - Each private endpoint can be connected to one tenant only. You can't set up a private link to be used by more than one tenant.   Private connectivty to Fabric from a separate tenant is a high priority for our customers who rely on our services to connect to their Fabric data sources, but have strict access requirements. Please consider enabling this functionality. You may contact me for a discussion on details and requirements, if desired.  ... View more

Idea: As an engineer responsible for managing and improving Microsoft Fabric Data Agents, I currently have no way to view how users are interacting with the agents I’ve built. While it’s likely that prompt and response data is being captured internally by Microsoft for telemetry purposes, there is no mechanism that makes this data available to those of us maintaining these solutions. Proposal: Introduce a feature within Fabric Data Agents that provides engineers with controlled access to interaction logs, including: User-submitted prompts Agent responses Feedback indicators (e.g., thumbs up/down, optional comments) Outcome metadata, such as whether the interaction was helpful or resulted in follow-up Why this is critical: Without access to this data, engineers are operating in the dark. We cannot evaluate how our agents are performing, where they are failing, or what users are actually trying to accomplish. This limits our ability to iterate, improve relevance, and ensure that Fabric Data Agents deliver real value. Key Benefits: Understand real-world usage and identify unmet needs Improve agent behavior by refining instruction sets and context Proactively address recurring failure patterns Increase user trust and adoption by continuously tuning responses Align agent capabilities with actual user workflows Governance & Privacy: Access should be controlled by tenant-level permissions and comply with Microsoft’s data governance policies. Logs can be anonymized and filtered to protect sensitive content, with visibility limited to approved roles (e.g., workspace admins or agent developers). Summary: Microsoft Fabric needs to provide engineers with visibility into how their Fabric Data Agents are being used. Access to prompt and response history, combined with user feedback, is essential to improving agent quality and delivering successful AI-driven experiences. ... View more

It would be super good to be able to download the report from the 3 dots in the workspace like you can semantic model. Opening the report and then downloading from file menu seems super unnecessary.    ... View more

Currently service princaipals can't read and write to OneLake storage when Tenant Setting:  "Allow apps running outside of Fabric to access data via OneLake" is disabled   Enabling this setting to able access is enabling to much access to OneLake and a more restrcitive option is required. We need a similar setting to this one for OneLake storage access:  "Service principals can call Fabric public APIs"   eg "Service principals can access OneLake storage"   ... View more

Since F64 is required for a number of features, new customers that are starting small are required to start with that sizing. This normally means that the same capacity is shared across different environments. Currently, we can only limit the amount of resources for a workspace by leveraging Spark pools, however that does not cover the Data Warehouse experience (for instance). It would be great to have an option to assign a max of X% of a capacity to a workspace so that we can prioritize the production workloads when 1 single capacity is used. ... View more

Enable Fabric Admin to turn off all preview features to prevent users from using preview features in production.   You could allow all preview features to be used by specific security groups. ... View more