Power BI Copilot • troubleshooting

Power BI Copilot “Something went wrong”? Find your fix.

Watch an expert setup fix or go straight to your error. Check access, capacity and service health before reinstalling or upgrading.

Updated November 22, 2026Official docs + real user cases

Quick answer: three checks before changing anything

1. Service health: check for a Fabric/Power BI outage. 2. Access: verify tenant policy and an eligible paid capacity or assigned Fabric Copilot capacity. 3. Location of the error: is it Desktop, the report pane, a narrative or a missing entry point? The same generic message can have different causes.

Start here • practical video solutions

Watch the fix that matches your Copilot error

If Copilot says “Something went wrong,” start with the admin settings walkthrough. If the button is disabled, choose the Desktop setup video. The third is an older video linked in a Microsoft Community answer to this exact error wording.

Disabled button • March 2026

Copilot Disabled? This Will Fix It

Patrick Wallet shows capacity and workspace setup for an inactive Copilot control.

Exact error case • Older tutorial

Video cited for “Something went wrong”

Linked in a real Fabric Community reply. The questioner did not verify the fix.

What these videos can fix: missing prerequisites and configuration errors. A backend outage, item-specific error or unsupported experience may need a different solution. Older tutorial screens can differ from today’s admin portal.

Don’t want to watch a video? Go straight to the exact symptom and written steps, with Microsoft documentation linked at each check.

Choose my error and fix ↓

Real thumbnails load as small images from YouTube’s thumbnail server. The video player itself is not requested until you select Play. If your organization blocks embeds, use the YouTube link next to the video.

Start here • choose your symptom

Which Power BI Copilot problem do you see?

Choose the closest match. Each path links to the first check and the official documentation or reported solution supporting it.

First 2 minutes

Use this diagnosis order before changing settings

1Confirm the failureRecord the exact message, UTC time, activity ID and where it happened.
2Check access routeTest the effective user’s workspace or assigned Fabric Copilot capacity, tenant group and region.
3Isolate the scopeCompare one approved user, report and environment. Escalate with evidence if all fail.

Open Microsoft Fabric service status first. Also ask your administrator to check your organization’s service-health dashboard, because public status may not describe every tenant-specific issue. A green public page is not proof that your tenant is unaffected.

Security first: never paste access tokens, sensitive model data, personal report screenshots or private prompts into a public forum. Do not enable cross-geography processing or move production workspaces just to make a test pass.

Path 01 • error on click

Fix “Something went wrong” after selecting Copilot

  1. Check status, and capture correlation IDs. If several users began failing at the same time, prioritize a service incident or a recent administrator change over browser cache.
  2. Identify the Copilot experience. Report-pane Copilot, report creation, Desktop DAX assistance, standalone Copilot, app-scoped Copilot and narrative generation do not all have identical requirements.
  3. Ask an admin to verify the effective policy. In the Fabric admin portal, inspect Tenant settings for Users can use Copilot and other features powered by Azure OpenAI and applicable allow/exclude groups. Where settings are delegated, also check the relevant capacity settings.
  4. Check which capacity will pay for this request. Use the workspace capacity route or the user’s assigned Fabric Copilot capacity (FCC)—not assumptions based on a Pro/PPU license alone.
  5. Retest with the same approved action. If it still fails, compare a second approved report or user without changing several settings at once. Collect the IDs for Microsoft support.
A real matching forum case: a Power BI Desktop user reported this exact message in April 2024. A Microsoft Fabric Community Super User recommended checking service-side settings and linked a walkthrough. The question author could not verify the fix due to insufficient permissions; it is an accepted answer, not a confirmed repair for every user. Read the original case and accepted suggestion.

Core fix • licensing and compute

Check the capacity route: F2+ is possible; F64 is not a universal requirement

Microsoft’s baseline for supported Copilot use is an eligible paid Fabric F2 or higher or Power BI Premium P1 or higher capacity, plus appropriate tenant, regional and feature prerequisites. The exact access path matters. An individual Power BI Pro or PPU license is not by itself a Copilot compute entitlement.

Your setupWhat to checkWhat it means
Report stored on paid F2+ or P1+ capacityCapacity is running, Copilot enabled and supported in the region; user has the required accessNormal content-capacity path, subject to feature-specific conditions.
User is assigned a Fabric Copilot capacity (FCC)Fabric admin authorizes FCC; capacity admin designates the relevant user group; effective assignment and home region are correctCopilot usage can bill to FCC instead of the workspace hosting the content.
Pro / PPU / Trial workspaceWhether the user is assigned a supported FCC and the exact feature supports that routeFCC documentation supports these workspace modes for Power BI Copilot usage. Pro or PPU alone is insufficient.
Trial SKU only, free SKU, paused or deleted paid capacityWhether any separate eligible paid route actually remainsA standalone trial SKU or missing eligible capacity is not enough.

FCC details that often get missed: Microsoft documents FCC as a designated paid F2/P1+ capacity in the Fabric tenant’s home region. A user should have one effective FCC; if assigned multiple, Microsoft says usage is recorded on the most recently created FCC. FCC takes billing precedence over the content workspace capacity. Embedded workspace license mode is excluded from the listed FCC scenario.

If you recently purchased or resized a capacity: Microsoft notes that Copilot availability can take up to 24 hours to recognize the change. Check state and entitlement before repeatedly purchasing or upgrading.

Official: Fabric Copilot capacity, supported scenarios and limits
Official: Power BI Copilot requirements by experience

Path 02 • disabled button

Copilot button greyed out? Fix the prerequisites before the app

Microsoft says the Copilot button can be visible in Desktop even when the required tenant or capacity authorization is missing. This is not proof that the feature has been activated for the account.

  • Confirm the correct work or school account is signed in. Personal Microsoft Copilot access is not a substitute for Fabric/Power BI organizational entitlement.
  • Have the Fabric admin confirm the Users can use Copilot and other features powered by Azure OpenAI setting and actual user-group membership.
  • Where tenant control is delegated, have the appropriate capacity admin inspect the delegated Copilot setting.
  • Confirm an eligible paid capacity route, supported region, active capacity and access to a Copilot-compatible workspace or an applicable assigned FCC.
  • If the button is disabled only while editing a semantic model on the web, check whether you are in Editing rather than Viewing mode and have write access to that model.

Microsoft’s enablement instructions give the admin sequence. An older Microsoft Community thread also reports a user who got greyed-out Copilot suggestions working after a geography-related setting change. That action requires compliance review; it is not a general recommendation to enable cross-border processing.

Path 03 • it used to work

Copilot stopped after a trial expired or a capacity changed

Ask the capacity owner whether the report’s workspace was reassigned, the trial ended, a paid capacity was paused, or the affected user was removed from an FCC security group. Look at the workspace’s current license mode, not the last screenshot taken before the change.

  1. Confirm that the eligible paid capacity still exists, is running and is in a supported region.
  2. Check whether the affected content is still in the expected workspace and whether the user retains relevant permissions.
  3. If an FCC is configured, inspect the user’s effective FCC group and any recent designation changes.
  4. Retest one approved report; do not move production data or scale the SKU until evidence identifies that as necessary.

Microsoft: Copilot unavailable after trial expiry · Microsoft: manage capacity settings

Path 04 • Desktop vs web

Power BI Desktop Copilot fails, but the service works

Desktop has its own workspace-selection and build requirements. Microsoft documents that versions from January 2025 or earlier do not support the report-view Copilot pane.

  1. Install an approved current Power BI Desktop build after saving your work.
  2. Open the report in Desktop, choose Copilot, and inspect the compatible-workspace picker. Only eligible workspaces appear. The chosen Copilot workspace need not be the report’s eventual publishing destination.
  3. Use the gear icon in Desktop’s Copilot pane or the Copilot settings to inspect and, where appropriate, select a different eligible workspace.
  4. Confirm at least the required workspace role—Microsoft documents admin, member or contributor on an eligible workspace for the ordinary Desktop path—and inspect any assigned FCC route.
  5. If there is a 403 Forbidden error, check the documented sovereign-cloud and authorization limitations; a fresh browser session is not a universal fix.
Test one change at a time: if the same account works in the Power BI service, log the Desktop build and chosen Copilot workspace before resetting anything. Do not delete user profiles, credentials or caches as a first-line repair.

Microsoft: use and troubleshoot Copilot in Desktop

Path 05 • visual and semantic model

“Something went wrong and we couldn’t load the narrative”

First separate the visual types. A standard Smart narrative visual and an AI-generated Copilot narrative are not equivalent. Record the exact visual, error text and whether the same report works in the service.

  1. Check the official status dashboard. Test the same narrative in a second approved report and with a second permitted account.
  2. If the ordinary Smart narrative fails, inspect visual errors and underlying measures/queries. Don’t assume every Smart narrative error is a Copilot-license failure.
  3. If Copilot-generated narrative fails, verify entitlement, group permissions, semantic-model access, and the feature’s support requirements.
  4. If only this model fails, examine field naming, relationships, missing values, security, supported features and AI preparation guidance. A small model working does not prove the original model must be rebuilt.
Useful unresolved example: a Fabric Community user reported narrative errors in both Desktop and the Power BI service even though Copilot settings appeared enabled. The discussion ultimately directs users toward a support ticket; it does not establish a universal narrative fix. Read the case.

Admin check • governance

Tenant policy, processing location and permissions: the safe checklist

CheckWho verifies itSafe action
Copilot tenant authorization and allowed/excluded groupsFabric administratorConfirm the affected user’s effective setting; scope a controlled pilot group if approved.
Capacity-level delegated settings / FCC designationFabric and capacity administratorsCheck the actual user group and eligible capacity route.
Capacity region / data-processing boundaryCapacity admin and data-governance ownerMatch Microsoft’s supported-region list and review compliance approvals before changing anything.
Report and semantic-model permissionsWorkspace ownerConfirm read, edit, build or write privileges appropriate to the exact Copilot task.

Cross-geography processing consent may be required in certain regions or experiences; Microsoft also distinguishes processing from FCC billing. It is not appropriate to enable tenant-wide data movement merely because a generic error appears. Microsoft’s Copilot/AI admin settings reference is the authority for the current labels.

New November announcement

Missing standalone or app Copilot? Check the announced retirements

Microsoft’s November 2026 Power BI update says support for standalone Power BI Copilot on the web, Teams and mobile is planned to end by the end of January 2027. App-scoped Copilot and its per-app setting are scheduled for removal in January 2027. Copilot within eligible reports remains supported.

These are future plans as of this review; they do not explain every Copilot failure in November 2026. Compare the same account’s report pane with the missing entry point. If the report pane works, check the transition notes and relevant app or standalone settings instead of relocating a workspace.

Don’t confuse removal with malfunction. Note precisely whether the control is missing, disabled, or produces an error. The diagnosis—and the useful Microsoft documentation—will differ.

What evidence actually exists?

Reported solutions vs. things that have not been proved

Directly matching error — tenant settings

A 2024 Microsoft Fabric Community thread recommends checking Power BI service settings, with a linked video. Accepted as plausible, not tested by the original reporter.

Evidence strength: user-reported suggestion

Read the accepted answer

Greyed-out Copilot — region setting

A separate 2024 user reported restoring Copilot suggestions after an admin changed a geography-related setting. This is not permission to bypass your organization’s residency policy.

Evidence strength: individual reported outcome

Read the report

Narrative load error — unresolved

A user described the error in Desktop and Service and later confirmed the Copilot admin setting was enabled. The thread recommended Microsoft support, with no generally proven repair.

Evidence strength: diagnostic case, not a fix

Read the issue

Vendor-supported prerequisites — current

Microsoft documentation is the primary authority for eligible F2/P1 capacity, FCC user billing, Desktop workspace selection, tenant policies, regional restrictions and future entry-point retirements.

Evidence strength: official product documentation

See the requirements

After the checks

Still failing? Send Microsoft a useful support case

Escalate if the same supported action fails across approved users or items despite verified capacity, effective tenant settings, feature permissions and a checked service status. For an intermittent issue, include the timestamp of a successful comparison too.

  • Exact Copilot action and whether the button was missing, disabled, or failed after clicking
  • UTC time, error text, request ID / activity ID and tenant details approved for support
  • Desktop build or browser and the specific workspace, report and semantic model identifiers
  • Workspace mode and effective FCC or content-capacity route, active state and region
  • Relevant approved group authorization, recent changes and test-case comparisons
  • Capacity Metrics app or incident evidence, without confidential model data
Power BI Copilot error — support summary
Exact error and Copilot experience:
UTC time / request ID / activity ID:
Desktop version or browser:
Workspace and item (sanitized identifiers):
Capacity status / SKU / region:
FCC routing or content-capacity route:
Effective tenant policy and group scope:
Same user / different item result:
Same item / different approved user result:
Service-status and Capacity Metrics evidence:
Last known working time / recent change:

Official: create a Fabric or Power BI support ticket · Official: check Copilot compute in the Capacity Metrics app

Frequently asked

Power BI Copilot “Something went wrong”: common questions

Do I need F64 or a Power BI Premium license to fix this?

No universal F64 requirement exists for the supported scenarios described here. Microsoft documents paid Fabric F2+ or Power BI Premium P1+ capacity as the baseline. You also need the correct feature, policy, region and user authorization. Don’t buy a bigger SKU without checking the actual cause.

Can Copilot work with a Pro or PPU workspace?

Pro/PPU alone is not enough. Microsoft’s Fabric Copilot capacity documentation supports assigned FCC users using Copilot in Pro and PPU workspaces, alongside other supported modes. Check the precise Copilot experience and requirements before assuming it applies to your case.

Why does the Copilot button appear but do nothing?

Desktop can display the button without qualifying tenant authorization or an eligible workspace. Check your effective tenant setting, capacity route, workspace choice and permissions before reinstalling the application.

Should I enable cross-region processing to make Copilot work?

Only after your Fabric administrator and data-governance owner confirm it is required for the supported experience and expressly approve it. A generic error does not authorize a change to data residency controls.

Does a working test report mean my original semantic model is broken?

No. It suggests an item-specific branch, but permissions, unsupported features, model metadata, query failures and AI preparation should be compared before any rebuilding.

Is Power BI Copilot being discontinued in January 2027?

Not all of it. Microsoft has announced plans to retire standalone and app-scoped preview experiences on the stated timeline. Copilot within eligible reports remains supported. A missing button today should still be investigated using the exact entry point and current rollout status.

Sources and transparency

Official documentation and evidence links

Primary-source review completed November 22, 2026. The community cases are labeled by what was actually established. This independent guide does not claim an error was reproduced in your tenant.

  1. Microsoft: Copilot for Power BI overview and requirements
  2. Microsoft: Enable and configure Fabric Copilot
  3. Microsoft: Fabric Copilot capacity and supported scenarios
  4. Microsoft: Copilot in Desktop and workspace selection
  5. Microsoft: Copilot and AI admin settings
  6. Microsoft: November 2026 changes and retirements
  7. Microsoft: Copilot FAQ and common symptoms
  8. Microsoft: support ticket instructions
Editorial note: Features, regional availability and capacity rules may change. Always check the linked Microsoft documentation before tenant-wide or production changes. Independent guide, not affiliated with Microsoft.
Scroll to Top