Dynamics 365 Storage Capacity: Planning for Growth and Managing Storage Costs
Table of Contents
Introduction
If you manage a Dynamics 365 environment, you’ve probably hit a storage capacity warning at some point. By the time it shows up, the data’s already in, more arrives daily, and management wants to know why nobody caught it sooner.
Here’s the uncomfortable truth: Dynamics 365 storage capacity is rarely a technical problem. It’s a planning problem wearing a technical costume. The platform will show capacity warnings, but those alerts usually arrive after the storage pattern is already expensive to fix. By the time admins see Database, File, or Log capacity approaching its limit, the bigger issue is often not the warning itself. It is the fact that files, logs, integrations, sandbox copies, or historical data have been allowed to grow without a clear storage strategy.
This guide breaks down how the storage model actually works, where costs build up unnoticed, and how to stay ahead of capacity issues instead of scrambling when the warning hits.
How Does Dynamics 365 Storage Pricing Actually Work?
Dynamics 365 splits storage into three separate pools: Database, File, and Log, each with its own price and entitlement. The platform won’t stop you from filling the expensive pool with data that belongs in a cheap one.
This is important because older Dynamics 365 storage reporting did not give teams the same level of visibility into what was driving consumption. The current Dataverse model separates storage into Database, File, and Log pools, making it easier to identify where capacity is being used and where costs may increase.
| Pool | What It Holds | Approx. List Price |
|---|---|---|
|
Database |
Structured records (accounts, contacts, cases) + table/field definitions |
~$40/GB per month (drops to ~$30/GB past 1,000 GB) |
|
File |
Attachments, PDFs, spreadsheets, images, emails |
~$2/GB per month |
|
Log |
Audit history (who changed what, when) |
~$10/GB per month |
A single gigabyte of database overage costs roughly $480 a year. That’s not a typo; it’s the number that should reset the way you think about where data lives.
Why Does It Matter Where Your Attachments Live?
Identical data costs wildly different amounts depending on which storage pool it sits in; the gap between Database and File pricing alone can mean a 20x cost difference for the same files.
Picture 50 GB of document-heavy data stored in the wrong Dataverse structure, unmanaged custom table, or legacy attachment pattern. If that data is counted against Database capacity instead of File capacity or an external document store, the cost difference can be significant. At Database storage pricing, 50 GB could represent roughly $2,000/month, compared with about $100/month in Dataverse File storage.
| Location | Cost for 50 GB of Files |
|---|---|
|
Database |
~$2,000/month ($24,000/year) |
|
Dataverse File storage |
~$100/month |
|
SharePoint / Azure Blob |
A few dollars/month |
Storage outcomes depend on how your tables, attachments, integrations, and retention rules are configured. Your finance director will care where that data ends up. Storage line items rarely get scrutiny because nobody owns them, and that’s exactly why they grow.
What Changed in the Recent Dynamics 365 Storage Update?
Microsoft raised default Dataverse storage entitlements twice in quick succession: a broad baseline increase at the end of 2025, followed by a further bump for Sales Premium tenants that reached general availability on April 15, 2026. Both changes were automatic, at no additional cost.
| Storage entitlement | Before Dec 2025 baseline | After Dec 2025 update | Sales Premium update |
|---|---|---|---|
|
Database capacity per tenant |
10 GB |
30 GB |
45 GB |
|
File capacity per tenant |
20 GB |
40 GB |
60 GB |
|
Per-user database accrual |
250 MB |
250 MB |
500 MB |
|
Log capacity |
2 GB |
2 GB |
2 GB |
If your understanding of storage limits predates this year, it’s outdated, and ERP environments have seen similar increases in databases and files over the same period. Log capacity is the exception: it hasn’t moved, so if audit logs are your bottleneck, none of this helped.
The part most teams miss: if you bought storage add-ons before this change to cover an overage, you may now be paying for capacity you don’t need. The new defaults might have already absorbed the gap you were patching.
Make reviewing those add-on SKUs a standing task, not a one-time check:
- Pull a current usage baseline
- Compare it against the new default entitlements
- Cancel or downsize add-ons that are now redundant
You may also like: How a Restaurant Brand Built a Unified Customer Data Platform
Why Can One Sandbox Environment Drain Your Whole Tenant?
Dataverse capacity is pooled at the tenant level, not allocated per environment, so a single forgotten copy of production sitting in a sandbox can push your entire tenant over its limit while every individual environment looks fine.
Your production org, sandboxes, and dev environments all draw from the same tenant-wide allowance. You have to evaluate the whole pool, not a single environment in isolation, or the real problem will stay invisible.
Common causes of unexpected tenant-wide storage growth include:
- Full production copies left running in sandbox environments long after testing is complete
- Multiple development and testing environments with no defined retention strategy
- Large data imports performed in non-production environments
- Environment sprawl caused by years of project and upgrade activity
- Duplicate records and historical data stored across multiple environments
What Should Finance and Supply Chain (ERP) Teams Know About Storage?
If you run Finance and Supply Chain, storage enforcement is catching up to you fast. F&O database consumption used to live quietly in Lifecycle Services, but it’s now on the same capacity reports and pricing logic as every other Dynamics 365 product.
At the ERP scale, the numbers stop being abstract:
- A multi-terabyte production database at $40/GB is a six-figure monthly conversation
- Non-production environments are cheaper per gig, but several full-size copies for testing add up quickly
Large ERP environments generate and retain significant volumes of operational data, including transactions, inventory movements, financial records, audit history, and integration data. Without clear retention policies and environment management practices, storage consumption can grow faster than expected.
Many organizations focus on application performance while overlooking storage growth until additional capacity purchases become necessary. By that point, reducing consumption often requires a larger cleanup effort than ongoing maintenance would have.
If that’s your environment, database housekeeping isn’t a nice-to-have. It needs its own budget line and its own review cadence.
You may also like: Dynamics 365 Field Service Features & Capabilities 2026
Concerned About Rising F&O Storage Costs?
If you're staring down a six-figure storage conversation on an F&O environment, that's exactly the kind of capacity assessment our team runs for clients before it becomes a budget crisis.
Talk to Our ExpertsHow Do You Check Your Current Dynamics 365 Storage Usage?
Go to the Power Platform admin center → Licensing → Dataverse → Summary to review your Dataverse storage capacity. This view shows your tenant-level Database, File, and Log usage against available entitlement. If your organization uses purchased capacity add-ons, you can also check Licensing → Capacity add-ons → Summary for add-on allocation and usage details.
If you manage Finance and Operations storage, Microsoft also surfaces F&O capacity through Licensing → Capacity add-ons, where admins can review tenant-level and environment-level consumption.
For genuine emergencies, Dataverse offers a temporary 25% capacity extension for 45 days. Microsoft allows this extension a limited number of times, so treat it as a bridge while you clean up storage or complete capacity procurement, not as a long-term strategy.
What's the Fastest Way to Reduce Dynamics 365 Storage Costs?
Review document-heavy data first. In many storage cleanups, notes, attachments, emails, imports, and file-heavy custom tables are the fastest places to identify avoidable capacity usage. From there, work through audit retention, dead data, and environment governance in roughly this order:
- Get attachments out of the database. Route files to SharePoint or Azure Blob and keep references in Dynamics. Built-in SharePoint integration covers most cases; Azure Blob is worth it once volumes are large or you need more control over retention and tiering.
- Right-size your audit logging. Auditing every field on every table, left running for years, is what fills the Log pool. Define what compliance actually requires, set a retention period, and let everything older drop off automatically.
- Clear the dead weight. Deactivated flows, leftover migration tables, orphaned records, stale sandbox copies of production, bulk-delete jobs, and retention policies exist for exactly this purpose. Run them on a schedule, not in a panic.
- Set a real environment strategy. Know how many environments exist, what each is for, and how much data each should reasonably hold. Tenants usually hit their limit because environments pile up with no one tracking total usage.
- Make capacity review a recurring task. Fifteen minutes a month with the capacity report catches problems while they’re cheap to fix.
You may also like: Dynamics 365 Implementation Cost
How Can You Prevent Storage Problems Before They Start?
The organizations that avoid storage warnings aren’t the ones with the most spare capacity; they’re the ones who decide where data should live before it lands there, every time a new integration or process goes live.
Dynamics 365 storage cost was never really about how much data you have. It’s about where you let it sit. Get placement right early, and “planning for growth” stops being a budget conversation you dread.
A proactive storage strategy typically includes:
- Defining where documents, attachments, and historical data should be stored before new projects launch
- Reviewing storage consumption trends monthly rather than waiting for capacity warnings
- Applying retention policies to audit logs and inactive records
- Limiting unnecessary environment copies and duplicate datasets
- Evaluating the storage impact of new integrations, automations, and business processes before deployment
Get Ahead of Your Storage Costs Before They Get Ahead of You
Storage warnings are predictable, and so is the fix. If your team is staring at a capacity alert, an unexpected add-on bill, or an ERP environment that's quietly become a six-figure line item, AlphaBOLD can run a capacity assessment, build a retention and environment strategy, and handle the implementation work to put it in place.
Request a ConsultationConclusion
Dynamics 365 storage capacity is not just an IT concern; it’s a cost management and governance issue. Organizations that actively monitor capacity, store data in the right locations, and maintain clear retention policies are far less likely to incur unexpected storage costs or undertake last-minute cleanup projects.
The key is to treat storage as part of your overall Dynamics 365 strategy. Regular capacity reviews, thoughtful environment management, and a clear approach to handling files, logs, and historical data can help control costs as your business grows. With the right planning in place, storage becomes a predictable operational consideration rather than a recurring budget challenge.
FAQs
Dynamics 365 storage capacity refers to the amount of Database, File, and log storage available to your organization. These storage types support different kinds of data, including business records, attachments, and audit history, and are managed at the tenant level.
Database Storage supports transactional business data and application functionality, making it the most expensive storage type. File Storage is designed for documents and attachments and typically costs much less, which is why many organizations use SharePoint for document management.
You can review storage consumption through the Power Platform admin center → Licensing → Dataverse → Summary. For purchased capacity add-ons and Finance and Operations storage, admins can also check Licensing → Capacity add-ons. These views show Database, File, and Log usage against available entitlement.
When storage usage exceeds the available capacity, your organization may need to purchase additional storage. Microsoft also offers temporary capacity extensions in certain circumstances, but these are intended to provide short-term relief while the underlying storage issue is addressed.
Yes. Storage capacity is pooled across the entire tenant rather than allocated to individual environments. This means production, sandbox, test, and development environments all consume capacity from the same storage allocation.
Explore Recent Blog Posts
