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

The Dataverse Database Capacity add-on is a nonprofit-priced capacity add-on for eligible Charity tenants that need more Dataverse database storage. It adds database capacity because it is a storage expansion SKU, not a new application, user license, or full Power Platform plan.

The Charity Dataverse Database Capacity add-on includes additional Dataverse database capacity as listed in the Microsoft/CSP catalog. It is appropriate when structured Dataverse data is the constraint, because it expands database capacity rather than file, log, user, or app entitlements.

The Dataverse Database Capacity add-on does not include user rights, base application licenses, Power Apps licenses, Dynamics 365 licenses, Dataverse file capacity, Dataverse log capacity, or professional services. Those are separate because this SKU is a non-core capacity add-on, not a standalone service license.

Usually no, because the Dataverse Database Capacity add-on is intended to supplement qualifying base licensing and eligible Dataverse environments. Before purchase, IT Partner should confirm that your tenant has the required base licenses, environment type, and Microsoft nonprofit eligibility.

You need Dataverse database capacity when structured table data is consuming the storage, because Dataverse separates database, file, and log capacity. If attachments, images, documents, or audit/log data are driving consumption, a different add-on may be required, so review Power Platform admin center capacity reports before ordering.

Dataverse capacity is generally managed at the tenant capacity level rather than assigned like a user seat, because it supports eligible Dataverse environments under the tenant. Internal chargeback by department can be handled administratively, but the Microsoft capacity entitlement itself is not a normal per-user license.

The add-on does not by itself convert a Microsoft Teams app into a fully licensed Dataverse solution, because Dataverse for Teams and full Dataverse have different licensing and capacity rules. If a Teams-based app has outgrown its included limits, confirm whether you need Power Apps licensing, full Dataverse environments, and the correct type of Dataverse capacity.

No, the Dataverse Database Capacity add-on does not include Copilot, Copilot Studio, or AI licensing because it only expands Dataverse database storage. Copilot or AI features may require separate licenses, capacity, security configuration, and eligibility checks.

No, buying Dataverse Database Capacity does not grant users access to data, because access is controlled through Dataverse security roles, environment permissions, Microsoft Entra ID, and app licensing. The add-on increases storage capacity but does not relax security, compliance, or role-based access controls.

No, the add-on does not choose or move your data residency location, because residency is governed by the tenant, environment region, Microsoft cloud, and service configuration. If your nonprofit has grant, donor, health, education, or government data requirements, confirm the target cloud and Dataverse environment region before purchase.

After purchase, the added capacity should be reflected for the tenant in Microsoft capacity reporting rather than installed on a device, because it is a cloud capacity entitlement. Administrators should verify the subscription, check Power Platform admin center capacity, and monitor which environments are consuming database storage.

Not necessarily, because the add-on increases available Dataverse database capacity and does not require a data migration by itself. A migration, cleanup, archiving, or environment redesign project may still be needed if the storage issue is caused by poor data model design, duplicated data, attachments stored in the wrong place, or unmanaged growth.

If the tenant exceeds available Dataverse database capacity, administrators may see capacity warnings and may be blocked from certain capacity-dependent actions, because Microsoft enforces Dataverse capacity at the tenant and environment level. The practical remedies are to reduce database usage, archive or delete data, optimize the data model, or add the correct Dataverse capacity.

For eligible Charity tenants, the catalog shows a one-month term billed monthly, a one-year term paid upfront, and a one-year term paid monthly. Annual upfront is typically the lowest listed total commitment, annual paid monthly spreads payment across the year, and month-to-month provides the most flexibility.

You can typically increase capacity during a subscription term because adding more quantity expands the entitlement. Reductions and cancellations are more restricted under Microsoft CSP term rules, often only allowed during the applicable cancellation window or at renewal, so confirm the exact subscription term before ordering.

Renewal follows the selected CSP term, because the add-on is sold as a subscription commitment rather than a one-time purchase. Before renewal, review actual Dataverse database usage, planned projects, and nonprofit eligibility so you do not renew too little or too much capacity.

Yes, a CSP partner transfer or new CSP ordering relationship should not migrate or interrupt your Dataverse data, because the tenant and Microsoft cloud service remain in place. The main work is commercial and administrative: confirming tenant access, eligibility, existing subscriptions, renewal timing, and the correct add-on SKU.

No, your Microsoft tenant, Dataverse environments, users, and data remain yours because CSP management changes the purchasing and support relationship, not the identity of the tenant. For the same eligible Microsoft CSP offer and term, IT Partner can quote the same Microsoft catalog pricing basis, subject to taxes, currency, and any separate services.

Yes, the Charity version requires Microsoft nonprofit eligibility because it uses Non-Profit Pricing. It should not be assumed to be covered by a grant, because Microsoft grants and donated offers apply only to specific eligible products and quantities; Education student or faculty licensing and standard Commercial licensing are separate purchasing paths that should not be mixed without an eligibility review.

Do not assume that the Charity Dataverse Database Capacity add-on applies to GCC or GCC High, because Government clouds have separate eligibility, cloud boundaries, and catalog availability. If your nonprofit operates under government requirements or needs GCC High, confirm the correct Government-cloud SKU, residency model, and tenant type before transacting.