Dynamics 365 Business Central Database Capacity — Pricing, Plans & What's Included

Dynamics 365 Business Central Database Capacity is an add-on for buying additional Business Central database capacity, because it is a capacity catalog line item rather than a Business Central user license. Commercial buyers use it when their Business Central tenant needs a separate database capacity purchase beyond what their current licensing and tenant configuration provide.

The Commercial catalog entries listed include the standard Dynamics 365 Business Central Database Capacity SKU, a Dynamics 365 Business Central Database Capacity 100GB SKU, and a Dynamics 365 Business Central Database Capacity Overage SKU. The exact capacity increment for the standard SKU and the mechanics of the overage SKU should be confirmed in the current Microsoft catalog before ordering, because the source pack does not define those operational details.

No, Dynamics 365 Business Central Database Capacity does not include Business Central user access, because it is a database capacity add-on and not a base application or user subscription. Users still need the appropriate Business Central licensing separately before this capacity add-on is useful.

In practice, you should confirm an active and eligible Business Central base licensing position before buying this add-on, because database capacity is meant to support a Business Central environment rather than grant access by itself. IT Partner should review your tenant, included capacity, and prerequisites before recommending a quantity.

No trial SKU is listed for Dynamics 365 Business Central Database Capacity in the Commercial source pack. Buyers should plan this as a paid capacity purchase and validate the required quantity before placing the order.

Yes, the Commercial source pack lists monthly commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly options. The available choices can vary by SKU, so the current configurator should be used to compare commitment and payment options before purchase.

No three-year term is listed in the Commercial source pack for Dynamics 365 Business Central Database Capacity. The listed Commercial terms are monthly and annual only, so any longer-term requirement should be confirmed separately with IT Partner before quoting.

You should choose based on the capacity increment, commitment structure, and Microsoft’s current overage mechanics, because the source pack lists multiple Commercial catalog lines but does not define all usage rules. IT Partner should confirm whether the overage SKU is customer-purchasable in advance or applied through Microsoft usage or overage handling for your tenant.

Dynamics 365 Business Central Database Capacity specifically references database capacity, so it should not be assumed to add file storage, log storage, more environments, or performance tuning. If your issue is file storage, log growth, environment limits, data cleanup, or performance, those requirements should be validated separately before buying this SKU.

Not by itself, because Dynamics 365 Business Central Database Capacity is a licensing add-on for database capacity and does not include migration, archiving, implementation, data cleanup, or performance-tuning services. Those services should be scoped separately if your project requires them.

No, Dynamics 365 Business Central Database Capacity does not include Teams, Copilot, or productivity app entitlements, because it is a Business Central database capacity add-on. Any Teams integration, Copilot capability, or Microsoft 365 licensing requirement should be evaluated separately from this capacity purchase.

Adding Dynamics 365 Business Central Database Capacity does not by itself change your identity, access, security configuration, or compliance controls, because it is a capacity entitlement rather than a security product. Your Business Central tenant settings, Microsoft cloud compliance commitments, role permissions, audit requirements, and data governance practices should still be reviewed separately.

No Government segment availability is listed in the source pack for this product; the listed segments are Commercial, Charity, and Education. If you require GCC, GCC High, DoD, or specific Government cloud residency assurances, you should not assume the Commercial SKU satisfies those requirements and should confirm the correct Government-eligible licensing path with IT Partner.

No specific data residency guarantee is stated in the source pack for Dynamics 365 Business Central Database Capacity. Data residency should be evaluated under the customer’s Business Central tenant, Microsoft cloud region, and contractual commitments, because a capacity add-on alone does not define residency.

Start by reviewing your current Business Central licensing, tenant capacity usage, included capacity, and expected data growth, because the correct add-on quantity depends on the existing environment. IT Partner can then help compare the listed Commercial capacity options and select the appropriate commitment and payment structure.

A CSP provider change normally does not require reinstalling Business Central or moving data, because the Microsoft tenant and service remain in place while the billing relationship changes. IT Partner should still coordinate the transfer timing and subscription details to avoid renewal or provisioning issues.

Moving the CSP relationship to IT Partner should not change the underlying Microsoft Business Central service, because the subscription remains a Microsoft cloud service tied to the tenant. The Microsoft catalog price for the same SKU and term should be comparable, but taxes, billing presentation, promotions, partner terms, and timing should be confirmed before transfer.

Cancellation and reduction rights depend on the commitment term and Microsoft CSP rules, because monthly and annual commitments are handled differently. Annual commitments usually provide less reduction flexibility than monthly commitments, so confirm the cancellation window, renewal date, and quantity-change rules before ordering.

Capacity increases are typically easier than reductions in cloud subscription licensing, because adding quantity supports growth while reductions are usually tied to cancellation or renewal rules. The exact process depends on the SKU, term, and tenant eligibility, so IT Partner should confirm the current Microsoft CSP rules before you rely on midterm changes.

Nonprofit and education organizations should not automatically buy the Commercial SKU, because the source pack lists Charity and Education as separate segments in addition to Commercial. Nonprofit eligibility, grant applicability, and student-versus-faculty education licensing context should be reviewed separately so the organization uses the correct segment and catalog offer.