<?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: How stable is the Data Engineering experience in Microsoft Fabric going forward? in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4901601#M14059</link>
    <description>&lt;P&gt;From everything Microsoft has published and communicated so far, Data Engineering in Microsoft Fabric is not a temporary experiment — it’s a core, strategic part of the platform and is expected to remain so going forward.Microsoft’s Fabric roadmap explicitly lists Data Engineering features (like Spark enhancements, data functions, connectors, integrations, and more) under active planning and development. While exact release dates can shift, the continued listing signals ongoing investment, not deprecation.If you're coming from a Power BI background, it's a great time to start exploring these tools. They open up new capabilities like scalable data transformation, lakehouse modeling, and deeper integration with Fabric's unified analytics stack.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Dec 2025 01:21:34 GMT</pubDate>
    <dc:creator>ssrithar</dc:creator>
    <dc:date>2025-12-15T01:21:34Z</dc:date>
    <item>
      <title>How stable is the Data Engineering experience in Microsoft Fabric going forward?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4901479#M14058</link>
      <description>&lt;P&gt;Hi everyone!&lt;/P&gt;&lt;P&gt;I’m starting to explore the Data Engineering features in Microsoft Fabric, and I wanted to better understand how stable and future-proof this area is.&lt;/P&gt;&lt;P&gt;With Fabric evolving so quickly, I was wondering if there’s any official guidance from Microsoft about the long-term direction of Data Engineering (Lakehouses, pipelines, notebooks, etc.).&lt;/P&gt;&lt;P&gt;Is this expected to remain a core and actively developed part of Fabric?&lt;BR /&gt;And for someone coming from a Power BI background, does it make sense to start investing time in these tools now?&lt;/P&gt;&lt;P&gt;Any insights, official references, or real-world experiences would be really helpful.&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Sun, 14 Dec 2025 16:54:50 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4901479#M14058</guid>
      <dc:creator>SavioFerraz</dc:creator>
      <dc:date>2025-12-14T16:54:50Z</dc:date>
    </item>
    <item>
      <title>Re: How stable is the Data Engineering experience in Microsoft Fabric going forward?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4901601#M14059</link>
      <description>&lt;P&gt;From everything Microsoft has published and communicated so far, Data Engineering in Microsoft Fabric is not a temporary experiment — it’s a core, strategic part of the platform and is expected to remain so going forward.Microsoft’s Fabric roadmap explicitly lists Data Engineering features (like Spark enhancements, data functions, connectors, integrations, and more) under active planning and development. While exact release dates can shift, the continued listing signals ongoing investment, not deprecation.If you're coming from a Power BI background, it's a great time to start exploring these tools. They open up new capabilities like scalable data transformation, lakehouse modeling, and deeper integration with Fabric's unified analytics stack.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 01:21:34 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4901601#M14059</guid>
      <dc:creator>ssrithar</dc:creator>
      <dc:date>2025-12-15T01:21:34Z</dc:date>
    </item>
    <item>
      <title>Re: How stable is the Data Engineering experience in Microsoft Fabric going forward?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4902324#M14079</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/1396709"&gt;@SavioFerraz&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pipelines, Notebooks, and Lakehouses have not materially changed too much since the release of Fabric. More features have been added, but I can't recall any changes that broke existing content (unless they were relying on preview features, never do that in prod).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There have been some changes that require some updates if you want to modify the old pipeline, but they did not break what was already running.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe that investing in these tools is a very good thing to do, it unlocks a lot of power behind Power BI.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once you get into these tools, you can start playing with translyticial task flows, you can have reports with real time data in them, and so much more.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 14:47:33 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/How-stable-is-the-Data-Engineering-experience-in-Microsoft/m-p/4902324#M14079</guid>
      <dc:creator>tayloramy</dc:creator>
      <dc:date>2025-12-15T14:47:33Z</dc:date>
    </item>
  </channel>
</rss>

