Power Apps Per App (1 app or website) — Pricing, Plans & What's Included

Power Apps Per App (1 app or website) is a focused Commercial license for one specific Power Apps app or one website, because it is designed to match licensing to a defined business scenario rather than unlimited app usage. It is typically used for a departmental app, request process, inspection app, intake workflow, or another single business process tool.

Power Apps Per App includes rights for the licensed scope of one app or one website, because the offer is measured per app-or-website access rather than broad platform access. Commercial buyers can choose from month-to-month, annual commitment paid upfront, or annual commitment paid monthly purchasing options.

Power Apps Per App does not include unlimited Power Apps usage, because the license is limited to one app or one website. It also does not include Dynamics 365 application licenses, Power BI Pro, Microsoft 365 apps, or other standalone Microsoft cloud services, and architecture-dependent items such as extra capacity, connectors, or separate service plans may still be required.

Yes, each user who needs access must be properly licensed under the right Power Apps licensing approach, because this license does not automatically cover every user in the organization. Before purchase, confirm the user population, access pattern, and whether one app or one website is the correct scope.

No, one Power Apps Per App license is for one app or one website, because the entitlement is intentionally limited to that licensed scope. If users need additional apps or websites, you should confirm whether to buy additional per-app licensing or move to a broader Power Apps plan.

Power Apps Per App is sold as a license for one app or one website, because the current offer scope explicitly includes that one-app-or-website model. You should still confirm the website architecture, authentication model, capacity needs, and any related Power Pages licensing requirements before purchase.

Power Apps Per App can be appropriate for a single app that uses premium Power Platform capabilities, because it is a Power Apps licensing path for a defined app or website scenario. However, the final app architecture matters: premium connectors, Dataverse usage, Power Automate flows, AI Builder, capacity, or separate service licenses may create additional requirements, so IT Partner should validate the design before purchase.

No, Power Apps Per App is not a Microsoft 365 suite license, because it licenses access to one Power Apps app or one website rather than Teams, Outlook, Word, Excel, or other productivity services. Microsoft Copilot, Copilot Studio, and related AI services are separate offerings unless explicitly included in another eligible license or add-on.

Not always, but users generally need an identity in the tenant and any separate licenses required for services the app relies on, because Power Apps Per App does not replace base productivity, email, Teams, SharePoint, or Dynamics licensing. If the app connects to Microsoft 365, Dataverse, Dynamics 365, or third-party systems, confirm the prerequisite licenses for those services.

No trial is listed for this Commercial CSP offer, because the available Commercial options are paid commitment and billing choices. If you need validation before production purchase, use a controlled proof of concept and confirm whether separate Microsoft trial or developer options are available for your tenant.

Start by identifying the exact app or website, the user list, the environment, connectors, Dataverse usage, and any related Power Automate flows, because those details determine whether the per-app license is sufficient. IT Partner can then help configure the Commercial purchase, assign the licensing correctly, and right-size the plan before rollout.

Yes, Power Apps Per App is often a good fit for pilot-to-production rollout of one defined app or website, because it lets the organization license the specific users who need that scenario. Before production, validate security roles, data sources, connector licensing, capacity, and the current Microsoft assignment or allocation process for the tenant.

Security is managed through the Power Platform and Microsoft Entra controls used by the tenant, because the license grants app or website access but does not replace identity, environment, role, data loss prevention, or governance configuration. Administrators should configure environments, security roles, DLP policies, connector controls, and monitoring according to the organization’s compliance requirements.

No license by itself guarantees compliance, because compliance depends on tenant configuration, data location, connectors, app design, access controls, and operational processes. Commercial customers should validate regulatory requirements, Microsoft service compliance documentation, and any industry-specific controls before deploying the app.

Usually no, Commercial licensing should not be assumed to fit GCC, GCC High, or other government cloud requirements, because government clouds have separate eligibility, availability, compliance, and residency considerations. Government buyers should confirm whether they need the Government segment offer and whether the target cloud is GCC, GCC High, or another sovereign environment before purchase.

No, the license alone does not determine data residency, because residency depends on the tenant region, environment region, Microsoft cloud, connectors, data sources, and service architecture. If residency is a requirement, confirm the Power Platform environment configuration, connected systems, and whether Commercial cloud is appropriate before buying.

Renewal and cancellation follow Microsoft CSP subscription rules for the selected commitment term, because month-to-month and annual commitments have different flexibility. Seats can generally be added during a term, while reductions or cancellations are more restricted and are typically handled at renewal or within Microsoft’s applicable cancellation window, so confirm the exact terms before purchase.

Choose month-to-month when flexibility is most important, because it is the most flexible listed Commercial option. Choose annual paid upfront when you want the lowest listed annual total, or annual paid monthly when you want an annual commitment but prefer spreading payments over the year.

Yes, buying through or moving CSP management to IT Partner can normally be done without app migration or user downtime when the same Microsoft tenant remains in use, because the Power Apps environments and data stay in the tenant. IT Partner should still review current subscriptions, renewal dates, license assignment, and any overlap plan before making changes.

IT Partner can transact the same Commercial CSP offer at Microsoft’s current listed CSP pricing for the selected term and billing option, because the product remains the Microsoft Commercial offer rather than a different edition. Final billing can still vary based on taxes, promotions, term selection, billing frequency, and tenant eligibility, so confirm the quote before ordering.

Not automatically, because Microsoft has separate Charity and Education segments that may have different eligibility rules, offers, and purchasing context. Nonprofits should confirm charity eligibility and any grant-related options, while education institutions should distinguish student, faculty, and staff licensing needs before choosing Commercial licensing.