Power Apps pricing and licensing for internal apps

Procurement is pricing an employee approval app and a supplier portal. Power Apps pricing starts at $20 per user per month, paid yearly, for Premium on Microsoft’s US pricing page, checked October 12, 2026. That is the employee-license starting point, not a complete quote for the portal, automation, storage, or implementation.

Separate the people using the app from the people visiting the portal, then map the data and automation each needs. Permute publishes this breakdown and sells connected business data and custom software with implementation support. Prices below are Microsoft’s published US figures; your agreement, purchasing channel, and checkout determine the amount you pay.

Published prices and the unit each one buys

Microsoft’s licensing guidance lists Premium at $12 per user per month with a minimum purchase of 2,000 licenses, paid yearly. Its Developer Plan is free for nonproduction building and testing. Keep those offers separate when comparing a small production rollout with an enterprise commitment.

The portal rates come from Microsoft’s Power Pages pricing page. Capacity applies per website and calendar month. Anonymous access is a different access model; do not use its lower rate to budget a supplier workflow that requires a private account and documents.

Check existing licenses against the proposed data sources

Microsoft’s licensing overview says some Microsoft 365 subscriptions include limited Power Apps and Power Automate rights for Microsoft 365 data and standard connectors. Those rights do not equal a standalone Premium license. A Dataverse service plan appearing in the admin center also does not establish rights to run an unrelated custom app.

List every connector used by the employee app and its supporting flows. Ask the administrator to classify each against current licensing terms before treating existing subscriptions as sufficient. Include custom connectors and on-premises access in that review; moving the connection into a flow does not make the licensing question disappear.

Microsoft’s Power Apps licensing FAQ says users need appropriate rights to run apps and that the required rights depend on the app’s context. Count everyone who will use the production workflow, including occasional reviewers. Purchasing a license for the maker does not establish coverage for the rest of the department.

Verify per-app availability through your purchasing channel

Older Power Apps licensing comparisons may show a per-app subscription as a universal entry option. Microsoft’s per-app sales notice describes an end of sale effective January 2, 2026, with channel-specific exceptions. Its clarification says existing and new Cloud Solution Provider customers can continue to purchase, use, and renew the subscription.

The same notice distinguishes existing Enterprise Agreement customers from Microsoft Products and Services Agreement customers. Give the reseller your agreement type and ask for an orderable SKU and written renewal terms. Do not treat the subscription SKU and an Azure pay-as-you-go meter as interchangeable just because both reference an app.

Price external access alongside the employee app

For a supplier portal built with Power Pages, count authenticated visitors to each site during the month. Microsoft’s pricing page says the authenticated subscription is sold in packs of 100, allocated at the environment level. A visitor using several sites can require capacity for each site. Power Apps Premium also grants assigned users Power Pages rights. Ask the licensing owner to confirm whether existing entitlements cover particular visitors and the site’s tenant before buying duplicate coverage.

Keep licensing separate from data access. A supplier with a valid portal account must still be restricted to the records intended for that supplier. Specify the private document, row, and approval boundaries before selecting an access model; a visitor allowance does not configure those rules.

As an illustrative budget, assume 50 employees each need a new $20 Premium license and one portal needs a single $200 authenticated-user pack. Multiplying those published rates gives $1,000 plus $200, or $1,200 per month equivalent and $14,400 per year. This calculated subscription baseline excludes taxes, extra capacity, separately licensed automation, and delivery work. It assumes those products and allowances fit the actual requirements.

Check automation context and shared storage

Microsoft’s Power Automate licensing FAQ limits the automation rights included with Power Apps to the app’s context. It distinguishes flows supporting the app and its data from unrelated automation requiring standalone licensing. Have the technical owner classify each flow and confirm any required association with the app.

For procurement, an approval notification and a company-wide data maintenance job need separate licensing review, even if the same employee built both. Document what triggers the flow, which data it accesses, and which application it supports. Check desktop automation and AI services as additional requirements rather than assuming the app license covers them.

The same Microsoft FAQ lists 250 MB of Dataverse database capacity and 2 GB of file capacity accrued per Power Apps Premium license. These entitlements join the tenant’s pool; they are not reserved storage for the application being budgeted. Review available capacity and consumption across the tenant before estimating an add-on.

Estimate structured records, uploaded files, and retained logs as distinct workloads. An onboarding form can store little structured data while retaining large attachments. Ask the administrator to reconcile those estimates with the applicable storage categories, retention policy, and other applications already using the pool.

Budget reusable definitions and production ownership

If the employee app reads NetSuite supplier records and an Excel onboarding register, someone must decide how supplier IDs match and which source controls approval status. Put that work in the implementation estimate. Use the same approved definition of an eligible supplier in the portal, internal queue, and management report so a policy change can be reviewed across all three.

Require acceptance evidence for a disputed supplier match, a revoked user, a failed refresh, and a repeated submission. Assign the person who corrects each failure after launch. Include release management and maintenance in the budget, with a distinction between the initial delivery and later policy changes.

Compare alternatives using that same scope. The Retool pricing breakdown helps compare a different internal-tool cost structure without equating a subscription with a delivered application. Keep the user counts and required workflow constant when requesting estimates.

If you are also considering a prompted build, the AI app builder comparison separates editing choices from backend and support responsibilities. Account for the people who will verify generated code and maintain source connections in that option’s budget.

Permute: scope the connected application and its support

Permute sells connected business data and custom software with implementation support. We connect approved sources, reconcile records, and apply the business rules your team approves. Your developers or our engineers can build applications using that prepared data, with current permissions governing access.

Reusable definitions let the procurement queue and its reporting use the same supplier identities and eligibility rules. An operations manager can inspect the evidence behind an exception instead of comparing unexplained statuses across screens. The custom software offering describes how the data work, application, and engineering support fit together.

Request an estimate for the same sources, users, actions, and maintenance obligations used in the Power Apps budget. We scope implementation and support around that work. Compare the delivered result and ongoing responsibilities alongside the software subscriptions.

Confirm implementation boundaries before committing

Permute app hosting is in early access for externally compiled static frontends; building and editing happen outside the hosting service. A general server runtime is outside that scope. Confirm availability and architecture before assuming an existing Power Apps application can be moved without redevelopment.

External writes require a verified, permissioned action path; a reporting connection does not establish support for every source-system change. Your team approves business policy and resolves exceptions requiring judgment. Microsoft licensing remains governed by your Microsoft agreement, regardless of which services prepare the app’s data.

Price the employee app and supplier portal from their respective users and access models. Check existing entitlements, purchasing-channel availability, automation context, and shared capacity before approving the subscription. Add the work to define supplier eligibility, verify access, and maintain the application. The completed budget should assign both a cost and an owner to the production workflow.

Questions about a Power Apps budget