Dynamics 365 Business Central Database Capacity for Nonprofits — Pricing & Add-On Options

Dynamics 365 Business Central Database Capacity for Nonprofits includes additional database capacity for an eligible nonprofit tenant that already uses Dynamics 365 Business Central, because it is an add-on capacity SKU rather than a full application license. Charity options include Database Capacity, Database Capacity 100GB, and Database Capacity Overage, with monthly and annual commitment structures available through CSP.

This product does not include Business Central user licenses, implementation services, migration work, Microsoft 365 storage, SharePoint storage, or OneDrive storage, because it only adds Business Central database capacity. If your nonprofit needs users, finance setup, reporting configuration, cleanup, or retention-policy design, those items must be licensed or purchased separately.

Yes, your nonprofit needs an eligible Dynamics 365 Business Central subscription before adding this capacity, because the SKU attaches to a Business Central tenant and is not a standalone ERP product. IT Partner should confirm the tenant eligibility and current Business Central admin-center capacity status before purchase.

Choose the capacity option based on measured Business Central database usage and expected growth, because the right SKU depends on whether you need planned extra capacity, a larger capacity block, or an overage-oriented option. The safest approach is to review Business Central admin-center storage usage, transaction growth, retention needs, and Microsoft’s current capacity enforcement rules before ordering.

No, the listed Charity options do not include a trial, because this is an add-on capacity purchase rather than an evaluation license. If your nonprofit is unsure how much capacity it needs, review current usage first rather than buying capacity speculatively.

Charity pricing is available with monthly commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly options, because Microsoft CSP supports different term and billing combinations for the listed nonprofit SKUs. Monthly commitment gives the most flexibility, annual upfront generally has the strongest listed rate posture, and annual paid monthly smooths cash flow while keeping an annual commitment.

Yes, capacity can generally be increased by purchasing additional eligible capacity SKUs, because the product is intended to add storage as Business Central data grows. Before increasing, confirm current usage in the Business Central admin center and verify the available Charity SKU and term options at checkout.

Reductions and cancellations depend on the selected commitment term and Microsoft CSP rules, because annual commitments are less flexible than monthly commitments. A nonprofit that expects uncertain data growth should consider the flexibility tradeoff before choosing an annual commitment.

At renewal, the capacity add-on should continue or renew according to the selected CSP term and renewal settings, because it is managed as a subscription add-on in the Microsoft commerce system. Your nonprofit should review capacity usage, renewal date, billing frequency, and whether the quantity is still appropriate before the renewal point.

Yes, the Charity SKU requires Microsoft nonprofit eligibility, because nonprofit pricing is restricted to organizations that qualify under Microsoft’s nonprofit program rules. IT Partner should confirm your nonprofit qualification and tenant eligibility before ordering.

Do not assume this add-on is grant-funded, because Microsoft nonprofit grants and discounts vary by product, program, country, and eligibility status. Treat this as a paid Charity capacity add-on unless IT Partner confirms a specific grant or program benefit applies to your tenant.

Do not assume the Charity commercial SKU applies to GCC or GCC High, because government cloud availability, data residency, and licensing channels can differ from standard nonprofit commercial-cloud licensing. If your nonprofit has government compliance requirements, confirm Business Central cloud availability, tenant type, residency, and eligible capacity SKUs with IT Partner before purchase.

Adding database capacity does not by itself change Business Central security roles, identity controls, or compliance configuration, because it expands storage capacity rather than altering access governance. Your nonprofit still needs to manage users, permissions, audit needs, retention policies, and compliance controls within Business Central and Microsoft Entra ID.

No, this add-on does not provide a backup service, archive project, or data cleanup engagement, because it is a licensing SKU for additional Business Central database capacity. If your nonprofit is adding capacity due to old data, attachments, or transaction growth, also review retention, cleanup, and reporting requirements separately.

Start by confirming the add-on is assigned to the correct Business Central tenant and then recheck capacity status in the Business Central admin center, because capacity management is tied to the tenant’s measured database usage. If the goal is to avoid overage or enforcement issues, document current usage, forecast growth, and keep the renewal and quantity plan updated.

Adding capacity normally should not require a Business Central data migration or planned user downtime, because it is a subscription capacity change for the existing tenant rather than a move to a new environment. IT Partner should still confirm timing, provisioning status, and any tenant-specific constraints before making the change.

Yes, a CSP transfer to IT Partner is typically a billing and partner-of-record relationship change, because the Business Central environment remains in the same Microsoft tenant. It should not require moving the database or reinstalling Business Central, but any separate tenant migration or licensing cleanup should be reviewed in advance.

The Microsoft list pricing for the same Charity SKU and commitment should be consistent through CSP, because the product and nonprofit licensing offer are defined by Microsoft. However, taxes, billing timing, promotions, partner services, and support packages can vary, so confirm the final checkout terms with IT Partner.

No, this add-on does not include Microsoft Teams, Microsoft 365 apps, Teams Phone, or collaboration storage, because it only expands Business Central database capacity. If your nonprofit needs Teams or Microsoft 365 services, those must be licensed separately under the appropriate nonprofit offers.

No, Business Central Database Capacity does not grant Copilot rights or add AI features by itself, because it is a storage-capacity add-on. Any Copilot or AI capability depends on the Business Central product features, user licensing, tenant settings, regional availability, and Microsoft’s current requirements at the time of use.

No, this SKU cannot replace Business Central user licenses, because it adds database capacity and does not grant users the right to access Business Central. Every person who needs to use Business Central must still have the appropriate Business Central license for their role.

Use the licensing segment that matches the eligible tenant and purchasing program, because Charity, Education, and Commercial offers are separate Microsoft pricing segments. Student-versus-faculty distinctions are not the main issue for this product because it is not a user license; if the organization is not approved for nonprofit pricing, use an eligible Education or Commercial option as applicable.