Many companies still run a customer or partner portal built years ago on Power Apps Portals: page templates, web forms, entity lists, content snippets, and a data model dictated by a Dynamics 365 module. It works, but every change is slow and the screens look dated.
Why the old portal feels stuck
- The UI is bound to template constructs, so a redesign means fighting the platform.
- The data model follows D365 module tables instead of your business.
- Changes are made by hand in a maker session, with no clear history.
What changed in 2026
Power Pages now supports single-page applications in general availability (since February 8, 2026, site version 9.8.1.x and later). The old portal constructs become optional implementation details, not architectural constraints. Your UI can be fully custom and call Power Pages Web APIs for data.
How we approach a migration
- Map what the current portal actually does: who signs in, what they see, what they submit.
- Keep the rows you already have in Dataverse. A release moves the system, not your data.
- Rebuild the screens as a modern front end, deployed with the Power Platform CLI.
- Put everything in a DevOps repo with a pipeline, so production changes wait for your approval.
Background: Microsoft’s Breaking the Shackles of Legacy Portals: Power Pages as Enterprise SaaS (April 2026) describes the approach we follow.
Talk it through with us
The first conversation is free. No deck, no commitment, and we’ll turn over your NDA within one day. We build in your Microsoft tenant, on your licenses, and you keep the code.
help@enterpl.ai · (858) 585-9680 · How we work in your tenant