For a US buyer using annual commitments, Microsoft 365 Business list prices with Teams are $7, $14, and $22 per user per month for Basic, Standard, and Premium from 1 July 2026. Model role-based license mixes, migration, identity, security, voice, backup, support, and renewal timing before comparing the quote.
Official public sources checked 15 September 2026. Prices below are USD list-price references, not a quote. Country, currency, tax, reseller, promotion, contract, legacy subscription, quantity, and renewal date can change the payable amount.
Published plan-price snapshot
| Plan | Billing basis | Published rate | What to verify |
|---|---|---|---|
| Business Basic with Teams | Annual | $7 | Web and mobile apps, email, storage, Teams |
| Business Standard with Teams | Annual | $14 | Adds desktop apps and broader collaboration capability |
| Business Premium with Teams | Annual | $22 | Adds advanced identity, security, and device management |
| Business Basic without Teams | Annual | $5.4 | No Teams entitlement |
| Business Standard without Teams | Annual | $10.79 | No Teams entitlement |
| Business Premium without Teams | Annual | $18.79 | No Teams entitlement |
A price row answers only the starting arithmetic. Before approval, preserve the dated vendor page or quote, record the currency and billing term, and identify every population that will be charged. If the vendor page and order form differ, the signed order form and governing contract control the purchase.
How Microsoft 365 billing changes total cost
- The 1 July 2026 change applies to commercial list pricing; currency, country, channel, promotion, and tax can change the quote.
- Existing paid subscriptions generally move to updated pricing at renewal rather than in the middle of a term.
- A with-Teams versus without-Teams decision changes both price and the collaboration architecture; compare the complete operating stack.
- Business plans have user and service limits. Confirm whether the intended population, shared devices, frontline roles, compliance, voice, BI, and AI require other licenses or add-ons.
Illustrative annual license baselines
The examples use the second paid public plan shown above where available. They are reproducible arithmetic, not a forecast or recommendation.
| Population | Assumption | Annual baseline | Excluded |
|---|---|---|---|
| 25 paid users | Business Standard with Teams · Annual | $4,200/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 100 paid users | Business Standard with Teams · Annual | $16,800/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 250 paid users | Business Standard with Teams · Annual | $42,000/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
Cost drivers the quote must expose
- Role-based mix of Basic, Standard, Premium, frontline, guest, shared-device, and specialist licenses
- Migration partner scope for mail, files, permissions, devices, and tenant configuration
- Identity, endpoint, compliance, telephony, backup, BI, and AI add-ons
- Internal administration, support tier, adoption, coexistence, and dependent tools
- Reduction rights, reassignment, renewal uplift, and the timing of true-ups
Build base, expected, and stress cases. A useful model separates recurring licenses and consumption from one-time vendor services, internal implementation effort, dependent tools, and exit work. Record unknown values as a range with an owner and decision deadline rather than silently entering zero.
Questions to put in writing
- Which users need desktop applications, advanced security, device management, voice, or compliance?
- Is Teams included in every quoted SKU, and what replaces it if excluded?
- Which migration objects, permissions, histories, devices, and validation tasks are included?
- Can licenses be reduced, reassigned, or mixed during the term and at renewal?
- Which quoted rates are list, promotional, partner-discounted, or protected beyond year one?
Renewal and exit checks
Record the initial term, renewal term, auto-renewal status, notice deadline and delivery method, protected pricing, uplift rule, minimum quantity, reduction window, reassignment rights, usage true-up, data-export method, post-termination access, deletion schedule, and retained-data exceptions. Test the export before the renewal decision if the product will hold business-critical records.
Official sources used
PR97 summarizes public vendor information for comparison. It has not inspected your tenant, order form, reseller proposal, or negotiated contract. Recheck the linked official source and written quote on the day of decision.
Normalize the quote in one worksheet
Capture plan, billable unit, allowances, services, internal cost, renewal, and exit assumptions beside their evidence.
Microsoft 365 approval record
The approval should state which operating roles require this service, why the selected edition is necessary, and which evidence proves the mandatory workflow. For Microsoft 365, record the exact quote, plan, billable population, included allowance, add-on, service scope, implementation owner, and first renewal deadline beside the decision.
Commercial facts to reconcile
- The 1 July 2026 change applies to commercial list pricing; currency, country, channel, promotion, and tax can change the quote.
- Existing paid subscriptions generally move to updated pricing at renewal rather than in the middle of a term.
- A with-Teams versus without-Teams decision changes both price and the collaboration architecture; compare the complete operating stack.
- Role-based mix of Basic, Standard, Premium, frontline, guest, shared-device, and specialist licenses
- Migration partner scope for mail, files, permissions, devices, and tenant configuration
- Identity, endpoint, compliance, telephony, backup, BI, and AI add-ons
- Internal administration, support tier, adoption, coexistence, and dependent tools
Reviewer questions
- Which users need desktop applications, advanced security, device management, voice, or compliance?
- Is Teams included in every quoted SKU, and what replaces it if excluded?
- Which migration objects, permissions, histories, devices, and validation tasks are included?
After launch, compare the first invoice with provisioned access and expected usage. Review adoption by required role and workflow at 30, 60, and 90 days. Before notice is due, test a current export and decide whether to retain, resize, renegotiate, replace, or cancel. Keep this evidence with the order form so future reviewers can reproduce both the cost and the reason for the purchase.