Choosing a Microsoft 365 License: Business Premium, E3 and E5 Compared

Choosing a Microsoft 365 license: component differences between Business Premium, E3, E5 and F3, a role-based mixed licensing example and finding wasted licenses with Graph PowerShell.
Technical summary
Technology
Microsoft 365 Business Premium, Microsoft 365 E3/E5, F1/F3, Entra ID P1/P2, Intune, Microsoft Graph PowerShell
Topic
Choosing Microsoft 365 licenses by feature need and building a license inventory
Level
Beginner–intermediate
Prerequisites
  • Access to the Microsoft 365 admin center
  • Microsoft Graph PowerShell module
In this article8 sections

In most organizations, the Microsoft 365 license is chosen by looking at the price list; missing features come to light when an Autopilot or conditional access project starts and are closed with an expensive upgrade. The right order is the reverse: first write down which management, security and compliance components you really need, then meet that need with the fewest different licenses. Below we compare Business Premium, E3, E5 and the Frontline plans at component level and give a role-based mixed licensing example and a method for reporting current license usage.

Questions that drive the license decision

Before looking at plan names, write down the answers to the following questions, taking your existing systems infrastructure into account. Each answer maps to a specific license component.

  • User count: Will total users and growth over the next two to three years exceed 300?
  • Desktop Office: Do users need the desktop versions of Word, Excel and Outlook, or are the web and mobile versions enough?
  • Device management: Will Windows and mobile devices be managed with Intune, and will Autopilot be used for setup?
  • Identity protection: Is conditional access enough, or are risk-based policies and privileged identity management (PIM) also needed?
  • Endpoint security: Is there an existing EDR solution, or will the Microsoft Defender family do the job?
  • Compliance and logging: Are there requirements such as advanced eDiscovery, long-term audit logs, automatic sensitivity labeling or insider risk management?
  • Telephony: Is replacing the phone system with Teams Phone planned?
  • Non-desk employees: Do you have staff working in the field, in production or in shifts who use shared devices?

If this list is left blank, the license decision is made by the sales quote.

The boundaries between Business and Enterprise plans

The Business family (Basic, Standard, Premium) is designed for small and medium organizations, with a purchase limit of 300 licenses. Confirm with your purchasing channel how the limit is applied per plan. The Enterprise family (E3, E5) has no user limit.

  • Business Basic: Exchange Online, Teams, SharePoint and OneDrive; only the web and mobile versions of the Office apps.
  • Business Standard: Basic plus the Microsoft 365 Apps for business desktop apps.
  • Business Premium: Standard plus Intune Plan 1, Entra ID P1, Defender for Business, Defender for Office 365 Plan 1, Purview Information Protection and Exchange Online Archiving.
  • Microsoft 365 E3: Microsoft 365 Apps for enterprise, Exchange Online Plan 2, Entra ID P1, Intune Plan 1, Defender for Endpoint Plan 1 and Windows Enterprise E3 rights. Microsoft’s 2026 plan update added Defender for Office 365 Plan 1, Intune Remote Help, Intune Advanced Analytics and Intune Plan 2.
  • Microsoft 365 E5: E3 plus Entra ID P2, the higher plans of the Defender XDR family, Purview’s advanced compliance components, Teams Phone and Power BI Pro. The 2026 plan update added Security Copilot, Intune Endpoint Privilege Management, Cloud PKI and Enterprise Application Management.

Two names that are often confused: Office 365 E3 and Microsoft 365 E3. They are not the same. Office 365 E3 doesn’t include Intune, Entra ID P1 or Windows Enterprise rights. If device management is planned, Office 365 E3 alone isn’t enough.

Component comparison table: Intune, Entra ID, Defender, Purview

Component Business Premium M365 E3 M365 E5
Mailbox 100 GB + archive (up from 50 GB with the 2026 plan update) 100 GB + archive 100 GB + archive
Intune Plan 1 Plan 1 Plan 1
Entra ID P1 P1 P2
Endpoint protection Defender for Business Defender for Endpoint P1 Defender for Endpoint P2
Email protection Defender for Office 365 P1 Defender for Office 365 P1 (added with the 2026 plan update) Defender for Office 365 P2
Identity threat detection None None Defender for Identity
Purview Information Protection Basic DLP and labeling Advanced eDiscovery, audit and automatic labeling

Two practical conclusions follow from the table. First: for an organization under 300 users, Business Premium includes Defender for Business with EDR capabilities, while E3 includes Defender for Endpoint Plan 1. After the 2026 plan update, Defender for Office 365 Plan 1 is in both plans. Second: the real reason for moving from E3 to E5 is usually Entra ID P2 (risk-based conditional access, PIM), Defender for Identity and Purview’s advanced components. How to configure these components is the subject of our Microsoft 365 security checklist guide. The license only opens the door. Configuration is a separate job.

F1 and F3 for frontline workers

Frontline plans are designed for staff who work in shifts, in the field or in production and mostly use shared or mobile devices. Use of these licenses depends on Microsoft’s definition of a frontline worker and the product terms; confirm eligibility before buying.

  • Microsoft 365 F1: Teams, SharePoint and limited OneDrive access. No mailbox and no editing rights in the Office apps. Suitable for announcements, shifts and internal communication.
  • Microsoft 365 F3: F1 plus a limited-size (kiosk) mailbox and editing in the Office web and mobile apps. No desktop Office apps. Shared devices can be managed thanks to the Intune and Entra ID P1 components.

Staff who share a terminal across shifts on the production floor can be managed with F3; the planning engineer on the same site, however, should get Business Premium or E3 because of the need for desktop Excel and a full mailbox. This split is the most direct way to lower total license cost without losing features.

A role-based mixed licensing example

The table below is an example split for a manufacturing company with 180 users; the figures are a worked example and don’t belong to a real organization.

Role group People Licensing Reason
Management and finance 20 Business Premium + Entra ID P2 add-on Privileged access, risk-based policy
Office staff 70 Business Premium Desktop Office, Intune, Defender
Production and warehouse 85 Microsoft 365 F3 Shared device, web/mobile apps
IT administrators 5 Business Premium + Entra ID P2 add-on Just-in-time access with PIM

In this model, features are added with add-ons only for the users who need them, without moving to E5. Organizations on E3 can also add security or compliance components with the Microsoft 365 E5 Security or E5 Compliance add-ons without changing plans. The add-on strategy has a limit: buying a feature as an add-on for most users can cost more than the higher plan overall. Compare with current prices, not estimates.

Manage license assignment with group-based licensing. This feature requires Entra ID P1, which Business Premium and E3 include. If role groups are synced from on-premises AD, license assignment happens automatically when people join and leave. In tenants where licenses are assigned to users by hand, after a year nobody knows who has what and why. For sync design, see our Entra Connect Sync versus Cloud Sync comparison.

Reporting current license usage

Before the renewal period, measure whether current licenses are really being used. With Microsoft Graph PowerShell, the subscriptions in the tenant and per-user assignments can be pulled like this:

Connect-MgGraph -Scopes "Organization.Read.All","User.Read.All","AuditLog.Read.All"

# Subscriptions: purchased and consumed units
Get-MgSubscribedSku |
  Select-Object SkuPartNumber, ConsumedUnits,
    @{n='Purchased'; e={$_.PrepaidUnits.Enabled}}

# Map SKU IDs to readable names
$sku = @{}
Get-MgSubscribedSku | ForEach-Object { $sku[$_.SkuId] = $_.SkuPartNumber }

# Licensed users, account status and last sign-in
Get-MgUser -All -Property DisplayName,UserPrincipalName,AccountEnabled,AssignedLicenses,SignInActivity |
  Where-Object { $_.AssignedLicenses.Count -gt 0 } |
  Select-Object DisplayName, UserPrincipalName, AccountEnabled,
    @{n='LastSignIn'; e={$_.SignInActivity.LastSignInDateTime}},
    @{n='Licenses'; e={($_.AssignedLicenses.SkuId | ForEach-Object { $sku[$_] }) -join ';'}} |
  Export-Csv C:\Report\license-inventory.csv -NoTypeInformation -Encoding UTF8

The SignInActivity property requires Entra ID P1, and reading it requires the AuditLog.Read.All permission. SKU names are technical abbreviations: SPB is Business Premium, SPE_E3 is Microsoft 365 E3 and ENTERPRISEPACK is Office 365 E3; O365_BUSINESS_PREMIUM, despite its name, corresponds to Business Standard. For an exact mapping, use Microsoft’s product names and service plan identifiers for licensing table.

In the report, look at these rows first: disabled accounts still holding licenses, users who haven’t signed in for 60–90 days, overlapping licenses on the same user (for example both Business Standard and Business Premium) and leavers’ accounts that could be converted to shared mailboxes. Wasted licenses are usually in these four rows.

Common licensing mistakes

  • Mistaking Office 365 E3 for Microsoft 365 E3: Intune and Entra ID P1 are missing; Autopilot and conditional access projects stall because of licensing.
  • Buying the same plan for everyone: Assigning licenses with desktop Office to frontline staff means paying for rights that aren’t used.
  • Deleting a leaver’s license right away: When the license is removed, mailbox and OneDrive data is deleted at the end of the retention period. First hand over data ownership, convert to a shared mailbox or apply a retention policy.
  • Not comparing add-ons with the higher plan: If add-ons are bought for most users, the higher plan may be more economical.
  • Mistaking a license for configuration: Buying Business Premium doesn’t protect devices; Intune, Defender and conditional access policies have to be designed and applied separately. An assigned license is a feature that hasn’t been turned on.

Once the license split is clear, continue with our Windows Autopilot guide for device setup and our article on continuity in Microsoft 365 and cloud infrastructure for a service continuity plan. For building a license inventory and preparing a role-based model, see our IT consulting and Microsoft 365 services pages.

Frequently asked questions

Can Business Premium and E3 licenses be used together in the same tenant?

Yes. Business, Enterprise and Frontline licenses can coexist in a tenant and are assigned per user. Policies must take license differences into account; for example, a risk-based policy that requires Entra ID P2 can only be applied to users with a P2 license.

Does a shared mailbox need a license?

A shared mailbox doesn’t need a license if it doesn’t exceed 50 GB and doesn’t require features such as archiving or litigation hold. If one of these limits is exceeded, Exchange Online Plan 2 or a suitable add-on is assigned. Signing in directly to a shared mailbox is not recommended.

When is it necessary to move from Business Premium to E3?

A move is worth considering if the user count is approaching the Business plans’ 300-license limit, or if you need components tied to the Enterprise family, such as 100 GB primary mailboxes or the E5 Security and E5 Compliance add-ons. A security need on its own is often met with add-ons.

Where should I confirm license prices?

Prices vary by country, currency, commitment term and purchasing channel (direct, CSP, enterprise agreement). Get current list prices from Microsoft’s official Microsoft 365 plan comparison pages and your specific price from your purchasing channel.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles