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

The Dataverse Log Capacity add-on for Government adds Dataverse log storage capacity for an eligible existing Government Dataverse environment, because it is a capacity add-on rather than a full service license. It is intended for Government customers whose Dataverse audit or log data is consuming log capacity. Confirm the precise capacity increment and how it is shown in the Microsoft admin or Power Platform admin experience before quoting.

The Dataverse Log Capacity add-on for Government does not include user licenses, app licenses, a new Dataverse environment, or a base Dataverse entitlement, because it only expands log capacity. It also does not add Dataverse database capacity or Dataverse file capacity, which are separate capacity types. Migration services, compliance assessments, and managed services are not part of the SKU.

Yes, the Dataverse Log Capacity add-on for Government requires an eligible base Dataverse entitlement, because it is not a standalone license. A Government buyer should validate the existing Power Platform, Dynamics 365, or other qualifying Dataverse entitlement before ordering. IT Partner should confirm eligibility against current Microsoft documentation and price list metadata.

You need Dataverse log capacity when the pressure is from Dataverse log or audit data, because Dataverse separates storage into database, file, and log capacity. If tables, records, or relational data are consuming storage, that is usually database capacity; if attachments or files are consuming storage, that is usually file capacity. Review capacity analytics in the Power Platform admin center before purchasing the add-on.

The exact capacity increment should be confirmed before quoting, because the source offer identifies the SKU as a Dataverse Log Capacity add-on but does not safely establish the increment in this context. Government buyers should verify the current Microsoft price list and admin-center behavior for the exact Government SKU. Do not assume the increment from a different segment, cloud, or older Microsoft offer.

Do not assume the same SKU is available in every government cloud, because Microsoft Government offer availability can differ across GCC, GCC High, and other sovereign or restricted environments. The buyer should confirm the target government cloud, tenant type, and CSP availability before ordering. Data residency and compliance boundaries are determined by the customer’s Microsoft government cloud and tenant configuration, not by the capacity add-on alone.

No, the Dataverse Log Capacity add-on for Government adds log storage capacity, because it is a capacity SKU rather than a security or compliance package. It does not create new compliance certifications, data-loss-prevention policies, encryption controls, audit configurations, or retention policies by itself. Government compliance requirements should be reviewed separately against the customer’s Microsoft cloud environment and workload configuration.

No, buying the Dataverse Log Capacity add-on for Government does not automatically configure auditing or retention, because it only increases available log capacity. Audit settings, retention behavior, and regulatory retention requirements must be managed through the relevant Dataverse, Power Platform, and compliance configurations. More log capacity can help support larger log volume, but it is not a substitute for governance design.

The Dataverse Log Capacity add-on for Government should not be purchased solely to unlock Dataverse for Teams, because Dataverse for Teams and full Dataverse licensing have different entitlement models and limits. The add-on requires an eligible base Dataverse entitlement and is intended to expand log capacity for eligible Dataverse use. Confirm whether the specific environment and underlying license qualify before ordering.

No, the Dataverse Log Capacity add-on for Government does not include Copilot, Power Apps, Power Automate, AI Builder, or user/app rights, because it only adds Dataverse log capacity. If a Copilot, app, or automation workload is creating more log volume, the add-on may help with log capacity only after the required base licenses are already in place. Licensing for the workload itself must be reviewed separately.

Start by confirming the customer has an eligible Government tenant, eligible base Dataverse entitlement, and the correct Government SKU, because the add-on depends on those prerequisites. After purchase, verify where the added capacity appears in the Microsoft admin or Power Platform admin experience. Also confirm whether the add-on is managed at tenant level, environment level, or another assignment model before communicating deployment steps.

No, the Dataverse Log Capacity add-on for Government does not perform a tenant or cloud migration, because it is only a storage-capacity add-on. Moving from Commercial to GCC or GCC High is a separate planning and migration effort involving identity, data, workloads, compliance, and Microsoft cloud eligibility. Do not buy this add-on as a substitute for a government cloud migration project.

A CSP provider change is typically designed to be licensing and billing administration rather than a Dataverse data move, because the Microsoft tenant and environment remain the customer’s tenant. However, the exact transfer or replacement path depends on the current subscription, term, and Microsoft commerce rules. IT Partner should confirm the transfer approach before any change so the service remains continuous.

For the same Government SKU, term, and billing option, Microsoft CSP pricing is based on the current price list, because the underlying offer is standardized in the channel. The final customer invoice can still vary due to taxes, partner services, support terms, timing, or co-terming choices. IT Partner should quote the current Government offer at the time of purchase or transfer.

The Government offer is available with monthly commitment paid monthly, annual commitment paid annually, and annual commitment paid monthly options, because the source offer lists those purchasing motions. Annual upfront is the best relative rate among the listed options, while annual paid monthly may help with cash flow. The right choice depends on budget rules, renewal timing, and expected capacity growth.

Increases are commonly easier than reductions, because capacity add-ons are subscription-based and Microsoft commerce rules tie cancellation and reduction rights to the selected term and timing. Annual commitments generally provide less flexibility to reduce after the allowed cancellation window than monthly commitments. Confirm the current CSP cancellation, reduction, and renewal rules before ordering or changing quantity.

Often, co-terming may be possible or commercially useful, because Government buyers frequently want renewals aligned for procurement and budget review. Co-terming availability depends on the current subscription structure, term, billing option, and Microsoft CSP rules. IT Partner should review renewal dates before ordering so the add-on does not create avoidable renewal fragmentation.

No, the source offer does not include a trial for the Dataverse Log Capacity add-on for Government, because it is listed only as a paid capacity add-on. Buyers should validate the capacity need in the Power Platform admin center before purchase. If there is uncertainty, confirm the required capacity type and increment with IT Partner before committing.

A nonprofit should not assume it can buy the Government SKU, because Government and Charity are separate purchasing segments with different eligibility and offer rules. Nonprofit grants or discounted licensing may not apply to this Government offer, and the customer should use the segment for which it is eligible. IT Partner should confirm whether the organization should buy through Charity, Government, or another approved purchasing motion.

An Education or Commercial customer should not buy the Government SKU unless it is eligible for the Government purchasing motion, because Microsoft segments have separate offers and eligibility requirements. Education buyers should distinguish student, faculty, and institutional licensing needs under Education offers, while standard businesses normally use Commercial offers. The correct Dataverse log capacity SKU should match the customer’s eligible segment, tenant, and cloud environment.