Bug: QuickBooks connector (QuickBooks for Pipeline) fails OAuth login
When attempting to create a connection of type QuickBooks for Pipeline (Cloud category) via Manage Connections and Gateways in Microsoft Fabric, with the authentication method automatically set to OAuth 2.0, clicking the Edit credentials button results in an error when trying to initiate the OAuth login flow. Error message: Unable to start OAuth login for this data source. Connection string is not supported. Details: Query contains unsupported function. Function name: QuickBooksForPipeline.Contents Session Id: 6fb86dae-dc71-4a06-8f7f-b99aee7885df RequestId: 710bfcb8-ff7a-444d-90dc-c2dcc311e0f9 Cluster URI: https://api.powerbi.com Status code: 400 Time: Fri Sep 11 2026 07:54:51 GMT+0300 (Eastern European Summer Time) Steps to reproduce: In a Fabric workspace, open a Copy Data activity (Source) or go to Manage Connections and Gateways. Click "+ New" to create a new connection. Select connection type Cloud. Search for and select QuickBooks for Pipeline as the data source. Authentication method is automatically set to OAuth 2.0. Click Edit credentials. The error above appears instead of the expected QuickBooks OAuth consent screen. Expected behavior: Clicking Edit credentials should open the standard Intuit OAuth 2.0 consent screen, as described in the QuickBooks connector documentation for Data Factory / Fabric pipelines. Impact: It is currently impossible to create a working QuickBooks Online connection in a Fabric pipeline using this connector, which blocks migrating an existing pipeline (where tokens are currently passed manually as parameters) to native OAuth authentication. Environment: Microsoft Fabric (trial capacity), browser: Chrome, date: 2026-09-11.
A bug in the Data pipeline expression builder
Since last week's Fabric update, the Expression Builder is generating incorrect expressions when selecting pipeline parameters. For example, instead of generating: It writes @linkedService().<parameter_name> instead of @pipeline.parameters.<parameter_name>. The expression is immediately flagged with an "UnsupportedConcept" error. Additionally, the value cannot be saved even after manually correcting the expression to the proper pipeline parameter syntax. The issue occurs with both newly created and existing parameters, suggesting a regression introduced in the latest Fabric update.
Workspace Identity works in one workspace but fails in another when executing Notebook Activity
Hi everyone, I'm troubleshooting an issue with Notebook Activity + Workspace Identity (WI) in Microsoft Fabric Data Factory and would like to know if anyone has experienced something similar. Scenario I'm trying to execute a notebook from a pipeline using a Workspace Identity connection. The notebook itself is very simple and does not require: Lakehouse Environment External connections The execution fails before Spark starts. Notebook Error An unexpected error encountered while preparing spark operation execution. The user access token was not found. The user session may have expired or the user is no longer valid. Please sign in again. Additional observations: In the notebook run history, the "Submitted By" column appears as "--" The notebook never reaches Spark execution Pipeline Error Notebook execution failed at Notebook service with http status code - '200' Failed to create session for executing notebook. Notebook execution is in Failed state. What I have already validated ✅ Workspace Identity exists and is active in Entra ID ✅ Workspace Identity is included in the Security Group allowed to use Fabric APIs ✅ Tenant setting "Service principals can call Fabric public APIs" is enabled ✅ Workspace Identity is Workspace Admin ✅ Workspace Identity is successfully used to access Azure Data Lake Storage Gen2 ✅ Notebook Activity is configured to use a Workspace Identity connection ✅ Notebook owner account is active and valid ✅ Pipeline owner account is active and valid ✅ No Environment attached ✅ No Lakehouse attached ✅ No external connections inside the notebook ✅ Created a brand-new notebook containing only: print("hello") ✅ Created a brand-new pipeline containing only a Notebook Activity Same result. ✅ The same Notebook Connection with Workspace Identity works successfully in another workspace Comparison with another workspace I have another workspace with: The same tenant Different Fabric capacity The same geography Different Security Group The same Fabric API tenant settings The same Notebook Connection owner and the exact same configuration works correctly there. Additionally: The same Notebook Connection was tested in both workspaces The same Workspace Identity pattern is used The working workspace can access Key Vault and execute notebooks through pipelines without issues The only variable that seems to change is the workspace itself. Additional Observation The Workspace Identity appears to be functioning correctly because it is already being used successfully to authenticate against Azure resources such as ADLS Gen2. Because of this, the issue does not appear to be related to Entra permissions, Fabric API permissions, or Workspace Identity access to Azure resources. Instead, it seems related to one of the following: Notebook Activity + Workspace Identity integration Session creation Workspace metadata Workspace-specific configuration Question Has anyone encountered a situation where: Workspace Identity authentication works for ADLS and Key Vault The same Notebook Connection works in another workspace Notebook Activity only fails in one specific workspace The error is related to: "The user access token was not found" "Failed to create session for executing notebook" Empty "Submitted By" field I'm trying to determine whether this is: A workspace-specific metadata issue A Notebook Activity bug A Workspace Identity provisioning issue An undocumented prerequisite for Workspace Identity execution Any insights would be greatly appreciated. Thanks!Materialized Lake View Refresh activity Pipeline bug
Hi all, When using the preview feature refresh mlv activity in the pipeline, is do have some major bugs. After saving, it goes back to default, the pipeline does not want to refresh after, and I cannot parametrize it. Is there any workarround, and is this a known bug? Cause this is not workable.
Is it possible to write Copy activity logging to Fabric Lakehouse?
Greetings, community. Have a requirement where we need to log what files get transferred/fail from a Copy activity. I want to use the Logging feature, but this currently only supports ADLS connections. I remember reading somewhere that it is possible to access Lakehouse as ADLS, but I cannot get that working in Fabric. Anyone have ideas?
Semantic Model Refresh failing in Pipeline but not manually
Hello everyone, we have a Fabric F8 environment with a pipeline that triggers multiple pipelines to load data into bronze, silver and gold layer. After the Gold pipeline is succeeded, a Semantic Model Refresh activity should refresh a Semantic Model in another workspace. After it had worked for a few days, the pipeline now fails at the Semantic Model Refresh step. Restarting the pipeline from that step or triggering the Semantic Model refresh from a another pipeline or manually via the Refresh Button all succeed. The error message states, that a column is missing in the rowset. The column is created immediately before the semantic model refresh starts. What I have tried so far: - adding a 15 minutes waiting time to solve any metadata refresh activities - rebuild the whole pipeline from scratch - adding an invoke pipeline step, that starts a pipeline which only contains the Semantic Model Refresh activity None of that has solved the issue. Any suggestion would be highly welcome. Error message: Semantic model refresh execution failed, error message received from semantic model refresh operation - '{"errorCode":"ModelRefresh_ShortMessage_ProcessingError","errorDescription":"Retry attempts for failures while executing the refresh exceeded the retry limit set on the request.\n0xC11200B0: The '<oii>is_anonym<\/oii>' column does not exist in the rowset.\n0xC112001C: The operation was canceled.. The exception was raised by the IDbCommand interface.\n0xC11C0006: The current operation was cancelled because another operation in the transaction failed.\n0xC112001C: The operation was canceled.. The exception was raised by the IDbCommand interface.\n0xC112001C: The operation was canceled.. The exception was raised by the IDbCommand interface.\n0xC14700F0: {\"RootActivityId\":\"46081B1B-9B40-4967-9402-297B0D45D710\"}"}'
AzureDatabricksWorkspace connector doesn't work in Pipeline with On-Prem Gateway?
Hello fellow Fabric users. I'm trying to create a Fabric Pipeline step that would trigger a job in Azure Databricks workspace using the built in activity for that (image #3). Our ADB workspace is accessible only through On-Prem gateway connection, querying from Databricks SQL connector works well through the gateway, but I need to be able to also trigger things when needed from Fabric. BUT, for some reason the activity settings do not "see" the gateway connection I created beforehand (image #1) and also when I try to create a brand new connection using built-in dialog, it completely ignores any gateways when I type in ADB workspace URL (image #2). Please advise on how to solve this 🤔 thank you!
Notebook concurrency in data pipelines not working
Hi all, I have a fabric data pipeline that runs a spark notebook then a pipeline task that calls a Azure Data Factory Pipeline and then another notebook. High concurrency is enabled, notebooks share the same environment, have the same session tag, timeout is set to multiple hours etc. I tested first the run by deactivating the pipeline task, so only the 2 notebooks run and they share the same Spark cluster correctly: Then I made a full run and for some reason the second notebook is not reusing the first cluster, but starts another one. Can somebody explain if this is a bug due connected to the pipeline task that calls an Azure Data Factory? Thanks for your help, Peter
