Business Applications

    Customer portals on Power Pages: requests, cases, own data.

    Customers, partners and members handle requests, enquiries and address changes in the portal themselves. What they submit reaches your team as a record in Dataverse.

    For companies, associations and funding bodies whose customers, partners or members should submit requests and concerns online themselves.

    • Power Pages
    • Dataverse
    • Microsoft Entra External ID
    • Power Automate
    • Power Apps
    • Copilot Studio
    A front door in the old town with a portal screen, a form on a phone lands as a card in the card index inside
    01

    An application on Sunday evening

    Sunday evening. The president of an association submits a funding application in the portal, with budget and attachments, and then sees that it has been received. On Monday the office reviews the application in its app and asks a question, and the answer comes back through the portal. Both sides work on the same record and see the same status.

    02

    Portals for requests, cases and partners

    Every portal starts with a transaction that external people trigger today by email, form or phone, and with the question of who may see which records. We build that transaction first, with your team and with test accounts for every role, and add more afterwards. The following portals are examples of this:

    • Application portalApplicants complete a guided form with required fields and attachments, save a draft and submit it; questions and the decision appear in the same portal, and your team handles the application in an app.Result: applicants can see at any time where their application stands.
    • Customer portal with casesA customer reports an issue about her installation or contract, follows the case and reads your team's replies; a workflow assigns the case to the right team.Result: customer and team see the same case with the same history.
    • Partner portalInstallation partners or dealers see their company's orders, report progress and upload acceptance reports; a company's contact person invites further colleagues on their own.Result: every partner sees their company's orders and only those.
    • Self-service for own dataMembers or customers change their address and contacts, register for events and download certificates; sensitive changes go through a check before they are applied.Result: master data is maintained by the people who know it best.
    • Data from business systemsInvoices, contracts or meter readings from the ERP appear in the portal through a connection to Dataverse, and changes flow back according to an agreed rule.Result: customers find their invoice or contract themselves.
    03

    Before the first external account

    One transaction with owners: who submits, who processes it internally, which statuses exist and what happens after a rejection. The groups that sign in, and how: with Microsoft Entra External ID, with an existing company account or by invitation. For personal data of external users you decide what is stored, how long it is kept and who sees it.

    04

    Accepted from the customer's side

    A portal in your production environment, tested with accounts from every role: each test user submits, follows the status and tries to open other people's records. Plus the Power Pages security scan across authenticated pages and the Web Application Firewall in front of the portal. One person on your team maintains content, roles and invitations, and day-to-day operation can go to our support and operations team.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 9 October 2026

    • As of 14 August 2026

      Power Pages is licensed by users per website and month.

      Authenticated users count once per calendar month and website, identified by their contact record in Dataverse; Power Pages recognises anonymous users by a browser cookie. Both are available as capacity packs or pay-as-you-go. Anyone who only opens the sign-in page does not count as anonymous, and people with Power Apps Premium may use any number of portals.

      Source: Microsoft Learn: Power Platform licensing FAQs
    • As of 18 June 2026

      The Web Application Firewall protects production portals.

      It runs on Azure Front Door in prevention mode and uses managed rules to block cross-site scripting and session fixation, among other attacks. Custom rules allow or block requests by country, IP address or page address and limit the request rate. Trial sites are excluded, and with the firewall on, custom rules take over from the site's IP restrictions.

      Source: Microsoft Learn: Web Application Firewall overview
    • Preview since 30 April 2026

      A security agent suggests web roles and permissions.

      In the security workspace of the design studio, the agent reviews sign-in settings and suggests an access level for each table, such as read-only or own records only. Every change needs explicit confirmation. Microsoft had announced general availability for August 2026; since September 2026 new capabilities appear in the AI at Work roadmap.

      Source: Microsoft Learn: Configure authentication with security agent

    External users on shared data.

    Partners who work on the same Dataverse foundation as the internal team at AEW myHome, and coupons that AEW customers redeem through a web portal, with shared reporting.

    Before external users sign in to the portal.

    How do we make sure nobody sees other people's data?

    The portal only shows records once a table permission grants them to a web role. For each table we decide whether a person sees only their own records, those of their company or all of them, and we check this with test accounts that deliberately request other people's records.

    How do customers without a Microsoft account sign in?

    Through Microsoft Entra External ID, with email and password or with a one-time code sent by email. Partners with their own Microsoft 365 tenant sign in with their company account. Whether people register on their own or only get access by invitation, you decide per portal.

    What counts for the licence?

    The number of people who sign in during a calendar month, and of anonymous visitors, each per website. Someone who signs in several times counts once. If the portal is protected except for the sign-in page, no licence for anonymous visitors is needed. We estimate the expected use with you before the build.

    Can we take over an existing portal?

    Yes. Portals from the days of Dynamics 365 Portals or Power Apps portals continue today as Power Pages. We review web roles, table permissions and sign-in methods, bring the data model up to date and keep what has proven itself.

    Can an agent in the portal answer questions?

    Yes. An agent from Copilot Studio can be added to the portal, and web roles decide who uses it. It answers questions about your services and can prepare a request so that it reaches your team as a case. Which sources it uses and what it does not do, we define together.

    When does a web application of our own fit better?

    When the interface, logic or integrations go beyond what Power Pages covers well with forms, lists and the Web API. We have written up the comparison on its own page, and Dataverse often remains the data foundation underneath.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.