<?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>Data Factory Community Blog articles</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/bg-p/df_blog</link>
    <description>Data Factory Community Blog articles</description>
    <pubDate>Wed, 18 Nov 2026 02:28:32 GMT</pubDate>
    <dc:creator>df_blog</dc:creator>
    <dc:date>2026-11-18T02:28:32Z</dc:date>
    <item>
      <title>Who Actually Runs Your Microsoft Fabric Data Pipelines?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Who-Actually-Runs-Your-Microsoft-Fabric-Data-Pipelines/ba-p/5419638</link>
      <description>&lt;P&gt;Identities involved with Fabric data pipelines might look simple at first, but there's more than meets the eye.&lt;/P&gt;&lt;P&gt;Pipelines have an owner, and an identity is tied to connections used to interact with other objects. When a pipeline run is triggered, you can also see who it was submitted by. But arguably the most impactful one is often overlooked - and that's the last modifier. Troubleshooting access or token-related errors can get confusing real fast if you don't take that into account.&lt;/P&gt;&lt;P&gt;This article covers common misconceptions and issues related to identities used during pipeline runs. I'll also explain what part each one plays in the grand scheme of things.&lt;/P&gt;&lt;H2&gt;The identities behind every pipeline run&lt;/H2&gt;&lt;P&gt;Before we explore where identities show up, let's briefly cover what an identity is, and what types of identities are available.&lt;/P&gt;&lt;P&gt;An identity is the key piece of access control. When anything is done in Fabric, the question "who is trying to do this" is always asked first - followed by "are they allowed to do this". This means an identity is always present when anything happens on the platform.&lt;/P&gt;&lt;P&gt;The most common one is the user identity. As you might expect, a user identity is tied to a specific user. When you take an action through the UI, such as creating an item or triggering a pipeline, your own user identity is used. It's simple to use, but a governance nightmare when used in production.&lt;/P&gt;&lt;P&gt;A service principal is a popular option to use instead. It is a non-human identity tied to an app registration in Microsoft Entra ID. Client ID and client secret are used to either set up a connection in Fabric or to fetch an access token to use for an API call. Service principals are the most common option for automated processes.&lt;/P&gt;&lt;P&gt;Workspace identities are managed identities tied to their respective workspaces. Creating a workspace identity can be done in workspace settings with just a couple of clicks. Using it is easy as there's no need to manage any credentials. Although handy, they're not that broadly supported yet, and have their own challenges.&lt;/P&gt;&lt;H2&gt;Where identities show up with pipelines&lt;/H2&gt;&lt;P&gt;&lt;STRONG&gt;Item owner&lt;/STRONG&gt; is the name visible in the workspace UI's owner column. By default, this is the identity that was used to create the pipeline item. Creating or deploying something through the UI will set the user as the owner. Using APIs with service principal tokens for item creation allows that service principal to become the owner. At this time, taking over ownership after an item is created is only possible through the UI, and only for the user identity that's doing the action.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;Owner as seen in the workspace UI.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Connections&lt;/STRONG&gt; store an identity. Supported identity types vary between different connection types. Fabric Data Pipeline connections currently support all three identity types presented above. Rights to use a connection can be shared without granting the user direct access to the underlying resources. They can still access those resources through the connection using its configured identity.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;Example settings for a Fabric data pipeline connection using a service principal.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Submitted by&lt;/STRONG&gt; is the identity that was used to submit the pipeline or notebook run. It can be seen in the monitoring view. When you trigger a pipeline manually, you'll see your name. When a connection is used to invoke a pipeline or a notebook, you'll see the identity the connection uses. There's more to this, but that will be covered later.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;Monitoring UI after the user has triggered a pipeline run.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Last modifier&lt;/STRONG&gt; is unsurprisingly the last identity to update the pipeline. This one can most easily be found in the pipeline settings. Modifying and saving the pipeline contents or even simply updating the description in the pipeline settings will change the last modified by identity.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;Last modifier can be found in the pipeline settings. In this example, the last modifier is a service principal.&lt;/P&gt;&lt;H2&gt;How identities flow through a pipeline run&lt;/H2&gt;&lt;P&gt;Now that we've introduced the building blocks, it's time to see how all this works in practice. I believe the best way to do so is through a simple example solution.&lt;/P&gt;&lt;P&gt;The items will stay the same throughout all examples, but identities and scenarios will change. In the solution, we have a data pipeline called Pipeline1. Pipeline1 is invoking another pipeline called Pipeline2. Pipeline2 contains a notebook activity that runs a notebook called Notebook1.&lt;/P&gt;&lt;P&gt;No connection is configured for the Notebook1 activity in any of the examples. Pipeline1 will always be triggered manually by the user. This is the same as if the user had scheduled the pipeline run.&lt;/P&gt;&lt;P&gt;The review of scenario one will also explain different access boundaries. The following scenarios will only focus on what changes.&lt;/P&gt;&lt;H3&gt;Scenario 1: The initial setup&lt;/H3&gt;&lt;P&gt;We're just starting out in a new environment. Developer1 creates all three items through the UI. He sets up a pipeline connection that uses a service principal. The connection is used to invoke Pipeline2. Developer1 triggers the pipeline manually.&lt;/P&gt;&lt;P&gt;Here's the identity flow:&lt;/P&gt;&lt;img /&gt;&lt;P&gt;You might already see something surprising. Why is the notebook in Pipeline2 submitted by Developer1? Sure, Developer1 is very involved with all the items, but there's only one identity slot that actually matters here. It's the last modifier of Pipeline2. The identity that last modified a pipeline is the identity used for the pipeline session.&lt;/P&gt;&lt;P&gt;Let's go through the access boundaries:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;To trigger Pipeline1, Developer1 needs to be a Contributor or higher in the workspace.&lt;/LI&gt;&lt;LI&gt;To invoke Pipeline2 using the connection, Developer1 needs to be a User or higher on the connection.&lt;/LI&gt;&lt;LI&gt;To run Pipeline2, the service principal used for the pipeline connection needs to be a Contributor or higher in the workspace.&lt;/LI&gt;&lt;LI&gt;To start the pipeline session for Pipeline2, Developer1, as the last modifier, needs to be a Contributor or higher in the workspace.&lt;/LI&gt;&lt;LI&gt;To run the notebook, Developer1, as the last modifier of Pipeline2, needs to be a Contributor or higher in the workspace.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;At least for me, everything starts simple, but quickly heads into unexpected territory. Suddenly it appears that the last modified by identity has a lot more impact than one would assume. Temporarily deactivating an activity for debugging has the power to break your pipeline runs in the future.&lt;/P&gt;&lt;P&gt;But how does that happen? Let's keep working on our scenario.&lt;/P&gt;&lt;H3&gt;Scenario 2: A small change&lt;/H3&gt;&lt;P&gt;Our pipeline has been successfully running for a few weeks now. Enter Developer2. Developer2 notices a typo in Pipeline2's description and fixes it. Everything keeps working perfectly.&lt;/P&gt;&lt;P&gt;Here's the identity flow:&lt;/P&gt;&lt;img /&gt;&lt;P&gt;As we can see, both the last modified by identity for Pipeline2 and the submitted by identity for Notebook1 have changed.&lt;/P&gt;&lt;P&gt;What this means is that compared to the prior setup, Developer2 is now the one who needs access to start Pipeline2's session and run Notebook1. If we are fetching user-specific tokens in Notebook1, those will now represent the identity of Developer2 instead of Developer1.&lt;/P&gt;&lt;P&gt;But everything's still good, right? Sure, for now. Let's keep going.&lt;/P&gt;&lt;H3&gt;Scenario 3: Developer2 leaves&lt;/H3&gt;&lt;P&gt;More time passes. Developer2 leaves the company, and their account is deleted. After a while, Pipeline1 starts failing as Pipeline2 is not starting at all. The interesting part is that the error happens before a job for Pipeline2 is created, so you might think the problem is in the connection between Pipeline1 and Pipeline2. But that's not the case.&lt;/P&gt;&lt;P&gt;The issue is with the stored authentication linked to Developer2 as Pipeline2's last modifier. If that authentication is no longer valid, Fabric can't use it to obtain new access tokens. The next time the pipeline needs to authenticate, it fails.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;To quickly get everything running, Developer1 changes the description for Pipeline2 and saves it. This updates the last modified by identity. Back to Developer1. Everything starts working again.&lt;/P&gt;&lt;P&gt;Technically, we're all good now. But we're still betting on Developer1 not leaving the company or even changing their password. Password changes can also invalidate refresh tokens - which can lead to the same issue&lt;/P&gt;&lt;P&gt;But don't worry, we can make this sustainable.&lt;/P&gt;&lt;H2&gt;How to keep your solutions robust&lt;/H2&gt;&lt;P&gt;The first thing you should do is to handle deployments between environments (dev, test, prod) using service principals. You can do so by either triggering Fabric deployment pipelines &lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment?#option-3---deploy-using-fabric-deployment-pipelines" target="_blank"&gt;through the API&lt;/A&gt; or using the &lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment?#option-2---definition-based-deployments-using-fabric-items-apis" target="_blank"&gt;fabric-cicd&lt;/A&gt; library. Each complete deployment will update the last modified by identity.&lt;/P&gt;&lt;P&gt;This is a good start. But again, if someone has to troubleshoot the deployed pipelines and, for example temporarily deactivate activities, the identity will change. Running the complete deployment process again will fix it, but you might not always want to do that.&lt;/P&gt;&lt;P&gt;Here's a lighter and simpler option you can go with instead.&lt;/P&gt;&lt;P&gt;To update the last modified by identity to be our service principal, we're going to be updating the pipeline through an API. Specifically, we're going to update the pipeline's description metadata field.&lt;/P&gt;&lt;P&gt;First of all, we need to get a token, and for that we need the service principal's credentials. The credentials are safely stored in a key vault.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;Calling the API requires knowing the pipeline's item ID. It can be found as a part of the URL after opening the pipeline.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;After we have the token and the complete endpoint, it's time to send the request.&lt;/P&gt;&lt;img /&gt;&lt;P&gt;It's as simple as that. To scale it up, other APIs and some extra logic can be used. You can get all the pipelines from your current workspace, filter by name and even check which ones are not last updated by the service principal.&lt;/P&gt;&lt;H2&gt;Summary&lt;/H2&gt;&lt;P&gt;Understanding identities and access boundaries is mandatory for efficiently building and maintaining pipelines. Everything might appear simple at first, but it can get confusing real fast. Some errors happen under the hood and can be very hard to troubleshoot. The last modified by identity holds a lot more importance than one would expect.&lt;/P&gt;&lt;P&gt;This post ended up being a bit longer than I first expected, so a huge thank you for taking the time to read it. I hope it helps you make sense of your own pipeline runs.&lt;/P&gt;&lt;P&gt;Originally published on my personal blog &lt;A class="lia-external-url" href="https://www.doformedata.com/microsoft-fabric-pipeline-identities/" target="_blank"&gt;here.&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 17:11:45 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Who-Actually-Runs-Your-Microsoft-Fabric-Data-Pipelines/ba-p/5419638</guid>
      <dc:creator>TeemuMultanen</dc:creator>
      <dc:date>2026-11-16T17:11:45Z</dc:date>
    </item>
    <item>
      <title>Calculate the Number of Days Between Order Date and Ship Date in Fabric Dataflow Gen2</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Calculate-the-Number-of-Days-Between-Order-Date-and-Ship-Date-in/ba-p/5357411</link>
      <description>&lt;P&gt;When working with sales and order data, one of the simplest—and most useful—business questions is:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How many days did it take to ship an order?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;At first glance, this looks like a straightforward subtraction:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Ship Date − Order Date = Shipping Days&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;But when you're working in &lt;STRONG&gt;Microsoft Fabric Dataflow Gen2&lt;/STRONG&gt;, there is a little more to it than simply subtracting two columns.&lt;/P&gt;&lt;P&gt;The good news is that Dataflow Gen2 uses the familiar &lt;STRONG&gt;Power Query&lt;/STRONG&gt; experience, so you can perform this calculation directly during your data transformation process without writing SQL or DAX. Microsoft describes Dataflow Gen2 as a cloud-based data preparation and transformation service built around the Power Query experience.&lt;/P&gt;&lt;P&gt;Let's see how to do it.&lt;/P&gt;&lt;H2&gt;The Business Scenario&lt;/H2&gt;&lt;P&gt;Imagine we have an orders table containing the following columns as seen in the screenshot below:&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;SPAN&gt;The business wants a new column called &lt;/SPAN&gt;&lt;STRONG&gt;Shipping Days&lt;/STRONG&gt;&lt;SPAN&gt;. This calculation can be performed directly inside the Dataflow Gen2 transformation layer.&lt;/SPAN&gt;&lt;/P&gt;&lt;H2&gt;Start with Your Dataflow Gen2&lt;/H2&gt;&lt;P&gt;Open your Microsoft Fabric workspace and create or open a &lt;STRONG&gt;Dataflow Gen2&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Once you're inside the Power Query editor, bring your orders table into the dataflow.&lt;/P&gt;&lt;P&gt;Dataflow Gen2 allows you to connect to a wide range of data sources and transform the data before loading it into destinations such as a Lakehouse or Warehouse.&lt;/P&gt;&lt;P&gt;The first thing I would check is the data type of both date columns.&lt;/P&gt;&lt;H2&gt;Make Sure Both Columns Are Actually Dates&lt;/H2&gt;&lt;P&gt;This is a small step that can save you from a surprisingly frustrating error.&lt;/P&gt;&lt;P&gt;Select OrderDate and confirm that its data type is &lt;STRONG&gt;Date&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Do the same for ShipDate.&lt;/P&gt;&lt;P&gt;You don't want one column to be Date while the other is Text or Date/Time.&lt;/P&gt;&lt;P&gt;Power Query performs date arithmetic based on compatible date and time types. Microsoft notes that subtracting different date/time types—for example, a date from a datetime—can result in an error unless you explicitly convert the values.&lt;/P&gt;&lt;P&gt;So, before doing the calculation:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;OrderDate → Date&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ShipDate → Date&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;As seen in the previous screenshot, the Order Date and the Ship Date columns has date data type&lt;/P&gt;&lt;H1&gt;The Simple Solution&lt;/H1&gt;&lt;P&gt;Now add a &lt;STRONG&gt;Custom Column&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;In the Power Query editor:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Add Column → Custom Column&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Give the new column a name:&lt;/P&gt;&lt;P&gt;ShippingDays&lt;/P&gt;&lt;P&gt;Then enter:&lt;/P&gt;&lt;PRE&gt;[ShipDate] - [OrderDate]&lt;/PRE&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;Dataflow Gen2 allows specifying the desired data type before hitting OK. This is not available in Power Query of Power BI and Excel . For this demonstration, the Whole number data type is selected. Then, click OK&lt;/P&gt;&lt;P&gt;That's it.&lt;/P&gt;&lt;P&gt;Power Query subtracts the two dates and produces the result as seen below:&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;SPAN&gt;What If Your Columns Are Date/Time?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;This is another situation you'll encounter frequently in real projects.&lt;/P&gt;&lt;P&gt;Suppose your data looks like this:&lt;/P&gt;&lt;PRE&gt;OrderDate = 2026-08-01 10:30:00
ShipDate  = 2026-08-03 14:45:00&lt;/PRE&gt;&lt;P&gt;Subtracting them produces a duration that includes both days and time.&lt;/P&gt;&lt;P&gt;If your requirement is to calculate the &lt;STRONG&gt;exact elapsed time&lt;/STRONG&gt;, that's useful.&lt;/P&gt;&lt;P&gt;But if the business question is simply:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;"How many calendar days passed between the order and shipping dates?"&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;you may want to convert both columns to Date first.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;PRE&gt;Date.From([ShipDate]) - Date.From([OrderDate])&lt;/PRE&gt;&lt;P&gt;and then:&lt;/P&gt;&lt;PRE&gt;Duration.Days(
    Date.From([ShipDate]) - Date.From([OrderDate])
)&lt;/PRE&gt;&lt;P&gt;This removes the time component from the calculation.&lt;/P&gt;&lt;H1&gt;What About Missing Dates?&lt;/H1&gt;&lt;P&gt;Real-world data is rarely perfect.&lt;/P&gt;&lt;P&gt;You might have an order like:&lt;/P&gt;&lt;P&gt;Order ID Order Date Ship Date&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;1005&lt;/TD&gt;&lt;TD&gt;08/08/2026&lt;/TD&gt;&lt;TD&gt;null&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;Perhaps the order hasn't shipped yet.&lt;/P&gt;&lt;P&gt;If you blindly calculate the difference, you won't get a meaningful shipping duration.&lt;/P&gt;&lt;P&gt;Instead, you can add some business logic.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;PRE&gt;if [ShipDate] = null then null
else Duration.Days([ShipDate] - [OrderDate])&lt;/PRE&gt;&lt;P&gt;This leaves the Shipping Days value blank until the order has actually shipped.&lt;/P&gt;&lt;P&gt;You could also return a label such as "Not Shipped" depending on the reporting requirement.&lt;/P&gt;&lt;H1&gt;What If the Ship Date Is Earlier Than the Order Date?&lt;/H1&gt;&lt;P&gt;This is another useful data-quality check.&lt;/P&gt;&lt;P&gt;Imagine:&lt;/P&gt;&lt;PRE&gt;Order Date = 10/08/2026
Ship Date  = 08/08/2026&lt;/PRE&gt;&lt;P&gt;The calculation would produce a negative duration.&lt;/P&gt;&lt;P&gt;Technically, that's valid arithmetic. From a business perspective, however, it probably indicates a data-quality problem.&lt;/P&gt;&lt;P&gt;You could identify such records with:&lt;/P&gt;&lt;PRE&gt;if [ShipDate] &amp;lt; [OrderDate] then "Invalid Dates"
else "Valid"&lt;/PRE&gt;&lt;P&gt;Or incorporate the validation directly into your shipping-days calculation.&lt;/P&gt;&lt;P&gt;This is one of the advantages of doing the transformation in Dataflow Gen2: you're not merely calculating a metric; you're also able to clean and validate the data before it reaches downstream reporting.&lt;/P&gt;&lt;H1&gt;Why Calculate This in Dataflow Gen2?&lt;/H1&gt;&lt;P&gt;You might wonder:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why not simply calculate Shipping Days in Power BI using DAX?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You certainly can.&lt;/P&gt;&lt;P&gt;But there is a strong architectural argument for performing the calculation during data preparation when the value is fundamentally a property of the source data.&lt;/P&gt;&lt;P&gt;If ShippingDays is required by multiple reports, calculating it once in the dataflow means downstream consumers don't all need to recreate the same logic.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;PRE&gt;Source System
      ↓
Dataflow Gen2
      ↓
Clean + Transform
      ↓
ShippingDays
      ↓
Lakehouse / Warehouse
      ↓
Power BI Semantic Model
      ↓
Reports&lt;/PRE&gt;&lt;P&gt;Now the transformation becomes part of your reusable data pipeline.&lt;/P&gt;&lt;H1&gt;A More Production-Ready Example&lt;/H1&gt;&lt;P&gt;For a real production dataflow, I might use something like:&lt;/P&gt;&lt;PRE&gt;if [OrderDate] = null or [ShipDate] = null then
    null
else if [ShipDate] &amp;lt; [OrderDate] then
    null
else
    Duration.Days(
        Date.From([ShipDate]) - Date.From([OrderDate])
    )&lt;/PRE&gt;&lt;P&gt;This handles three important scenarios:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Missing Order Date&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Missing Ship Date&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Ship Date earlier than Order Date&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Only valid records receive a shipping duration.&lt;/P&gt;&lt;P&gt;You can then create a separate data-quality flag for the invalid records rather than silently hiding them.&lt;/P&gt;&lt;H1&gt;Turning the Calculation into a Business KPI&lt;/H1&gt;&lt;P&gt;Once you have ShippingDays, you can do much more than display it in a table.&lt;/P&gt;&lt;P&gt;For example, the business could define:&lt;/P&gt;&lt;PRE&gt;0–2 days   → Fast
3–5 days   → Standard
6+ days    → Delayed&lt;/PRE&gt;&lt;P&gt;That allows Power BI to answer questions such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;What is our average shipping time?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Which customers experience the longest delays?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Which products take the longest to ship?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Which warehouses are performing poorly?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;What percentage of orders ship within two days?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Has shipping performance improved over time?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;A simple date subtraction has now become a useful operational metric.&lt;/P&gt;&lt;H1&gt;The Bigger Fabric Lesson&lt;/H1&gt;&lt;P&gt;This small example demonstrates an important principle in Microsoft Fabric:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Transform data as close to the data-engineering layer as practical.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Dataflow Gen2 gives you a low-code environment for ingestion and transformation using Power Query, while allowing the resulting data to be loaded into Fabric destinations for downstream analytics.&lt;/P&gt;&lt;P&gt;Instead of repeatedly calculating the same business logic inside individual Power BI reports, you can create a reusable transformation once and make the resulting column available to multiple consumers.&lt;/P&gt;&lt;P&gt;And because Dataflow Gen2 is part of the broader Fabric ecosystem, the transformation can become one stage of a much larger data platform.&lt;/P&gt;&lt;H1&gt;&amp;nbsp;&lt;/H1&gt;&lt;P&gt;In conclusion, calculating the number of days between Order Date and Ship Date in Dataflow Gen2 is straightforward once you understand how Power Query handles dates.&lt;/P&gt;&lt;P&gt;The key expression is:&lt;/P&gt;&lt;PRE&gt;Duration.Days([ShipDate] - [OrderDate])&lt;/PRE&gt;&lt;P&gt;But the real lesson goes beyond the formula.&lt;/P&gt;&lt;P&gt;Always check your data types, handle missing values, validate unexpected dates, and decide whether the calculation belongs in the transformation layer or the semantic model.&lt;/P&gt;&lt;P&gt;Sometimes a two-line Power Query expression is all you need to turn raw operational data into a useful business metric.&lt;/P&gt;&lt;P&gt;And that's one of the things I like about Microsoft Fabric—simple transformations can become reusable building blocks in a much larger analytics architecture.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Aug 2026 13:47:42 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Calculate-the-Number-of-Days-Between-Order-Date-and-Ship-Date-in/ba-p/5357411</guid>
      <dc:creator>abiola_david</dc:creator>
      <dc:date>2026-08-11T13:47:42Z</dc:date>
    </item>
    <item>
      <title>Orchestration Tool Selection in Microsoft Fabric Data Factory</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Orchestration-Tool-Selection-in-Microsoft-Fabric-Data-Factory/ba-p/5305609</link>
      <description>&lt;P&gt;&lt;img /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jul 2026 14:09:41 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Orchestration-Tool-Selection-in-Microsoft-Fabric-Data-Factory/ba-p/5305609</guid>
      <dc:creator>Ilgar_Zarbali</dc:creator>
      <dc:date>2026-07-20T14:09:41Z</dc:date>
    </item>
    <item>
      <title>Building Your First Pipeline in Microsoft Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Building-Your-First-Pipeline-in-Microsoft-Fabric/ba-p/5221289</link>
      <description>&lt;P&gt;&lt;img /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 14:10:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Building-Your-First-Pipeline-in-Microsoft-Fabric/ba-p/5221289</guid>
      <dc:creator>Ilgar_Zarbali</dc:creator>
      <dc:date>2026-06-22T14:10:35Z</dc:date>
    </item>
    <item>
      <title>Creating Azure Data Lake Storage (ADLS) in Azure: A Step-by-Step Guide</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Creating-Azure-Data-Lake-Storage-ADLS-in-Azure-A-Step-by-Step/ba-p/5177108</link>
      <description>&lt;P&gt;&lt;img /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2026 13:57:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Creating-Azure-Data-Lake-Storage-ADLS-in-Azure-A-Step-by-Step/ba-p/5177108</guid>
      <dc:creator>Ilgar_Zarbali</dc:creator>
      <dc:date>2026-05-04T13:57:49Z</dc:date>
    </item>
    <item>
      <title>Site to Insight: Fabric’s New SharePoint Picker</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Site-to-Insight-Fabric-s-New-SharePoint-Picker/ba-p/5155347</link>
      <description>&lt;P&gt;One of the greatest things about attending&amp;nbsp;&lt;STRONG&gt;FABCON in Atlanta&lt;/STRONG&gt;&amp;nbsp;recently wasn’t just the incredible community or the deep-dive sessions – it was those “aha!” moments during the keynote announcements. Among the many massive reveals, there was one specific update that caught my attention as a massive “quality of life” win: the&amp;nbsp;&lt;STRONG&gt;SharePoint Site Picker (Preview).&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;For anyone who works between SharePoint and Fabric daily, this was easily one of my favourite announcements of the conference. Here’s why it’s a gamechanger.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 13:55:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Site-to-Insight-Fabric-s-New-SharePoint-Picker/ba-p/5155347</guid>
      <dc:creator>Pragati11</dc:creator>
      <dc:date>2026-04-21T13:55:22Z</dc:date>
    </item>
    <item>
      <title>SAP Mirroring in Microsoft Fabric with SAP Datasphere How to - Part 1 SAP</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/SAP-Mirroring-in-Microsoft-Fabric-with-SAP-Datasphere-How-to/ba-p/5132247</link>
      <description>&lt;DIV style="font-size: 14px; line-height: 20px;"&gt;
&lt;P&gt;In this article, I walk through the complete process of replicating data from an SAP S/4HANA system into Microsoft Fabric.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Part 1&lt;/STRONG&gt; focuses entirely on the SAP landscape. This includes the installation and configuration of the SAP Cloud Connector, the setup of the connection to SAP Datasphere, and the integration of all required internal SAP resources. In addition, the necessary prerequisites are described to ensure that the SAP environment is fully prepared for data replication.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Part 2&lt;/STRONG&gt; continues with the configuration inside SAP Datasphere, where the source and target systems are connected and the replication flow is created. After completing the SAP-side setup, Part 2 then transitions into Microsoft Fabric, showing how the replicated SAP data is connected, stored, and made available through Azure Data Lake Storage Gen2 and the Mirrored SAP Database. This results in a complete end-to-end pipeline bringing SAP data reliably into Microsoft Fabric for analytics and reporting.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here you can direct go the &lt;STRONG&gt;Part 2.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;A href="https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/SAP-Mirroring-in-Microsoft-Fabric-with-SAP-Datasphere-How-to/ba-p/5138853"&gt;https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/SAP-Mirroring-in-Microsoft-Fabric-with-SAP-Datasphere-How-to/ba-p/5138853&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also you can read the full Blog Article on my own Blog Site.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://renefuerstenberg.de/microsoftfabric/sap-mirroring-in-microsoft-fabric-with-sap-datasphere-step-by-step-guide/#more-1209"&gt;https://renefuerstenberg.de/microsoftfabric/sap-mirroring-in-microsoft-fabric-with-sap-datasphere-step-by-step-guide/#more-1209&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 30 Mar 2026 14:15:56 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/SAP-Mirroring-in-Microsoft-Fabric-with-SAP-Datasphere-How-to/ba-p/5132247</guid>
      <dc:creator>spaceman127</dc:creator>
      <dc:date>2026-03-30T14:15:56Z</dc:date>
    </item>
    <item>
      <title>Incremental Loading in Fabric Pipelines: Warehouse to Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Incremental-Loading-in-Fabric-Pipelines-Warehouse-to-Lakehouse/ba-p/4883314</link>
      <description>&lt;P&gt;If you are working with large fact tables in Fabric, loading everything on every run quickly becomes slow and costly. Incremental loading fixes that by moving only the new records since the last pipeline run, and the watermark pattern makes this easy to manage. In this walkthrough, you will see how to set up a simple watermark table, build a stored procedure, and wire up a Fabric pipeline that reads the last load timestamp, fetches the latest data from FactImport, copies only the delta, and updates the watermark for the next run. It is a straightforward pattern that keeps your Warehouse and Lakehouse in sync without wasting compute or time.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 14:57:16 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Incremental-Loading-in-Fabric-Pipelines-Warehouse-to-Lakehouse/ba-p/4883314</guid>
      <dc:creator>Shubham_rai955</dc:creator>
      <dc:date>2025-11-25T14:57:16Z</dc:date>
    </item>
    <item>
      <title>Power Query: Table.TransformColumnTypes Now Supports MissingField</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Power-Query-Table-TransformColumnTypes-Now-Supports-MissingField/ba-p/4827416</link>
      <description>&lt;P&gt;Power Query’s &lt;CODE data-start="161" data-end="189"&gt;Table.TransformColumnTypes&lt;/CODE&gt; has long supported a Culture tag as an optional third parameter. As of May 2025, it now goes further: you can pass an Options record that includes both Culture and &lt;CODE data-start="354" data-end="368"&gt;MissingField&lt;/CODE&gt;. This makes it the only M function where &lt;CODE data-start="410" data-end="424"&gt;MissingField&lt;/CODE&gt; lives inside the Options record, bringing new flexibility and fewer errors.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 03:24:16 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Power-Query-Table-TransformColumnTypes-Now-Supports-MissingField/ba-p/4827416</guid>
      <dc:creator>m_dekorte</dc:creator>
      <dc:date>2025-09-22T03:24:16Z</dc:date>
    </item>
    <item>
      <title>Anonymously Query Public Google Drives (Fast, Refreshes in Service, No Cloud Project)</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Anonymously-Query-Public-Google-Drives-Fast-Refreshes-in-Service/ba-p/4807585</link>
      <description>&lt;P&gt;DISCLAIMER: This method uses the internal&amp;nbsp;takeout-pa.clients6.google.com API and is thus UNSUPPORTED and BRITTLE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a custom function that you can paste into advanced editor and then use to get Public Google Drive contents with just the Drive ID and without needing a) any authentication or b) a Google Cloud Project key.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Aug 2025 15:13:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Anonymously-Query-Public-Google-Drives-Fast-Refreshes-in-Service/ba-p/4807585</guid>
      <dc:creator>MarkLaf</dc:creator>
      <dc:date>2025-08-27T15:13:46Z</dc:date>
    </item>
    <item>
      <title>Why Is Power Query List.Contains Slow? Faster Lookup Alternatives</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Why-Is-Power-Query-List-Contains-Slow-Faster-Lookup-Alternatives/ba-p/4805878</link>
      <description>&lt;P data-unlink="true"&gt;&lt;STRONG&gt;&lt;SPAN&gt;tl;dr&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; List.Contains is slow in Power Query because for each iteration, for example each row in your table you check, it scans the list from the start until it finds a match. Buffering helps so it doesn’t re-evaluate on every iteration, but it still scans each item in the list. A better approach is merging via Table.Join, or best of all (in the right scenario), turn your list into a single record to create a hash map and do near constant-time lookups with &lt;/SPAN&gt;&lt;SPAN&gt;Record.Fi&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN&gt;eldOrDefault.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Aug 2025 16:25:01 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Why-Is-Power-Query-List-Contains-Slow-Faster-Lookup-Alternatives/ba-p/4805878</guid>
      <dc:creator>vojtechsima</dc:creator>
      <dc:date>2025-08-26T16:25:01Z</dc:date>
    </item>
    <item>
      <title>How to Build and Orchestrate a Scalable Data Pipeline in Microsoft Fabric? A Step-by-Step Guide</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/How-to-Build-and-Orchestrate-a-Scalable-Data-Pipeline-in/ba-p/4801197</link>
      <description>&lt;P&gt;&lt;FONT size="5" color="#008000"&gt;&lt;STRONG&gt;How to Build and Orchestrate a Scalable Data Pipeline in Microsoft Fabric? A Step-by-Step Guide&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="4" color="#000000"&gt;&lt;STRONG&gt;In today’s data-driven world, organizations handle massive volumes of information from multiple sources. The challenge is not just storing this data but ensuring it is organized, transformed, and analytics-ready—without manual intervention.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;img /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2025 17:19:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/How-to-Build-and-Orchestrate-a-Scalable-Data-Pipeline-in/ba-p/4801197</guid>
      <dc:creator>suparnababu8</dc:creator>
      <dc:date>2025-08-22T17:19:49Z</dc:date>
    </item>
    <item>
      <title>Auto-Magic Data Ingestion in Microsoft Fabric Lakehouse using Data Activator &amp; Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Auto-Magic-Data-Ingestion-in-Microsoft-Fabric-Lakehouse-using/ba-p/4762011</link>
      <description>&lt;P&gt;&lt;FONT size="5" color="#008000"&gt;&lt;STRONG&gt;Auto-Magic Data Ingestion in Microsoft Fabric Lakehouse using Data Activator &amp;amp; Pipelines&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;Imagine this you drop a .csv file into your &lt;STRONG&gt;Lakehouse&lt;/STRONG&gt;, and within moments - without any manual intervention - it appears as a fully formed&lt;STRONG&gt; Delta Table&lt;/STRONG&gt; in your workspace. No scripts, no button clicks. Just &lt;STRONG&gt;pure automation&lt;/STRONG&gt;.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;img /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 15:28:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Auto-Magic-Data-Ingestion-in-Microsoft-Fabric-Lakehouse-using/ba-p/4762011</guid>
      <dc:creator>suparnababu8</dc:creator>
      <dc:date>2025-08-01T15:28:49Z</dc:date>
    </item>
    <item>
      <title>Set Data Types in Power Query M Without Extra Steps</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Set-Data-Types-in-Power-Query-M-Without-Extra-Steps/ba-p/4761866</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Learn a handy Power BI trick to set column data types directly in the Power Query M formula. This approach avoids adding extra “Changed Type” steps and keeps your queries clean.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 14:22:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Set-Data-Types-in-Power-Query-M-Without-Extra-Steps/ba-p/4761866</guid>
      <dc:creator>uzuntasgokberk</dc:creator>
      <dc:date>2025-07-14T14:22:35Z</dc:date>
    </item>
    <item>
      <title>Send Customized Emails Using Fabric Data Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Send-Customized-Emails-Using-Fabric-Data-Pipelines/ba-p/4737741</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Ever wondered if you can send personalized emails&amp;nbsp;directly&amp;nbsp;from Microsoft Fabric Data pipelines?&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;In my latest blog, I show how I built a simple automation that notifies employees when their weekly working hours fall below a threshold — no Power Automate, no external tools.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;All done within the Fabric ecosystem&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 14:37:38 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Send-Customized-Emails-Using-Fabric-Data-Pipelines/ba-p/4737741</guid>
      <dc:creator>tharunkumarRTK</dc:creator>
      <dc:date>2025-07-01T14:37:38Z</dc:date>
    </item>
    <item>
      <title>Public Parameters Boost the Scalability of Dataflow Gen2</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Public-Parameters-Boost-the-Scalability-of-Dataflow-Gen2/ba-p/4685530</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;!--ScriptorStartFragment--&gt;Public parameters are two small words that substantially boost the versatility and usability of Dataflow Gen2s in Microsoft Fabric for your data orchestrations.&lt;!--ScriptorEndFragment--&gt;&lt;BR /&gt;&lt;!--ScriptorEndFragment--&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 18:28:42 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Public-Parameters-Boost-the-Scalability-of-Dataflow-Gen2/ba-p/4685530</guid>
      <dc:creator>jennratten</dc:creator>
      <dc:date>2025-05-22T18:28:42Z</dc:date>
    </item>
    <item>
      <title>Unlocking the Power of Fabric Data Pipelines: A Guide for Power BI users - Part 1</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Unlocking-the-Power-of-Fabric-Data-Pipelines-A-Guide-for-Power/ba-p/4309927</link>
      <description>&lt;P&gt;&lt;SPAN&gt;In this blog post, we'll explore how you can start using Fabric Data Pipelines as a Power BI user that wants to take full advantage of Microsoft Fabric.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;And if you have never used Power BI before but still want to start with pipelines, you are in the right place!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Dec 2024 14:42:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Unlocking-the-Power-of-Fabric-Data-Pipelines-A-Guide-for-Power/ba-p/4309927</guid>
      <dc:creator>pchristinami</dc:creator>
      <dc:date>2024-12-31T14:42:22Z</dc:date>
    </item>
    <item>
      <title>Data Pipeline Expression Language – Check if field exists, handling non-existent properties</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Data-Pipeline-Expression-Language-Check-if-field-exists-handling/ba-p/4297805</link>
      <description>&lt;P&gt;In this blog we discuss how to use the expression language to handle referencing a field that may or may not exist at runtime, a non-existent property.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 20:21:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Data-Pipeline-Expression-Language-Check-if-field-exists-handling/ba-p/4297805</guid>
      <dc:creator>sean_ms</dc:creator>
      <dc:date>2024-11-22T20:21:22Z</dc:date>
    </item>
    <item>
      <title>Data Pipeline Storage Event Triggers (Preview) - Ignore Empty Files</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Data-Pipeline-Storage-Event-Triggers-Preview-Ignore-Empty-Files/ba-p/4297715</link>
      <description>&lt;P&gt;This short blog details a common scenario we saw in Azure Data Factory where we wanted to ignore zero-byte (empty) files landing in out storage accounts.&amp;nbsp; In this blog we show you how to achieve this functionality with data pipeline storage event triggers (preview) and provide references to the properties and schemas of the event grid topics which will empower you to specify the filters you need to be successful.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:14:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Data-Pipeline-Storage-Event-Triggers-Preview-Ignore-Empty-Files/ba-p/4297715</guid>
      <dc:creator>sean_ms</dc:creator>
      <dc:date>2024-11-22T18:14:06Z</dc:date>
    </item>
    <item>
      <title>Getting On-Premises SQL Server Data to Microsoft Fabric Lakehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Getting-On-Premises-SQL-Server-Data-to-Microsoft-Fabric/ba-p/4289590</link>
      <description>&lt;P&gt;&lt;img /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For the last few days, I have been working on the Contoso Sales data to create a Power BI report as part of the learning. Currently, I am using the default ready to go Power BI data model provided by Microsoft which can be found &lt;A href="https://www.microsoft.com/en-US/download/details.aspx?id=46801" target="_blank" rel="noopener"&gt;here&lt;/A&gt;. As Microsoft Fabric is the new tech buzz, so I thought why don’t I get this data somehow in the Fabric environment.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Nov 2024 01:22:24 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Factory-Community-Blog/Getting-On-Premises-SQL-Server-Data-to-Microsoft-Fabric/ba-p/4289590</guid>
      <dc:creator>Pragati11</dc:creator>
      <dc:date>2024-11-19T01:22:24Z</dc:date>
    </item>
  </channel>
</rss>

