Heads‑up: Microsoft 365 Apps is unifying SAEC and MEC in July—here’s how MSPs should prep
Starting with Version 2606 in July, Microsoft will merge Semi‑Annual Enterprise Channel into Monthly Enterprise Channel. Expect a one‑time larger update and new Copilot eligibility for supported users. Here’s the MSP checklist.
Microsoft is collapsing Semi‑Annual Enterprise Channel (SAEC) into Monthly Enterprise Channel (MEC) beginning with Microsoft 365 Apps Version 2606 in July 2026. Devices on SAEC will start receiving the same features and security updates as MEC, and after the update they’ll show MEC in the Office “Account” page. The first jump (for many estates, 2508 → 2606) is bigger than usual—roughly a 1.6 GB payload—then you’re back to normal monthly sizes. Devices that meet Copilot requirements become eligible once they’re on the MEC experience.
Why this matters for MSPs
- A one‑time bandwidth spike can hit branch sites and remote users.
- Reporting and automation that key off “SAEC” labels will flip to “MEC.”
- Cloud Update may trigger a second notification in July to complete the channel change on onboarded devices.
A fast readiness checklist
- Validate inventory: export all devices currently on SAEC per tenant; confirm update rings/GPO/Intune policies don’t pin to an old build.
- Plan bandwidth: schedule maintenance windows, pre‑stage content where possible, and set expectations with customers that July’s Office update is larger.
- Update automations: adjust detection rules, scripts, and dashboards that filter by channel name. Treat “MEC” as the new steady state.
- Review end‑user comms: assure users the change won’t alter day‑to‑day workflows; it just aligns update cadence.
- Cloud Update tenants: check the Apps admin center. After 2606, eligible devices evaluate as MEC and can be brought under Cloud Update if desired.
- Copilot customers: re‑evaluate eligibility post‑update; MEC is a prerequisite for many Copilot experiences.
The takeaway
This is an operational event more than a technical crisis: one larger update, new labels, and then business as usual on MEC. Do a quick sweep now so your networks—and your reporting—don’t get surprised.
How many of your tenants still have SAEC devices, and what’s your plan to stage the 2606 jump without saturating links?