Right now everyone in a workspace can create and manage all the items. Already in Power BI this often results in a huge mess in large organisations since many business users are not trained properly. From a Governance point of view it would be great to be able to limit e.g. Data Factory elements to our group of Data Engineers and Notebooks/Lakehouses to our trained Data Scientists and limit Power BI elements to our group of BI Analysts. Give us the option to limit what employees can do based on Security Groups. ... View more

today, if you want to give contributor role to a business user, they can basically create any item include Lakehouse, Spark Notebook etc, in our case, a lot of users are just familiar with PowerBI and we would love to have an option to assign something like PowerBI_Contributor/ PowerBI_viewer so we can turn on our fabric capacity with a peace of mind. ... View more

The ask is to integrate something like Azure Monitor/Log analytics or a better solution to centralize the logs within Fabric. In particular, it must be possible for semantic model and Power BI report developers to see the individual queries (M, dax, or sql) executed by their artifact to purposefully evaluate its performance. ... View more

For all Fabric items besides Power BI: Only item-level metadata and lineage will be captured, scanning metadata and lineage of sub-level items like Lakehouse tables or files isn't supported. In other words, currently, Purview does not support scanning sub-level artifacts such as tables and columns in Lakehouse KQL databases and Data warehouse. Data Products are usually composed of tables, not databases thus failure to register tables in the data map, and data catalog makes it impossible to manage Fabric data products in Purview. ... View more

It would be nice if when a user searched the Catalog in Purview they are shown the column names rather than just the object they reside in. With the current functionality, if a user searches for a column, they have to open the Object, go to the Schema, and scroll until they find the column. ... View more

Please add the ability to see the lineage of the indivdual tables that are used from a semantic model into reports published on fabric. The lineage view is already super handy and helpful to determine what dashboard uses what sources. Adding the ability to see what tables are sued and in which reports is a mjaor win for governance to make sure everyone is on the same table and that the unused tables can be easily identified and removed for compliance and security. ... View more

Requesting that Task Flows be able to include items across workspaces. A host of Microsoft documentation recommends splitting different items/objects across workspaces. For example, we have our lakehouses in separate workspaces from our semantic models, and those are in separate workspaces from our reports built on the semantic models. Task Flows would add significant organizational value if we could use them, but with them being constrained to a single workspace, they're currently of very limited value. ... View more

Complete lineage view, including for example: across workspaces all Fabric items data which gets "pushed" (written) from an item to a destination data connections which are written in code (parameterized) etc. ... View more

Provide an experience to link domains in Fabric to business domains in Purview Data Governance aligning things like roles and artifacts with a way to switch between the Fabric and Purview portal. ... View more

Often Data factory is managed with a SQL server to manage watermarks, queries, batch size configuration etc. to be used with dynamic content in order to increase reuse and repeatability. Currently there is no standard SQL server function or configuration management of Data factory within Fabric meaning customers would have to create the database in Azure limiting the 'one stop shop' and SaaS offering of Fabric. Being able to create a simple light database within fabric that has standard SQL capabilities would be great. Integrating it more with DF would be even better as it would lower confusion of why a standard SQL server would be needed. Current workaround is to use a SQL warehouse though functionality is limited. ... View more

Dear reader, I'm working at a data engineering team and for our customers we would like to export monitoring logs from Microsoft Fabric. To automate this for Synapse and Data Factory we used the log analytic workspace. I saw that there is a connection possible to log analytic workspace from the Fabric workspace, however there isn't an option to export the monitoring logs within that same connection. Could that be made available? That would help alot to monitor multiple clients at once, instead of opening every fabric capacity each day. Best regards, Wilco ... View more

It would be great to have data documentation, data modeling, cataloging, definitions, descriptions and ownership tied to the physical data tables, reports, notebooks, dataflows, semantic models, objects, etc... Most people agree that doing this is important and generally a missing piece in the data world. If it could be integrated to the physical objects people will use it more. We could track changes to the documentation, see which objects are missing it, etc... This could be used in data exploration helping people understand their data more. Copilot would be a great fit to help with this. Even just a simple notes link to each object would be a start. Could this architecture be created in a way that the same parts could be used for documentation in the rest of the Power Platform too? Thanks ... View more

Domain administrators can control the types of items that can be created, either by security group, subdomain, or at the workspace level. ... View more

With the recent open-sourcing of Databricks Unity Catalog, which has proven to be a fantastic capability for data governance in Databricks, are there plans to integrate Unity Catalog into Microsoft Fabric? Adopting this tool in Fabric could significantly enhance our data governance capabilities. ... View more

Currently mane organization are struggling to identify the right assets and they are not rightly utilizing Azure Purview too. Can we build around a solution where Fabric OneLake creates table & column level description using Co-Pilot and provide suggestion to the customers on how to setup the reporting structure, Business glossary and help in rightly tagging the tables/ assets to the right glossary. This will help in Data Owners to align right data security by creating data stewards, limiting access on entire datasets. ... View more

Currently in Fabric, one can set notebooks and pipelines to run in set schedules. However it is difficult to get a big picture of everything that is scheduled. A "triggers"-pane (like in ADF) would be very useful to see everything that is scheduled. ... View more

It would be a very nice addition to the context menu, if I was able to clone a notebook from the workspace experience in Fabric. When clicking the three dots (...) I should be presented with an option to clone the notebook. The notebook should named " _copy_ " ... View more

I really need an overview of all the scheduled jobs in fabric, both the ones that i have scheduled to run, that the ones that are scheduled by the system. For example the usage statistics, which is set to update by the system, but it is not possible to see it. ... View more

In the monitoring hub, when clicking on recent runs for an artifact show additional details like end time, duration, refresh type, error message, etc. This will save time when investigating errors and/or long-running refreshes without having to navigate to each artifact and looking at it's refresh history. ... View more