Quick Answer
When a business unit asks for a supplier or claimant portal and somebody in the room says the company already pays for Microsoft 365 so this should be free, the answer as of September 2026 is that it is not free, and Microsoft settles it in a table rather than leaving it to inference: in the Power Platform Licensing Guide, September 2026 edition, page 18, the table of Power Pages use rights included with other licences carries the row “Microsoft 365 / Office 365” against the value “None”. A Microsoft 365 or Office 365 subscription therefore carries no right to run a Power Pages site, and Power Pages is a separate budget line. What it is billed on is not seats in your employee directory. Microsoft states that “Power Pages licensing is based on two user types, authenticated users per website /month and anonymous users per website/month” and that “Sufficient user capacity must be assigned to the environment to cover the total number of unique users who access the website/month” (Power Platform Licensing Guide, September 2026, page 16). So the decision in front of you is not whether to budget for Power Pages but which of the two audience meters your portal’s users fall under, how many unique people reach the site in a month, and which environment that capacity has to be assigned to. Two exceptions change the arithmetic before you take this to finance, and both are licences you may already hold: a Power Apps Premium licence and the Dynamics 365 Enterprise and Premium apps carry Power Pages use rights of their own, bounded by environment (page 18).
What your Microsoft 365 subscription actually carries here
If somebody has already told your finance partner that the renewal covers this, the fastest way to close the question is to show them where the vendor draws the line rather than to argue about it. Microsoft does grant some Power Platform rights to Microsoft 365 licence holders, and the guide says so plainly: “Limited Power Platform use rights are included with select Dynamics 365, Microsoft/Office 365 and Windows licenses” (Power Platform Licensing Guide, September 2026, page 5). The question is which rights, and Power Pages is not among them. Page 18’s table of Power Pages use rights lists “Microsoft 365 / Office 365” as “None”.
The guide’s own appendix corroborates it, and it is worth naming exactly which part, because page 29 carries two tables that look alike. The first, “Dynamics 365 – Limited Use Rights Included with Qualifying License”, has a Power Pages column, and a number of Dynamics 365 licences are marked in it. The second, “Microsoft 365*, Office 365, and Windows – Limited Use Rights Included with Qualifying License”, has columns for Power Apps, Power Automate cloud flow, Power Automate desktop flow and Dataverse for Teams, and no Power Pages column at all. The affirmative answer is the “None” on page 18; the appendix is the corroboration, not the argument.
This page assumes you have already decided a portal is the right shape. If that is still open, the capability question is answered on What Is Microsoft Power Pages?, which owns it.
Who counts as a billable user on an external portal
When a portal is being scoped, the number that decides the budget is almost never the number of employees who will administer it, and that is where estimates go wrong. Microsoft defines the two populations it counts. “Power Pages authenticated users are users who obtain secure access to a website by logging in through an authentication provider on the website.” “Power Pages anonymous users are users who access a website and do not log in.” Both definitions are on page 16 of the September 2026 guide. The unit in both cases is per website per month, and the guide’s pay-as-you-go meter definition says the same thing in measurement terms: “A measure of the number of unique authenticated users per website per month” (page 17).
Three consequences follow that a budget owner should carry into the conversation. Capacity is assigned to an environment, not handed to named individuals: the guide notes that authenticated user capacity “needs to be assigned to an environment”, and that anonymous capacity packs “do not need to be assigned to individual users. These capacities are assigned to an environment” (pages 16 and 17). Capacity does not bank: “Unused capacity does not carry over to the next month” (page 16). And the two purchasing routes do not mix, so the choice is made once per environment rather than tuned later: “Power Pages subscription licenses cannot be used in a pay-as-you-go environment” (page 17).
The boundary case is the one that catches people. An employee who already holds a Microsoft 365 licence and who signs in to your external portal is an authenticated user of that website. The Microsoft 365 licence they hold carries “None” for Power Pages use rights (page 18), so it does not exempt them from the site’s authenticated capacity. If your internal reviewers work inside the portal alongside your suppliers, they are in the count.
i3solutions builds secure external Power Pages portals for regulated enterprises, owning authentication, role-based access, data protection, and audit evidence rather than handing over a template. Which of your populations ends up authenticated and which anonymous is a design decision taken during scoping, and it moves the number.
The three questions that decide your number before anyone quotes you
If you are being asked for a figure this week and nobody can yet tell you who will use the portal, these are the three answers to get before a number leaves your desk. None of them requires a vendor conversation, and each one changes the meter.
- Who signs in, and who does not? Authenticated and anonymous are separate meters with separate capacity, counted per website per month (Power Platform Licensing Guide, September 2026, pages 16 and 17). A portal where suppliers log in to submit documents and the public reads a status page is consuming both. Settle the split by population before anyone sizes it.
- How many unique people reach the site in a month, not how many accounts exist? The guide’s requirement is capacity “to cover the total number of unique users who access the website/month” (page 16), and unused capacity does not carry to the next month (page 16). A directory of ten thousand dormant supplier accounts and four hundred monthly actual users are very different numbers, and the second one is the one that is counted.
- Which environment does this site live in, and what else lives there? Capacity is assigned to an environment (pages 16 and 17), and use rights that arrive with a Power Apps Premium or a Dynamics 365 Enterprise licence are “limited to the same environment as the Power Apps and Dynamics Enterprise Apps” (page 18). Where a Dynamics 365 Enterprise licence is carrying the entitlement, the guide also keeps the restricted-table rules in force: “restricted tables and the associated Dynamics 365 license requirements for users who create, update, or delete data stored within these tables remain in place” (page 18). An environment decision made for convenience can quietly forfeit an entitlement you already paid for.
i3solutions designs and builds Power Pages sites with senior, US-based engineers and the table-permission, web-role, and governance model an external site requires. Those three answers are the first thing a scoping conversation establishes, because the rest of the design rests on them.
The published capacity-pack figures, and one specific pattern in which a portal reduces licensing cost elsewhere in the estate, are set out on Can Power Pages Reduce ERP Customization and Licensing Costs at the Same Time? Yes, in One Specific Pattern, which owns that arithmetic. This page deliberately does not restate it.
What changes in a government cloud
If your portal has to stand up in a government cloud tenant, stop before you reuse a commercial estimate, because the document that settles the commercial answer does not speak to your case. The Power Platform Licensing Guide, September 2026 edition, addresses government clouds nowhere in its thirty pages; a full-text scan of the edition cited throughout this page returns no occurrence of “Government”, “GCC” or “US Gov”, against eighty-two occurrences of “Power Pages” in the same scan, so the silence is the document’s and not a reading error. The entitlement logic above is the commercial-cloud position.
For a government tenant the method is the same and the sources are different: read the plans and entitlements your own tenant already carries in your own cloud’s admin centre, and price against the terms that govern that cloud rather than the commercial list. The worked arithmetic for a government cloud, for the adjacent product, is on What Does Power Apps Licensing Cost in GCC Compared to the Commercial Cloud?, which owns that comparison. Your contracting officer and the contract clause govern any determination about what your programme may use.
Honest counter-case: when this page’s answer is the wrong one to act on
If you already hold licences with Power Pages rights attached, acting on the headline answer will make you budget for something you have bought twice, so check the exceptions before you raise a line item. The guide records them. A Power Apps Premium licence carries “Unlimited Power Apps and Power Pages websites”. Dynamics 365 Enterprise and Premium apps carry “Power Pages websites that map to the same environment as the licensed Dynamics 365 application” and “Unlimited Power Pages websites”. Both are on page 18, and both are bounded by the environment rule quoted above. Equally, the same table records “None” against Dynamics 365 Team Members, Dynamics 365 Operations – Activity and the Dynamics 365 professional-tier apps, so holding some Dynamics 365 licence is not the same as holding the right one.
Three further situations put this page’s answer outside its competence, and in each of them the number on the slide is decided somewhere other than a published guide. An enterprise agreement or a bundled renewal negotiation can carry terms that differ from list. A pre-existing capacity commitment may already cover the site. And Microsoft can change SKUs and terms between editions of the guide, which is why the edition and page are cited on every statement here rather than the fact being asserted flatly. In any of those three, your licensing desk or your reseller of record holds the answer and this page does not; take the questions in the previous section to them rather than the conclusion.
One thing this page does not decide is whether Power Pages is the right product at all. That question belongs to Power Pages vs Power Apps: Which One a Given Application Needs, and it is worth settling first, because a Power Apps Premium licence you already hold changes both the product answer and the bill.
How i3solutions answers this in a scoping conversation
When the entitlement question is settled and the portal still has to be built, the next thing a VP of IT usually needs is a number that survives contact with a finance review. i3solutions has completed more than 600 Microsoft platform implementations. i3solutions has used Power Pages for several of its applications. What a scoping conversation produces here is a written basis for the number rather than the number itself: the population split between authenticated and anonymous users, the environment the site will live in and what that environment already carries, the entitlements your existing Power Apps and Dynamics 365 licences bring with them, and the table-permission and web-role model the site needs before any of it is priced.
Those are framework outputs, and they are deliberately the limit of what is offered here. The figure itself depends on your audience and your agreement, and it is not something a page can responsibly quote. Who builds the portal once the basis is agreed is a separate question, answered on Enterprise Power Pages Development & Integration Services for Secure Business Portals, and the wider estate model it sits inside is on Enterprise Power Platform Development & Implementation Services for Governed Operations.
If you are holding a portal request, a renewal conversation and a budget deadline in the same quarter, and you want the entitlement position and the counting basis established before a figure goes on a slide, Contact a senior Power Platform architect.
Key Takeaways
- A Microsoft 365 or Office 365 subscription carries no Power Pages use rights. The Power Platform Licensing Guide, September 2026 edition, page 18, records “None” against that licence family, so Power Pages is a separate budget line.
- The meter is not seats. It is unique authenticated users per website per month and unique anonymous users per website per month, with capacity assigned to an environment and no carry-over of unused capacity (pages 16 and 17).
- An employee who holds a Microsoft 365 licence and signs in to your external portal still counts against the site’s authenticated capacity, because that licence carries no Power Pages rights (page 18).
- Check what you already hold before you raise the line item: Power Apps Premium and the Dynamics 365 Enterprise and Premium apps carry Power Pages use rights, bounded to the same environment (page 18).
- The September 2026 edition does not address government clouds. For a government tenant, read your own tenant’s entitlements and the terms that govern that cloud, and treat any determination as your contracting officer’s.
Frequently Asked Questions
Is Power Pages included in Office 365?
No. In the Power Platform Licensing Guide, September 2026 edition, page 18, the table of Power Pages use rights included with other licences records the row “Microsoft 365 / Office 365” against the value “None”. Office 365 and Microsoft 365 licences do carry some limited Power Platform use rights (page 5), but Power Pages is not among them, and page 29’s “Microsoft 365*, Office 365, and Windows” appendix table has no Power Pages column at all. Power Pages is licensed separately, on two audience meters counted per website per month: authenticated users, who sign in through an authentication provider, and anonymous users, who do not log in (page 16).