Microsoft announced a new SKU tier in March 2026. It became generally available on May 1. It is called Microsoft 365 E7 — internally branded the Frontier Suite — and it costs $99 per user per month.
Three things are happening at the same time that make this worth reading carefully before your next EA renewal:
- Microsoft E7 is a real product that bundles four things you might otherwise buy separately — and those components are worth roughly $117 per user per month if priced standalone.
- Microsoft is raising E3 prices from $36 to $39 and E5 prices from $57 to $60 per user per month, effective July 1, 2026.
- Enterprise customers are receiving push from Microsoft account teams to evaluate E7 as part of their next EA renewal — often framed as a natural upgrade from E5.
The result is a set of decisions that need clear commercial analysis, not a vendor-led upgrade conversation.
This guide covers what E7 actually contains, who needs it, what it costs at scale, and how to negotiate it into an EA without overpaying for capabilities most of your organization will not use.
What Microsoft 365 E7 Contains
Microsoft 365 E7 bundles four distinct products:
Microsoft 365 E5. The full E5 stack — Office apps, Teams, Exchange, SharePoint, OneDrive, Defender for Endpoint, Defender for Identity, Defender for Office 365, Intune, Purview compliance and eDiscovery, Power BI Pro, and the complete E5 security and compliance capabilities. If you are already at E5, this is the base you know.
Microsoft 365 Copilot. Microsoft’s AI assistant embedded across Word, Excel, PowerPoint, Teams, Outlook, and Loop. Copilot was previously sold as a separate add-on at $30 per user per month. In E7 it is included in the bundle. This is one of the two primary financial arguments for E7 over buying standalone.
Microsoft Agent 365. Microsoft’s control plane for deploying, managing, and governing AI agents across your Microsoft estate. Agent 365 is new infrastructure — it covers agent identity, orchestration policies, security guardrails, and usage monitoring. For organizations planning to deploy AI agents at scale, this is a materially different capability from anything in E5 or standalone Copilot.
Microsoft Entra Suite. Microsoft’s identity and access management suite, including Entra ID Governance, Entra Private Access, Entra Internet Access, Entra Verified ID, and Entra Workload ID. Previously available as a separate subscription, Entra Suite is included in E7.
At list prices, buying these four components separately runs approximately $117 per user per month, which puts E7’s $99 at roughly a 15% effective discount on the bundle.
The question is not whether the bundle is mathematically efficient. The question is whether your organization will actively use all four components — at every user tier you assign E7 to.
The Upgrade Decision: E3 → E5 → E7
Before E7 existed, the primary decision was E3 versus E5. That decision had a clear framework: users who need advanced security, compliance, or analytics capabilities justify E5’s premium; users who need productivity apps and basic collaboration justify E3.
E7 adds a second decision layer — but the underlying logic is the same.
E3 users ($39/user/month as of July 1) need Office apps, Teams, Exchange, and SharePoint. They do not need E5 security capabilities, Copilot, Agent 365, or Entra Suite. Assigning E7 to E3-appropriate users represents a $720 per user per year overpayment.
E5 users ($60/user/month as of July 1) need the E5 security and compliance stack — typically IT security, finance, legal, compliance, and executive roles. Whether they also need Copilot, Agent 365, and Entra Suite depends on function and usage profile.
E7 users ($99/user/month) need all of the above plus active Copilot use, planned AI agent deployment, and identity governance capabilities at the level Entra Suite provides. The honest E7 users are a subset of the E5 population — likely 10–30% of most enterprise estates.
The commercial risk is not E7 itself. The risk is assigning E7 broadly because it simplifies the SKU conversation with Microsoft, then paying for capabilities the majority of your organization does not access.
If your Microsoft EA renews in the next twelve months, you need a position on E7 before Microsoft brings it to the table.
Start a Microsoft 365 licensing review: UMS maps your current SKU usage by role and function, quantifies the E7 versus E5 versus E3 split that matches actual deployment, and builds the commercial position before your renewal negotiation opens.
The Cost Math at Scale
The difference between disciplined E7 adoption and blanket E7 adoption is significant at enterprise scale.
Consider a 10,000-user organization currently on a mix of E3 and E5:
- Current blended cost (7,000 E3 at $36 + 3,000 E5 at $57): $25.2M per year
- Blanket E7 (10,000 users at $99): $11.88M per year — this is the number Microsoft will show
- Optimized mix (7,000 E3 at $39 + 2,000 E5 at $60 + 1,000 E7 at $99): $4.9M E3 + $1.44M E5 + $1.19M E7 = $7.53M per year
The blanket E7 proposal saves $13M+ versus current mixed pricing and sounds compelling. The optimized mix saves $17M+ versus current, costs $4.35M less annually than blanket E7, and does not overpay for Copilot and Agent 365 licenses that 90% of users will not actively use in year one.
The optimized math holds even accounting for the July 1 E3 and E5 price increases — because overpaying for E7 broadly still exceeds right-sizing to updated E3/E5 tiers with selective E7 for genuine heavy users.
What “Active Copilot Use” Actually Means
Microsoft’s internal data on Copilot usage shows significant adoption variance by role type. Users who use Copilot daily are typically in drafting-intensive functions: legal, finance, communications, sales, executive support. Users who log in once a quarter and run one prompt are not Copilot users in any meaningful commercial sense.
When you pay $99/user/month for E7, you are paying for Copilot whether or not the user activates it. The question is how many of your users will reach usage levels that justify the Copilot component’s embedded cost.
A practical threshold: if a user group would not have justified purchasing standalone Copilot at $30/month, they do not justify the E7 premium over E5. Assign them to the updated E5 at $60/month instead.
Agent 365: Who Needs It, When
Microsoft Agent 365 is the component of E7 that is most genuinely new. It is infrastructure for managing AI agents — think orchestration policies, agent identity governance, and security controls across automated workflows.
For organizations that are actively deploying AI agents into business processes (finance automation, legal review workflows, IT operations agents, customer service orchestration), Agent 365 is meaningful infrastructure. For organizations that are running Copilot experiments or in early AI adoption phases, it is unused infrastructure that you are paying $99/user/month to carry.
The commercial decision about Agent 365 depends on your AI deployment roadmap for the next 24 months. If you have a defined roadmap for agent deployment, selective E7 adoption at the functional level where agents will be deployed is defensible. If your AI roadmap is still exploratory, you are buying Agent 365 infrastructure you cannot use yet.
How Fiscal Year End Timing Intersects With E7
Microsoft’s fiscal year ends June 30 — two days from today. The E7 announcement in March was well-timed against the fiscal year end renewal cycle.
The combination of the E7 launch, the July 1 price increases on E3 and E5, and the fiscal year end window creates real commercial pressure. Microsoft account teams will be working to include E7 in EA renewals closing before June 30, or framing E7 migration as a next-cycle commitment.
This is a legitimate commercial opportunity and a real risk simultaneously.
The opportunity: June 30 fiscal year end means Microsoft sellers have quota pressure to close volume. Organizations with defined positions can use that pressure to negotiate better pricing on E7 adoption, accelerate EA restructuring, or lock in favorable rates before the July 1 price adjustments compound across the E3/E5 base.
The risk: Microsoft’s account teams are experienced at using complexity and time pressure to close EA upgrades before customers have fully modeled what they are buying. An organization that commits to blanket E7 in a June 30 renewal without a usage-based analysis of who actually needs it has signed a three-year obligation that will be difficult to unwind.
For more on how to use fiscal year end timing strategically, see the Microsoft EA renewal negotiation guide.
Real Numbers: What Right-Sizing Microsoft Licensing Produces
UMS has run Microsoft estate optimization engagements across sectors, sizes, and agreement structures. Three reference points:
New York City. A comprehensive Microsoft licensing review across the city’s enterprise agreements identified $700M in software savings potential, with M365 SKU rationalization and EA restructuring among the largest contributors.
Financial services — SQL Server true-up. A $5.67M SQL Server true-up demand was negotiated down through edition substitution, virtualization rights documentation, and Software Assurance offset. The same analytical discipline that uncovers SQL Server exposure applies to M365 SKU-mix modeling — the exposure is different, but the method is the same.
Enterprise software estate — OpenText. A $170M OpenText licensing review identified significant restructuring opportunity through contract consolidation, module-level entitlement validation, and renewal timing optimization. Multi-publisher estate discipline is the same work as Microsoft estate discipline, applied across vendors.
The pattern is consistent: organizations that enter renewal cycles with a data-based position on what they own, what they use, and what their commercial obligations actually require consistently produce better outcomes than organizations that negotiate from vendor-provided numbers.
Four Mistakes to Avoid on E7
Mistake 1: Treating E7 as the simple “all-in” option
Microsoft will position E7 as the option that eliminates the complexity of managing E3/E5/Copilot/Entra subscriptions separately. That is accurate — it does simplify the SKU structure. But it simplifies at a cost that, for most enterprise estates, is higher than a properly maintained mixed-SKU structure. Simplicity has a price. Know what it is before you pay it.
Mistake 2: Assuming Copilot adoption follows licensing
Buying Copilot for every user does not produce Copilot adoption across the organization. Adoption requires change management, training, and use-case activation that most IT and HR functions have not yet funded or staffed. Organizations that have bought standalone Copilot at $30/month are still working on activation plans. Adding Copilot to 10,000 E7 licenses does not change that deployment curve.
Mistake 3: Skipping the Entra Suite overlap analysis
Many organizations have already purchased components of what is now the Entra Suite separately — Entra ID Governance, Conditional Access, privileged identity management. Before E7, these were available as standalone products or bundled into E5 security add-ons. The Entra Suite in E7 may duplicate coverage you are already paying for. The overlap analysis matters before you commit.
Mistake 4: Negotiating E7 as a renewal add-on instead of a commercial restructure
Microsoft will typically present E7 as an upgrade or add-on to an existing EA. The correct frame for a first E7 discussion is a commercial restructure — rebuild the enrolled quantity from scratch based on actual usage tiers, add E7 only where the usage profile justifies it, and use the restructure as the basis for negotiating total EA value. An add-on conversation starts from Microsoft’s current commercial position. A restructure conversation starts from yours.
What to Do Before July 1
If your Microsoft EA renews in the next twelve months, or if you have received E7 pricing from your Microsoft account team:
1. Pull your Copilot usage data. If you already have Copilot licenses, look at monthly active users versus assigned users. The gap tells you your real Copilot adoption rate before you buy it at scale inside E7.
2. Map your E3/E5 population by function. Which roles are security, compliance, legal, finance, or analytics-heavy enough to justify E5? That same population is the ceiling for E7 candidates. E7 should not exceed your E5 population as a starting principle.
3. Get a position on Agent 365 before Microsoft asks. If you do not have a 24-month AI agent deployment roadmap, Agent 365 is premature infrastructure. If you do, identify which functional areas will deploy agents first — those are your E7 candidates, not the full organization.
4. Model the blended cost at two or three SKU mixes. Take your current user population, apply the July 1 E3 and E5 prices, and model (a) blanket E7, (b) current mix at new prices, and (c) an optimized mix with selective E7. The difference in total annual cost across those three scenarios is the number that should drive your EA conversation.
UMS runs Microsoft 365 licensing reviews, E7 evaluation engagements, and EA renewal negotiations for enterprise organizations. The work includes mapping current SKU usage by function, modeling E7 versus E5 versus E3 assignments based on actual deployment data, and building the commercial position before renewal negotiations open.
For organizations evaluating E7 as part of an upcoming EA renewal, start with the Microsoft 365 optimization review or review the EA renewal service for organizations with a renewal in the next twelve months.
For organizations receiving Microsoft audit or true-up pressure alongside an E7 upgrade conversation, see the Microsoft audit defense service — the audit and the renewal should be run as separate, coordinated tracks.
Source Notes
- Microsoft 365 E7 Enterprise page: Microsoft’s published E7 product page covering included components and $99 list pricing.
- SAMexpert: Microsoft 365 E7 licensing guide: Component-level breakdown of E7 bundle contents and commercial analysis.
- UMS Microsoft 365 optimization service: UMS service page for M365 SKU rationalization and licensing review.
- UMS Microsoft EA renewal service: For organizations with an EA renewal in the next twelve months.
- UMS AI cost optimization service: For organizations evaluating Copilot and Agent 365 spend across the enterprise.