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

The Dataverse Log Capacity add-on for Nonprofits includes an add-on capacity subscription for Dataverse log capacity under Charity/nonprofit pricing, because the catalog identifies it as a Charity-priced Dataverse Log Capacity add-on. It is intended to help qualifying nonprofit organizations add log capacity to an existing Microsoft environment after prerequisite licensing is confirmed.

The Dataverse Log Capacity add-on does not include Power Apps, Power Automate, Dynamics 365, Copilot, Teams, or other user/app licenses, because it is a capacity add-on rather than a core service license. It also does not add Dataverse database capacity or Dataverse file capacity, so it should not be purchased to solve database or file storage shortages.

No, this should not be treated as a standalone license, because the Dataverse Log Capacity add-on is an add-on that depends on the customer having the required underlying Microsoft licensing and Dataverse-backed usage. Before ordering, confirm the base licenses, tenant, and Power Platform or Dynamics 365 environment where the added log capacity is expected to apply.

You need Dataverse log capacity only if the shortage is actually in Dataverse log storage, because Dataverse database capacity, file capacity, and log capacity are separate capacity categories. A nonprofit should check current Dataverse capacity consumption in the relevant Microsoft admin experience and confirm whether the growth is from audit, telemetry, system, or another log category before buying this add-on.

No, the source catalog does not list a trial for the Dataverse Log Capacity add-on for Nonprofits, because the available Charity options are paid subscription options. If a nonprofit is unsure whether log capacity is the issue, it should review capacity reporting with IT Partner before purchasing rather than relying on a trial.

For Charity customers, the catalog lists monthly commitment billed monthly, annual commitment billed annually, and annual commitment billed monthly options, because the nonprofit SKU is available across those term and billing combinations. The right choice usually depends on whether the nonprofit wants flexibility, annual budget alignment, or monthly cash-flow billing under an annual commitment.

No, nonprofit pricing is not the same thing as a grant entitlement, because Charity pricing requires Microsoft nonprofit eligibility but does not automatically mean the product is donated or covered by grant credits. A nonprofit should confirm its eligibility status, available nonprofit benefits, and whether this specific add-on is paid or grant-covered before ordering.

A nonprofit should confirm Microsoft nonprofit eligibility before relying on Charity pricing, because the Dataverse Log Capacity add-on for Nonprofits is offered as a Charity/nonprofit-priced SKU. Eligibility is separate from the technical need for log capacity, so both eligibility and licensing prerequisites should be verified before purchase.

No, the add-on does not give users application or service-use rights, because it adds Dataverse log capacity rather than app, workflow, or Dynamics 365 entitlements. Users still need the appropriate underlying Power Apps, Power Automate, Dynamics 365, or other Microsoft licenses for the workloads that generate or use Dataverse data.

No, Teams does not include this Dataverse Log Capacity add-on, because the add-on is a separate Dataverse capacity subscription. If the nonprofit is using Dataverse-backed apps connected to Teams or Dataverse for Teams, it should confirm the environment type, licensing model, and whether the capacity need is actually Dataverse log capacity before buying.

No, the Dataverse Log Capacity add-on does not include Copilot, Copilot Studio, or AI Builder capacity, because it is only a Dataverse log capacity add-on. If Copilot or AI Builder usage is part of the project, those licensing and capacity requirements should be assessed separately from Dataverse log storage.

No, buying the add-on does not by itself change security roles, data loss prevention policies, audit configuration, retention settings, or compliance obligations, because it is a capacity purchase rather than a governance configuration. The nonprofit should separately review Power Platform administration, audit settings, retention requirements, and access controls for the environments producing the logs.

No, the add-on should not be assumed to change data residency, because it adds Dataverse log capacity rather than moving the tenant or environment to another geography. Data residency depends on the Microsoft cloud, tenant, environment region, and service configuration, so nonprofits with residency requirements should confirm the applicable Microsoft documentation and admin settings before ordering.

Do not assume a Charity-priced add-on applies to GCC or GCC High, because Government cloud licensing, availability, and procurement rules can differ from nonprofit commercial-cloud licensing. If a nonprofit has government-related compliance needs, IT Partner should confirm whether the organization belongs in Commercial, GCC, GCC High, or another Microsoft cloud and whether the exact Dataverse Log Capacity SKU is available there.

Start by checking Dataverse capacity reporting and identifying whether the shortage is log capacity, because buying this add-on will not fix database, file, or user-license problems. Then confirm the required underlying licenses, nonprofit eligibility, the intended tenant and environments, and how the add-on will be applied in the Microsoft admin experience.

Adding a Dataverse Log Capacity add-on is normally a licensing and capacity change rather than a data migration, because it is intended to increase available log capacity for an existing Microsoft tenant or environment. However, the nonprofit should confirm provisioning behavior, timing, and how the capacity is reflected in the admin center before ordering, especially if it is already in an over-capacity state.

Yes, CSP management can typically be moved without a workload migration, because the Microsoft tenant and services remain in place while the reseller relationship or subscription management changes. The nonprofit should still coordinate the transfer, confirm the same SKU and term, and verify that Microsoft catalog pricing, taxes, promotions, and invoice terms are handled as expected.

Renewal and cancellation rules depend on the selected commitment term, because monthly and annual commitments have different flexibility under Microsoft CSP subscription policies. In general, increases are usually easier than reductions, while cancellations or reductions may be limited after the allowed cancellation window and may need to wait until renewal; confirm the exact rules with IT Partner before purchase.

This add-on should not be treated like a user seat license, because it is a Dataverse capacity add-on rather than a per-user entitlement. Before ordering, confirm in the Microsoft admin experience whether the capacity is tenant-level, environment-level, pooled, or otherwise applied for the nonprofit’s specific Dataverse setup.

If the organization is not approved for Microsoft nonprofit eligibility, it should not rely on the Charity-priced Dataverse Log Capacity add-on, because Charity pricing is tied to Microsoft nonprofit qualification. If eligibility changes later, the nonprofit should expect licensing and pricing to be reviewed and may need to move to another eligible segment or commercial option.

A nonprofit school should not choose the Charity SKU solely because it is nonprofit, because Microsoft Education licensing and Charity licensing are separate eligibility and purchasing paths. Student-versus-faculty licensing questions belong in the Education licensing review, while this Charity add-on is for organizations purchasing under nonprofit eligibility.

A standard business should use the Commercial licensing path rather than the Charity-priced Dataverse Log Capacity add-on, because nonprofit pricing is reserved for organizations that meet Microsoft nonprofit eligibility requirements. The technical need may still be Dataverse log capacity, but the eligible segment, SKU, and commercial terms should match the customer’s organization type.