Enable individual users / freelancers to study and practice fabric with a per-user license similar to Premium Per User in Power BI. F2 is a price point that is too high for them. Strong limitations in time and resources available would make sense, but there should be a clear monthly cap that cannot be like the current F2. ... View more

When data from SharePoint Online lists are made into dashboards in Power BI, users should be able to show or hide them at will. ... 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

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

Is it possible to add more write access roles for specific folders in a lakehouse? It seems that the folder-based access currently only has the option of providing read access to other users. We are thinking of a data landing lakehouse for external users to upload data into specific folders they are provided access to. ... 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

There are a large number of Fabric API's available, all with a lot of functionality. Which is good. The one functionality I'm missing is the one where I can get to my pipeline or notebook and return the result. The use case? To build a dashboard for customers to show the status of their ELT/ETL processes. Instead of having to dig through all the items manually, I want to have a process that can run every X hours to get the status of the latest run, save it into a database and visualise the results in a Power BI report. It would be a very nice to have if it could show the amount of CU's used as well but with all the smoothing, that might be a far stretch. But getting the result (succeeded/failed) shouldn't be that hard I think. As a definition, a pipeline fails when there's a failure that's not caught by an error handling. A notebook fails whenever one of the cells in the notebook fails. ... View more

Make it possible to add multiple owners on all Fabric items types. Both through API and in user interface (UI). To decrease risk of item unavailability when a single item owner leaves the organization. ... View more

Please make bookmarks available in the Org App. We group reports in a workspace and want to share them out like a dashboard view, however our end users require personlized bookmarks for reports. This minimizes the number of reports we need. ... View more

Can we just get an API that does whatever is going on under the hood when the user goes through the UI and does the Edit Model > Refresh action? I have a lakehouse. I build a custom semantic model from it. Now I add or delete columns in tables of the LH. As Patrick points out in this GIAC video, there is no way to get the model to auto-update columns (add or delete them). You have to go into the UI (Edit Model > Refresh). https://youtu.be/2RuoHpNZbc4?si=zSbhKHc0G0iIzQVJ That is a non-workable solution for any large deployment. There is an API that can modify the model schema, but it requires explicit naming of columns to be added or deleted. That requires coding scripts that read the LH model, compare it to the semantic model, then dynamically build script to add/delete columns. So ... can we just get an API that does whatever is going on when the user does Edit Model > Refresh in the UI? We clearly have the function to do it. Just need to be able to call it. ... View more

Bring-Your-Own-Key aka. Customer-Managed Keys for encryption is a mandatory requirement in many companies to ensure compliance with GDPR and internal security regulations. As long as Fabric doesn't support BYOK, we can't use it's full potential. Key Vaults must be assignable on workspace-level or lower, e.g. per lakehouse, so that we can reduce the risk of a compromised key by decentralizing the key management. Defining one Key Vault per Workspace would imho be the best balance between decentralization and maintenance effort. ... View more

The current version of the Fabric API's does not support executing via a Service Principal. This makes automation from Notebooks/Azure Functions/... difficult, and is not in line with how the "old" Power BI API's are working. Please add support for Service Principals when running the new API's. ... View more

Currently we cannot associate one workspace to multiple deployment pipelines. If We have two workspaces with different sets of code and want to deploy to one Workspace that holds all code. It is not possible to create two deployment pipelines and deploy code from two workspaces into one. Use case: We have architecture where common/orchestration code sites in one workspace and deploy the code to any team's workspaces that want to utilize our orchestration code. With current product limitation, we cannot have multiple deployment pipelines created for each team and have common code workspace assigned to each pipeline. ... View more

Currently, it's not possible to load an Excel file directly from the lakehouse into a PySpark DataFrame within a Fabric notebook. The existing solution requires first loading the file into a Pandas DataFrame and then converting it to a PySpark DataFrame, which negatively impacts performance with large files. It would be helpful if a Spark engine were available that allows Excel files to be loaded directly into a PySpark DataFrame, similar to how CSV files can be handled. ... View more

Idea: Allow syncing of "Object Type Code Name fields" from Microsoft Dataverse Reason: Currently, when making a Fabric Lakehouse link from Dataverse, for choice fields, only internal values (Object Type Code) get pulled from Dataverse (e.g. "recurringapppointmentmaster" instead of the more eligible "Recurring Appointment"). While in Dataverse the column Object Type Name doesn't get pulled to Fabric Lakehouse Benefit: By allowing this extra field to by synced to Lakehouse also, it takes away the need for manual intervention, in such cases when the more stylized and eligible Object Type Code Name is preferred over the internal values, like when used Reports, Analytics and Presentation. Especially since Fabric is already a Storage and Analytics service. ... View more

To work with S3 shortcuts without storing credentials somewhere in Fabric would be amazing and more secure. That would be possible with Identity Federation for passwordless Authentication based on Workspace Identity. AWS IAM allows to build this, there should be a good instruction and the technical possibility. ... View more

Currently only git repos in Azure Devops are supported as part of the git integration for workspaces, see https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration#considerations-and-limitations Given we use Github for all our other repos and we would like to keep all repos in Github, we would need Fabric to support Github as well. ... View more

At the moment, it's only possible to set a default value for the parameters of a data pipeline. It would be beneficial if a dropdown list could be created for specific parameters. This would allow business users, when manually triggering the data pipeline, to save time by avoiding the need to manually enter parameter values and reduce the risk of providing incorrect values. ... View more

I wish it was possible to set a limit on a workspace level on how many CUs the workspace was allowed to use. And also an option to bundle together workspaces and set a limit on how many CUs these workspaces were allowed to use combined (e.g. dev and test workspaces). Possibly also an option to prioritize some workspaces (e.g. prod workspaces or critical prod workspaces). That way, we could reduce the risk of exceeding our capacity and cause problems for critical workloads. ... View more