How much does Microsoft 365 cost for a business with 100 employees?

What should a 100-person business include in its Microsoft 365 budget?

Start with the people and services you need, rather than multiplying the first advertised price by 100. A company with 100 employees may also have contractors, shared mailboxes, meeting rooms, administrators and temporary staff. These identities do not all have identical licensing requirements. Some people need installed Office applications and managed laptops. Others work through a browser on a controlled shared device. Count requirements by role before deciding how many seats to purchase.

Separate the recurring subscription from the work needed to run it well. Migrating email, configuring devices, protecting accounts and helping employees use the service are different budget lines. An inexpensive subscription can become an expensive operating model if nobody owns those tasks. Equally, a higher plan may replace services you currently buy separately. The comparison should show the whole arrangement over the same period, with responsibilities and exclusions written down.

For a practical starting point, NetMonkeys’ Microsoft 365 support services provide a route to reviewing licences alongside configuration and ongoing support. Bring your current invoice and a simple staff list by job type. That makes the conversation about the actual environment, rather than a generic price calculator.

What do current UK prices look like for 100 employees?

The table below uses prices displayed on Microsoft’s UK business pricing and product pages when checked on 27 October 2026. These are licence-only arithmetic examples, not NetMonkeys quotations. The displayed terms are a per-user monthly equivalent paid yearly, excluding VAT. The rows labelled with Copilot are bundles. The standalone Business Standard row is shown separately, so the bundle prices are not mistaken for base-plan prices.

Check the exact product name, Teams inclusion, Copilot inclusion, billing frequency and commitment term before using any figure in a purchase decision. Promotions, customer eligibility, existing agreements and partner arrangements can produce different quotes. Microsoft’s current UK plans and pricing is the source for the displayed examples. Capture a dated quotation for your own procurement record, because a web page can change after a budget has been approved.

The standalone Business Standard product page lists the £10.80 annual-payment equivalent for the version with Teams. This provides a base-plan comparison alongside the explicitly labelled Copilot bundles. A no-Teams variant and monthly subscription terms have separate prices; compare equivalent variants before drawing a conclusion.

Why is the monthly advertised price different from a monthly contract?

A price described as a monthly equivalent can still require an annual commitment and annual payment. That affects cash flow and how readily you can reduce seats. A company expecting a seasonal workforce should model the value of flexibility alongside the unit price. The cheapest rate is not automatically the cheapest annual outcome if it leaves the business paying for unnecessary seats after a project ends.

Ask the supplier to state the commitment period, payment schedule, renewal date and cancellation or reduction rights separately. For example, a monthly invoice does not by itself mean a month-to-month commitment. Put renewal reminders in a shared procurement calendar, with an owner and enough lead time to review staff changes. Approval should be based on the contractual liability, not just the amount expected on the next invoice.

Does every employee need the same Microsoft 365 licence?

Usually the better question is whether each employee has the capabilities their role requires. A browser-based worker may not need installed desktop applications. A finance colleague using complex workbooks may need those applications every day. Device management, identity controls, email protection and compliance requirements can affect the decision even where two employees use the same documents. Feature usage alone is an incomplete way to decide a security-related entitlement.

Create a small number of role profiles rather than a unique licence arrangement for every person. Record the approved plan, any justified add-ons and the reason for each exception. Test a proposed profile with representative employees before changing a wider group. Mixed licensing needs careful entitlement checking: a person benefiting from a licensed feature may need the relevant licence even if an administrator configured it centrally. Ask the supplier to confirm that point for your proposed design.

How can a mixed licence model change the total?

Use a transparent calculation that colleagues can reproduce. As an illustrative exercise, take 40 people at the displayed Business Basic rate and 60 people at the displayed Business Premium with Copilot rate. The monthly equivalent is 40 × £5.40 plus 60 × £24.60, or £1,692 excluding VAT. The annual equivalent is £20,304. This demonstrates arithmetic only; it does not establish that those plans meet the company’s requirements.

The next step is a capability check. Would those 40 people still need security, device or app features absent from their chosen plan? Are there separately purchased services that cover the requirement, and are they configured and supported? A mixed model is worthwhile when it reflects a defensible operating design. It is less useful when savings in one column simply reappear as overlooked add-ons or support effort elsewhere.

What one-off costs should be allowed for?

Implementation can include tenant assessment, domain work, mailbox migration, identity configuration, endpoint enrolment, document migration and user training. Scope depends on where you are starting. Moving from a well-managed Microsoft 365 environment is different from replacing several disconnected email and file systems. File volumes, old applications and poorly understood permissions can create more work than the number of employees suggests.

Ask for a project estimate based on named deliverables. A statement such as “migrate Microsoft 365” is too broad to compare fairly. Does it include calendars, contacts, shared mailboxes, archives, Google Drive content, permissions, mobile devices and support after cutover? Agree what will be tested and what counts as completion. NetMonkeys’ cloud migration services can be discussed as a separate workstream so that subscription and transition costs remain visible.

Which ongoing costs are easy to overlook?

Think about the activities that continue after the first successful sign-in. Someone must handle starters and leavers, licence renewals, administrative access, alert review, device changes, recovery requests and updates to security policies. Include a support route for employees and a clear division between internal responsibilities and any service provider. An agreement should make it easy to identify who acts when a problem crosses email, identity and devices.

Avoid adding every possible extra automatically. Instead, ask what requirement each service satisfies and whether your existing arrangement already meets it. The same principle applies to backup: define the data, retention and recovery needs, then assess suitable provision. A generic “cloud backup” label does not explain whether a deleted mailbox, overwritten document or compromised account can be recovered within the business’s required timescale.

How should Copilot be budgeted for?

Distinguish plans that include Copilot from eligible base subscriptions with a separately purchased Copilot entitlement. The current offer can vary by product, route to purchase and customer status. Do not add an assumed standalone Copilot charge to a bundle that already includes the capabilities you intend to use. Conversely, access to an AI chat interface should not be taken as proof that every app-integrated experience is included.

Budget for adoption as well as the licence. Select roles with repeatable tasks, agree an approved information-handling approach and measure results against the time required to check outputs. Start with a limited cohort rather than using company headcount as the purchase quantity. If the pilot shows value, expand with evidence. If usage is low, investigate whether training, permissions, task selection or the product itself is the limiting factor before renewing the same allocation.

Can existing subscriptions reduce the amount we need to buy?

Yes, but only after checking what has actually been purchased and assigned. Businesses sometimes have overlapping subscriptions acquired by different teams, old add-ons retained after a plan upgrade, or seats reserved for staff who have left. Compare supplier invoices with tenant subscriptions and user assignments. An unassigned seat is a prompt to investigate; it is not proof that the next invoice can immediately be reduced.

Look at both recurring products and the services they enable. Removing a licence without understanding mailbox, archive, retention or device dependencies can create disruption. Review current Microsoft guidance and agree the required data-preservation steps before making changes. A controlled audit should produce a list of immediate actions, renewal-time reductions and cases requiring further investigation. That is more useful than a single optimistic savings figure.

How do we compare two supplier quotes fairly?

Ask both suppliers to quote the same staff profiles, exact product variants, term and implementation scope. Check whether VAT is included and whether the price is fixed for the commitment period. Separate Microsoft subscription charges from managed support and one-off consultancy. If one proposal includes recovery services, employee training or security configuration and another does not, bring those differences into the comparison explicitly.

Consider the practical cost of service gaps. Who will investigate suspicious inbox rules? Who will support the managing director’s phone after migration? Who owns a failed automated process using an employee account? These questions do not justify buying the most expensive proposal automatically. They help you choose an arrangement with a clear operating model and avoid discovering unpriced responsibilities after the contract starts.

What should finance receive before approving the budget?

Provide a one-page summary showing the baseline headcount, proposed licence mix, annual commitment, monthly equivalent and first-year project costs. Include assumptions about growth, contractors, migration overlap and optional services. Put any uncertain items in a separate section with an owner and a date for resolution. Finance should be able to trace each total back to a quantity and a contracted unit price.

Show a base case and a realistic change scenario. For instance, model ten additional employees or a reduction in temporary staff at the next available contract adjustment date. Keep the scenario consistent with the actual terms rather than assuming licences can be cancelled whenever staff numbers change. A useful budget tells decision-makers what they are committing to and how costs will respond to foreseeable business changes.

What should happen during the first three months?

Before rollout, confirm licence assignments, security responsibilities and a representative user pilot. During rollout, keep a log of access and app issues so that staff problems are resolved through one visible process. After rollout, review whether the intended features are configured and whether employees can complete the work that justified the purchase. Buying an entitlement and adopting a capability are separate milestones.

At the end of the first quarter, compare actual invoices and support effort with the budget. Review unused allocations, new starters, device coverage and optional services. Record any changes that should be made at renewal, even where an immediate reduction is unavailable. This turns the initial procurement into an ongoing management routine and prevents the licence estate becoming difficult to explain a year later.

How should we account for VAT and cash flow?

Keep the economic comparison and the payment schedule separate. The plan examples exclude VAT, while the amount leaving the bank may include VAT and any project invoice due at the same time. Ask finance how the organisation treats VAT rather than assuming every business can recover it in full. A charity or another organisation with a particular tax position may assess the cash impact differently from a fully taxable company.

Build a calendar of expected payments as well as an annual total. An annual subscription payment, migration invoice and device replacement programme can create a larger first-month cash requirement than the monthly equivalent suggests. If a provider offers several billing arrangements, compare their full committed cost and timing. Record who approves additional seats during the year so that growth does not bypass the original budget assumptions.

What should a budget reserve cover?

Use a reserve for specific uncertainties rather than an unexplained percentage that hides incomplete scope. Examples include a mailbox archive requiring additional assessment, an old application needing remediation or a temporary period of overlapping subscriptions during migration. Give each uncertainty an estimated range, an owner and the evidence needed to narrow it. Remove resolved items from the reserve rather than letting them become a permanent extra charge.

The reserve should not replace a proper survey. If nobody knows how many devices or shared mailboxes exist, the right next step is inventory work. A supplier cannot reliably price an unknown estate from headcount alone. Once the survey is complete, update the budget before committing to the main project and distinguish genuine contingency from work that is now clearly within scope.

How should licences be tracked after approval?

Maintain a register linking each subscription to its supplier, term, renewal date, business owner and approved use. Keep quantities and rates alongside the licence assignment process, so that operational changes can be reconciled with finance records. The register can be simple; it needs to remain understandable when a colleague is absent or a service provider changes.

Use a regular reconciliation to compare people, assignments and purchased quantities. Investigate discrepancies rather than assuming they are errors. A reserved seat may support a confirmed starter, while an apparently dormant account may have a valid business requirement. Document the decision and revisit it at a defined date. This creates a useful audit trail without turning every small change into a lengthy procurement exercise.

How can NetMonkeys help calculate a realistic total?

Bring a current licence export, invoices, renewal dates and a role-based staff summary to the discussion. Add a short description of email, file storage, devices and any migration requirement. Avoid sending unnecessary personal data in an initial enquiry. An anonymised inventory is usually sufficient to establish whether a detailed review is worthwhile and what access would be needed later.

NetMonkeys can discuss Microsoft 365 support, migration and the surrounding operating model together. Ask for a proposal that separates subscriptions, project work and recurring support, and records the assumptions behind each figure. The objective is a Microsoft 365 budget that finance understands and IT can operate, with employees licensed for the work they actually need to do.