Skip to content
TrustedSkillsbeta
Back to all skills

Azure Cloud Migrate

Official
microsoft·vlatest·cloud·MIT

Official microsoft skill covering Azure, migration for deploying and managing cloud infrastructure.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add microsoft/azure-skills --skill azure-cloud-migrate -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

microsoft

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned microsoft/azure-skills at 9bb168c343.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9bb168c343
Manifest
skills/azure-cloud-migrate/SKILL.md
Scanned
60 files, 8,362 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Microsoft Azure Cloud Migrate skill enables AI agents to assist with identifying, planning, and executing migrations of workloads to Microsoft Azure. It provides tools for assessing on-premises or other cloud environments, recommending migration strategies, and automating the movement of data, applications, and infrastructure to Azure.

When to use it

  • You need to evaluate existing IT infrastructure for potential migration to Azure.
  • Your organization is planning a hybrid or full-cloud transition and requires guidance on workload compatibility.
  • You want to automate the transfer of virtual machines, databases, or applications to Azure with minimal downtime.

Key capabilities

  • Assess current environments for migration readiness
  • Recommend optimal migration strategies (lift-and-shift, rehost, refactor)
  • Automate data and application transfers to Azure

Example prompts

  • "Assess my on-premises servers for migration to Azure."
  • "Generate a migration plan for moving our SQL Server databases to Azure."
  • "Automate the transfer of this virtual machine to an Azure VM instance."

Tips & gotchas

  • Ensure that your source environment is properly documented and accessible for assessment.
  • Migration strategies may vary depending on workload type, so review recommendations carefully before execution.