Blazor framework + Fluent UI components for Dataverse
Build smarter, faster, and cleaner with Power Portals Pro—a framework of tools and components designed to supercharge Microsoft Dataverse. Skip the complexity and launch a fully working custom portal in record time, without sacrificing flexibility, scalability or performance.
Power Portals Pro gives you production-ready Blazor components that read and save form data back to Microsoft Dataverse. Controls configure themselves using Dataverse metadata (labels, tooltips, required/constraints), and the framework makes localization and translation straightforward.
<RecordContext/>
<Section/>
<SectionColumn HeaderText="Account Info"/>
<ColumnEdit ColumnName="name" //>
<ColumnEdit ColumnName="telephone1" //>
<ColumnEdit ColumnName="websiteurl" //>
<ColumnEdit ColumnName="parentaccountid" //>
<ColumnEdit ColumnName="tickersymbol" //>
</SectionColumn/>
<SectionColumn HeaderText="Primary Contact"/>
<LookupRecordContext ColumnName="primarycontactid"/>
<Section/>
<ColumnEdit ColumnName="firstname" //>
<ColumnEdit ColumnName="lastname" //>
<ColumnEdit ColumnName="emailaddress1" //>
<ColumnEdit ColumnName="mobilephone" //>
<ColumnEdit ColumnName="jobtitle" //>
</Section/>
</LookupRecordContext/>
</SectionColumn/>
</Section/>
<SubGrid RelationshipName="contact_customer_accounts" //>
</RecordContext/>
Power Portals Pro components automatically configure themselves using Dataverse metadata—so you spend less time wiring labels, tooltips, required rules, and constraints, and more time shipping portal experiences.
Built on ASP.NET Core Identity and authentication. Users are created as Contacts and use the same Contact fields Power Pages uses. Supports local username/password plus Microsoft Entra ID (Azure AD), Google, and other providers supported by ASP.NET Core.
Labels, tooltips, required flags, min/max, and length constraints come from Dataverse—consistent across pages.
Build pages that load records and persist changes back to Dataverse using a clean, reusable pattern.
A configurable grid component that can act as a sub-grid to display related records.
When users save, Power Portals Pro persists all changes—form fields plus grid/sub-grid edits—in a single Dataverse transaction, so updates are atomic (everything succeeds or everything rolls back). And because you’re building a true custom portal on ASP.NET Core Blazor, you can use the full .NET ecosystem and any capabilities available to a standard Blazor project (libraries, middleware, authentication providers, logging, background services, and more).
Modern component model, enterprise-friendly UI system, and a clean developer experience.
Constraints and required rules flow through so forms behave the way Dataverse expects.
Built-in capabilities that make it easier to plan for multiple languages and translated experiences.
A practical set of field editors for building Dataverse-backed forms quickly.
Single-line text with Dataverse constraints (required/length).
Multi-line text, with max length and helpful UX defaults.
Numeric input honoring Dataverse min/max and formatting.
Currency input aligned to Dataverse precision and rules.
Two-option boolean editor with correct labels/tooltips.
Option sets rendered as the right Fluent UI pattern.
Date/time editor consistent with Dataverse behavior.
Lookup selection for related tables with a portal-friendly UX.
Manage N:N relationships without custom plumbing.
Upload file fields while keeping the experience consistent.
Image upload/edit experience for Dataverse image columns.
Configurable grid to show and manage related records.
A clean flow from Dataverse metadata to a polished, working portal page.
Bind editors to Dataverse entities and attributes (columns).
Editors pull label/tooltips and enforce required + constraints automatically.
Submit changes reliably with patterns that match Dataverse expectations.
$149 per month. One product, continuous updates.
Framework + components for Dataverse portals
Answers tailored to Dataverse portal builders.
Editors and grids use Dataverse metadata to configure labels and tooltips, and to enforce constraints like required fields, min/max values, and length limits—so your portal stays consistent with your data model.
Power Portals Pro is built on Microsoft Blazor and uses the Fluent UI design system for a modern, consistent enterprise look and feel.
Yes. The grid component can be configured as a sub-grid to display related records (for example, child contacts on an account).
The framework includes capabilities that make it easier to design for localization and translation from day one (labels/content can be planned to vary by language and region).
Yes. Power Portals Pro includes authentication and authorization using ASP.NET Core Identity. Portal users are created as Dataverse Contacts and use the same Contact fields that Power Pages uses, making the model familiar for Dataverse portal scenarios.
Power Portals Pro supports local authentication (username/password) and external identity providers such as Microsoft Entra ID (Azure AD), Google, and other providers supported by ASP.NET Core authentication.
No. Power Portals Pro does not require Power Pages to be enabled in your environment. Because you’re not using Power Pages, there are no Power Pages-related licensing costs.
Power Portals Pro is a Blazor + Fluent UI framework and component set for building a custom portal that integrates with Dataverse. It uses ASP.NET Core Identity (users as Contacts, using familiar Contact fields) and does not require Power Pages to be enabled—so you avoid Power Pages licensing costs.
Start Power Portals Pro for $149/mo.