Renting AppSource Visuals vs Owning Your .pbiviz (2026)

Most paid visuals on Microsoft AppSource use an in-app-purchase (IAP) model: the visual installs free with a limited basic version, and the full feature set unlocks with a paid license. You buy the license in AppSource with a credit card, then assign it to users in the Microsoft 365 admin center; anyone can purchase, and the buyer is auto-assigned a seat. Two things make this a rental rather than a purchase. First, it is a subscription tied to a seat: Microsoft's own FAQ notes you get a full refund only if you cancel within seven days, and multi-year purchases are not supported — you renew a year at a time. Second, licensing is per user: viewers who do not have an assigned license generally see the unlicensed state rather than the paid visual. Updates are outside your control too — AppSource visuals update automatically whenever the publisher ships a new version.

If a license is missing, partial, or expired, Microsoft documents several fallbacks: an unlicensed icon in the visual's corner, an upgrade banner, a watermark on paid features, or — in the strongest case — the visual does not render at all and instead shows a button to get a license or contact the report owner. So a lapsed subscription does not merely remove new features; it can blank the visual in a live report. Deprecation is the sharper version of the same risk. Because the publisher controls the version and can retire it, a visual you built dashboards around can reach end-of-life on the vendor's timetable, not yours. A concrete, recent example: OKVIZ retired the original Synoptic Panel (v1). Its documentation lists the retirement date as April 10, 2026 and states that "After the retirement date ... Synoptic Panel v1 will no longer work in your reports and you will see messages indicating that the visual is not available." There is a migration path — a rewritten v2, better in many ways, and existing maps keep working — but v1 and v2 are not fully feature-compatible, and the timing was the vendor's to set.

Renting from an established ISV is not just a cost — it buys real things, and an honest comparison has to credit them. Many AppSource visuals are Microsoft-certified, meaning Microsoft reviewed the code and verified it makes no external service calls (no HTTP, WebSocket, or fetch to outside endpoints). Certified visuals carry a badge and, importantly, are supported in export to PowerPoint and PDF and in email subscriptions — uncertified visuals can fail to render in those export paths. You also get a maintained product: bug fixes, new features, security patches, compatibility work as Power BI's APIs change, and a support channel to escalate to. For a mission-critical visual with deep, specialized functionality, that ongoing engineering and accountability is often worth paying for.

A generated .pbiviz is a file you own outright. You import it into a report (or upload it to your organization's visuals), and it renders with no license server, no per-user seat, and no runtime fee — it keeps working whether or not you ever pay again. Crucially, you also hold the full TypeScript source, so the visual can be read, audited, forked, and changed on your schedule instead of a vendor's. That ownership has honest tradeoffs. You are now the maintainer: when Microsoft advances the powerbi-visuals-api, you (or a tool) recompile and re-import. An owned visual is uncertified by default, so unless you submit it for certification it inherits the same export-to-PowerPoint/PDF caveat as any uncertified visual. And there is no vendor hotline — support is you plus whatever tooling generated it. Owning trades a recurring bill and lock-in for self-reliance.

The math is structural, not about any single vendor's sticker price — which is exactly why we will not quote specific vendor prices here; check each listing's Plans + Pricing tab. A rented visual's cost is roughly price-per-user × number of licensed users × every year it stays in use. Because it is per-seat and renews annually, cost scales with your audience and never reaches zero: a visual seen by hundreds of report consumers can require hundreds of seats, indefinitely. An owned visual inverts that — a one-time cost to generate it, then no per-seat multiplier and no renewal. Against that you carry occasional maintenance effort (recompiling for API changes) and, if you need them, the cost of certification or your own testing. For a niche visual used by a few authors, a yearly seat cost may be trivial and renting is simplest. For a visual rolled out across a large audience or kept for years, owning usually wins on total cost — and removes the lapse-and-it-stops-working failure mode entirely.

Rent when you need a specific vendor's proven feature depth right now, when certification and export-to-PowerPoint support are non-negotiable out of the box, when you want someone else on the hook for maintenance and support, or when the audience is small enough that per-seat pricing is a rounding error. Own when cost matters at scale, when longevity matters (a report that must still open in five years should not depend on a subscription that can lapse or a version that can be retired), when you need customization the vendor will not build, or when governance requires that you hold and can audit the source. Many teams do both: rent the one or two deep, specialized visuals a vendor does best, and own the long tail of charts, KPIs, and slicers they would otherwise rent forever.