Power Apps in 2027: app access, licensing enforcement and higher costs

Your users could lose access to affected Power Apps from February 2027 if they do not have the appropriate licences. Microsoft is tightening enforcement of existing requirements that it says have been applied leniently, and users without the required coverage will be unable to open those apps until an appropriate licence is assigned. The enforcement announcement comes alongside a Power Apps Premium price increase from January 2027 and an earlier AI Builder credit transition from November 2026. Each affects a different part of your access rights or costs.

• App access: February 2027 enforcement includes apps in Managed Environments, model-driven apps and custom apps outside the licensed Dynamics 365 context. Microsoft's examples are not exhaustive.

• Premium prices: From 1 January 2027, the published United States (US) annual-billing rates rise from $20 to $22 per user per month, or from $12 to $14 for the qualifying 2,000-seat offer. Existing subscriptions retain their current price until their term ends.

• Licensing alternatives: Premium, per-app subscriptions and the per-app pay-as-you-go meter can satisfy premium use-right requirements, subject to the licence and app context. Their costs and purchasing availability differ.

• AI Builder: Eligible licences purchased or renewed from 1 November 2026 receive no included AI Builder credits. Existing qualifying terms retain their credits until expiry, and AI Builder features remain supported through Copilot Credits.

Which apps face access restrictions?

If your app is affected, a user without the required licence cannot open it. The reason your existing coverage may be insufficient depends on the app and where it runs.

A Power Platform environment is a space in which you store, manage and share business data, apps and automated workflows, which Microsoft calls flows. You can use separate environments to keep apps apart by department, audience or security requirement, as Microsoft's environment overview explains. Enabling Managed Environments adds premium administrative capabilities to an environment, such as limits on app sharing and usage insights.

The app's design also affects its licensing. Model-driven apps organise forms, views and charts around data held in Dataverse, Microsoft's database platform for these apps. Canvas apps give the designer control over the screen layout. Microsoft's app-design overview explains that distinction. The enforcement guidance identifies the following three examples.

Sources: Power Apps licensing frequently asked questions (FAQ), Managed Environments licensing and Power Platform licensing guide. Microsoft's FAQ presents examples, so the table is not an exhaustive list of affected scenarios.

For Managed Environments, Microsoft began administrative notifications in March 2026 and in-app notifications in June 2026. An initial informational message becomes a warning after seven days without an appropriate licence, then an error after another seven days. Blocking follows the final notification stage. Your apps remain in the environment, and access resumes when an appropriate licence is detected, according to Microsoft's end-user experience guidance.

The published start is February 2027. Neither the app FAQ nor the Managed Environments guidance gives an exact universal day or a rollout timetable for each cloud.

Your Microsoft 365 and Dynamics 365 rights have limits

A connector lets an app or flow communicate with another service and use its data or actions. Microsoft's standard and premium classifications determine which licensing rights you need to use those connections. If you rely on Power Apps rights included with Microsoft 365, those rights allow standalone apps extending Microsoft 365 with standard connectors. Premium, custom and on-premises connectors require the relevant standalone rights. The Microsoft 365 licensing FAQ sets out that boundary; the current pricing announcement leaves the included entitlement unchanged.

There is separate historical context for older apps and flows. Extended rights for certain apps and flows dating from before October 2019 ended on 1 October 2024, with in-product enforcement from 1 April 2025. If you had relied on those extended rights, their expiry changed the entitlement available to you and therefore the basis on which paid coverage might be needed. The historical transition FAQ documents that earlier transition. It is separate from the February 2027 enforcement, and the evidence here does not quantify a cost effect.

Your Dynamics 365 licence also needs to be understood in its specific context. The pricing announcement leaves existing included Power Apps entitlements unchanged, but the Power Platform licensing guide limits those rights by Dynamics 365 licence type as well as by the licensed application's context and environment.

Microsoft's documentation distinguishes the right to use Managed Environments from the underlying rights to run an app. The Managed Environments page lists Power Apps, Power Automate, Copilot Studio, Power Pages and specified Dynamics 365 licences and meters among qualifying product families. It also identifies allocated per-app capacity as a route for app users. Its examples say that either Power Apps Premium or Power Automate Premium can satisfy the Managed Environments requirement for a user running apps and flows.

You cannot infer unrestricted rights to run custom Power Apps from eligibility for Managed Environments under Dynamics 365 Team Members, Dynamics 365 Sales Professional or Dynamics 365 Customer Service Professional. The Power Platform guide's summary and Appendix B distinguish Power Apps app rights from Power Automate rights, and the app-rights appendix does not mark any of those three licences as having Power Apps rights. The summary also says Dynamics 365 Pro lacks Power Apps rights.

The Managed Environments page includes Team Members in its eligibility wording and refers to Dynamics 365 Pro use in context. That eligibility wording needs to be read alongside the app-rights limits above. The Dynamics 365 guide's Team Members guidance and Appendix H limit Dynamics 365 Team Members to specified activities and application modules and refer back to the Power Platform guide for included platform rights.

One licence raises three separate questions: whether it makes a user eligible for Managed Environments, whether it carries Power Apps rights, and in which environment those rights apply. Removing the Managed Environments designation settles only the first.

Premium is one of the qualifying licensing routes

Your available choices depend on the apps, their environment and the rights already held. Microsoft's enforcement FAQ explicitly identifies Premium, per-app plans and the per-app pay-as-you-go meter as options that generally satisfy premium use-right requirements, subject to licence and app context. You can also mix Power Apps licence types across your organisation.

Sources: Power Platform licensing guide, Power Platform licensing FAQ, app meter and Premium price announcement. Subscription prices are monthly equivalents based on annual billing. The Premium timing and qualifying conditions are explained below.

App counting has its own boundaries. Embedded canvas components within a model-driven app count as one app for per-app licensing. If you deploy the same app into two environments, a user accessing both needs separate per-app coverage for each, under the app-counting FAQ and licensing guide.

The $10 per active user per app is not the whole pay-as-you-go bill. Dataverse storage above the first 1 GB of database and 1 GB of file capacity is metered separately, AI Builder consumption draws on credits, and in Managed Environments flow usage needs Power Automate licences or per-flow plans of its own.

Per-app purchasing depends on your agreement

The Power Apps per-app end of sale has different consequences across purchasing channels. The $5 option remains available in the circumstances below, so a comparison that assumes either universal availability or universal withdrawal would miss the documented exceptions.

Source: Microsoft's per-app end-of-sale announcement and Cloud Solution Provider clarification.

App coverage does not settle every connected entitlement

Power Apps licences include Power Automate flows within the app's context. Unrelated standalone flows require separate Power Automate licensing, as Microsoft's platform FAQ explains.

An automated flow starts when an event occurs, while an instant flow starts when a user selects a button or control, according to Microsoft's cloud-flow overview. For an automated flow within a Power Apps or Dynamics 365 app's context, the flow must be associated with that app and its owner needs Power Apps Premium or a Dynamics 365 licence. For an instant flow within that app context, every user running the flow needs Power Apps Premium or a Dynamics 365 licence. Microsoft's app FAQ sets out those owner and user requirements. The pay-as-you-go treatment in Managed Environments has a further qualification, explained below.

Trial licences can give you temporary Managed Environments coverage within their restrictions. The Power Apps Developer Plan does not provide the Managed Environments entitlement for users running their assets. Microsoft describes it as a build-and-test plan for non-production use in its pricing page, alongside the Managed Environments licensing restrictions.

Your rights to change data are also limited where restricted tables are involved. Under both the Microsoft Customer Agreement Product Terms and the Enterprise Agreement and Enterprise Agreement Subscription Product Terms, Power Apps users have read-only access to tables designated as restricted in the linked documentation. Those Power Apps rights prohibit creating, modifying or deleting data in restricted tables, while allowing those operations on non-restricted tables.

What the January Premium increase adds to your bill

Microsoft announced the increase on 9 September 2026, raising both affected Premium plans by $2 per user per month. The percentage increase differs because the volume offer starts from a lower price.

Source: Microsoft pricing announcement. Prices are US dollars per user per month based on annual billing. Percentages are calculated as 2 ÷ 20 and 2 ÷ 12, multiplied by 100, with the latter rounded.

The volume offer requires 2,000 or more new user licences under the Power Platform licensing guide. The named product's minimum quantity of 2,000 must be maintained throughout the agreement or enrolment term in both the Microsoft Customer Agreement terms and the Enterprise Agreement terms.

Your existing subscription retains its current price until its term ends. New purchases, renewals and co-terminations with a term beginning on or after 1 January 2027 take the new list price. Co-termination is the alignment of subscription end dates. Microsoft says the increase applies regardless of monthly or annual billing frequency. For your renewal planning, the relevant date is therefore the start of the affected term, as set out in the announcement.

Only the two named Premium plans are affected by that announcement. Other Power Apps and Power Platform products retain their prices, and Microsoft says no Premium capabilities or entitlements are being removed by the price change. Its stated rationale lists artificial intelligence (AI) and app-development capabilities; Dataverse security, resilience and storage capabilities; and administration, governance and application lifecycle management capabilities. Those are Microsoft's reasons for the increase; the commercial effect for you is the higher rate when an affected term begins.

The increase is global, with comparable local-currency pricing. Non-profit and education prices will adjust in line with commercial prices while existing eligible discounts remain unchanged. Microsoft caps US Government list-price increases at 10% annually and says any excess will be phased over two years, according to the same pricing announcement.

Sterling prices and monthly billing need separate treatment

As of 6 October 2026, Microsoft's United Kingdom (UK) pricing page displays £15.40 for Premium and £9.20 for the 2,000-seat-minimum offer, per user per month paid yearly, excluding value added tax (VAT). It cautions that checkout prices can differ because of country, currency and regional factors. Those figures do not establish your January 2027 sterling price.

Microsoft has separately moved Commercial Cloud local-currency updates to an annual January schedule from its 2027 financial year, with the next update effective on 1 January 2027. Product-specific adjustments continue to be communicated separately. The July 2026 currency notice schedules further guidance for November 2026. Neither the Premium announcement nor the UK page supplies January sterling prices or a full future product price table for monthly billing. Those documents establish no future price in pounds sterling (GBP) or euros (EUR), or customer-specific transaction price.

There is also an existing billing-frequency adjustment. From 1 April 2025, Microsoft introduced a 5% adjustment for new and renewing annual subscriptions billed monthly across Buy Online, Cloud Solution Provider and Microsoft Customer Agreement for enterprise. Power Platform is a named category, although not every annual subscription offers monthly billing. If you pay monthly under that arrangement, your commitment still runs for a year. Microsoft's billing announcement also allows for currency and rounding variations.

How app usage changes a pay-as-you-go bill

If you use the Power Apps meter, a person is counted once per app per environment in a month when they open that app at least once. Repeated use of the same app in that month does not add further user-app charges; opening additional apps does. Users already covered by Power Apps per-user licences are excluded, under Microsoft's metering rules.

Pay-as-you-go requires an Azure subscription and is configured at environment level. You can exclude an app from Azure billing and require per-user licensing for it instead. Existing per-app passes in a pay-as-you-go environment are ignored rather than consumed, so prepaid passes and the app meter cannot be combined for different apps in the same environment. Microsoft's pay-as-you-go FAQ and metering guidance set out those conditions.

For Managed Environments, Microsoft says the per-app pay-as-you-go meter satisfies the requirement for all active Power Apps usage in the environment. When that meter is enabled, users whose Microsoft 365 licences provide Power Apps access are not counted or charged by the app meter for apps using standard connectors. That exclusion appears in the metering rules and the Microsoft 365 pay-as-you-go FAQ.

Flow coverage needs a narrower reading. The general meter page describes coverage for flows triggered directly from Power Apps and cloud flows linked to an app using the same data sources. For Managed Environments, however, the Managed Environments page and licensing guide specify that the per-app meter covers Power Apps usage only. Power Automate flow usage there requires standalone Power Automate licences or Power Automate per-flow plans.

Dataverse storage is a separate cost

Your app meter does not absorb every Dataverse charge. Microsoft publishes the following US rates per gigabyte (GB) for storage exceeding applicable included or allocated capacity.

Source: Dataverse capacity meter.

Pay-as-you-go environments include the first 1 GB of database storage and 1 GB of file storage without charge. Log storage has no equivalent free base allowance. Storage exceeding allocated capacity is billed through Azure, as explained in the capacity meter and capacity FAQ.

Capacity accrued from your per-user licences does not apply to a pay-as-you-go environment; it is pooled at tenant level, according to the pay-as-you-go FAQ. Your tenant is the Microsoft service boundary for your organisation that contains its environments, as illustrated in Microsoft's environment overview. The licensing guide says pay-as-you-go environments do not consume tenant-wide Dataverse capacity.

Capacity preallocation and add-ons have separate treatment. The pay-as-you-go FAQ permits you to preallocate capacity to an environment and says capacity add-ons have been usable there since December 2024.

For comparison, Premium accrues 250 megabytes (MB) of database capacity and 2 GB of file capacity per user, pooled at tenant level. Per-app subscriptions accrue 50 MB of database capacity and 400 MB of file capacity, according to the licensing guide.

For Azure cost optimisation, you can see billed totals by meter and billing-plan resource in Microsoft's Azure Cost Management, while the Power Platform admin centre provides downloadable details identifying environments, apps and users. Microsoft says usage can take up to 24 hours to appear in Azure Cost Management. Its usage and billing guidance also documents budgets, alerts and action groups at resource or meter level.

What the published prices produce in worked comparisons

The calculations below separate unit price, licence quantity and activity. They use hypothetical licence populations and usage levels, US annual-billing list prices and a full 12 months at the stated rate. They exclude negotiated discounts, taxes, storage, AI consumption and separate flow charges. They are arithmetic illustrations rather than Microsoft quotations or estimates of your own costs, using the published Premium prices, licensing guide and app meter.

The same licence quantity at the higher price

Source: calculations from Microsoft's Premium prices, using licence quantity × monthly rate × 12. The table shows annualised run rates. Existing term protection prevents treating them as a forecast that every subscription reprices on 1 January.

A change in licence quantity has a separate effect. Consider a hypothetical deployment with 500 ordinary Premium licences at $20, giving a $120,000 annualised licence cost. If 100 additional users are determined to require ordinary Premium and all 600 licences are priced at $22, the annualised amount becomes $158,400. The $38,400 difference comprises $12,000 to reprice the original 500 licences and $26,400 for the additional 100. The calculation uses Microsoft's price inputs. It assumes neither that Premium is the only qualifying option nor that earlier unlicensed use was compliant; the enforcement FAQ describes existing requirements and qualifying alternatives.

App count and monthly activity change the comparison

For a user who needs paid app coverage and uses each counted app every month, the following licence-only comparisons follow from the $5 per-app subscription, the $10 meter and the announced Premium prices. The calculation assumes one environment and ordinary separately counted apps. Embedded canvas components in a model-driven app retain the single-app treatment explained earlier.

Sources: calculations from Premium prices, per-app prices and rights and metering rules. The 2,000-seat minimum terms and per-app purchasing restrictions still apply.

For one app shared with N users, allocating $5 per-app subscriptions costs $5 × N each month. At $10 per billable monthly active user, the meter costs $10 × M, where M is the billable active-user count. The costs are equal when M = 0.5 × N, or half the allocated population. That equality concerns a purchasable per-app subscription and users who need paid coverage. It cannot be applied as a universal crossover against Premium. The inputs and limits come from the subscription price, meter exclusions and counting rules and channel availability.

AI Builder changes can add another renewal cost

If your apps or flows consume AI Builder credits, the November 2026 transition affects the capacity available to them. Since 1 November 2025, new customers without an active AI Builder capacity add-on have been unable to purchase those add-ons. Existing add-on customers could continue purchases and renewals until the 1 November 2026 end-of-life milestone. From that milestone, existing contracts retain their credits until expiry, but add-ons cannot be bought or renewed, under the transition calendar.

For seeded credits, which are included with eligible Power Platform or Dynamics 365 licences, the contract date also determines what remains available. Licences purchased or renewed before 1 November 2026 retain those credits through the applicable contract term. New or renewed licences from that date receive no seeded AI Builder credits. AI Builder features themselves remain supported through Copilot Credits, according to the licensing overview and transition guidance.

A term that begins in November or December 2026 sits between two of the changes. It starts before the 1 January price increase, yet an eligible licence bought or renewed from 1 November already comes without included AI Builder credits.

Your AI Builder credit entitlement does not automatically convert to Copilot Credits. In Power Apps and Power Automate, AI Builder credits are consumed first, followed by Copilot Credits when the former are absent or exhausted. If neither is available, features fail. Consumption resets monthly and unused credits do not roll forward. Microsoft has also discontinued AI Builder trials, as documented in the transition FAQ and licensing overview.

The published cost of AI Builder consumption

The capability rates below use Copilot Credits. Their dollar equivalents use Microsoft's stated pay-as-you-go rate of $0.01 per Copilot Credit; the figures do not convert an existing AI Builder credit entitlement. For large language model prompts, abbreviated as LLM prompts in Microsoft's table, consumption is expressed per 1,000 tokens. A token is a unit processed by the model and can represent a character, part of a word or a whole word. Prompt costs account for input and output tokens, including system instructions and reasoning, so a token count is not a fixed word count. Microsoft's prompt-token guidance explains the charging units.

Source: Microsoft's AI Builder capability rate table.

Your AI consumption costs are separate from the right to run the flow. Microsoft says every AI Builder action, including the business card reader, is a premium connector and makes a Power Automate flow a premium flow. The relevant standalone connector rights described earlier therefore still apply. Under Power Automate pay-as-you-go, each run incurs a separate cloud-flow-run charge in addition to any credit consumption, according to the AI Builder licensing overview.

What your administrators can see and assign

The Power Apps licence-consumption experience in the Power Platform admin centre is labelled preview. It reports purchased, assigned and used per-user licences, allocated and purchased per-app capacity, and linked pay-as-you-go plans. The used per-user count reflects people who launched an app during the previous 90 days, according to the reporting documentation.

Your administrators can download reports of active users, all licensed users and users requiring licences in Managed Environments. The last report includes app and environment details but only covers users who launched an app in the selected month. Someone who has been assigned a qualifying licence can remain on that report until they next launch an app. The download options and Managed Environments report limitations explain why the report is not an immediate view of every potential user or every assignment change.

Access to the reporting also depends on administrative role. Power Platform and Dynamics 365 administrators can access summary and environment views and allocate app passes. Environment administrators can access their own environment view, while tenant administrators can permit summary access through the tenant licensing summary setting. Microsoft documents those reporting permissions separately from licence requirements.

Automatic assignment has capacity and timing limits

Power Apps auto-claim policies can assign available per-user licences when an unlicensed user launches a premium app or an app in a Managed Environment. Microsoft documents automatically created policies for specified tenant scenarios, along with controls to disable or delete a policy and scope it to Managed Environments or all environments. Assignment depends on licences being available in your tenant, according to the auto-claim guidance.

Group-based assignment through auto-claim can take up to 24 hours. Auto-claim is unsupported in the US sovereign clouds Government Community Cloud (GCC), Government Community Cloud High (GCC-H) and Department of Defense (DoD), as stated in the same guidance. These government offerings serve eligible US public-sector bodies and other entities handling regulated government data. Microsoft describes GCC High as serving defence contractors and federal agencies, while DoD is available only to Department of Defense entities, in its US Government service description.

Per-app subscriptions use a different assignment mechanism. Your administrators allocate passes to environments, configure apps for per-app use and share the apps with users. Sharing consumes per-app capacity. The subscriptions are not assigned as user licences on the Microsoft 365 admin centre's Billing > Licenses page, according to Microsoft's per-app administration guidance.

The Managed Environments designation is also an administrative setting that can be removed in specified circumstances. Microsoft permits disabling the property through PowerShell only when no Managed Environments capabilities remain in use. Removing that designation addresses the Managed Environments part of the access question. Your app-licensing requirements still depend on the apps and their use rights, including the separate requirements for model-driven apps and apps outside the licensed Dynamics 365 context.

We can help you compare licensing options against your apps, usage and budget.

If you need help assessing your Power Apps access rights and the cost of the available licensing options, contact SAMexpert. We do not sell Microsoft licences or cloud services, so our advice is independent of the product or purchasing route you choose.