# Power Automate per flow plan > A Charity-segment Power Automate per flow plan option for nonprofits that want to evaluate licensing an automation at the flow level, subject to Microsoft’s current per-flow rules and nonprofit eligibility requirements. Canonical: https://o365hq.com/subscriptions/power-automate-per-flow-plan-nonprofit-pricing Provider: IT Partner LLC — US Microsoft partner since 2006. Book: https://o365hq.com/book ## Pricing (CSP / NCE, per seat per month unless noted) | Segment | Term · Billing | Invoice per cycle | Monthly equivalent | vs annual-upfront | |---|---|---|---|---| | Charity | 1-year · Annual | $300 | $25/mo | +0.0% | | Charity | 1-year · Monthly | $26.25 | $26.25/mo | +5.0% | | Charity | Monthly · Monthly | $30 | $30/mo | +20.0% | Prices are Microsoft ERP (estimated retail) — the same price as buying direct; IT Partner adds advisory and support on top. Last price sync: 2026-10-01. Consider this plan when your nonprofit is evaluating a Power Automate per-flow purchase for a specific automation. Final fit should be confirmed against current Microsoft licensing terms, especially if users, connectors, child flows, service accounts, or underlying applications affect the licensing design. ## What's included - Charity/Non-Profit Pricing catalog availability for Power Automate per flow plan, subject to Microsoft eligibility and availability. - Monthly commitment, annual upfront, and annual paid monthly purchase options are shown in the source catalog. - A flow-level licensing approach is indicated by the product name; the exact assignment model, scope, and any minimums should be verified before ordering. - No trial catalog entry is shown for this Charity SKU in the source pack. ## Not included - This is not presented in the source as a per-user SKU; do not treat it as user-based Power Automate licensing without a licensing review. - Not a substitute for confirming Microsoft’s current per-flow assignment, allocation, minimum-purchase, and scope rules. - Do not assume premium connector rights, third-party service subscriptions, API usage, or underlying application licenses are included until the flow design is reviewed. - Do not choose it solely because a process is shared; if users need many separate premium automations, separate capacity or add-ons, or Microsoft recommends another current licensing option, review alternatives before purchase. ## FAQ ### What is Power Automate per flow plan? Power Automate per flow plan is a Charity-segment catalog option for licensing a Power Automate automation at the flow level, because the SKU is listed as Power Automate per flow plan with Non-Profit Pricing. It should be evaluated against Microsoft’s current per-flow rules before purchase, especially for assignment, covered flow scope, child flows, and any minimum-purchase requirements. ### What does the Charity Power Automate per flow plan include? The Charity Power Automate per flow plan includes nonprofit catalog availability for the Power Automate per flow plan and purchase options with monthly commitment, annual commitment paid upfront, or annual commitment paid monthly. It does not by itself prove that every automation design is covered, because Microsoft’s current per-flow assignment and scope rules must be applied to the specific flow. ### What is not included with Power Automate per flow plan? Power Automate per flow plan is not a per-user Power Automate license, because the source SKU is explicitly a per-flow plan. Do not assume it includes third-party service subscriptions, underlying Microsoft 365 or Dynamics 365 application licenses, API charges, specialty capacity, or every premium connector scenario without a licensing review. ### Is there a trial for the Charity Power Automate per flow plan? No trial is listed for this Charity SKU, because the source catalog shows only paid nonprofit purchase options and marks no trial availability. A nonprofit should validate the flow design before ordering rather than relying on a trial conversion path for this specific SKU. ### How is the nonprofit eligibility handled for this SKU? Nonprofit eligibility must be validated under Microsoft’s current nonprofit requirements, because the catalog lists the SKU in the Charity segment with Non-Profit Pricing. IT Partner can help prepare the purchasing and eligibility questions, but Microsoft determines eligibility and applicable nonprofit terms. ### Can Microsoft nonprofit grants be used for Power Automate per flow plan? Do not assume a Microsoft nonprofit grant covers this Power Automate per flow plan, because grant benefits and discounted catalog purchases are separate programs that can change. The SKU is shown with Non-Profit Pricing, so a nonprofit should confirm whether its available grant benefits, if any, apply before purchase. ### When should a nonprofit choose per-flow licensing instead of per-user Power Automate licensing? A nonprofit should consider per-flow licensing when it wants to license a specific automation rather than assign Power Automate rights to each individual user, because this SKU is the Power Automate per flow plan. If users need many separate premium automations, personal automation rights, or broader Power Platform capabilities, a per-user or newer Microsoft-recommended option may fit better and should be reviewed first. ### Do all users who trigger or benefit from the flow avoid needing Power Automate user licenses? Not necessarily, because Microsoft’s current per-flow rules, user participation model, connectors, service accounts, and underlying applications can affect whether separate user licensing is required. A nonprofit should validate the exact flow design before assuming every participant is covered by the per-flow plan. ### Does the Charity per-flow plan include premium connector rights? Do not assume premium connector rights are fully included for every scenario, because connector licensing can depend on the current Power Automate terms, connector type, API usage, and the applications involved. Before ordering, confirm whether the flow uses premium connectors, third-party services, Dynamics 365, Microsoft 365, or custom APIs that require separate licenses or subscriptions. ### Does Microsoft Teams include this Power Automate per flow plan? No, Microsoft Teams does not include the Charity Power Automate per flow plan, because Teams licensing and Power Automate per-flow licensing are separate licensing constructs. Teams may be part of the collaboration experience, but premium automation, connectors, and flow-level licensing should be reviewed independently. ### Is Microsoft Copilot included with Power Automate per flow plan? No, Copilot should not be assumed to be included, because the source SKU is Power Automate per flow plan and does not list Copilot entitlement. If the automation design uses Copilot, generative AI features, or Power Platform AI capacity, confirm the current Microsoft licensing and data-governance requirements separately. ### Are add-ons or extra capacity ever needed with the per-flow plan? Yes, add-ons or separate capacity may be needed, because some scenarios can involve higher usage, premium connectors, Dataverse capacity, AI features, hosted RPA, custom connectors, or application-specific prerequisites. The per-flow plan should be reviewed against the actual architecture rather than treated as an all-inclusive automation bundle. ### What security controls apply to flows licensed under this nonprofit plan? Power Automate security is managed through Microsoft Entra ID, Power Platform environments, roles, connectors, data loss prevention policies, and tenant governance settings, because the flow runs inside the organization’s Microsoft cloud environment. The license purchase does not automatically configure security, so nonprofits should set environment strategy, DLP policies, owner controls, and audit expectations before production use. ### Does Power Automate per flow plan meet nonprofit compliance requirements by itself? No license alone proves compliance, because compliance depends on tenant configuration, data types, connectors, geography, retention, auditing, and the nonprofit’s regulatory obligations. The Power Automate service may support Microsoft compliance capabilities, but IT Partner should confirm the relevant Microsoft documentation and the customer’s configuration for the specific workload. ### Does the Charity SKU provide GCC, GCC High, or special government data residency? No, a Charity SKU should not be treated as a Government, GCC, or GCC High license, because the source lists this purchase in the Charity segment and government cloud eligibility is separate. If a nonprofit handles government-regulated data or needs GCC/GCC High residency, it should confirm government cloud eligibility, SKU availability, and tenant-cloud requirements before buying. ### Can a nonprofit use the Education or Commercial version instead of the Charity version? Usually the organization should buy in the segment for which it is eligible, because Charity, Education, Government, and Commercial offers have different eligibility and terms. Student-versus-faculty rules apply to Education offers, standard business rules apply to Commercial offers, and nonprofit validation applies to Charity purchases. ### How should a nonprofit get started with this plan? Start by documenting the flow, owners, triggers, connectors, users, child flows, service accounts, and source applications, because those details determine whether per-flow licensing is the right fit. Then confirm Microsoft’s current per-flow assignment rules, nonprofit eligibility, and the preferred commitment option before ordering. ### Can existing Power Automate flows be migrated to this nonprofit per-flow plan? Existing flows may be able to be licensed or reorganized under a per-flow approach, but this should be reviewed first because ownership, environment placement, connectors, child flows, and solution packaging can affect the migration path. Licensing the flow does not automatically fix design, governance, or application-permission issues. ### Can we transfer our CSP subscription for this SKU to IT Partner with no downtime? A CSP transfer to IT Partner is normally a billing and support relationship change, not a tenant migration, so the Microsoft cloud service should continue without data movement or planned downtime. For the same Microsoft Charity SKU and commitment, IT Partner can align to the Microsoft catalog price; confirm taxes, currency, partner services, and any legacy promotional terms before transfer. ### What are the renewal, cancellation, and quantity-change rules for the Charity per-flow plan? The catalog shows monthly and annual commitment options, because nonprofits can choose flexibility or a longer commitment at purchase. Under Microsoft commerce rules, cancellations and reductions are generally restricted after the applicable post-purchase or renewal cancellation window, while additions may be handled differently; confirm the current CSP terms with IT Partner before checkout or renewal. --- To buy or migrate with zero downtime, book a call with Mike (https://o365hq.com/book) or email sales@o365hq.com. Same Microsoft price, partner support included.