Power Pages licenses external facing websites on a capacity model that splits sharply between authenticated and anonymous users. Authenticated capacity is billed per logged in user per site per month, sold in tiered packs, and suits a portal where named customers or partners sign in. Anonymous capacity is billed per page view per site per month and suits a public site open to the world. The two meters are independent, and the cost behaves very differently under load: an authenticated portal scales with the registered population, while an anonymous site scales with traffic and can spike without warning when a campaign or a press mention drives a surge. Buyers consistently size to the launch state and get caught when usage moves. Power Pages is where a portal business case meets a metered bill that does not forgive a traffic event.
Power Pages licenses per site across two independent capacity meters, authenticated and anonymous, with a Dataverse dependency underneath. The site count, the meter that fits each site, and the capacity pack sizing are the three decisions that govern the bill.
Power Pages bills two ways per site. Authenticated capacity counts the logged in users on a portal and is sold in tiered per user packs. Anonymous capacity counts page views on a public site and is sold in per view packs. A single site can use both meters when it serves a signed in audience and a public audience together.
Power Pages sites run on Dataverse, which means the data layer carries its own capacity that bills alongside the page capacity. A site that stores significant data, or grows its data over time, consumes Dataverse capacity that the page meters do not include. The total cost of a portal is the page capacity plus the Dataverse footprint it stands on.
Power Pages produces three recurring exposures. The first is choosing the wrong meter for the site's real audience. The second is sizing capacity to the launch state and overrunning on a traffic event. The third is ignoring the Dataverse footprint that grows underneath the portal.
A site that is mostly public traffic licensed on authenticated capacity, or a registered portal licensed on anonymous views, pays the wrong meter for its audience. The two meters price very differently, and choosing the one that does not fit the access pattern inflates the bill or caps the site at the wrong ceiling. The audience shape should pick the meter, not the default.
Capacity is bought for the expected launch volume. When a campaign, a partner onboarding, or a public mention drives a surge, the meter runs past the purchased pack and the overage bills at the higher incremental rate. Organizations that do not monitor the meter or pre commit headroom discover the spike on the invoice rather than in advance.
The portal launches lean and accumulates data as users transact. The Dataverse capacity that the site stands on grows quietly, and the storage overage bills separately from the page meters. Without a steward watching the data footprint, the true cost of the portal drifts above the page capacity the business case was built on.
The Power Pages bill responds to three levers. The meter fit matches each site to the capacity model its audience justifies. The capacity sizing pre commits the right tier with headroom for the known peaks. The Dataverse governance keeps the data footprint inside the entitlement.
Each site is profiled by access pattern. A registered portal moves to authenticated capacity sized to the named population. A public site moves to anonymous capacity sized to the traffic. A mixed site splits across both meters so each audience is billed on the model that fits it. Getting the meter right is the single largest determinant of whether the portal cost tracks its value.
The site portfolio then anchors the EA renewal so the Power Pages capacity is committed at the tier the real audience justifies.
Capacity is committed at the tier that lowers the unit rate, with headroom modeled against the known traffic events so a campaign does not trigger overage at the incremental price.
The Dataverse footprint underneath each site is governed against the included pool, with data lifecycle rules and cleanup so the storage stays inside the entitlement rather than drifting into a separate recurring charge.
Power Pages negotiates inside the Power Platform envelope. The tiered capacity packs and the Dataverse dependency give a buyer with a clear site portfolio real leverage on the committed rate and the overage terms.
The capacity packs price lower at higher committed tiers. A buyer who has profiled the site portfolio and sized the authenticated and anonymous capacity to the real audience can commit the tier that lowers the unit rate while protecting against overage. Committing blind to an unprofiled portfolio risks locking the wrong tier. Committing on a validated baseline turns the volume into a negotiated discount.
The overage rate on a traffic event is where an anonymous site can surprise the budget. A buyer who raises the overage and burst terms in the negotiation can secure protection on the incremental rate or pre committed burst capacity at the committed price. Leaving the overage at the default list rate hands Microsoft the upside of every campaign and press event the portal was built to drive.
The Power Pages engagement is a site portfolio and meter diagnostic, a capacity and Dataverse sizing model, and the integration of the result into the Power Platform negotiation. The output is a portal estate priced at the audience each site actually serves, with the overage protected.
We inventory every Power Pages site, profile each by access pattern, and match it to the authenticated or anonymous meter its audience justifies. We size the capacity to the real population and traffic, model the Dataverse footprint underneath each site, and identify the sites on the wrong meter or the wrong tier. The output is a defensible picture of what the portal estate actually requires.
We move each site to the meter that fits, size the committed tier with headroom for known peaks, govern the Dataverse footprint inside the pool, and fold the portfolio into the Power Platform negotiation. We commit the tier for the discount, negotiate the overage and burst protection, and lock multi year rates. The output is a Power Pages position priced at real audience and defensible through the term.
The Power Pages diagnostic profiles every site by audience, matches each to the authenticated or anonymous meter, sizes the capacity with headroom for peaks, governs the Dataverse footprint, and brings the portfolio into the Power Platform negotiation with overage protection. The result is a portal line priced at the audience each site serves, not at the launch state it was sized for.