Content reviewed: 12 October 2026

A company has 280 employees and expects 50 more during the year. New starters need entitlements, while existing devices must remain protected. The 300-user boundary affects more than a purchase line: growth can change the suitability of a security product and how the licence mix is managed.

Count the whole Business family

The current Business Premium FAQ sets a combined maximum of 300 provisioned seats across Business Basic, Standard and Premium. Do not calculate headroom from Premium alone. Consult Product Terms for the relevant agreement; this link displays MCA. Apps for business and Teams Essentials have separate limits in the terms, rather than automatically sharing the three-suite total.

With 220 Premium and 60 Standard seats, 20 remain in this family. Adding 50 Premium produces 330. Another supplier or a no-Teams variant does not create fresh headroom for the same organisation. Count purchased/provisioned seats, not only employees active last month.

Enterprise does not require another tenant

Changing plans within the organisation changes entitlements and configuration. It does not itself require moving identities, domains and mail into a second tenant. Microsoft permits subscription combinations. Above 300 users it recommends Enterprise, and individual services have their own limits. Keeping the Business total below 300 alone does not validate the whole design.

Options for planned growth
DesignWhen usefulChecks required
Enterprise for everyoneConsistent administration and long-term growthEndpoint protection, add-ons and commitment transition
Role-based Business and EnterpriseDemonstrably different work requirementsBusiness total, use rights and supported security configuration
Enterprise and eligible Frontline rolesSome people work in qualifying scenariosF eligibility, apps, mail and devices

Do not allocate by hiring order. “The first 300 get Premium; the rest get E3” cannot explain different protection policies. Record services required by each role and verify the exact SKU, including Teams. Microsoft 365 E3 and Office 365 E3 are not interchangeable suites.

Make a separate Defender for Business decision

The Defender for Business FAQ matters for this transition. It does not support mixed licensing; a P2 experience requires coverage for all users and a support-assisted switch. Above 300 it recommends enterprise protection for everyone. A few E3 or E5 licences do not automatically establish a supported split between Defender for Business and Endpoint P2.

Supported Endpoint P1/P2 mixed mode is a different environment. Settings and device tags allocate capabilities. That is not evidence that the same model applies to Defender for Business. Before purchasing an add-on for a subset, confirm the destination environment and transition procedure.

The Defender service description separates P1 prevention from P2 EDR and automated investigation. Do not automatically describe Business Premium → Microsoft 365 E3 as an improvement in every security feature: Defender for Business already has some investigation capabilities. Document the protection standard and how the destination meets it.

A 330-person example without invented savings

A hypothetical company compares 280 Premium + 50 E3 with 330 E3 plus required add-ons. The first allocation stays below 300 Business seats, yet still needs endpoint protection designed for the whole growing organisation. It is not a validated purchasing recommendation.

Inputs for your cost model
ItemMixed designUniform design
Base suites280 × Premium price + 50 × E3 price330 × E3 price
Target protectionCover affected people in a supported environmentAdd capabilities missing from the base suite
Service transitionPilot, possible support and configurationPilot and service verification
Transitional costsRemaining commitments and necessary overlapRemaining commitments and necessary overlap

Use the actual quote, currency, term, billing frequency and applicable tax treatment. Include management of two standards and avoid counting included features twice. A lower base price does not establish a lower total cost. This article assumes no percentage saving.

Verify services before assignment

For device management, review current Intune plans, benefiting users or devices and the advanced capabilities needed. A visible portal option is insufficient. For Windows, assess qualifying OS, local use and virtualisation; applicable rights are in Product Terms.

Exchange limits and the account’s actual quota inform mailbox planning. Check archives, holds and other compliance requirements separately. Do not rely on an old comparison table or assume a higher plan name configures everything immediately. Preserve current service-plan and retention requirements before changing assignments.

Stage the transition in the existing tenant

  1. 01

    Inventory and target roles

    All Business seats, subscriptions, renewals, devices and required services

  2. 02

    Protection decision

    Supported Defender environment, required capabilities and affected-user coverage

  3. 03

    Representative pilot

    Mail, archive, apps, Teams, Windows, access and device management

  4. 04

    Destination before source removal

    Confirm destination licensing and required services before removing the original source

  5. 05

    Commercial and operational verification

    Check orders, overlap, billing, actual capabilities and exceptions after the change

The plan-change guide distinguishes moving everyone from moving a subset; options also depend on billing account type. Handle CSP orders with the partner under the relevant commitment. For group licensing, Microsoft explicitly requires confirming the destination assignment first. Membership alone is insufficient.

Removing an employee’s licence is not subscription cancellation. NCE cancellation rules have a limited window and contractual exceptions. Plan around actual renewals and an available upgrade route. Purchasing E3 does not automatically terminate an old annual commitment.

Frequently asked questions

Do we need another tenant for employee 301?

The licensing limit alone does not require one. Design suitable plans, service rights and configuration in the existing environment.

Can we simply keep 300 Premium and add E3?

Assess the complete design. The Business count is only one check; Defender for Business and other services have their own boundaries and requirements.

Is E3 automatically more secure than Premium?

Not in every capability. Compare the actual protection, particularly Endpoint P1, P2 and Defender for Business, plus any add-ons.

Does unassigning a licence immediately reduce the bill?

Not necessarily. Assignment and commercial commitment are separate. Check the agreement, order, renewal and permitted change.

Audit licence sources and errors with Graph