Guide · Power Pages and portals

Power Pages or a custom-built portal: how to choose

Assaf Semoun, Founder & CEO of Zooz-TechUpdated 19.11.20267 min read
In short

If your data already lives in Dynamics 365 or Dataverse, and the portal is mostly forms, a personal area and service requests, Power Pages will go live faster and is secure from the ground up. Custom development fits when the experience is the product itself, when the audience is very large, or when the data lives outside the Microsoft ecosystem. In between there is a third option that we use: a custom React front end on top of Power Pages and Dataverse, which gives you design freedom without giving up the platform's security model.

What exactly are we comparing?

A Power Pages portal is an external website that runs on Microsoft's platform and sits directly on Dataverse, the same data platform used by Dynamics 365 and Power Apps. Power Pages is part of Power Platform. Authentication, permissions, forms and hosting already exist, and you build on top of them.

A custom-built portal is an application your team writes from scratch, for example React or Next.js on the client side, an API layer on the server side and its own database. Every component is chosen and built for the need, and every component also needs maintenance.

We covered the capabilities and security layers of Power Pages in our guide to building a secure customer portal in Power Pages. Here we focus on the decision itself.

How fast does each option go live?

Power Pages is almost always faster. There is no need to build user management, an API layer, a permissions model or hosting. A form connected to a Dataverse table is configuration, not a project.

In custom development, all of these are work. The extra time pays off when the requirements go beyond what the platform offers, but it is worth knowing up front that this is the cost.

How does the portal connect to data and the CRM?

In Power Pages, the portal and the internal system share the same data. A request a customer opens in the portal appears immediately for the agent in Dynamics 365, with no sync and no extra copy.

In custom development there are two routes: keep the data in a separate database and sync it to the CRM, or read and write to the CRM through an API. Both work, and both add points of failure: queues, retries, conflicts and monitoring.

Connecting to systems such as Priority ERP or SAP is needed in both approaches. In Power Pages it is usually done through Power Automate or Azure services.

What does the security model look like in each approach?

Power Pages has three built-in layers. Authentication through Microsoft Entra External ID or Azure AD B2C. Web roles that determine who sees which pages. And table permissions that determine which user sees which records. Enforcement happens on the server and does not depend on code running in the browser.

In custom development you can use the same identity provider, but the authorization itself is written in code: every endpoint has to check who the user is and what they are allowed to do. That is more flexible, and also easier to get wrong. One forgotten check exposes another customer's data. That is why, in a custom portal, code review and security testing are a fixed part of every release.

How much freedom is there in design, performance and SEO?

Custom development gives complete freedom. Every screen and flow is built exactly as designed. Power Pages gives broad freedom within its framework: templates, CSS, Liquid and JavaScript. An experience that goes far beyond the framework starts fighting the platform.

On performance, Power Pages is hosted and managed by Microsoft. A lot of custom client-side code and heavy queries hurt it, so it is better to rely on the built-in capabilities. In custom development, performance and scale are in your hands, for better and for worse: both the design and the infrastructure.

Both approaches can meet the accessibility requirements of Israeli Standard IS 5568 (Israel's web accessibility standard, based on WCAG), and in both you need to test it in practice. For public pages that need to appear in search, Power Pages renders HTML on the server. A custom React app needs server-side rendering, for example with Next.js. In a personal area behind sign-in, SEO hardly matters.

How is the cost model structured?

Power Pages licensing is calculated per user per month, separately for authenticated users who sign in and anonymous users who browse the public pages. The cost grows with the number of users, so for a portal with a very large audience it is worth calculating it in advance.

Custom development has no per-user licensing, but it has hosting, a database, monitoring, security updates and developer time throughout the life of the system. The right comparison is the total cost over several years, not just the build cost.

Who maintains the portal after go-live?

In Power Pages, a low-code team can update content, forms, pages and permissions with the platform's tools. In custom development, every change goes through developers.

Application lifecycle management (ALM) exists in both approaches. In Power Pages you work with solutions, separate environments and Power Platform pipelines. In custom development you work with Git and a CI/CD pipeline. Code written with AI also needs to pass the same quality gates, as we explain on From vibe coding to production.

Vendor lock-in: Power Pages ties you to Dataverse and to Microsoft's licensing model. You can export the data, but the portal itself does not move to another platform. In custom development the code is yours, and the dependency shifts to the team that knows it.

What does the comparison look like in one table?

CriterionPower PagesCustom developmentHybrid
Time to go-liveShortestLongestIn between: data and permissions are ready, screens are written in code
CRM connectionDirect, on the same DataverseThrough an API or syncDirect, on the same Dataverse
SecurityBuilt in: web roles and table permissionsWritten and tested in codeBuilt in, enforced on the server
Design freedomBroad, within the frameworkCompleteNearly complete
Performance and scaleManaged by MicrosoftUnder your control and your responsibilityManaged, with careful query design
Cost modelLicensing per user per monthHosting, infrastructure and development timePer-user licensing, plus code maintenance
Who makes changesA low-code team tooDevelopersDevelopers, with data and permissions also in the platform's tools
Vendor lock-inHighLow on the platform, high on the teamHigh on data, lower on the front end

What is the hybrid approach?

Sometimes Power Pages fits the data and the security, but the standard components are not enough for the screens. Then you build a custom React front end that runs inside Power Pages and talks to Dataverse through the platform's Web API. Authentication and table permissions stay with Power Pages, and the experience is built in code.

That is how we built Ashtrom's quality control system: 39 screens in React, about 30 tables in Dataverse, 84 table permissions and more than 20 Power Automate flows, with a live connection to Priority ERP. A plant manager sees only their own plants, and enforcement happens on the server, not in the browser.

This approach requires deep knowledge of the platform. These are the four walls we hit, and how we got past them:

  • The Web API composes only one nested lookup. The solution: a read channel in Liquid FetchXML that still respects permissions.
  • Liquid breaks above 15 link-entities. The solution: a hop budget for each permission chain, measured per table.
  • Server Logic does not sign SAS tokens and is limited to 16KB. The solution: an Azure Function with a Managed Identity that issues the token.
  • A site upload deletes everything that does not exist locally. The solution: a deploy kit with sync, a pre-check and a post-upload check.

So which one should you choose?

Power Pages fits when:

  • The data already lives in Dynamics 365 or Dataverse.
  • The portal is mostly forms, a personal area, service requests and documents.
  • Going live quickly on a proven security model matters.
  • An internal team wants to update content and forms without developers.
  • The number of users is predictable, so licensing can be calculated in advance.

Custom development fits when:

  • The experience is the product, and the design goes far beyond a portal template.
  • The audience is very large, and per-user licensing makes the solution expensive.
  • The data lives outside the Microsoft ecosystem, and there is no plan to move it.
  • There is a permanent development team to maintain the code, the security and the infrastructure.

A hybrid approach fits when:

  • The data and the CRM are in Dataverse, but the screens are too complex for the standard components.
  • You need a rich mobile experience, such as photos, signatures and field work.
  • You want design freedom without rebuilding authentication and permissions.

Which portals have we built, and with which approach?

Israel Aerospace Industries (IAI) · the iCare portal: a Power Pages customer portal on Dynamics 365, with service requests, shipments and technical literature.

Mekorot (Israel's national water company) · Customer portal: a Power Pages portal on top of the Dynamics 365 CRM, adapted for mobile, with contact management synced with SAP.

HaShomer HaChadash · Two portals: a portal for instructors and a portal for parents in Power Pages, on Dynamics 365 and Dataverse as a single source of truth.

The Histadrut (Israel's General Federation of Labor) · New employee portal: an external portal with Azure B2C authentication, documents for signature and a personal area.

Reichman University · Dormitories portal: registration, payment through PayPlus and a digital contract on top of a CRM system. Sign-in with a one-time code sent by email, and about 10 seconds from payment to a contract ready for signature.

Ashtrom · Quality control: the hybrid example, a React front end on top of Power Pages and Dataverse with a live connection to Priority ERP.

Frequently asked questions

Can we start with Power Pages and move to custom development later?

Yes. The data stays in Dataverse, and a new front end can read and write it through an API. That is why it is worth designing the data model and permissions correctly from the start.

Can you build a React front end in Power Pages?

Yes. In Ashtrom's quality control system, Zooz-Tech built a React front end on top of Power Pages and Dataverse, and permissions are enforced on the server through table permissions.

How is Power Pages licensing calculated?

Per number of users per month, separately for authenticated users and anonymous users. For a portal with a large audience, calculate the cost in advance and compare it with the total cost of custom development.

Who can change the portal after go-live?

In Power Pages, a low-code team can update content, forms and pages with the platform's tools. In custom development, every change goes through developers and a deployment pipeline.

Can a Power Pages portal connect to Priority ERP or SAP?

Yes, through Power Automate or Azure services. At Ashtrom, the portal pulls live data from Priority ERP, which sits behind an on-premises data gateway.

Assaf Semoun
Assaf Semoun

Founder & CEO of Zooz-Tech, solutions architect, Microsoft 365 Architect Expert.

Torn between Power Pages and custom development?

Book a call