Power Apps and Power Automate capacity add-on — Pricing, Plans & What's Included

The Power Apps and Power Automate capacity add-on includes Power Platform Requests add-on capacity, because it is designed to increase request capacity for higher-volume Power Apps and Power Automate scenarios. It is available to Commercial customers with monthly and annual commitment options shown in the CSP source. It should be evaluated against the customer’s existing Power Platform licenses and current request consumption.

No, the Power Apps and Power Automate capacity add-on is not a standalone or core user license, because it is an add-on for Power Platform request capacity. Users, makers, flow owners, apps, connectors, Dataverse, and other services may still require separate eligible licenses. Confirm the tenant’s base licenses before relying on this add-on for production use.

A Commercial customer should consider this add-on when Power Platform request capacity is the constraint, because busy apps and automated flows can consume request entitlement beyond what existing licenses provide. It is best evaluated after reviewing current Power Apps, Power Automate, Dynamics 365, or Power Platform licensing. It should not be used to fix missing app, connector, storage, or user-license requirements.

The add-on provides Power Platform Requests add-on capacity, but the exact current request quantity should be confirmed before quoting, because Microsoft’s published licensing documentation controls the entitlement details. IT Partner should validate the current per-add-on capacity, allocation model, and consumption guidance for the customer’s tenant. This is especially important for high-volume production flows or business-critical apps.

Usually it should be treated as an add-on to an existing Power Platform licensing position, because it does not replace base user, app, flow, connector, or service entitlements. The correct prerequisite can depend on the customer’s scenario, such as Power Apps, Power Automate, Dynamics 365, Dataverse, or other Power Platform licensing. Confirm the current Microsoft prerequisite and assignment rules before purchasing.

Yes, this product is positioned for Power Apps and Power Automate request-capacity scenarios, because it is a Power Platform Requests add-on. However, workload eligibility and allocation can depend on how Microsoft measures requests in the tenant and how the app or flow is licensed. Review the customer’s actual request consumption before deciding how many add-ons are needed.

No, this add-on does not itself include Microsoft Teams, because it is a Power Platform request-capacity add-on rather than a Teams or Microsoft 365 plan. If the app or flow runs in or with Teams, the Teams licensing and Power Platform licensing must still be valid separately. Confirm whether the scenario uses standard Teams capabilities, Power Apps in Teams, Dataverse for Teams, premium connectors, or full Dataverse.

No, Copilot, AI Builder, and other AI-specific entitlements should not be assumed to be included, because the source identifies this SKU as a Power Platform Requests add-on. AI Builder capacity, Copilot licensing, and related service requirements are governed by separate Microsoft licensing terms. Confirm current AI and Copilot requirements before positioning this add-on for AI-heavy apps or flows.

No, Dataverse storage and premium connector rights should not be assumed to be included, because this add-on is for Power Platform request capacity. Customers may still need eligible Power Apps, Power Automate, Dynamics 365, Dataverse storage, or connector licensing depending on the workload. Validate storage, connector, maker, user, and flow-owner requirements before purchase.

No, buying the add-on does not by itself change security or compliance controls, because it adds request capacity rather than changing identity, access, data loss prevention, audit, or environment governance settings. Security remains governed by Microsoft Entra ID, Power Platform environment settings, DLP policies, role assignments, and applicable service compliance commitments. Review governance before scaling high-volume apps and flows.

No, the add-on should not be treated as a data residency change, because it adds Power Platform request capacity rather than moving the tenant to a different cloud. Commercial data residency depends on the customer’s Microsoft tenant, environment region, service configuration, and Microsoft’s current cloud commitments. If residency is a hard requirement, confirm the tenant and environment location before purchase.

A standard Commercial customer should not assume it can buy GCC or GCC High capacity, because Government cloud availability and eligibility are separate from Commercial licensing. The source shows the product exists across multiple segments, but segment availability does not mean every tenant qualifies for every cloud. Government residency, compliance, and eligibility should be validated before choosing GCC, GCC High, or Commercial.

The source indicates the product is present in the Charity segment, but nonprofit eligibility and grant treatment must be confirmed, because Microsoft nonprofit offers can have separate qualification and benefit rules. A Commercial price or subscription should not be assumed to qualify for nonprofit grant funding. Eligible nonprofits should validate their Microsoft nonprofit status and the specific Charity SKU options before ordering.

The source indicates the product is present in the Education segment, but student and faculty eligibility should be checked separately, because Education licensing can distinguish between academic user types and institutional eligibility. This Commercial FAQ does not establish Education entitlement rules. Schools should confirm whether the add-on applies to the intended student, faculty, staff, or shared workload scenario.

Start by reviewing Power Platform request consumption, because this add-on is only useful when request capacity is the actual bottleneck. Then validate existing Power Apps, Power Automate, Dynamics 365, Dataverse, connector, and environment licensing. IT Partner can help compare monthly flexibility against annual commitment and billing options before the customer commits.

Yes, adding capacity is normally a licensing and capacity change rather than an application migration, so it should not require app or flow downtime by itself. However, the tenant’s allocation model and effective timing should be confirmed, because Microsoft licensing systems and admin-center reporting can take time to reflect changes. For critical workloads, plan the order before the capacity limit is reached.

A CSP partner transfer is typically a billing and partner-of-record change, not a tenant migration, so it should not interrupt Power Apps or Power Automate services when handled correctly. The customer keeps the same Microsoft tenant, identities, environments, apps, and flows. IT Partner should confirm the current subscription term, renewal date, and any partner-transfer requirements before the move.

The Microsoft CSP SKU and commitment options can remain the same when the same product and term are used, because the transfer changes the purchasing relationship rather than the Microsoft cloud service itself. The final quote should still be confirmed, because billing frequency, term, taxes, promotions, and partner commercial terms can affect the invoice. No technical reconfiguration should be required solely because of the CSP provider change.

Commercial options in the source include a monthly commitment billed monthly and an annual commitment billed either annually or monthly, because the SKU is offered with both monthly and annual term structures. The source also marks the price-change status as unchanged. Choose the term based on whether the customer values short-term flexibility or annual commitment planning.

Changes are governed by the Microsoft CSP subscription term and cancellation rules, because this is a purchased add-on rather than an on-demand metered switch. In general, increases are often easier during a term, while reductions or cancellations may be limited until renewal or the applicable cancellation window. Confirm the exact change rules for the selected monthly or annual commitment before ordering.