Migrating to Azure? Look Beyond the VM Inventory

Two Microsoft support deadlines land within months of each other. SQL Server 2016 reached the end of extended support on July 14, 2026. On November 10, 2026, .NET 8 and .NET 9 follow. After that date, Microsoft will no longer provide servicing updates, security fixes or technical support for either version. Applications keep running, but without patches.

Teams now must retarget affected applications to .NET 10 or later, and check the SQL databases behind them for compatibility with their Azure target. Each step depends on facts that many teams do not have in one place: which applications run on which runtime, what else they depend on, which databases sit behind them, and what moving them will cost.

That is the real planning problem in most Azure programs. The move itself is rarely the hard part. Knowing what to move, in what order, and in what form is.

Migration is only half the job

Gartner forecasts 21.3% growth in public cloud services in 2026, citing ongoing migration and modernization efforts and demand for AI integration. Customers rarely want servers lifted and shifted. They want applications modernized, databases moved to managed services, and data that is ready for AI.

That last point matters. In a Gartner survey, 63% of organizations said they lack, or are unsure they have, the right data management practices for AI. Gartner predicts that through 2026, organizations will abandon 60% of AI projects that are not supported by AI-ready data. A migration that moves servers and leaves the data estate unexamined can leave that problem exactly where it was.

Budgets are under pressure too. Gartner's July 2026 forecast puts worldwide IT spending at $6.37 trillion, up 14.2%, with infrastructure as a service among the fastest-growing segments. It also notes that technology budgets are being strained by inflation, supply shortages, rising hardware and memory costs, and competing AI funding. In that environment, a migration plan needs a cost basis that a finance team can test. That is where a TCO built from visible assumptions earns its place: reviewers can see what drives the number and challenge it before money is committed.

Where plans go wrong

Many plans start from a VM inventory. It is a sound basis for sizing and a weak basis for decisions:

• It shows servers, not the applications they support or how critical those applications are.
• It does not show dependencies, so move groups become guesses.
• It says little about databases, such as whether SQL Server can move to Azure SQL Managed Instance or Azure SQL Database serverless, and what compatibility changes that would need.
• It misses cross-database dependencies. Queries and transactions that span databases add coordination, latency and failure handling, which can raise operating and query costs.
• It tends to default to rehosting, even where a managed service would be cheaper to run.

A runtime deadline shows the gap. Retargeting an application to .NET 10 can involve more than the application itself. Third-party components built for .NET 8 or 9 may depend on vendor updates, and in regulated or security-critical environments, running an unsupported runtime can cause compliance failures. A VM inventory shows little of that.

VMware exits add pressure. Gartner expects more than a third of VMware workloads to run on another platform by 2028. It also cautions that a full migration can take three or more years, and that selective re-platforming can pay off. Choosing what to move, and how, is an assessment question before it is a migration one.

What a unified assessment changes

A unified assessment looks at infrastructure, applications and databases in one pass and ties every finding to a named application and its business criticality. Instead of three reports to reconcile by hand, you get one portfolio view. Concierto, Trianz's platform for cloud transformation, takes this approach. In practice it means:

• Dependency maps that show what has to move together.
• Application and database analysis, with a recommended approach for each: retire, rehost, replatform, refactor, repurchase or retain.
• Database analysis that rates schema complexity and maps each database to an Azure target, for example SQL Server to Azure SQL.
• A TCO built from visible assumptions: your on-premises costs or an industry baseline, rightsizing from actual utilization, and Azure pricing options including Azure Hybrid Benefit.

It can also start small. From an inventory export such as RVTools, Trianz demonstrates a directional Azure TCO in under 30 minutes. Azure Migrate reports can be ingested as well. Directional is the word to hold on to. Until real costs and utilization data replace the defaults, the number is an early estimate, and a good assessment says so. Discovery inside your network then narrows the gaps.

Three questions before you approve a plan

We cover this in more depth in our technical white paper, Assessing the Whole Estate for Azure. If you would like to talk it through, we will be at Microsoft Ignite in San Francisco on November 17–20. Book a meeting at trianz.com/azure.

Sources

• Microsoft Community Hub: SQL Server 2016 Extended Security Updates. End of extended support, July 14, 2026.
• Microsoft .NET Blog: .NET 8 and .NET 9 will reach End of Support on November 10, 2026. Servicing, security fixes and support end for both versions; .NET 10 is the recommended target. June 29, 2026.
• Gartner: Forecast: Public Cloud Services, Worldwide, 2023–2029, 3Q25 Update. 21.3% growth in 2026.
• Gartner: Lack of AI-Ready Data Puts AI Projects at Risk. 63% and 60% figures, Feb 26, 2025.
• Gartner: Worldwide IT Spending to Grow 14.2% in 2026, Totaling $6.37 Trillion. Press release, July 27, 2026.
• The Register: Gartner on VMware migration. More than a third of workloads by 2028, Sept 11, 2025.