Dataverse File Capacity add-on for Government — Pricing, Plans & What's Included

The Dataverse File Capacity add-on for Government adds Dataverse file capacity under Governmental Community Cloud pricing, because the source SKU is identified as a Government segment Dataverse File Capacity add-on. The exact capacity increment per add-on unit is not defined in the source pack, so it should be confirmed with IT Partner before checkout.

This add-on does not include Dataverse database capacity, Dataverse log capacity, Power Apps, Power Automate, Dynamics 365, Teams, Copilot, SharePoint, OneDrive, or Azure Storage, because the source pack identifies it only as a Dataverse file capacity add-on. It also does not grant user access rights or app-use rights; those must come from the customer’s eligible base licenses.

You should buy Dataverse File Capacity only when the shortage is specifically Dataverse file capacity, because Dataverse capacity is separated into different storage types such as database, file, and log. IT Partner should review the customer’s current Dataverse capacity usage in the appropriate Microsoft admin or licensing portal before ordering to avoid buying the wrong capacity type.

No, it should be treated as an add-on rather than a standalone user or app license, because the source pack identifies the offer as an add-on. Any required base service, tenant eligibility, environment, or user-license prerequisites should be confirmed before purchase because the source pack does not list them.

No, this add-on does not license additional users for Power Apps, Dynamics 365, or other workloads, because it is only for Dataverse file capacity. If more people need to access apps or data, the organization must separately confirm and purchase the correct user or app licenses.

The add-on is not a Teams license, because it is a Dataverse file capacity SKU for Government rather than a Teams service plan. If the customer’s Teams-related solution uses Dataverse or Dataverse for Teams, IT Partner should validate the actual capacity model and licensing path before ordering this SKU.

No, the Dataverse File Capacity add-on for Government does not include Copilot or AI feature rights, because the source pack only identifies additional Dataverse file capacity. Copilot availability, eligibility, data boundary, and licensing requirements must be validated separately for the customer’s specific Government cloud.

Do not assume GCC High eligibility from this SKU alone, because the source pack states Governmental Community Cloud Pricing but does not provide separate GCC High detail. IT Partner should confirm whether the SKU is valid for the customer’s specific government cloud tenant before purchase.

No capacity add-on should be assumed to change data residency by itself, because it adds capacity within the customer’s existing Microsoft cloud context rather than creating a separate storage platform. The customer should confirm the applicable Government cloud environment, regional data boundary, and Dataverse residency commitments for its tenant before ordering.

No, buying this add-on does not by itself add new security or compliance controls, because it is a capacity purchase rather than a security product. The customer’s compliance posture depends on the underlying Government cloud service, tenant configuration, identity controls, data governance, and workload design.

No, this add-on is not a replacement for SharePoint, OneDrive, or Azure Storage capacity, because it is specifically for Dataverse file capacity. If files are stored outside Dataverse, IT Partner should confirm the correct Microsoft storage service and licensing model before purchase.

Start by confirming that the tenant is eligible for the Government SKU and that the capacity shortage is Dataverse file capacity, because the add-on should match both the cloud segment and the capacity type. IT Partner can then help select the correct commitment and billing option and confirm the capacity increment before checkout.

No, this add-on does not perform migration, cleanup, archiving, or environment redesign, because it is a licensing capacity add-on. If the organization needs to reduce consumption or move data, those activities should be planned separately from the license purchase.

Government purchasing supports a monthly commitment with monthly billing, or an annual commitment paid either upfront or monthly, because those term and billing combinations are listed in the source pack. Annual upfront is the lowest listed rate structure in the source pack, annual paid monthly runs higher, and monthly commitment provides the most flexibility.

Usually, additional add-on quantity can be purchased when more capacity is needed, because capacity add-ons are commonly expanded as usage grows. The exact availability, effective date, and co-terming behavior should be confirmed with IT Partner for the selected Government CSP subscription.

Reduction and cancellation rights depend on the selected commitment, because monthly commitments are generally more flexible while annual commitments are typically locked except during Microsoft’s applicable cancellation window or renewal events. IT Partner should confirm the current CSP rules before purchase, especially if capacity needs may decline.

At renewal, the customer should reassess Dataverse file-capacity usage and the commitment option, because renewal is the best time to right-size quantity and term. IT Partner can help confirm whether the organization should keep, increase, reduce, or replace the add-on based on current Microsoft portal usage data.

A CSP transfer to IT Partner is typically a billing and partner-management change rather than a Dataverse data migration, so the Microsoft tenant and Dataverse environments should remain in place. IT Partner should still validate subscription eligibility and timing so the transfer does not interrupt billing continuity or renewal management.

Transferring CSP management should not change the underlying Microsoft product, because the service remains the Dataverse File Capacity add-on for the selected Government SKU. IT Partner can quote against the current Microsoft-published CSP pricing for the chosen term and billing option, with final commercial terms confirmed before checkout.

No, a Government customer should not assume it can use Charity, Education, or Commercial segment offers, because Microsoft segment pricing is tied to eligibility and purchasing context. Nonprofit grant eligibility, student-versus-faculty education licensing, and standard commercial business licensing are separate segment rules and should be validated before using any non-Government SKU.