You've heard about Microsoft Fabric, and you're ready to take it for a spin? Excellent, let's get us started off in those few advertised minutes! But hold on .. you need a capacity to actually use something, and might not be completely clear on what it actually entails? You're not alone with these questions, and it is perfectly fine to stop and think about it for a while. In fact, it's a good thing you want to understand the single most core concept of Fabric as that will hopefully allow you to make better decisions down the road.

The introduction of Fabric Capacities sparked a lot of questions with Data Architects, Engineers, and Analysts coming from an IaaS or Paas (Infrastructure or Platform as a Service) way of working. Microsoft Fabric is presented as an all-in-one Analytics SaaS (Software as a Service) solution, with a unified measure for Compute and Storage. Great, promising to make the cost and performance predictability a lot simpler. Great! But what exactly does that mean, and what will it actually cost the company?

To understand Fabric Capacities, we need to briefly look at the architecture and what exactly those unified measures look like, including how they are similar, yet different from the existing Power BI Premium Capacities. Understanding the different types and sizes of capacities will help us make the right decisions for our Data Platform solutions in the organization.

But then, how do you manage those capacities and assess if they are in a healthy state? What are some of the options to follow the demands and needs of your business users to allocate the right resources to them? Most importantly, what options do I have to automate the majority of these tasks?

Walking out of the session, you should understand the key concept of Fabric Capacities and how they are at the core of everything you'll do in Microsoft Fabric, be able to choose the one that is right for you, periodically assess if the choice was right, and act where needed.