Business Problem: Understanding semantic model structure (tables, columns, measures, relationships, and their descriptions) is crucial for both report developers and business users. While the new INFO.VIEW DAX functions allow programmatic access to this metadata, creating a user-friendly, interactive data dictionary report still requires manual DAX structuring and report design effort. This can be a barrier to widespread adoption and consistent presentation of model documentation across an organization. Proposed Solution: Introduce a native, interactive "Data Dictionary Explorer" visual or feature within Power BI Desktop and Power BI Service. Key Capabilities: Automatic Generation: Connects to a selected Semantic Model and automatically ingests and displays metadata (potentially leveraging INFO.VIEW functions behind the scenes). Interactive Exploration: Offers built-in search, filtering (by object type, name, description keywords), and sorting capabilities. Clear Presentation: Provides a clean, pre-formatted layout for tables, columns (with data types, descriptions), measures (with DAX expressions, descriptions), and relationships (ideally with a simple graphical representation). Customization (Optional): Allow basic branding or selection of fields to display. Accessibility: Easily embeddable in Power BI reports or accessible as a standard feature when exploring a semantic model in the Service. Benefit: This would significantly reduce the effort to create and maintain data dictionaries, promote better model understanding across users, ensure consistency, and encourage developers to thoroughly document their models knowing it will be easily accessible and well-presented. ... View more

Support for temp tables was introduced recently in Fabric warehouses.  For workloads/applications that are migrated from Azure Synapse SQL dedicated pools, this is a very important feature.  While I understand that Distributed temp tables are ideal going forward considering new architecture of warehouse (decoupled storage/compute). Existing applications (that support Azure synapse SQL pools) still use syntax that for Non-distributed #temp Table in application generated queries and SQL statements.  So here is what I ask-  there should be configuration/setting for a warehouse to have default mechanism for temp tables to be distributed temp tables.  Once its enabled, users/apps don't have to add clause below explicitly while creating temp tables  WITH (DISTRIBUTION=ROUND_ROBIN)   This will ensure that Insert into #temp table statements are supported (as they are only supported for distributed temp tables but not for non-distributed temp tables).    @TwinkleCyril  Tagging you here since you originally posted blog on this feature.  ... View more

Using the Task Flow to organize your various Fabric artifacts into various groupings is great! It would be helpful if we could also view and understand the assigned Task Name label in the "View Item lineage" and "View Workspace Lineage" sections. ... View more

When there is an error with a measure, the exclamation triangle icon shows beside the field when you expand the table.  If you have a lot of tables, you have to expand / collapse them all to fix the errors.   It would be nice to see the same icon at the table level so that you can just eyeball down the list to see which ones have errors. ... View more

I've tried using Co-Pilot in Fabric Notebooks to help generate SQL statements, such as "Get the first and last dates for each month in the given date ranges."  The suggestions will often include functions like EOMONTH() or DATEFROMPARTS(), which when run are found not exist in the notebook's functionality.  Can someone train/inform Co-Pilot that certain functions can and can't be used in these environments ?  I've found that it's easier and faster for me to think for myself and refer to documentation and forums than use Co-Pilot when it keeps providing code that simply can't run, which differs from what I anticipated with the tool: providing code that is directionally or wholly functional and accurate. ... View more

Just noticed Microsoft Purview eDiscovery is not natively supporting the audit logs from Power BI Desktops, where as Power BI Services do support. The audit logs like create/change/delete sensivitiy label to Power BI artifact is not logged in Purview and only retained in the Power BI admin portal. Also the documentations are not quite clear about how to get them into the Sentinel - Audit log activities | Microsoft Learn.   Does anyone knows how can we govern the user activities in Power BI Desktop outside Power BI Admin audits? ... View more

I would like to create a script activity in a pipeline. The script should start a copy job (item). The script activity asks for a data connect and does not have a non-query option. It would be nice to be able to start copyjobs (item) from a pipeline. ... 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

It would be great to set the color of the banner at the top of the workspace so you can easily identify what environment you are in (Production, Test, Dev, etc.). This would be similar to SSMS where you can set a connection to be a certain color so you don't accidently run a query in the wrong environment.  ... View more

There needs to be an API end point exposed to allow the programatic changing of the owner of a subscription. In an organization with centralized datat reporting, there are only one or two people who are creating all the subscriptions. If one person leaves and their account is deleted it is not known what will happen to the subcriptions.  ... View more

It would be nice to have the option to include a copy of the data from a source stage to a target stage, in a deployment pipeline. (Files od tables). ... View more

Dear Microsoft,   Some of your customers like banks or other big companies with regulatory restrictions are obliged by law to create a central repository with metadata and data lineage of their DWH/Reporting.    With PowerBI it is a tough nut to crack. Yes you can use REST API to loop through all the reports in a Workspace and export them to PBIX files that would be injested by data lineage software. However the new formats that use JSON would be much, much easier to work with.    IDEA: add additional paramteres to the EXPORT endpoint to allow not just PBIX but the new formats as well. Alternatively provide a simple, automated and scalable way of exporting PowerBI Service Workspace report metadata for purposes of data lineage and config management software.   many thanks, Adam  ... View more

Hi Community, as mentioned in this post, the idea is to have access to the opportunities to create presets in a JSON theme for series as well. This would provide users the option to name series and have them styled automatically. Imagine you'd have an AC / PL series in your charts and with the click of a Preset it will be styled according to IBCS rules. This would also leverage options to share partial and useful JSON snippets across the community and make data-viz-best-practises more accessible.   I would imagine to have two options for styling series: * named series * numbered series   In a named series the references would be accessed with a $id-property e.g.   "$id": "AC", [...], "$id": "PL", [...]   In a numbered series the 1. series would always be styled according to the JSON and up to N different elements could be styled through the JSON theme, e.g.   "dataPoint": [ { // 1. Series-Item "fill": { "solid": { "color": "#000000" } } }, { // 2. Series-Item "fillTransparency": 90, "borderColorMatchFill": true, "borderTransparency": 60, "fill": { "solid": { "color": "#000000" } } } ]   Thank you, Konstantin ... View more

Hi Fabric Team, I’m writing to report a bug we've encountered while using Microsoft Fabric. we rely on Fabric for our ETL and ELT processes, leveraging both Warehouse and Lakehouse features. As you know, when setting up a copy activity, we are typically allowed to use a query only on Warehouse, not on Lakehouse tables. However, we discovered that Fabric currently allows users to reference Lakehouse tables in a Warehouse-scoped query, which results in subtle and hard-to-detect issues. This behavior caused a critical problem in one of our production pipelines: records from yesterday’s load were not copied from Fabric to Oracle. After thorough investigation, we found that the issue stemmed from a query referencing a Lakehouse table, even though the copy activity was configured to use a Warehouse. Fabric did not validate this inconsistency, and as a result, the copy activity silently failed to move the expected data. This bug could potentially have significant consequences in production environments. I recommend implementing a validation step to ensure that all objects used in a query are consistent with the selected source type (Warehouse vs. Lakehouse), to avoid such hidden issues in the future.   Kind regards, Yazdan Data Engineer ... View more

The TimePointBackgroundDetail table records capacity usage at 30-second intervals. We would like to propose a feature improvement to enable data retrieval in 30-minute intervals. Alternatively, if there is another method to retrieve such data, we would greatly appreciate your guidance. ... View more

  I have a table that I can filter in different ways in Power BI, and I want to be able to copy and paste the resulting table quickly into Excel.  (No, I don't want to download the table into csv and then convert to Excel- that takes too long for what we're trying to do).  Because we have to do a bunch of groupings for each of our borrowers depending on criteria and make their own mini tables, I'd love it if we could filter, right-click on the table, and the menu give us the option to Copy All Visible Rows (with Header)" in the filtered table, which we'd then paste into Excel.     If that's not an option, it would be GREAT if we could click on the top row, hold down shift key, and click on the last row, and then do "Control C".   Or, failing that, let us lassoo the rows!   It would be a HUGE time saver!   Thanks! ... View more

Currently, Power Automate can directly trigger Azure Data Factory pipelines using the built-in connector, enabling streamlined automation and integration scenarios. However, this capability is not yet available for Fabric Pipelines, which creates a significant gap for organizations migrating to Microsoft Fabric and aiming for operational consistency. ... View more

It is very useful that one can create custom python packages and use them in a custom environment.   I however have created custom packages (using cython) that has pyd files in whl. When I try to install this notebook, I get Error "cust_lib-0.1.0-cp313-cp313-win_amd64.whl is not a supported wheel on this platform".   The contet of whl is +---cust_lib | core.cp313-win_amd64.pyd | main.py | __init__.cp313-win_amd64.pyd | +---cust_lib-0.1.0.dist-info | METADATA | RECORD | top_level.txt | WHEEL   ... View more

Power Query can't connect to dataverse ... View more