[AI-Suggested] Content update request from Blogs signal: Your Migration's Source of Truth: The Modernization Assessment

[learn-build-service-ppe]

Background

A recent product update has been released that may impact our documentation. This could include new features, changes to existing functionality, or other product enhancements.
Your Action Required: Please review the suggestions below and update the relevant documentation to ensure accuracy and completeness.

Signal Details:

• Title: Your Migration's Source of Truth: The Modernization Assessment
• Source URL: https://devblogs.microsoft.com/dotnet/your-migrations-source-of-truth-the-modernization-assessment

Source Signal Summary
GitHub Copilot’s application modernization provides an end-to-end Assess → Plan → Execute workflow that analyzes .NET and Java codebases, generates an assessment document, creates migration plans, and provisions Azure infrastructure. The GitHub Copilot Modernization VS Code extension (GA) enables assessments, dependency upgrades, containerization, and Azure deployment directly in Visual Studio Code, while the Modernization CLI (public preview) supports terminal and multi-repo batch assessments. Assessments support domains (Java/.NET Upgrade, Cloud Readiness, Security), multiple analysis coverage levels, and target compute comparisons across Azure App Service, Azure Kubernetes Service (AKS), and Azure Container Apps (ACA), with Linux/Windows and containerization options. The assessment report captures runtime/framework inventory, issue severity (Mandatory/Potential/Optional), file-level findings with remediation guidance, and supports export/import (including AppCAT CLI and Dr. Migrate) and side-by-side comparison. Upgrade rules include Java (OpenJDK 11→17→21, Spring Boot 2.x→3.x) and .NET (.NET Framework→.NET 10, ASP.NET→ASP.NET Core). Planning and execution generate plan.md and tasks.json, produce IaC as Bicep or Terraform, and create Dockerfiles and service-specific deployment manifests for AKS, ACA, and App Service, with human-in-the-loop editing and Git-tracked changes. The workflow supports Azure Landing Zone-aligned infrastructure planning and independent, phase-based execution.

Suggestions

Note

Suggestions are generated by AI and they may not be entirely accurate or complete. Please check impacted files scope and suggestions details before making changes.
Copilot should only fix suggestions with a checkmark. Do not make any updates for unchecked suggestions.

• docs/core/porting/github-copilot-app-modernization/overview.md:
  • [Improvements] In the 'How it works' > Assessment stage section, add details about assessment domains (for .NET: Upgrade, Cloud Readiness, Security), selectable analysis coverage levels, and severity categories (Mandatory, Potential, Optional). Note that the assessment provides file-level findings with remediation guidance, supports export/import of the assessment report (including interoperability with AppCAT CLI and Dr. Migrate), and enables side-by-side comparison of multiple assessments.
  • [Improvements] In 'Migrate .NET projects to Azure', explicitly list the supported deployment targets and containerization options: Azure App Service, Azure Kubernetes Service (AKS), and Azure Container Apps (ACA), with Linux/Windows runtime options and optional containerization. Include that the assessment compares target compute options to help choose the right service.
  • [Correction Required] In 'How it works' > Planning and Execution descriptions and in 'Upgrade results', update references to generated files to reflect the latest outputs: the planning stage produces plan.md and the execution stage produces tasks.json (not tasks.md). Ensure all mentions of tasks.md are replaced with tasks.json where task status tracking is described.
  • [Improvements] In 'How it works' > Planning/Execution, add that the workflow can generate Infrastructure as Code artifacts (Bicep or Terraform) aligned with Azure Landing Zone guidance, and produces Dockerfiles and service-specific deployment manifests for AKS, ACA, and App Service. Clarify that changes are Git-tracked and support human-in-the-loop editing before execution.
  • [Improvements] In 'How it works' > Start the agent, refine tooling entry points to call out the GitHub Copilot Modernization VS Code extension and the dedicated Modernization CLI (for terminal and multi-repo batch assessments) alongside Visual Studio, Copilot Chat, and GitHub.com. Keep this at a high level without status labeling, and link to install/setup where appropriate.

---

📚 To learn more about agentic content maintenance workflow, visit Agentic workflow for Learn content maintenance. Sign in using Learn Profile to access the content on this link.

💬 Share your feedback on the Learn Content Maintenance Agentic Workflow here.