CSP (Cloud Solution Provider)
Microsoft's modern partner-led channel for cloud subscriptions. Monthly or annual term commitments through a partner, with the New Commerce Experience (NCE) governing cancellations and seat changes.
Also known as: Cloud Solution Provider, NCE
Last reviewed by MSLicenseHub Licensing Desk on 2026-11-12.
At a glance
- Licensing model
- Subscription via partner (NCE terms)
- Related entities
- NCE · Partner of Record · Microsoft 365 · Azure · Dynamics 365
Key licensing rules
- CSP subscriptions are bought through a Microsoft partner, who bills you and provides first-line support.
- New Commerce Experience (NCE) offers monthly, annual and (for some products) three-year terms; monthly terms cost more than annual ones.
- After purchase or renewal there is a short cancellation window (about 7 days) for a prorated refund; after that, annual seats cannot be reduced until renewal.
- Perpetual software such as Windows Server or SQL Server can also be bought through CSP, separately from subscriptions.
Common mistakes and how to avoid them
Compare 3-year total cost including term premiums, seat changes and support.
Keep a monthly-term buffer for uncertain seats.
Ask the partner to confirm the tenant, partner of record and renewal dates in writing.
Before you request a quote, gather
- Tenant domain and global admin contact
- Seat counts per product and expected changes
- Term and billing frequency per product
- Partner support scope and response times
- Renewal dates aligned across products
Compare options
In-depth articles
Navigating Microsoft licensing for MSPs requires choosing between CSP Tier 1 and Tier 2. We debunk 6 common my…
The transition to Microsoft's New Commerce Experience (NCE) has fundamentally altered the renewal lifecycle fo…
Confused by Microsoft licensing? This beginner's guide breaks down CSP, Enterprise Agreement, and Open Value t…
Learn how to evaluate Microsoft CSP quotes by looking beyond the sticker price. This guide shows you how to ca…
For mid-market organizations, choosing between MPSA and CSP can define your IT budget for years. We compare MP…
An exhaustive analysis of Microsoft CSP New Commerce Experience (NCE) commitment terms, exploring the long-ter…
Frequently asked questions
CSP vs Volume Licensing — what is the difference?
Cloud Solution Provider (CSP) is the modern Microsoft channel where a partner manages your subscription. Billing is monthly or annual, seats can scale up and down each month, and the partner handles support tickets. Best for cloud-first workloads (Microsoft 365, Dynamics 365, Azure) where flexibility matters.
Volume Licensing (Open Value, MPSA, Enterprise Agreement) is the traditional channel for perpetual on-premises licenses — Windows Server, SQL Server, Office LTSC. Three-year commitments are typical, with optional Software Assurance for upgrade rights. Best for perpetual server licensing where you want to own the asset.
Most organizations use both: CSP for the cloud subscriptions and Volume Licensing for the on-prem perpetual licenses.
🔄 Updated 2026-11-10
As of late 2026, the distinction between CSP vs Volume Licensing remains fundamental to Microsoft’s procurement ecosystem. While Microsoft continues to migrate more products toward the CSP model to simplify administrative overhead, Volume Licensing remains a stable, essential framework for large-scale enterprise deployments and fixed-term commitments.
The current landscape reinforces these trends:
- Cloud Agility: CSP has become the industry standard for managing operational expenditure (OpEx), offering the granularity required for modern, fluctuating workforce needs.
- Perpetual Stability: Volume Licensing programs remain the primary mechanism for procuring perpetual software assets and specialized server infrastructure that does not fit the recurring cloud subscription model.
- Strategic Hybridization: The most common recommendation remains a hybrid approach. Organizations should utilize CSP for agile, cloud-native workloads and leverage Volume Licensing for the foundational, static on-premises assets that require multi-year budget predictability.
When evaluating these models, focus on your organization’s total cost of ownership (TCO) and administrative capacity. CSP offloads much of the management burden to your partner, whereas Volume Licensing often requires more direct involvement with procurement and asset management lifecycles.
Frequently asked questions
Which licensing model is right for my organization?
CSP is primarily for recurring cloud subscriptions (Microsoft 365, Azure), while Volume Licensing remains the standard for perpetual on-premises software and specific long-term server commitments. Many organizations adopt a hybrid approach to leverage the benefits of both.
Sources
What is the Microsoft Admin Center for Volume Licensing?
Microsoft retired the old VLSC (Volume Licensing Service Center) in 2024 and consolidated all licensing management into the Microsoft 365 Admin Center and the Microsoft Cloud Partner Program portal. Volume Licensing customers now download keys, view orders and manage agreements under "Billing → Your products" in the Microsoft 365 Admin Center, signed in with the tenant's global admin or billing admin role.
If you still see references to VLSC in older documentation, mentally swap it for the M365 Admin Center.
🔄 Updated 2026-11-12
Updated 2026-11-12: The transition from the legacy Volume Licensing Service Center (VLSC) to the Microsoft 365 Admin Center is now fully complete. All Volume Licensing administrative functions, including contract management and product fulfillment, are exclusively handled within the M365 Admin Center. Users should ensure that appropriate administrative roles are assigned to their tenant accounts to maintain continuous access to licensing assets.
Frequently asked questions
Can I still access the legacy VLSC?
No, the legacy VLSC has been fully retired. All Volume Licensing administrative tasks, including software downloads, license key management, and agreement tracking, must be performed within the Microsoft 365 Admin Center.
What permissions are needed to manage Volume Licensing in the Microsoft 365 Admin Center?
You typically require the Global Admin or Billing Admin role within your organization's Microsoft 365 tenant to manage and view Volume Licensing agreements. Assigning these permissions is managed through the "Roles" section of the Admin Center.
Sources
When do I outgrow Microsoft 365 Business and need Enterprise?
Three triggers. Seat count — Business plans cap at 300 seats per tenant. Advanced security and compliance — eDiscovery (premium), insider risk management, customer key, advanced data residency and information protection beyond labels live in E3/E5. Windows Enterprise — if you want the Windows 11 Enterprise SKU bundled with the user license, that comes with M365 E3/E5, not Business Premium.
If none of those apply, Business Premium often gives you Defender for Business and Intune for less than E3 with similar day-to-day functionality.
🔄 Updated 2026-11-12
As of late 2026, the guidance regarding when to upgrade from Microsoft 365 Business to Enterprise remains consistent. The primary decision factor is the 300-seat cap; if your organization is nearing this threshold, you should begin the procurement planning for Enterprise (E3/E5) licensing via Volume Licensing or direct subscription channels. Do not consider OEM versions as they are restricted to hardware-bundled scenarios and are not a viable licensing strategy for scaling user counts.
Regarding feature parity, Microsoft continues to differentiate Enterprise plans through advanced compliance and governance tooling. Organizations requiring automated insider risk management, comprehensive eDiscovery, or specific advanced data residency obligations should prioritize an Enterprise upgrade regardless of their current seat count. For organizations under 300 seats that do not require these specialized compliance features, Business Premium continues to be the most effective choice for managing endpoints and cloud security without the additional cost of an Enterprise license.
Frequently asked questions
Is there a hard limit on the number of users for Microsoft 365 Business?
Business plans are limited to 300 users. If you anticipate exceeding this headcount, you must plan a migration to Enterprise licensing (E3/E5).
Which security features require an upgrade to an Enterprise plan?
Enterprise plans provide access to advanced compliance tools like eDiscovery (Premium), insider risk management, and advanced data residency, which are not included in Business plans.
Sources
When is Software Assurance worth paying for?
Software Assurance (SA) adds roughly 25–29% per year on top of a perpetual Volume License. It is worth it when you actually use the benefits:
- Version upgrades — the biggest benefit. Without SA, every major upgrade is a fresh purchase.
- License Mobility — needed to run server workloads (SQL Server, SharePoint) on Azure or AWS using your existing license.
- Azure Hybrid Benefit for Windows Server and SQL — saves roughly 40% on Azure VM and SQL DB pricing.
- Training vouchers, planning services, 24/7 problem-resolution support.
SA is rarely worth it for desktop apps you do not plan to upgrade. It almost always pays for itself on Windows Server, SQL Server and Exchange Server in 3 years.
🔄 Updated 2026-11-10
Updated 2026-11-10: As of late 2026, the strategic value of Software Assurance (SA) continues to center on total cost of ownership (TCO) for hybrid environments. While cloud-native services have evolved, SA remains the essential vehicle for the Azure Hybrid Benefit, which continues to be a primary driver for cost efficiency when deploying Windows Server and SQL Server workloads in Azure. Organizations should evaluate SA strictly based on their three-year infrastructure roadmap rather than generic bundles. If your strategy involves migrating existing on-premises perpetual workloads to the cloud, the potential savings from SA typically outweigh the annual maintenance premiums. Conversely, for static, localized environments where no hardware refresh or version upgrade is scheduled within the next 36 months, the return on investment for SA is significantly diminished.
Frequently asked questions
Is Software Assurance still relevant in a cloud-first era?
Software Assurance remains the primary mechanism for accessing new version rights, the Azure Hybrid Benefit, and specific hybrid cloud deployment flexibilities. It is most valuable for organizations with standardized server infrastructures and those actively migrating to or operating within a hybrid cloud environment.
Sources
How does Dynamics 365 base + attach licensing work?
Microsoft prices the first Dynamics 365 app per user at the higher "base" rate. Each additional qualifying app for the same user is sold at the "attach" rate — typically about 70% less. This rewards users who span multiple Dynamics modules (Sales + Customer Service + Field Service).
The catches: only certain apps qualify as a base, and the attach price applies only to that same user. You cannot mix and match across the team. Plan the user-to-app mapping carefully — getting it wrong inflates the cost by thousands per year on a small team.
🔄 Updated 2026-11-13
The core logic of the Dynamics 365 base + attach licensing model remains a fundamental cost-saving strategy for enterprise deployments. As of November 2026, the requirement to maintain a single, qualifying base license per user before applying attach licenses remains strictly enforced. Organizations must ensure that the user profile remains consistent across these assignments to remain compliant and avoid unnecessary surcharges.
Practical recommendations for 2026 include:
- Audit User Needs: Before renewal, map specific application usage to individual roles. Avoid assigning a high-cost base license to users who only require limited functionality if an attach license would suffice under a different base.
- Review Licensing Guides: The qualification list for "base" vs. "attach" can fluctuate with new product releases. Always verify the latest Microsoft Dynamics 365 Licensing Guide to confirm which applications qualify as a base for your specific business requirements.
- Centralize Management: Utilize the Microsoft 365 admin center to track these assignments systematically. Misalignment often occurs when organizations attempt to swap licenses between employees without updating the base-to-attach mapping, leading to license non-compliance or inflated invoices.
For organizations looking to scale, these licensing rules prioritize users with comprehensive cross-departmental requirements. If your team requires multiple Dynamics 365 modules, ensure that the most expensive qualifying application is designated as the base to properly trigger the attach discount structure.
Frequently asked questions
What is the difference between a Dynamics 365 base and attach license?
A base license is the first full-priced qualifying application assigned to a user. Once a base is assigned, that same user can be licensed for additional qualifying applications at a significantly reduced attach license rate.
Can I share attach licenses across my team?
Attach licenses are user-specific and non-transferable between team members. You must ensure the user assigned the base license is the same individual receiving the attach licenses to benefit from the reduced pricing.
Sources
Glossary terms
Related pages and official sources
Binding terms: CSP program overview · Microsoft Product Terms. This hub is general guidance, not a substitute for your agreement.