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.
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.
News about Refresh Materialized Lake View activity in Fabric Pipelines
Hi, this month the Refresh MLV activity in Fabric pipeline is available in Public Preview, as reported in this article Refresh Materialized Lake View activity in Fabric Pipelines (Preview), but when will this feature be in GA? It's a feature very useful and important! Many thanksError - Using the MongoDB Om-Premise Connector
Hello everyone, I'm trying to establish a connection between Fabric and an on-premises MongoDB server. https://learn.microsoft.com/en-us/fabric/data-factory/connector-mongodb-overview In fact, the scenario involves writing data from Fabric to an on-premises MongoDB NoSQL database. The connection has been successfully established on the gateway side (with all necessary firewall rules configured). Then I see the connection in the “Copy Data” section of the “Data Pipeline.” So that means the mapping is working properly. However, the connection test isn't working... Of course, the error message doesn't help at all. For your information, here is the server pattern specified in the gateway connection mongodb01.example.com:27017,mongodb22.example.com:27017,mongodb03.example.com:27017/?authMechanism=DEFAULT&authSource=xxxxxxxxx Thank in advance for your help Have a nice day, Vivien
Changing the server/connection path in existing connection?
In Fabric in 'Manage connections and gateways', once the connection is created I can't edit the server of the SQL server anymore or base URL for API for example, it's greyed out. Is it possible to edit this without deleting the existing connection and recreating it? This is an example for a connection for Fabric API, but it's the same thing for all my connections. Can't change connection type, which makes sense, but I should be able to change the data source path. edit: I created this connection, and even the tennant admin can't do this
