[Epic] Migrate and modernize existing workloads onto Azure

## Problem statement

Migration and modernization require coordinated assessment, target selection, code and infrastructure changes, deployment, and validation. Isolated conversion guidance does not produce a successful migration.

## Outcome

Teams can move supported workloads to Azure and verify that the modernized application operates correctly.

## Goals

- Assess source workloads and recommend supported Azure targets
- Coordinate code, configuration, identity, data, and infrastructure changes
- Support cross-cloud, runtime, SDK, and service modernization paths
- Validate deployment and runtime behavior after migration

## Non-goals

- Fully automated migration for every workload
- Replacing specialized migration products

## Success criteria

- [ ] Priority migration paths have end-to-end workflows
- [ ] Generated changes use supported Azure patterns
- [ ] Post-migration validation confirms the intended outcome

## Dependencies

Azure migration services, target service teams, deployment skills, and validation tooling.

No files, tests, or entry points are identified in the issue. Start by breaking the epic into priority migration paths and identifying the relevant Azure migration services, target service teams, deployment skills, and validation tooling. Done means supported paths have end-to-end workflows, generated changes follow supported Azure patterns, and post-migration validation confirms the intended outcome.

Written by the indexing model from the issue text.