Introduction

Microsoft Fabric is like an all-in-one toolbox for crunching numbers and making sense of data. It's got a bunch of tools, like moving data around, storing it in lakes, doing engineering work on it, mixing it together, using it for science stuff, keeping an eye on it in real-time, and helping you make smart business decisions. And the best part is it's got a strong foundation that makes sure your data is safe, plays by the rules, and follows all the important guidelines. In this article, we will learn how to create a data pipeline to copy data from the Azure blog and ingest it into a Lakehouse in Microsoft Fabric. Let’s get started.

Azure Blob to Lakehouse Data Pipeline in Microsoft Fabric

The first thing we want to do is to create a workplace that is typical of a container or organizing structure that allows us to collaborate on and manage content, such as reports, dashboards, datasets, and more.

To create the workspace, click on Workspaces and Click on New Workspace.

Provide a name for the workspace. In this article, DataPipelineFromAzureBlob is given.

In the Account name or URL of the Connection Settings, we provided the following.

https://azuresynapsestorage.blob.core.windows.net/sampledata/

In the Connection credentials tab, select Create a new connection in the dropdown for the Connection.

To access the .parquet files in https://azuresynapsestorage.blob.core.windows.net/sampledata/WideWorldImportersDW/parquet/full/dimension_city/*.parquet.

In the File path text boxes, we provided the following.

In Table Name, select New and provide BlogCustomerInformation (you can choose whatever name you want).

CustomerInformation

table

In the screenshot below, we can see that the data pipeline was successful.

 data pipeline

Next, we need to check the data in the DataPipelineFromAzureBlog workspace we created initially. Click on the workspace.

In the screenshot below, we have the CustomerData in the Lakehouse and the SQL endpoint.

SQL endpoint

When we click on the CustomerData with the SQL endpoint, we can begin to write queries against the data.

In the screenshot below, we executed a query, and everything is working fine.

CustomerData with the SQL endpoint