M365 July 2026 Price Increase: The MSP Re-Quoting Playbook

Microsoft 365 prices change on July 1, 2026. If you resell M365 through CSP, this is not just a Microsoft announcement your clients can read later. It is a quoting problem, a margin problem, and a client communication problem with a fixed date attached.

A 40-seat Business Standard client moves from $500/month at list price to $560/month. That sounds small until you multiply it across every client, SKU, renewal date, and agreement where your pricing is already too loose.

Quick answer: MSPs should handle the M365 July 2026 price increase by auditing affected licenses, calculating the per-client annual delta, deciding whether to pass through or right-size each agreement, then sending revised quotes before the client sees the new number on an invoice.

What is actually changing on July 1, 2026?

Microsoft's official pricing page says commercial pricing updates take effect July 1, 2026, while existing customers stay on current pricing until their next renewal. The update affects Enterprise, Business, Frontline, Government commercial equivalents, and several standalone components. Standalone Teams and Copilot SKUs are not part of this pricing update.

For the MSP owner managing SMB clients, these are the numbers to care about first:

Plan	Current list price	New list price July 1, 2026	Change
Microsoft 365 Business Basic	$6.00/user/month	$7.00/user/month	+16%
Microsoft 365 Business Standard	$12.50/user/month	$14.00/user/month	+12%
Microsoft 365 Business Premium	$22.00/user/month	$22.00/user/month	No list price change
Microsoft 365 F1	$2.25/user/month	$3.00/user/month	+33%
Microsoft 365 F3	$8.00/user/month	$10.00/user/month	+25%
Microsoft 365 E3	$36.00/user/month	$39.00/user/month	+8%
Microsoft 365 E5	$57.00/user/month	$60.00/user/month	+5%

Source check: these figures come from Microsoft's Microsoft 365 Pricing and Packaging Updates page. Microsoft's public FAQ also says pricing changes apply globally at the next renewal after July 1, 2026, with local market adjustments where applicable.

Two details matter for MSPs: Business Premium does not show a list price increase in Microsoft's table, but it does receive packaging changes. And Microsoft list pricing is only the planning input. Pull your distributor sheet before changing client quotes.

Why this is an MSP margin problem, not a Microsoft news item

The client sees a small per-user change. You see the operational mess.

Take a basic portfolio:

Client segment	Example mix	Monthly list-price delta	Annual delta
25 users on Business Basic	25 x $1.00 increase	$25	$300
40 users on Business Standard	40 x $1.50 increase	$60	$720
70 users on F3	70 x $2.00 increase	$140	$1,680
100 users on M365 E3	100 x $3.00 increase	$300	$3,600

None of those numbers are terrifying alone. The danger is silent absorption.

If your agreements say M365 is included inside a managed services bundle and you do not have clean pass-through language, the increase can come out of your margin. If the client is month-to-month and your billing system updates before your account manager explains it, the client hears about the change from the invoice instead of from you. That is how a vendor price change becomes a trust tax.

Most MSP clients are not asking for enterprise licensing strategy. They are asking a simpler question: "Why is my bill higher, and did my MSP see this coming?" Your answer needs to be yes.

Step 1: Audit your M365 exposure before June

Do not start with a client email. Start with the client list.

Pull every active M365 subscription from your CSP portal, PSA, billing system, or license management tool. For each client, capture:

• SKU name
• Seat count
• Current cost
• Renewal date
• Billing term: monthly, annual, or multi-year
• Agreement language: pass-through, bundled, or unclear
• Client owner
• Last quote or proposal date

Then tag each client: re-quote now, add to renewal calendar, confirm packaging changes only, or right-size before quoting.

This is where many MSPs find the real money. The price increase might add $60/month for one client, but the audit may reveal 11 inactive users on Business Standard. Removing those seats saves $154/month at the new list price. The price change becomes a reason to clean up license waste, not just a reason to pass along a higher bill.

If you already run quarterly business reviews, fold this into the same data pull. If you do not, this is your excuse to build the habit.

Step 2: Pick the right pricing move for each client

There are three sane ways to handle this. Pick per client, not across the whole base.

Option 1: Pass through with a clear explanation

This is the default for clean agreements. Microsoft changes the list price, your agreement reflects the new cost, and you explain it before the bill changes.

Use this when the client is on the right SKU, seat counts are clean, your agreement allows vendor price pass-through, and the annual delta is small enough that a full repricing conversation would be overkill. Clients need the number, the date, and what you checked.

Option 2: Right-size first, then pass through

This is the best path for clients with messy license counts.

Use the price change as the forcing function: remove inactive users, downgrade users who do not need the current SKU, consolidate duplicate licenses, confirm annual commitments before July where it makes financial sense, then re-quote the cleaned-up environment.

This keeps the client conversation constructive. You are not saying, "Microsoft made your bill go up." You are saying, "Microsoft pricing changes in July, so we reviewed your tenant and found a way to control the impact."

Option 3: Reprice the service agreement

Sometimes the M365 change exposes a larger issue. The client has grown. The scope changed. Your service bundle includes too much vendor cost. Your agreement still reflects a stack from two years ago.

Use this path when:

• Vendor costs are eating managed services margin
• The client has outgrown the original agreement
• M365 is bundled with security, support, and vCIO work in one flat number
• You have not re-priced the client in more than 12 months

This is the most sensitive option. It needs a real business review, not a surprise email. But it is also the path that fixes the underlying margin problem.

Step 3: Build the re-quoting workflow

Here is the manual version most MSPs will end up doing if they wait too long:

1. Export license counts.
2. Match subscriptions to clients.
3. Find the current agreement or quote.
4. Update unit prices.
5. Recalculate monthly and annual totals.
6. Add a note explaining the Microsoft change.
7. Send to the account manager for review.
8. Send to the client.
9. Update the PSA or billing system.

If that takes 30 minutes per client and you have 60 affected clients, that is 30 hours before anyone handles exceptions. If it takes 40 minutes, you lose a full workweek.

Better workflow: connect license data to quoting data, update the M365 price table once, generate affected-client quote drafts in bulk, then let account managers review exceptions instead of rebuilding every quote by hand.

That is the operational point. Automation should not remove judgment from the pricing conversation. It should remove copy-paste work from the process so your team can spend time on the clients where the decision is not obvious.

Scopable is built for that kind of workflow: live client data, scoped changes, margin-aware quotes, and less spreadsheet archaeology. If you want to test that before July, join Scopable early access.

Step 4: Give clients the email before the invoice changes

Here is a simple template your account managers can adapt.

Subject: Microsoft 365 pricing change for [Client Name]

Microsoft is changing commercial Microsoft 365 pricing on July 1, 2026. We reviewed your current licenses so you are not surprised by the change at renewal.

Your affected plans are [plans]. Based on your current seat count, the estimated change is [monthly delta] per month, or [annual delta] per year. We also checked for inactive or mismatched licenses and found [cleanup summary].

Our recommendation: [pass through / right-size first / review agreement]. We will update your quote before the new pricing applies and walk you through the exact numbers before anything changes on your bill.

Short. Specific. No panic.

The important line is "we reviewed your current licenses." That tells the client you did not forward a Microsoft notice and call it account management. You checked their account.

What Microsoft says clients are getting with the change

Microsoft is positioning the pricing update around added value. The packaging changes begin rolling out in summer 2026, with Microsoft saying customers will receive at least 30 days notice in Message Center before changes become available in their tenant.

Examples from Microsoft's packaging table include:

• Business Basic and Business Standard: 50GB email, URL time-of-click protection, Copilot Chat enhancements, and Copilot Chat Analytics
• Microsoft 365 E3: Defender for Office Plan 1, Intune Remote Help, Intune Advanced Analytics, Intune Plan 2, Copilot Chat enhancements, and Copilot Chat Analytics
• Microsoft 365 E5: E3 additions plus Microsoft Security Copilot, Intune Endpoint Privilege Management, Microsoft Cloud PKI, and Intune Enterprise Application Management

Use those details carefully. Do not promise value the client will not use. For some clients, the added security and management tools can replace separate spend or justify staying on the current tier. For others, it is just a higher Microsoft bill with features they will not deploy this quarter.

What happens if you miss the July 1 window

Nothing explodes, so this is easy to ignore.

The mess shows up slowly:

• Monthly clients renew into higher pricing without a clean client conversation.
• Annual renewals after July pick up new pricing on the renewal date.
• Your team handles one-off questions instead of one planned communication wave.
• Clients assume you reacted late, even if Microsoft gave the market months of notice.
• Margin gets squeezed where agreements do not pass through vendor cost cleanly.

This is preventable admin pain. Put the re-quoting sprint on the calendar now, while there is still time to be calm and precise.

The MSP playbook before July 1

Here is the short version:

1. Export every M365 subscription and renewal date.
2. Verify exact CSP pricing against your distributor sheet.
3. Calculate the monthly and annual delta by client.
4. Remove unused seats before sending new quotes.
5. Decide which clients need pass-through, right-sizing, or full repricing.
6. Draft quotes and client emails before invoice changes hit.
7. Update PSA, billing, and account manager notes in the same pass.

Do that and the M365 July 2026 price increase becomes a controlled client communication, not a margin leak.

If you want the faster version, connect your PSA, RMM, and M365 data so affected-client quotes can be generated from current environment data instead of rebuilt by hand. Join Scopable early access and test the workflow before July catches up.