Automate Google Managed for Microsoft Active Directory
HumDay reads Google Managed for Microsoft Active Directory’s own published API description and derives 29 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Managed for Microsoft Active Directory is
The Managed Service for Microsoft Active Directory API is used for managing a highly available, hardened service running Microsoft Active Directory (AD).
API host: managedidentities.googleapis.com
What HumDay can do in Google Managed for Microsoft Active Directory
20 documented operations change something in Google Managed for Microsoft Active Directory.
- POSTAdds AD trust in a given domain.
/v1alpha1/{name}:attachTrust - POSTCreates a Backup for a domain.
/v1alpha1/{parent}/backups - POSTCreates a Microsoft AD Domain in a given project.
/v1alpha1/{parent}/domains - POSTCreates a Peering for Managed AD instance.
/v1alpha1/{parent}/peerings - DELETEDeletes identified Peering.
/v1alpha1/{name} - PATCHUpdates the labels for specified Peering.
/v1alpha1/{name} - POSTStarts asynchronous cancellation on a long-running operation.
/v1alpha1/{name}:cancel - POSTRestoreDomain restores domain backup mentioned in the RestoreDomainRequest
/v1alpha1/{name}:restore - POSTRemoves identified trust.
/v1alpha1/{name}:detachTrust - POSTValidate the trust state Operation
/v1alpha1/{name}:validateTrust - POSTExtend Schema for Domain
/v1alpha1/{domain}:extendSchema - POSTUpdates the dns conditional forwarder.
/v1alpha1/{name}:reconfigureTrust - POSTSets the access control policy on the specified resource.
/v1alpha1/{resource}:setIamPolicy - POSTDomainJoinMachine API joins a Compute Engine VM to the domain
/v1alpha1/{domain}:domainJoinMachine - POSTReturns permissions that a caller has on the specified resource.
/v1alpha1/{resource}:testIamPermissions - POSTAuditMigration API gets the current state of DomainMigration
/v1alpha1/{domain}:checkMigrationPermission - PATCHPatches a single ldaps settings.
/v1alpha1/{name}/ldapssettings - POSTEnable Domain Migration
/v1alpha1/{domain}:enableMigration - POSTDisable Domain Migration
/v1alpha1/{domain}:disableMigration - POSTResets managed identities admin password identified by managedidentitiesadminname
/v1alpha1/{name}:resetAdminPassword
What HumDay can read from Google Managed for Microsoft Active Directory
These are the operations a schedule or a trigger can watch.
- GETGets details of a single Peering.
/v1alpha1/{name} - GETGets the access control policy for a resource.
/v1alpha1/{resource}:getIamPolicy - GETLists information about the supported locations for this service.
/v1alpha1/{name}/locations - GETLists Backup in a given project.
/v1alpha1/{parent}/backups - GETLists Domains in a given project.
/v1alpha1/{parent}/domains - GETLists operations that match the specified filter in the request.
/v1alpha1/{name}/operations - GETLists Peerings in a given project.
/v1alpha1/{parent}/peerings - GETGets the domain ldaps settings.
/v1alpha1/{name}/ldapssettings - GETLists SQLIntegrations in a given domain.
/v1alpha1/{parent}/sqlIntegrations
How automating Google Managed for Microsoft Active Directory works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Managed for Microsoft Active Directory account.
- Grant access, then go live. You approve the specific Google Managed for Microsoft Active Directory operations it may use — and only those.
Automate Google Managed for Microsoft Active Directory with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Managed for Microsoft Active Directory automation
- Can HumDay connect to Google Managed for Microsoft Active Directory?
- Yes. HumDay reads Google Managed for Microsoft Active Directory's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 29 operations are documented.
- Do I need to write code to automate Google Managed for Microsoft Active Directory?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Managed for Microsoft Active Directory account.
- What can HumDay do in Google Managed for Microsoft Active Directory?
- 20 of the 29 documented operations change something in Google Managed for Microsoft Active Directory, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Managed for Microsoft Active Directory account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Managed for Microsoft Active Directory is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Managed for Microsoft Active Directory at managedidentities.googleapis.com/$discovery/rest?version=v1alpha1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.