Microsoft Azure Guest Diagnostic Settings Association

What authentication does this API use?

It uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. Through Jentic, your service principal credentials sit in the encrypted vault and are exchanged for a scoped bearer token at execution.

Does this API define what gets collected?

No. The list of event logs and perf counters lives in the companion Guest Diagnostic Settings API (azure.com/guest-diagnostic-settings). This Association API only binds an existing settings resource to a target VM or Arc machine via PUT on /{resourceUri}/providers/microsoft.insights/guestDiagnosticSettingsAssociation/{associationName}.

What are the rate limits?

Standard ARM throttles apply at the subscription level - roughly 12,000 reads and 1,200 writes per hour. Bulk onboarding scripts that attach a profile to many VMs should batch and back off on 429 responses.

How do I attach a diagnostic profile to a VM through Jentic?

Run jentic.search('attach guest diagnostic settings to azure vm'), load the GuestDiagnosticsSettingsAssociation_CreateOrUpdate schema, and execute it with the VM's resource URI, an association name such as 'default', and a body referencing the guestDiagnosticSettings resource ID.

Can I limit what my agent is allowed to do with the Guest Diagnostic Settings Association API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use with this API. Since every association is keyed on the target resource URI and association name in the path, you can pin the agent to a single VM or Arc machine, and you choose which operations it may call, so you can leave it with the list, get, and create-or-update operations while withholding the destructive delete. Your Azure AD client credentials stay in your instance and are injected as a scoped bearer token, never reaching the agent's prompt or logs.