A portal on your domain and with your brand, built on the reports already in your Power BI. Pro adds the user provisioning API, capacity auto-suspend, automatic history retention, Google sign-in and a Jump team from the first login onward.
View-only users don't need a Power BI Pro license. The Microsoft capacity is purchased separately, directly from Microsoft.
Every screen the User profile sees, with your brand and on your domain. Click the workspaces, open reports, send a chat message and request access to anything locked.
Interactive preview with sample data, in the User profile. In the real portal, the reports are yours, from Power BI, with the model's RLS.
Four features only Pro has and two services from Jump. Each one takes on a job that, in Community, stays with your team.
Jump sets up Azure, the Service Principal, the capacity, the catalog and your brand with you. Portal live in [IMPLEMENTATION TIMELINE].
A team that knows the code and Power BI Embedded, responding within [SUPPORT SLA].
Your system creates users in the portal with an API key. No one creates accounts by hand.
The capacity pauses on its own so it isn't left running for nothing. On pay-as-you-go capacity, paused time isn't billed.
Access and admin histories follow a retention rule, with no manual cleanup.
Besides local and Microsoft sign-in, your users sign in with their Google account.
Configurable domain, brand and theme, including in emails. All of this comes with Pro.
A catalog of the workspaces and reports that already exist in your Power BI, with the model's own RLS roles applied on every access.
Each report has its own chat between portal users, with notifications for whoever needs to follow along.
Who accessed, what they opened and what changed in administration. On the operations side, dataset refreshes and the capacity status.
No report is migrated or rewritten. JHub embeds what is already published in your Power BI.
How many users, which workspaces, which systems will provision access.
Jump connects Azure, the Service Principal and the capacity, and builds the catalog.
Provisioning API, brand, theme, profiles, groups and RLS roles.
Unlimited portal users, auto-suspend on and Jump on support.
The portal is the same in both editions. Pro adds four features, plus implementation and support from Jump. The Microsoft capacity is purchased separately, directly from Microsoft.
| Feature | Pro | Community |
|---|---|---|
| JUMP SERVICES | ||
| Implementation | ✓ | — |
| Support | Jump, [SLA] | Community |
| PRO ONLY | ||
| User provisioning API with API key | ✓ | — |
| Capacity auto-suspend | ✓ | — |
| Automatic history retention | ✓ | — |
| Google sign-in | ✓ | — |
| PORTAL, IN BOTH EDITIONS | ||
| Your own domain, brand and theme, including in emails | ✓ | ✓ |
| Unlimited users, no Power BI Pro license for view-only users | ✓ | ✓ |
| Catalog, favorites and PDF export per profile | ✓ | ✓ |
| Profiles, groups and RLS by Power BI roles | ✓ | ✓ |
| Local and Microsoft sign-in, authorized domains, import from Azure AD and via CSV | ✓ | ✓ |
| Per-report chat, notifications and access requests | ✓ | ✓ |
| Access, admin and refresh histories, with spreadsheet export | ✓ | ✓ |
| Automatic daily dataset refresh and on-demand refresh | ✓ | ✓ |
| Capacity status, with manual pause and resume | ✓ | ✓ |
| Self-host on your infrastructure (Docker image) | ✓ | ✓ |
The table lists what exists today. A feature that isn't listed here isn't available in either edition.
Implementation by Jump, with Azure, Service Principal, capacity, catalog and brand set up with you, and support from Jump within [SUPPORT SLA]. In the software, Pro adds the provisioning API, capacity auto-suspend, automatic history retention and Google sign-in.
No. In the App Owns Data model, users who only view content in the portal don't need a Power BI Pro license: the Microsoft capacity covers access. People who create and publish reports still need their own license.
Yes. The workspaces shown must be on a dedicated capacity (Fabric F, Embedded A or Premium P). Workspaces on PPU don't work, because PPU is an individual license. During implementation, Jump checks this with you.
Nothing. Reports stay in the Power BI Service and JHub embeds them in the portal. Development, gateways and publishing stay as they are, and no report is migrated.
Through three layers: the portal's profiles and groups, the RLS roles of the Power BI model itself, and sign-in (local, Microsoft or Google) restricted to authorized email domains. Every access and every admin action is logged in the history.
Talk to us to size Pro: implementation, integration and support from Jump.