You want to use Copilot in Power BI to generate reports, ask questions about your data, or create visuals using natural language. But when you try to open the Copilot pane, you see an error message or the pane is grayed out. This usually happens because your workspace permissions are not set correctly. In this article, you will learn exactly which workspace roles and Microsoft 365 licenses are required for Copilot to function in Power BI.
Key Takeaways: Power BI Copilot Workspace Permissions
- Power BI workspace role Admin, Member, or Contributor: Required for any user who wants to open the Copilot pane and generate content.
- Microsoft Fabric or Premium capacity: The workspace must be assigned to a Fabric F64 or higher capacity, or a Power BI Premium P1 or higher capacity.
- Copilot license enabled in tenant settings: The Power BI admin must turn on the Copilot feature switch in the Microsoft 365 admin center.
Why Copilot in Power BI Depends on Workspace Permissions
Copilot in Power BI is not available in every workspace by default. The feature requires specific infrastructure and user roles because it runs on large language models that need dedicated compute resources. Microsoft enforces these requirements to control cost and ensure data security.
The root cause of Copilot not appearing is almost always one of these three conditions:
- Capacity type: The workspace must reside on a Fabric F64 or higher capacity, or a Power BI Premium P1 or higher capacity. Shared capacity, Premium Per User, and Fabric trial capacities do not support Copilot.
- User role: Only users with the Admin, Member, or Contributor role in the workspace can access the Copilot pane. The Viewer role cannot generate or view Copilot outputs.
- Tenant setting: The Power BI admin must enable Copilot at the tenant level in the Microsoft 365 admin center. If this switch is off, no user in any workspace can use Copilot.
Understanding these three gates helps you diagnose the problem quickly. If any one of them is not met, Copilot will remain inaccessible.
Steps to Verify and Set Workspace Permissions for Copilot in Power BI
Follow these steps to check your current workspace setup and assign the correct permissions. Perform each step in the order listed.
- Check the workspace capacity type
Open the Power BI service at app.powerbi.com. Select the workspace from the left navigation pane. Click the workspace settings gear icon and select Premium. Look for the License mode field. It must show Fabric F64 or higher, or Power BI Premium P1 or higher. If it shows Shared, Premium Per User, or Trial, Copilot will not work. - Assign the workspace to a supported capacity
If the workspace is on shared capacity, ask your Power BI admin to assign it to a Fabric F64 or Premium P1 capacity. Go to Admin portal > Capacity settings. Select the capacity and click Assign workspaces. Check the box next to the workspace name and click Assign. - Verify your workspace role
In the workspace list, find the workspace and look at the Role column next to your name. If it says Viewer, you cannot use Copilot. Ask the workspace Admin to change your role to Contributor, Member, or Admin. - Change your workspace role if needed
The workspace Admin goes to Manage permissions > Access. Select your name and choose Change role. Select Contributor, Member, or Admin from the dropdown. Click Save. - Confirm the Copilot tenant setting is enabled
Only a Power BI admin can do this step. Go to Microsoft 365 admin center > Settings > Org settings > Power BI > Copilot. Set the toggle to On. If you are not an admin, ask your admin to check this setting. - Test Copilot in a report
Open a report in the workspace. Click the Copilot button in the top-right corner of the Power BI service. The Copilot pane should open. Type a question or request to generate a visual.
If Copilot Still Does Not Appear After Setting Permissions
Even after you meet all three requirements, Copilot may not appear due to other configuration issues. Below are the most common scenarios and their fixes.
Copilot pane is grayed out or shows a loading spinner indefinitely
This usually means the capacity is not fully provisioned for Copilot. Go to the Fabric admin portal > Capacity settings. Under the Copilot section, check that the Copilot feature is enabled for that specific capacity. If it is disabled, click Enable and save. Then refresh the Power BI service page.
Error message: Copilot is not available for this workspace
The error text is explicit. It means the workspace is on a capacity that does not support Copilot. Double-check the license mode in workspace settings. If it shows Premium Per User, you must migrate the workspace to a Premium P1 or Fabric F64 capacity. Migration does not delete existing reports or datasets.
Copilot generates generic answers instead of using your data
This happens when the dataset does not have a semantic model that Copilot can read. Open the dataset in Power BI Desktop. Go to the Model view and ensure that at least one table has a relationship defined. Copilot requires a star or snowflake schema. If the model is flat with no relationships, Copilot cannot ground its output in your data.
Copilot button is missing entirely from the Power BI service
The button may be hidden due to a browser extension or an old browser version. Clear your browser cache and cookies. Use Microsoft Edge or Google Chrome in Incognito mode. If the button still does not appear, check the Power BI admin setting for Copilot. The admin may have disabled Copilot for specific security groups.
Copilot in Power BI: Workspace Roles and Capacity Types Compared
| Item | Admin / Member / Contributor | Viewer |
|---|---|---|
| Can open Copilot pane | Yes | No |
| Can generate visuals and reports | Yes | No |
| Can see Copilot outputs in shared reports | Yes | No |
| Required capacity | Fabric F64+ or Premium P1+ | Any capacity but Copilot never shown |
| Required license | Power BI Pro or Premium Per User plus Copilot tenant enablement | Power BI Pro or Premium Per User |
The table above shows that the Viewer role cannot access Copilot under any capacity. Even if the workspace is on a Premium P1 capacity, a Viewer will not see the Copilot button. Only workspace Admins, Members, and Contributors can use Copilot.
Now you can check your workspace capacity, verify your role, and enable the tenant setting if needed. The most common cause is a workspace on shared capacity or a user with the Viewer role. Ask your Power BI admin to assign the workspace to a Fabric F64 or Premium P1 capacity and change your role to Contributor if needed. After these changes, the Copilot pane will appear and you can generate reports using natural language.