HybridDataManagementClient

Name: HybridDataManagementClient API
Brand: HybridDataManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth229 EndpointsREST

For Agents

Provision Azure HybridData data managers, define jobs that move data between on-premises and cloud stores, and run, cancel, or resume those jobs through Azure Resource Manager.

Connect the HybridDataManagementClient to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 HybridDataManagementClient API.

Create and update HybridData data manager resources scoped to a resource group

Configure data stores and data store types that act as sources and sinks for hybrid data movement

Define job definitions that describe how data moves between paired data stores

Trigger a job run, then cancel or resume in-flight jobs against a job definition

GET STARTED

Start building with HybridDataManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for HybridDataManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for HybridDataManagementClient, keeping it validated and agent-ready. The Azure Hybrid Data Management API provisions and operates Microsoft.HybridData data managers that move data between on-premises stores and Azure cloud services. It exposes 29 ARM endpoints to create data managers, configure data services and data stores, define job definitions, and run, cancel, or resume hybrid data movement jobs across resource groups and subscriptions.

Use Cases

Patterns agents use HybridDataManagementClient API for, with concrete tasks.

★ On-Premises to Azure Data Migration Pipeline

Move data from on-premises file shares or storage devices into Azure Storage by provisioning a HybridData data manager, attaching source and sink data stores, and defining a job definition that maps the transfer. The API drives the full lifecycle through Azure Resource Manager, so DevOps teams can codify hybrid migration jobs in ARM templates or scripts and run them on demand. A typical migration setup is a one-day exercise once data manager and store credentials are in place.

Create a data manager named 'archive-mover' in resource group 'rg-archive', attach an on-premises file data store as source and an Azure Blob data store as sink, then run the configured job definition and wait for completion.

Scheduled Hybrid Job Operations

Operate recurring data movement jobs by listing job definitions, running them on a schedule, and reacting to failures with cancel and resume calls. The API exposes per-job state under each data service so an orchestrator can poll jobs by jobId and intervene when a job hangs. This is the operational backbone for teams running nightly hybrid ingestion into Azure data lakes.

List all jobs under data service 'DataTransfer' for data manager 'nightly-ingest', find any in 'Failed' state, and resume each one via the resume endpoint.

Hybrid Data Estate Inventory

Audit a subscription's hybrid data footprint by enumerating data managers across resource groups, then walking each data manager's data stores, data store types, and job definitions. The output supports compliance reviews and cost allocation by showing which on-premises sources are wired into which Azure resources. Inventory runs complete in minutes against a single subscription.

Enumerate all data managers in subscription 'sub-prod', and for each one return the count of data stores and job definitions as a single CSV report.

Agent-Driven Hybrid Data Workflow via Jentic

AI agents can drive Azure HybridData operations end-to-end through Jentic without handling raw Azure AD tokens. An agent searches Jentic for 'run an Azure hybrid data job', loads the run-job operation schema, and executes with the data manager and job definition names. Jentic's MAXsystem holds the OAuth credentials and supplies a scoped token for the call, so the agent never sees the client secret or refresh token.

Use the Jentic MCP tool azure_hybriddata_run_job to start the 'daily-archive' job under data manager 'prod-mover' and report the returned job status.

Key Endpoints

29 endpoints — jentic publishes the only available openapi specification for hybriddatamanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.HybridData/dataManagers

List data managers across the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}

Create or update a data manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}/dataServices/{dataServiceName}/jobDefinitions

List job definitions under a data service

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}/dataServices/{dataServiceName}/jobDefinitions/{jobDefinitionName}/run

Trigger a run of the named job definition

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}/dataServices/{dataServiceName}/jobDefinitions/{jobDefinitionName}/jobs/{jobId}/cancel

Cancel a running job

POST

Resume a paused or failed job

GET

/subscriptions/{subscriptionId}/providers/Microsoft.HybridData/dataManagers

List data managers across the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}

Create or update a data manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}/dataServices/{dataServiceName}/jobDefinitions

List job definitions under a data service

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridData/dataManagers/{dataManagerName}/dataServices/{dataServiceName}/jobDefinitions/{jobDefinitionName}/run

Trigger a run of the named job definition

Why though Jentic?

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

Credential isolation

Azure AD OAuth 2.0 client secrets and refresh tokens for HybridDataManagementClient are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped bearer tokens for the management.azure.com audience — raw client secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'run an Azure hybrid data job') and Jentic returns the matching HybridData ARM operation with its parameter schema, so the agent can call the right endpoint without crawling Azure REST docs.

Time to first call

Direct Azure HybridData integration: 2-4 days to wire AAD app registration, ARM token refresh, and long-running operation polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure IoT Hub

IoT Hub ingests device telemetry that HybridData jobs can subsequently move into long-term Azure storage.

Choose IoT Hub when the source is connected devices rather than on-premises file or database stores.

Complementary

Azure Key Vault

Key Vault stores the secrets and certificates that HybridData data stores consume for source and sink credentials.

Use Key Vault to manage secrets that HybridData data store definitions reference, instead of inlining credentials.

Alternative

Azure Stack Infrastructure Insights

Infrastructure Insights covers Azure Stack health and inventory rather than data movement, but is the closest hybrid-management peer.

Choose Infrastructure Insights when the goal is monitoring hybrid infrastructure health rather than moving data.

FAQs

Specific to using HybridDataManagementClient API through Jentic.

Why is there no official OpenAPI spec for HybridDataManagementClient?

Microsoft Azure does not publish an OpenAPI 3 specification for the HybridData control plane. Jentic generates and maintains this spec so that AI agents and developers can call HybridDataManagementClient 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 HybridDataManagementClient use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against the management.azure.com audience. Through Jentic, the AAD client secret and refresh token are stored in the Jentic vault (MAXsystem), and a scoped bearer token is injected into each request so the agent never handles raw credentials.

Can I run and cancel hybrid data jobs with this API?

Yes. Trigger a run by POSTing to the .../jobDefinitions/{jobDefinitionName}/run endpoint, then cancel or resume the resulting job at .../jobs/{jobId}/cancel or .../jobs/{jobId}/resume. The job state is returned from the standard list and get operations under the data service.

What are the rate limits for HybridDataManagementClient?

It uses the standard Azure Resource Manager throttling — typically 12,000 read and 1,200 write operations per hour per subscription, tracked via the x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes response headers. The HybridData provider does not document tighter limits, so plan against the ARM defaults.

How do I trigger a hybrid data job through Jentic?

Install the SDK with pip install jentic, then search Jentic with the query 'run an Azure hybrid data job', load the run-job operation, and execute with subscriptionId, resourceGroupName, dataManagerName, dataServiceName, and jobDefinitionName. Jentic returns the job resource so you can poll it via the jobs endpoint.

Is the HybridDataManagementClient API free to call?

The control-plane calls themselves are billed under standard ARM usage and are effectively free. The underlying Microsoft.HybridData resources, on-premises agents, and Azure storage egress are billed separately under your Azure subscription per the published Azure pricing pages.