Google Managed Service for Microsoft Active Directory API
Browse all Google APIs41
AI ReadinessFoundational (D-)41/100
Official vendor OpenAPI document · agent-readyIdentity AuthDirectory Servicesoauth228 EndpointsREST
For Agents
Provision and manage Google Cloud's managed Microsoft Active Directory: create domains, attach trusts, extend the schema, configure LDAPS, run backups, and join machines to the domain.
Use for: Provision a new managed Microsoft AD domain in us-central1, Attach a forest trust between my managed domain and our on-premises AD, Extend the schema of my managed AD with a custom attribute, Configure LDAPS on a managed Microsoft AD domain
Not supported: Does not handle AD user accounts, group policy, or DNS records inside the domain - use for managed domain lifecycle, trusts, schema, LDAPS, backups, and migration only.
Managed Service for Microsoft Active Directory provides a hardened, highly available Microsoft AD running on Google Cloud, with the API covering domain provisioning, trust relationships, schema extension, LDAPS configuration, backups, and migration from existing on-premises forests. Operations are scoped to project locations and most state changes return long-running operation handles for polling. The API also exposes domain-join helpers, peerings, and SQL integration controls used by hybrid Windows workloads.
Install Jentic One Beta
Connect the Managed Service for Microsoft Active Directory API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Managed Service for Microsoft Active Directory API, 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.
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%2Fgoogleapis.com%2Fgoogle-managed-microsoft-ad" | 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%2Fgoogleapis.com%2Fgoogle-managed-microsoft-ad" | 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.
Capabilities
What an agent can do with Managed Service for Microsoft Active Directory API.
Provision and delete managed Microsoft AD domains in Google Cloud project locations
Attach, detach, validate, and reconfigure forest trusts with on-premises or other AD environments
Extend the AD schema with custom attributes via the extendSchema operation
Configure and update LDAPS settings on a managed domain
Trigger and restore from domain backups for disaster recovery
Initiate, check, disable, and enable migration from an existing AD forest into the managed service
Domain-join machines and manage peerings to connected VPCs
Use Cases
Patterns agents use Managed Service for Microsoft Active Directory API for, with concrete tasks.
★ Hybrid Windows workload identity
Stand up a managed Microsoft Active Directory domain in Google Cloud and attach a forest trust to an existing on-premises AD so that Windows VMs and SQL Server workloads in Google Cloud authenticate users from the corporate directory. The managed service handles patching, replication, and high availability so platform teams do not run their own domain controllers.
Create a managed AD domain named corp.example.com in projects/acme/locations/global, then call attachTrust with the on-premises forest target and validate the trust
AD forest migration to Google Cloud
Migrate from a self-managed Active Directory forest into Managed Microsoft AD using the migration endpoints, which let you check, enable, and disable migration permission and execute the cutover. The flow keeps existing SIDs and group memberships so workloads continue to authenticate without reconfiguration.
Call checkMigrationPermission on the source domain, enableMigration if eligible, and poll the returned operation until cutover is complete
Schema extension and LDAPS hardening
Extend the managed AD schema to add custom attributes that downstream applications require, and configure LDAPS so applications that demand encrypted LDAP can bind securely to the managed domain. The schema extension and LDAPS update endpoints both return long-running operations.
Call extendSchema with the LDIF describing a new employeeBadgeID attribute, then update the domain's ldapssettings to enforce LDAPS only
Agent integration via Jentic
AI agents managing Windows fleets on Google Cloud can use this API through Jentic to provision domains, join VMs, or kick off backups without holding the underlying OAuth refresh token in the prompt. Long-running operation handles are returned for the agent to poll.
Call domainJoinMachine for the VM corp-app-1 in projects/acme and confirm the join completes by polling the returned operation
Key Endpoints
28 endpoints — managed service for microsoft active directory provides a hardened, highly available microsoft ad running on google cloud, with the api covering domain provisioning, trust relationships, schema extension, ldaps configuration, backups, and migration from existing on-premises forests.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/domains
List managed AD domains in a location
DELETE
/v1/{+name}
Delete a managed AD domain
POST
/v1/{+name}:attachTrust
Attach a forest trust
POST
/v1/{+domain}:extendSchema
Extend the AD schema
POST
/v1/{+domain}:domainJoinMachine
Join a machine to the managed domain
POST
/v1/{+domain}:checkMigrationPermission
Check AD migration eligibility
POST
/v1/{+domain}:enableMigration
Enable migration mode
GET
/v1/{+name}/ldapssettings
Read LDAPS settings
GET
/v1/{+parent}/domains
List managed AD domains in a location
DELETE
/v1/{+name}
Delete a managed AD domain
POST
/v1/{+name}:attachTrust
Attach a forest trust
POST
/v1/{+domain}:extendSchema
Extend the AD schema
POST
/v1/{+domain}:domainJoinMachine
Join a machine to the managed domain
POST
/v1/{+domain}:checkMigrationPermission
Check AD migration eligibility
POST
/v1/{+domain}:enableMigration
Enable migration mode
GET
/v1/{+name}/ldapssettings
Read LDAPS settings
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Managed Service for Microsoft Active Directory API
- Foundational (D-)41/100
67
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security55
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
68%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
74%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
55
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
55%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Managed Service for Microsoft Active Directory API by hand means setting up Google OAuth 2.0 with the cloud-platform scope, refreshing bearer tokens, and polling long-running domain operations yourself against the managedidentities.googleapis.com host. Through Jentic you install once, import the Managed Service for Microsoft Active Directory API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the managed domain name in the URL path (/v1/{+domain}... and /v1/{+name}...), so a rule can pin your agent to one managed domain: it can attach trusts and read LDAPS settings there and nothing else. You choose the operations it may call, so destructive ones like domain deletion or enabling migration are not included unless you add them.
Credential isolation
Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'provision a managed Active Directory domain' or 'attach an AD trust', and Jentic returns the matching managed-AD operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Managed Service for Microsoft Active Directory API through Jentic.
What authentication does the Managed Microsoft AD API use?
The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic the OAuth client credentials and refresh tokens are stored encrypted; the agent only ever sees a scoped, short-lived bearer token.
Can I attach a trust to an on-premises AD forest through this API?
Yes, the attachTrust endpoint creates a forest or external trust between a managed domain and a remote forest. You then call validateTrust to confirm the relationship is healthy before relying on it for authentication.
What are the rate limits for this API?
Per-project quotas are listed under the Managed Service for Microsoft AD service in the Google Cloud Console quotas page. Most lifecycle and trust operations are long-running and have concurrency caps in addition to per-minute request limits.
How do I migrate an existing AD forest to managed AD through Jentic?
Search Jentic for migrate active directory to google cloud, load the checkMigrationPermission and enableMigration operations, and execute them in sequence with the domain resource path. Jentic injects the OAuth token and surfaces the returned long-running operation for polling.
Is the Managed Microsoft AD API free?
API calls themselves are not separately billed, but managed AD domains incur a per-hour charge per domain plus network egress. See the Managed Service for Microsoft AD pricing page for current rates.
Does this API let me create AD users or groups?
No, user, group, and OU management happens through standard Windows tools or LDAP clients connected to the running domain. This API manages the domain itself, trusts, schema, LDAPS, backups, and migrations.
Can I limit what my agent is allowed to do with the Managed Microsoft AD API?
Yes. Because this API carries the managed domain name in the URL path (/v1/{+domain} and /v1/{+name}), a rule in your self-hosted Jentic One instance can pin the agent to a single domain, letting it do things like attach trusts or read LDAPS settings there and nothing else. You decide which operations the agent may call, so destructive ones such as domain deletion or enableMigration are excluded unless you add them. Your own rules and your stored OAuth credential control exactly what the agent can reach.
GET STARTED