Microsoft 365 Apps for Enterprise (formerly Office 365 ProPlus) is the desktop Office suite component of the Microsoft 365 stack. It includes Word, Excel, PowerPoint, Outlook, OneNote, Access, Publisher, and the desktop versions of Teams and OneDrive, licensed for installation on up to five PCs/Macs, five tablets, and five smartphones per user.
For most enterprises on M365 E3 or E5, M365 Apps for Enterprise is already included in the suite licence — there is no additional cost. The commercial problem arises in two specific scenarios: first, when organisations purchase M365 Apps for Enterprise as a standalone licence for users on lighter plans (O365 E1, M365 F3, or Exchange Online Plan) when a cheaper alternative would serve them equally well; and second, when large populations of frontline or task workers are licensed with M365 Apps when they have no business need for full desktop Office applications.
What M365 Apps for Enterprise Includes
The M365 Apps for Enterprise licence provides the following:
Desktop applications (latest version, always current): Word, Excel, PowerPoint, Outlook, OneNote, Access (PC only), Publisher (PC only), Skype for Business (legacy). Each application is subscription-updated — users always run the current version, with updates managed via Microsoft Update or deployment tools (Configuration Manager, Intune).
Five device installations per user: Unlike perpetual Office licences, M365 Apps is licensed per named user for up to five Windows PCs or Macs, five tablets (iPad, Android, Windows), and five smartphones. This device flexibility is the primary commercial justification for subscription versus perpetual.
Microsoft 365 cloud integration: AutoSave to OneDrive/SharePoint, co-authoring in real time, Copilot integration (with M365 Copilot add-on), connected services for translation, research, and accessibility checks.
Deployment and update infrastructure: Click-to-Run deployment, Office Deployment Tool, Intune-managed deployment, update channel control (Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel). For enterprises with update governance requirements, the Semi-Annual Channel provides a predictable update cadence.
M365 Apps for Enterprise vs M365 Apps for Business: The Critical Difference
Many enterprises have mixed populations that could be served by M365 Apps for Business (~£8.25/user/month standalone) rather than Apps for Enterprise (~£10.10/user/month standalone). The differences are narrower than the names imply:
| Feature | M365 Apps for Business | M365 Apps for Enterprise |
|---|---|---|
| Desktop Office apps | Yes | Yes |
| 300-user cap | Yes (max 300 seats) | No cap |
| Group Policy management | Not supported | Full Group Policy support |
| Shared Computer Activation (SCA) | No | Yes |
| Microsoft 365 Admin Center features | Business-tier only | Full enterprise admin controls |
| Volume Activation | No | Yes (KMS/MAK/ADBA) |
| Telemetry and policy controls | Limited | Full policy controls |
The practical difference for enterprise IT: Apps for Business lacks Group Policy management and Shared Computer Activation. Group Policy is essential for enterprises that use GPO to configure Office applications centrally. SCA is essential for organisations using RDS/Azure Virtual Desktop/Windows 365/shared devices. For any enterprise with Group Policy-managed deployments or shared device scenarios, Apps for Enterprise is required. For sub-300-seat organisations with simple deployments, Apps for Business is a legitimate cost-saving option.
M365 Apps for Enterprise vs O365 E3 Suite: Which is the Right Commercial Vehicle?
One of the most common procurement errors: purchasing M365 Apps for Enterprise standalone (~£10.10/user/month list) for users who also need Exchange Online, SharePoint Online, and Teams — when M365 E3 (~£30.10/user/month list) includes all of those services plus Apps for Enterprise in a single licence.
M365 Apps for Enterprise standalone is the right product in a limited set of scenarios:
Users who already have cloud services from another source. If an organisation has Exchange Online Plan 1 or 2 purchased through an older agreement, and needs to add desktop Office without transitioning to a full M365 suite, Apps for Enterprise as an add-on is appropriate. However, the total cost analysis (exchange standalone + Apps for Enterprise) typically approaches M365 E3 in price, at which point suite migration is the better commercial outcome.
Users who genuinely need only Office desktop with no cloud collaboration. In practice, this population has shrunk to near-zero in most enterprises. Even back-office users on limited connectivity need OneDrive sync, SharePoint access, and Teams. A user who genuinely needs only local Office applications with no cloud services is rare enough to warrant a standalone perpetual licence rather than an Apps for Enterprise subscription.
Supplemental licensing for specific compliance scenarios. Some regulated environments use Apps for Enterprise standalone to maintain Office application access on air-gapped or regulated workstations alongside a separate O365 plan for non-regulated collaboration. This is a niche scenario and should be validated against the current M365 compliance architecture.
Before purchasing M365 Apps for Enterprise standalone, run a full total cost comparison against M365 E3. For most users who need any M365 cloud service alongside desktop Office, E3 is either the same price or cheaper — and includes substantially more. The standalone Apps licence exists primarily for specific architectural scenarios, not as a general-purpose Office deployment mechanism.
Shared Computer Activation: Enterprise Requirement You Cannot Ignore
Shared Computer Activation (SCA) is the feature that makes M365 Apps for Enterprise viable for virtualised and shared device deployments. SCA allows multiple users to sign in to Office applications on a single shared machine, with each user's Office activation tied to their identity rather than the device. This is required for:
Azure Virtual Desktop (AVD) and Windows 365 environments where multiple users access Office from a shared virtual machine pool. Without SCA, each virtual machine would consume a device activation, exhausting the five-device limit rapidly in pooled VM architectures.
RDS (Remote Desktop Services) environments with shared session hosts. SCA allows Office to be installed once on the RDS host and activated per user session.
Shared physical workstations in healthcare (nurse stations, pharmacy workstations), manufacturing (production line terminals), and retail (back-of-house shared PCs). SCA ensures each user authenticates with their own credentials and activates Office against their licence rather than the device licence.
M365 Apps for Business does not support SCA. If your organisation uses any form of shared device or virtualised desktop deployment, M365 Apps for Enterprise (or a full E3/E5 suite that includes it) is required. This is a non-negotiable technical requirement that frequently drives Apps for Business → Apps for Enterprise upgrades after the fact, at additional cost.
M365 Apps and Frontline Workers: The Over-Licensing Pattern
The most prevalent M365 Apps over-licensing pattern at enterprise scale is providing M365 Apps for Enterprise (or E3, which includes it) to frontline and task workers whose actual work involves no desktop Office document creation.
Warehouse operatives, retail floor staff, hospitality workers, manufacturing production employees, and field service technicians typically use mobile applications, purpose-built operational tools, or at most browser-based M365 web apps. They do not need a full Word or Excel desktop installation. The M365 F1 and F3 frontline plans are designed for this population: F1 at approximately £2.25/user/month provides browser-based Office web apps (not desktop), Teams, and SharePoint access.
Copilot and M365 Apps for Enterprise
Microsoft 365 Copilot ($30/user/month, or approximately £24.70/user/month) requires Microsoft 365 Apps for Enterprise as a prerequisite. Copilot integrates into Word, Excel, PowerPoint, Outlook, and OneNote via the desktop and web applications — these integrations require the Apps for Enterprise licence base.
This prerequisite is important for two commercial reasons. First, it means Copilot is not available to users on O365 E1 or M365 F1/F3 plans without upgrading to Apps for Enterprise or a full M365 E3/E5 plan. If your Copilot deployment scope overlaps with users on lighter plans, the Copilot business case must include the prerequisite Apps for Enterprise licence cost.
Second, if your Copilot evaluation determines that only a subset of users justify the Copilot investment, only those users need to be licensed with Apps for Enterprise as a prerequisite. Users not in the Copilot scope do not need to be upgraded. This is relevant for organisations maintaining mixed O365/M365 licence stacks — see our M365 Copilot licensing guide for the full prerequisite analysis.
Deployment Governance: The Update Channel Decision
M365 Apps for Enterprise provides four update channels that affect how quickly users receive feature updates and security patches. The update channel decision is both a technical and commercial consideration — non-current channels create security debt that compliance teams increasingly flag.
Current Channel delivers new features as soon as they are available, with security updates released as needed. Appropriate for users who want the latest features and can tolerate frequent small changes. Default for most consumer-oriented organisations.
Monthly Enterprise Channel delivers one feature update per month on a predictable schedule, with security updates on Patch Tuesday. Appropriate for most enterprises — provides predictability for IT operations while maintaining monthly currency. This is the most common enterprise deployment choice.
Semi-Annual Enterprise Channel delivers feature updates twice yearly (January and July), with security updates on Patch Tuesday. Appropriate for highly regulated environments where application change validation is required before deployment. Acceptable for security teams with formal change management programmes. Carries the risk of falling behind on features, particularly AI/Copilot features which are frequently delivered via Current or Monthly channels first.
Microsoft's current position: Extended Support for any given Semi-Annual Channel release is 14 months from the release date. This means organisations on Semi-Annual Channel are always within 14 months of their current version becoming unsupported — a tighter lifecycle than many IT teams realise. For organisations with strict compliance requirements, the Semi-Annual Channel provides predictability at the cost of a compressed support window compared to perpetual Office versions.
Negotiating M365 Apps for Enterprise in Your EA
Apps for Enterprise is rarely negotiated explicitly in EA renewals — it is either included in the suite licence or added as a standalone with the suite's overall discount applied. The negotiation leverage points are primarily upstream: they are in the M365 E3/E5 suite decision and the licence mix between E3, F3, and standalone Apps.
The frontline displacement exercise. Before your EA renewal, run a proper workforce classification exercise. Identify every user receiving E3 (which includes Apps for Enterprise) and classify whether they actually use desktop Office applications. Users classified as frontline or task workers (no document creation, primarily mobile or browser-based workflows) can be migrated to F1 or F3, displacing the E3 licence and its embedded Apps for Enterprise. At scale, this is the highest-ROI exercise in a Microsoft licence optimisation programme. See the M365 licence harvesting guide for the full methodology.
Standalone Apps vs E3 total cost comparison. If any of your users are on a standalone Apps for Enterprise licence plus separate cloud services, model the E3 transition. In the majority of cases, E3 is either cheaper or the same cost, and includes services the standalone Apps users are actually using via separate licences. Consolidating to E3 simplifies the estate and typically reduces total cost.
Volume and mix leverage. During EA negotiations, your Apps-included user count (E3/E5 seats) contributes to your overall Microsoft 365 volume tier. A decision to migrate frontline workers from E3 to F1 reduces your E3 seat count — potentially dropping you to a lower discount tier if your E3 count crosses a volume threshold boundary. Model this interaction before finalising your frontline migration scope to ensure the unit price impact does not offset the volume reduction savings. Our EA negotiation complete guide covers volume tier mechanics in detail.
Frequently Asked Questions
Is M365 Apps for Enterprise included in M365 E3?
Yes. M365 E3, M365 E5, O365 E3, and O365 E5 all include Microsoft 365 Apps for Enterprise. If your users are on any of these plans, you do not need a separate Apps for Enterprise licence. Users on O365 E1, M365 F1, M365 F3, Exchange Online Plan 1/2, or SharePoint Online Plan 1/2 do not receive Apps for Enterprise and would need the standalone add-on or a plan upgrade to access desktop Office.
What is the difference between M365 Apps for Enterprise and Office 2024 perpetual?
M365 Apps for Enterprise is a subscription that provides always-current Office applications with cloud features (co-authoring, AutoSave, Copilot integration). Office 2024 is a perpetual licence for a specific version of the Office applications with no feature updates after launch and a fixed support lifecycle (mainstream support to 2029). For enterprises with EA or M365 subscriptions, the perpetual option has diminishing relevance — the ongoing update and cloud integration value of Apps for Enterprise outweighs the perpetual cost argument at subscription scale. See our Software Assurance guide for the perpetual vs subscription analysis.
Can I deploy M365 Apps for Enterprise offline on air-gapped systems?
Yes. Apps for Enterprise can be deployed to machines without internet connectivity using the Office Deployment Tool and an on-premises file share as an update source. The licence activation requires network access to Microsoft activation servers periodically (every 30 days for standard activation, with grace periods). For fully air-gapped deployments without any internet connectivity, volume activation using KMS or MAK is the supported mechanism — this requires the Volume Activation Management Tool (VAMT) and a KMS host on the local network.
How does M365 Apps for Enterprise handle shared devices in shift-working environments?
Shared Computer Activation (SCA) is the mechanism for shared device deployments. Each user who logs into a shared device must have an Apps for Enterprise licence (standalone or via E3/E5). The SCA mechanism activates Office against the user's identity rather than the device, allowing multiple licensed users to share a single physical machine. For shift-working environments, each worker who uses Office applications during their shift must be individually licensed — there is no "concurrent user" or "shift-based" licensing model.
Where does M365 Apps fit in a broader M365 licence review?
M365 Apps for Enterprise is a component of the broader M365 licensing strategy. The decision to deploy E3 vs standalone Apps, and to right-size the frontline vs knowledge worker split, directly affects your overall Microsoft spend. For organisations with 1,000+ users, the Apps-related decisions typically represent £200,000–£500,000 in three-year EA savings opportunities when approached with rigour. Contact our advisory team for an independent assessment before your next EA renewal.