01
Bound the package
Reject traversal, encryption, case collisions, suspicious ratios, oversized entries, and malformed ZIP records before metadata inflation.
VizForge Verify / free static scan
Know what's inside your visual.
Drop in a compiled Power BI custom visual. Get a bounded package inventory, capability checks, and an honest AppSource-readiness preflight—without sending the file to VizForge.
Browser-only inspection No Desktop claim 32 MB maximum
Local inspection bay
Select one .pbiviz package
FILE CONTENTS STAY LOCAL
01ZIP bounds02Metadata03Role mappings04Privileges05Code signals
The package is processed in this browser tab. Site analytics may record a page visit, but the selected file and its inspection result are not sent to VizForge.
What the browser can prove
A useful preflight has hard edges.
The inspector reads only the evidence available in a compiled package. Every boundary stays visible in the result.
02
Read the contract
Inventory visual identity, API target, data roles, DataView mappings, format objects, and declared privileges from compiled metadata.
03
Surface static signals
Look for WebAccess, external scripts, blocked browser calls, interaction plumbing, accessibility hooks, and data-reduction rules.
Evidence boundary
Static readiness is not runtime verification.
A package can look sound and still fail with real data, keyboard interaction, high contrast, export, or performance. Connected model tests, Desktop rendering, source-license review, and Microsoft approval remain separate gates.
See VizForge's quality modelPlain-language answers
Before you inspect.
Does VizForge upload my .pbiviz file?
No. The selected package is read and inspected by JavaScript in your browser. VizForge does not send its contents to an inspection API.
Does a passing scan mean my visual is Microsoft certified?
No. The inspector reports static preflight evidence only. Microsoft controls publication to Microsoft Marketplace (formerly AppSource) and certification, and runtime behavior still needs accessibility, interaction, performance, and Power BI Desktop testing.
What does the inspector read?
It validates the bounded ZIP structure, then reads package.json and the compiled .pbiviz.json resource to inventory metadata, capabilities, data roles, formatting objects, privileges, and selected compiled-code signals.
Can the inspector verify my visual against a semantic model?
No. A standalone .pbiviz contains no customer model or report binding. Connected-model and Desktop-render badges are therefore shown as not applicable or not run.
Fix what the inspector finds
If the inspector flags a problem, or the visual imports but misbehaves, these guides walk through the usual causes and fixes.
Free tool
Will it work in your tenant?Verdict per scenario with the admin steps and an admin pack.
Troubleshooting
Custom visual not showingNo data, admin blocks, API mismatches and slow visuals.
Troubleshooting
Can’t import a .pbivizTenant settings, certified-only mode and blocked files.
Troubleshooting
Report Server compatibilityDesktop release, visuals-API version and offline installs.
Security
Are custom visuals safe?What a .pbiviz can access, certification and admin controls.
Developers
pbiviz build errorsTwelve common pbiviz errors and the fix for each.
VizForge
Quality SLAHow VizForge checks the visuals it generates.
Rather own a visual you can read end to end?
VizForge generates Power BI custom visuals from a plain-English brief and gives you the .pbiviz together with its TypeScript source, so every API call and permission is yours to review.
Generate a custom visual with AI · starts free →