Power Pages lets you build secure, external-facing websites and portals for customers, partners, suppliers, applicants and members, connected to Microsoft Dataverse, Dynamics 365 and the rest of your systems. FlexiSolutions designs, develops and supports Power Pages portals that give external users a real self-service experience and your business the data, identity and process rigour it needs.
A quick orientation for people who already know the rest of the Microsoft Power Platform, and for people who don't.
See Power Platform overviewPower Pages is the portal capability of the Microsoft Power Platform. Where Power Apps and Power Automate are typically used by people inside your business, Power Pages is built for people outside it: customers, partners, suppliers, applicants, members. They need a secure, branded experience that connects to the data and processes you already run.
To the external user, a Power Pages site looks and behaves like a normal website. Underneath, it is a governed, secure application environment with structured data, configurable forms, lists, charts, workflows and integrations, delivered without the cost and lead time of a fully custom web application.
Every Power Pages site has a Microsoft Dataverse environment behind it. The portal is a controlled, secure view of that data, not a separate copy.
External users sign in with the identity model that fits your environment. Web roles, table permissions and row-level security control what each user can see and do.
Power Pages works alongside Power Apps, Power Automate, Dataverse, Dynamics 365 and the rest of the Microsoft ecosystem, not on its own.
Power Pages is not a marketing website builder, not a SharePoint extranet, and not a replacement for a custom-coded web application when one is genuinely required. It is a portal platform with a strong identity, data and process story, and that focus is what makes it the right answer for a specific set of problems.
Most organisations eventually need to give someone outside the business a controlled way to do something: see their data, submit a request, track an application, complete a process. Power Pages is the structured, governed version of that problem.
A large share of "where is my order?", "can I change my details?" and "I want to log a request" enquiries can be completed in a portal, but the existing website is brochure-only.
Documents, certificates, compliance forms, orders and updates are sent in unstructured email threads with no audit trail, no consistent process, and procurement chasing for what's missing.
Each new customer, supplier or applicant is processed manually, with version control issues, lost attachments and a slow turnaround that frustrates the external user.
The data exists, but giving external users even a filtered, read-only view requires significant custom development, or never happens at all.
Often the answer was SharePoint, a marketing site, or an under-used custom build, none of which gave the right combination of identity, data and process. The result is a half-finished site nobody is sure how to maintain.
Loan applications, grant requests, supplier onboarding, KYC and similar processes move slowly because external and internal parties have no shared, structured way to collaborate.
These problems are common because they sit at the boundary between the business and its customers, partners and suppliers, a place where off-the-shelf products rarely fit exactly, and full custom development is disproportionate. Power Pages is the in-between option that often fits the actual need.
We deliver Power Pages portals end-to-end: design, build, integrate, secure and support. The capabilities below are the ones we deliver most often; the specifics of any engagement are shaped by your business problem and the systems you already run.
External users sign in through the identity model that fits your environment: Microsoft Entra ID (B2B) for business-to-business scenarios, Microsoft Entra External ID for consumer-style sign-up and self-service registration, or a third-party identity provider. Azure AD B2C remains supported for existing customers but is no longer available for purchase by new customers. Web roles, table permissions and page-level access rules control what each user can see and do.
Forms and lists that read from and write to your existing data, with business rules, validation, conditional logic and lookup fields. The portal is a controlled window into the system, not a separate copy of it.
Multi-step processes where external users submit information, internal teams review and approve, and the system records the outcome. Power Automate handles the routing; the portal handles the experience.
Secure upload and download of supporting documents, with metadata captured into Dataverse and a clear audit trail. Suitable for onboarding, KYC, supplier compliance, insurance claims and similar use cases.
External users see their own data (orders, status, history, balances, documents) directly in the portal, with row-level security ensuring they only see their own records. Power BI can be embedded where richer reporting is required.
Custom themes aligned to your brand, with the option of self-service content updates for the teams that own marketing or service pages. Power Pages content snippets let non-technical users update copy without breaking the design.
Where a richer in-portal experience is required, a canvas Power App or a flow can be embedded to handle a specific case while the rest of the portal stays clean. Where data needs to be exchanged with back-office systems (ERP, finance, line-of-business apps), the portal connects through system integration patterns such as Dataverse, connectors, Azure Logic Apps or direct APIs, and we choose the route that fits the system in question.
Power Pages works particularly well where external users need to do something specific with your data, on an ongoing basis, with appropriate identity and access. The scenarios below are the ones we deliver most often.
Account holders sign in, see their orders, cases or service history, update their details, submit requests and track progress. The service desk stops being the first point of contact for routine enquiries.
New customers complete a structured onboarding journey: identity verification, document upload, account configuration, regulatory checks. The system records what was provided, by whom and when, and the internal team reviews a single queue rather than handling email attachments.
Suppliers register, maintain their company and compliance data, upload certificates, respond to qualification questionnaires, view open purchase orders and submit invoices or delivery documents. Procurement gains visibility without chasing by email.
Channel partners, resellers or franchisees access deal registration, training, marketing assets, pricing and support. The portal can be tied to Dynamics 365 Sales so partner managers see the partner's activity in context.
Members sign in, manage their profile, access resources, register for events, pay fees and engage with the association's services. Non-members can apply and be approved through a workflow.
Insurance claims, grant applications, registrations and similar processes move from email to a structured portal with full audit and status tracking.
For each of these, the design is shaped by your existing data model, your authentication requirements and the processes that already exist. We don't deliver portals from a template. We deliver them to fit the business.
A Power Pages portal is rarely a standalone investment. The real value comes from how it connects to the rest of the Microsoft environment you already run: Dataverse, Dynamics 365, Power Automate, Power Apps, Microsoft 365 and Azure.
Every Power Pages site has a Dataverse environment behind it. This is what makes a portal different from a regular website: data, security, business rules and integrations live in Dataverse, and the portal is the controlled external face for that data.
Where the business data is already in Dynamics 365 Sales, Customer Service, Field Service or Dynamics 365 Finance and Operations, a Power Pages portal can present a filtered, secure view of the same records to external users. This is often the answer to "how do we let customers see their cases without giving them a Dynamics 365 licence?"
Approval steps, notifications, status changes, document handling and integration with back-office systems are typically delivered as Power Automate flows, often triggered from portal activity.
Where a portal needs an internal counterpart, for example an internal team reviewing portal submissions on a mobile device, a canvas or model-driven Power App can sit alongside the portal and share the same Dataverse tables.
External notifications often go via Outlook or Teams. Identity is typically handled through Microsoft Entra ID for business-to-business scenarios or Microsoft Entra External ID for consumer-style sign-up and self-service registration. Azure AD B2C remains relevant for organisations that have already adopted it but is no longer available for purchase by new customers. Internal users continue to sign in through your normal Microsoft Entra ID.
For more complex integration, retrieval or aggregation, Azure Functions, Azure Logic Apps, Azure Service Bus, Azure Event Grid and Azure Key Vault can sit behind the portal, called through Power Automate or custom connectors.
The right combination is what makes a portal work. We design Power Pages solutions so that each of these components is used where it adds the most value, rather than treating Power Pages as an isolated product.
A portal is only as useful as it is trusted by your security and compliance team, and by your customers, partners and suppliers. We treat security, access and governance as a design decision rather than a checkbox.
External users sign in through the identity provider that fits your environment:
Multi-factor authentication and conditional access policies are applied where the design requires them.
Web roles and table permissions are configured against Dataverse, so users only see and do what their role allows. Row-level security means a customer in the portal only sees their own data, never another customer's. Page-level access rules control which pages and sections a user can reach.
Outbound connections from the portal to other systems use secure connection references. Secrets are stored in Dataverse environment variables, Azure Key Vault or the platform's secure connection store, never hard-coded in portal configuration.
DLP policies are defined and applied so the portal can only use the connectors and data sources it is meant to use. Power Pages connectors are managed in the same governance framework as the rest of the Power Platform estate.
We work in separate Dataverse environments for development, test and production, with solutions moved between them. This keeps the production environment stable and gives you proper change control. Configuration, customisations and code are stored in source control.
Portal activity, failed submissions and integration errors are logged and routed to a monitored channel so issues surface quickly rather than being absorbed by the business. Application Insights and Dataverse auditing are configured to fit your operational model.
Power Pages runs on Microsoft's security infrastructure, but no platform makes a portal automatically secure. That comes from design, configuration and the way the portal is integrated with the rest of your identity, data and governance environment. We build with that in mind from the first conversation. For a deeper treatment of the wider Power Platform governance work, see Governance & Security.
We work in stages, with each stage producing something visible and useful. Not every engagement goes through every stage, but the structure is consistent and follows the same methodology we use for other Power Platform solutions.
We start by understanding the audience for the portal, the business processes it must support, the systems it must connect to and the constraints it must respect. The output is a short brief that everyone agrees with before design begins.
For each user journey the portal must support, we map the current process, identify simplifications, and decide what belongs inside the portal, what belongs in a back-office system, and what still belongs in email. Sometimes the right answer is to redesign a process before automating it.
We confirm what the proposed solution requires from Dataverse, Dynamics 365, Microsoft Entra ID, Power Automate and any other systems, and we check the licensing implications against current Microsoft terms. We flag any constraints early.
The portal's information architecture, page structure, user roles, data model, integrations and security model are designed in detail. Where the design has trade-offs, we present them and get a decision.
We build in a development environment using Dataverse solutions, so configuration is portable and reviewable. The build is iterative: we show working pages early, so feedback is grounded in something real.
Functional testing, user-acceptance testing, accessibility testing and end-to-end integration testing, with a clear record of what was tested and the outcome. Security and permission testing is built in, not added at the end.
The portal is deployed to production, monitored through a settling-in period and handed over to your team with documentation, training and a clear support path.
We provide ongoing support and maintenance, monitor the portal's health and work with you on the changes a real portal always needs: new requirements, regulatory change, integrations with new systems.
Throughout the engagement, we are honest about scope, timeline and what the technology can and cannot do. A portal that has been properly scoped is cheaper to run and easier to evolve than one that was sold on features that never quite worked.
The right portal solution depends on what you are trying to achieve, what you already have and how much customisation you need. Power Pages is the right tool for a specific set of problems; it is not the right tool for everything.
SharePoint is excellent as an internal collaboration and document management tool. As an external-facing portal, it is rarely the right answer: external sharing has limits, the branding and user experience are constrained, and the access and audit story is harder to communicate to a security team.
Where SharePoint can be enough:
For internal portals with a small number of trusted external users and limited customisation needs, SharePoint can work. For real external-facing portals at any scale, Power Pages is the better fit.
Power Apps is built for internal and authenticated users inside the business; Power Pages is built for external users. The two are often used together: a Power App for the internal team, a Power Pages portal for the external audience, both reading and writing to the same Dataverse data.
The decision is usually about audience:
If the people using the application are inside your tenant, Power Apps is the right answer. If they are outside it, Power Pages is.
A fully custom build gives you unlimited control but at significant cost and lead time, and you have to build identity, access, audit and lifecycle management yourself. Power Pages delivers these capabilities out of the box, which is why it is often the more practical answer for a typical portal.
When a custom build is genuinely required:
Deep integration with systems that have no API, very specific user experience that Power Pages cannot match, or unique regulatory or hosting requirements. We will tell you when that is the case.
A marketing site is a publishing tool. A Power Pages portal is an application: it has data, identity, business rules and integrations. If you need to publish content for search engines, a marketing site is the right tool. If you need external users to do things with your business data, a portal is the right tool. They are not substitutes; many organisations use both.
The simplest test:
"Does the visitor need to read this, or do they need to do something?" Reading → marketing site. Doing → portal.
The right answer is the one that fits the problem and the constraints. We will tell you when Power Pages is not the right answer; that is part of how we work.
The benefits of a well-built Power Pages portal are real and measurable, but they depend on the problem the portal is solving and how the wider business uses it. We do not promise specific percentages or savings. We work with you to define what success looks like before the portal goes live, and we help you measure it afterwards.
Our approach
Agree the metric, deliver the portal, review the result. We do not quote percentages in advance because doing so produces numbers that are either padded to cover uncertainty or wrong.
Measured by ticket volume, first-contact resolution and call duration. Common for self-service portals.
Measured by time-to-onboard, time-to-approve and data-quality errors at intake.
External users enter data through a structured form with validation rather than by email or spreadsheet.
Who did what, when, with what data. Visible to your security and compliance team rather than reconstructed after the fact.
Measured by completion rate, time-to-complete, support requests related to the process and user feedback.
The cost of a Power Pages project depends on the design, not on the technology licensing in isolation. We work with you to understand the factors that drive cost and licensing, and we point you at current Microsoft guidance rather than quoting a price that will be wrong by the time you read it.
Power Pages is licensed per user, per website and per capacity, with different plans for authenticated users, anonymous users and internal admin users. The exact licence model for your engagement depends on the audience, the design and the data.
We assess the licensing implications of any specific design and refer you to Microsoft's current Power Pages licensing terms. Pricing shown elsewhere on this site covers our service fees, not Microsoft licence costs.
Ongoing support can be structured as a retainer, a fixed-fee package or per-engagement work, depending on what makes sense for your team. We agree the model up front and review it after the settling-in period.
We provide a tailored proposal once the brief is clear. We will not quote a fixed price before we understand the problem, because doing so produces a number that is either padded to cover uncertainty or wrong.
If your question is not here, contact us and we will answer it directly.
Power Pages is the low-code portal capability of the Microsoft Power Platform. It is used to build secure, external-facing websites and portals for customers, partners, suppliers, applicants and members that connect to Dataverse, Dynamics 365 and other business systems. To the external user it looks like a normal website; underneath, it is a controlled, governed application environment.
Power Apps is for people inside your business. Power Pages is for people outside it. They are often used together, with a Power Pages portal for the external audience and a Power App for the internal team, both reading and writing to the same Dataverse data. The audience, internal versus external, is usually the deciding factor.
SharePoint is built for internal collaboration and document management. As an external-facing portal, SharePoint has limits on branding, external sharing, security and audit. Power Pages is purpose-built for external users, with proper identity, role-based access and integration with Dataverse and Dynamics 365. For internal portals with a small number of trusted external users, SharePoint can be enough; for real external-facing portals at any scale, Power Pages is the better fit.
Yes, and this is one of the most common scenarios we deliver. A Power Pages portal can present a filtered, secure view of Dynamics 365 Sales, Customer Service, Field Service or Dynamics 365 Finance and Operations data to external users, with table permissions and row-level security applied. The external user does not need a Dynamics 365 licence; the data and business logic stay in Dynamics 365, and the portal is the controlled window.
Yes, through Dataverse, Power Automate, custom connectors, Azure Logic Apps, Azure Functions or direct APIs, a Power Pages portal can connect to most systems that expose an API or support a connector. Where a system has no API, we will tell you whether a portal is the right approach or whether the use case is better served by a Power App or a different integration pattern. See System Integration for the wider topic.
External users can sign in with Microsoft Entra ID for business-to-business scenarios, Microsoft Entra External ID for consumer-style sign-up and self-service registration, or a third-party identity provider. Azure AD B2C remains supported for organisations that have already adopted it but is no longer available for purchase by new customers. Multi-factor authentication and conditional access are applied where the design requires them. Internal users sign in through your normal Microsoft Entra ID. The choice depends on your audience, your existing identity infrastructure and the experience you want external users to have.
Security is built into the design: web roles, table permissions and column-level security in Dataverse, row-level security where required, secure connection references, secrets in Azure Key Vault or environment variables, and DLP policies that govern which connectors the portal can use. The portal can only do what its configuration and the wider governance framework allow it to do. We design for this from the first conversation.
It depends on scope. A focused, single-audience portal can be scoped and delivered in a matter of weeks. A multi-audience portal with deep Dynamics 365 integration, custom workflows, document handling, accessibility and multilingual support is a longer engagement. We commit to a properly scoped plan with stages you can see, rather than a number given before we understand the problem.
Yes. We start by reviewing the existing portal: its structure, data model, security model, integrations and the audience's experience. Then we identify what is working, what is not and what the most cost-effective path is. Sometimes the answer is a targeted improvement; sometimes it is a rebuild. We will tell you which, and why.
We provide ongoing support and maintenance, monitoring and a clear path for change. Portals are not static: they evolve with the business. We work with you to keep the portal healthy, current and aligned with what your users actually need.
Yes. Power Pages supports multiple languages for content and for the user interface, with the configuration work depending on the depth of localisation required. We agree the language scope as part of the brief, since localisation has both design and ongoing-maintenance implications.
Accessibility is built into the design: semantic HTML, ARIA where appropriate, keyboard navigation, colour contrast and testing against WCAG 2.1 AA where required. We test with assistive technologies as part of the build, not as a final review. The specific standard (WCAG 2.1 AA, EN 301 549 or another) is agreed with you up front.
Power Pages can be configured to handle sensitive and regulated data, but the design matters. The right combination of identity, authentication, data partitioning, audit and governance is what makes a portal safe for regulated use, and we design for that from the start. We will tell you during discovery whether the data you intend to expose is appropriate for a Power Pages portal, or whether it needs a different approach.
Power Pages is most often delivered alongside other Power Platform and integration services. If any of the following are part of your context, they are worth a conversation.
See how Power Pages fits alongside Power Apps, Power Automate, Power BI and Microsoft Copilot in the wider Power Platform ecosystem.
Where internal users need their own application alongside the external portal, we build the Power App counterpart that shares the same Dataverse data.
Approvals, notifications, status changes and back-office integration for your portal, delivered as Power Automate flows.
Connecting Power Pages to ERP, finance, CRM and line-of-business systems through the right integration pattern for each one.
Where the portal needs to read from or write to an ERP or finance system, including Microsoft Dynamics 365 Finance and Operations.
The wider Power Platform governance work that surrounds a Power Pages portal: environments, DLP, lifecycle management and access control.
We will start by listening. Tell us who the portal is for, what they need to do, which systems it must connect to and what is in the way today. We will come back with a clear view of the problem, the options and what we think the right next step is, including where appropriate when Power Pages is not the right answer.
Not the technology. We want to understand who the portal is for and what they need to do.
We will tell you when Power Pages is the right answer, and when it isn't.
A scoped plan, a real proposal and a path forward that fits your business.
