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.
Sharepoint lists mirroring issue
Hello, We currently face an issue with sharepoint lists mirroring in microsoft fabric and we have no clue what can happen because the error message is pretty useless : In fact, we are mirroring more than 20 lists but only half of them succeed. The others failed with the following error : Internal system error occurred. ArtifactId: daa35143-...-5aa6accfec68, SequenceNumber: 9 I have linked an eventhouse but the error message is still the same, no more information: Internal system error occurred. ArtifactId: daa35143-...-5aa6accfec68, SequenceNumber: 9 How can I have more information about the issue ? Thank you very much for your help, Regards
How can AI agents improve Microsoft Fabric Data Factory pipeline automation?
I am exploring how AI agents can help make data pipeline development and monitoring more efficient in Microsoft Fabric Data Factory. Some potential use cases: Automatically creating pipeline workflows based on business requirements Detecting pipeline failures and suggesting fixes Optimizing data movement and transformation steps Monitoring data quality and identifying anomalies Triggering automated actions through APIs or external tools I would like to understand how teams are currently combining AI agents with Fabric Data Factory. Are you using: AI-assisted pipeline generation? Automated error analysis and recovery workflows? Fabric notebooks with AI models for data operations? Custom agents connected with Data Factory pipelines? Would appreciate insights, real-world examples, or architecture patterns from developers working with Fabric Data Factory automation.
What are the actual network settings for Gateway access without needing to open source
When we first adopted Fabric we ran into an issue where we had granted access to the Fabric endpoints as indicated in the Microsoft docs to our Gateway server but could not get data up via the Copy Data activity. In the end we resolved this by putting the same Fabric access on our source SQL server which resolved the issue but didn't seem to fit the Microsoft advice. This was never required for Power BI connections via the Gateway, it doesn't make sense for this to be a requirement at all. It has been several years since this and we are now migrating into another set of servers. The set up is exactly the same, a gateway server with fabric endpoints allowed and the source sql server without and we cannot transfer data via data factory copy activities. We had effectively forgotten that we allowed source to Fabric connections to resolve this issue, and before doing it again wanted to investigate why this is the case. I cannot see anything in the docs that would suggest anything needs to be opened on the source server. How to access on-premises data sources in Data Factory - Microsoft Fabric | Microsoft Learn Adjust communication settings for the on-premises data gateway | Microsoft Learn Is anyone aware of any potential configuration mistakes we could have made with our servers that would require this to be the case? For clarity, the gateway and source server are actually separate servers completely.
CopyJob status is different in a Pipeline
Hello everyone! I'm having an issue with a pipeline that calls a Copy Job activity. When the pipeline sends a request for the Copy Job to run, the activity shows a "Running" status in the pipeline. However, when I check the execution history of the Copy Job that was called, the latest run already shows a "Completed" status. The problem is that the pipeline continues to show the activity as running even though the Copy Job has already completed. This keeps my entire pipeline running for a long time, and eventually the activity changes to "Completed." Here is a screenshot of the pipeline activity showing that it had been running for 26 minutes at 9/25/2026 12:17 PM UTC. And here is a screenshot of the Copy Job execution history. It shows the same time, but in UTC-3. Both screenshots were taken at the same time. This Copy Job usually takes around 10–20 minutes to complete, but the pipeline activity remained running for 54 minutes. Is this normal behavior? Has anyone experienced something similar?
Intermittent Gateway Connectivity Error in Fabric Pipelines
Hi everyone, I'm posting because we're experiencing an issue with some of our Fabric pipeline executions and would like to know if anyone has encountered something similar. We have an on-premises SQL Server and an on-premises data gateway installed on a dedicated gateway server. The issue is that, intermittently, approximately 60% of pipeline executions fail when a pipeline activity executes a query against the SQL Server database. The error returned is: "Please check your network connectivity to ensure your on-premises data gateway can access ne.frontend.clouddatahub.net and restart the service to retry the connection again once the connectivity issue has been resolved." What makes this error difficult to understand is that: We currently have more than 800 Power BI Dataflows Gen1 running through the same gateway, and none of them experience this issue. The same pipeline sometimes runs successfully and sometimes fails with the error above. Because of this inconsistent behavior, it does not appear to be a permanent connectivity problem between the gateway and the cloud service. Has anyone experienced a similar issue or found a solution? Any guidance or suggestions would be greatly appreciated. Thanks in advance!
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!
Copy Job Not Saving
I want to know how everyone is dealing with this. I have a Copy Job that brings over 30+ tables from one lakehouse to another and has column mappings. I find that when I try to edit the mapping of one table after running the Copy Job and then hitting the Apply button, I receive a validation model error message even though I only edited a single table and then the mappings of the other tables disappear and I have to redo the mappings for all 30+ tables. If I try to add another table from the source, all my mappings from the previous sources will disappear as well and I have to redo it. I was hoping that I could hold onto the JSON code and paste in the old mappings but there's no way to edit the Copy Job JSON file only to view it. How is everyone editing their Copy Jobs?
Fabric Data Factory system variable pipeline().triggertype
Hello I would be grateful if someone from Microsoft would clarify whether, for Fabric Pipelines, the system variable pipeline.triggertype() is officially supported. Our pipeline is set up to be triggered by a schedule. At the moment, on pipeline run, when we pass the value of the system variable pipeline.triggertype() through to our own logging tables, it returns the value of either Manual or 1. This is different to what is stated in the pipeline development user interface, which shows that it passes through value of either Manual or Scheduler. Also in the documentation below re pipeline scope variables for Fabric data factory, no mention is made of the system variable pipeline.TriggerType() https://learn.microsoft.com/en-us/fabric/data-factory/expression-language#pipeline-scope-variables Please clarify if the values of Manual and 1 currently being passed through are a reliable means to determine whether the pipeline was a manual or scheduled trigger - or will these values be subject to change? If not reliable, I will have to develop a manual work around. Many thanks for your help in anticipation.
