Why small Power Apps projects often unexpectedly pay for Dataverse storage, and how to avoid it from the start.
A small team builds a first application with Power Apps, for example a digital checklist or a simple form for field service. The license is quickly purchased, Dataverse runs in the background automatically, and everything starts inexpensively.
Only after a few months of productive operation does a warning appear in Power Platform administration: storage capacity is exhausted, and the next bill contains a line item that no one had planned for. This is exactly the Dataverse cost trap: the included storage quota is significantly smaller for small projects than most expect.
Each Power Apps license comes with only a very small Dataverse quota that quickly reaches its limit with active use. According to the Power Platform License FAQs from Microsoft each Per-App license receives an additional 50 MB of database and 400 MB of file capacity, a Per-User license receives 250 MB of database and 2 GB of file capacity, each on top of the tenant-wide base quota. According to Microsoft, this base quota has been 5 GB of database storage per tenant since January 2021, previously it was only 1 GB. Those starting with two or three licenses thus often have only a few hundred megabytes of additional database capacity, not the gigabytes you would expect from a full database.
File capacity runs short fastest, not the database, because attachments like photos, receipts, or PDF documents quickly consume several megabytes per record. An app that field service workers use to attach two or three photos for each job fills a small file quota within weeks. Log capacity is equally underestimated: as soon as change tracking is enabled for a table, log storage grows regardless of whether new records are created at all, simply because every change is logged. In practice, we see the same pattern over and over at NordFlux: small Power Apps projects are planned with focus on app functionality, Dataverse capacity doesn't appear in the budget at all because it remains inconspicuous in the first month.
Additional capacity can be purchased either as a fixed Capacity Add-on or on a usage basis via Pay-as-you-go, at different prices. As a Capacity Add-on, 1 GB of additional database capacity costs 40 USD per month, 1 GB of file capacity 2 USD per month, and 1 GB of log capacity 10 USD per month, according to Microsoft's Power Platform License FAQs. Via Pay-as-you-go, that is, billing directly through an Azure subscription, the rates according to the Microsoft documentation on Pay-as-you-go meters at 48 USD per GB database, 2.40 USD per GB file, and 12 USD per GB log, are somewhat higher. Microsoft itself points out that actual prices may vary depending on the contract, but the order of magnitude shows why database capacity in particular is significant: if you only need 5 GB additional, you'll quickly pay an extra 200 USD per month, without a single new user license being added.
The most effective lever is to plan capacity from the start rather than noticing it only when the warning appears in Admin Center. This includes regularly checking the storage quota in Power Platform Admin Center rather than only reacting to a warning message, enabling change tracking only for tables where it is functionally needed, placing large attachments externally where possible instead of in Dataverse, and already when choosing a license between Per-App, Per-User, and development environment—which is hard-capped at 2 GB database and cannot be expanded—considering the actual storage needs. If you're planning a Power Automate-supported automation or a broader Power Platform consultation you should include Dataverse capacity as part of the calculation from the start, not as an afterthought cost item.
A Per-App license includes an additional 50 MB of database and 400 MB of file capacity, a Per-User license includes 250 MB of database and 2 GB of file capacity, each in addition to the tenant-wide base quota of 5 GB database storage.
As a Capacity Add-on, 1 GB of database storage costs 40 USD per month, 1 GB of file storage 2 USD, and 1 GB of log storage 10 USD. Via Pay-as-you-go, the rates are somewhat higher at 48, 2.40, and 12 USD per GB.
Usually it's due to attachments like photos or documents that fill file capacity, or enabled change tracking that continuously consumes log storage regardless of new records.
Yes. Disabling auditing for unneeded tables, externalizing large attachments, and regularly checking capacity in Power Platform Admin Center often reduces demand more clearly than simply buying additional capacity.
It depends on consumption: Pay-as-you-go fits when demand is variable and difficult to plan, a fixed Add-on usually pays off once the additional demand remains stable over months because unit prices are lower with the Add-on.
NordFlux builds digital employees for organisations: automations and AI agents that take over repetitive work. You stay in control.
When a Flow Needs a Premium Connector and What the Required License Per User or Per Flow Really Costs. Calculated Honestly.
In a free initial analysis, we examine with you how much Dataverse capacity your Power Apps project actually needs, and where storage and license costs can be avoided from the start.
