Dataverse Database Capacity add-on for Government — Pricing, Capacity & What’s Included

Dataverse Database Capacity add-on for Government is extra Dataverse database storage for eligible Government catalog customers, because it increases the database-capacity pool used by compatible Dataverse environments. It is an add-on, not a standalone Power Apps, Power Automate, Dynamics 365, or Dataverse user license.

It includes additional Dataverse database capacity measured per GB, because it is intended to expand storage for structured Dataverse data in compatible Power Platform or Dynamics 365 environments. It does not include Dataverse file capacity, Dataverse log capacity, app licenses, user access rights, migration services, or application design work.

No, because this product only adds database storage capacity and does not grant application or user rights. Users still need the appropriate Power Platform or Dynamics 365 licenses for the apps, flows, or Dynamics workloads they will use.

Dataverse database capacity is for structured relational data in Dataverse, while file capacity and log capacity cover different storage categories. You should confirm consumption in the Power Platform admin center before buying, because purchasing database capacity will not fix a file-capacity or log-capacity shortage.

Government customers can buy the add-on through the Government catalog with a monthly commitment billed monthly, or an annual commitment billed either annually or monthly. Annual upfront is typically the best overall commitment structure, annual commitment with monthly billing is next, and monthly commitment gives the most flexibility.

No, this Government add-on does not have a trial in the provided catalog data, because it is sold as paid capacity rather than a trial service. If you are testing a new workload, confirm the base environment and licensing first, then size only the capacity you actually need.

Eligible Government segment customers can purchase the Government version, because it is tied to the Government catalog and customer eligibility rules. IT Partner should confirm the customer’s tenant, catalog, and eligibility before ordering to avoid buying under the wrong segment.

Do not assume one Government SKU covers every government cloud, because GCC, GCC High, and DoD availability, residency, and ordering paths can differ. Confirm the exact tenant cloud and Government catalog with IT Partner before purchase, especially when compliance or data residency requirements drive the decision.

No, adding database capacity does not by itself change tenant residency, security configuration, retention policy, or compliance boundary, because it is a storage entitlement rather than a governance control. Validate residency, cloud boundary, encryption, auditing, and compliance requirements separately for your specific Government tenant.

Yes, it can be used with compatible Dataverse-enabled Dynamics 365 Government environments, because Dynamics 365 apps commonly store structured data in Dataverse. It does not replace the required Dynamics 365 user or application licenses.

Yes, it can support compatible Dataverse-enabled Power Apps environments, because those environments consume Dataverse database capacity. It does not include Power Apps user rights, so the users and makers still need the appropriate Power Platform licenses.

Not necessarily, because Dataverse for Teams has its own limits and environment model and should not be treated the same as a standard Dataverse environment. If a Teams app has outgrown Dataverse for Teams, confirm whether it must be moved to a standard Dataverse environment and whether this database add-on is the right capacity purchase.

No, because Dataverse Database Capacity add-on for Government only adds Dataverse database storage. Microsoft Teams, Microsoft 365 Copilot, Copilot Studio, Power Platform, and Dynamics 365 rights must be licensed separately where required.

It can help only if the workload is consuming Dataverse database capacity, because the add-on expands the database-capacity pool. It does not include Copilot Studio, Microsoft Copilot, AI credits, or user access rights, so confirm both the licensing and the storage bottleneck before ordering.

Size it from actual Dataverse database consumption in the Power Platform admin center, because database, file, and log usage are tracked separately. Review current usage, growth rate, environment plans, and any upcoming migrations before selecting the quantity.

Usually no migration is required just to add capacity, because the entitlement increases available Dataverse database storage for eligible environments in the tenant. Application changes, environment moves, or Dataverse for Teams-to-Dataverse transitions may require separate planning.

Yes, a CSP partner change normally does not move your Dataverse data or interrupt service, because the workloads remain in your Microsoft tenant. IT Partner should confirm the current subscription, Government catalog, term, renewal date, and authorization steps before the transfer.

The Microsoft service and underlying tenant do not change just because the CSP partner changes, because Dataverse remains provisioned by Microsoft in your tenant. The applicable Government catalog, commitment term, reseller quote, taxes, billing dates, and any support terms should still be confirmed before transfer.

Increases are generally easier than reductions, because capacity subscriptions are governed by the selected commitment term and Microsoft CSP change rules. Reductions, cancellations, and billing-frequency changes may be limited after the allowed adjustment window or until renewal, so confirm the exact rules before ordering.

No, customers should buy under their own eligible segment, because Government, Charity, Education, and Commercial catalogs are separate purchasing paths. Nonprofit grant eligibility, student-versus-faculty education eligibility, and standard business licensing do not automatically qualify a customer for the Government add-on.