Microsoft Licensing Guide 2026

Microsoft licensing has long been considered one of the most complex areas of IT management. With dozens of products, evolving subscription models, cloud and hybrid environments, volume agreements, and ever-changing terms, it is easy for companies to overspend or fall out of compliance.  

Understanding how licensing works is not just a technical concern, but essential for IT managers, procurement teams, consultants, and business leaders responsible for budgeting, security, and long-term strategy. 

In 2026, Microsoft’s continued cloud-first approach, updated subscription structures, AI-enabled services, evolving Enterprise Agreement terms, and pricing adjustments make it more important than ever to review and optimize your licensing strategy.

 

In 2026, Microsoft offers several licensing models designed to match different organizational sizes, purchasing preferences, product mixes, and deployment scenarios, and choosing the right one can significantly affect cost, flexibility, and administrative overhead.  

At a high level, subscription licensing (cloud-centric, term-based access) differs substantially from perpetual licensing (traditional on-premises software ownership): subscription models require ongoing payments to maintain access and automatically include updates, while perpetual licenses involve a one-time purchase that grants indefinite use of that specific version but usually does not include new features or upgrades without additional purchases or Software Assurance. 

Subscription is ideal for dynamic environments where scalability and continuous upgrades matter most, whereas perpetual works best in stable on-premises setups with predictable requirements. 

You can buy and manage these licenses:

• Cloud Solution Provider (CSP) is a flexible subscription channel through partners where you can add, remove, or change licenses frequently (often monthly) and pay as you go. It is especially suited for cloud services like Microsoft 365, Microsoft Azure, Microsoft Dynamics 365, and companies that value agility over long-term contract commitments.
• Enterprise Agreement (EA) is designed for large companies and ties you into a three-year commitment with volume pricing benefits and predictable budgeting, but with less flexibility to scale down mid-term.
• Microsoft Products and Services Agreement (MPSA) is a transactional model for mid-to-large companies that lets you mix cloud and on-premises purchases under one account without a commitment term.
• Microsoft Open License or Open Value is historically suited for smaller companies (5–499 users) and allows simpler volume licensing with optional Software Assurance and commitment options. It provides user-based, service-based, and cloud-based opportunities. However, it was retired in 2022, and most SMB licensing is now delivered through CSP under the New Commerce Experience (NCE), a licensing, subscription, and billing platform used for licensing within this program.
• Select Plus used to serve government and academic customers with on-premises purchases without organization-wide commitment but has been succeeded by MPSA where available.
• Microsoft Online Subscription Agreement (MOSA) lets companies of any size procure cloud services directly via the web without an enterprise contract - ideal for simple cloud-only scenarios.
• Academic and Government agreements may have specialized terms and pricing tailored to those sectors, often reflected across the above channels with eligibility-based discounts and compliance requirements.

In addition to volume and subscription programs, companies should also consider the following licensing models:

• Pre-installed or OEM (Original Equipment Manufacturer) licenses are perpetual and hardware-bound. They come preinstalled on new devices, are permanently tied to the original hardware (typically the motherboard), cannot be transferred to another device, and generally include limited support from Microsoft (support is primarily provided by the hardware manufacturer). They are usually the lowest-cost option and are often not purchased separately from the device.
• Retail Licensing (FPP – Full Packaged Product model) provides flexible, individually purchased licenses through the Microsoft Store or authorized retailers. These licenses are typically transferable (subject to license terms), purchased per device or per user depending on the product, and are well suited for individuals, small businesses, or isolated licensing needs outside of volume programs.

Here is a brief comparison of these models:

By understanding these models and how they align with your technology strategy, you can better balance cost, control, and operational agility as you plan your Microsoft licensing for required periods. 

In addition to licensing programs and purchasing channels, Microsoft licensing is broadly structured around two fundamental approaches:

• User-based licensing

User-based licensing (per user) assigns licenses to individual users, allowing them to access services across multiple devices; this model is common in offerings like Microsoft 365 and is ideal for organizations with stable workforces and predictable usage patterns.

• Consumption-based licensing

In contrast, consumption-based licensing (capacity or usage-based) charges based on actual resource usage, such as compute power, storage, or transactions, as seen in Microsoft Azure. This approach provides maximum flexibility and scalability, enabling organizations to pay only for what they use, but it also requires careful monitoring and governance to avoid unexpected costs. Understanding the differences between these two approaches is essential for aligning licensing decisions with both operational needs and financial control.

In 2026, Microsoft’s productivity licensing landscape continues to revolve around two fundamentally different approaches: Microsoft 365 subscription suites and perpetual Office licenses, each tailored to distinct usage and organizational needs.  

Microsoft 365 Suites provide users with a cloud-centric subscription model that bundles productivity apps with email, collaboration tools, security, and management services, and these plans are regularly updated with new features, including AI enhancements set to roll out through 2026, as part of the subscription experience. 

Within Microsoft 365, there are different tiers:

• Business plans (Business Basic, Business Standard, and Business Premium) 

They are designed for small and medium businesses (up to 300 users) and vary from basic web-only app access and email (Basic) to full desktop Office, Teams, and advanced security management in Premium. 

• Enterprise plans like E1, E3 and E5 

They offer broader capabilities, including enhanced security, compliance, analytics, and extended device management suitable for larger companies without user caps. 

• Specialized Frontline (F) and Academic (A) plans 

They deliver cost-effective cloud productivity for frontline workers or educational institutions with tailored feature sets and pricing.

The perpetual versions do not receive continuous feature updates and eventually reach the end of support after a fixed lifecycle, making them better suited for environments where stability and controlled feature sets are critical. 

Here is a simple comparison of subscription-based Microsoft 365 suites versus perpetual Office licensing in 2026:

By understanding these distinctions and mapping plans to organizational requirements, such as cloud integration, device management, compliance, and budget constraints, businesses can choose the licensing path that delivers the right balance of productivity, security, and cost for 2026 and beyond.

For large companies with 500+ users or devices, the Enterprise Agreement (EA) remains one of Microsoft’s primary volume licensing programs in 2026, designed to provide standardized, organization-wide licensing with predictable budgeting and discounted pricing. 

Under an EA, companies typically commit to a three-year term, licensing core products such as Windows Enterprise, Microsoft 365, and Enterprise Mobility + Security across all qualified users or devices. Enterprise Enrollment allows customers to structure their agreement around specific solution areas (for example, a Microsoft 365–focused enrollment) while maintaining centralized contract management and reporting. One of the defining mechanisms of an EA is the true-up process, which requires companies to report and pay annually for any additional users or devices added above the initial baseline. Traditionally, reductions in license counts (“true-down”) were limited until renewal; however, Enterprise Subscription Agreements (EAS) offer more flexibility by allowing companies to reduce license quantities at the anniversary date, aligning costs more closely with workforce changes.

EA agreements typically include access to a broad catalog of Microsoft products, cloud services like Microsoft 365 and Azure, as well as certain on-premises server and client licenses, often with Software Assurance benefits such as upgrade rights, training vouchers (historically), and planning services. For enterprises, the primary benefits include volume discounts, price protection for the term of the agreement, centralized asset management, and the ability to standardize technology across global subsidiaries. 

Pricing and negotiations are usually handled directly with Microsoft or through a Licensing Solution Provider (LSP), and costs depend on the following factors:

• product mix
• user count
• geographic footprint
• strategic commitments (for example, shifting workloads to Azure)

Successful negotiations often involve careful analysis of current usage, projected growth, and alternative purchasing models, such as CSP, to ensure the agreement delivers both cost efficiency and long-term flexibility.

Explore the UDS Microsoft Licensing Services.

In 2026, Microsoft’s cloud purchasing framework is largely built around the Microsoft Customer Agreement (MCA) and the Cloud Solution Provider (CSP) program, which together define how most companies procure Microsoft 365, Azure, Dynamics 365, and Power Platform services. 

Under the CSP model, customers purchase cloud subscriptions through an authorized Microsoft partner rather than directly from Microsoft, allowing for delegated management, advisory support, and consolidated billing. 

There are two primary partner structures: 

• Direct (Tier 1) resellers

They transact directly with Microsoft and manage billing and support infrastructure themselves

• Indirect (Tier 2) resellers

They work through an authorized distributor that handles Microsoft relationships, provisioning infrastructure, and sometimes credit facilities. For customers, the operational difference is usually invisible, but it can affect pricing flexibility, support depth, and escalation paths.

CSP licensing typically offers subscription-based billing with monthly or annual commitment terms under the New Commerce Experience (NCE), where annual subscriptions may provide lower pricing, but reduced mid-term flexibility compared to month-to-month plans. 

Azure services under CSP are generally billed based on actual consumption, while seat-based products like Microsoft 365 follow per-user subscription pricing. 

The benefits of CSP include agility (the ability to scale licenses up quickly), partner-led support, simplified billing across multiple services, and access to managed services bundles. 

However, limitations may include less direct negotiation leverage with Microsoft compared to large Enterprise Agreements, potential partner margin impact on pricing, and stricter cancellation or reduction policies under annual terms. 

Overall, CSP and MCA-based agreements are designed to support cloud-first, subscription-driven IT strategies with scalable, operationally flexible licensing structures.

Microsoft Dynamics 365 plays a central role in Microsoft’s cloud ecosystem in 2026, combining CRM and ERP capabilities into modular, subscription-based applications. Unlike traditional monolithic CRM systems, Dynamics 365 is licensed per application, per user, allowing companies to pay only for the specific business functions they require.

One of the most widely adopted segments is Customer Engagement (CE), which focuses on sales, marketing, customer service, and field operations.

Dynamics 365 Sales

It is licensed per user (or per device for Enterprise) and available in multiple editions:

• Sales Professional

It provides core sales force automation capabilities for basic sales process support without advanced customization or extensibility.

• Sales Enterprise

It adds advanced sales-process automation, customization, extensibility, and embedded intelligence. Includes Copilot in Dynamics 365 Sales for AI-assisted workflows. Enterprise also automatically includes an entitlement to 2,000 Customer Voice responses per tenant per month.

• Sales Premium

It builds on Enterprise by adding more advanced AI-powered sales insights and automation, including further Sales Insights capabilities and enhanced Copilot experiences.

• Additional licensed capabilities

Sales Insights

They may be included or added (features like predictive scoring, conversation intelligence, assistant studio); availability depends on the specific Sales license edition.

Device licenses

They are enterprise licenses that can also be assigned to devices instead of named users.

! Note. All licensed users can access sales data, mobile and web clients, and integrations (such as Outlook). Specific rights vary by edition (for instance, customizations and extensive analytics require Enterprise or Premium).

Dynamics 365 Customer Service

It is licensed per user and available in these editions:

• Customer Service Professional

It provides core case management functionality designed for smaller support teams. Advanced capabilities, such as resource scheduling, unified routing, and deeper analytics, are available in the Customer Service Enterprise and Premium editions.

• Customer Service Premium

It combines Enterprise with a Copilot-first contact center (digital + voice) and generative AI support.

• Customer Service Add-ons

Licensed users with Enterprise can purchase Dynamics 365 Contact Center Digital or Contact Center Voice add-ons, or the combined Contact Center bundle, to support omnichannel engagement and license call center agents in Dynamics 365.

• Device licenses

They are available for shared device scenarios, granting the same feature rights as Enterprise, but specific to the device.

! Note. Licensed users can access customer records, manage service cases, use mobile and Outlook clients, and perform key service operations consistent with their edition.

Dynamics 365 Field Service

Dynamics 365 Field Service focuses on work order management, scheduling, and mobile service operations. It is licensed per user (and per device) to empower field operations teams with service task automation and integration with case management.

Field Service licenses include such core capabilities as the following:

• access to mobile work order applications
• work order and asset management
• scheduling and resource optimization
• integration with Dynamics 365 Customer Service

Additional related solutions are available to extend Field Service functionality:

• Dynamics 365 Guides
• Dynamics 365 Remote Assist

Licensing automatically includes 2,000 Customer Voice responses per tenant per month:

• Field Service Contractor licenses

These are scaled-down user licenses intended for non-employee workers needing essential field service work order functionality. They require an existing Field Service license to purchase.

• Field Service Device licenses

They are available for shared machines or mobile scenarios.

• Add-ons

Resource Scheduling Optimization is an add-in licensed per resource that automates scheduling by optimizing technician assignments and work order routes.

• Field Service Full User

It is a full-access license intended for technicians, dispatchers, and service managers who require complete functionality, including work order management, scheduling, asset management, and advanced configuration capabilities.

! Note. Team Member licenses can be used for limited access scenarios across Dynamics 365 applications, including Field Service.

! Note. Some Dynamics 365 licenses may include a limited entitlement for Microsoft Customer Voice responses. The exact number depends on the specific license and current Microsoft terms.

! Note. Licensed users can access field service tasks through web, mobile, and Teams integrations (e.g., Remote Assist). They can create/read and update work orders and resource schedules appropriate to their security role.

Dynamics 365 Customer Insights

They are licensed per tenant, not per named user, which distinguishes them from other D365 applications.

A Customer Insights subscription includes rights to two bundled applications:

• Customer Insights – Data

It is a customer data platform (CDP) that unifies customer data for insights.

• Customer Insights – Journeys

It is a tool for real-time orchestration of the customer journey across channels.

Each tenant license includes base capacity:

• 10,000 Interacted People (for engagement and journey automation)
• 100,000 Unified People (for profile unification/data platform)
• 2,000 Customer Voice responses per tenant per month
• Unlimited environments for installing or usage (production or sandbox).

Companies with at least 10 seats of certain qualifying Dynamics 365 products can license Customer Insights as an attach license at potentially different pricing, retaining the same default capacity entitlements.

Customers can purchase additional Interacted People and Unified People capacity packs to scale beyond base limits.

! Note. Licensed tenants can unify customer profiles and orchestrate journeys across channels, gaining insights to personalize experiences and integrate data across sales, service, and marketing touchpoints.

Each of these applications is licensed primarily on a per-user subscription basis, with pricing tiers typically divided into these:

• Full (Base) licenses

They provide complete functionality for a primary application.

• Attach licenses

They discounted licenses for additional apps assigned to the same user who already holds a qualifying base license.

! Note. This “base + attach” model is one of the most important cost-optimization mechanisms in Dynamics 365 licensing. For example, a user licensed with Dynamics 365 Sales Enterprise as a base license can add Customer Service or Field Service at a significantly reduced attach price, avoiding the need to purchase multiple full licenses.

Common Dynamics 365 CE Licenses and Descriptions

Dynamics 365

Power Platform

Microsoft 365

Security & Compliance

Copilot

CE User Types and Access Models

Dynamics 365 CE also distinguishes between different levels of access:

• Full Users

They are a good match for sales representatives, service agents, or managers requiring broad functionality.

• Team Member licenses

They are lower-cost licenses designed for light users who need limited access (e.g., read access, basic updates, approvals).

• Device licenses

They are used in shared-device scenarios such as call centers or front desks.

• Activity or capacity-based licenses (in specific workloads).

Choosing the correct user type is critical to avoid over-licensing expensive enterprise editions for users who only need minimal functionality.

Dataverse and Capacity Licensing

All Dynamics 365 CE applications run on Microsoft Dataverse, which provides the underlying data platform, automation, and integration framework.

Dataverse capacity is calculated based on base tenant allocation plus additional capacity granted through user licenses.

! Note. Companies can purchase additional database, file, or log capacity if their usage exceeds the included limits.

! Note. Capacity planning should therefore be part of every Dynamics 365 licensing assessment to prevent unexpected cost overruns.

Integration with Power Platform and AI

Dynamics 365 CE is deeply integrated with the Microsoft Power Platform, including Power Apps, Power Automate, and Power BI.

In many cases:

• Dynamics 365 licenses include limited Power Platform usage rights.
• Advanced automation or custom applications may require additional Power Apps or Power Automate premium licenses.
• AI-driven capabilities (such as predictive scoring, Copilot features, and analytics enhancements) may require premium tiers or add-ons.

In 2026, AI-enabled features across Sales and Customer Service are increasingly embedded into higher-tier plans, reinforcing the importance of selecting the correct edition (e.g., Professional vs. Enterprise) based on business requirements.

Deployment Scenarios: Online vs Hybrid

Most new deployments are cloud-based (Dynamics 365 Online), licensed strictly via subscription. However, some companies still maintain hybrid or on-premises environments.

In such cases:

• On-premises server licenses may require Server + CAL models.
• Transition scenarios may involve dual-use rights or Software Assurance benefits.
• Migration planning should account for license conversion paths to cloud subscriptions.

Licensing Optimization Best Practices for Dynamics 365 CE

To optimize Dynamics 365 CE licensing in 2026, companies should perform these actions:

• Map each business role (sales rep, manager, service agent, executive) to the appropriate license level.
• Leverage attach licensing wherever possible.
• Monitor Dataverse capacity consumption regularly.
• Review inactive users and reallocate licenses (license harvesting).
• Align Power Platform usage with Dynamics entitlements to avoid unnecessary duplication.

Because Dynamics 365 licensing combines user subscriptions, capacity entitlements, AI add-ons, and Power Platform rights, it is often more complex than Microsoft 365 licensing and requires structured planning.

When properly aligned with business processes, however, Dynamics 365 CE licensing provides a scalable, modular, and cost-efficient CRM foundation that integrates seamlessly with the broader Microsoft ecosystem in 2026.

Maintaining licensing compliance is critical in 2026, as companies that fail to adhere to Microsoft’s licensing terms risk costly penalties, audit findings, or service disruptions. 

Common compliance risks include the following:

• under-licensing users or devices 
• misclassifying users or devices between User and Device CALs 
• using unlicensed virtual environments
• exceeding the permitted number of installations for a given subscription 

Microsoft may conduct license verification or formal compliance audits. Software Asset Management (SAM) engagements are typically advisory programs designed to help companies assess and optimize their licensing position. 

To avoid surprises, companies should implement best practices for license tracking, such as maintaining up-to-date inventory of all software installations, regularly reconciling subscriptions and CALs, and monitoring license consumption across both on-premises and cloud environments.

A variety of tools and reporting solutions can simplify compliance management. For example, Microsoft provides the Microsoft 365 admin center and Azure Cost Management + Billing dashboards to monitor subscriptions, usage, and assignments, while third-party SAM tools can automate tracking for server licenses, CALs, and hybrid deployments. Periodic internal audits, combined with automated license reporting, help companies proactively identify under- or over-utilized licenses, optimize costs, and ensure adherence to Microsoft’s licensing rules, reducing the risk of penalties while supporting effective IT governance.

Microsoft subscription licenses are available through three main purchasing options:  

1. Annual commitment – paid upfront   
   You pay the full annual amount in advance. Excluding any financing considerations, this is the most cost-effective option for purchasing Microsoft licenses.  
2. Annual commitment – paid monthly   
   You commit to a 12-month term but pay in monthly installments. The monthly price is 5% higher than the “annual upfront” rate. Although you pay monthly, you are still committed to the full 12 months. Overall, this option costs about 6% more annually than paying upfront (excluding financing costs). 
3. Monthly commitment – paid monthly   
   You commit on a month-to-month basis, paying each month in advance. The monthly cost is 20% higher than the annual upfront rate. This is the most expensive option overall (excluding financing costs), which limits your commitment to one month at a time, reducing long-term exposure.

Effective cost management is a critical component of Microsoft’s licensing strategy in 2026, as subscription and volume-based models can quickly become expensive if not actively managed.

The most effective strategies include these ones:

• Rightsizing licenses

It involves assigning the correct license type and level to each user based on their actual needs, for example, ensuring frontline workers use Microsoft 365 F1/F3 plans rather than more expensive E3/E5 subscriptions, or switching users who only need web-based apps to Business Basic instead of Standard. 

• License harvesting

It identifies inactive or underutilized licenses within the organization and reallocates them to users who need them, rather than purchasing new subscriptions unnecessarily. Microsoft provides Licensing Advisors and official consultants who can analyze your current licensing footprint, recommend optimizations, and guide negotiations for Enterprise Agreements or CSP subscriptions to ensure both compliance and cost efficiency. 

• Leveraging Software Asset Management (SAM) tools, such as Microsoft’s own SAM offerings or third-party solutions 

It enables continuous monitoring of license usage, automates tracking across on-premises and cloud environments, and provides actionable reports to forecast needs, optimize subscriptions, and prevent over-purchasing. 

By combining these strategies, companies can significantly reduce unnecessary licensing spending while maintaining full compliance and supporting workforce productivity.

Learn about our Microsoft License Calculator.

Even experienced IT teams can make costly errors when managing Microsoft licensing, so it is essential to be aware of common pitfalls and actively avoid them. 

The list of frequent mistakes usually includes the following:

• Overbuying unused licenses 

It often happens when companies purchase subscriptions based on projected growth rather than actual usage, leaving many licenses idle and wasting budget. 

• Misclassifying users or devices

 An example may be assigning Device CALs to users who regularly work on multiple devices.

• Giving high-tier enterprise licenses to employees who only need basic functionality 

It often leads to unnecessary costs. 

• Ignoring cloud benefits

It leads to failing to take advantage of subscription-based scalability, bundled services, and continuous feature updates that can reduce the need for separate on-premises solutions. 

• Misunderstanding of Client Access Licenses (CALs)

It also includes the cases when a user or device of CAL is required, or how external users are licensed, and can result in compliance risks and unexpected audit findings. 

Avoiding these mistakes requires careful planning, ongoing monitoring, and regular review of both license assignments and usage patterns to ensure efficiency, compliance, and cost optimization.

Address our Microsoft Licensing Services.