Azure Data Catalog Resource Provider

Name: Azure Data Catalog Resource Provider API
Brand: Azure Data Catalog Resource Provider
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth26 EndpointsREST

For Agents

Provision and manage Azure Data Catalog service resources via the Microsoft.DataCatalog ARM provider. Supports six endpoints covering catalog CRUD plus operations discovery.

Quickstart

Get started with Azure Data Catalog Resource Provider in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision an azure data catalog service"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Azure Data Catalog Resource Provider API.

Provision a new Azure Data Catalog service in a resource group with a chosen SKU and units

List all Data Catalog services within a resource group

Retrieve a specific Data Catalog service to inspect SKU, location, and tags

Patch a Data Catalog service to scale capacity units or update tags

GET STARTED

Start building with Azure Data Catalog Resource Provider API

Explore with Jentic

View OpenAPI Document

Use for: I need to provision a new Azure Data Catalog service for the analytics team, List all Data Catalog services in resource group rg-data, Retrieve the SKU and units of an existing Data Catalog service, Scale a Data Catalog service from Standard 1 unit to Standard 4 units

Not supported: Does not register data assets, manage glossary terms, or run lineage queries — use for Microsoft.DataCatalog service provisioning only.

Jentic publishes the only available OpenAPI document for Azure Data Catalog Resource Provider, keeping it validated and agent-ready.

The Azure Data Catalog Resource Provider API manages Azure Data Catalog services as ARM resources. It exposes operations to list, create, update, and delete catalogs scoped to a resource group, plus a discovery endpoint that returns supported Microsoft.DataCatalog actions. This is the control plane for provisioning the catalog itself; the catalog's data-plane content (assets, sources, terms) is registered through a separate Data Catalog REST API.

Use Cases

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

★ Stand Up a New Data Catalog Service

Provision a Microsoft.DataCatalog service so analysts and data engineers can register and discover enterprise data sources. The Resource Provider API accepts a single PUT with location, SKU (Free or Standard), and units, after which the catalog endpoint becomes available for data-plane registration. End-to-end provisioning typically completes in a few minutes for a fresh resource group.

PUT /subscriptions/{subscriptionId}/resourceGroups/rg-data/providers/Microsoft.DataCatalog/catalogs/AcmeCatalog with location=westeurope and properties.sku=Standard, units=1.

Scale Catalog Capacity for Heavier Use

Adjust the number of units on a Data Catalog service to support more registered assets and concurrent users. The PATCH operation accepts a units value within the SKU bounds, applying the change without recreating the resource. This lets capacity planning happen alongside other ARM resource scaling rather than through portal clicks.

PATCH the AcmeCatalog Data Catalog service to set properties.units to 4.

Decommission Unused Catalog Services

Delete legacy Azure Data Catalog services that have been replaced by Microsoft Purview or other modern governance tools. The DELETE call removes the resource cleanly through the resource provider, which lets cleanup pipelines reclaim spend without manual portal access. Pair the delete with a tag-based filter to scope the cleanup safely.

List catalogs in rg-legacy-data, identify any with tag deprecated=true, and DELETE each via the catalog resource endpoint.

Agent-Driven Catalog Inventory

A Jentic agent enumerates every Data Catalog service across multiple subscriptions to produce a governance inventory. It calls List Catalogs in each resource group and reports SKU, units, tags, and provisioning state back to a central report. The same agent can then patch SKUs or tags to align with policy.

For every resource group in subscription 1111-2222, list Data Catalog services and emit a row per catalog with subscriptionId, resourceGroupName, name, sku, and units.

Key Endpoints

6 endpoints — the azure data catalog resource provider api manages azure data catalog services as arm resources.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.DataCatalog/operations

List Microsoft.DataCatalog operations

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs

List catalogs in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Get a single Data Catalog service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Create or update a Data Catalog service

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Patch SKU, units, or tags

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Delete a Data Catalog service

GET

/providers/Microsoft.DataCatalog/operations

List Microsoft.DataCatalog operations

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs

List catalogs in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Get a single Data Catalog service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Create or update a Data Catalog service

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName}

Patch SKU, units, or tags

Why though Jentic?

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

Credential isolation

Azure AD service principal credentials are stored encrypted in the Jentic MAXsystem vault. The agent calls Microsoft.DataCatalog endpoints with a scoped bearer token issued at execution time, keeping secrets out of prompts and logs.

Intent-based discovery

Agents search Jentic by intent (e.g. "provision azure data catalog") and Jentic returns the matching catalogs operation with its full request schema, including SKU and units fields, so the agent does not need to consult ARM docs.

Time to first call

Direct integration: about half a day for AAD setup, ARM polling, and SKU validation. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Data Migration Service Resource Provider

Manages migration services that move databases into Azure data sources later registered in the catalog.

Use alongside this API when the agent's pipeline both migrates data and registers the resulting assets.

Complementary

Azure Data Factory Management

Orchestrates pipelines that produce or consume data assets surfaced through the catalog.

Use when the agent needs to coordinate data movement around the catalog rather than manage the catalog itself.

Alternative

Data Lake Analytics Catalog Management

Catalog management for Azure Data Lake Analytics databases, schemas, and assemblies.

Choose this when the catalog under management is a Data Lake Analytics catalog, not the Microsoft.DataCatalog service.

FAQs

Specific to using Azure Data Catalog Resource Provider API through Jentic.

What authentication does the Azure Data Catalog Resource Provider API use?

Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, the AAD client credentials sit in the MAXsystem vault and the agent receives a runtime bearer token, never the secret.

Can I provision a Data Catalog with this API?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataCatalog/catalogs/{catalogName} with location, properties.sku (Free or Standard), and properties.units to create the service. The same endpoint updates an existing catalog.

What are the rate limits for the Azure Data Catalog Resource Provider API?

It shares Azure Resource Manager subscription throttling, typically 12,000 reads and 1,200 writes per hour per subscription. Honour 429 responses and the Retry-After header; the spec does not declare per-endpoint quotas.

How do I scale a catalog's units through Jentic?

Search Jentic for "scale azure data catalog", load the schema for the catalogs PATCH operation, then execute with properties.units set to the new value. Sign up at https://app.jentic.com/sign-up to obtain an API key.

Does this API register data assets in the catalog?

No. Asset registration, source discovery, and term glossary management happen through the Data Catalog data-plane REST API, not this control-plane resource provider. This API only provisions and configures the catalog service itself.

Should I use this for new projects?

Microsoft Purview is the current governance product for new deployments. Use the Data Catalog Resource Provider when managing existing catalog services or migrating off them; for greenfield work consider the Purview management API.