Azure Copilot Migration Agent preview
Microsoft put Azure Copilot Migration Agent in public preview to automate cloud migration planning—discovering VMware estates and creating landing zones from the Azure portal. The agent signals growing expectation that LLM assistants will handle infra discovery and runbook generation inside cloud consoles. (infoq.com)
Microsoft framed the announcement as part of a new “agentic” modernization push in a Mar 11, 2026 Azure blog post by Jeremy Winter, citing a Forrester Q1 2026 survey that 91% of IT leaders see application modernization as necessary for AI initiatives. (azure.microsoft.com) Microsoft’s public documentation shows the Azure Copilot migration agent docs were published to the Azure Docs repository on Mar 18, 2026 and describe the agent as planning‑focused—able to analyze readiness, ROI, and landing‑zone requirements but not to perform replication or cutover. (github.com) The Agents (preview) guidance states current support is strongest for VMware workloads with “full end‑to‑end” migration assistance, while Hyper‑V and physical/bare‑metal servers receive analysis and strategy help rather than execution automation. (learn.microsoft.com) Discovery pathways documented include RVTools imports for quick inventories and the Azure Migrate appliance for continuous discovery, and the agent can apply tags, summarize dependency maps, and generate deployable landing‑zone templates in Terraform or Bicep aligned to Microsoft’s Cloud Adoption Framework. (learn.microsoft.com) Microsoft and press coverage describe a companion Azure Migrate Collector (public preview) for offline inventory collection and highlight integration with GitHub Copilot and third‑party tools—InfoQ specifically noted handoffs for.NET/Java modernization and CAST Highlight integration. (techcommunity.microsoft.com) Enterprise constraints called out in the docs include required access to VMware vCenter, an Azure subscription with Azure Migrate configured, explicit tenant enablement of Agents (preview) and Azure Copilot, and incompatibility with tenants using Bring Your Own Storage for Copilot conversation history. (learn.microsoft.com) Multiple outlets and Microsoft docs reiterate that the migration agent functions as an intelligent planning layer while actual migration execution steps—starting replication, test migrations, and cutover—remain the responsibility of Azure Migrate workflows in the portal. (learn.microsoft.com)
