A Fabric trial gives you the whole platform and none of the AI.

Most people who start a Microsoft Fabric trial are not there to evaluate lakehouse architecture. They have seen a demo where somebody types "show me sales by region and explain the drop in Q3" and a report appears, and they want to know whether it works on their own data.

So they sign up for the 60-day free trial, open a report, and look for the Copilot button. This article is about what happens next.

Tested in the CaseWhen Microsoft tenant on 2026-09-22, on a Fabric trial capacity (SKU FTL64, Germany West Central, created 2026-09-21), with every Copilot admin setting read directly from the Fabric admin API and confirmed switched on.

Quick answer

Copilot does not work on a Fabric trial capacity. Not in Power BI, not in pipelines, not in notebooks. It requires a paid capacity, and Microsoft's documentation is explicit that "trial capacities and free SKUs aren't supported."

Three things follow from that, and they are the reason this article is longer than one sentence:

• It is not a setting you missed. Every Copilot switch in our tenant was already on. The block is the capacity type, and nothing in the admin portal can change it.

• The trial is still worth running. Everything in Fabric that is not AI works, and it is a lot.

• Turning Copilot on is cheaper than most people assume. The smallest paid capacity is roughly €0.38 an hour and can be paused when you are not using it. There is a catch, and it is covered below.

The one idea that explains all of this

If you come from Power BI, you are used to software sold per person. You buy a Pro license for each person who needs one, and that is the whole model.

Fabric is sold differently. You rent an engine, called a capacity, and everything your organization does in Fabric runs on it. Capacities come in sizes: F2 is the smallest, then F4, F8, and up through F64 and beyond. You pay by the second for the size you pick, whether one person uses it or a hundred.

Copilot's cost is charged to that engine, not to a person. Every question you ask Copilot burns a measurable amount of the capacity you are renting. That is why no per-person license gets you Copilot. A Power BI Pro license is not enough. Premium Per User is not enough either. Microsoft says so directly: "A Power BI Pro or Premium Per User (PPU) license alone isn't sufficient."

If the capacity model itself is new to you, we have written separately about planning and implementing a Power BI capacity, which covers the sizing question this article assumes you have already met.

The free trial gives you an engine – a good one, equivalent to a 64-unit capacity – but Microsoft excludes it from AI. You are renting the engine for free, so they do not let you spend it on the expensive part.

Once you understand that one thing, everything below stops being surprising.

What you were probably hoping to do

Here are the three jobs people actually start a trial to test, and what happens to each one.

It is not your settings, and it is not your admin

The first thing anyone does when Copilot does not appear is ask IT whether it has been turned off. Worth ruling out before you spend a morning on it.

In the tenant these screenshots come from, every relevant setting is on, read straight from the Fabric admin API rather than by eye.

Fabric admin portal > Tenant settings > Copilot and AI. CaseWhen tenant, 2026-09-22. The main Copilot setting reads "Enabled for the entire organization."

With that setting on, opening Copilot from the Fabric navigation gives you this.

Power BI standalone Copilot, CaseWhen tenant, 2026-09-22. "Copilot isn't available in your workspaces. None of your workspaces have the required capacity for Copilot. To get started, contact an admin."

Read the last line again. It tells you to contact an admin. In this tenant the person reading that message is the Fabric administrator, the capacity administrator and the global administrator, and every switch is already on. There is no admin to contact and nothing left to enable. The message sends you down a path that has no end.

This is worth knowing before you open a support ticket about it.

The same block appears three different ways

If Fabric said "this needs a paid capacity" once, consistently, this would be a two-paragraph article. It does not. Here is the same single cause, presented three ways in three parts of the product.

In a Power BI report, it blames your workspace.

Power BI service, report in a trial workspace, 2026-09-22. Tooltip: "Copilot isn't supported in this workspace. Try using it in another workspace or check Power BI documentation for details on compatible workspaces."

The advice is to try a different workspace. On a trial, every workspace you are able to create sits on the same trial capacity, so every one of them fails identically. Nothing in the message mentions the capacity or the trial, so the natural reading is that you have set this workspace up wrong.

In a data pipeline, it says nothing at all.

Fabric Data Factory, new data pipeline, 2026-09-22. The "Need help? Ask Copilot" prompt appears on the start screen. Clicking it, and clicking the Copilot button in the ribbon, produces nothing.

Fabric offers Copilot to you, in the middle of the screen, on a capacity where it cannot run. Click it and nothing happens. No pane opens, no message appears, nothing is logged on screen. That silence is by design rather than a local fault – Microsoft's own Data Factory Copilot page states that when it cannot run, "it doesn't give an error message either."

In a notebook, it finally tells you the truth.

Fabric notebook, 2026-09-22. Tooltip: "Your Fabric license SKU does not allow access to copilot (preview)."

One cause, three experiences. Which explanation you get depends entirely on which part of Fabric you happened to open first. If it was a report, you will go looking for a workspace setting. If it was a pipeline, you will assume something is broken. Only the notebook tells you it is about what you are paying for.

Two AI features let you start, then fail later

Microsoft's trial documentation says that AI experiences "such as Data agent, AI functions and AI services aren't supported" on a trial. The product does not stop you from starting them.

Data agents appear in the create menu like any other item.

Fabric New item panel, trial capacity, 2026-09-22. Data agent and Operations agent are both offered, described normally, with no notice that a trial capacity cannot run them.

You can click straight through, name it, and only then find out.

Fabric, Create data agent dialog on a trial capacity, 2026-09-22. "Can't create data agents in this workspace: An admin needs to change the SKU type for your organization's Fabric capacity."

This is the closest the interface comes to telling the truth, and it still frames the fix as somebody else's job. "An admin needs to change the SKU type" means "somebody has to buy a paid capacity." If you are the admin, as you often are on a trial, there is nothing for you to change and no setting to find.

Creating the same item through the Fabric REST API drops the euphemism entirely:

{
  "errorCode": "UnsupportedCapacitySKU",
  "message": "FTL64 SKU Not Supported"
}

FTL64 is the trial capacity. One sentence, no ambiguity, available only to people calling the API.

AI functions open a full setup pane.

Fabric notebook, AI tools > Set up an AI function, trial capacity, 2026-09-22. The pane opens and offers four AI functions. The code it generates needs a paid capacity to run.

In both cases the feature is discoverable, configurable, and will let you invest time in it. The failure is deferred until you try to run it. If you are evaluating Fabric against a deadline, this is the part that costs you a day.

What the trial is genuinely good for

None of the above means the trial is a waste. It is 60 days of a 64-unit capacity, free, and it covers everything in the platform except the AI.

A data pipeline, a notebook and a lakehouse all create and open on a trial capacity without complaint.

CaseWhen Demo workspace, 2026-09-22, after creating three items on the trial capacity. A lakehouse with its SQL analytics endpoint, a notebook and a pipeline, all working.

On a trial you get all the Fabric workloads – Data Factory, Data Engineering, Data Science, Real-Time Intelligence and Power BI – pipelines, notebooks, lakehouses, warehouses, workspace collaboration, the Capacity Metrics app, and up to 1 TB of storage in OneLake.

You also get a Power BI individual trial alongside it, carrying Premium Per User rights if you do not already have them. In practice that means large semantic models, 48 data refreshes a day instead of eight, the XMLA endpoint, deployment pipelines and Direct Lake.

One benefit is easy to miss and it matters when you decide what to buy. A trial capacity behaves like an F64 for viewing, which means colleagues who hold only a free license can open your Power BI reports. On any paid capacity below F64, they cannot – every viewer needs a Pro or PPU license.

If your question is "is Fabric the right platform for us", the trial answers it well. If your question is "will Copilot make my team faster", the trial cannot answer it at all.

What you can and cannot do on a Fabric trial

The full picture in one place. Everything in the AI block is blocked by the trial SKU, and nothing you can configure changes it.

AI features

Building and shipping

Platform and security

What it costs to actually turn Copilot on

The smallest capacity that supports Copilot is an F2. At roughly €0.19 per capacity unit per hour, an F2 is about €0.38 an hour, or around €276 a month if you leave it running. Paid capacities can be paused, and a paused capacity costs nothing but storage, so a few days of genuine evaluation costs single-digit euros rather than a monthly commitment.

Three things to know before you do it.

1. Moving off the trial costs you free viewers. Your trial behaves like an F64 for viewing. An F2 does not. The moment you move a workspace onto an F2 so Copilot works, every person who opens those reports needs a Pro or PPU license. The cheapest way to switch Copilot on is also a downgrade in who can read your reports, and nobody mentions it.

2. There is a way to keep both, and most people miss it. You can designate a capacity as a "Fabric Copilot capacity" – one capacity that exists purely to collect Copilot usage for a named group of people, wherever their content actually lives. Microsoft's specification lists Trial among the workspace types those people can then use Copilot on in Power BI. So one small F2, doing nothing but paying for Copilot, switches it on while your work stays on the trial capacity. Two limits apply: Trial is listed for Power BI but not for pipelines, notebooks or the warehouse, so do not assume those come with it; and AI functions are excluded from a Fabric Copilot capacity outright, whatever else you set up.

3. Buying a capacity does not give you Copilot immediately. Microsoft states that when you purchase or resize a capacity, "it can take up to 24 hours for Copilot to recognize the change." Plan your evaluation around that rather than booking a demo for the same afternoon.

Microsoft 365 Copilot is a different product

This is the most common confusion in the whole topic. Microsoft 365 Copilot answering questions from Power BI data is not Copilot in Fabric. It runs on a per-person Microsoft 365 Copilot seat, needs no Fabric capacity at all, and is on by default. The two get discussed as if they are the same thing. They are separate products with separate bills.

So should you bother with the trial?

It depends entirely on which question you are actually asking.

Inviting a colleague adds 7 days to your trial

This appears in no Microsoft documentation. The screenshot below shows the same page describing "a 60-day free Fabric trial" while the Days left column reads 66, on a capacity that was a day old. Microsoft's trial page names only one route to an extension, which is to contact a sales representative.

Fabric admin portal > Capacity settings > Trial, 2026-09-22. The description says "a 60-day free Fabric trial". The Days left column says 66, on a capacity created 2026-09-21, after a 7-day extension earned by inviting a colleague.

Worth knowing too: Microsoft now provisions trials at either 4 or 64 capacity units depending on the tenant. If yours came in at 4, check Admin portal > Capacity settings > Trial for a Change size button, which may let you raise it to 64. Resizing does not reset or extend the clock.

The environment behind these results

Every behavior described above was confirmed in a live Microsoft tenant on 2026-09-22: a Fabric trial capacity, SKU FTL64, 64 capacity units, Germany West Central, with the workspace set to workspace type Fabric Trial.

Workspace settings > Workspace type, 2026-09-22. Current workspace type: Fabric Trial. SKU: FTL64, Region: Germany West Central.

Tenant settings were read through the Fabric admin API rather than by eye, so "the settings were on" is a measurement rather than an impression. The pipeline, notebook and lakehouse were created through the Fabric REST API and then opened in the browser.

Fact check

Microsoft ships changes to Fabric monthly, and settings pages move. Every tenant observation above is true as of 2026-09-22 and worth re-checking before you rely on it.