فا
MSLicenseHub
About · the team

An independent reference for Microsoft licensing.

MSLicenseHub explains every Microsoft licensing track in plain English — editions, CALs, Volume Licensing, CSP, Software Assurance and the subscription transition for Microsoft 365.

MSLicenseHub01Official source02Agreement03DecisionConcept diagram · not a Microsoft product screenshot
Editorial promise

Clear distinctions between licence ownership, activation and support.

Product references
51
Windows, Office, Server, SQL, Visual Studio, Visio, Project, Exchange, SharePoint.
Languages
2
Persian-first guidance with an English reference catalogue.
Buying channels
3
Retail, Volume Licensing and CSP — explained side by side.
OEM keys promoted
0
OEM is supplied pre-installed by hardware makers, never as standalone keys.
What we do

Translate Microsoft's catalog into decisions you can defend

Edition, deployment and access rights must be considered together. This reference helps identify the questions to resolve before procurement; your applicable agreement remains authoritative.

Mission
Plain English, every time

If a Microsoft licensing concept can be explained in a sentence, we'll write the sentence. If it really takes a diagram, we'll draw one.

Method
Read the Product Terms

Use Microsoft's Product Terms, licensing guides and lifecycle pages to confirm the rules applicable to your exact product, region and agreement.

Posture
No affiliate selling

We do not sell licenses. We point readers to legitimate channels and explain how to read a quote so you can pressure-test it.

What we will not do

A short list of things you will not find here

Never #1
Recommend standalone OEM keys

OEM licensing is reserved for hardware manufacturers shipping pre-installed software. Standalone OEM keys sold to end users violate Microsoft's distribution terms. Anyone selling them online is, at best, distributing a key they have no right to.

Never #2
Push a single channel

Retail isn't evil. Volume Licensing isn't always cheaper. CSP isn't always right. We compare them against your actual scale — not against a partner commission rate.

Coverage

What MSLicenseHub covers, by category

Number of product reference pages in each catalogue category.

Product references by category
windows13
server8
office14
database5
collaboration6
developer4
cloud1
Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Site structure

Where to find what

Section
Products

Every major Microsoft product — what's in the box, how editions differ, how it's licensed.

Open →
Section
Magazine

Long-form analysis of changes, edition swaps and licensing shifts worth tracking.

Open →
Section
FAQ

The questions that come up most in licensing conversations — answered shortly and exactly.

Open →
Section
Glossary

CAL, SA, VLSC, KMS, MAK, CSP, OSE — every acronym defined with the procurement implication.

Open →
Sources and limitations

How to verify a licensing decision

  1. Identify the exact product, release, edition and agreement.
  2. Read the Microsoft Product Terms and product-specific licensing guide.
  3. Check the official lifecycle directory; licence validity and security support are different.
  4. Keep purchase records and confirm unresolved deployment questions in writing. Site summaries are educational, not a substitute for contractual or legal advice.