MICROSOFT FABRIC

Preview, GA, and other Microsoft Fabric terms: what do they mean?

By Karine Batista · 2026-10-18 · 6 min read

Understand the differences between Preview, GA, and other Fabric terms, and learn what to consider before using new features in your projects.

Hello, apprentices! 🧙

You know when Microsoft announces something new in Fabric, you start thinking about where you could use it, and then notice Preview next to its name? Or when a feature finally reaches GA and you wonder: “Okay, but what has changed?”

Frieren looking confused by Fabric terminology.

Character: Frieren · Series: Frieren: Beyond Journey’s End (Sousou no Frieren).

These terms appear frequently in Microsoft’s announcements and tell us a lot about what we can expect from a feature. That matters especially when we are working on projects, because not everything available to use is necessarily ready for production.

So, let’s unpack these terms and understand why they deserve our attention.

1. Preview: available, but use with care

When a feature is in Preview, Microsoft has released an early version for users to try, evaluate, and provide feedback on.

It is an opportunity to explore the feature before its official launch, but it also means that it may change, be unstable, or have limitations.

There are two main ways to make it available:

Type	What it means
Private Preview	Access is restricted to selected customers or invited participants.
Public Preview	The feature is available to a wider audience, although it may still require enablement or specific permissions.

One key point: according to Microsoft’s documentation, Fabric Preview features are not intended for production and do not have an SLA (Service Level Agreement).

What does that mean? If a feature has problems, we do not have the same availability and support guarantees as with a GA feature. Microsoft may provide limited technical support for Public Preview, but there is no guarantee of a fix or that everything will keep working as expected.

That is why we should remember that we are trying something still under development, and these limitations are part of the process.

2. GA: ready for production now?

GA stands for General Availability.

It is when a feature reaches general release, moving beyond the evaluation stage. It can then be considered for production use, subject to the service’s conditions and requirements.

There is an important detail, though: being in GA does not mean that everything is automatically available for every scenario.

Depending on the feature, licensing, permissions, regional availability, or capacity requirements may still apply.

A feature may also be in GA while a related integration remains in Preview.

Before implementing something new, check exactly what has been released and whether all the features your project needs are available.

3. What about the other terms used in Fabric?

Besides Preview and GA, we encounter other expressions in the documentation. Some seem to describe a feature’s maturity, but actually relate to updates, access, or planning.

Term	What it means in practice
Early Access	Lets you try certain updates before they reach the default channel, as with Spark runtimes.
Default	The standard update channel, in the context of Spark release channels.
Trial	A time-limited evaluation offering with its own conditions and restrictions.
Roadmap / Planned	Indicates planned features whose expected release dates may still change.

For example, using a Fabric Trial capacity does not mean that all the features available on it are in Preview. One concerns evaluating the service; the other indicates a feature’s release stage.

The same goes for Early Access. In Spark release channels, it provides early access to updates, but should not be confused with Private Preview.

4. How do we decide what to use in a project?

In some projects I have worked on, clients had a very clear rule: do not use Preview features.

That makes sense when we consider the risks involved.

Imagine you are building a solution in Fabric and discover a new feature that would make the work much easier. You test it, see that it works well, and decide to use it.

Then, overnight, an update changes its behavior, it starts producing errors, or it simply becomes unavailable. What now?

If this is a solution the client uses every day, it can become a major problem.

This is why we need to consider a few questions before adopting something new:

Does the client allow it? Are there restrictions on using Preview features?
What are the risks? How could a change or instability affect the solution?
Do we have an alternative? If the feature stops working as expected, can we take another approach?

That does not mean we should ignore new features. Quite the opposite! Preview is a great opportunity to study, experiment, and explore features that may become part of our projects in the future.

The difference lies in knowing when and where to use them. Testing a new feature to understand its potential is one thing. Depending on it to keep a production solution running is another, especially when Microsoft itself still makes it available only for evaluation.

5. Where can we follow these updates?

With so many Fabric updates, it is not always easy to keep track of what has just launched, what is still in Preview, or what is planned for the coming months.

Two Microsoft pages are particularly useful:

What’s new in Microsoft Fabric: brings together updates, new features, and Preview and GA announcements.
Microsoft Fabric roadmap: shows what is being planned and expected release dates.

I also recommend checking the specific documentation whenever you find something you want to use. Fabric keeps evolving, and a feature that is in Preview today may reach GA in an upcoming update.

Understanding these differences helps us follow new developments more clearly and, above all, make more informed decisions in our projects.

6. References

Until our next adventure!

Karine Batista