Home › Start here
Microsoft licensing · start here
Microsoft sells the same things through four programmes and forty names. You do not need to know which. Say what is happening — a first purchase, a server, developers, an agreement that is ending, an audit letter — and the next page asks only what it needs. Every route ends in a quote, an invoice, or the honest answer that you need not buy anything.
1 · What brought you here?
2 · I need Microsoft licences — which of these?
Business Basic, Standard, Premium, E3 or E5: start from the needs — security, devices, phone system, mailbox size, leavers — and get the plan plus the cheaper of upgrade or add-ons.
Email, Office, Teams and security for everyone: say what worries you and get the plan that covers it, with a monthly price per person.
A per-user monthly cost, annual or monthly commitment, invoiced in your currency by an entity in your country; the finder shows two routes and the cheaper one.
The tenant your code will live in: identity, Teams, storage, Copilot. The finder picks the plan; Visual Studio is a separate route below.
Plan finder →Core minimums, Standard against Datacenter, per core against Server + CAL, passive replicas, perpetual or subscription, six currencies, invoice from the result.
A server licence for a system the business runs on: the calculator asks about the hardware and the users and gives one number.
One-time perpetual or annual subscription; the calculators show three-year and five-year totals and the invoice request attaches the configuration.
Licences for production servers. For dev/test copies of the same products, see Visual Studio below — they are included there.
Windows Server → · SQL Server →Copilot needs a qualifying base plan and respects existing permissions, so over-shared files surface; the plan finder prices it and the readiness review finds the sharing problems first.
AI in Word, Excel, Outlook and Teams on your own data. Priced per user per month on top of the plan; a short readiness check comes before rollout.
An add-on per user per month, annual commitment; pilot a group first. The plan finder prices it with the base licence.
Licensed per user on top of the base plan; Graph permissions decide what it sees. The readiness review is a permissions audit.
Price Copilot →Community, Professional perpetual or monthly, or a subscription with Software Assurance under Open Value; six questions decide it, with prices and how to buy.
Tools for the development team: the finder tells you whether the free edition is allowed, and if not, what the right licence costs per developer per year.
Per developer per year under a three-year agreement paid annually, or per month with no commitment; the finder shows which and why.
The one that matters: do you install SQL Server or Windows Server in test labs? If yes, the subscription; if no, the editor. Community is free if you qualify.
Which Visual Studio? →Subscriptions through CSP with our support, Azure Hybrid Benefit for licences you own, dev/test pricing with a Visual Studio subscription, and infrastructure migration at a fixed price.
Servers in Microsoft’s cloud instead of your own room: we size it against real usage, migrate it, and invoice the consumption monthly.
Pay-as-you-go consumption invoiced monthly in your currency, with reserved pricing for the stable part; licences you already own reduce the bill.
Dev/test subscriptions at reduced rates for Visual Studio subscribers, Azure DevOps included, and a lab that costs less than the hardware it replaces.
Azure infrastructure →2 · I already have licences — which of these?
Renew SA, add licences, move some of it to CSP, or pay less; free audit first, and it can be signed with any reseller before the end date.
The one moment everything is negotiable: what to keep, what to drop, what to move to a subscription. Free audit, no obligation.
The licences become yours at the end and the annual payments stop; renewing Software Assurance is cheaper than the first term. We quote both routes.
Your Visual Studio subscriptions expire with the agreement even though the licences are yours; renewal keeps the new versions and the dev/test catalogue.
Renewal options →Open Value or CSP; part number known or not; mid-term additions priced to end with the agreement.
More seats or a new product on what you already have, with the same end date and one invoice.
Pro-rated to the existing end date so everything renews together; the quote shows the per-year effect.
Add subscriptions for new developers to the existing agreement rather than starting another; they end on the same date.
Add licences →Same tenant, same agreement, different partner and invoice; nothing migrates; six-step CSP switch timed to renewal, reseller transfer for Open Value.
Keep everything, change the company that invoices you and answers the phone. Users notice nothing.
Like-for-like comparison at our price, invoicing from an entity in your country, no double payment during the switch.
Your tenant, code and pipelines do not move; only the partner of record does.
Change partner →What is installed against what is licensed, per product, before Microsoft counts it; SQL Server and Windows Server especially; then the cheapest way to close each gap.
A count of what you use against what you own, done by us before Microsoft does it, with the cheapest way to fix any gap. Read-only.
A liability estimate before the audit letter, and the options: true-up, licence reassignment, or retiring what is not used.
Test installs of SQL Server and Windows Server are the usual finding: covered by a Visual Studio subscription, or licensed in full otherwise.
Licensing review → · Recount SQL Server →2 · We are moving somewhere — which of these?
Tenant-to-tenant, Google Workspace, on-premises Exchange and AD to the cloud; fixed prices, no planned downtime, the migration host sized for the volume.
Moving the company’s mail and files to Microsoft 365, or merging two companies’ systems after an acquisition, with a fixed price and a date.
Fixed price after a free scoping; the cost calculator gives the range before you talk to anyone.
Identity, DNS, DKIM and the order of operations decide whether Monday works; the guides cover each.
Migration cost → · Consolidation after M&A →2 · I need prices, or the channel — which of these?
Every CSP subscription and perpetual licence in six currencies, every Open Value line in EUR and GBP, with part numbers.
The full price lists, searchable by product name.
List prices with our price on Open Value lines; add to a quote and we invoice.
Search by CFQ7TTC0… or 9EM-… part numbers directly.
CSP catalogue → · Open Value catalogue →Which products are sold through CSP, which need Open Value, which Microsoft sells only directly: one table, one selector.
Some Microsoft products can be bought from us on a monthly invoice; some need a three-year agreement; a few only Microsoft sells. Pick the product and see.
Which purchase route applies to each product, and therefore which commitment and invoice you are looking at.
Visual Studio subscriptions are the classic case: not sold through CSP at all. The table says what is.
Which channel? →Own the licence with Software Assurance in three payments, or buy perpetual or subscribe through CSP; priced both ways from the September lists.
Own it and pay over three years, or pay as you go and stay flexible: the comparison with real numbers.
Capital or operating: three annual payments ending in ownership, or a subscription that never does. Both priced.
The dev/test catalogue and Azure credit come only with Software Assurance; that is what Open Value buys.
Read the comparison →We sell to legal entities; private individuals buy from Microsoft directly. Prices on every page are Microsoft’s list prices unless marked as ours; the quote sets the final figure.
Why this page exists
CSP, Open Value, NCE, EA, Standard, Enterprise, MSDN, E3, E5, Premium: every one of them is a way of packaging the same software. The wrong choice costs either money or a licence audit; the right one depends on what is happening in your company, not on the name. So this page asks about your situation and takes you to the tool that already knows the names.
Where each programme fits
The recommendation at the end of every route follows these rules, and you can apply them yourself.
Microsoft 365, Azure, Dynamics, and one-payment perpetual Windows Server, SQL Server and Office. Monthly or annual, invoiced by our entity in your currency, cancel or reduce at renewal. The default for almost everything.
Licence with Software Assurance in three annual payments, perpetual after the third; new versions, licence mobility, failover rights. Required for Visual Studio subscriptions, which CSP does not sell. Five licences minimum.
Visual Studio Community for small teams, features already inside the plan you own, a mailbox that only needs a hold, shared mailboxes that need no licence. The routes say so when it applies.