Microsoft Azure Domain Services Resource Provider

Name: Domain Services Resource Provider API
Brand: Domain Services Resource Provider
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthDirectory Servicesoauth27 EndpointsREST

For Agents

Provision, update, list, and delete Azure AD Domain Services managed domains so VMs and applications can perform domain join, LDAP bind, and Kerberos authentication.

Install Jentic One Beta

Connect the Domain Services Resource Provider to your agent

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

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 Domain Services Resource Provider API.

Provision a managed Azure AD Domain Services instance in a chosen region and VNet

Update a domain service to change SKU, replica sets, or notification settings

List every Azure AD Domain Services instance in a subscription

GET STARTED

Start building with Domain Services Resource Provider API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Domain Services Resource Provider API for, with concrete tasks.

★ Lift-and-Shift of Domain-Joined Workloads

Migrating on-premises VMs that depend on Active Directory typically requires domain controllers in Azure. Azure AD Domain Services removes that operational overhead by providing a managed domain. Using DomainServices_CreateOrUpdate an automation agent can stand up a managed domain inside a chosen VNet, wait for provisioning to complete, then domain-join migrated VMs without ever deploying a DC.

Create an Azure AD Domain Services instance named contoso.local in resource group identity-rg with the Standard SKU in eastus2 and return the provisioning state.

Identity Inventory Across Subscriptions

Identity teams in regulated industries need a single inventory of every managed domain in the tenant. By calling DomainServices_List against each subscription the agent can build a complete picture of where AAD DS instances live, which SKU they run on, and which VNets they are wired into, then feed it into compliance dashboards.

Iterate over every subscription the service principal can read and call DomainServices_List, returning a CSV of domain name, SKU, and provisioning state.

Decommissioning Stale Managed Domains

Managed domains accrue cost even when the workloads using them have been retired. By listing domains and inspecting the joined resources, an agent can identify candidates with no active VMs in the same VNet and call DomainServices_Delete after approval. This delivers steady identity-platform cost reduction.

Find any Azure AD Domain Services instance in resource group legacy-rg with no domain-joined VMs over the past 30 days, then delete it.

AI Agent Identity Provisioning via Jentic

An identity automation agent integrated through Jentic can resolve a request like stand up a managed domain for the new finance app end-to-end. It searches Jentic for create azure ad domain services, loads the DomainServices_CreateOrUpdate schema, supplies the domain name and VNet ID, and returns the provisioning status. Credentials never leave the Jentic vault.

Through Jentic, search for create azure ad domain services, load DomainServices_CreateOrUpdate, and provision contoso.local with the Standard SKU in eastus2.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for domain services resource provider, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Create or update a managed domain

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Get a managed domain

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Update a managed domain

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Delete a managed domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AAD/domainServices

List managed domains in a subscription

GET

/providers/Microsoft.AAD/operations

List operations on the Microsoft.AAD resource provider

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Create or update a managed domain

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Get a managed domain

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Update a managed domain

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName}

Delete a managed domain

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AAD/domainServices

Why Jentic?

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

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault (MAXsystem). The agent receives a short-lived bearer token scoped to management.azure.com — the underlying secret or certificate stays out of agent context.

Intent-based discovery

Agents search by intent (e.g. 'create azure ad domain services') and Jentic returns the matching DomainServices_* operation with its full input schema, so the agent picks the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-2 days for AAD token acquisition, ARM URL construction, and async LRO polling. Through Jentic: under 30 minutes — search, load schema, execute (provisioning itself still takes 30-60 minutes server-side).

FAQs

Specific to using Domain Services Resource Provider API through Jentic.

Why is there no official OpenAPI spec for Domain Services Resource Provider?

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

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs at least Contributor on the target resource group plus permission to create resources in the Microsoft.AAD provider. Through Jentic, Azure credentials live in the Jentic vault and the agent only sees a scoped bearer token.

Can I create a managed domain in any region with this API?

AAD DS supports a defined set of regions. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AAD/domainServices/{domainServiceName} accepts a location field, but the API will reject the call if the region is not supported by AAD DS. Check the location field of an existing instance for valid values in your tenant.

What are the rate limits for the Domain Services Resource Provider?

Azure Resource Manager applies the standard subscription-scoped throttling (broadly 12,000 reads per hour and 1,200 writes per hour). Create and update on a managed domain are long-running operations: expect 30-60 minutes for initial provisioning. Poll DomainServices_Get and check provisioningState until it reads Succeeded.

How do I provision a managed domain through Jentic?

Run pip install jentic, search for create azure ad domain services, load the DomainServices_CreateOrUpdate schema, supply domainServiceName, location, domainName, and the subnet resource ID, then execute. The call returns 202 with a long-running operation URL — poll DomainServices_Get until the provisioning state is Succeeded.

Does this API manage Azure Active Directory tenants or users?

No. This API manages AAD Domain Services instances — the managed domain that VMs join. To manage Azure AD users, groups, or applications, use the Microsoft Graph API instead.

Microsoft Azure Domain Services Resource Provider

Connect the Domain Services Resource Provider to your agent

Capabilities

Start building with Domain Services Resource Provider API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs