Microsoft Azure Azure Migrate

Name: Azure Migrate API
Brand: Azure Migrate
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth224 EndpointsREST

For Agents

Provision and operate Azure Migrate projects — create projects, group discovered machines, run readiness and sizing assessments, and download assessment reports for migration planning to Azure.

Install Jentic One Beta

Connect the Azure Migrate to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Migrate, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Azure Migrate API.

Create or update a Microsoft.Migrate project in a resource group

List discovered machines reported into a Migrate project

Group machines into named groups for assessment

Run a readiness and sizing assessment against a group

GET STARTED

Start building with Azure Migrate API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Azure Migrate API for, with concrete tasks.

★ Datacenter Discovery to Assessment Pipeline

Migration teams stand up a Migrate project, ingest discovered machines from the on-prem appliance, group machines by application, then run assessments to estimate Azure VM size, monthly cost, and readiness. The PUT on /projects creates the project, /groups defines the assessment scope, and the PUT on /assessments triggers the assessment run; the assessedMachines GET returns per-VM recommendations.

Create Migrate project 'migrate-london' in resource group 'rg-migrate', create group 'app-tier' with the 30 discovered machine IDs in tag 'app=ecommerce', and start an assessment named 'assess-2026q2'.

Assessment Report Distribution

After an assessment completes, the POST on /assessments/{assessmentName}/downloadUrl returns a short-lived SAS URL pointing at a CSV report containing per-machine readiness, suggested Azure VM SKU, and monthly cost estimate. Migration leads attach this report to project status updates without exporting machine data manually.

Generate the download URL for assessment 'assess-2026q2' under project 'migrate-london' and return the SAS URL with its expiry time.

Per-Machine SKU Lookup

The GET on /assessments/{assessmentName}/assessedMachines returns each assessed machine's suggested Azure VM size, suitability rating, and monthly cost. This is useful for engineering teams who need to pick the right SKU per workload before lift-and-shift, and for finance teams modelling steady-state costs after migration.

List assessed machines for assessment 'assess-2026q2' under project 'migrate-london', filter to suitability='Suitable', and return name, suggestedSize, and monthlyComputeCost.

Agent-Driven Migration Planning

An AI agent through Jentic can list every Migrate project across subscriptions, summarise readiness counts per group, and trigger fresh assessments after configuration changes. Jentic returns the operation schema for each call so the agent can iterate on assessment runs without parsing the Microsoft.Migrate Resource Provider docs.

List groups in project 'migrate-london', start an assessment on each group with default sizing criteria, and report group name, assessment name, and provisioning state.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for azure migrate, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}

Create or update a Migrate project

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Migrate/projects

List Migrate projects in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}

Create or update a group of machines

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}

Create or update an assessment on a group

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}/downloadUrl

Generate an assessment report download URL

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}/assessedMachines

List assessed machines

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Migrate/locations/{locationName}/checkNameAvailability

Check Migrate project name availability

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/keys

Issue project keys for appliance registration

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}

Create or update a Migrate project

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Migrate/projects

List Migrate projects in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}

Create or update a group of machines

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}

Create or update an assessment on a group

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}/downloadUrl

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD service principal credentials and Migrate project keys are stored encrypted in the Jentic vault. Agents receive short-lived Bearer tokens scoped to https://management.azure.com/ — client secrets and project keys never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'run an Azure Migrate assessment' or 'list assessed machines') and Jentic returns the matching Microsoft.Migrate operation with its parameter schema.

Time to first call

Direct integration: 2-3 days for Azure AD setup, project lifecycle wiring, and async assessment polling. Through Jentic: under 2 hours — search, load schema, execute.

FAQs

Specific to using Azure Migrate API through Jentic.

Why is there no official OpenAPI spec for Azure Migrate?

Microsoft Azure does not publish a single consolidated OpenAPI specification for the Microsoft.Migrate Resource Provider at this revision. Jentic generates and maintains this spec so that AI agents and developers can call Azure Migrate via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Migrate API use?

The API uses Azure Active Directory OAuth 2.0; agents acquire a token for the https://management.azure.com/ resource and pass it as a Bearer token. Jentic stores the service principal credentials in its vault and injects scoped tokens at call time.

Does this API run the actual migration or just plan it?

This API plans migrations — it manages Migrate projects, discovers machines, groups them, and runs assessments that produce sizing and cost recommendations. The actual lift-and-shift is performed by Azure Site Recovery or Server Migration tools, which are separate control planes.

How do I run an assessment through Jentic?

Search Jentic for 'run an Azure Migrate assessment', load the resulting PUT operation on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Migrate/projects/{projectName}/groups/{groupName}/assessments/{assessmentName}, then execute it with the assessment name and target Azure location. Install with pip install jentic and run the async search-load-execute flow.

How do I download an assessment report?

Call POST /projects/{projectName}/groups/{groupName}/assessments/{assessmentName}/downloadUrl. The response contains a short-lived SAS URL pointing at a CSV with per-machine readiness, suggested Azure VM SKU, and monthly compute cost.

What are the rate limits for this API?

Azure Resource Manager applies subscription-level throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Assessment runs are long-running operations that progress through 'Running' to 'Succeeded' over minutes.

Microsoft Azure Azure Migrate

Connect the Azure Migrate to your agent

Capabilities

Start building with Azure Migrate API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs