Microsoft Power PagesLet customers, partners or suppliers submit information, check progress and complete agreed actions online. We build Power Pages experiences around Dataverse records, clear access rules and the business process behind each page.
Design the portal around the user’s task and apply permissions to the records and fields behind it.
Present selected Dataverse information and collect structured submissions through configured forms and lists.
Configure supported identity providers and the appropriate signed-in or anonymous experience.
Use web roles, table permissions and relevant column controls to scope access.
Create responsive pages and branding using the design tools and code extensions appropriate to the site.
Connect submitted information to Dataverse apps and configured automation.
Use the documented Stripe payment integration where it fits, with the required setup and billing-event handling.
Choose a useful role for AI, then define the information, access and review needed for that role.
Use Copilot to propose site structure, page content and layout. Review the generated experience, accessibility and copy before delivery.
Add a configured Copilot Studio site agent using approved sources. Define authentication and tools before it accesses customer records.
Add AI Builder or Azure document processing to the backend workflow. It is a connected capability, with validation and review for uncertain fields.
Combine the agreed product configuration with the systems and development that make the complete experience work.
Guide a customer through application details, required qualified signing and provider-controlled payment.
Discuss Apply, Sign & Pay in One PortalLet customers submit cases, upload supporting information and view their own service history.
Discuss a Case Portal with Evidence & StatusGive members a portal for renewal and an optional Apple or Google Wallet membership pass.
Discuss Renew Membership & Add a Digital PassChoose an example to see the work, decision, handover and completion point.
Follow the work through the decision, handover and confirmed result.
Capture the required information under the agreed access model.
Approve the application and send the required qualified signing request.
Use the configured checkout and confirm the final provider event.
Update the business system and expose the confirmed status to the customer.
Measures to Agree
Started applications submitted with the required data.
Approved requests with validated signing evidence.
Verified payments against approved applications.
Time from completed prerequisites to activation.
Follow the work through the decision, handover and confirmed result.
Sign the customer in and resolve the permitted account context.
Collect structured details and the agreed supporting evidence.
Assign the service team and required service commitment.
Expose authorised status updates and the final resolution.
Measures to Agree
Requests containing the required issue details.
Contacts asking about a portal-visible status.
Time to the service team’s first response.
Time to the confirmed case outcome.
Follow the work through the decision, handover and confirmed result.
Show the signed-in member’s eligible renewal options.
Process checkout and verify the payment through the backend.
Confirm the new validity period in the membership system.
Provide an Add to Wallet link or update supported information on an issued pass.
Measures to Agree
Eligible renewals reaching confirmed membership status.
Renewals with unresolved payment status.
Eligible digital passes successfully generated.
Contacts about renewal or membership status.
Use the application that owns each record and make the handover between systems explicit.
Agree the business outcome, prepare the foundation and validate the complete experience before expanding it.
Choose the first process, its owner, completion criteria and baseline measures.
External user model, site capacity, record permissions, identity, payment setup and document handling need explicit design.
Configure or develop the agreed experience, permissions and system handovers.
Check realistic data, permissions, exceptions and confirmed outcomes. Prepare the team for a controlled launch.
Review source-confirmed results, operational issues and adoption before extending the next use case.
The starting point depends on the process and the systems you already use.
Access must be configured through the relevant web roles and table permissions. We test record isolation and any exposed fields against the intended customer, partner or anonymous access model.
Start with a specific task and the evidence needed to evaluate it. We check current feature status, environment prerequisites, data quality, permissions and cost. Preview capabilities are assessed separately from the agreed production scope.
The examples describe configured or custom solutions. The feature cards explain the product or delivery foundation; each use case and process identifies the connections, development and related services it needs.
External user model, site capacity, record permissions, identity, payment setup and document handling need explicit design. We also agree ownership, acceptance criteria, operating responsibility and the first measurable outcome.
Explore the applications, data platforms, and development capabilities that can support your requirements.
Browse practical use cases for payments, subscriptions, portals, approvals, customer communications, and connected operations.
Tell us where customers or teams lose time, context or a clear next action. We’ll help identify a practical starting point for Microsoft Power Pages.