A Practical Guide to Microsoft Fabric Licensing for Schools
Understanding capacity, Power BI Pro, and what actually applies in a school context
Microsoft Fabric introduces a different licensing model to what many schools are used to with Power BI. Instead of licensing analytics per user, Fabric is licensed by capacity, which changes how schools should think about access, costs, and scale.
This guide explains how Fabric licensing works in practice for schools, what decisions you’ll need to make, and the common patterns schools are using today.
1. What does a Microsoft Fabric license actually cover?
Microsoft Fabric is licensed through capacity SKUs. When a school purchases Fabric capacity, it enables a shared analytics platform that includes:
-
OneLake (centralised data storage)
-
Lakehouse and Warehouse (SQL analytics)
-
Data Pipelines and Dataflows Gen2
-
Notebooks (Spark)
-
Semantic models
-
Power BI reporting
-
AI and Copilot capabilities (subject to region and tenant settings)
Rather than assigning licenses to individuals, users consume a shared pool of compute and resources.
This is an important shift for schools that previously licensed Power BI on a per-user basis.
2. Understanding Fabric capacity sizes in a school context
Fabric capacities scale by compute power and concurrency rather than features. The most commonly discussed SKUs in education are:
| Capacity | Typical usage pattern | Considerations for schools |
|---|---|---|
| F2 / F4 | Proof of concept, demos | Limited headroom |
| F8 | Small production workloads | May constrain growth |
| F16 | Core analytics workloads | Often suitable as a baseline |
| F32+ | Large or multi-campus environments | Higher concurrency and scale |
Schools typically evaluate capacity based on:
-
Number of data sources (SIS, LMS, assessments, wellbeing systems)
-
Frequency of data refresh
-
Number of concurrent report viewers
-
Use of Spark, notebooks, or AI workloads
3. Where Fabric fits into typical school analytics workloads
Fabric capacity can support a range of common school use cases, including:
-
Daily ingestion from student administration systems
-
Attendance and wellbeing reporting
-
Academic performance tracking
-
Compliance and statutory reporting
-
Embedded analytics in LMS or portals
-
Long-term data modelling (medallion architecture, Data Vault, star schemas)
The capacity choice determines how much of this can run concurrently and how fast, rather than which features are available.
4. Do schools still need Power BI Pro?
This is one of the most common questions schools ask.
Fabric capacity changes who needs Power BI Pro, but it does not remove it entirely.
Power BI Pro is typically required for:
-
Creating and editing reports
-
Publishing reports and semantic models
-
Managing workspaces
-
Advanced model and dataset management
These activities are usually performed by:
-
Data and analytics staff
-
IT or systems teams
-
A small group of power users
Power BI Pro is typically not required for:
-
Teachers viewing reports
-
School leaders consuming dashboards
-
Students accessing analytics
-
Parents viewing embedded reports
When reports are published in a Fabric capacity workspace, view-only users can access them without individual Pro licenses.
5. Viewing vs creating: the key licensing distinction
A useful way to think about licensing is:
-
Creating analytics → Pro licenses
-
Viewing analytics → Covered by Fabric capacity
This distinction helps schools align licensing costs with actual usage, rather than licensing entire staff or student populations.
6. Cost and scale considerations for schools
Schools often compare Fabric to traditional Power BI licensing by looking at:
-
How many users actively build reports
-
How many users only consume insights
-
Whether analytics will be embedded into school platforms
-
Expected growth over time
Fabric capacity can reduce the need to license large numbers of viewers individually, particularly in environments with many teachers and students.
7. Copilot and AI considerations
Fabric capacity supports AI workloads, but availability depends on:
-
Tenant configuration
-
Data residency and compliance settings
-
Regional rollout of Copilot features
In Australia, for example:
-
Some Copilot features are still being rolled out
-
Cross-geo AI processing must be explicitly enabled
-
Schools can prepare data models and governance now, even if AI features are not yet active
Capacity sizing generally affects performance and concurrency, rather than whether AI features are available.
8. When might a school need larger capacity?
Schools may consider higher capacities if they:
-
Operate multiple campuses in one tenant
-
Run frequent or near-real-time data refreshes
-
Have large numbers of concurrent report users
-
Use intensive Spark or machine learning workloads
-
Support analytics across multiple schools or organisations
Capacity can be adjusted as usage patterns become clearer.
9. Typical licensing patterns seen in schools
While every school is different, common patterns include:
-
One Fabric capacity supporting the analytics platform
-
A limited number of Power BI Pro licenses for creators
-
View-only access for the wider school community
-
Embedded analytics for students and parents
This approach aligns licensing with roles rather than headcount.
Closing thoughts
Microsoft Fabric introduces a licensing model that better matches how schools actually use analytics: a small number of creators and a large number of consumers.
Understanding the difference between capacity, creation, and consumption allows schools to make informed decisions, plan for growth, and avoid unnecessary licensing complexity.
Recommended licensing setup (summary)
| Item | Recommendation |
|---|---|
| Fabric capacity | F2 To F16 |
| Power BI Pro | 5–10 licenses |
| Teachers | Free viewers |
| Students | Free viewers |
| Parents | Embedded (no license) |
