How to Fix the Copilot Unavailable Error in Power BI

João Barros 13 de July de 2026 4 min read

Opening a report and not seeing the Copilot button in Power BI is one of the most common problems for people getting started with the feature. The good news: the "Copilot unavailable" error almost always has a concrete cause - licence, tenant setting, capacity or region - and you can solve it by elimination. Follow the steps in the order below and within minutes you will know exactly what is blocking you.

Prerequisites

A workspace in the Power BI service where you can open a report.
Access to a Fabric / Power BI administrator (needed in Step 2), or someone you can ask.
Knowing which licence backs your workspace (Fabric F, Premium P, or Pro only).
Optional: PowerShell with the MicrosoftPowerBIMgmt module, for Step 3.

Step 1: Check the licence and the capacity

Copilot in Power BI does not work in workspaces without dedicated capacity. The workspace must be backed by a Fabric capacity (SKU F2 or higher) or a Power BI Premium capacity (P1 or higher). If your organisation only has Pro licences, the button simply will not appear - and no setting will bring it back.

To check, open the workspace, go to Workspace settings and look at the License tab. If it says Pro, you have found the cause and can stop here.

Step 2: Check the tenant setting

Even with capacity, Copilot stays invisible if the administrator has not turned the matching setting on. Ask a Fabric administrator to go to Admin portal > Tenant settings and look for the Copilot and generative AI setting. It must be Enabled, and if it is scoped to specific security groups, your user has to belong to one of them - by far the most common reason why Copilot works for a colleague but not for you.

After enabling it, the change can take a few minutes to propagate. Do a full browser refresh (Ctrl+F5) before concluding that it still fails.

Step 3: Confirm which capacity holds the workspace

Very often the report lives in a different workspace than the one we assume. With the MicrosoftPowerBIMgmt module you can quickly list the workspaces that are not on dedicated capacity:

# Install and authenticate (once)
Install-Module -Name MicrosoftPowerBIMgmt -Scope CurrentUser
Connect-PowerBIServiceAccount

# List workspaces WITHOUT dedicated capacity
Get-PowerBIWorkspace -Scope Organization -All |
    Where-Object { $_.IsOnDedicatedCapacity -eq $false } |
    Select-Object Name, Id, CapacityId

The command returns exactly the workspaces where Copilot will never appear. If yours is on the list, move the content to a workspace backed by a Fabric capacity (or assign a capacity to that workspace, if you have the rights). The -Scope Organization parameter requires admin rights; without them, use -Scope Individual.

Step 4: Check the capacity region

Copilot relies on AI services that are not available in every region. If your capacity sits in a region where those services do not exist yet, the administrator must enable the admin portal setting that allows data to be processed outside the geographic region of the capacity. Without that consent, Copilot shows as unavailable even when everything else is correct. Check the region under Admin portal > Capacities, and validate the decision with whoever owns compliance, because it means sending data to another region.

Step 5: Isolate the problem with a simple model

If the Copilot pane opens but returns an error, or says it cannot find the data, the problem is no longer configuration: it is the semantic model. Technical names such as FCT_SLS_01, missing descriptions and badly defined relationships leave Copilot without context. Test with a small, clean model - two or three tables with business-friendly names and correct relationships. If it works there, you know the path forward is improving the model, not touching the configuration again.

Verify the result

Open a report in the Power BI service. You should see the Copilot button in the top bar and, when you click it, a side pane with prompt suggestions. Ask for something simple, such as a summary of the current page. If you get a text answer back, everything is working. Final checklist: capacity F2 or higher (Step 1), tenant setting enabled with your user included (Step 2), the right workspace on the right capacity (Step 3), and a compatible region or cross-region processing allowed (Step 4).

Conclusion

In the vast majority of cases the "Copilot unavailable" error is solved at one of these four points, and following the order above saves time because it starts with the most likely one. The natural next step is preparing the semantic model so you get real value from Copilot: table descriptions, synonyms, and names any business user would recognise. Final tip: before opening a support ticket, ask a colleague from another team to test - if it works for them and not for you, the problem is almost certainly the security group from Step 2. Which of the four was yours?