Content reviewed: 12 October 2026
Putting every employee on one Microsoft 365 plan is simple to administer but may not match the work they do. Start with roles and required services: productivity apps, email, collaboration, device management, identity, security and compliance. Verify exact capabilities in Microsoft's current plan comparison.
Group employees by need
| Role | What to check |
|---|---|
| Office worker | Desktop apps, email, collaboration and account protection. |
| Frontline worker | Shared-device workflow and Frontline plan restrictions. |
| IT or sensitive role | Device management, advanced security and audit needs. |
| Contractor | Actual access pattern and whether an individual licence is required. |
Assess Business and Enterprise together
Business plans have their own eligibility rules. Microsoft says its base Business plans are designed for organisations with up to 300 users, and explains mixing offers in the Business Premium FAQ. Assess Enterprise and Frontline rights per user, rather than using tenant size alone as a shortcut.
Before placing the order
- 01
Map roles
Record headcount, work scenarios and required services.
- 02
Shortlist plans
Compare rights in current documentation and record uncertainties.
- 03
Check add-ons
Do not assume a full plan upgrade is the only option; confirm add-on prerequisites.
- 04
Review renewals
Account for commitments, seat changes and approval ownership.
Separate roles, entitlements and actual use
Start with a role inventory rather than a product catalogue. For each group, record its everyday tasks, the services it must access, the sensitivity of its data, the devices it uses and the likely change in headcount. Two people with the same job title can still need different security or analytics capabilities. Then compare this matrix with exact product SKUs and their service plans. A purchased seat is an entitlement; assignment identifies its recipient; activity reports describe use. These three views answer different questions and should not be treated as interchangeable. The Microsoft 365 subscription view and usage reports provide the starting evidence.
| Question | Evidence | Decision |
|---|---|---|
| What does the role do? | Task and application inventory | Base plan and add-ons |
| What data does it handle? | Security and compliance requirements | Protective capabilities |
| Where and on what device? | Device type and access pattern | User or other entitlement for the actual service |
| How does the team change? | Hiring plan and history | Term and spare capacity |
Make assignment a controlled process
Map approved roles to licensed groups, appoint an owner for each group, and review membership when someone joins, changes role or leaves. Microsoft's group-based licensing guidance explains both the automation and its limits: nested groups are not supported for this purpose, user location matters and assignment errors need attention. Test a group change with a small, representative pilot before applying it broadly, because moving a user between licensed groups can briefly interrupt access if the sequence is wrong. An inactive service does not automatically mean the license is unnecessary; verify exceptional and security-related use with the process owner.
Model commitment separately from technology
The technically appropriate plan still leaves a commercial choice. In New Commerce, subscription term and billing frequency are separate fields: an annual commitment paid in monthly instalments remains annual. Compare the cost over the full term, the risk of unused seats and each renewal date. Keep uncertain pilots and seasonal work separate from stable roles. Partner Center's pricing guidance explains these fields and notes that term availability depends on the particular offer. Before signing, validate the actual SKU and market price rather than assuming that every plan has the same monthly option.
Record the outcome as a decision, not merely as a revised price spreadsheet. For each role, keep the required capability, chosen license, accountable owner, review date and reason for any exception. When Microsoft changes a bundle or a team's work changes, this record lets you return to the original need instead of renewing the same mix by habit. Review assignment errors and spare seats monthly, revisit role definitions quarterly and run a separate review before each renewal. This cadence keeps entitlements and cost under control without indiscriminately removing access from people who need it.
Count people within the security feature’s scope
A hypothetical company has 200 employees and five IT administrators. If an ordinary Conditional Access policy protects all 200, do not count P1 only for the five administrators. Check coverage for everyone affected, including rights already in their suites. The Entra matrix separates ordinary access from risk policies requiring P2. Enabling a portal option does not establish coverage for each user.
| Field | Our working example |
|---|---|
| Feature and scope | Ordinary Conditional Access for 200 people |
| Existing rights | Check each person’s included P1 or higher entitlement |
| Missing coverage | Fill the actual gap; do not count the same person repeatedly |
| Decision evidence | Exact service plan, policy rule, owner and source |
Also compare the three-year offer
Partner Center documents selected three-year Enterprise SKUs for SMC. They have separate SKU IDs and a 100-seat minimum on purchase or conversion; an annual-to-three-year move is an upgrade/conversion. It is not simply a billing switch. Verify the actual offer and commitment for stable roles.
Count Business Basic, Standard and Premium together towards 300 provisioned seats. Growth needs more than a seat total: Defender for Business has separate limits and does not support an ordinary Business/P2 mix. See the growth plan for the transition. For Frontline, verify eligibility and actual apps; a role label alone is insufficient.
Frequently asked questions
Does every employee need the same licence?
Not necessarily. The role and the rights actually needed should drive the choice.
Is seat price enough to compare offers?
No. Include services, add-ons, term and administration.
