Built-in security Exchange on-premises mailboxes add-on — Exchange Online Protection Government Pricing & What's Included

The Built-in security Exchange on-premises mailboxes add-on is the Government-segment Exchange Online Protection offer for organizations that keep mailboxes on on-premises Exchange. It adds Microsoft’s cloud-based email protection layer in front of those on-premises mailboxes, because mail can be routed through Exchange Online Protection before it reaches the customer’s Exchange environment.

The Government Exchange Online Protection add-on includes the Exchange Online Protection Government SKU for eligible Government customers and is intended for spam, malware, and policy-based email filtering scenarios for Exchange on-premises mailboxes. It is an add-on protection service, because the source catalog positions it for Exchange on-premises mailboxes rather than as a hosted mailbox plan.

This add-on does not include hosted Exchange Online mailboxes, Microsoft 365 desktop apps, Teams, Copilot, endpoint management, or identity governance services. It also does not include Microsoft Defender for Office 365 advanced features such as Safe Links and Safe Attachments, because those are separate security capabilities outside the listed scope of this add-on.

No, this add-on does not replace Exchange Server or host mailboxes in Exchange Online, because it is a protection service for Exchange on-premises mailboxes. If the requirement is hosted mailboxes, the buyer should evaluate an Exchange Online or Microsoft 365 plan instead of this add-on.

Do not assume this SKU is valid for every Microsoft government cloud, because the source identifies Government availability but does not specify the exact tenant cloud such as GCC, GCC High, or DoD. Government buyers should confirm tenant eligibility and cloud availability with IT Partner before ordering so provisioning matches the customer’s Microsoft environment.

No specific residency, compliance, or clearance guarantee is stated in the source for this SKU, so it should not be treated as proof of compliance by itself. Government agencies should perform customer-specific due diligence and confirm the applicable Microsoft government cloud, service terms, and compliance documentation before relying on it for a regulated workload.

No, Microsoft Defender for Office 365 advanced capabilities such as Safe Links and Safe Attachments are not included in the listed scope of this add-on. This offer is Exchange Online Protection for on-premises mailbox protection, because the source describes it as the Government Exchange Online Protection SKU rather than a Defender for Office 365 plan.

No, this add-on does not include Teams, Microsoft 365 Copilot, or Microsoft 365 desktop apps, because it is not a productivity suite subscription. It is only for the Exchange Online Protection use case for eligible Government customers with Exchange on-premises mailboxes.

A Government customer should confirm the exact Microsoft government tenant type, the required licensing unit, and the Exchange on-premises mail-flow design before buying. This is important because the source does not specify the assignment model or mailbox coverage rules, and mail protection depends on correct routing between Microsoft’s protection service and the customer’s on-premises Exchange environment.

Mail is typically routed through Exchange Online Protection before delivery to the on-premises Exchange environment, because the service is designed to filter mail before it reaches the organization. The exact MX record, connector, accepted-domain, and hybrid-routing configuration should be validated for the customer’s Exchange version and topology before deployment.

Yes, it may fit some hybrid or on-premises Exchange protection scenarios, because Exchange Online Protection can be used as a cloud filtering layer while mailboxes remain on-premises. The customer should still validate the exact hybrid topology, routing requirements, and Government tenant availability before ordering or changing production mail flow.

The exact licensing unit and assignment rules are not specified in the source, so the number of required licenses should be verified before purchase. Government buyers should confirm whether coverage is based on users, mailboxes, protected recipients, or another licensing metric, because under-licensing can create compliance and operational risk.

No trial SKU is listed for the Government offer in the source catalog. A buyer should plan a paid subscription and confirm the commitment model before ordering, because trial availability cannot be assumed for this SKU.

The Government offer is listed with monthly commitment billed monthly, annual commitment paid upfront, and annual commitment paid monthly. Annual upfront is the lowest listed unit-rate structure in the source, annual paid monthly costs more over the term, and monthly commitment provides the most flexibility.

Seat increases are generally easier than reductions in Microsoft CSP subscriptions, because reductions are often governed by the selected commitment term and cancellation window. For this specific add-on, the customer should confirm the current CSP seat-change rules and the licensing unit with IT Partner before ordering, especially for annual commitments.

Renewal and cancellation depend on the selected commitment model, because monthly commitment and annual commitment carry different flexibility. Government buyers should review renewal dates, cancellation windows, and reduction rules before purchase, since annual commitments typically limit mid-term reductions and should be sized carefully.

Yes, a CSP billing or support relationship change can usually be handled without moving mailboxes or changing mail flow, because the tenant and on-premises Exchange environment remain in place. IT Partner should coordinate the partner relationship, subscription timing, and administrative access so protection remains active during the transition.

The source catalog shows the Government Exchange Online Protection offer as unchanged, but the final invoice should still be confirmed with IT Partner because CSP quotes can include term, billing, tax, and partner-specific commercial details. The important licensing check is that the same Government SKU and commitment model are being ordered for the correct tenant.

The first steps are to verify Government tenant eligibility, confirm the required licensing unit, purchase the appropriate commitment option, and design the mail-flow configuration. Deployment should then validate domains, connectors, MX routing, quarantine and filtering settings, and any hybrid requirements before the service is relied on for production mail protection.

This specific offer is the Government-segment Exchange Online Protection SKU, so buyers outside the Government segment should not assume eligibility. Nonprofit, education, and commercial customers should use the appropriate segment offer for their tenant and eligibility status, because Government pricing and provisioning rules are tied to Government customer qualification and tenant availability.