Azure Data Basics

If your company runs on Microsoft, you have almost certainly heard a string of Azure names thrown around — Data Factory, Synapse, Fabric, Databricks, Power BI — usually in the same breath and rarely explained. Azure is simply Microsoft’s cloud: a huge collection of computers and storage you rent by the hour instead of buying and running yourself. The services on top of it are the named tools that store, move, crunch and display data. Here is what each one actually does, without the jargon.

Where the data sits: storage accounts

At the bottom of almost everything is an Azure Storage account. Think of it as a giant, secure hard drive in Microsoft’s cloud — the place where raw files, exports, logs and the data lake itself physically live. It is cheap, vast, and not something people open directly. It is the warehouse floor, not the shop window. Almost every other service reaches into storage to read or write data.

Moving and orchestrating: Data Factory

Azure Data Factory is the conductor of the pipelines. It is the service that schedules and runs the jobs that pull data from one place, move it to another, and trigger the cleaning steps — the overnight refresh you read about earlier is very often Data Factory at work. It does not analyse anything itself; its talent is reliably moving and coordinating data on time, every time.

Organising and querying: Synapse and Fabric

Azure Synapse Analytics is a platform for bringing big piles of data together and running large queries against them — essentially a powerful, cloud-scale data warehouse with analytics built in. Microsoft Fabric is the newer, all-in-one offering that bundles storage, pipelines, warehousing and reporting into a single tidy package, with a shared store at its heart called OneLake. In plain terms: Synapse is the established engine room; Fabric is Microsoft pulling the whole toolkit under one roof so teams juggle fewer separate products.

You do not need to know which service did the work. You just need to know roughly what kind of work each one does.

The heavy lifting: Databricks

Azure Databricks is built for the seriously heavy jobs — processing enormous volumes of data and powering data-science and machine-learning work. When a team needs to crunch billions of rows or train a model, Databricks is often where that happens. It is the industrial mixer rather than the kitchen whisk: overkill for a small report, invaluable for genuinely large workloads.

The shop window: Power BI

Power BI is the one most non-technical people actually touch. It is Microsoft’s reporting and dashboard tool — the place where all that stored, moved and crunched data finally turns into charts, KPIs and interactive reports you can click through. When a leader says “send me the dashboard,” they almost always mean a Power BI report. Everything upstream exists so that Power BI has clean, trustworthy numbers to display.

How it all connects

Picture the flow left to right. Raw data lands in a Storage account. Data Factory moves and schedules it. Synapse or Fabric organises it into something query-friendly. Databricks handles the truly heavy crunching when needed. And Power BI presents the finished result to people. Not every company uses every piece, and the names shift as Microsoft rebrands — but the jobs stay the same: store, move, organise, crunch, show.

Spot it: Azure services

Read each situation and decide for yourself, then tap a card to flip it and check your answer.

Sort the Azure services

Drag each item into the bucket it belongs to — or tap an item, then tap a bucket. Hit Check placement when you’re done.

How to use it

The goal is fluency, not expertise. In your next data conversation, try: “Is that refresh running through Data Factory?” or “Are we moving toward Fabric, or staying on Synapse?” or “Can the team publish that as a Power BI dashboard so the whole team can see it?” If a name is unfamiliar, ask which of the five jobs it does — store, move, organise, crunch, or show. That single question will place almost any Azure service for you and keep you firmly in the discussion rather than nodding along.