<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Evolving the ADF to Fabric migration experience in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/Evolving-the-ADF-to-Fabric-migration-experience/m-p/5144111#M9295</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="781788" data-lia-user-login="arabalca" class="lia-mention lia-mention-user"&gt;arabalca&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That’s a great perspective, thank you for sharing it.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;The current ADF to Fabric migration experience is already a positive step, helping teams transition more smoothly. Your suggestion for deeper integration—such as executing assets directly from Fabric and aligning consumption with Fabric capacity, is very logical.&lt;/P&gt;
&lt;P&gt;Additionally, offering flexibility in cost allocation between Azure and Fabric is practical, especially for organizations gradually adopting Fabric.&lt;/P&gt;
&lt;P&gt;I appreciate you sharing this idea with the community, and I’ve supported it.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Apr 2026 10:23:26 GMT</pubDate>
    <dc:creator>v-sgandrathi</dc:creator>
    <dc:date>2026-04-06T10:23:26Z</dc:date>
    <item>
      <title>Evolving the ADF to Fabric migration experience</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Evolving-the-ADF-to-Fabric-migration-experience/m-p/5144082#M9294</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;When working with Azure Data Factory and moving into Microsoft Fabric, the new “migration” experience is a really interesting step forward. It helps bring both worlds closer and makes the transition smoother.&lt;/P&gt;&lt;P&gt;After trying it out, I’ve seen that it opens up a lot of possibilities, and it’s great to see that we can also propose ideas to continue improving it.&lt;/P&gt;&lt;P&gt;In this context, I’ve shared an idea that I believe could bring even more value.&lt;/P&gt;&lt;P&gt;Right now, the experience allows you to connect and integrate existing ADF assets into Fabric, which is very helpful to start working within the ecosystem. As a next step, it could be interesting to move towards a deeper integration where:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Assets are fully integrated into Fabric&lt;/LI&gt;&lt;LI&gt;They are executed from Fabric&lt;/LI&gt;&lt;LI&gt;And their consumption can be associated with Fabric capacity&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Additionally, it could be valuable to give customers the flexibility to choose where the cost is allocated (Fabric or Azure), enabling a more gradual adoption.&lt;/P&gt;&lt;P&gt;This is a small evolution on top of what already exists, but it could make a big difference in how the experience aligns with different adoption scenarios.&lt;/P&gt;&lt;P&gt;If this idea resonates with you, you can vote for it here:&amp;nbsp;&amp;nbsp;&lt;A href="https://lnkd.in/ejT9QSRj" target="_self"&gt;https://lnkd.in/ejT9QSRj&lt;/A&gt;&lt;/P&gt;&lt;P&gt;And if you find it useful, I would really appreciate your support with a like on the comment and voting for the idea.&lt;/P&gt;&lt;P&gt;This helps increase visibility and gives it a better chance to evolve.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2026 09:10:50 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Evolving-the-ADF-to-Fabric-migration-experience/m-p/5144082#M9294</guid>
      <dc:creator>arabalca</dc:creator>
      <dc:date>2026-04-06T09:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: Evolving the ADF to Fabric migration experience</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Evolving-the-ADF-to-Fabric-migration-experience/m-p/5144111#M9295</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="781788" data-lia-user-login="arabalca" class="lia-mention lia-mention-user"&gt;arabalca&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That’s a great perspective, thank you for sharing it.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;The current ADF to Fabric migration experience is already a positive step, helping teams transition more smoothly. Your suggestion for deeper integration—such as executing assets directly from Fabric and aligning consumption with Fabric capacity, is very logical.&lt;/P&gt;
&lt;P&gt;Additionally, offering flexibility in cost allocation between Azure and Fabric is practical, especially for organizations gradually adopting Fabric.&lt;/P&gt;
&lt;P&gt;I appreciate you sharing this idea with the community, and I’ve supported it.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2026 10:23:26 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Evolving-the-ADF-to-Fabric-migration-experience/m-p/5144111#M9295</guid>
      <dc:creator>v-sgandrathi</dc:creator>
      <dc:date>2026-04-06T10:23:26Z</dc:date>
    </item>
  </channel>
</rss>

