Microsoft licensing · Module 1
How does Microsoft licensing
work?
Using Microsoft software requires more than a purchase receipt. What matters is which product is being used, who is allowed to use it, and which rules apply under the relevant agreement.
In brief
A licence answers a simple question: who may use which product, and how?
Correct licensing requires the product, usage rights, quantity, assignment, and agreement to align.
- 01Which product is being used?
- 02How are licences counted?
- 03Who may use the software?
- 04Which agreement covered the purchase?
- 05Which rules applied when it was bought?
Explained simply · The essential terms
Three terms worth understanding first
A software licence gives you permission to use a particular program or online service under specified conditions.
Licence
The right to use a program or online service in the way your agreement allows.
Licensing metric
The unit being counted: for example, people, devices, or processor cores.
Product Terms
Microsoft's official rules explaining what a particular licence permits.
A practical example: If 25 employees use a Microsoft 365 offer licensed per user, the appropriate rights must be assigned to those 25 people. The number of devices is not automatically the relevant measure.
01 · The core principle
Usage rights are what make software licensable
Installation, activation, and licensing are different things. A product key or technical access does not, on its own, describe everything an organisation is legally entitled to use.
What is being used?
Start with the exact offering—for example, Microsoft 365 E3, Office LTSC 2024, or Windows Server 2025 Standard.
What is permitted?
The Product Terms describe installation, running, access, assignment, and special rights for the relevant offering.
What was acquired?
Orders, agreements, invoices, and portal records evidence acquired licences and must align with actual use.
02 · Product, edition, and version
Similar names do not mean identical rights
Microsoft assigns usage rights to specific offerings. Edition and version should therefore not be inferred from the technical installation alone.
Standard is not Datacenter
Editions provide different functions and usage rights. Rights to a higher or lower edition exist only where the applicable terms expressly permit them.
2025 is not 2022
Version rights, upgrade rights, and permitted downgrade paths depend on the product, acquisition, and—where relevant—active Software Assurance.
A suite is not a standalone product
A suite can bundle multiple components. Whether and how those components may be used separately follows the relevant suite and product terms.
03 · Software or Online Service
Microsoft separates installed software and cloud services
The Product Terms list Software and Online Services in separate offering areas. Some suites combine both.
Installed products
Software is assigned under a defined licensing model to a user, device, server, core, or another unit. The product entry defines the specific running and access rights.
Time-bound access
Online Services grant access for the subscription term. Scope, users, capacity, and prerequisites depend on the offer purchased.
04 · Perpetual or time-limited
Perpetual licences and subscriptions follow different logic
The agreement term and the duration of a usage right are not automatically the same.
Perpetual licence
An entitled software version can generally continue to be used under a perpetual licence. If Software Assurance expires, version rights acquired while it was active remain; later releases are not included.
Time-limited right
A subscription grants rights for the agreed period. Without renewal, the subscribed use or access right generally ends, subject to the specific agreement and product terms.
05 · Licensing model and metric
Microsoft counts differently by product
The product name alone does not reveal how many licences are required. The licensing model defines assignment and counting.
User or device
Common in Microsoft 365, Windows, and desktop scenarios. The key question is who or what receives the licence assignment.
Compute or instance
Server products may consider physical or virtual cores, server instances, and minimum licence quantities.
Assess access separately
Server/CAL and Per Core/CAL models may also require access licences for each user or device.
06 · Which terms apply?
Agreement, Product Terms, and date belong together
The Product Terms form part of the broader Microsoft contractual relationship and are generally updated monthly.
The agreement sets the framework
An Enterprise Agreement, Microsoft Customer Agreement, or another programme determines which published terms apply to the customer.
The product defines the rights
Universal License Terms, the licensing model, and product-specific terms describe availability, acquisition conditions, and use.
Check the historical version
Depending on the agreement, its effective date or the licence acquisition date may matter. The Product Terms site supports earlier dates, with older documents held in the archive.
Already covered in depth
Licence metrics: User, Device, Server, Core, and more
We deliberately avoid repeating the general counting models here. The existing foundation article explains them with examples and a checklist.
Open the metrics article →07 · Practical check
Five questions for every Microsoft licensing assessment
If one answer is missing, the assessment is not yet defensible.
- 01Which exact product, edition, and version are in use?
- 02Is the right perpetual or subscription-based?
- 03Which licensing model and metric apply?
- 04Through which agreement, and on what date, was the licence acquired?
- 05Who or what is the licence assigned to—and how is the product actually used or accessed?
Continue with Module 2
How can Microsoft software be purchased?
Next, distinguish agreements, licensing programmes, and purchasing channels—from EA and MCA to CSP, MPSA, and Open Value.
Remember
Product + right + metric + assignment + agreement + date
Only when these elements align can a Microsoft licensing position be assessed with confidence.
Primary and official sources
Current, verified, and traceable.
The statements were checked against official Microsoft sources as of 20 August 2026. Product Terms are updated continuously; the customer's specific agreement and acquisition records remain decisive.
Note: This article provides accessible professional guidance, not legal or individual licensing advice. The applicable agreements, orders, and Product Terms govern.
Complete learning pathUnderstand Microsoft licensing from the ground up
Ten connected modules—from the foundations to compliance and a defensible licence position.