Microsoft 365's July 2026 Price Increase: A Small Business Budgeting and Right-Sizing Guide

If you pay for Microsoft 365 for your team, your next renewal on or after July 1, 2026 will cost more — even if you never touch the new features Microsoft is adding. For a 15-person shop on Business Standard, that is an extra $270 a year. For a 50-seat E3 tenant, it is $1,800 a year. And if you bought through an Enterprise Agreement with volume discounts, the combined impact of a discount removal in late 2025 plus the new list prices can push your effective increase closer to 20%.

This is Microsoft's first commercial price increase since 2022, and it lands at the exact moment many small businesses are trying to trim subscription spend, not grow it. The good news is you still have decisions to make before your renewal hits. Your plan mix, your license count, and your renewal timing all change the math — but only if you act before the deadline.

This guide covers every plan that is changing, what Microsoft is bundling in to justify the hike, when you actually pay the new rates, and the audit and budgeting steps that turn a price increase into a right-sizing opportunity.

What Is Changing on July 1, 2026​

On December 4, 2025, Microsoft announced new commercial pricing effective July 1, 2026 for most Business, Enterprise, and Frontline suites. The increases apply globally to commercial subscriptions with annual commitments, with local market adjustments. Government suites with large increases will be phased in over multiple years.

Key facts to anchor your planning:

• Effective date: July 1, 2026 for new subscriptions and renewals signed on or after that date. Existing subscriptions stay on current pricing until their next renewal event after July 1.
• Scope: Business, Enterprise, and Frontline families. Microsoft 365 Business Premium and Office 365 E1 hold flat. Microsoft 365 Business Apps and Office applications-only SKUs are included. Standalone Microsoft Teams and standalone Microsoft 365 Copilot add-on licenses are not affected.
• Commitment basis: Prices below are per user per month with an annual commitment. Monthly commitment options typically cost more.
• Microsoft 365 E7 (the Frontier suite launched May 1, 2026) is not part of this update and carries separate promotional pricing through December 31, 2026.

Microsoft frames the change as reflecting investments since 2022 — more than 1,100 features added across security, AI, and device management. Whether that translates into value for your shop depends entirely on whether you already pay for those capabilities elsewhere.

The New Price List: Every Plan That Is Going Up​

All figures are U.S. commercial list prices for suites with Teams included. Without-Teams variants exist for the Suites where Microsoft offers them, and Frontline without-Teams sees an even steeper jump.

Without-Teams F1 is the steepest percentage increase in the table. If your frontline staff actually use Teams on the floor or in the field, the with-Teams configuration at $3.00 is the more defensible choice despite its own 33% rise.

Nonprofit suites move by the same percentages, but the dollar impact is lower because nonprofits pay a fixed discount off commercial list (typically 60–75% off). Government suites with increases above 10% are capped at 10% per annual adjustment until the full increase is phased in — you will not absorb a 25% or 33% government increase in a single year.

How to Translate the Table Into Your Budget​

Run a quick scenario with your current seat count. For annual-commit pricing:

• 12 users on Business Basic: ($7.00 − $6.00) × 12 × 12 = $144 more per year
• 15 users on Business Standard: ($14.00 − $12.50) × 15 × 12 = $270 more per year
• 50 users on Microsoft 365 E3: ($39 − $36) × 50 × 12 = $1,800 more per year
• 200 users on Microsoft 365 E5: ($60 − $57) × 200 × 12 = $7,200 more per year
• 1,000 frontline workers on F3: ($10 − $8) × 1,000 × 12 = $24,000 more per year

Those are list-price deltas only. Your effective delta depends on whether you currently carry add-ons that become redundant and whether you lost Enterprise Agreement volume discounts in late 2025.

What Microsoft Is Adding to Justify the Hike​

Microsoft is not calling this a straight price increase. New capabilities roll out by August 1, 2026 and are included in the base license going forward. For shops already paying for those capabilities as separate add-ons, the bundle can partially offset the hike. For everyone else, it is a price increase with features you did not request.

Business Basic and Business Standard​

• 50 GB additional Exchange mailbox storage
• URL time-of-click protection in Outlook — checks links at the moment a user clicks, not at send time. This closes a real phishing gap for teams without a separate email security gateway.
• Copilot Chat enhancements — inbox and calendar awareness plus agents that can work across Word, Excel, and PowerPoint files. This is the lighter Copilot Chat layer, not the full Microsoft 365 Copilot add-on that remains $30 per user per month for document generation, meeting summarization, and deep email drafting.

Business Premium customers do not see a price increase precisely because these capabilities were already largely included or are being added there at no extra cost — which sharpens the tier comparison discussed below.

Microsoft 365 E3​

E3 gets the most substantive additions of any plan in this cycle:

• Microsoft Defender for Office 365 Plan 1 — enhanced anti-phishing, Safe Links, and anti-malware for Exchange Online and Teams. As a standalone add-on this previously ran about $2 per user per month. If you already pay for it, the $3 E3 increase is partly a reclassification of spend. If you do not use it, you are absorbing a capability you did not shop for.
• Intune Remote Help — secure, cloud-based remote assistance integrated into Intune and Teams.
• Intune Advanced Analytics and Intune Plan 2 capabilities — proactive device health, endpoint analytics, and advanced app management that previously required Intune Suite add-on licenses.

Document which add-ons you carry today. Any that duplicate newly bundled capabilities are candidates to drop at renewal, which directly reduces the net increase.

Microsoft 365 E5​

E5 includes everything added to E3, plus:

• Security Copilot — AI-powered assistance embedded in Defender, Entra, Intune, and Purview workflows. Microsoft includes 400 Security Compute Units (SCUs) per 1,000 licensed E5 users per month; consumption beyond that is metered through Azure.
• Intune Endpoint Privilege Management
• Intune Enterprise Application Management
• Microsoft Cloud PKI — cloud-native private certificate authority for device and user certificates.

These are meaningful for IT teams managing AI usage controls and application security at scale. For a 50-person professional services firm without dedicated security staff, the practical day-to-day value of Security Copilot SCUs may be modest relative to the $3 per seat increase — which is why a usage audit matters more than the feature list.

Frontline F1 and F3​

No major capability bundles were announced for Frontline. The increases there are straightforward list-price moves. For organizations with large frontline populations in retail, manufacturing, or health care, the per-seat numbers look small but the aggregate impact scales quickly.

Why the Real Increase Is Bigger Than the Headline​

The published percentages understate the effective increase for many mid-size and large customers because of a separate change that hit before the pricing announcement.

In November 2025, Microsoft removed Enterprise Agreement volume discounts across its licensing programs. Organizations that previously held Level D EA pricing lost a tiered discount that, for large tenants, was material. That discount removal stacks directly on top of the July 2026 list-price increase — two separate cost events hitting the same renewal.

For example, analysis of a 25,000-user E5 tenant estimated the combined impact of lost EA discounts plus the new list prices at roughly $3 million more per year versus pre-November 2025 pricing — an effective increase closer to 20%, not the 5.3% headline for E5. Organizations that locked a multi-year EA before November 2025 at Level D pricing are protected through their current term. Everyone who renews after that window is negotiating without the discount structure that existed a year ago.

Small businesses on Business plans through CSP or direct purchase never had EA discounts, so the headline percentages are the effective percentages for you. The stacking issue matters most if you buy Enterprise plans through an EA or have grown into EA-eligible seat counts.

When You Actually Pay the New Price​

You do not pay the new rate on July 1 if your renewal is later. You pay it at your next renewal or new subscription event on or after July 1, 2026.

• Annual commitment renewing June 15, 2026 — you renew at current pricing for the full next term, even though your term runs past July 1.
• Annual commitment renewing September 10, 2026 — you renew at new pricing.
• Three-year Enterprise Agreement renewing August 1, 2026 — the entire three-year term prices at new rates.
• Adding seats mid-term before renewal — additional seats typically price at the rate in effect at the time of purchase, not at renewal, so check whether mid-term adds after July 1 carry new pricing even if your base term has not renewed yet.

Should You Renew Early to Lock Current Pricing?​

Renewing before July 1 locks current pricing for the full new commitment term. For a three-year EA that means deferring the increase through 2029. For a one-year Business Standard renewal, it means one more year at $12.50 before moving to $14.00.

Early renewal is worth modeling, not assuming:

Model it when:

• You have high confidence in your plan mix and seat count for the next 12–36 months
• Your tenant is stable — you are not about to migrate, consolidate tenants, or shift a large cohort between Business and Enterprise
• The dollar deferral outweighs the flexibility cost

Skip it or audit first when:

• You have not done a license audit in the last six months. Locking an unoptimized tenant multiplies waste — paying $12.50 for licenses you do not need is still waste, even if you avoid $14.00.
• You carry add-ons that will become redundant. Renewing early before you have mapped add-on overlap means you lock duplicate spend.
• Your headcount is volatile. Annual commitment seats are not easily returned mid-term; monthly commitment costs more but preserves flexibility.

For a 500-seat E3 tenant, the annual delta of $18,000 is often enough to justify the administrative work of moving a renewal forward by a few weeks. For a 12-seat Business Basic tenant, the $144 annual delta rarely justifies the hassle of an off-cycle renewal.

Business Standard vs. Business Premium: The Gap Just Narrowed​

Business Standard moves from $12.50 to $14.00. Business Premium holds at $22.00. The gap between them shrinks from $9.50 to $8.00.

That does not automatically make Premium the right answer, but it does mean you should re-run the comparison at renewal rather than carrying a prior tier decision forward on inertia.

Business Premium includes capabilities Business Standard does not:

• Microsoft Entra ID P1 (formerly Azure AD P1)
• Microsoft Intune device management
• Microsoft Defender for Business
• Conditional Access and advanced identity controls

If you already pay for a separate device management tool, endpoint protection, or identity add-on, compare that standalone spend against the $8 gap. For organizations with remote workers, compliance obligations, or meaningful device management overhead, the $8 often disappears when measured against duplicated tooling. You also consolidate billing and support into one suite.

Premium may not be worth it when:

• You have no device management burden beyond basic Office apps — a team of owner-operators on personal devices with no compliance requirements rarely uses Intune or Defender for Business in practice.
• You are paying for Premium seats for users who only need email and basic Office — those users may be better fit for Business Basic or Apps for business.

The fastest way to decide is a license-by-license audit: who actually uses device management, who opened Defender, who has conditional access policies applied. Usage data beats assumptions.

Nonprofit and Government: Different Rules​

• Nonprofits: Pricing adjusts by the same percentages, but the absolute increase is smaller because the nonprofit discount (often 60–75% off commercial) applies to the new commercial list. Verify your specific nonprofit grant status through your licensing partner — the discount band is not uniform across SKUs.
• Government (GCC and related SKUs): Increases above 10% are phased — no more than 10% in any single annual adjustment until the full increase is complete. This phasing applies per plan, so a Frontline government SKU with a 25% commercial increase will take multiple renewal cycles to reach its new list price. Confirm your specific phasing timeline, since it varies by agreement type.

How to Audit and Right-Size Before July 1​

Three actions make the most difference in the window before your renewal. Do them in order — each one feeds the next.

1. Run a License Truth Audit​

Pull a current license assignment report from the Microsoft 365 admin center and answer:

• Which assigned licenses have not been signed in for 90 days? Those are immediate candidates to remove or downgrade.
• How many mailboxes, Teams users, and OneDrive users actually consumed storage or sent messages in the last 30 days?
• Which users carry E3 or E5 but only use email and Office apps? Downgrading those seats to Business Standard or Apps for business can save $25–$47 per user per month, dwarfing the $3–$14 price increases.
• How many shared mailboxes, room mailboxes, or resource accounts are incorrectly consuming paid licenses?

Aim to complete this at least 60 days before renewal so you have time to reassign or remove seats and run a clean reconciliation before you sign.

2. Map Add-Ons Against Newly Bundled Capabilities​

List every add-on you currently pay for: Defender for Office 365 Plan 1, Intune Suite components, Advanced Analytics, additional mailbox storage, and any Copilot-related licenses. Cross-reference that list against what Microsoft is bundling into your base plan on August 1, 2026.

• Defender for Office 365 Plan 1 on top of E3: candidate to drop at renewal once it is included in base E3.
• Intune Remote Help or Advanced Analytics as standalone: candidate to drop if moving to E3 or E5 that now includes them.
• Security Copilot SCU consumption beyond the included 400 per 1,000 E5 users: model your expected overage through Azure — this is metered spend, not flat.

Document the offset. For example, a 100-seat E3 tenant paying $2 per seat for Defender for Office P1 today sees a gross increase of $300 per month ($3 × 100) but a net increase of roughly $100 per month after dropping the $200 add-on. That net number is what should hit your budget, not the headline.

3. Model Renewal Timing and Commitment Length​

With clean license counts and add-on mapping, model three scenarios:

• Renew now at current pricing vs. renew at new pricing — quantify the deferral in dollars for each commitment length (12 months vs. 36 months for EA).
• Annual commitment vs. monthly commitment — monthly is more expensive but preserves flexibility for volatile headcount. The right answer depends on turnover. A staffing firm with 40% annual churn often saves by paying the monthly premium to return seats.
• Plan mix optimization — what does a blended tenant look like? Not everyone needs the same plan. A common right-sized mix is Business Premium for staff who need device management and E3 only for users who genuinely require enterprise compliance features.

Bring that model to your licensing partner or Microsoft account team before you are in a renewal crunch. Organizations that modeled early have leverage; organizations that react in the last week before renewal do not.

Budgeting and Bookkeeping for the Increase​

A price increase is a bookkeeping event as well as a procurement one. How you record Microsoft 365 affects your monthly profit picture, your department allocations, and your ability to catch leakage.

Recognize the Expense Correctly​

Most small businesses pay Microsoft 365 monthly but commit annually. Even if you pay monthly, you have committed to pay for 12 months — the expense is incurred as you use each month, not when you pay the invoice. For accrual-basis books:

• If you prepay annually at renewal, book the payment to Prepaid Expenses and amortize one twelfth each month. Do not expense the full annual payment in the renewal month, or your profit in that month will look artificially low and every other month artificially high.
• If you pay monthly on an annual commitment, book each monthly invoice to Software and Subscriptions (or IT Expense: Productivity Software) as incurred. The commitment itself is not a liability beyond the next billing — you have a noncancelable commitment, but you recognize expense as service is delivered.

Cash-basis businesses expense as paid, but still track the commitment for cash forecasting. Your forecast should show the stepped increase beginning at the first renewal after July 1, not a sudden annual surprise.

Allocate to Departments or Clients Where Appropriate​

If your chart of accounts supports it, allocate M365 cost beyond a single lump:

• By department: Create subaccounts or classes for Operations, Sales, and Administration and allocate licenses by assigned user. This surfaces the true technology cost of each team rather than burying it in a generic overhead pool.
• By client or project: Service businesses that provision M365 tenants or seats for clients should track per-client subscription cost as a direct or pass-through expense, not as overhead. If you bundle software into a managed service fee, knowing the per-seat cost preserves margin when the underlying suite price rises.

In plain-text accounting systems, a clear naming hierarchy such as Expenses:Technology:Productivity:M365 with department tags keeps allocation transparent and version-controllable.

Build the Increase Into Your Forecast Now​

Do not wait for the renewal invoice to update your forecast. Insert the new per-seat rate effective at your next renewal month and project 12 months forward. For mixed tenants, project by plan:

• Business Basic seats × $7.00
• Business Standard seats × $14.00
• E3 seats × $39.00
• F3 seats × $10.00
• Add-on additions or removals netted separately

Add a line for metered Security Copilot SCU overage if you carry E5 and expect heavy consumption. Even a modest overage estimate prevents a forecast variance that otherwise shows up as an unexplained Azure cost increase.

Reconcile What You Pay Against What Microsoft Bills​

At each monthly billing, reconcile three numbers:

1. Seats assigned in the Microsoft 365 admin center
2. Seats billed on the Microsoft or CSP invoice
3. Seats recorded in your accounting system

Mismatches are common after employee turnover — a departed employee's license removed from assignment but not from billing, or vice versa. A monthly three-way match catches leakage before it compounds. The same discipline applies to annual true-ups: confirm that true-up seat counts match HR hire dates, not just IT request tickets.

Common Mistakes That Waste Money at Renewal​

Paying for seats that no longer have owners. The most common leakage is licenses assigned to former employees or contractors that were never reclaimed. An offboarding checklist that includes license removal within 48 hours prevents this permanently.

Carrying the same plan for everyone. E5 for a user who only needs Business Standard is not resilience — it is $46 per month of unused entitlement. Right-size by job function, not by seniority.

Buying add-ons that are about to be included. Renewing Defender for Office P1 as a standalone add-on on E3 after August 1 duplicates what the base plan now includes. Map before you sign.

Treating annual commitment as monthly flexibility. Annual commitment seats generally cannot be reduced mid-term without penalty. If headcount is uncertain, mixing annual and monthly commitments — annual for stable core staff, monthly for seasonal or project-based hires — balances cost and flexibility.

Forgetting to budget metered consumption. Security Copilot SCUs beyond the included pool and Intune overages beyond bundled capabilities are Azure-metered. Small businesses that never had metered Microsoft spend before can be surprised by a variable Azure invoice. Estimate, budget, and monitor.

Not documenting the tier decision. The Business Standard to Premium comparison is not a one-time judgment. Workforce needs, device management requirements, and standalone tool pricing all drift. Document why you chose a tier at renewal so the next renewal does not default to inertia.

Your Action Plan Before Your Renewal​

Use your actual renewal date, not July 1, as your planning anchor. Counting backward:

• 60+ days before renewal: Pull license assignment and 90-day usage reports. Identify inactive licenses, over-licensed users, and shared mailboxes consuming paid seats. Inventory add-ons.
• 45 days before renewal: Cross-reference add-ons against August 1 bundled capabilities. Build the net-increase model and the blended plan-mix alternative. Decide whether early renewal or tier changes are worth pursuing.
• 30 days before renewal: Update your 12-month forecast with the chosen plan mix at new pricing. Adjust department allocations and prepaid amortization schedules. Confirm monthly vs. annual commitment split for volatile seats.
• At renewal: True up seat counts to HR records, drop redundant add-ons, and record any annual prepayment to Prepaid Expenses with a monthly amortization schedule.

Small businesses that do this work once often build it into a recurring cadence: a quarterly license review tied to the close process, a monthly invoice-to-assignment reconciliation, and a forecast update anchored to the renewal anniversary. The price increase is the trigger; the discipline is the lasting benefit.

Keep Your Tech Spend Transparent and Under Control​

A subscription price increase is a reminder that recurring software costs deserve the same rigor as payroll and rent. Clear records of what you pay, who it covers, and where it is allocated make the next increase easier to absorb and harder to be surprised by.

Beancount.io helps with that rigor. Plain-text, version-controlled accounting gives you a transparent ledger for every subscription, allocation, and amortization — no hidden ledgers, no vendor lock-in, and AI-ready data you can query and forecast against. As you model the Microsoft 365 change and the next dozen SaaS renewals behind it, having your financial records in a format you fully control pays for itself. Get started for free and bring the same clarity to your books that you are bringing to your license audit.