Microsoft Intune Suite Is Now Free in M365 E3/E5: How MSPs Should Restructure Billing Before July 1

Microsoft is not handing out Intune. It is folding more endpoint management into Microsoft 365 E3 and E5, then raising the suite price on July 1, 2026. If you resell Microsoft 365, this is a billing change first and a feature update second.

Quick answer: MSPs should audit every E3 and E5 tenant, compare current Intune add-ons to the new bundle, update quotes before renewal, and tell clients about it before the invoice does.

The math is not subtle. Microsoft says Microsoft 365 E3 moves from $36 to $39 per user per month and Microsoft 365 E5 moves from $57 to $60. That is only a $3 bump per seat, but on a 100-user tenant it is $300 a month or $3,600 a year. Small changes get loud when you sell licenses for a living.

If you want the broader pricing breakdown, start with Microsoft 365 July 2026 Price Increase: The MSP Re-Quoting Playbook. This post is the endpoint-management version of the same problem.

What is actually changing on July 1, 2026?

Microsoft's pricing update is two changes at once:

1. The suite price goes up on July 1, 2026.
2. New Intune and security capabilities start rolling into M365 E3 and E5 during the summer 2026 rollout.

Microsoft says packaging changes begin in June 2026, customers get at least 30 days notice in Message Center before the changes show up in their tenant, and the rollout is complete by August 1, 2026. Existing customers stay on current pricing until renewal.

Here is the part MSPs need to read twice:

Suite	New capabilities rolling in	July 1, 2026 list price
Microsoft 365 E3	Microsoft Defender for Office 365 Plan 1, Intune Remote Help, Intune Advanced Analytics, Intune Plan 2, Copilot Chat enhancements, Copilot Chat Analytics	$39/user/month
Microsoft 365 E5	Everything in E3, plus Microsoft Security Copilot, Intune Endpoint Privilege Management, Microsoft Cloud PKI, and Intune Enterprise Application Management	$60/user/month

Microsoft also says these features are currently available as add-ons or part of the Intune Suite. That is the whole point. The new bundle does not remove the old standalone options, it just changes what is baked into the suite price.

In plain English, this is the stuff MSPs usually end up paying for separately:

• Remote Help covers live remote assistance when a user needs a human, not a knowledge base article.
• Advanced Analytics gives you better endpoint visibility, trends, and health reporting.
• Intune Plan 2 is the advanced management layer that supports more complex device work.
• Endpoint Privilege Management controls when users can request temporary admin rights without turning everyone into a local admin.
• Microsoft Cloud PKI handles certificate workflows without another vendor glued to the stack.
• Enterprise App Management helps with third-party app packaging and control.

What MSPs typically bill separately today that's now included

This is where the billing mess starts.

If you already sell endpoint management as a premium layer, you may have separate line items for:

• Remote Help
• Advanced analytics or endpoint analytics
• Privilege management
• Cloud PKI
• Enterprise application management

If those items are already separate on the invoice, July 1 does not just change Microsoft pricing. It changes your service math.

That can work in your favor if you handle it cleanly.

• If the client already buys the feature separately, you can fold it into the base bundle and simplify the bill.
• If the client never used the feature, do not pretend they are suddenly getting a gift. They are paying more for something they may not touch.
• If you bundled the feature into a managed service fee, the new Microsoft pricing may change how much room you have left in that fee.

The mistake is treating this like a press release. It is a margin review.

Three billing scenarios and what to do in each

1. You have been billing these features separately

This is the cleanest problem and the easiest one to ignore until it gets expensive.

If you sold Remote Help or other Intune capabilities as premium add-ons, you need to decide whether the new M365 bundle replaces that line item or just changes the value story.

The right move is usually one of these:

• Fold the capability into the base suite and remove the extra line item.
• Keep the separate line item only if it still includes real work, not just the Microsoft license.
• Reprice the whole agreement if the old packaging no longer reflects how the client is actually supported.

Do not keep billing for the same thing twice just because the invoice template still lets you.

2. You have not offered these features yet

This is the upside case.

Microsoft just made it easier to package more endpoint management into the stack without buying a pile of separate add-ons. That means you can build a more useful service tier without introducing new tool cost.

If you want to move a client up a tier, the new bundle gives you a cleaner argument:

• Better endpoint control
• Better visibility
• Better privilege management
• Less dependence on bolt-on tools

That is not a free lunch, because the suite still costs more. But it is a stronger story than selling generic "managed Microsoft 365" and hoping the client does not ask what they get for the extra spend.

3. The client is on Business Premium, not E3 or E5

This change does not hit the base price of Business Premium.

That said, it changes the upsell math. If a client is growing into more endpoint complexity, the line between Business Premium and E3 just got easier to explain. You are no longer selling vague "enterprise readiness." You are selling specific management features that Microsoft is now bundling into the higher suites.

That is a better conversation than "we think you should move up because reasons."

How to audit current client agreements against the new bundle

Do this before you write a single client email.

1. Pull every active M365 E3 and E5 client.
2. List the current Microsoft 365 license, any Intune add-ons, and any endpoint management line items in the service agreement.
3. Flag clients who already pay separately for Remote Help, advanced analytics, privilege management, or app management.
4. Flag clients who are on renewal windows between July and September.
5. Decide whether each account needs pass-through pricing, a rebundle, or a no-change note.
6. Set a review deadline before June 15 so your account managers are not drafting apologies in late June.

If this still lives in a spreadsheet with four tabs and a prayer, that is your real problem.

The useful output is not a spreadsheet. It is a clean list of:

• clients to notify
• clients to re-quote
• clients to leave alone
• clients where the bundle now covers work you were already doing

That is the difference between bookkeeping and billing strategy.

How to have the repricing conversation without losing trust

Do not lead with "Microsoft changed something."

Lead with "we reviewed your tenant and checked what changed."

That matters because clients do not care that a vendor memo exists. They care that you are watching their account closely enough to catch it before the bill changes.

Here is a simple version of the message:

Microsoft is updating Microsoft 365 pricing on July 1, 2026. We reviewed your current licenses and the endpoint management features you already use. Here is the new monthly total, what changed, and whether any of your current add-ons should be folded into the new bundle.

Short. Specific. No theater.

If the client is already using the capabilities, say that plainly. If they are not, say that too. If the agreement needs a pricing adjustment, tell them before the invoice does the talking for you.

What this means for your service tier architecture

This is not just a billing event. It is a tier design event.

If your tiers are still built around "good / better / best" language with no real feature logic behind them, the Intune change exposes the gap. The higher Microsoft 365 suites now include real management capabilities that are easy to point at, easy to compare, and easy to justify.

That gives MSPs three clean moves:

• Standardize what lives in each tier.
• Stop bundling away capabilities you should be naming explicitly.
• Use the new M365 E3 and E5 bundle to justify an upgrade only when the tenant actually needs the features.

If you are still pricing service tiers by memory, this is a good moment to stop.

Microsoft already gave you the checklist for the features. Use it.

Do this before July 1

If you only do one thing, do this:

1. Audit every M365 E3 and E5 client.
2. Check which accounts already buy Intune-related add-ons.
3. Compare those add-ons to what Microsoft is now bundling.
4. Update quotes or service agreements where the bundle changes your math.
5. Send client notices before renewal, not after the invoice lands.
6. Keep the wording blunt and calm. Nobody needs a dramatic licensing manifesto.

If you want the broader pricing context, read Microsoft 365 July 2026 Price Increase: The MSP Re-Quoting Playbook. If you want the operational side of turning this into a cleaner service model, join Scopable early access.