Power Pages Authenticated Users for Government — Pricing, Plans & What's Included

Power Pages Authenticated Users for Government includes capacity for users who sign in to a Power Pages site, because the unit of measure is a 100 authenticated users per site/month capacity pack. The Government catalog entries include GCC-titled T1, T2, and T3 capacity-pack SKUs with monthly and annual commitment options.

Anonymous-user capacity is not included, because Power Pages licenses authenticated and anonymous portal usage separately. The pack also does not include site design, implementation services, security review, content migration, general Microsoft 365 licensing, or separate Power Platform and Dynamics 365 licenses that may be needed for makers, administrators, or connected business applications.

Buy authenticated-user capacity when portal visitors sign in, because this SKU is specifically measured as authenticated users per site per month. If the portal is public and does not require sign-in, use the separate Power Pages anonymous-user capacity model instead.

Each pack represents capacity for 100 authenticated users for one Power Pages site in a month, because the catalog unit is defined per site/month rather than as a named-user license. Agencies should size each site based on expected signed-in traffic and confirm whether multiple sites require separate capacity planning.

T1 is the base 100 users per site/month capacity pack, while T2 and T3 are higher-volume tiers, because the Government source catalog lists T2 with a minimum of 100 units and T3 with a minimum of 1,000 units. Agencies should use T1 for smaller or uncertain workloads and evaluate T2 or T3 only when forecasted authenticated traffic supports the minimum unit commitment.

Government offers are available as monthly commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly, because the source catalog includes P1M and P1Y entries with different billing models. Annual upfront is generally the best rate posture in the catalog, annual paid monthly provides payment spreading, and month-to-month provides the most flexibility.

No trial is listed for this Government offer, because the source catalog marks the available Government SKUs as non-trial. If a pilot is needed, agencies should confirm whether a separate Power Pages trial, developer environment, or proof-of-concept approach is appropriate before purchasing production capacity.

No, this capacity pack does not include Teams, Microsoft 365, or Copilot, because it is an add-on capacity SKU for authenticated Power Pages site usage. Any Teams collaboration, Microsoft 365 productivity licensing, Copilot licensing, or user licensing for internal staff must be purchased and validated separately.

A government buyer should confirm that the purchasing tenant and Power Platform environment match the required Government/GCC context, because the Government SKU titles in the source catalog are GCC-based. The agency should also confirm expected authenticated traffic, site count, and any separate licensing needed for makers, administrators, Dataverse, Power Platform, or Dynamics 365 resources connected to the portal.

This listing should be treated as GCC unless confirmed otherwise, because the source SKU titles explicitly reference GCC and do not state GCC High or DoD. Agencies needing GCC High or DoD should not assume compatibility and should have IT Partner validate the exact cloud, tenant, and offer availability before purchase.

No, the capacity pack alone does not guarantee a specific residency or compliance outcome, because residency and compliance depend on the Power Pages service, the Power Platform environment, the tenant cloud, configuration, and connected data sources. Government agencies should validate GCC/GCC High/DoD requirements, data location, identity configuration, and compliance obligations before production use.

The capacity covers users who authenticate to a Power Pages site, because it is licensed for authenticated portal usage rather than anonymous visits. The specific identity provider, access rules, and security model must be configured in Power Pages and the agency’s identity architecture, so IT Partner should confirm the sign-in approach before capacity is sized.

No, this pack is for authenticated portal-user capacity, because it measures external or internal sign-in traffic to a Power Pages site rather than granting maker or administrator rights. Employees who create, manage, or access underlying Power Platform, Dataverse, or Dynamics 365 resources may need separate licenses depending on their role and usage.

Estimate packs by forecasting the number of unique authenticated users expected per site each month, because each pack represents 100 authenticated users per site/month. Agencies should size for peak program periods, enrollment windows, citizen-service deadlines, and partner-access cycles, then choose T1, T2, or T3 based on volume and minimum unit requirements.

Capacity can typically be increased by adding more units or moving to an appropriate tier, because the offer is sold as capacity packs rather than fixed named-user seats. The exact change rules depend on the CSP term, billing model, and Microsoft offer availability, so agencies should confirm timing and renewal impact before committing.

Reductions and cancellations are constrained by the selected commitment term, because annual and monthly CSP subscriptions have different change windows and renewal rules. Agencies should not assume annual paid monthly can be canceled at any time; IT Partner should confirm the current Microsoft CSP cancellation and reduction policy before the order is placed.

At renewal, the agency should reassess traffic, tier, and billing model, because portal usage may change and T2 or T3 minimums can materially affect capacity planning. IT Partner can help confirm whether to renew as-is, adjust units, change commitment model, or align the subscription with budget and procurement cycles.

Yes, CSP management can usually be transferred without portal downtime, because changing the CSP partner relationship does not normally require moving the tenant, rebuilding the Power Pages site, or changing user access. The agency should still confirm the current subscription term, renewal date, and administrative relationship so the transfer is coordinated cleanly.

The underlying offer remains a Microsoft catalog-priced CSP subscription, because the product, tier, term, and billing model define the licensing basis. Partner quotes, taxes, support scope, and timing can affect the invoice presentation, so the agency should compare the same SKU, commitment, billing option, and quantity when validating pricing.

Government agencies should buy through the Government/GCC-appropriate offer when their tenant and procurement requirements require it, because Charity, Education, and Commercial are separate purchasing segments with different eligibility and cloud-fit assumptions. Nonprofit grant eligibility, student or faculty licensing, and standard business licensing do not automatically apply to a government tenant, so cross-segment purchasing should be validated before quoting.