Power Platform Requests add-on for Government — Pricing, Plans & What's Included

The Power Platform Requests add-on for Government is a capacity add-on, because it adds extra Power Platform request capacity for eligible government organizations using Power Apps or Power Automate. It is not a standalone license and does not by itself grant rights to create, run, or administer apps and flows.

This add-on includes additional Power Platform request capacity, because it is sold as a capacity unit associated with Power Apps and Power Automate usage. It does not include standalone Power Apps or Power Automate user rights, Dataverse storage, AI Builder credits, unattended RPA, Copilot capacity, or other separately licensed services unless those are purchased separately.

Yes, you should have the required underlying Power Platform licenses first, because this SKU only extends request capacity and does not replace base licensing. IT Partner should review the workloads consuming requests to confirm the add-on is solving a capacity issue rather than a missing-license issue.

Do not assume the request quantity without checking current Microsoft documentation, because Microsoft defines request entitlements by product, licensing program, and current service rules. IT Partner should confirm the current Microsoft-defined request amount for this Government SKU before you size or quote the purchase.

Government eligibility must be confirmed before ordering, because this offer is listed for the Government segment and may require the correct government tenant, cloud, or provisioning path. IT Partner should validate whether your organization qualifies and whether the SKU can be provisioned in your specific Microsoft environment.

Do not treat GCC and GCC High availability as interchangeable, because Microsoft government cloud availability and provisioning paths can differ by SKU and customer eligibility. Confirm with IT Partner which government cloud applies to your tenant before presenting this add-on as available for GCC, GCC High, or another government environment.

No, the add-on itself should not change data residency, because it is capacity attached to Power Platform usage rather than a separate hosting environment. Your residency and compliance posture depend on the underlying Microsoft government cloud, tenant configuration, and services in use, so confirm the applicable government cloud boundary before purchase.

No, buying this add-on does not add new security controls, because it increases request capacity rather than changing identity, access, data loss prevention, auditing, or compliance configuration. Security and compliance should still be managed through Microsoft Entra ID, Power Platform admin controls, environment strategy, and the applicable government cloud compliance commitments.

It may help only if the Teams-based apps or flows are consuming Power Platform requests that are eligible for the add-on, because the SKU adds request capacity rather than changing Teams licensing rights. You should confirm the specific workload, connectors, environments, and underlying licenses before assuming Teams usage is covered.

No, those should not be assumed to be included, because this SKU is specifically a Power Platform Requests capacity add-on. Copilot, AI Builder, premium connectors, attended or unattended RPA, and other Power Platform capabilities can have separate licensing or entitlement requirements.

Buy the add-on when legitimate production workloads need more request capacity, because high-volume apps, flows, integrations, or service workloads can exceed available request limits. Do not use the add-on as the first response to inefficient design; review flow frequency, connector patterns, retry loops, and integration architecture before sizing additional capacity.

Size it from actual request consumption, because request pressure depends on app usage, flow runs, connector calls, integration frequency, and shared service patterns. IT Partner should review Power Platform admin data and Microsoft’s current entitlement rules, then map the gap to add-on units instead of estimating from user count alone.

The capacity should surface through Microsoft’s Power Platform administration and licensing experience, because it is a tenant capacity add-on tied to Power Platform usage. The exact allocation or visibility method should be confirmed at the time of purchase, since Microsoft can change how capacity is displayed and assigned in the Power Platform admin center.

No trial should be expected, because the current source data lists this Government add-on as a paid SKU with no trial offer. If you need to validate demand before committing, use usage reporting and a licensing review rather than relying on a trial conversion path.

Government pricing is available with monthly commitment billed monthly, annual commitment billed annually, or annual commitment billed monthly, because the SKU is offered with multiple commitment/payment structures. Annual upfront is the best-rate posture in the current price list, annual paid monthly costs more over the term, and month-to-month provides the most flexibility.

You can generally add more capacity when needed, because additional add-on units can be purchased as demand grows. Reductions and cancellations are governed by the selected Microsoft commerce term and cancellation window, so annual commitments should be treated as a term commitment even when billed monthly; confirm the current CSP rules before ordering.

At renewal, you should review capacity usage and commitment level, because that is the safest point to adjust quantities or change the purchasing posture. If the subscription auto-renews or is renewed into a new term, Microsoft commerce rules may limit reductions after the renewal window, so renewal planning matters.

Yes, a CSP partner transfer can usually be handled without workload downtime when the Microsoft tenant and service subscriptions remain in place, because it is a billing and management relationship change rather than a data migration. The Microsoft SKU entitlement and Microsoft price-list basis remain the same, but final invoice terms depend on the selected commitment and partner agreement.

Do not assume a simple license move is available, because Commercial and Government tenants can have different eligibility, cloud boundaries, and provisioning paths. A move from Commercial to Government may require tenant, data, environment, and licensing planning rather than just transferring the add-on.

Only eligible government customers should buy the Government offer, because Microsoft separates availability and pricing by segment such as Government, Charity, Education, and Commercial. Nonprofits should validate Charity eligibility and grant context, education organizations should distinguish student and faculty/staff licensing where applicable, and standard businesses should use the Commercial purchasing path rather than the Government SKU.