Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / Azure Data Migration Service Resource Provider
Azure Data Migration Service Resource Provider logo

Microsoft Azure Azure Data Migration Service Resource Provider

Browse all Azure APIs
58
AI ReadinessFoundational (C+)58/100
See full scorecard
Community OpenAPI document · agent-readyStorageDatabaseoauth226 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision Azure Data Migration Service instances, manage migration projects, and run typed migration tasks that move databases from on-premises or older platforms into Azure. Supports 26 endpoints across services, projects, tasks, SKUs, and usages.

Use for: I need to migrate a SQL Server database to Azure SQL Database, Provision a new Data Migration Service in eastus2 bound to my VNet, List all DMS services in resource group rg-migration, Retrieve the status of a specific migration task

Not supported: Does not provision target Azure SQL databases, run continuous ETL pipelines, or manage Azure Data Factory triggers - use for DMS service, project, and task lifecycle only.

The Azure Data Migration Service (DMS) Resource Provider API manages DMS service instances and the projects and tasks they execute to move databases into Azure. It exposes 26 endpoints covering service CRUD, project lifecycle, generic migration tasks with typed inputs and outputs, SKU listings, name availability checks, and quota usage. Tasks are deliberately generic so new migration scenarios can be added without provider updates.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Azure Data Migration Service Resource Provider to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Data Migration Service Resource Provider, 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-data-migration-service-resource-provider" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-data-migration-service-resource-provider" | 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 Data Migration Service Resource Provider API.

Provision a Data Migration Service instance bound to a virtual network

List DMS services across a subscription or scoped to a resource group

Create migration projects under a service and group related migration tasks

Run migration tasks with typed inputs (e.g. SQL Server to Azure SQL) and inspect outputs

Cancel a running migration task without tearing down the project

Check whether a candidate DMS service or project name is available in a region

List supported SKUs and current quota usage for a region

Use Cases

Patterns agents use Azure Data Migration Service Resource Provider API for, with concrete tasks.

★ On-Prem SQL Server to Azure SQL Migration

Move a SQL Server database from an on-premises VM into Azure SQL Database using a DMS service joined to the customer VNet. The Resource Provider API provisions the service, creates a project with sourcePlatform=SQL and targetPlatform=SQLDB, and runs a typed migration task whose input describes connection strings and selected databases. The task's output reports per-database progress and any validation issues, replacing manual schema-and-data export workflows.

Create a DMS project named SqlToAzure under service acme-dms, then start a Migrate.SqlServer.AzureSqlDb task with the source SQL Server connection and the target Azure SQL Database name.

Capacity and Region Planning

Pick the right region and SKU for a Data Migration Service before provisioning. The API exposes Skus_ListSkus and Usages_List endpoints that report supported SKU tiers per region and current subscription usage against quotas. Procurement and platform teams can call these read-only endpoints to choose Standard or Premium SKUs without raising support tickets.

Call Skus_ListSkus for subscription 1111-2222 and Usages_List for location=westeurope, then return the available Premium SKUs and remaining quota.

Long-Running Migration Lifecycle Control

Drive a long-running migration end to end without portal interaction: create a project, start a task, poll its state, and cancel cleanly if a stop condition fires. The DMS API models tasks as resources with state and output fields, so an agent can implement deterministic polling and error-handling loops. Teams typically wrap this in a runbook that handles retries and notifications.

Create and start a migration task, poll the task resource until state is Succeeded or Failed, and call the cancel operation if state stays Running for longer than the configured timeout.

Agent-Driven Migration Orchestration

A Jentic agent orchestrates a fleet of database migrations: it lists candidate sources, calls checkNameAvailability per service, creates DMS instances and projects, and starts the appropriate typed task per source platform. The agent uses the same 26 endpoints in this spec to coordinate the migration, replacing portal-driven runbooks with a structured tool-using loop.

For each entry in a migration plan list, check name availability, provision a DMS service if missing, create the project, and start a Migrate.SqlServer.AzureSqlDb task with the supplied connection details.

Key Endpoints

26 endpoints — the azure data migration service (dms) resource provider api manages dms service instances and the projects and tasks they execute to move databases into azure.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/services

List DMS services in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services

List DMS services in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}

Get a single DMS service

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}

Delete a DMS service

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/locations/{location}/checkNameAvailability

Check service or project name availability

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/skus

List supported DMS SKUs

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/locations/{location}/usages

Get DMS quota usages for a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/services

List DMS services in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services

List DMS services in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}

Get a single DMS service

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}

Delete a DMS service

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/locations/{location}/checkNameAvailability

Check service or project name availability

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/skus

List supported DMS SKUs

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataMigration/locations/{location}/usages

Get DMS quota usages for a region

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Azure Data Migration Service Resource Provider

- Foundational (C+)
58/100
99
Foundational Compliance
63
Developer Experience & Jentic Compatibility
39
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

39

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
94%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Azure Data Migration Service Resource Provider by hand means registering an Azure AD app, exchanging OAuth 2.0 tokens for management.azure.com, assembling the right typed task input per migration scenario, and building the Azure Resource Manager plumbing that polls long-running tasks and retries on throttling. Through Jentic you install once, import the Azure Data Migration Service Resource Provider from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the subscription, resource group, and service name in the URL path (for example /subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}), so a rule can pin your agent to a specific migration service. You choose the operations it may call, so ones like deleting a DMS service or cancelling a running task are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'migrate a SQL Server database to Azure SQL' or 'check DMS quota usage in a region', and Jentic returns the matching tasks create-or-update operation with the full task input schema for that taskType so the agent does not assemble JSON from documentation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure SQL Database

→

The most common destination for DMS migrations and the resource that hosts migrated databases.

Use alongside DMS when the agent must also create or configure the target Azure SQL database resource.

Alternative

Azure Data Factory Management

→

Pipeline-based ETL service for ongoing data movement rather than one-time migrations.

Choose Data Factory for repeated ELT workflows; choose DMS for cutover-style database migrations.

Complementary

Azure Data Catalog Resource Provider

→

Provisions the catalog where migrated databases can be registered as discoverable assets.

Use after a successful DMS migration to register the new Azure SQL or other target as a catalog asset.

FAQs

Specific to using Azure Data Migration Service Resource Provider API through Jentic.

What authentication does the Azure Data Migration Service API use?

Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, AAD client credentials live in your Jentic One instance and the agent receives a runtime bearer token rather than the secret.

Can I migrate SQL Server to Azure SQL with this API?

Yes. Provision a DMS service via PUT under Microsoft.DataMigration/services, create a project, then start a typed task such as Migrate.SqlServer.AzureSqlDb with the source connection and target database name in the task's input block.

What are the rate limits for the Azure DMS API?

Azure Resource Manager subscription throttling applies, typically 12,000 reads and 1,200 writes per hour per subscription. Long-running migration tasks themselves are not rate-limited by ARM; their progress is polled via the task resource's state field.

How do I start a migration task through Jentic?

Search Jentic for "start azure database migration task", load the schema for the tasks createOrUpdate operation, set the typed input block (taskType plus connection details), and execute. Run it through Jentic One, the self-hosted execution layer to get an API key.

How is connectivity to source databases handled?

The DMS service is joined to a customer-supplied virtual network at provisioning time. Connectivity from the service workers to source databases is the customer's responsibility through that VNet, including any required DNS, firewall, and ExpressRoute or VPN configuration.

Why are tasks generic instead of typed per scenario?

The resource provider models tasks generically with a taskType, input, and output so Microsoft can add new migration scenarios (e.g. MongoDB to Cosmos DB) without versioning the resource provider. Clients pick the right taskType and matching input schema for the specific migration.

Can I limit what my agent is allowed to do with the Azure Data Migration Service API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which operations and credentials the agent may use. This API puts the subscription, resource group, and service name in the URL path (for example /subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.DataMigration/services/{serviceName}), so you can pin the agent to one specific migration service. You also choose the exact operations it may call, so destructive ones like deleting a DMS service or cancelling a running task stay out of reach unless you explicitly add them.

GET STARTED

Start building with Azure Data Migration Service Resource Provider API

Explore with Jentic One
View OpenAPI Document