general question
359 TopicsNews 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 thanks620Views1like3CommentsError - 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, Vivien1.7KViews0likes11CommentsChanging 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 thisSolved3.3KViews2likes6CommentsPipeline Fails with "Operation returned an invalid status code 'BadRequest'" After Successful Run
Hi Everyone, Our Fabric pipeline was running successfully but has now started failing with the below error: ❌ Fabric pipeline execution failed, error message received from failing pipeline - 'Failed to run the Pipeline: Operation returned an invalid status code 'BadRequest'' No changes were made to the pipeline before the failure. Error occurs at the pipeline level, not at a specific activity. Re-runs do not resolve the issue. Connections, capacity, and schemas are all verified and valid. Is this a known platform-side issue? Any diagnostic steps to trace the root cause of this BadRequest? Appreciate any help. Thanks! Thanks and Regards, ShreyaSolved1.5KViews0likes5CommentsIs ADF Fabric version compactable with Github Proxima on version control?
Hi, I am an internal Microsoft employee. we're evaluating whether to use Data Factory in Microsoft Fabric for a new SQL→Kusto pipeline. We need Git integration with GitHub Enterprise Server (specifically msft.ghe.com, which uses SAML SSO), instead of Azure DevOps repo. Does Fabric Data Factory support GitHub Enterprise Server as a source control backend, similar to how classic ADF does? If so, are there any known limitations compared to classic ADF's GitHub Enterprise Server integration (e.g., PAT authentication, branch management)? Thanks!Solved901Views1like1Comment