Can't Import a .pbiviz? Fix 'Get More Visuals' Greyed Out (2026)

Before changing anything, narrow the cause with a 30-second triage. If the Visualizations-pane ellipsis is greyed out, or 'Get more visuals' and 'Import a visual from a file' are missing or disabled, the block is almost always governance - a tenant setting or Group Policy - or, in Desktop, developer mode simply isn't switched on for this session. If the menu works and the import completes but the visual shows an error box where the chart should be, suspect the certified-only policy, a visual an admin removed from the organizational store, or a visual built for a newer API than your Desktop supports. If the file picker opens, you select the .pbiviz, and nothing happens - an endless spinner - you are looking at a corrupted download or, on Report Server, the offline visual-host problem covered at the end. Match your symptom to the right section below.

This is the single most common reason imports are blocked, and only a Fabric administrator can change it. The setting lives in the Fabric admin portal (https://app.fabric.microsoft.com/admin-portal, or in the Power BI service go to Settings > Admin portal) under Tenant settings; scroll to the 'Power BI visuals' group. It is not in the Power Platform admin center. The switch named 'Allow visuals created using the Power BI SDK' governs every visual imported from a .pbiviz file or from AppSource - exactly the things you are trying to add. Microsoft documents it as disabled by default, so in the Power BI service, adding a custom visual is blocked for the whole organization until an admin enables it (for everyone, or for a specific security group). To turn it on: expand 'Allow visuals created using the Power BI SDK', select Enabled, choose the audience, and select Apply; changes can take up to 15 minutes to propagate. Important nuance: the admin-portal switches only affect the Power BI service. Power BI Desktop reads a separate Group Policy value, EnableCustomVisuals, which defaults to enabled (1) when no policy is deployed - so Desktop normally allows imports unless your IT team pushed a policy to block them. If Desktop is blocking .pbiviz files across your company, that Group Policy is the thing to check.

Sitting right next to the SDK switch is a second tenant setting, 'Add and use certified visuals only (block uncertified)'. When an admin enables it, only visuals that passed Microsoft's certification render; any AppSource visual or .pbiviz that isn't certified returns an error and refuses to draw, even though you were allowed to import it. This one is also disabled by default. The tell-tale sign is that the import succeeds - the icon appears in the pane - but the visual area shows an error instead of a chart. In Desktop the equivalent Group Policy value is EnableUncertifiedVisuals: 1 allows uncertified visuals, 0 enforces certified-only. There is a sanctioned escape hatch: neither the SDK setting nor the certified-only setting applies to visuals an admin publishes through the Organizational visuals (organizational store) tab. A Fabric admin can go to Admin portal > Organizational visuals > Add visual > From a file, upload the .pbiviz, and optionally 'Enable for Visualization Pane'. Org-store visuals deploy to Power BI Desktop automatically and bypass both restrictions, which is the clean way to approve one specific visual without opening the whole tenant. Note that Power BI Report Server does not support organizational visuals.

If you can import in the service but not in Power BI Desktop, this is usually it - and the mechanism changed, so old instructions mislead people. There is no registry hack and no Preview features toggle any more. In current Desktop, go to File > Options and settings > Options, and under the 'Current file' group select 'Report settings', then tick the 'Develop a visual' checkbox and select OK. Only after that does 'Import a visual from a file' work. The catch that trips everyone up: this setting stays enabled for the current session only. Close the file or restart Desktop and you must tick it again before importing. Once a .pbiviz is imported into a report it keeps working without the checkbox; you only need it at import time. This is separate from the live developer visual used with pbiviz start during development - for simply importing a finished .pbiviz file, the 'Develop a visual' checkbox is all you need.

'Get more visuals' opens the AppSource marketplace, and browsing AppSource generally requires you to be signed in to Power BI with a work or school account. If you are signed out, or signed in with a personal Microsoft account, AppSource browsing and any organizational-store visuals your company published will not appear, which reads as the option being unavailable. Sign in with your work account (top-right of Desktop or the service) and reopen the menu. Version matters too: keep Power BI Desktop updated to the latest release. Very old builds can lack the current menu layout or fail to render visuals compiled against a newer visuals API than the build understands - the fix is simply to update Desktop. If you use Power BI Report Server, you must use the matching 'Power BI Desktop for Report Server' client, and custom visuals only work on Report Server versions released after May 2021; upgrading the server to the latest build resolves most rendering issues.

A .pbiviz is a packaged (zipped) bundle, and the journey through a browser, email client, or SharePoint often damages it. Three things to check. First, the extension: make sure the file ends in exactly .pbiviz and not .pbiviz.zip, .zip, or .txt - some tools helpfully 'recognise' the zip and rename it. Do not unzip the file; Power BI imports the .pbiviz as-is. Second, Mark of the Web: files downloaded from the internet are often blocked by Windows. Right-click the .pbiviz, choose Properties, and if you see an 'Unblock' checkbox at the bottom of the General tab, tick it and select OK, then try the import again. Third, a truncated or corrupted download simply fails to import - re-download it from the original source. If you generated the visual with VizForge, re-download the .pbiviz from your dashboard to be sure you have an intact copy.

Report Server behaves differently from the service. A classic symptom: you select 'Import a visual from a file', the visual sits at a loading spinner, and it never appears. That happens because Power BI Desktop for Report Server tries to reach https://pbivisuals.powerbi.com on port 443 to fetch the latest copy of the visual, and if the machine is offline or a firewall blocks that host, the load fails (you may see a DNS-lookup error for pbivisuals.powerbi.com in logs). Fixes, in order: make sure the machine has internet access; if it does, allowlist https://pbivisuals.powerbi.com/; and if the machine genuinely cannot reach the internet, add a user environment variable named PBI_userFavoriteResourcePackagesEnabled set to 0, then restart Desktop - expect a 20-to-30-second delay on first load while it retries before falling back to the local copy. Remember the version floor from above (Report Server builds after May 2021), and that Report Server does not support organizational visuals, so the org-store workaround from Cause 2 is not available there.