Built-in security Exchange on-premises mailboxes add-on — Pricing, Plans & Licensing

Built-in security Exchange on-premises mailboxes add-on is a Commercial CSP add-on offer, because the source listing identifies it as an add-on SKU for Exchange on-premises mailboxes rather than a standalone Microsoft 365 or Exchange Online mailbox plan. Buyers should confirm the exact Microsoft entitlement mapped to the SKU before purchase, because the listing does not publish detailed service-feature entitlements.

No, Built-in security Exchange on-premises mailboxes add-on should not be treated as a standalone hosted mailbox service, because the listing positions it as an add-on for Exchange on-premises mailboxes. It does not confirm Exchange Online mailbox hosting, Exchange Server licensing, Windows Server licensing, or on-premises infrastructure rights.

The Commercial SKU includes the CSP offer listing for Built-in security Exchange on-premises mailboxes add-on and the ability to buy it under available monthly or annual commitment options, because those are the entitlements shown in the source pack. The source pack does not provide a detailed feature matrix, so IT Partner should verify the exact Microsoft service entitlement in the tenant before checkout.

Built-in security Exchange on-premises mailboxes add-on does not include a trial, confirmed Exchange Online mailbox hosting, Exchange Server licensing, Windows Server licensing, Microsoft 365 Apps, Teams, SharePoint, OneDrive, or migration services, because none of those entitlements are listed for this SKU. Any deployment labor or migration assistance must be separately scoped if needed.

No, there is no trial listed for Built-in security Exchange on-premises mailboxes add-on, because the source pack marks the offer as non-trial. A Commercial buyer should use the available paid commitment options and confirm prerequisites before ordering.

The unit of measure and assignment model must be confirmed before purchase, because the source pack does not state whether licensing is per mailbox, per user, or another coverage model. This is especially important for Exchange on-premises environments where shared, resource, service, and inactive mailboxes may have different licensing treatment depending on Microsoft rules and actual usage.

Do not assume coverage rules for shared, resource, service, or inactive mailboxes, because the source pack does not define mailbox assignment or exemption rules for this SKU. IT Partner should validate the Microsoft licensing treatment against the customer’s actual Exchange configuration before purchase.

Commercial buyers can choose monthly commitment with monthly billing, annual commitment paid upfront, or annual commitment paid monthly, because those are the purchase structures listed for this offer. Monthly commitment provides the most flexibility, while annual commitment options are designed for customers willing to commit for a longer term.

Seat reductions and cancellations are governed by Microsoft CSP subscription-term rules, because this is a CSP subscription offer. In Microsoft’s modern CSP commerce model, increases are generally easier than reductions during a term, so buyers should confirm the current cancellation window, renewal date, and seat-change rules with IT Partner before ordering.

Yes, additional quantities are generally added through the CSP subscription when more coverage is needed, because CSP subscriptions support quantity management. The exact assignment model and whether every mailbox type must be covered should be confirmed first, because the source pack does not define mailbox coverage rules.

The exact meaning of “built-in security” must be verified for this SKU, because the source pack does not list specific security capabilities, policies, threat-protection features, or compliance features. A buyer should not assume inclusion of any named Microsoft security service unless IT Partner confirms the mapped Microsoft entitlement in the tenant.

Do not assume Microsoft Purview compliance, eDiscovery, retention, or audit capabilities are included, because the source pack does not list those entitlements for Built-in security Exchange on-premises mailboxes add-on. If compliance coverage is the purchase driver, IT Partner should confirm the exact Microsoft entitlement and any required base licenses before the order is placed.

No Teams entitlement is confirmed for this SKU, because the source pack lists this as an Exchange on-premises mailboxes add-on and does not include Teams as an included service. If users need Teams, the organization should license Teams through an appropriate Microsoft 365, Office 365, or Teams offer as applicable.

Do not treat Built-in security Exchange on-premises mailboxes add-on as a Microsoft 365 Copilot qualifying base license, because the source pack does not identify it as a Copilot prerequisite or Microsoft 365 productivity suite. Copilot eligibility should be checked against Microsoft’s current qualifying-license rules for the customer’s tenant before purchase.

Prerequisites should be confirmed before purchase, because the source pack does not state the required Exchange Server version, mailbox configuration, hybrid status, identity setup, or base licensing. IT Partner should validate the customer’s Exchange on-premises environment and the Microsoft entitlement mapped to this SKU before licenses are ordered.

Hybrid Exchange support should be confirmed before purchase, because the source pack does not say whether the SKU is intended for hybrid environments or only specific on-premises mailbox scenarios. A buyer with both Exchange Online and Exchange on-premises mailboxes should verify coverage rules with IT Partner before relying on this add-on.

No, this SKU should not be described as a migration service or a confirmed migration-readiness product, because the source pack does not include migration entitlements or deployment labor. If the goal is to move mailboxes online, IT Partner should scope migration services and the correct Exchange Online or Microsoft 365 licensing separately.

A CSP partner transfer generally affects billing and administration rather than mailbox data, because the Microsoft tenant and services remain in place when the partner relationship is changed correctly. IT Partner should review the current subscription term, renewal timing, and transfer method to avoid administrative disruption.

Buying through IT Partner does not change the underlying Microsoft SKU or tenant entitlement, because the offer remains the same Microsoft CSP product when ordered correctly. The final quote, billing terms, taxes, and any partner-provided services should still be reviewed before purchase.

This page is for Commercial business tenants, because the source pack identifies Commercial availability and the revised content limits this page to Commercial buyers. Government customers should validate the appropriate Government cloud offer and residency requirements, nonprofits should check charity eligibility and grant context, and Education customers should use the correct student or faculty licensing path rather than assuming this Commercial SKU is the right fit.