Microsoft Azure DomainRegistrationProvider API Client

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth21 EndpointsREST

For Agents

Install Jentic One Beta

Connect the DomainRegistrationProvider API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DomainRegistrationProvider API Client, 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 DomainRegistrationProvider API Client API.

Retrieve the full operations catalogue for the Microsoft.DomainRegistration provider

Discover which actions on Microsoft.DomainRegistration require RBAC permissions

Drive role-definition tooling that needs the provider operations list

GET STARTED

Start building with DomainRegistrationProvider API Client API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for DomainRegistrationProvider API Client, keeping it validated and agent-ready. The Azure DomainRegistrationProvider API Client exposes the operations metadata for the Microsoft.DomainRegistration resource provider — the namespace that powers Azure App Service custom domain registration and the Domains API. It exposes a single endpoint that returns the list of available CSM operations, used for RBAC role definition, audit, and feature discovery against the provider.

Use Cases

Patterns agents use DomainRegistrationProvider API Client API for, with concrete tasks.

★ Custom RBAC Role Authoring

Defining a custom Azure role that allows only domain renewal but not domain deletion requires the exact action strings from Microsoft.DomainRegistration. By calling DomainRegistrationProvider_ListOperations a tool can pull the full operations catalogue, filter for domain renew operations, and emit a Bicep or ARM role definition that grants only those actions. This avoids over-privileging service principals that automate domain renewals.

Call DomainRegistrationProvider_ListOperations and return only the operations whose name contains domains/renew.

Provider Feature Discovery

Azure resource providers add new operations over time. Tooling that wraps the Domains API needs a way to detect when new actions become available — for example, a new validate operation. Calling the provider operations list lets a control plane discover supported actions at runtime and surface only the ones the current API version exposes.

Compare the output of DomainRegistrationProvider_ListOperations across two API versions and emit a diff of added or removed operation names.

Compliance Audit of Domain Permissions

Compliance teams need to verify that no service principal holds blanket permissions on Microsoft.DomainRegistration. By cross-referencing role assignments against the operations catalogue, an audit tool can flag wildcard grants and recommend tightening to specific operations such as domains/read and domains/renew/action only.

Pull the operations list and verify that no role assignment in subscription X holds the wildcard Microsoft.DomainRegistration/* on any scope.

AI Agent RBAC Planning via Jentic

An IAM agent integrated through Jentic can answer a question like what permissions does a service principal need to renew an Azure domain by searching Jentic for list azure domain registration operations, calling DomainRegistrationProvider_ListOperations, and returning only the relevant action strings. This makes least-privilege role definition a one-prompt task.

Through Jentic, search for list azure domain registration operations, load DomainRegistrationProvider_ListOperations, execute it, and return the action names that mention domain.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for domainregistrationprovider api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.DomainRegistration/operations

List CSM operations supported by Microsoft.DomainRegistration

GET

/providers/Microsoft.DomainRegistration/operations

List CSM operations supported by Microsoft.DomainRegistration

Why Jentic?

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

Credential isolation

The Azure AD client secret or certificate is stored encrypted in the Jentic vault (MAXsystem). The agent receives a bearer token scoped to management.azure.com only — the underlying credential never enters the agent context.

Intent-based discovery

Agents search by intent (e.g. 'list azure domain registration operations') and Jentic returns the DomainRegistrationProvider_ListOperations operation with its empty input schema, so the agent calls it directly without crawling ARM docs.

Time to first call

Direct integration: a few hours for AAD token acquisition, ARM URL construction, and response parsing. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using DomainRegistrationProvider API Client API through Jentic.

Why is there no official OpenAPI spec for DomainRegistrationProvider API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DomainRegistrationProvider API Client 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 DomainRegistrationProvider API Client use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs read access at the appropriate scope. Through Jentic, the underlying client secret stays in the Jentic vault and the agent receives only a scoped bearer token.

What does DomainRegistrationProvider_ListOperations return?

GET /providers/Microsoft.DomainRegistration/operations returns the catalogue of CSM operations the provider supports, each with a name like Microsoft.DomainRegistration/domains/read and a display object describing the operation in natural language. Use this list to build custom RBAC roles or audit role assignments.

What are the rate limits for the DomainRegistrationProvider API Client?

Standard Azure Resource Manager subscription-scoped read throttling applies (broadly 12,000 reads per hour). Because this API exposes a single read endpoint with a small response payload, throttling is rarely the binding constraint.

How do I list provider operations through Jentic?

Run pip install jentic, search for list azure domain registration operations, load DomainRegistrationProvider_ListOperations, and execute it with no parameters. The response is the array of operation definitions ready to drop into a role-definition tool.

Does this API let me register or renew domains?

No. This API only lists provider operations metadata. To purchase, renew, or manage Azure-bought domains use the separate Domains API Client (azure.com/domains-api-client) on the same Microsoft.DomainRegistration provider.