Azure APIs
237 APIs4,900 Endpoints17 Categories
Categories
API Catalog(29 of 237)
Azure Data Catalog Resource Provider
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.
6 endpointsAzure Data Migration Service Resource Provider
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.
26 endpointsAzure SQL Database
Jentic publishes the only available OpenAPI specification for Azure SQL Database, keeping it validated and agent-ready. This 2014-04-01 surface scopes down to the checkNameAvailability operation under Microsoft.Sql, which validates whether a candidate Azure SQL server name is available within a subscription before provisioning. It is a focused control plane utility used as a precondition step in any Azure SQL server creation workflow.
Connect Your Agent
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" | sh2
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" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.