Dataverse Database Capacity add-on — Pricing, Plans & What's Included

The Dataverse Database Capacity add-on is an add-on purchase that increases available Dataverse database storage for a Commercial tenant. It is intended for organizations that already use Dataverse and need more room for Dataverse data, not for organizations trying to buy a new app or a core user license.

The Dataverse Database Capacity add-on includes additional Dataverse database capacity, because its purpose is to expand the storage available for Dataverse data. It is sold as a Commercial add-on with monthly and annual commitment options, depending on how much flexibility or commitment the organization wants.

The Dataverse Database Capacity add-on does not include a standalone application, a full service subscription, user access rights, a new Dataverse environment, a migration project, or deployment services. It also does not include other capacity types, AI credits, automation entitlements, request capacity, or Copilot rights unless those are separately licensed and confirmed.

No, this should not be treated as a standalone license, because it is an add-on capacity purchase for Dataverse. Your organization must still have any required qualifying Microsoft service subscriptions and user access licenses for the apps and services that use Dataverse.

A Commercial customer should buy the Dataverse Database Capacity add-on when Microsoft capacity reporting shows that Dataverse database storage is the constraint. It is not the right purchase if the issue is file capacity, log capacity, API limits, Power Platform requests, user licensing, or a missing application license.

Commercial customers can buy the Dataverse Database Capacity add-on as a monthly commitment with monthly billing, an annual commitment with annual upfront billing, or an annual commitment with monthly billing. Annual upfront is generally the lowest-rate posture, annual commitment paid monthly provides payment spread with a longer commitment, and monthly commitment provides the most flexibility.

You should confirm the exact capacity pressure in the relevant Microsoft admin experience, because Dataverse database capacity is only one type of storage or service limit. If the report shows file, log, request, automation, AI, or another limit, this add-on may not solve the issue and IT Partner should validate the sizing before purchase.

Dataverse Database Capacity is capacity licensing, not a user license, because it increases available Dataverse database storage rather than granting a person access. Microsoft’s exact application and management rules can depend on tenant, subscription, and environment configuration, so IT Partner should confirm how the capacity will appear and be consumed before final sizing.

No, the Dataverse Database Capacity add-on does not include Teams, Dataverse for Teams entitlements, Microsoft Copilot rights, or AI capacity by itself, because it is specifically a Dataverse database storage add-on. If the workload involves Teams-connected apps or Copilot, confirm that the measured constraint is Dataverse database capacity before buying this add-on.

No, the Dataverse Database Capacity add-on does not include Power Apps, Power Automate, or Dynamics 365 user rights, because it only adds database capacity for Dataverse. Users still need the appropriate licenses and service entitlements for the applications, flows, or Dynamics workloads that access the Dataverse data.

No, adding Dataverse Database Capacity does not by itself change security roles, audit settings, encryption behavior, retention policies, DLP policies, or compliance configuration, because it is a capacity add-on rather than a security feature. Security and compliance remain governed by the Microsoft services in use and by the tenant’s administrative configuration.

No, buying the Dataverse Database Capacity add-on should not be assumed to change data residency, geography, or tenant region, because it adds capacity rather than moving data. Customers with residency or sovereign-cloud requirements should confirm their tenant location, Power Platform environment region, and Microsoft service terms before purchase.

Start by reviewing Microsoft capacity reporting for the tenant and confirming that the shortage is specifically Dataverse database capacity. Then choose the commitment option that matches the organization’s procurement preference, and have IT Partner validate prerequisites, current usage, and expected growth before the order is placed.

No, the Dataverse Database Capacity add-on does not include migration, app build, environment design, data cleanup, or deployment services, because it is a licensing add-on. If the storage issue is caused by legacy data, poor environment design, or a planned migration, those services should be scoped separately from the capacity purchase.

Yes, a CSP partner transfer is typically a billing and subscription-management change rather than a data migration, so it should not interrupt Dataverse apps or move tenant data. The Microsoft Commercial offer remains the same offer family, but IT Partner should validate the transfer path, timing, taxes, promotions, and any partner-specific quote details before the change.

Renewal and cancellation depend on the commitment selected, because monthly commitment is designed for more flexibility while annual commitment creates a longer obligation. Annual subscriptions, including annual subscriptions paid monthly, are subject to Microsoft CSP cancellation and renewal rules, so cancellation timing should be confirmed before purchase.

Capacity needs can often be adjusted, but the allowed timing and direction depend on the Microsoft CSP subscription rules and the selected commitment. In general, increases are easier during a term than reductions, while reductions on annual commitments are commonly handled at renewal, so IT Partner should confirm the exact change rules before ordering.

No, a government customer should not assume the Commercial add-on is appropriate for GCC, GCC High, or other government cloud requirements, because those environments have separate eligibility, residency, and cloud-specific purchasing considerations. Government customers should validate the correct Government segment offer and tenant type before buying capacity.

A nonprofit should use the correct Charity or nonprofit-eligible purchasing path when eligible, because nonprofit licensing and grants can differ from standard Commercial purchasing. If the organization is not eligible or chooses Commercial procurement, it should still confirm that the purchase is for Dataverse database capacity and not for user licensing or another capacity type.

An education customer should confirm whether it should purchase through the Education segment, because student, faculty, and staff eligibility can affect Microsoft licensing and procurement. The Dataverse Database Capacity add-on itself is capacity rather than a student or faculty user license, so the school still needs the correct underlying user and service entitlements.