{"id":3805,"date":"2026-04-07T19:12:00","date_gmt":"2026-04-07T19:12:00","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/04\/07\/your-migrations-source-of-truth-the-modernization-assessment\/"},"modified":"2026-04-07T19:12:00","modified_gmt":"2026-04-07T19:12:00","slug":"your-migrations-source-of-truth-the-modernization-assessment","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/04\/07\/your-migrations-source-of-truth-the-modernization-assessment\/","title":{"rendered":"Your Migration\u2019s Source of Truth: The Modernization Assessment"},"content":{"rendered":"

I\u2019ve been exploring GitHub Copilot\u2019s modernization<\/a> capabilities for .NET and Java applications, and I wanted to share what I\u2019ve learned about the most critical piece of the puzzle: the assessment document.<\/p>\n

Here\u2019s what makes this tool interesting \u2013 it\u2019s not just a code suggestions engine. It\u2019s an agentic, end-to-end solution that analyzes your entire codebase, writes an assessment document, builds a migration plan, and can provision the Azure infrastructure to run it. The experience follows an Assess \u2192 Plan \u2192 Execute<\/strong> model, and I\u2019ve found that assessment is the foundation everything else builds on.<\/p>\n

\"Assess
The three-phase modernization workflow: Assessment drives planning, which drives execution.<\/figcaption><\/figure>\n<\/p>\n

At each step, a document is generated with Copilot\u2019s findings and recommendations. You can interject at this point and provide feedback, enhancements, and corrections to assist GitHub Copilot for the next phases of your migration. Copilot gives you the opportunity to steer it so that your migration completes with the results you\u2019re seeking.<\/p>\n

The tooling ships through a VS Code extension<\/a> (generally available for both .NET and Java) that puts the full modernization workflow directly in your editor: running assessments, migrating dependencies, containerizing apps, and deploying to Azure. There\u2019s also a Modernization CLI<\/strong><\/a> in public preview for terminal-based and multi-repo batch scenarios<\/a>, but for this post I\u2019m working on one project in Visual Studio Code.<\/p>\n

The assessment document is the most important artifact the tool produces, and I\u2019m blown away by what insight it gives me. It reports what gets upgraded, what Azure resources get provisioned, and how your application gets deployed. Everything downstream \u2013 infrastructure-as-code, containerization, deployment manifests \u2013 takes its cues from what the assessment finds. I\u2019ve found that understanding how to configure, read, and act on this document is the single highest-leverage skill in the modernization workflow.<\/p>\n

\n

Two Paths In \u2013 Recommended Assessment & Upgrade Paths<\/h2>\n

The VS Code extension gives you two ways to kick off an assessment. They lead to the same interactive dashboard, but they differ in how much configuration you want to do upfront.<\/p>\n

Path 1: Recommended Assessment (Fast Start)<\/h3>\n

This is the \u201cshow me what I\u2019m dealing with\u201d path. No manual configuration required.<\/p>\n

\"VS
\nThe Quickstart section with Start Assessment option in VS Code<\/em><\/p>\n

    \n
  1. Open the GitHub Copilot modernization<\/strong> pane in VS Code.<\/li>\n
  2. Select Start Assessment<\/strong> (or Open Assessment Dashboard<\/strong>) from the Quickstart section.<\/li>\n
  3. Choose Recommended Assessment<\/strong>.<\/li>\n
  4. Pick one or more domains from the curated list \u2013 Java\/.NET Upgrade<\/strong>, Cloud Readiness<\/strong>, Security<\/strong> \u2013 and click OK.<\/li>\n<\/ol>\n

    That\u2019s it. The assessment runs against your codebase and results appear in the interactive dashboard. Each domain represents a common migration scenario with preconfigured settings, so you get meaningful results without touching a single configuration knob.<\/p>\n

    This felt like the right starting point when I just wanted a quick read on where an app stands before committing to a migration strategy.<\/p>\n

    Path 2: Custom Assessment (Targeted)<\/h3>\n

    When you already know your target \u2013 say, AKS on Linux with containerization \u2013 the custom assessment lets you configure exactly what to analyze.<\/p>\n

    Select Custom Assessment<\/strong> from the assessment pane, then dial in:<\/p>\n

    \"Custom
    \nCustom assessment lets you target specific compute options and analysis domains<\/em><\/p>\n\n\n\n\n\n\n\n\n\n
    Setting<\/th>\nOptions<\/th>\n<\/tr>\n<\/thead>\n
    Assessment Domains<\/strong><\/td>\nJava\/.NET Upgrade, Cloud Readiness, Security \u2013 pick one or combine all three<\/td>\n<\/tr>\n
    Analysis Coverage<\/strong><\/td>\nIssue only<\/em> \u2013 just the problems. Issues & Technologies<\/em> \u2013 problems plus tech inventory. Issues, Technologies & Dependencies<\/em> \u2013 the full picture.<\/td>\n<\/tr>\n
    Target Compute<\/strong><\/td>\nAzure App Service<\/a>, Azure Kubernetes Service (AKS)<\/a>, Azure Container Apps (ACA)<\/a> \u2013 pick multiple to compare side-by-side<\/td>\n<\/tr>\n
    Target OS<\/strong><\/td>\nLinux or Windows<\/td>\n<\/tr>\n
    Containerization<\/strong><\/td>\nEnable or disable containerization analysis<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    When you select multiple Azure service targets, the dashboard lets you switch between them to compare migration approaches and view service-specific recommendations \u2013 that\u2019s pretty slick when the hosting decision hasn\u2019t been finalized yet.<\/p>\n

    I use this path when I know I\u2019m going to AKS on Linux and I want to know exactly what\u2019s blocking that.<\/p>\n

    Upgrade Paths the Assessment Covers<\/h3>\n

    The assessment isn\u2019t just about cloud readiness. It also evaluates framework and runtime upgrade paths with specific issue detection rules and remediation guidance:<\/p>\n