Power Apps Per App for Nonprofits — Pricing, Plans & What's Included

Power Apps Per App for Nonprofits is best when a charity user needs one specific custom app or one website, because it licenses a narrow Power Apps use case instead of the full Power Apps portfolio. It is commonly used for intake forms, case workflows, volunteer processes, program tracking, and replacing paper-based departmental processes.

The nonprofit per app license includes access for a user to one custom Power Apps app or one website, subject to Microsoft licensing terms. It is a focused standalone Power Apps license for charities that do not need to give the same user broader rights across many apps or websites.

Power Apps Per App for Nonprofits does not include unlimited Power Apps usage, because the plan is intentionally scoped to one app or one website. It also does not automatically include standalone Power Automate Premium, robotic process automation, Copilot, AI Builder, extra capacity, or rights for multiple apps unless those are separately licensed or allowed by the current Microsoft terms.

No, the Charity catalog entry for Power Apps Per App does not include a trial offer. Nonprofits should instead compare the available nonprofit paid commitment options and any donation option for which the tenant is eligible.

The donation option is a nonprofit-specific annual offer, while the paid nonprofit options include different commitment and payment timing choices. Donation availability is not guaranteed, because Microsoft nonprofit eligibility, tenant qualification, and program rules determine whether the donation SKU can be used.

Charity pricing requires Microsoft nonprofit eligibility, because Microsoft restricts nonprofit offers to approved organizations and qualified tenants. A charity should confirm eligibility before checkout, especially if it expects to use the donation offer rather than a paid nonprofit subscription.

A user who needs several apps or websites may need additional per-app coverage or a broader Power Apps plan, because this offer is scoped to one app or one website. IT Partner should map each user to the apps and websites they actually use before purchase to avoid under-licensing or overbuying.

Power Apps Per App can be used for one covered website where Microsoft licensing terms allow it, because the catalog title is scoped to one app or website. However, website capacity, authenticated access patterns, anonymous usage, and Power Pages-specific requirements should be validated against the current Microsoft Power Platform licensing guide before deployment.

Only flows that are allowed under the current Power Apps per app licensing terms should be treated as covered, because standalone Power Automate Premium and RPA rights are not automatically included. If the solution uses premium automation, unattended automation, desktop flows, or flows shared beyond the app context, confirm whether separate Power Automate licensing is required.

It may be appropriate for apps that use premium connectors or Dataverse, because Power Apps standalone licensing is often used for more advanced app scenarios than Microsoft 365 seeded use rights. The exact connector rights, Dataverse capacity, storage, API limits, and request limits depend on the current Microsoft Power Platform licensing guide and the solution design, so these should be confirmed before purchase.

No, Power Apps Per App does not include Microsoft Teams or Microsoft 365, because it is a standalone Power Apps license for app or website access. Users still need the required identity, access, and any Microsoft 365 or Teams licensing that your organization uses for collaboration, authentication, email, files, or embedding apps in Teams.

No, Copilot, AI Builder, extra Dataverse capacity, Power Pages capacity, and other Power Platform add-ons should not be assumed to be included, because the per app plan is a narrow app or website access license. If the app uses AI prompts, document processing, advanced capacity, or specialized add-ons, validate the required add-on licensing with IT Partner before checkout.

Security is controlled through Microsoft Entra ID, Power Platform environments, app sharing, connectors, data loss prevention policies, and Dataverse security where Dataverse is used. The license grants usage rights, but compliance depends on how the app is designed, where data is stored, which connectors are allowed, and how administrators configure tenant governance.

Not necessarily, because Government cloud availability, data residency, GCC, and GCC High requirements are handled through Microsoft government offerings rather than standard Charity catalog assumptions. A nonprofit with government contract, regulated residency, or GCC High requirements should confirm the correct cloud, SKU availability, and licensing path before buying the Charity offer.

Start by identifying the exact app or website, the user group, the data sources, and any automation, because the license is only cost-effective when the scope is narrow and clear. IT Partner can help validate whether the workload fits one-app licensing, whether premium connectors or Dataverse are involved, and whether a broader Power Apps plan would be safer.

Licenses should be matched to the users who need access to the specific app or website, because per app licensing is not a general-purpose license for every Power Apps workload. Before rollout, confirm the app, environment, user list, guest access needs, and any website access model so the subscription quantity aligns with actual usage.

Yes, CSP management can usually be moved without app downtime, because the Microsoft tenant, Power Platform environments, apps, data, and user identities remain in place. The change is primarily a partner and subscription management change, but IT Partner should review renewal dates, commitment terms, and SKU alignment before the transfer.

For the same Microsoft Charity SKU and term, the Microsoft catalog basis should be the same, because IT Partner is transacting Microsoft CSP offers rather than moving you to a different product. Final invoicing can still vary due to taxes, partner services, support agreements, or term selection, so compare the quote details before checkout.

Yes, but the rules depend on the commitment term, because monthly and annual subscriptions have different renewal, cancellation, and seat-reduction treatment under Microsoft CSP rules. Seat increases are commonly easier during a term, while reductions or cancellations may be limited to renewal or a short cancellation window, so confirm the exact terms on the quote before committing.

Only eligible nonprofit users and tenants should use the Charity SKU, because Microsoft separates Charity, Education, Commercial, and Government offers by eligibility and program rules. A nonprofit school may need to distinguish staff, faculty, and students under the appropriate Microsoft program, and a commercial subsidiary or standard business workload may need Commercial licensing instead of Charity pricing.