What Planning Services Actually Are
Planning Services — formerly called Planning Vouchers, now delivered under the Planning Agreement framework — are pre-funded consulting days included with specific Software Assurance products. When you purchase SA on qualifying server products or certain desktop suites, Microsoft credits your VLSC account with a defined number of days that a Microsoft-qualified partner must redeem against structured advisory workshops before the SA period ends.
The workshops are not implementation engagements. Microsoft restricts them to pre-deployment planning activities: architecture scoping, migration readiness assessments, security baseline reviews, cloud adoption strategy sessions, and technology proof-of-concept planning. The partner delivers the workshop; Microsoft underwrites the cost from the SA licence fee you already paid. You pay nothing additional at point of delivery.
This is a meaningful benefit when correctly activated. A qualified Planning Services engagement from a Microsoft Certified Solutions Provider typically costs £8,000–£22,000 in the open market per three to five days depending on complexity. Under SA, that cost is already embedded in your licence investment. The problem — and it is widespread — is that roughly 40% of entitled enterprises never claim these days before they expire.
Which SA Products Generate Planning Days
Not every Software Assurance purchase generates Planning Services entitlements. The benefit is attached to specific server products and select desktop suites. As of 2026, the primary qualifying products are:
| Product | Planning Services Generated | Day Allocation | Notes |
|---|---|---|---|
| SQL Server Enterprise Edition | Yes | 5 days per 2-licence set | Most commonly claimed for Azure SQL migration planning |
| SQL Server Standard Edition | Yes | 3 days per 4-licence set | Often overlooked for smaller SQL environments |
| Windows Server Datacenter | Yes | 5 days per 2-core pack set | Frequently applied to Azure Arc or hybrid cloud planning |
| Windows Server Standard | Yes | 3 days per 4-core pack set | Low per-licence yield; accumulates in large estates |
| SharePoint Server | Yes | 3–5 days depending on edition | Migration to SharePoint Online planning primary use case |
| Exchange Server | Yes | 3–5 days depending on edition | Exchange Online migration scoping most common application |
| Microsoft 365 Apps (desktop) | Limited | Varies by agreement | Not all M365 agreements include Planning Services; verify in VLSC |
| Office Standard / Professional Plus | Typically No | – | Perpetual Office SA rarely generates Planning Services in current agreements |
The exact day allocation depends on the volume of licences under SA, not a flat per-product entitlement. A customer running 200 Windows Server Datacenter 2-core packs under SA accumulates significantly more Planning Services days than one running 20. Check your current entitlement balance in the VLSC Benefits portal under Software Assurance → Benefits Summary → Planning Services.
Categories of Planning Services Engagements
Microsoft maintains an approved catalogue of Planning Services engagement types. Partners must deliver from within this catalogue — they cannot use the days for custom engagements outside the defined scope. The primary categories as of 2026 include:
Cloud Adoption Planning
The most frequently claimed category. Covers Azure migration readiness assessments, landing zone architecture reviews, workload migration prioritisation, and hybrid cloud integration planning. Particularly relevant for organisations under active pressure from Microsoft account teams to increase Azure MACC commitments — a Planning Services engagement provides validated scope before the commercial conversation, strengthening your negotiating position. See the Azure MACC negotiating leverage guide for how pre-engagement scoping integrates with MACC negotiation.
Security and Compliance Planning
Covers Microsoft Defender for Endpoint deployment planning, Purview Information Protection architecture, Zero Trust implementation roadmapping, and Sentinel architecture scoping. High value for organisations evaluating security licence upgrades, because the engagement output should inform whether an E5 or standalone security add-on investment is warranted before purchase — not after. Reference the Microsoft security licensing guide for the pre-purchase evaluation framework.
Application Portfolio Management (App Cat)
Application Compatibility Testing (App Cat) and modernisation planning engagements. Relevant for organisations planning Windows 11 migrations, Office upgrades, or application rationalisation ahead of EA renewal. Outputs typically include a compatibility assessment report and a prioritised modernisation roadmap — both useful artefacts for contract negotiations where Microsoft is pushing desktop upgrade steps.
Modern Workplace Planning
Covers Microsoft Teams deployment planning, Exchange Online migration strategy, SharePoint Online governance design, and Microsoft Viva adoption planning. The most common use case is scoping a Teams Phone deployment before committing to Calling Plan or Operator Connect licences at renewal.
Data Platform and AI Planning
SQL Server migration to Azure SQL, Azure Synapse Architecture planning, Microsoft Fabric adoption readiness, and Power BI Premium capacity scoping. Particularly relevant for organisations evaluating the cost case for SQL Server SA renewal vs. Azure SQL migration. The SQL Server Azure vs on-premises cost analysis explains how Planning Services outputs feed into this commercial decision.
The Redemption Process: How Planning Services Actually Work
The Planning Services redemption process involves four parties: the customer (you), Microsoft (VLSC), a Microsoft-qualified planning partner, and the Planning Services programme administration. The sequence is:
Step 1: Verify your entitlement balance. Log into the VLSC at https://www.microsoft.com/Licensing/servicecenter. Navigate to Software Assurance → Benefits → Planning Services. The system shows your available day balance, the expiry date (tied to your SA anniversary or end date), and any previously redeemed engagements.
Step 2: Identify a qualified partner. The partner must be registered in the Microsoft Partner Network as a Planning Services-qualified partner for the specific service type you want. Not all Microsoft partners are qualified for all engagement types. Use the Microsoft Solutions Provider search to filter by Planning Services capability.
Step 3: Create a voucher. In the VLSC, create a Planning Services voucher specifying the engagement type, the number of days, and the partner. This generates a voucher code that you provide to the partner. The voucher must be issued before your SA expiry date.
Step 4: Partner delivers the engagement. The partner conducts the workshop within the VLSC-specified timeframe (typically 180 days from voucher creation). At completion, the partner submits proof of delivery. Microsoft releases payment to the partner from the SA benefit pool — you receive no invoice.
The voucher must be created in the VLSC before your SA expiry date, but the engagement itself can be delivered after expiry within the 180-day redemption window. This is the most commonly misunderstood aspect of Planning Services. If your SA expires in June, you can issue a voucher in May for a workshop scheduled in August — but you cannot issue a voucher in July for an expired SA period.
Commercial Traps: When Partners Misuse Planning Days
Planning Services creates a specific commercial conflict of interest that procurement teams should understand. The partner delivering the engagement is paid by Microsoft from the SA benefit pool — but the partner's commercial interest is to convert the engagement into a paid implementation project. This creates pressure to scope engagements that identify complexity requiring follow-on work, rather than engagements that provide the most useful pre-decision analysis for the customer.
Three patterns to watch for:
Scope inflation. Partners sometimes propose multi-day engagements for straightforward activities that could be completed in one day, consuming your entire Planning Services balance on a single topic and leaving no days for other SA benefits. Counter by pre-defining the engagement deliverables and time allocation before issuing the voucher.
Implementation framing. Planning Services engagements must be pre-implementation activities. A partner who uses the days to begin configuration, testing, or deployment is misusing the benefit. If the partner produces a Statement of Work for implementation services as a direct output of the Planning Services engagement, treat this as a flag — good advisory planning should produce a roadmap and a business case, not a vendor's pre-drafted implementation SOW.
Voucher pressure at renewal. Microsoft account teams sometimes encourage customers to redeem Planning Services days quickly through a preferred partner at EA renewal — often the same partner who is also acting as the Microsoft reseller. An independent advisory position for your EA negotiation is compromised if the partner delivering your pre-renewal planning is commercially aligned with the transaction. The independent vs. aligned adviser framework explains how to evaluate this conflict.
When Planning Services Deliver Real Value
Planning Services benefits are worth activating when three conditions are met: (1) you have an active workload migration, consolidation, or technology decision in the relevant area, (2) your internal team lacks the specific Microsoft platform expertise to scope the decision independently, and (3) you can identify a partner with genuine delivery capability rather than a Microsoft-aligned reseller using the engagement as a sales discovery exercise.
The highest-ROI activations in 2026 are SQL Server Azure migration planning for organisations actively evaluating SA renewal vs. cloud migration (where the planning output directly informs a $100K–$500K commercial decision), Zero Trust and Sentinel architecture scoping for organisations evaluating E5 upgrades (where a validated-scope architecture prevents buying capabilities you will not deploy), and Exchange Online migration planning for organisations still running on-premises Exchange with expiring SA.
Planning Services days have no cash redemption value. You cannot convert unclaimed days to credit against future licence costs. They expire at SA boundary. The only question is whether you claim them or let Microsoft retain the value you already paid for.
For a comprehensive view of all SA benefits and how to prioritise them across a renewal cycle, see the complete Software Assurance benefits guide for 2026 and the SA ROI calculation framework.
If you are negotiating a Software Assurance renewal and are uncertain about the value of SA for specific product lines, unclaimed Planning Services days are a concrete data point: your organisation has consistently failed to extract this funded benefit, which weakens the ROI case for renewing SA at current price levels. Use it as part of the SA removal decision framework or as leverage for price concession at renewal.