Microsoft 365 F1 — Pricing, Plans & What's Included

Microsoft 365 F1 is a Commercial Microsoft 365 catalog offer for buyers selecting the F1 plan family. The catalog includes both Microsoft 365 F1 and Microsoft 365 F1 (no Teams), because Microsoft treats those as separate SKU choices. Before rollout, verify the current Microsoft service-plan list because the source catalog confirms the SKUs and terms but not every workload entitlement.

Microsoft 365 F1 can be purchased as a Teams-inclusive SKU, because the Commercial catalog lists “Microsoft 365 F1” separately from “Microsoft 365 F1 (no Teams).” If your organization needs the no Teams version, choose that distinct SKU rather than buying the Teams-inclusive SKU and simply disabling Teams administratively.

Microsoft 365 F1 and Microsoft 365 F1 (no Teams) are separate Commercial SKU choices, because the catalog lists them as distinct offers. The no Teams SKU should be selected when the purchasing intent is specifically to exclude Teams from the licensed package. Confirm the current Microsoft regional, contractual, and service-plan rules before standardizing on either version.

Do not assume the Defender Suite FLW or Purview Suite FLW capabilities are included in the base Microsoft 365 F1 SKU, because the Commercial catalog lists Microsoft Defender Suite Add-on FLW, Microsoft Purview Suite Add-on FLW, and Microsoft Defender + Purview Suite Add-on for FLW as separate add-on SKUs. Buy the add-on only after confirming its qualifying base-license requirements, capabilities, and limitations.

Yes, the Commercial catalog includes separate FLW add-on paths for Microsoft Defender Suite, Microsoft Purview Suite, and the combined Defender + Purview Suite. However, add-on eligibility and prerequisites are not confirmed in the source catalog, so verify Microsoft’s current requirements before attaching those add-ons to F1 users.

No Copilot entitlement is confirmed for Microsoft 365 F1 in the provided Commercial catalog data, because Copilot is not listed as part of the F1 SKU or its related FLW add-ons. Treat Microsoft 365 Copilot as a separate product decision and confirm current Copilot prerequisites with IT Partner before quoting or assigning it.

The catalog confirms Microsoft 365 F1 and separate Defender/Purview FLW add-on SKUs, but it does not enumerate the exact security or compliance service plans included in base F1. That means you should verify Entra, Intune, Defender, Purview, and compliance entitlements against Microsoft’s current service-plan documentation before relying on a specific control.

Microsoft 365 F1 is commonly evaluated for frontline-worker scenarios, and the catalog also lists FLW add-ons for Defender and Purview. However, the source catalog does not define frontline-worker eligibility rules or use-right limitations, so confirm the Microsoft Product Terms and current assignment requirements before licensing a workforce broadly.

The Commercial catalog includes monthly-term and annual-term purchase patterns, because it lists P1M with monthly billing, P1Y with annual billing, and P1Y with monthly billing. A monthly-billed annual term is still an annual-term subscription, so do not treat it as the same commitment model as a monthly-term subscription.

Yes, the Commercial catalog includes trial entries for Microsoft 365 F1 and Microsoft 365 F1 (no Teams). Trial duration, eligibility, conversion behavior, and limitations are not specified in the source data, so confirm those details before using a trial as part of a rollout plan.

A trial path is listed for Microsoft 365 F1 and Microsoft 365 F1 (no Teams), but the source catalog does not state the conversion mechanics. Confirm whether the trial converts automatically, requires manual purchase, or has tenant-specific limits before assigning it to production users.

Start by choosing the correct Commercial SKU: Microsoft 365 F1, Microsoft 365 F1 (no Teams), or a separate FLW add-on if needed. Then verify the current Microsoft service-plan matrix, user eligibility rules, and any add-on prerequisites before assigning licenses in the tenant. This avoids mixing base F1 licenses with no Teams or add-on SKUs incorrectly.

The catalog confirms both SKU choices, but it does not define the administrative switch process or commercial change rules. In practice, treat a move between Teams-inclusive and no Teams as a SKU change that should be planned around license assignment, renewal timing, and current CSP subscription policies.

Seat-add, proration, and seat-reduction rules are not stated in the source catalog. Confirm the current CSP or New Commerce policy before changing quantities, especially on annual-term subscriptions where monthly billing does not necessarily mean monthly cancellation or reduction rights.

Cancellation-window details are not provided in the source data, so verify the current CSP or New Commerce cancellation rules before ordering. This matters because P1Y monthly-billed subscriptions are annual-term entries, and cancellation rights may differ from a true monthly-term subscription.

Renewal behavior is not stated in the source catalog, so confirm renewal settings, term, billing frequency, and renewal date in the purchasing system before placing the order. This is especially important if you are comparing P1M, P1Y annual-billed, and P1Y monthly-billed options.

A CSP partner change can usually be planned without tenant data migration, because the Microsoft 365 tenant and cloud services remain in place while the billing relationship changes. To avoid downtime, IT Partner should align the transfer with existing subscription terms, renewal dates, license quantities, and the intended Teams or no Teams SKU choice before any old subscriptions are removed.

For the same Microsoft Commercial SKU, term, and billing pattern, the Microsoft catalog basis is the same, but partner-specific fees, discounts, or promotions can differ. User access should not change if license coverage is maintained continuously, because the transfer should be handled as a billing and subscription-management change rather than a tenant rebuild.

No, this page is for the Commercial purchase path, even though the product family is also listed in Government as a separate segment. Government, GCC, GCC High, data residency, and sovereign cloud requirements must be confirmed through the relevant Microsoft Government offer documentation before purchase.

Commercial buyers can use the Commercial purchase path, but Charity and Government are separate listed segments and Education is not confirmed in the provided source data. Nonprofit grant eligibility, charity pricing, student licensing, and faculty licensing should be verified under the appropriate Microsoft program rather than assumed from this Commercial Microsoft 365 F1 SKU.