Dataverse Database Capacity add-on Tier 2 (Min 1000GB) — Pricing, Plans & What's Included

Dataverse Database Capacity add-on Tier 2 (Min 1000GB) includes additional Dataverse database storage capacity for a Commercial tenant, because it is a capacity add-on SKU rather than an application license. The product title identifies Tier 2 as having a 1000 GB minimum purchase, so it is intended for larger Dataverse database storage requirements.

Dataverse Database Capacity add-on Tier 2 does not include Power Apps, Power Automate, Dynamics 365, Copilot, or user access rights, because it only adds Dataverse database storage capacity. It also does not add Dataverse file capacity or Dataverse log capacity, which are separate capacity types.

No, Dataverse Database Capacity add-on Tier 2 is not a standalone license, because it does not create app access or user entitlements by itself. The customer must already have the appropriate Microsoft services, environments, and user licenses that use Dataverse; confirm the exact prerequisites in the tenant before purchase.

A Commercial business should consider Dataverse Database Capacity add-on Tier 2 when it specifically needs a large amount of additional Dataverse database storage, because this SKU is identified as having a 1000 GB minimum purchase. It is not the right choice for a small incremental storage need below the Tier 2 minimum.

Dataverse Database Capacity add-on Tier 2 is for Dataverse database capacity only, because Microsoft separates Dataverse database, file, and log storage into different capacity categories. If the storage pressure is from attachments, files, audit logs, or other non-database usage, confirm whether a file or log capacity SKU is needed instead.

Dataverse database capacity is generally available to the tenant’s Dataverse environments, because capacity add-ons increase the organization’s available storage pool rather than granting a specific user license. Administrators should review capacity usage in the Power Platform admin center and confirm how Microsoft enforces the Tier 2 minimum and ordering quantities at checkout.

Dataverse Database Capacity add-on Tier 2 is available for Commercial customers with monthly commitment paid monthly, or annual commitment paid either upfront annually or monthly, because those options are present in the Commercial catalog for this SKU. Current availability and checkout behavior should be verified before ordering.

Yes, a Commercial trial SKU is present for Dataverse Database Capacity add-on Tier 2, because the catalog includes a trial entry for this product. Do not treat the trial as production-ready until IT Partner confirms the trial duration, limits, conversion path, and any tenant-specific restrictions.

No, this add-on does not give users rights to Power Apps, Power Automate, or Dynamics 365, because it only provides additional Dataverse database capacity. Users still need the appropriate base licenses for the apps and services that create, read, or manage Dataverse data.

Yes, Dataverse Database Capacity add-on Tier 2 can support Dataverse database storage used by Power Platform and Dynamics 365 environments, because those services commonly store business data in Dataverse. It still does not replace the underlying app, environment, or user licensing required for those workloads.

Not necessarily, because Dataverse for Teams has its own licensing and capacity behavior separate from full Dataverse environments. If the storage need is tied to Microsoft Teams apps or Dataverse for Teams, confirm with IT Partner whether this Commercial Dataverse database capacity add-on applies to that scenario before purchase.

No, this add-on is not a Copilot license, because it only adds Dataverse database storage capacity. A Copilot deployment may increase Dataverse usage depending on the apps and data involved, but Copilot licensing and prerequisites must be validated separately.

No, buying Dataverse Database Capacity add-on Tier 2 does not change Dataverse security permissions, because storage capacity and access control are separate. User access continues to be governed by the tenant’s Microsoft Entra identities, Dataverse security roles, environment settings, and applicable app licenses.

No, this add-on does not change compliance, audit, retention, DLP, or data protection settings, because it is only a storage capacity entitlement. Compliance posture depends on the customer’s Microsoft tenant configuration, Power Platform environment settings, and applicable Microsoft cloud commitments.

No, this specific catalog entry is for the Commercial segment, because the source catalog lists Commercial availability only. Government customers should use the appropriate government cloud catalog and confirm GCC, GCC High, or DoD availability, residency, and compliance requirements separately.

No, Dataverse Database Capacity add-on Tier 2 does not by itself determine data residency, because it is a capacity add-on rather than a region-selection product. Data location depends on the tenant, Power Platform environment region, cloud segment, and Microsoft’s applicable data residency commitments.

This SKU is listed for the Commercial segment, because the source catalog does not show Charity or Education availability for this product. Nonprofit and education customers should confirm eligibility, grant applicability, faculty versus student licensing rules, and any discounted segment-specific alternatives with IT Partner before buying a Commercial SKU.

After purchase, administrators should confirm the add-on appears in the Microsoft tenant and then review Dataverse capacity in the Power Platform admin center, because the practical value is increasing available database storage for existing environments. They should also identify which environments are driving database growth and confirm the need is database capacity rather than file or log capacity.

No, Dataverse Database Capacity add-on Tier 2 does not migrate, compress, archive, or clean up data, because it is a licensing and capacity entitlement only. Any data migration, storage optimization, table cleanup, retention review, or environment redesign is a separate technical activity.

Yes, changing CSP management to IT Partner should not require Dataverse downtime, because the customer’s Dataverse data remains in the same Microsoft tenant and is not migrated as part of a reseller or subscription management change. Coordinate timing carefully so the existing capacity does not lapse before the replacement or transferred subscription is active.

No, the Microsoft cloud entitlement for the same SKU and term should remain the same, because IT Partner is the CSP billing and support channel rather than a different Dataverse service. The final quote, commitment option, availability, and checkout behavior should still be verified before ordering.

Renewal, cancellation, and reduction rules depend on the selected CSP commitment and Microsoft commerce policies, because monthly and annual commitments have different change windows and billing behavior. Before purchase, confirm whether the subscription auto-renews, when reductions are allowed, and whether the tenant must continue meeting the Tier 2 1000 GB minimum.