Question about Copilot availability with Fabric and Embedded

Question

We have purchased a Fabric F16 capacity and enabled Copilot. At the same time, we also use Power BI Embedded (A SKUs) to embed reports into our applications.

Could you please clarify:

• If Copilot is enabled on the Fabric F16 capacity, will Copilot features also be available when those reports are viewed through Embedded capacity?
• Or is Copilot only available when reports are accessed directly in the Power BI Service (workspaces assigned to Fabric capacity), and not when embedded via A SKUs?

Thank you for your guidance.

Best regards,

QuyenNT

Answer 1

I think Copilot only runs when the rpt’s home‑ws sits on ur F16… open it once in that F‑ws and see the icon light.

Answer 2

Copilot features are tied to Fabric/Power BI Premium capacity, not to Power BI Embedded (A SKUs).

From the provided information:

• Copilot in Power BI requires a paid Fabric capacity (F2 or higher) or Power BI Premium capacity (P1 or higher). Trial capacities and free SKUs are not supported.
• Workspaces that have a workspace type of Power BI Pro, Premium Per User (PPU), or an unsupported F SKU don't support Copilot.
• Capacities with the Embedded license mode aren't supported for Fabric Copilot capacity.
• Copilot can be enabled for secure embedded reports only when the report’s workspace is backed by Power BI Premium or paid Fabric capacity, and the Copilot tenant switch is active.

Applying this to the scenario:

1. Fabric F16 capacity
   • Workspaces assigned to the F16 Fabric capacity meet the capacity requirement for Copilot.
   • When users access reports directly in the Power BI Service (in those Fabric-backed workspaces), Copilot features are available, assuming tenant/workload Copilot settings are enabled.
2. Power BI Embedded (A SKUs)
   • A SKUs are Embedded capacities and are not listed as supported capacities for Copilot.
   • Fabric Copilot capacity explicitly does not support Embedded license mode.
3. Embedded reports scenario
   • If a report is embedded via “Website or portal” with the Enable Copilot checkbox, Copilot in the embedded report requires:
     • An active Copilot tenant switch, and
     • The report’s workspace to be on Power BI Premium or paid Fabric capacity.
   • Simply running the report on an A SKU Embedded capacity does not make Copilot available.

Therefore:

• Copilot is only available when the report’s workspace is on Fabric (F SKUs, including F16) or Power BI Premium (P SKUs) and Copilot is enabled at the tenant/workload level.
• Copilot is not provided by A SKU Embedded capacity itself. If a report is hosted purely on an Embedded (A SKU) capacity without being backed by a Fabric/Premium workspace, Copilot features will not be available.

In practice, Copilot will work:

• In Power BI Service for workspaces assigned to the F16 Fabric capacity.
• In embedded scenarios only when embedding reports from those Fabric/Premium-backed workspaces with Copilot enabled.

It will not work when relying solely on A SKU Embedded capacity without Fabric/Premium backing.

---

References:

• Fabric Copilot capacity
• What is Copilot in Fabric?
• Enable Copilot in Fabric
• Copilot for Power BI overview
• Embed a report in a secure portal or website
• Copilot in Power BI integration