Dataverse Database Capacity add-on for Education — Pricing, Plans & Capacity Details

The Dataverse Database Capacity add-on for Education is an add-on SKU for buying additional Dataverse database capacity under the Microsoft Education pricing segment, because it is not listed as a core product or standalone user license. It is intended for an eligible education tenant that already has, or is planning to use, Microsoft services that depend on Dataverse.

This SKU includes a Dataverse database capacity add-on purchase option for the Education segment, because the catalog identifies it specifically as Dataverse Database Capacity add-on. It includes catalog term options for monthly commitment and annual commitment, but the exact capacity increment per purchased quantity should be confirmed in the Microsoft tenant or catalog before ordering.

This SKU does not include a trial, a standalone app, or a user license, because the catalog lists it as an add-on capacity SKU only. It also does not confirm Power Apps, Power Automate, Dynamics 365, Microsoft 365, Copilot, Teams, implementation, data migration, or advisory services; those requirements should be checked separately before purchase.

The exact Dataverse database capacity increment is not stated in the provided catalog facts, so it should be confirmed in the customer’s Microsoft tenant, admin center, or current CSP catalog before purchase. This matters because Dataverse database, file, and log capacity are separate capacity types and buyers should not assume one add-on covers all storage needs.

Yes, users may still need separate user licenses, because this SKU adds Dataverse database capacity and does not grant user access rights by itself. Confirm the required Power Apps, Power Automate, Dynamics 365, Microsoft 365, or other licenses for the actual app and user scenario before ordering the capacity add-on.

The add-on is tied to the Education pricing segment rather than to a specific student-only or faculty-only user license, because it is a tenant capacity SKU. The institution should confirm Education eligibility, tenant enrollment, and the user licenses assigned to students, faculty, or staff separately.

This SKU is not a Microsoft Teams license, because it is listed as a Dataverse database capacity add-on. If the use case involves Dataverse for Teams, confirm whether the environment needs to be upgraded or whether separate Power Platform licensing is required, since Dataverse for Teams and full Dataverse capacity rules can differ.

No, this add-on should not be treated as a Copilot license, because the catalog facts only identify Dataverse database capacity. Copilot, Copilot Studio, AI capacity, and any related user licensing or message capacity should be confirmed and purchased separately if needed.

No, you should not assume it increases file or log capacity, because this SKU is specifically identified as Dataverse Database Capacity. Dataverse database, file, and log storage are commonly managed as separate capacity categories, so confirm whether your tenant needs additional file capacity or log capacity before purchase.

It may help if the overage is specifically Dataverse database capacity, because this SKU is a database capacity add-on. It will not address a file-capacity or log-capacity shortage, so the administrator should review the Power Platform admin center capacity report before selecting the add-on.

No, the add-on does not change security or compliance controls by itself, because it adds storage capacity rather than granting new security features. Dataverse security roles, environment settings, data loss prevention policies, auditing, retention, and compliance configuration remain dependent on the tenant, environment, and underlying licensed services.

No, this add-on does not by itself determine data residency, because it is a capacity SKU added to an existing Microsoft tenant and environment configuration. Data location and residency should be verified based on the tenant region, Power Platform environment region, Microsoft cloud used, and any applicable institutional compliance requirements.

After purchase, an administrator should verify the added capacity in the Microsoft Power Platform admin center, because Dataverse capacity is managed at the tenant or environment capacity level rather than installed like desktop software. Before ordering, confirm the correct tenant, Education segment, SKU, commitment term, billing cadence, and capacity increment.

No, migration services are not included in the catalog facts for this SKU, because it is a capacity add-on rather than a services engagement. If the institution needs app design, environment setup, data import, integration, or advisory work, those services should be scoped separately with IT Partner.

A CSP relationship or subscription management transfer is typically designed not to move tenant data or interrupt the Microsoft cloud service, because the customer tenant and Dataverse environments remain in Microsoft’s cloud. The exact transfer path, timing, and subscription handling should be reviewed with IT Partner so the same SKU, Education segment, term, and tenant are preserved where possible.

For the same Microsoft SKU, segment, term, and billing option, the Microsoft CSP catalog basis should be comparable, because the product is a standard Microsoft catalog add-on. Final invoicing can still depend on currency, taxes, proration, partner services, and order timing, so confirm current pricing at order submission.

The Education catalog lists monthly commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly, because those are the current purchase options in the source catalog. Annual paid monthly is still an annual commitment, while monthly commitment provides the most flexibility; confirm current availability before ordering.

You can generally add more capacity during a term, because capacity add-ons are commonly expandable when more storage is needed. Reductions and cancellations are more restricted, especially on annual commitments, and Microsoft CSP new commerce rules commonly allow only a short cancellation or reduction window after purchase or renewal; confirm the exact rules with IT Partner before ordering.

At renewal, the add-on normally continues according to the selected commitment and billing option unless it is changed or canceled under the applicable CSP rules, because it is a subscription-based add-on. Review capacity usage, required quantity, Education eligibility, and whether monthly or annual commitment is still appropriate before the renewal date.

No, the Education SKU should be used only for an eligible Education tenant, because Microsoft segments such as Education, Government, Charity, and Commercial have different eligibility and catalog handling. Government tenants should confirm GCC or GCC High availability and residency requirements separately, nonprofits should confirm Charity eligibility or grant context separately, and standard business customers should use the Commercial segment rather than Education pricing.