The gap between E1 and E3 just got wider, and that is why your finance team is asking about it.
On July 1, 2026, Microsoft 365 E3 rose from $36 to $39 per user per month. Office 365 E1 did not move. It held at $10. The spread between the two went from $26 to $29 per user per month, which is $348 per user per year. Across 500 users that is $174,000 a year sitting in a single line item, and it is now a larger number than it was in June.
So the question arrives from finance, not from IT: can some of these people move down?
The answer is yes for a specific population and no for another, and the difference is not the org chart. It is dependency. This article covers what actually separates an E1 candidate from an E3 requirement, why the license most E1 candidates should get is not E1 at all, and how to make the call with evidence rather than with a spreadsheet.
What Changed in the E1 vs E3 Gap on July 1, 2026
Three price movements matter for this decision, and they did not move in the same direction.
Microsoft 365 E3 rose 8.3 percent, from $36 to $39. Office 365 E3 rose 13 percent, from $23 to $26, the steepest increase in the enterprise lineup. Office 365 E1 held flat at $10, treated in Microsoft’s pricing and packaging update as a packaging change rather than a price increase.
The practical effect is that every argument for moving users down got stronger on the same day, without anyone at your organization doing anything. If your renewal falls after July 1, you inherit the new spread whether or not you revisit your license mix.
There is a second movement that most comparisons miss, and it changes the answer for the largest E1 candidate population. More on that in a moment.
Existing customers stay on current pricing until their first renewal after July 1, 2026. If your renewal already passed, you are paying the new rate now. If it is ahead of you, the audit work has a deadline you did not set.
What Office 365 E1 Actually Includes, and What It Does Not
E1 is a web and mobile plan. That single sentence explains most of what follows.
What E1 includes. Web and mobile versions of Word, Excel, PowerPoint, and Outlook. Exchange Online with a 50 GB mailbox. Teams. SharePoint. OneDrive with 1 TB. Basic security and a 99.9 percent uptime commitment. For a user who lives in a browser, this is a complete product.
What E1 does not include. The desktop applications. That is the boundary that breaks downgrades. A user on E1 cannot install Excel on their laptop. They open it in a browser tab.
E1 also excludes the Enterprise Mobility and Security stack that comes with Microsoft 365 E3: Intune device management, Entra ID P1 with conditional access, Azure Information Protection, and Windows Enterprise. It excludes advanced compliance features such as eDiscovery and retention policies at the E3 level.
Our Office 365 E1 reference page covers the full inclusion list. What matters for the downgrade decision is narrower: desktop apps, device management, and conditional access. Those three account for the overwhelming majority of failed downgrades.
The License Most E1 Candidates Should Get Is Not E1
Here is the movement that changes the answer.
Microsoft 365 F3 rose 25 percent on July 1, from $8 to $10 per user per month. Office 365 E1 held at $10.
They now cost the same.
For years the frontline conversation had an easy answer on price: F3 was cheaper than E1, so frontline users went to F3. That argument is gone. At identical list price, the decision has to be made on capability and on licensing rules, which is a harder conversation and a better one.
What F3 gives you that E1 does not. Intune device management. Entra ID P1, which means conditional access. Windows Enterprise E3 rights. Basic Microsoft Defender coverage. In other words, F3 carries a meaningful slice of the security and device management stack that E1 lacks entirely.
What E1 gives you that F3 does not. A 50 GB mailbox instead of 2 GB. Full SharePoint and OneDrive storage instead of restricted allocations. No licensing restriction on who can hold it.
The rule that decides it. F1 and F3 are licensed for frontline workers, defined by Microsoft as deskless, shift-based, or field staff who do not have a dedicated workstation. You cannot assign F3 to an information worker and stay compliant. E1 has no such restriction.
So the decision tree is not E3 or E1. It is three questions:
- Is this person a frontline worker under Microsoft’s definition? If yes, F3 at $10 gives you more than E1 at $10, and F1 at $3 covers view-only staff.
- If not frontline, do they need desktop apps or device management? If yes, they stay on E3.
- If not frontline and no desktop or device dependency, E1 at $10 is the fit.
Most organizations reviewing an E1 downgrade have not asked question one. That is where the money and the compliance exposure both sit. Microsoft documents the frontline definition in its frontline worker licensing guidance.
Which Users Can Move From E3 to E1 Without Risk
Four populations clear the bar consistently.
Browser-only office staff. Users whose entire working day happens in Outlook, Teams, and a handful of web applications. They open documents to read them and occasionally edit. They do not build anything. In most mid-market organizations this is a larger group than IT expects, concentrated in operations, scheduling, and coordination roles.
Contractors and temporary staff. Short engagements, limited system access, no device managed by your organization. The absence of Intune in E1 is not a gap here because you were not managing their device anyway.
Read-mostly staff in shared functions. Users who consume reports rather than produce them. They need the mailbox and the meeting, not the modeling.
Secondary accounts. Service mailboxes, shared inboxes with named owners, and accounts that exist for routing rather than for a person. These frequently sit on E3 for no reason other than that they were provisioned during an earlier migration.
The test that works is not job title. Pull the Microsoft 365 usage report for the last 90 days and look at desktop application activations per user. A user with zero desktop activations in 90 days is a candidate. A user with daily desktop activations is not, regardless of what their role description says.
Where the Downgrade Creates Risk
Four dependencies break downgrades, and three of them are invisible in a license report.
Desktop application dependency. Excel is the recurring one. Web Excel handles ordinary spreadsheets and fails on the things finance and operations actually build: large workbooks, pivot-heavy models, add-ins, macros, and Power Query. A controller moved to E1 discovers this on day one and the ticket lands the same afternoon. Access and Publisher are also desktop only.
Device management dependency. E1 has no Intune. If your organization enrolls corporate devices, enforces compliance policies, or wipes lost laptops remotely, moving a user to E1 removes them from that framework. This is the dependency that most surprises organizations, because device management is administered by a different team than licensing.
Conditional access dependency. E3 includes Entra ID P1, which is what enforces conditional access policies. E1 does not. Move a user to E1 and any policy that depends on P1 stops applying to them. In a Zero Trust posture, that is a hole in the model rather than a downgrade.
Compliance dependency. Retention policies, eDiscovery, and audit capability step down with the license. For a user whose mailbox or files fall under a legal hold or a regulatory retention requirement, the downgrade is not a cost decision. It is a compliance event.
The pattern across all four: the capability is invisible until it is removed, because the people who depend on it never had to ask for it.
The Hidden Cost of Downgrading the Wrong User
The savings are easy to calculate and the cost is not, which is why the cost usually wins.
Moving one user from Microsoft 365 E3 to Office 365 E1 saves $29 per month, or $348 per year. That is the number in the business case.
Now price the other side. A single support ticket costs most mid-market IT organizations between $20 and $60 in loaded time to resolve. A user who cannot open their workbook the way they used to generates more than one ticket. Add the workaround period, the manual escalation path, and the eventual reversal when someone senior notices, and a wrong downgrade consumes the annual saving inside the first quarter.
That math holds even before counting the reputational cost. A licensing project that visibly broke someone’s job does not get a second budget cycle.
The asymmetry is what should drive the process. A correct downgrade saves $348 a year. An incorrect one costs more than that and also costs the credibility of the next optimization initiative. When the downside is larger than the upside, evidence beats speed.
A Segmentation Framework That Survives Scrutiny
Five columns, one row per user population. This is the artifact that turns a licensing argument into a licensing decision.
| Step | Question | Evidence to gather |
|---|---|---|
| Role | What does this population actually do? | Function, not job title. Group by working pattern. |
| Requirements | Which applications does the work require? | Microsoft 365 usage report, desktop activations over 90 days. |
| Dependencies | What else breaks if the license changes? | Intune enrollment status, conditional access policy scope, retention holds. |
| Risk | What is the consequence of removing the capability? | Regulatory exposure, business continuity, support volume. |
| License | Which plan fits, including F-series? | E3, E1, F3, or F1, with the frontline eligibility test applied. |
The fifth column is where most frameworks go wrong by offering only two options. Adding F1 and F3 to the decision usually changes the answer for the largest population under review, and it is the difference between a licensing exercise and a licensing strategy.
For organizations under 300 users, the Business Premium and Business Standard comparison is a separate track worth evaluating before the enterprise plans, since Business Premium held flat at $22 and includes device management that E1 lacks.
Five Questions to Answer Before Renewal
Answer these with data rather than with recollection.
- Who currently holds E1, E3, and E5, and how many of each? Pull the assignment report, not the purchase order.
- How many desktop activations did each population record in the last 90 days? Zero activations is the strongest single downgrade signal available to you.
- Which users are enrolled in Intune, and which are covered by conditional access policies? These define the population that cannot move to E1 regardless of application usage.
- Which mailboxes or sites are under retention or legal hold? Compliance overrides cost.
- How many users meet Microsoft’s frontline definition? This is the question that reveals whether F3 belongs in the conversation, and it is the one most organizations skip.
An organization that can answer all five has a defensible plan. An organization that can answer two is guessing with a spreadsheet, and the guess costs more than it saves.
If the broader tier comparison is still open, our Microsoft 365 license cost guide covers the full E1, E3, and E5 pricing structure, and the E3 vs E5 comparison covers the decision at the other end of the range.
Frequently Asked Questions
What is the difference between E1 and E3?
Office 365 E1 provides web and mobile access to Microsoft 365 applications with a 50 GB mailbox, Teams, SharePoint, and OneDrive. Microsoft 365 E3 adds the desktop applications, Intune device management, Entra ID P1 with conditional access, Windows Enterprise, and advanced compliance capability. As of July 1, 2026, E1 costs $10 per user per month and Microsoft 365 E3 costs $39, a difference of $29 per user per month or $348 per year.
Can I move all my users from E3 to E1 to save money?
No. Four dependencies break the downgrade: desktop application use, Intune device enrollment, conditional access policy coverage, and compliance retention or legal hold. The reliable test is desktop application activations over the last 90 days combined with Intune enrollment status. A user with zero desktop activations who is not enrolled in device management and not under a retention hold is a candidate. Everyone else needs a case by case review.
Should frontline workers get E1 or F3?
For genuine frontline workers, F3 is usually the better fit. Since July 1, 2026, F3 and Office 365 E1 both cost $10 per user per month, so price no longer separates them. At the same price, F3 includes Intune device management, Entra ID P1, and Windows Enterprise rights that E1 does not. The constraint is that F1 and F3 are licensed only for frontline workers, meaning deskless, shift-based, or field staff without a dedicated workstation. Information workers cannot be assigned F-series licenses.
Does Office 365 E1 include desktop Office applications?
No. E1 provides web and mobile versions only. Users can open and edit documents in a browser or on a phone, but cannot install Word, Excel, PowerPoint, or Outlook on a computer. This is the single most common cause of failed downgrades, particularly for finance and operations staff who rely on desktop Excel for large workbooks, pivot tables, add-ins, or Power Query.
Did the July 2026 price increase change the E1 versus E3 decision?
It widened the gap and changed the frontline answer. Microsoft 365 E3 rose 8.3 percent to $39 while Office 365 E1 held flat at $10, increasing the spread to $29 per user per month. At the same time F3 rose 25 percent to $10, matching E1 exactly. The result is that downgrading to E1 saves more than it did before, while the F3 versus E1 choice for frontline staff must now be made on capability rather than on price.
What happens to conditional access if a user moves to E1?
Conditional access requires Entra ID P1, which is included in Microsoft 365 E3 but not in Office 365 E1. Moving a user to E1 removes them from the scope of any conditional access policy that depends on P1 licensing. For organizations operating a Zero Trust model, this creates a gap in enforcement rather than a reduction in features, and it is frequently missed because identity policy and license assignment are managed by different teams.
How much does a wrong downgrade actually cost?
Moving one user from E3 to E1 saves $348 per year. A user who loses a capability they depend on generates support tickets that cost most mid-market IT organizations $20 to $60 each in loaded time, plus the workaround period and the eventual reversal. In practice a single wrong downgrade consumes its own annual saving within the first quarter, which is why the segmentation work should precede the change rather than follow the escalation.
How do I identify which users to move?
Group users by working pattern rather than by job title, then gather four pieces of evidence for each group: desktop application activations over the last 90 days, Intune enrollment status, conditional access policy coverage, and any retention or legal hold. Apply Microsoft’s frontline definition to determine whether F-series licensing is available. The populations that clear all four checks are candidates. The rest are exceptions that need individual review.
