Most 2027 IT budgets were drafted before Microsoft finished announcing its 2027 price changes. Between September 9 and November 11, 2026, Microsoft told customers and partners about higher Azure rates in seven regions, a new default for Copilot billing, a Power Apps price increase and currency adjustments, all taking effect between January 1 and the end of March. Add the end of Windows Server 2016 support on January 12 and you have a single quarter that touches infrastructure, collaboration and licensing at once. This checklist puts the dates in order and lists what to decide before each one.
Why bother? A survey commissioned by Origina, an independent software maintenance company, found that large US and UK organizations spend about 28% of their software budgets, close to $12.9 million a year on average, on initiatives their vendors push, as CIO.com reported. Origina sells an alternative to vendor support, so read the number with that in mind. The point holds anyway: costs you don’t plan for end up planned by someone else.
The Microsoft 2027 price calendar at a glance
- January 1, 2027: Power Apps Premium goes from $20 to $22 per user per month, and from $12 to $14 on the 2,000-seat plan. Local-currency cloud prices change in five currencies.
- January 12, 2027: Windows Server 2016 reaches the end of extended support.
- January to March 2027: usage-based billing is switched on by default for new Microsoft 365 Copilot Business purchases through CSP.
- February 1, 2027: Azure VM and storage prices rise by 8% to 17% in seven regions, and reservation exchanges end for services covered by savings plans.
Azure: region now sets the price
According to the Azure Service Health notice Microsoft sent in early October, quoted in a Microsoft Q&A thread, VM and storage prices rise on February 1 by 17% in North Europe (Dublin), 11% in France Central and France South, 9% in West Europe (Amsterdam), Norway East and Norway West, and 8% in Southeast Asia (Singapore). The v1, v2 and v7 VM series are excluded, along with several storage services such as General Block Blob, Tables and Queues. Techzine notes that the widely used v4, v5 and v6 D and E series are in scope.
The money is easy to model. LicenseQ calculates that €10,000 a month of eligible spend costs an extra €10,800 a year in West Europe and €20,400 a year in North Europe. Some partners also report a separate rise of about 25% for v1 and v2 VMs, but the advisory doesn’t mention it, so treat that figure as unconfirmed.
Commitments protect you less than you might think. Per MetrixData and Techzine, reservations bought before February 1 keep their rate for the term (for compute), while savings plans keep the hourly commitment but buy less capacity once the underlying rates go up. After February 1, new reservations for savings-plan-eligible services can no longer be exchanged.
- Pull a cost report by region and VM series and flag anything in the seven regions.
- Decide on reservations before February 1, while the current rate and exchange terms still apply.
- Check storage accounts against the exclusion list; anything not listed should be budgeted at the new rate.
- For workloads without data residency constraints, compare a move to an unaffected region or to v7 series against the migration effort.
Copilot: consumption billing becomes the default
On November 3, Microsoft’s Partner Center announcements moved the date: usage-based billing will be on by default for new Copilot Business subscriptions bought through CSP during Microsoft’s fiscal Q3 (January to March 2027), not December 1 as first announced. The default spending limit is 4,000 Copilot Credits per user per month. One detail matters a lot: a new purchase also turns usage-based billing on for the existing Copilot Business licenses in the same tenant. MetrixData puts the credit at one cent, which means up to $40 per user per month at the default limit.
Microsoft’s cost management documentation adds another default to check. The “Auto-apply new services” setting is on for spending policies, so new Copilot services inherit your limits automatically. Separately, since November 2 for organizations with up to 2,000 seats and November 9 for larger ones, users without a Copilot license hit fair-use limits in Copilot Chat. Microsoft doesn’t publish those limits, and the notice users see usually offers an upgrade path. Expect license requests to climb.
- Set per-user and per-group limits below the default before any new Copilot Business purchase.
- Review whether auto-apply should stay on, and give finance read-only access to the consumption dashboard.
- Decide who approves license requests and whether self-service purchases stay enabled.
Power Apps, currencies and Windows Server 2016
The Power Apps Premium increase, announced on September 9, applies to new purchases, renewals and co-terminations with terms starting on or after January 1. Existing subscriptions keep their price until the term ends, so renewal timing is a real lever. Count your Premium seats and check which renewals fall just after the change.
If you buy in local currency, the November 11 Partner Center update lists the January 1 cloud adjustments: +15.7% in Indian rupees, +10% in New Zealand dollars, −4% in Australian dollars, −5.9% in Norwegian krone and up to −8.5% in Chinese yuan. Global teams paying in those currencies should update their forecasts.
Finally, the Microsoft Lifecycle page shows Windows Server 2016 extended support ending on January 12, 2027, with paid Extended Security Updates listed for up to three years. Any server you can’t migrate in time needs an ESU line in the budget.
Give the whole quarter one owner
None of these changes is large in isolation. Together they land in the same quarter, owned by different teams, and two of them (reservation exchanges and Copilot billing defaults) reward decisions made before the date rather than after. Put one person in charge of the calendar, attach an action to each date and review progress in December. If you want help mapping your Azure footprint or modeling Copilot consumption before the changes hit, talk to the Luby team.
