Microsoft 365 / How to Choose Business Basic, Standard, or Premium for Your Organization

When choosing the Microsoft 365 license your organization needs, base the decision on the user’s work and required features rather than the product name. First, determine whether users will only use web apps, require desktop Office apps, and need device management and advanced security. Even within the same organization, different users can be assigned different licenses.

Four things to check before purchasing

  • Number and type of users: Distinguish full-time employees, field workers, users of shared devices, and external collaborators. Avoid having multiple people use a shared account to cover one license.
  • App usage method: Check whether browser and mobile apps are sufficient, or if desktop apps installed on Windows or Mac are needed.
  • Service: Check whether company email, Teams, OneDrive, and SharePoint are actually needed. Depending on the region and time of purchase, inclusion of Teams may vary.
  • Security & Device Management: Check whether features such as conditional access, Intune, and endpoint protection are needed. Security products with similar names may also have different coverage.

Licenses are rights bundled per product. The right to use services and the authority to manage the tenant are separate. Check which features are included by comparing the Microsoft 365 and Office 365 plan service descriptions with the product names in the actual quote just before purchase.

Choosing Business Basic, Standard, or Premium

Key requirements Plans to review first Points to check
Focus on web/mobile productivity apps and cloud services Business Basic May not be suitable for roles that require the right to install desktop apps.
Desktop Office apps are also required. Business Standard Check security and device management requirements separately.
Need device management and enhanced security in addition to desktop apps. Business Premium Check whether the product includes the required features and whether additional licenses are needed.
Need to exceed the seat limit of Business plans or require enterprise features. Review Enterprise series. Compare the detailed services of E3 and E5 and purchase conditions by region.

This table is a starting point and not a guarantee of functionality. Check the current sales configuration and whether Teams is included in Microsoft’s Business plan comparison. Microsoft explains seat limits for the Business plans in Business Premium FAQ. You should also check the terms based on purchase channels and contract types.

For the per-user basic plan in the Business series, you need to consider the total seat limit of 300 per organization. Even if you mix Basic, Standard, and Premium, you cannot assume that each product can separately secure 300 seats. For example, if you have 250 seats of Business Premium, the additional seats that can be considered in the Business series is a total of 50 seats. This is a condition stated in Microsoft’s above FAQ, and if your organization exceeds this range, also review the Enterprise plan.

Office 365 E3 and Microsoft 365 E3 are not the same product. On the quotation, do not just compare names like “E3” – check the full product name and included services. Having a menu open in a specific admin center and having licenses to apply that function to all users are separate issues.

Example: choosing plans for a 35-person organization

The following hypothetical example illustrates the selection process. Assume that out of 35 employees, 10 use mail and documents in a browser, 20 need desktop Excel and Word, and 5 handle sensitive materials on company laptops from outside.

User Types Candidates for Initial Review Checks Needed for Final Decision
10 Web-Focused Users Business Basic Can they handle actual document formats and work functions in a browser?
20 Users Needing Installed Apps Business Standard Are device management or conditional access also required according to company policy?
5 Managed Laptop Users Business Premium Are the required security features covered and is the operations staff prepared?

This combination is the starting point for the quote. To apply the company's access policy to all 35 people, you should not assume that the licensing requirements of that policy can be met with just 5 people. Conversely, you should not assume that all users need the same security features just because they require the desktop app. Check the rights based on the recipients of the feature rather than the number of people.

Actual sequence for narrowing down license candidates

  1. Create user groups based on roles. For example, office workers may need the desktop app and email, field workers may need mobile access, and users of managed laptops may require device management.
  2. Separate essential features from optional features for each group. Do not include features you currently do not use without reason, and record the implementation schedule and the responsible operators.
  3. Compare the features and limitations in the service descriptions of candidate plans. Especially check storage capacity, email functionality, security features, and whether Teams is included in the exact product SKU (stock-keeping unit) being quoted.
  4. After calculating the expected number of users and any spare licenses you need, compare purchase methods, monthly/annual commitments, taxes, and renewal conditions. Prices vary by region, currency, and timing, so compare quotes under the same currency, tax conditions, and commitment period.
  5. Assign to a small number of users first to check whether app activation, email, file sharing, and required security policies actually work.

Product and contract checks before purchase

  • Accurate sales configuration: Note the actual product configuration and additional features in the quote, such as whether Teams is included or not. Do not assume that having the same product family name gives the same rights as the existing contract.
  • Commitment and payment cycle: Monthly payment for an annual commitment and a monthly commitment may differ. Paying monthly does not mean you can freely reduce the quantity starting next month.
  • Existing costs and duplication: Check whether it overlaps with separately purchased email, security, or app subscriptions. Make a plan for transferring data and usage rights before canceling existing subscriptions immediately.
  • Trial expiration: Check the end date, paid conversion conditions, payment settings, and data processing schedule. Compare to see if trial features are included in purchased paid products.

Checking your existing licenses

In the Microsoft 365 admin center, go to Billing → Your products to check your subscriptions and available seats, and go to Users → Active users to check the license assignment status of specific users. The menu names or displayed items on the screen may vary depending on your purchase path and role. If purchased through a reseller, quantity changes and billing tasks may need to follow the partner's procedures.

On the subscription screen, the total purchased, assigned, and available quantities are recorded by product, and on the user screen, you can check which products and apps are enabled for that person. For example, if 35 were purchased and 32 assigned, that means 3 are remaining, not that only 32 are being billed. Cost and quantity adjustments should be separately confirmed according to subscription, license, and billing checks (Korean).

Before changing a license, review the impact on the services in use and data retention. Especially, changes that remove email or storage services are not just simple app changes. After the change, verify that the necessary apps and services for the users open normally.

Results to check after pilot assignment and reasons for failure

  1. After recording the existing products and enabled apps, apply the approved new configuration to one representative user. Also, check the user’s usage location and the remaining seats.
  2. Have the user verify mail sending and receiving, document opening and saving, and activation of necessary apps in a new login session. Distinguish between completion of assignment in the admin center and actual usage by the user.
  3. If the purpose is device management or access control, verify both the policy target and the application result. Having a license does not automatically design and deploy the policy.
  4. If it fails, check for insufficient seats, user location, inter-app dependencies, group-based assignment status, and error messages. When restoring the original configuration, first check available seats and retention conditions, and do not repeatedly remove the product without identifying the cause.