Currently, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... View more

We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more

  The current inability to parameterize connections in pipeline activities means we need to use the same identity to run the pipeline activities across dev/test/prod environments.   This means the same identity needs to have write access to all environments dev/test/prod.   This creates a risk that code executed in dev writes data to prod, because the identity has write access to all environments.   Please make it possible to parameterize the connection of all pipeline activity types, so we can isolate the identities for dev/test/prod and make it physically impossible for a dev pipeline activity to write data to prod environment.   Here's an overview based on my trials and errors:   Activities that do have "Use dynamic content" option in connection:   - Copy activity  - Stored procedure  - Lookup - Get metadata - Script - Delete data  - KQL   Activities that do not have "Use dynamic content" option in connection:   - Semantic model refresh activity  - Copy job - Invoke pipeline - Web - Azure Databricks  - WebHook - Functions - Azure HDInsight  - Azure Batch  - Azure Machine Learning ... View more

Similar to the Monitor page, where we can see what has run and what is currently running, it would be useful to see what's scheduled to run in the future. This to check that all schedules are set up as expected.   Reason: Easy and conveniently verify that all schedules are configured as expected. ... View more

Today, only Oauth 2.0 (user account) is supported as authentication option when setting up an Azure Key Vault reference.   Please add support for Workspace Identity  Service principal User assigned managed identity ... View more

Currently, with the new multiple scheduler feature, we can define multiple run schedules for a Fabric item. However, when using deployment pipelines, there’s no way to control which schedules are active in Dev, Test, or Prod. This means schedules intended only for Prod must also run in Dev, consuming unnecessary compute.   It would be very useful to allow using the Variable Library or deployment rules to set the active/inactive state of each schedule per environment, making deployments more efficient and flexible. ... View more

When connecting to a semantic model currently, we have to use the workspace/lakehouse/warehouse unique id and semantic model unique id in order to analyze that semantic model.  Instead of using those unique ids attached to a very specific semantic model we should be able to have the ability to customize those unique ids to a static customizable user friendly names for ease of use and the best customer experience.  Currently if I want to analyze a semantic model in Microsoft Excel or another methodology, if I have to connect to that model with the unique workspace/warehouse/lakehouse id and unique semantic model id, why can't I use the user facing workspace name, lakehouse name and semantic model name?  Why are we using GUIDs in 2025?   Additionally, if I have a new model that needs to replace an existing model, I should be able to replace or rename that model to the existing model name and it should inherit the current model's lineage vs recreating and redeploying all the associated lineage items to the new model.  This would save so much development time it's ridiculous that there is no solution for this currently. ... View more

Please make it possible to access the Workspace Name as a system variable.   It would be very useful to be able to easily include the workspace name when sending alerts from the data pipeline.   Currently, only Workspace ID is available as a system variable i.e. pipeline().DataFactory. ... View more

its well known that intellisense has always been broken with things like ListList.Contains or pressing . after typing certain prefixes does not correctly show options, or typing null enter puts null.type in. Also a huge issue is no intellisense in Dataflows both need fixing ... View more

Hi Power BI currently allows deleting report pages only one by one Large reports with many pages become slow to manage and reduce productivity. A multi-select delete option is needed to remove several pages at once. In addition, reports with many pages are hard to navigate. A search box for pages would help users quickly locate the page they need. Both features will improve efficiency and make complex reports easier to maintain. ... View more

While CI/CD support for Job Schedules can be a useful feature, it is not always desirable.   It would be better if users could choose whether this is enabled for a workspace or via something like a .gitignore or perhaps .schignore for more fine-grained control.     ... View more

It would be useful to configure different refresh frequencies for specific time windows within a single day. For example, during peak hours a data pipeline could run every 15 minutes, while during off-peak hours it runs every hour. This provides more flexibility and efficient resource usage.   Even with the multiple schedule features which was recently released (summer 2025) this is not possible. We still need to manually input each timepoint, possible 30+ timepoints, when setting up the schedules. Which feels very cumbersome. ... View more

Currently, the Lakehouse destination only supports Organizational account authentication.   This means the destination connection is depending on a specific user's account.   Please make it possible to use Service Principal authentication instead.   By going through the destination settings inside the Dataflow Gen2, I can see that the options for connecting to the various destinations are:   * **Lakehouse**    * Organizational account * **Warehouse**    * Organizational account    * Service Principal * **Fabric SQL Database**    * Organizational account    * Service Principal * **Azure SQL Database**    * Basic (username/password)    * Organizational account    * Service Principal    * Workspace identity    * Note: Basic and Service Principal options can use Azure Key Vault references in this connector. * **Azure Data Explorer**    * Organizational account    * Service Principal * **SharePoint**    * Anonymous    * Organizational account    * Service Principal    * Workspace identity * **Azure Data Lake Storage Gen2**    * Account key    * Organizational account    * Shared Access Signature (SAS)    * Service Principal    * Workspace identity   (Sorry about the bad formatting).   The Lakehouse destination only supports Organizational account - why? ... View more

Please add an endpoint to the Job Scheduler API where we can get a list of all failed runs.   The response from this endpoint should, by default, include all failed runs across all workspaces that the caller has access to, and include all item types.   The caller must specify a startTime and an endTime in the request, to only search for failed runs within that time interval.   Optionally, to narrow down the search further, the caller can specify: workspace IDs (list of IDs) item types (list of item types) item IDs (list of item IDs) The default should be to include all. ... View more

A Fabric item can now have up to 20 schedules attached to it.   These schedules can have different purposes, let's say one is for nightly runs and another one is for runs during working hours.   If we want to update a schedule via API, we need the schedule ID.   To get the ID, we can list the schedules. But, there's no easy way to pick the relevant schedule from the returned list or schedules - because there's no name or description associated with a schedule object.   Please add the option to create a name or description for an item schedule.   This could also show up in the run log of an item (run was triggered by schedule [Name]) which would provide useful context for the run.   It could also be cool if an item could pick up the schedule name as a "TriggeredBy" property and potentially execute conditional logic depending on which schedule triggered the run. ... View more

Please add support for mirroring to OneLake from on-premise SQL Server. ... View more

As Schedules are Git integrated and cary across when using deployment pipeline, I'd like to be able to use the Variable Libary value sets to parameterise within the configuration of "Schedules" for Data Pipelines and Notebooks. For example I might want differing schedules for each environment, Feature Branch Workspace, Dev, Test or Prod environments.  As a minimun is would be useful to be able to use this feature to "toggle" schedules on or off using variable library values, but even better if the specific date/ time settings of the schedules could be controlled via parameters.  ... View more

Enable to modify the mashup document of a Dataflow Gen2 by passing a variable from a pipeline before an execution of the Dataflow ... View more

Please make it possible to open a dataflow gen2 without taking it over. I wish we could open a dataflow gen2 even if it is "owned" by someone else in the workspace. I think that the user who opens the dataflow gen2 should need to apply their own - or shared - data source connections in order to see any data in the query steps. Otherwise, they would be able to use the owner's connections to interact with the data sources, and I don't think that's a good idea. Because the owner might not want other workspace members to use his/her connections. So I think that the user who opens the dataflow gen2 should need to apply their own - or shared - data source connections in order to see any data in the query steps. I think it should be possible to open the item and start editing it, and not having to formally "take over" until you are ready to publish the changes. Or some times you just want to open it for inspection without making any changes. And if you do start to edit the dataflow, but then realize you aren't able to authenticate to all the data sources, then it should be possible to cancel so that the dataflow remains unchanged and the previous connections keep working. Would be nice to have: before a user saves (publishes) changes to the dataflow, there could be a validation step to check that the user has authenticated properly to all of the item's data sources and data destinations, so that they won't cause the dataflow to stop working. If the validation fails, the dataflow should keep running with the previous connections and the changes should be undone. ... View more