# Server Refresh, ESU or Azure: Renewal Decision Assessment

> A fixed-price, one-week decision assessment for the moment a hardware-refresh quote, a hosting or support renewal, or an Extended Security Updates (ESU) bill lands on a Windows Server or SQL Server estate. IT Partner takes your inventory — your own export or the output of our Azure Migrate assessment — establishes your real licensing position, groups the servers into decision groups, and builds a three-year total-cost model per group across five paths: refresh on-premises, renew the hosting or support you have, bridge on ESU, move to Azure, or move to Azure Local. Azure Hybrid Benefit, Microsoft's current ESU rules — including the April 2026 change that ended free ESU on Azure for the 2016 generation — and Microsoft migration-funding eligibility are applied only where they genuinely apply. You get a one-page decision matrix, a recommendation memo written for the CFO, and a sequenced next step. $1,950 fixed for estates of up to 50 servers; larger estates are quoted per estate. Microsoft's own charges — ESU fees, Azure consumption, licenses — are yours and are never bundled into this fee.

Canonical: https://o365hq.com/services/server-refresh-esu-or-azure-decision-assessment
Provider: IT Partner LLC — US Microsoft partner since 2006. Book: https://o365hq.com/book

**Price:** $1,950 per project · **Duration:** 1 week · Fixed price, pay after approval.

## Overview

The decision usually arrives as somebody else's paperwork. The hardware vendor's refresh quote. The colocation or hosting provider's renewal. The support contract's auto-renew notice. A Microsoft quote for Extended Security Updates. Each one answers its own question — should you buy this? — and none of them compares the paths against each other. Meanwhile the calendar is not neutral: per Microsoft's product lifecycle, Windows Server 2012 R2's ESU program ended on 13 October 2026, SQL Server 2016 left extended support on 14 July 2026 (ESU available through July 2029), and Windows Server 2016 leaves extended support on 12 January 2027 (ESU available through January 2030). Estates built around the 2016 generation are about to get a bill for standing still, and the people writing the refresh quote know it.

The rule most advice still gets wrong: from 1 April 2026 Microsoft applies the same ESU list price regardless of deployment location — Azure, on-premises or another cloud — and regardless of purchasing channel, for ESU offerings released on or after that date, Windows Server 2016 and SQL Server 2016 included (Microsoft's pricing-consistency notice of 27 March 2026). The older rule, ESU at no additional charge on top of the VM cost, survives only for the earlier programs the notice excludes — Windows 10 version 22H2 and SQL Server 2014 (and Windows Server 2012 and 2012 R2, until that program ended on 13 October 2026). For Windows Server 2016 and SQL Server 2016, "move it to an Azure VM and the ESU is free" is advice from before April 2026, and a model built on it will mislead your CFO by a real number. Microsoft's Arc documentation at the time of writing still names Azure VMware Solution and Azure Local VMs as entitled without an Arc enrollment, while its Azure Local documentation places Windows Server 2016 under the new pricing; where Microsoft's documents differ we print the safer reading — budget for the charge — and confirm the current rule for your platform at kickoff. What still moves the number is more specific: Azure Hybrid Benefit for Windows Server and SQL Server licenses with active Software Assurance or subscription; Datacenter edition's dual-use rights during a migration; SQL Server Enterprise cores converting to Azure SQL vCores; ESU charges that stop automatically the moment a database lands in Azure SQL; and monthly pay-as-you-go ESU through Azure Arc that you switch off server by server as you migrate — with Microsoft's back-billing rules for late enrollment modeled honestly, because they bite.

So we build the comparison the vendors will not. Your inventory — a CMDB or hypervisor export, or the output of our [Azure Migrate discovery and assessment](/services/azure-migration-discovery-assessment) if you do not trust what you have — is reconciled and grouped into decision groups: the SQL Server 2016 estate behind the ERP, the 2012 R2 domain controllers, the file and print servers, the twelve application servers nobody has touched since 2019. Your licensing position is established from documents, not memory: editions, core counts, Software Assurance or subscription status, agreement type, expiry dates, and what each of those means for Azure Hybrid Benefit and ESU eligibility. Then each group is costed over three years across five paths — refresh on-premises, renew the hosting or support you have, bridge on ESU, move to Azure, or move to Azure Local — on Microsoft's published pricing on the delivery date, with every assumption written down. The output is a one-page decision matrix, a recommendation memo written for the finance leader who signs, and a walkthrough with the consultant who built the model.

This is a decision assessment, deliberately narrow. It is not the tool-driven discovery that measures utilization and dependencies — that is the [Azure Migrate assessment](/services/azure-migration-discovery-assessment), and its output feeds this one. It is not cost optimization of Azure you already run — that is the [Azure Cost Optimization and FinOps Assessment](/services/azure-cost-optimization-finops-assessment). It is not Azure design, license procurement or execution of any path; each of those is its own scoped engagement, and the memo names which one comes next. What it is: the week in which somebody with no commission on the outcome puts refresh, renew, ESU, Azure and Azure Local side by side, per server group, in numbers a CFO can check.

## Success criteria

- Every in-scope server is reconciled into a named decision group with its operating system and SQL Server version, edition, core count, host, role and the end-of-support or ESU date that applies to it.
- Your licensing position is documented from evidence — agreement type, editions, core licenses, CALs, Software Assurance or subscription status and expiry — with Azure Hybrid Benefit and ESU eligibility flagged per group and gaps named rather than assumed away.
- A three-year total-cost model exists per decision group across all five paths, on Microsoft's published pricing on the delivery date, with every assumption on its own tab and changeable by your finance team.
- ESU is modeled to Microsoft's current rules: per core, the 16-physical-core and 8-virtual-core minimums for Windows Server and the four-core-per-instance minimum for SQL Server, Microsoft's per-year pricing (at the time of writing the full license price in each of years one, two and three through Volume Licensing, with years two and three purchasable only after the prior years), Volume Licensing versus monthly Azure Arc billing, and back-billing for late enrollment — including Microsoft's 1 April 2026 pricing-consistency rule, under which ESU for Windows Server 2016 and SQL Server 2016 carries the same list price in Azure as anywhere else.
- Azure Hybrid Benefit is applied only where your license position qualifies, with the Standard-versus-Datacenter dual-use rules, the 180-day migration window and SQL Server core conversion stated wherever they change the number.
- Microsoft migration-funding eligibility is assessed and written up as assessed — never assumed into the model — with what would be needed to pursue it.
- A one-page decision matrix and a recommendation memo for the CFO exist: one verdict, one three-year number, one risk statement and one next step per decision group, plus the cost of doing nothing.
- The consultant who built the model has walked you through it, answered your finance team's challenges, and delivered fixed written quotes for any next step you asked about.

## Deliverables

- Decision-group inventory workbook: every server assigned to a group with operating system and SQL Server version, edition, cores, host, role, the dependencies you told us about, and the lifecycle date that applies.
- Licensing position statement: Windows Server, SQL Server and CAL entitlements by edition and program, Software Assurance or subscription status and expiry, and per-group Azure Hybrid Benefit and ESU eligibility flags with the evidence behind each.
- Three-year total-cost model (editable workbook): five paths per decision group, an assumptions tab, a pricing-source tab dated to the delivery date, and a sensitivity view for the two or three assumptions that swing the answer.
- ESU exposure schedule: which servers reach which date, the ESU cost curve year by year per group, the last responsible date to start each alternative, and what late enrollment would cost under Microsoft's back-billing rules.
- Decision matrix — one page: decision groups down the side, five paths across, three-year totals and a written verdict in every cell.
- Recommendation memo for the CFO: two to four pages in finance language — recommended path per group, cash and operating-expense view over three years, commitment and exit risks, the do-nothing cost, and the sequence of next steps with their fixed quotes where we provide them.
- Microsoft funding eligibility note: which of Microsoft's current partner-led migration programs your estate plausibly fits, what evidence Microsoft would require, and a plain statement that the model does not depend on it.
- Findings walkthrough with the consultant who built the model — up to 90 minutes, your finance team welcome.
- On request: fixed, written quotes for the next step — Azure Migrate discovery, Windows Server or SQL Server migration, Azure Arc onboarding for ESU delivery, an Azure landing zone, or Azure Local design — each a separate engagement you can accept, decline or take elsewhere.

## Implementation plan

1. **Day 1 — Intake and scoping** — Kickoff with your IT owner and finance contact. We collect the paperwork that triggered the decision — refresh quote, renewal notice, ESU quote — plus your inventory export, licensing documents and current run-cost invoices, and agree the decision groups and the assumptions we will use where you have no data.
2. **Days 1–2 — Inventory reconciliation and grouping** — Servers are reconciled against what you believe you own (the deltas are always instructive), assigned to decision groups by role, dependency and lifecycle date, and flagged where a group needs an Azure Migrate discovery before anyone should commit money to it.
3. **Days 2–3 — Licensing position** — Entitlements are established from agreements and license statements, not recollection: editions, core licenses, Software Assurance or subscription status and expiry. Each group gets its Azure Hybrid Benefit and ESU eligibility flags, with the Microsoft rule that decides them written next to the flag.
4. **Days 3–4 — Five-path cost modeling** — Each group is costed over three years on refresh, renew, ESU bridge, Azure and Azure Local using your quotes, Microsoft's published pricing on the delivery date and the stated assumptions. Funding eligibility is assessed alongside — and kept outside the base case.
5. **Day 5 — Matrix, memo and walkthrough** — The decision matrix and the CFO memo are written, reviewed with you, and walked through by the consultant who built the model. Fixed quotes for next steps follow on request; the decision is yours.

## Prerequisites

- A server inventory you can export — from a CMDB, vCenter or Hyper-V, an RMM tool, or the assessment output of our Azure Migrate discovery. If you do not trust your inventory, the Azure Migrate assessment comes first and this assessment reads its results.
- The paperwork that triggered the decision: the hardware refresh quote, the hosting or colocation renewal, the support-contract renewal, the ESU quote. We model against the real numbers you have been given, not our guess at them.
- Licensing evidence: your Volume Licensing statement or agreement summary, the Microsoft 365 admin center license view for CSP purchases, OEM and SPLA details where they apply, and Software Assurance or subscription expiry dates. Our [Windows Server licensing calculator](/tools/windows-server-calculator) and [SQL Server licensing calculator](/tools/sql-licensing-calculator) help you assemble the core counts.
- Current run costs where you have them — power, space or colocation, hosting, hardware support, backup and disaster-recovery contracts, and an honest estimate of staff time. Where you have none, we state an assumption and you can change it.
- A named IT owner and a finance contact available for two working sessions during the week; the memo is written for the second of them.
- An estate of up to 50 servers under the fixed fee. Windows Server 2012 R2 through 2022 and SQL Server 2012 through 2022 are in scope; Linux servers are inventoried and costed on the refresh and Azure paths, but the licensing analysis is Windows Server and SQL Server specific.
- For the Azure and Azure Local paths, a sense of your finance team's appetite for one- or three-year commitments and for capital versus operating expense — the model presents both; you choose.
- Willingness to hear a verdict that is not the one you walked in with: the assessment tells the truth per group, including "refresh it" and "switch it off".

## Responsibilities

**IT Partner:**

- Reconcile the inventory, define the decision groups and flag any group that needs tool-based discovery before a commitment.
- Establish the licensing position from evidence and state the Azure Hybrid Benefit and ESU rule that applies to each group, citing Microsoft's published terms.
- Build the five-path, three-year model on Microsoft's published pricing on the delivery date, with assumptions written down and changeable.
- Assess Microsoft funding eligibility honestly and keep it out of the base case.
- Write the decision matrix and the CFO memo in finance language, with verdicts that include the paths that earn us nothing.
- Walk you through the findings and provide fixed written quotes for next steps on request.
- Treat everything we see — contracts, quotes, licensing, inventory — as confidential.

**Client:**

- Provide the inventory export, the triggering quotes and renewals, licensing evidence and run-cost data by the agreed intake date.
- Make the IT owner and the finance contact available for the two working sessions.
- Answer the context questions the data cannot — which application depends on which server, which contract cannot be broken, which workload the regulator cares about.
- Attend the walkthrough and challenge the assumptions; the model is built to be argued with.
- Decide what happens next — with us, with another provider, or not at all. The memo serves all three.

## Not included

- Executing any path — migrations, upgrades, ESU enrollment, Azure Local deployment and hardware procurement are each separately quoted, fixed-price engagements: [Windows Server migration to Azure](/services/windows-server-migration-to-azure-from-physical-server), [VMware to Azure VM migration](/services/vmware-to-azure-migration), [Hyper-V to Azure VM migration](/services/hyper-v-to-azure-migration), [SQL Server migration to Azure SQL Managed Instance](/services/sql-server-migration-azure-sql-managed-instance), [Windows Server 2016 to 2025 upgrade](/services/windows-server-2016-to-2025-upgrade), [SQL Server 2016 in-place upgrade](/services/sql-server-2016-in-place-upgrade), [Windows Server ESU enrollment through Azure Arc](/services/windows-server-esu-enrollment-azure-arc), [SQL Server 2016 ESU enrollment through Azure Arc](/services/sql-server-2016-esu-enrollment-azure-arc) and [Azure Arc hybrid server management](/services/azure-arc-hybrid-server-management).
- Tool-based discovery — performance-based right-sizing and dependency mapping are the [Azure Migrate Datacenter Discovery and Assessment](/services/azure-migration-discovery-assessment); its output is the best input to this one, and the memo says if a group needs it before you commit.
- Product-specific technical roadmaps — the [Windows Server 2016 End of Support Assessment and Roadmap](/services/windows-server-2016-end-of-support-assessment) and the [SQL Server 2016 End of Support Options Assessment](/services/sql-server-2016-end-of-support-assessment) go deep on one product's upgrade path, application compatibility and sequencing. This page is the cross-estate finance decision that tells you which of them, if either, you need next.
- Engine-level SQL Server analysis — choosing between Azure VM, Managed Instance and Azure SQL Database database by database is the [SQL Server to Azure Migration Assessment](/services/sql-server-azure-migration-assessment).
- Designing the Azure foundation — networking, identity, governance and policy for a target environment are the [Azure Landing Zone implementation](/services/azure-landing-zone-cloud-adoption-framework-implementation); the memo says plainly when it is a prerequisite.
- Optimizing Azure you already run — that is the [Azure Cost Optimization and FinOps Assessment](/services/azure-cost-optimization-finops-assessment), with different evidence and a different discipline.
- Buying, renewing or truing up licenses — we state your position and what each path needs; procurement, agreement negotiation and true-up work are the [Microsoft Volume Licensing](/services/microsoft-volume-licensing-consulting) engagement, or a purchase through us at Microsoft's published list price.
- Microsoft's charges — Extended Security Updates, Azure consumption, Azure Local host fees, Windows Server and SQL Server licenses and Software Assurance are billed by Microsoft, or through a CSP partner at Microsoft's published price, to you. Nothing metered is inside this fee.
- Hardware quotes — we do not resell servers; we compare the quotes you hold and tell you what to ask the vendor for.
- Security assessment of whatever stays — if 2012 R2 domain controllers or unpatched servers remain after the decision, the [Active Directory Security Assessment](/services/active-directory-security-assessment) and a containment plan are separate work, and the memo will say so.

## Limitations & technical notes

- Lifecycle dates are stated per Microsoft's product lifecycle at the time of writing — Windows Server 2012 R2 ESU ended 13 October 2026; SQL Server 2016 extended support ended 14 July 2026 with ESU through July 2029; Windows Server 2016 extended support ends 12 January 2027 with ESU through January 2030. Microsoft's lifecycle pages are authoritative if they ever disagree with this page.
- The model is a decision-grade estimate on Microsoft's published pricing on the delivery date and the quotes you supply, with every assumption written down. It is not a guarantee of your future bill — Microsoft's prices, SKUs and programs change, and the meter is Microsoft's.
- ESU pricing: we apply Microsoft's published rules — per core; a 16-physical-core or 8-virtual-core minimum per Windows Server ESU license and a four-core minimum per SQL Server instance; through Volume Licensing, at the time of writing, the full license price in each of years one, two and three per Microsoft's Lifecycle FAQ, with years two and three purchasable only after the prior years; back-billing to the end-of-support date for late enrollment — and take dollar figures from Microsoft's price list on the delivery date. This page deliberately quotes no ESU dollar amounts.
- ESU eligibility: for Windows Server 2016 on-premises, Microsoft requires Software Assurance or an equivalent server subscription and does not offer the program through SPLA; SQL Server ESU can be bought monthly through Azure Arc without Software Assurance. Where your position does not qualify, the ESU column says so rather than pretending.
- ESU on Azure: from 1 April 2026 Microsoft applies the same ESU list price regardless of deployment location — Azure, on-premises or another cloud — and regardless of purchasing channel, for ESU offerings released on or after that date, Windows Server 2016 and SQL Server 2016 included (Microsoft's pricing-consistency notice of 27 March 2026); the no-charge rule on Azure, Azure VMware Solution and Azure Local survives only for the earlier programs the notice excludes — Windows 10 version 22H2 and SQL Server 2014 (and Windows Server 2012 and 2012 R2, until that program ended on 13 October 2026). Microsoft's Arc documentation at the time of writing still names Azure VMware Solution and Azure Local VMs as entitled without an Arc enrollment, while its Azure Local documentation places Windows Server 2016 under the new pricing — the documents differ, we print the safer reading and budget for the charge, and we confirm the current rule for your platform at kickoff. The model reflects this; if Microsoft changes the rule again, the assumptions tab is where it changes.
- Azure Hybrid Benefit depends on active Software Assurance or a qualifying subscription, a minimum of eight core licenses per Azure VM, and edition rules — Standard licenses run on-premises or in Azure but not both beyond a one-time 180-day migration window; Datacenter licenses allow simultaneous use during a migration. For Azure Local, Windows Server Datacenter licenses must cover every physical core, and Microsoft limits the benefit to its standard hyperconverged deployment type. We model what your position supports; commitment decisions are yours.
- Microsoft funding is assessed, never assumed: eligibility, scope and amounts belong to Microsoft, change by fiscal year and are not guaranteed. The base case never depends on it.
- The fixed fee covers estates of up to 50 servers in a single decision cycle; larger, multi-site or multi-entity estates receive a fixed written quote before anything starts.
- Inventory quality bounds the answer. Where your export cannot tell us utilization or dependencies, the memo says which groups need the Azure Migrate discovery before a commitment, and the Azure numbers for those groups carry stated headroom rather than false precision.
- The assessment tells the truth even when it costs us: some servers should be refreshed, some renewed, some bridged on ESU for a year, and some switched off. We sell migrations and we still write those verdicts, because a partner who thinks everything should move to Azure is a salesman.

## FAQ

### Which servers is this for — and how urgent is it?

Any Windows Server or SQL Server estate facing a dated decision. The dates, per Microsoft's product lifecycle: Windows Server 2012 R2's Extended Security Updates ended on 13 October 2026; SQL Server 2016 left extended support on 14 July 2026 and is already in its ESU period; Windows Server 2016 leaves extended support on 12 January 2027. Windows Server 2019 and 2022 estates use this assessment too, usually because a hardware refresh or a hosting renewal forces the question early. Urgency is per group: the memo gives each group a last responsible date to start the alternative, which is earlier than most people assume once migration or upgrade lead times are counted.

### Is ESU still free if we move the servers to Azure?

Not for the 2016 generation. From 1 April 2026 Microsoft applies the same ESU list price regardless of deployment location — Azure, on-premises or another cloud — and regardless of purchasing channel, for ESU offerings released on or after that date, Windows Server 2016 and SQL Server 2016 included (Microsoft's pricing-consistency notice of 27 March 2026), and Microsoft's SQL Server documentation states plainly that SQL Server 2016 on Azure VMs is not eligible for free ESU. The no-charge rule on Azure, Azure VMware Solution and Azure Local survives only for the earlier programs the notice excludes: Windows 10 version 22H2 and SQL Server 2014 (and Windows Server 2012 and 2012 R2, until that program ended on 13 October 2026). For Windows Server 2016 VMs on Azure VMware Solution and Azure Local, Microsoft's Arc documentation at the time of writing still names them as entitled without an Arc enrollment while its Azure Local documentation places Windows Server 2016 under the new pricing, so we budget for the charge and confirm the rule at kickoff. Plenty of advice written before April 2026 still says otherwise; our model reflects the current rule and cites it, because a CFO who discovers the difference after the migration will not care whose article it was.

### How is ESU priced?

Per core, at a price Microsoft publishes per program year — at the time of writing Microsoft's Lifecycle FAQ prices on-premises and hosted ESU at the full license price in each of years one, two and three, with years two and three purchasable only after the prior years — and with minimums that matter for small servers: a Windows Server ESU license covers at least 16 physical cores, or at least 8 virtual cores per VM, and a SQL Server ESU subscription meters at least four cores per instance. Windows Server ESU on-premises requires Software Assurance or an equivalent server subscription, and for Windows Server 2016 it is not offered through SPLA; SQL Server ESU can be bought monthly through Azure Arc without Software Assurance. Buy it through Volume Licensing and you pay in yearly increments; buy it through Azure Arc and it is a monthly meter you switch off per server as that server is migrated — but enrol after the end-of-support date and Microsoft back-bills to that date. This page quotes no dollar figures on purpose; the model uses Microsoft's price list on the delivery date and shows its source. If ESU is the verdict for a group, enrollment through Azure Arc is its own fixed-price engagement — [Windows Server](/services/windows-server-esu-enrollment-azure-arc) or [SQL Server 2016](/services/sql-server-2016-esu-enrollment-azure-arc) — and running the bridged estate for you until it is retired is the [Managed ESU and Legacy Server Lifecycle Service](/services/managed-esu-legacy-server-lifecycle).

### What is Azure Hybrid Benefit, and do we qualify?

It lets Windows Server and SQL Server licenses with active Software Assurance or a qualifying subscription pay a reduced rate in Azure — the compute-only rate for Windows VMs, and a base rate on Azure SQL vCores, where a SQL Server Enterprise core with Software Assurance converts to more than one vCore on the general-purpose tiers. Qualification is a documents question: licenses bought OEM with the server, or through SPLA, generally do not qualify; licenses under an Enterprise Agreement, Open Value with Software Assurance, or a CSP subscription generally do. Edition matters too — Standard licenses cannot run on-premises and in Azure at the same time beyond a one-time 180-day migration window; Datacenter licenses can. We establish the position from your agreement and license statements and state the rule per group, so the Azure column contains only savings you can actually claim.

### What is Azure Local, and when does it beat Azure or a refresh?

Azure Local — formerly Azure Stack HCI — is Microsoft's hyperconverged platform on validated hardware you own, operated through Azure Arc, with a per-core host fee billed to your Azure subscription. It wins when workloads must stay on your floor — latency, data residency, a regulator, a hardware dongle — but you want Azure's operating model and a refresh is due anyway. The lever is Azure Hybrid Benefit: with Windows Server Datacenter licenses under active Software Assurance covering every physical core, Microsoft waives the host fee and the Windows Server guest subscription, which turns an expensive-looking column into a plausible one. Without that licensing, or with an estate small enough that a plain refresh is cheaper, it loses — and the matrix will show it losing. Designing and deploying it is a separate engagement.

### How is this different from the Azure Migrate discovery and assessment?

Different question, different evidence. The [Azure Migrate assessment](/services/azure-migration-discovery-assessment) puts an appliance in your environment for two weeks to measure utilization and map dependencies — it answers "what would this cost in Azure, and what has to move together". This assessment answers "which of five paths should each server group take over the next three years, and what does the CFO need to know" — and it costs the on-premises paths too, which Azure Migrate does not. They chain naturally: if your inventory is trustworthy, do this one now; if it is not, do Azure Migrate first and this one reads its output. The memo tells you which groups need tool discovery before anyone commits money.

### And different from the Azure Cost Optimization and FinOps Assessment?

That one makes Azure you already run cheaper — reservations, right-sizing, waste — from billing and utilization data. This one decides whether on-premises workloads should go to Azure at all, against refresh, renewal, ESU and Azure Local alternatives. If you already have a meaningful Azure footprint the two complement each other: the [FinOps assessment](/services/azure-cost-optimization-finops-assessment) optimizes the existing estate, this one stops you adding to it badly.

### What inventory do you need, and what if ours is unreliable?

Any export that lists each server with operating system, SQL Server version and edition, core count, host and role: vCenter or Hyper-V exports, an RMM report, a CMDB extract, or the assessment workbook from Azure Migrate. We reconcile it against licensing and against what your people believe exists — the deltas are always instructive. If the inventory is untrusted, or utilization and dependencies are unknown for a group where the Azure number is close, the memo says so and recommends the Azure Migrate discovery for that group before commitment. We would rather write "needs measurement" than invent precision.

### Can Microsoft funding pay for the migration?

Sometimes. Microsoft runs partner-led funding and incentive programs for qualifying Azure migrations — the Azure Accelerate offerings, carried into Microsoft's current partner framework — and eligibility, scope and amounts are Microsoft's decision, change by fiscal year and are never guaranteed. We assess whether your estate plausibly fits the current programs and say what Microsoft would need to see; the recommendation memo states it as assessed, and the model never depends on it. Plans built on incentives that then lapse are how migrations stall halfway.

### What if the answer is "refresh the hardware" or "renew the contract"?

Then that is what the memo says, per group, with the numbers. Refresh genuinely wins for small, latency-bound or hardware-licensed estates; renewal genuinely wins when a bigger decision is already scheduled and the contract is fair. Both earn us nothing — nobody at IT Partner is paid on commission, and the assessment is a fixed fee precisely so the verdict does not have to pay for itself with a migration. What we will add is the ESU exposure the on-premises path inherits, because a three-year renewal on 2016-generation servers is also a three-year ESU bill, or three years unpatched.

### Our SQL Server 2016 is already out of support. Is it too late?

No, but the clock is billing. SQL Server 2016 entered its ESU period on 14 July 2026; enrol now and Microsoft's terms back-bill to the start of the current ESU year, so waiting does not save money — it delays the invoice. The assessment models the honest options: [ESU through Azure Arc](/services/sql-server-2016-esu-enrollment-azure-arc) as a monthly bridge while an upgrade or migration completes; an [in-place upgrade to a supported SQL Server release](/services/sql-server-2016-in-place-upgrade); or a move to Azure SQL, where the ESU charge stops automatically on arrival. Which one wins depends on the application vendor's certification, your Software Assurance position and the shape of the database estate — all of which the week establishes.

### Our domain controllers are still on Windows Server 2012 R2. What then?

That group gets its own line and usually its own urgency, because its ESU ended on 13 October 2026 — since that date there have been no security updates at any price. Domain controllers are rarely a migrate-to-Azure decision; they are an upgrade decision — promote new controllers on a supported version, demote the old — sometimes paired with a longer-term move toward Microsoft Entra ID. The memo states the exposure and the next step; hardening what remains is the separate [Active Directory Security Assessment](/services/active-directory-security-assessment), any 2012 R2 server that has outlived its ESU belongs in the [Windows Server 2012 R2 Post-ESU Isolation and Exit Plan](/services/windows-server-2012-r2-post-esu-isolation-exit-plan), and the identity transition is its own engagement.

### Why one week, and what do you need from us to hit it?

Because the evidence already exists — quotes, contracts, licensing, inventory — and the work is reconciling and modeling it, not measuring anything new. One week is realistic when the intake paperwork arrives on day one and your IT owner and finance contact can each give us a session. If the inventory turns out to need tool discovery, that is a two-week Azure Migrate engagement in front of this one, and we say so at intake rather than stretching the week silently.

### What happens after — and can we take the memo to another provider?

You decide, from evidence. Most clients convert the recommended path into fixed written quotes per group — migration, Azure Arc onboarding for ESU, an upgrade, a landing zone — and sequence them by the last-responsible dates; some do the refresh with their hardware vendor and bring us only the groups that move; some conclude that renewal plus a dated exit is right and revisit in a year. The workbook, matrix and memo are yours, built on Microsoft's published rules with sources shown, and there is nothing proprietary in them. We would like the migration work and we price it in fixed per-workload quotes so comparison is easy — but an assessment that only makes sense if you hire its author is an advertisement.

---

Fixed-price engagement by IT Partner LLC. To scope it for your tenant, book a call with Mike (https://o365hq.com/book) or request a quote via the site's /api (see https://o365hq.com/openapi.json).