Power Pages comes up in nearly every Dynamics 365 conversation I have these days, usually pitched by someone who saw a demo and now wants a customer portal, a supplier portal and a partner portal by the end of the quarter. Sometimes that is exactly the right call. Quite often it is a solution looking for a problem, and it ends up costing far more than the licence tab ever suggested it would.
Power Pages is Microsoft's low code platform for building external facing websites on top of Dataverse, the same data that sits behind your Dynamics 365 apps. It replaced the old Dynamics 365 Portals product a few years back, and it is genuinely a better tool than what came before. That does not mean it is the right tool for every self service problem someone hands you.
What Power Pages Actually Solves
The strongest use case is letting people outside your organisation see or touch a slice of Dataverse without you giving them a full Dynamics 365 licence or building an entire custom application. A customer checking the status of their support cases, a supplier updating their own bank details, a member renewing a subscription, all of that is a genuinely good fit because the data already lives where the portal needs to read and write it.
Where it gets interesting is authentication. You can let people sign in with an existing Microsoft, Google or LinkedIn account, or run your own local sign up flow entirely inside the portal, or trust an external identity provider you already run. Get this decision right early, because switching authentication providers after real customers have accounts is a genuinely painful migration, not a config change.
Self Service That Actually Reduces Support Load
The projects that pay for themselves are the boring ones. A landlord portal where tenants log their own repair requests instead of phoning. A distributor portal where partners check stock and place orders instead of emailing a rep. Every one of those interactions used to cost someone in your business five or ten minutes on the phone, and now it does not. That is a real, measurable saving you can put in front of a finance director, which is more than you can say for most digital transformation projects.
Where Power Pages Falls Over
The first thing that catches people out is licensing, and it genuinely is not as simple as "authenticated users cost more than anonymous ones." Power Pages is sold on page views for external users, with tiers that step up sharply once you go past a modest monthly allowance, alongside a separate per app or per login model for authenticated capacity. I cover the wider Dynamics 365 licensing picture properly in my licensing guide, but the short version for portals is to model your expected traffic honestly before you commit, not after the first invoice arrives.
The second thing is design. Power Pages templates look reasonable out of the box and fall apart the moment a client wants something that genuinely matches their brand, with custom layouts, bespoke components or anything beyond fairly standard forms and lists. You can get there with Liquid templating and custom CSS, and I have done it plenty of times, but budget for that work properly rather than assuming the low code label means low effort.
The Security Model You Cannot Skip
Every table you expose through a Power Page needs table permissions configured explicitly, on top of the security roles governing the rest of your Dynamics 365 environment. It is entirely possible to expose a table correctly to your internal users through security roles and then accidentally let an external portal user see records that were never meant for them, because the portal level permission was left too broad. Test this properly with an actual external test account before go live, not just as an internal admin who bypasses most of the checks anyway.
The Real Cost Conversation
I always have the same conversation with clients weighing up a Power Page against a bespoke web application: a portal built on Dataverse wins hands down when the data genuinely needs to live in Dynamics 365 and the interactions are largely forms, lists and status checks. It loses when the client actually wants a proper product with its own roadmap, its own design language and its own release cadence, because you will spend more time fighting the portal framework than you would have spent building something purpose built. I go through this trade off in more depth alongside general Dynamics 365 implementation costs, and it is worth doing the sums before anyone commits to a build.
My Honest Take
Power Pages earns its place when the goal is genuinely simple self service against data you already hold in Dataverse, and it is being sold as a shortcut far too often for projects that actually need a proper application. Ask what the portal needs to do in eighteen months, not just what it needs to do at launch, because that is usually where the real answer to build versus buy shows up.
If you are weighing up whether a Power Page is the right call for a customer or supplier facing project, or you have already built one that is starting to strain against what it was designed for, this is exactly the kind of decision I help clients work through in my Dynamics 365 consulting work.
