Power Pages authenticated users — Pricing, Plans & What’s Included

Power Pages authenticated users licenses signed-in capacity for Power Pages sites, because each unit is a 100 authenticated-users-per-site/month capacity pack. It is intended for customer portals, partner portals, and other self-service sites where users log in rather than browse anonymously.

No, Power Pages authenticated users is capacity licensing, because the Commercial SKUs are measured as 100 authenticated users per site per month rather than assigned to named people. Buyers should size by expected signed-in usage for each Power Pages site, not by assigning seats to every possible visitor.

A Power Pages authenticated users capacity pack includes authenticated-user capacity for Power Pages sites, because the unit of measure is 100 signed-in users per site per month. It does not include anonymous-user capacity, site build services, migration services, or managed administration.

No, Power Pages authenticated users does not cover anonymous visitors, because it is specifically capacity for users who sign in to a Power Pages site. If the site will also serve unauthenticated traffic, confirm and license the appropriate anonymous-user capacity separately.

Size Power Pages authenticated users by site and by expected signed-in usage, because capacity is expressed as 100 authenticated users per site per month. Before purchase, confirm Microsoft’s current counting method for an authenticated Power Pages user and model peak monthly usage for each site.

The Commercial offer includes T1, T2, and T3 capacity tiers, because the source lists all three tiers for Power Pages authenticated users. T2 has a minimum of 100 units, and T3 has a minimum of 1,000 units, so higher tiers are designed for larger volume commitments.

Commercial options include monthly commitment billed monthly, annual commitment billed annually, and annual commitment billed monthly, because those term and billing combinations are listed for the Commercial SKUs. Annual commitment paid annually has the lowest listed annualized cost in the source, while monthly commitment may fit shorter-term or uncertain usage scenarios.

No trial is shown for Power Pages authenticated users in the provided Commercial source, because the listed SKUs are marked as non-trial. If a proof of concept is needed, confirm available evaluation options with IT Partner before committing to production capacity.

Usually the purpose of this SKU is to cover signed-in Power Pages site users through capacity, because it is not sold as a traditional named-user seat. However, maker, admin, internal app, Dataverse, identity, or tenant prerequisites can vary by scenario, so confirm the current Microsoft Product Terms with IT Partner before final sizing.

No, Power Pages authenticated users should not be treated as including Teams, Microsoft 365 Copilot, or Copilot Studio, because the listed entitlement is authenticated-user capacity for Power Pages sites. If the portal uses Teams collaboration, AI copilots, or custom bot experiences, license those services separately as required.

No, the capacity pack itself should not be read as including professional services, because the source only identifies authenticated-user capacity measured per site per month. Power Pages commonly depends on Power Platform environments, Dataverse, security configuration, and identity setup, so validate prerequisites, storage needs, and implementation services separately.

Power Pages authenticated users provides the licensing capacity, not the security design, because access control depends on the Power Pages site, Dataverse permissions, identity provider configuration, and Power Platform governance. Commercial buyers should review authentication, role design, data loss prevention policies, auditing, and compliance requirements before go-live.

No, buying this Commercial capacity SKU alone does not guarantee a specific residency or compliance outcome, because residency and compliance depend on the tenant, environment region, connected services, data model, and applicable Microsoft cloud terms. Confirm regional deployment, Dataverse residency, identity configuration, and regulatory requirements with IT Partner before purchase.

Start by estimating signed-in usage per Power Pages site, because each unit covers 100 authenticated users per site per month. Then choose the Commercial tier and commitment term, confirm prerequisites such as environment, Dataverse, identity provider, and admin licensing, and plan whether anonymous capacity is also needed.

Yes, a Power Pages portal can be planned around capacity rather than individual named-user seats, because this SKU is measured by authenticated users per site per month. The migration itself is separate from the license purchase, so data migration, page rebuild, integrations, identity mapping, and testing should be scoped as an implementation project.

Yes, a CSP partner transfer is generally designed to change the reseller relationship rather than move the tenant or portal data, because the Microsoft cloud subscription remains associated with the customer tenant. To avoid downtime, coordinate the transfer timing, subscription mapping, renewal dates, and admin access with IT Partner before making changes.

For a like-for-like CSP SKU and term, the Microsoft product functionality does not change, because the same Power Pages authenticated users capacity remains in the customer tenant. Commercial pricing should be confirmed in the quote, including term, billing frequency, taxes, and any partner-managed services that are separate from the Microsoft subscription.

Renewal and cancellation depend on the selected Commercial commitment term, because monthly and annual commitments have different flexibility. Under Microsoft CSP new commerce rules, cancellation or reduction rights are typically limited after the post-purchase cancellation window, so confirm the exact renewal date, auto-renewal setting, and change window with IT Partner before ordering.

You can generally add capacity during a term, because additional units can be purchased when signed-in usage grows. Reductions are more restricted, especially on annual commitments, so size carefully by site and confirm Microsoft CSP change rules with IT Partner before choosing the tier and quantity.

Commercial is the standard business segment, because Government, Charity, and Education are separate segments in the source. Government customers should confirm GCC versus GCC High availability and residency requirements, nonprofits should validate Microsoft nonprofit eligibility and any grant context, and Education customers should confirm whether student, faculty, or institutional licensing rules apply before using a Commercial SKU.