What Is Microsoft Volume Licensing?

Microsoft groups the long-standing programs as classic volume licensing. The agreement types administered on the volume licensing pages of the Microsoft 365 admin center are Microsoft Enterprise and Enterprise Subscription, Select and Select Plus, academic agreements (Education Enrollment or School Enrollment), and Open Value, Open Value Subscription and the legacy Open License program.

Open License itself is closed: Microsoft retired the program on 1 January 2022, and customers who registered their Open licenses before that date keep online access to them. Open Value and Open Value Subscription continue as named agreement types, which is why parts under those programs still appear on distributor price lists.

Two other roads sit outside the classic set and are administered separately. Licenses bought under a Microsoft Products and Services Agreement (MPSA) are registered and managed in the Microsoft Business Center, and licenses bought under a Microsoft Customer Agreement for Enterprise are invoiced and administered apart from the volume licensing pages entirely.

Commercial and Government Community Cloud customers reach their classic agreements through the volume licensing pages of the Microsoft 365 admin center. Government Community Cloud High and Department of Defense administrators use the equivalent government admin centers rather than the commercial one — the same functions, a different address, and worth confirming before an administrator is told to sign in.

Access is by role, not by mailbox. A volume licensing role is assigned during contract creation or later by an administrator, and for new contracts Microsoft assigns roles to a Microsoft Entra ID rather than to a separate login identity. The practical consequence at renewal time is that the person named on the contract as the notices contact has to sign in first and become the online administrator before anyone else can be given access.

Price is negotiated; rights are published. Microsoft's Product Terms site states that the unified Product Terms are incorporated by reference into the agreements governing a customer's use of Microsoft products and professional services — so what a license actually permits is settled there, not in a quote or a reseller's description.

That is where the questions procurement usually cares about are answered: whether a license may be reassigned from one user or device to another and how often, whether it carries downgrade rights to an earlier version, what a Client Access License covers, and what Software Assurance adds while it is current. Read the entry for the specific product and the specific program before assuming a right carries across from another agreement.

Start from the count and the horizon, not from the product page. Establish how many users or devices need the product, whether the requirement is permanent or for a fixed term, and whether the organization already holds an agreement the purchase can be added to — adding to an existing enrollment is usually simpler than opening a second one.

Then decide between a perpetual license and a subscription, because that choice determines what happens when the term ends rather than what the software does. Confirm whether Software Assurance or its subscription equivalent is wanted for version rights and support benefits, and get the whole thing quoted as a line-itemized document: program, product, license type, term and quantity, so the renewal in three years can be reconciled against it.