Exchange Online Kiosk for Government — Pricing, Plans & What's Included

Exchange Online Kiosk for Government is a low-cost standalone Exchange mailbox for eligible government users, because it provides basic email, calendar, and contacts without buying a full Microsoft 365 suite. It is best suited for frontline, shift, kiosk, shared-workstation, and occasional-access users who need a government-cloud mailbox rather than a knowledge-worker plan.

Exchange Online Kiosk for Government includes a cloud Exchange mailbox for one licensed user, because the plan is sold per user for basic mailbox access. It supports core email, calendar, and contacts administration through Microsoft cloud admin experiences, but it should be validated against current Government cloud service limits if mailbox size, archive, protocol access, or compliance features are important.

Exchange Online Kiosk for Government does not include the Microsoft 365 Apps suite or an Outlook desktop app license, because it is a standalone Exchange mailbox plan rather than a full Microsoft 365 bundle. It also does not include Teams, SharePoint, OneDrive, or broader suite services unless those are licensed separately through another eligible plan.

Usually no, because Exchange Online Kiosk is designed for basic, low-touch mailbox scenarios rather than full-featured knowledge-worker email. If a user needs richer mailbox capabilities, desktop Outlook rights, larger mailbox or archive requirements, or broader Microsoft 365 services, IT Partner should compare this plan with higher Exchange Online or Microsoft 365 Government plans before purchase.

No, a user subscription should be assigned to the individual who needs their own mailbox, because Microsoft cloud user licensing is generally per named user. A shared workstation does not mean a shared license; each person who signs in and uses their own mailbox needs appropriate licensing.

No, Exchange Online Kiosk for Government does not include Teams, because it is a standalone Exchange email plan. If the user needs Teams chat, meetings, calling, or collaboration, the organization should license an eligible Microsoft Teams or Microsoft 365 Government plan separately and confirm tenant compatibility.

No, Exchange Online Kiosk for Government does not include Microsoft 365 Copilot, because it is only a basic Exchange mailbox plan. Copilot availability depends on the customer’s government cloud, eligible base licenses, and Microsoft’s current Copilot prerequisites, so IT Partner should confirm eligibility before assuming Copilot can be added.

Some add-ons may require a qualifying base license and may not apply to every government cloud or kiosk plan, because Microsoft eligibility rules vary by workload, tenant type, and cloud environment. If archiving, eDiscovery, retention, encryption, or advanced security is required, confirm the exact add-on prerequisites with IT Partner before buying the kiosk plan.

Do not assume one Government SKU fits both GCC and GCC High, because Microsoft government cloud eligibility and SKU availability differ by tenant type. Before provisioning, IT Partner should confirm whether the customer tenant is GCC, GCC High, or another environment and whether this specific Government SKU is appropriate for that tenant.

Data residency depends on the Microsoft government cloud environment assigned to the tenant, because GCC and GCC High have different compliance and residency commitments. Buyers should confirm the tenant cloud and Microsoft’s current service documentation for residency requirements before treating this plan as meeting a specific regulatory mandate.

Not by itself in every case, because a mailbox license provides the Exchange service but does not automatically satisfy all agency, CJIS, ITAR, FedRAMP, retention, eDiscovery, or records-management requirements. Government buyers should map their compliance obligations to the tenant cloud, Exchange plan limits, and any required security or compliance add-ons before purchase.

Exchange Online Kiosk runs on Microsoft’s cloud email platform and can use tenant-level identity and mail-security controls available in the customer’s environment, because security is managed across Microsoft Entra ID, Exchange admin settings, and any licensed security services. Advanced protection features may require separate Microsoft Defender, Entra, or compliance licensing, so confirm the required controls before assigning kiosk mailboxes.

Yes, mailboxes can generally be migrated into Exchange Online in a government tenant when the tenant and migration path are properly configured, because the license provides a destination mailbox for the user. The right approach depends on the source system, identity setup, domain readiness, mailbox size, and coexistence needs, so plan migration with IT Partner before cutting over users.

You need an eligible Government tenant and a user licensing plan, because this SKU is intended for qualified government environments and is assigned per user. Before purchase, confirm tenant eligibility, domain and identity readiness, mailbox requirements, and whether users need only basic email or a higher Microsoft 365 Government plan.

No trial is listed for this CSP offer, because the available Government options are paid subscription terms. If a pilot is needed, buyers typically use a small paid deployment and validate mailbox behavior, admin settings, and user workflows before broader rollout.

Exchange Online Kiosk for Government is available as a monthly commitment with monthly billing or as an annual commitment paid either upfront or monthly, because the CSP offer supports multiple subscription paths. Annual upfront is generally the strongest per-seat posture, annual paid monthly spreads payments across the term, and monthly commitment offers the most flexibility.

You can typically add seats during an active subscription term, because CSP subscriptions are designed to support user growth. Reductions and cancellations are more restricted on annual commitments and are usually governed by Microsoft’s cancellation-window and renewal rules, so confirm the specific term rules before ordering.

At renewal, the subscription generally continues into the next term unless changes are made according to CSP renewal rules, because annual commitments are term-based. Buyers should review seat counts, billing frequency, and whether kiosk users still match the plan before renewal to avoid carrying unnecessary licenses.

Yes, a properly coordinated CSP partner transfer should not require mailbox downtime, because the mailboxes and data remain in the Microsoft tenant while the billing and support relationship changes. IT Partner should validate the tenant, subscription timing, and license continuity before the transfer so users keep access during the change.

Transferring the CSP relationship to IT Partner does not move the tenant or mailbox data, because the Microsoft tenant remains the same. For the same Microsoft SKU and term, the Microsoft-set CSP pricing basis should be consistent, but partner services, billing presentation, and quoted totals can differ, so confirm the final quote before authorizing the transfer.

Not unless they qualify for the applicable Government tenant and offer, because this SKU is intended for eligible Government customers rather than nonprofit grant programs, student or faculty education licensing, or standard commercial tenants. Nonprofit, education, and commercial buyers should use the licensing program and tenant type that matches their eligibility instead of assuming the Government SKU applies.