Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi everyone,
I'm currently planning our data ingestion strategy for Microsoft Fabric and have been exploring different ETL/ELT tools.
My team has experience with Airbyte, but we've hit a roadblock as there doesn't appear to be a native destination connector that writes directly to a Fabric Lakehouse or Warehouse.
My primary question for the community is:
1. Has anyone found a reliable and efficient workaround to get Airbyte to write data into Microsoft Fabric?
If a direct Airbyte connection isn't feasible, I'm looking for proven alternatives. Our immediate priority is to ingest data from key advertising platforms.
2. What are you using for connectors to bring data from LinkedIn Ads, Facebook Ads, and Google Ads into Fabric?
I'm especially interested in solutions that are both reliable and cost-effective. Have you had good experiences with other third-party tools (but more cost effective than Fivetran, CData, Meltano, etc.), or have you found success building your own pipelines using the Web API connector in a Dataflow?
Any insights, experiences, or recommendations you could share would be hugely appreciated!
Thanks in advance.
Solved! Go to Solution.
Hi @Kletzy,
Thanks for the detailed and thoughtful question this is a great topic, especially as more teams start to adopt Microsoft Fabric as their central data platform.
Workaround for Airbyte to Fabric: While Airbyte currently does not support Microsoft Fabric directly as a destination, a common workaround is:
Using Airbyte Connectors: Airbyte supports Facebook and Google Ads out-of-the-box. LinkedIn may require a custom connector, but the community has examples. You can still follow the Blob Storage to Fabric pattern above.
Dataflow Gen2 + Web API: You can also build direct pipelines using the Web API connector in Dataflow Gen2, which allows you to authenticate and pull from:
This approach is cost-effective (no licensing) and highly customizable.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.
Hi @Kletzy,
Thanks for the detailed and thoughtful question this is a great topic, especially as more teams start to adopt Microsoft Fabric as their central data platform.
Workaround for Airbyte to Fabric: While Airbyte currently does not support Microsoft Fabric directly as a destination, a common workaround is:
Using Airbyte Connectors: Airbyte supports Facebook and Google Ads out-of-the-box. LinkedIn may require a custom connector, but the community has examples. You can still follow the Blob Storage to Fabric pattern above.
Dataflow Gen2 + Web API: You can also build direct pipelines using the Web API connector in Dataflow Gen2, which allows you to authenticate and pull from:
This approach is cost-effective (no licensing) and highly customizable.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.
Hi @Kletzy,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.
Thank you.
Thanks for the reply @v-kpoloju-msft - that is exactly the same pattern I ended up with following my research, it gives me comfort to know it actually works.
User | Count |
---|---|
16 | |
4 | |
3 | |
3 | |
2 |