Editorial photograph of a Microsoft 365 Apps standalone licensing review with the SKU ladder on the boardroom table
Article · Microsoft · M365 Apps

Microsoft 365 Apps. The standalone reading.

Microsoft 365 Apps for Enterprise is the standalone Office productivity SKU. The standalone option beats the full E3 bundle on selected user populations. The buyer side moves decide whether the saving holds at renewal.

Read the Briefing Microsoft Hub
$8.25M365 Apps per user per month
28%Median saving captured
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

What this article delivers

  • M365 Apps for Enterprise is the standalone Office productivity SKU. Covers the desktop apps, mobile apps, and basic OneDrive storage without the full E3 services.
  • Six user populations fit the standalone SKU better than the full E3 bundle. Frontline shared workers, third party contractors, M and A in flight users, kiosk users, BYOD personal devices, and legal hold populations.
  • List price runs $8.25 per user per month. E3 list price runs $23.00 per user per month. The standalone gap funds the saving on the right population.
  • Four traps cluster around the renewal cycle. Identity coverage drift, security baseline mismatch, the Teams Phone overlap, and the Microsoft Copilot eligibility cap.
  • The buyer side moves run at the EA renewal cycle. Population segmentation, SKU mix optimisation, identity coverage check, and the documented Google Workspace alternative.
  • Median saving captured runs 28 percent. The band depends on the population mix and the Microsoft EA renewal cycle position.
  • Vendor Shield runs the SKU mix review across the term. The subscription holds the population segmentation clean and runs the mix review each quarter.

Microsoft 365 Apps for Enterprise is the standalone Office productivity SKU that covers the desktop and mobile Office apps with basic OneDrive storage. The SKU sits below E3 in the Microsoft license ladder. For selected user populations the standalone option beats the full bundle by 60 percent on per user license cost across the term.

Across 35 Microsoft EA engagements where the SKU mix was reviewed, median saving captured against the all E3 baseline ran 28 percent. The lowest saving was 6 percent on a deployment where the customer needed full Teams and Exchange across every population. The highest was 48 percent on a deployment with a large frontline and contractor population.

What is M365 Apps standalone

Microsoft 365 Apps for Enterprise is the standalone version of the Office productivity suite. The SKU covers Word, Excel, PowerPoint, Outlook, OneNote, Access, Publisher on desktop, plus the mobile and tablet apps. The SKU includes 1TB of OneDrive storage per user.

What it includes

Desktop apps for Windows and Mac. Mobile apps for iOS and Android. OneDrive for Business at 1TB per user. Office for the Web. Volume activation through shared computer activation for VDI.

What it excludes

Exchange Online, SharePoint Online, Teams chat, Teams meetings, Teams Phone, Power BI Pro, Defender for Endpoint, Intune, Entra ID Premium, the full security and compliance stack.

The price point

List price runs $8.25 per user per month under an Enterprise Agreement. The price compares to E1 at $10.00, E3 at $23.00, and E5 at $38.00. The standalone gap funds the saving on the right population.

  • Desktop and mobile Office apps. Word, Excel, PowerPoint, Outlook, OneNote across all platforms.
  • 1TB OneDrive storage. Per user storage allowance.
  • Office for the Web. Browser based Office editing.
  • Shared computer activation. For VDI and shared device populations.
  • No Exchange or SharePoint. Email and document management not included.
  • No Teams chat or meetings. Teams services require an E3 or higher SKU.

Standalone versus E3 and E5

The SKU ladder runs from F1 frontline through M365 Apps standalone, E1, E3, E5. Each tier adds a service layer. The customer that runs every population on E3 pays for services that some populations never use. The standalone SKU sits at the productivity only layer.

M365 Apps versus E3

M365 Apps standalone runs at $8.25. E3 runs at $23.00. The $14.75 monthly gap covers Exchange, SharePoint, Teams chat and meetings, Defender for Office, Intune, Entra ID Premium P1, and Power Apps for Microsoft 365.

M365 Apps versus E5

E5 adds Defender for Endpoint Plan 2, Defender for Identity, Defender for Cloud Apps, Power BI Pro, Audio Conferencing, Phone System, and the full security and compliance stack on top of E3.

F1 and F3 frontline tier

F1 runs at $2.25 and covers limited Teams chat and basic Outlook on the web. F3 runs at $8.00 and adds the web versions of Office. F3 sits parallel to M365 Apps standalone for frontline workers who need device shared Office.

SKUList priceOffice appsExchange and SharePointTeamsSecurity
F1$2.25Web onlyLimitedChat and basic meetingsBasic
F3$8.00Web and mobileLimitedStandard meetingsBasic
M365 Apps$8.25Full desktop and mobileNoneNoneNone
E1$10.00Web onlyFullStandard meetingsBasic
E3$23.00Full desktop and mobileFullStandard meetingsDefender Office plus Intune plus Entra P1
E5$38.00Full desktop and mobileFullFull plus Phone and AudioFull Defender stack

Six standalone use cases

Six user populations fit the standalone SKU better than the full E3 bundle. Each population either does not consume the E3 services or consumes them through a parallel system. The buyer side review runs the population segmentation against each use case.

Use case one. Frontline shared workers on full Office

Frontline workers on shared devices who need full desktop Office but do not need Exchange Online or Teams. The shared computer activation feature lets the SKU run on a kiosk.

Use case two. Third party contractors with own identity

Contractors with their own corporate identity that already covers email and collaboration. The customer provides Office for project work without provisioning a full E3 inbox.

Use case three. M and A in flight users

Acquired entity users running on the legacy email and collaboration stack during the integration. The customer provisions Office for the inflight period without paying for E3 services that sit on the legacy stack.

Use case four. Kiosk and meeting room scenarios

Shared device populations such as meeting rooms, manufacturing floor terminals, and lab workstations. The shared computer activation feature licenses the device, not the per user E3 services.

Use case five. BYOD personal devices

Personal devices used for limited corporate work. The Office apps run on the personal device without provisioning a full E3 inbox that the user cannot read on the same device.

Use case six. Legal hold and read only populations

Populations under legal hold who need read only access to historical Office files without provisioning new email or collaboration services.

  • Frontline shared workers. Full Office desktop on shared device through shared computer activation.
  • Third party contractors. Office without provisioning a full E3 inbox.
  • M and A inflight users. Office during the integration period.
  • Kiosk and meeting room scenarios. Shared device Office through shared activation.
  • BYOD personal devices. Office on personal device without full E3.
  • Legal hold and read only populations. Read only Office without new email services.

The TCO math

The total cost of ownership math runs the per user license cost across the population over the EA term. The standalone SKU saves $14.75 per user per month against E3. For a population of 2,000 users across a three year EA the saving runs $1,062,000.

Three year saving on 2,000 user population

Per user gap of $14.75 per month across 2,000 users across 36 months. The saving lands at $1,062,000 on a population that does not consume the E3 services.

Five year saving on 5,000 user population

Per user gap of $14.75 per month across 5,000 users across 60 months. The saving lands at $4,425,000 on a population that does not consume the E3 services.

Mixed population math

Most enterprises mix populations. The buyer side review segments the user base, applies the standalone SKU to the populations that fit, and holds E3 on the populations that consume the services.

  1. Segment the user population. Identify the populations that fit the six use cases.
  2. Build the SKU mix model. Map the populations to the SKUs across the EA term.
  3. Run the TCO math. Apply the per user gap across the population and the term.
  4. Negotiate the SKU mix into the EA. Lock the mix at the renewal table.

Four standalone traps

Four traps cluster around the M365 Apps standalone SKU. The customer that runs the standalone SKU without buyer side review carries the traps across the EA term. The cleanup motion picks up 5 to 15 percent of the saving leakage.

Trap one. Identity coverage drift

Users provisioned on M365 Apps standalone need a separate identity service. Customers that drift the standalone population onto Entra ID Premium for security pay the Entra Premium cost twice if the population then moves to E3.

Trap two. Security baseline mismatch

M365 Apps standalone does not include Defender for Office or Defender for Endpoint. Customers with a uniform security baseline policy need to license the security stack separately on the standalone population.

Trap three. Teams Phone overlap

Customers that license Teams Phone separately on M365 Apps standalone populations pay for two phone systems if the population then moves to E5 or to a Teams Phone bundle later in the term.

Trap four. Microsoft Copilot eligibility cap

Microsoft Copilot for Microsoft 365 requires a Microsoft 365 Apps for Business, M365 Apps for Enterprise, E3, or E5 prerequisite. M365 Apps standalone qualifies, but the Copilot license adds the full Copilot price on top of the standalone band.

Buyer side moves

The buyer side moves run inside the EA renewal cycle. Each move targets the SKU mix, the population segmentation, or the renewal cap clause. The moves run inside the 90 day negotiation window before the EA renewal.

Move one. Population segmentation

Buyer side segmentation of the user base into the six use cases plus the full E3 population. The segmentation runs against Entra ID directory data and the service consumption record.

Move two. SKU mix optimisation

Apply the standalone SKU to the populations that fit. Hold E3 on the populations that consume Exchange, Teams, and the Defender stack. Apply E5 only on the populations that consume the full security and compliance services.

Move three. Identity coverage check

Confirm every standalone population has identity coverage. The standalone SKU does not include Entra ID Premium. The customer that needs conditional access or multi factor authentication on the population licenses Entra Premium separately.

Move four. Renewal cap and SKU mix lock

Lock the SKU mix into the EA at signature. The renewal cap clause holds the per SKU price at 0 to 3 percent uplift across the renewal.

  • Population segmentation. Six use cases plus full E3 population identified.
  • SKU mix optimisation. Standalone, E3, and E5 applied per population.
  • Identity coverage check. Entra ID Premium licensed where needed.
  • Renewal cap and SKU mix lock. Per SKU price locked across the EA term.
Microsoft EA SKU mix review with the population segmentation and the TCO math on the boardroom table
The population segmentation runs against directory data and service consumption record. The output is the SKU mix model across the EA term.

What to do next

The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.

  1. Pull the current EA enrolment. Identify every SKU and every population.
  2. Run the directory analysis. Map every user to a population segment.
  3. Build the SKU mix model. Apply the six use cases against the population segments.
  4. Run the TCO math. Per user gap across the population and the EA term.
  5. Document the Google Workspace alternative. Pilot, architectural review, or signed proposal.
  6. Insert the SKU mix lock into the EA. Lock per SKU price across the term.
  7. Cap the renewal escalator. 0 to 3 percent uplift at the next renewal.
  8. Run the engagement through Vendor Shield. Independent buyer side review at every gate.

Frequently asked questions

What is Microsoft 365 Apps for Enterprise?

Microsoft 365 Apps for Enterprise is the standalone Office productivity SKU under the Microsoft Enterprise Agreement. The SKU covers the desktop apps for Windows and Mac, the mobile apps for iOS and Android, Office for the Web, and 1TB of OneDrive for Business per user. The SKU excludes Exchange Online, SharePoint Online, Teams services, and the Defender security stack.

What does M365 Apps standalone cost?

Under an Enterprise Agreement the list price runs $8.25 per user per month. The price compares to E1 at $10.00, E3 at $23.00, and E5 at $38.00. The standalone gap funds the saving on populations that do not consume the E3 services. Discount bands of 6 to 12 percent off list are typical inside the EA renewal cycle.

Which populations fit the standalone SKU?

Six user populations fit the standalone SKU better than the full E3 bundle. Frontline shared workers on full Office, third party contractors with their own corporate identity, M and A inflight users, kiosk and meeting room scenarios, BYOD personal devices, and legal hold or read only populations. The buyer side segmentation runs against directory data and service consumption record.

Does M365 Apps standalone include Teams?

No. The standalone SKU does not include Teams chat, Teams meetings, or Teams Phone. Customers that need Teams on the standalone population either move the population to E3 or license Teams Essentials separately. The decision depends on the population size and the Teams feature need.

Can M365 Apps standalone users use Microsoft Copilot?

Yes. M365 Apps standalone qualifies for Microsoft Copilot for Microsoft 365 at $30 per user per month. The combined cost runs $38.25 per user per month.

That sits below the E3 plus Copilot bundle at $23.00 plus $30.00, totalling $53.00 per user per month. Standalone plus Copilot is the cheaper Copilot path when the population does not need full E3 services.

How does shared computer activation work?

Shared computer activation lets multiple users sign in to the same device with their own Office licenses. The feature licenses the device, not the per user E3 services. The feature fits kiosk, meeting room, manufacturing floor, and shared workstation scenarios where multiple users share the same hardware.

How does the standalone SKU affect the EA discount band?

The EA discount band runs against the total committed value. Customers that hold the EA value through a mixed SKU strategy keep the discount band. Customers that drop the EA value through standalone substitution risk a discount band reduction. The buyer side move keeps the EA value flat while shifting the per user SKU mix.

How does Redress engage on Microsoft 365 Apps SKU mix?

Redress runs the buyer side EA SKU mix engagement inside the Vendor Shield subscription and the Renewal Program. The work includes the population segmentation, the SKU mix optimisation, the identity coverage check, the renewal cap clause, the SKU mix lock, and the documented Google Workspace alternative. Engagements typically save 15 to 35 percent against the all E3 baseline.

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Microsoft service line, and the Software Spend Assessment.

Read the related Microsoft EA Renewal Playbook, the Microsoft Knowledge Hub, the Microsoft services overview, the benchmarking service, and the Benchmark Program.

Model the exposure for your specific environment with the Microsoft 365 license optimizer.
Open the Calculator →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

The companion playbook covers Microsoft Enterprise Agreement renewal timing, the Q4 motion, true up moves, and the buyer side discount bands that hold across the term.

Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.

Microsoft EA Renewal Playbook

Open the playbook in your browser. Corporate email only.

Open the Paper →
$8.25
M365 Apps band
28%
Median saving
6
Standalone use cases
4
SKU traps
35
EA mix engagements

The standalone SKU is not a downgrade. The SKU is a population fit. Apply standalone where the population does not consume E3 services, hold E3 where the population does, and the saving compounds across the EA term.

Buyer side Microsoft EA SKU mix reviewer
35 Microsoft EA SKU mix engagements
More Reading

More from this practice.

Microsoft Hub →
Microsoft EA Renewal Playbook
Microsoft · EA
Microsoft EA Renewal Playbook
The full EA renewal cycle decoded.
16 min read
Microsoft Knowledge Hub
Microsoft · Hub
Microsoft Knowledge Hub
All Microsoft research in one place.
7 min read
Microsoft Advisory Services
Microsoft · Services
Microsoft Advisory Services
Buyer side advisory across Microsoft.
9 min read
Copilot versus Gemini versus Amazon Q
Microsoft · Copilot
Copilot versus Gemini versus Amazon Q
Procurement analysis across AI assistants.
14 min read
Webex Calling versus Teams Phone
Microsoft · Teams
Webex Calling versus Teams Phone
The phone system decision math.
12 min read
Editorial photograph of a Microsoft EA SKU mix review with the CIO, CFO, and procurement around the boardroom table

Optimize the M365 SKU mix. Hold the renewal price.

35 Microsoft EA SKU mix engagements with median 28 percent saving against the all E3 baseline. Every engagement starts with one conversation.

Buyer side intelligence, monthly.

Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.