Please add workspace settings >> Data Warehouse >> Collations to the Fabric rest API config.   This is the only way make Lakehouse SQL Endpoint Case insensitive, it is a must for customers coming from a SQL background.  Currently I deploy workspaces by automation, then manually change the collation then deploy Lakehouses & Warehouses which is time consuming and annoying....   This is pre-req before the terraform provider could also be updated to set.   Thanks, Darren ... View more

Currently, the Azure Maps visual in Power BI cannot be effectively restricted to specific security groups. Administrators require more granular control to enable or limit usage for selected users or departments, especially for governance, compliance, and controlled feature rollout scenarios. It would be better if we give an option to enable for specific security groups. ... View more

Customer is looking for the Azure SQL Database connector in Power BI Service to create a cloud or gateway connection without creating any semantic model, dataflow or a report, just to create a connection to use the connections in Pipelines as creating a connection will help them create a unique ID.    Raising this on behalf of our customer. ... View more

Customer is seeking a solution to retrieve gateway roles assigned to all users across all gateway connections within their tenant. However, based on our current assessment, there is no out-of-the-box method or available API that supports retrieving this information at a tenant-wide level. Could you please confirm if there are any alternative approaches or solutions to achieve this requirement? Raising this on behalf of our customer. ... View more

I would suggest to introduce "folders" to have new connections organized in a easier and segregated way. In a Enterprise environment, wheer all teh connecitons to resources are managed ina  centralized way, having the possibility of creating folders, as in the Workspaces, would allow better organized resources (e.g. Like in the Deployment pipelines). Thank you for the opportunity, Alfredo Lourido Santos ... View more

Customers using the Power BI Output Tool in Alteryx to publish datasets to the Power BI Service are currently limited by the backend Push Dataset API restrictions. Since this tool relies on the Push Dataset API, the same limitations apply during publish, and datasets with 10M+ rows cannot be pushed successfully. We would like an enhancement to this limitation so customers can publish large datasets/models from Alteryx flow to the Power BI Service using Power BI output tool. This is important for enterprise scenarios where Alteryx is used as the primary data preparation and publishing tool, and the current API-based limit prevents large-scale reporting workflows from being implemented efficiently. ... View more

Summary The recently introduced Recycle Bin in Microsoft Fabric is a very useful addition; however, it currently lacks support for multi‑select and bulk delete operations. Although the UI displays a checkbox (square box) suggesting multi‑selection is possible, selecting multiple items does not allow deleting or restoring them in one action. Current Limitation Users can only delete or restore one object at a time. The UI visually implies multi‑select capability, but the functionality is not implemented. This becomes inefficient and time‑consuming when cleaning up: Abandoned pipelines Temporary lakehouses Test notebooks CI/CD artifacts Failed or duplicate objects Expected / Requested Enhancement Enable the following capabilities in the Fabric Recycle Bin: True multi‑select support Allow selecting multiple objects using checkboxes. Bulk actions Delete selected items in a single operation. Restore selected items in a single operation. “Delete All” or “Empty Recycle Bin” option Similar to the Windows Recycle Bin experience. Clear visual feedback Enable/disable action buttons based on selection state. Why This Is Important Improves productivity and usability, especially in development and test environments. Aligns user expectations with standard operating‑system behavior (Windows Recycle Bin). Reduces repetitive manual actions and accidental errors. Supports better workspace hygiene, especially for teams using: CI/CD Frequent branching Automated pipeline generation Business Impact Faster environment cleanup Better developer experience Lower operational friction More intuitive and consistent UI behavior Conclusion Since the UI already indicates multi‑select capability, enabling bulk delete and restore would be a natural and highly valuable enhancement. Making the Fabric Recycle Bin function similarly to the Windows Recycle Bin would significantly improve usability and efficiency. ... View more

Problem: Currently, there's no way to filter the "CU% over time" visual by workspace.   This means we're unable to track interactive CU% by workspace. We have 20+ workspaces in a capacity, and we wish to filter the "CU% over time" visual by workspace.   Proposed solution: Make it possible to filter the CU% over time visual by workspace. ... View more

Server-Sent Events (SSE) is a highly popular and rapidly growing protocol particularly for applications requiring one-way, real-time data streaming from server to client.   This is a nice addition to the HTTP connection source as offered at this moment. The SSE protocol built-in auto-reconnection with a 'last received message id' makes it easy to offer disconnects without message loss.   We see SSE also being offered by Azure IoT Operations so there is knowledge with Microsoft on how to set this up efficiently. ... View more

Add a new Transform CustomCode node in Eventstreams that lets users author and run sandboxed JavaScript or .NET code as a streaming transformation step—similar in UX placement to existing transformations and the SQL operator, but designed for arbitrary code logic.  ... View more

Please make the Page Preview image in the email larger so that users can consume directly from the email.  This would be soooo useful! ... View more

A user is unable to select Analyze in Excel from a report within an app in the Power BI service. The user has been granted Viewer access to the workspace, and the customer does not want to provide Build permission on the semantic model to end users. The user understands that this behavior is expected under the current permission setup and would like to know if there are any available workarounds for this limitation.   ... View more

Having the ability to run python code outside of the notebook environment (like we can for pyspark jobs) could be a real win for efficiency and modularity. It would allow users to package robust, unit-tested code and deploy it to the fabric environment where it could run as a cost-effective single-node job. Databricks has an implementation for this, and it would be really nice to see something similar come to Fabric. Notebooks are great for ad-hoc or exploratory stuff, but building something robust in them feels like shoving a peg into a wrong-shaped hole. They are (nearly) impossible to unit test, so you often end up creating libraries which allow you to package transformations in a way that can be tested, then your notebooks end up being essentially thin wrappers around a bunch of external code. I think the most obvious example for this is the number of Fabric DBT implementations that essentially involve installing DBT core into a notebook and running it there (I know there is DBT jobs coming, but this is beside the point). This is a symptom of a larger need for this type of hosting/execution of code within the environment. Yes, you could host the code on a vm external to Fabric but that goes against the ethos of a unified data platform. Offering something like this would be a great way to increase the flexibility and extensibility of the platform. The implementation can be fairly barebones and developer forward, aiming to provide maximum flexibility and extensibility. Basically a way to run python scripts/CLI tools on the Fabric capacity.    ... View more

Category color in the new Card visual resets when repointing to a different data source. Even when using the same field, changing the data source causes the category/header color to revert to default. This breaks formatting consistency and requires manual rework during dataset switching (e.g., Dev → Prod). Formatting should persist when the same field is used. ... View more

After I create a new step, I want to be able to rename the step to document the purpose of the step.  However, I have to wait for the step to completely execute first. This can cause a delay of several seconds for a complicated query, and if I'm adding several steps in sequence, this adds up.  Other commands on the query step are available without waiting, but I'd like Rename to be included in those commands.   I know I can skip the wait by using Advanced Editor, but then I have to edit the name in multiple locations to ensure that I don't break the query. ... View more

We had a situation where a rogue report used a ridiculous amount of CUs in a Fabric Capacity, causing the Capacity to lock up. Anyway, while reviewing Fabric Capacity Metrics dashboard the same day, the huge spike reduced our normally populated CU % Over Time graph to compress the bars so badly that they are no longer visible. Also, even if we adjust the date/time slider to omit the time of the problem spike, the Y scale stays the same for the remaining data and we still can't display it.  See the attached screenshots - one with the spike showing, and one without. See the Y Axis. In the graph without the spike, there should be normal 20%-100% traffic showing. Could the Y axis have an option to use a logarithmic scale if required, and if not, can it just top out at 100%, but the tooltip and any data exports show the actual number? ... View more

Please can we extend the GraphQL functionality to surface semantic model data? This would allow us to use measures, dimensions, attributes etc in our apps. ... View more

I know there's a hacky roundabout way of achieving this using the line and clustered bar chart, but the functionality to add vertical lines to show events really should be a native feature of the line chart. As data storytellers, this feature would enable us to provide important context for our stakeholders/end users. ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more