Also called an experience: a Fabric toolset aimed at one job role, e.g. Data Factory, Data Engineering, Data Warehouse, Real-Time Intelligence or Power BI. Each keeps its data in OneLake.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Workload in context, with comparison tables and the common traps.
Terms in this definition
- Job
A sequence of steps executed together on one agent or runner, or on the server for agentless work. While running, each occupies one of your parallel jobs.
- Role
How an actor normally or expectedly behaves, or the part a person takes in a process. A single actor may hold more than one role.
- Azure Data Factory
Managed data integration service for ETL and ELT, built from pipelines, copy activities, triggers, mapping data flows and integration runtimes. It works in batches rather than routing individual transactions.
- Data warehouse
Built for analysis instead of transaction processing, this relational store usually links facts to dimensions using a snowflake or star layout. Microsoft's present offering is Fabric Warehouse.
- Real-Time Intelligence
Microsoft Fabric's workload for data in motion. Using eventstreams, eventhouses with KQL databases, the Real-Time hub, Real-Time Dashboards and Activator, it takes in events, processes, stores and analyses them, and acts on them.
- Power BI
Microsoft's analytics and reporting service. It reaches data held on-premises through the on-premises data gateway.
- OneLake
Built on Azure Data Lake Storage Gen2, it is the one logical data lake for an entire Microsoft Fabric tenant, provisioned automatically, and the place where every Fabric workload keeps its data.
Related terms
- AI landing zone
There is no distinct AI landing zone to build. According to the Azure landing zone FAQ, AI workloads simply go into normal workload landing zones beneath the platform you already have.
- Allowed storage account SKUs
A built-in Azure Policy that limits the SKUs people may pick for a new storage account. It keeps redundancy and spending in check when a workload has no need for the pricier options.
- Architecture decision record
A running log of the significant architectural choices made for a workload, recording for each one the context, the alternatives weighed, what was decided, the trade-offs and its status. Entries are never edited: if a decision changes, a fresh record is added that supersedes the earlier one.
- Automatic index management
Lets the database add and remove indexes by itself to match the workload, through the
CREATE_INDEXandDROP_INDEXautomatic tuning options. You'll only find it in SQL database in Fabric and Azure SQL Database. - Azure Architecture Center
Microsoft's online library of Azure architecture: reference designs, solution ideas and design guides, all on Microsoft Learn. It's also where you'll find the deployment options for landing zones and accelerators for workload landing zones.
- Azure landing zone
The architecture Microsoft recommends for running a multi-subscription Azure environment that is governed, secure and able to scale. It consists of a single platform landing zone plus workload landing zones operating inside the guardrails it provides.
- Azure NAT Gateway
Gives every resource in a subnet a managed way out to the internet through one or more fixed public IP addresses, while accepting no unsolicited inbound connections. Azure Container Apps can use it only when the environment is a workload profiles one.
- Azure Well-Architected Framework
A set of Microsoft design guidance aimed at raising the quality of a workload. Its five pillars cover reliability, security, cost optimisation, operational excellence and the efficiency of performance.