What authentication does the Guest Diagnostic Settings API use?

The API 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 time.

Does this API attach a diagnostic profile to a VM?

No. This API only defines the reusable settings resource itself - the catalogue of event logs and perf counters. To attach a setting to a specific VM or scope, use the companion Guest Diagnostic Settings Association API at azure.com/guest-diagnostic-settings-association.

What are the rate limits?

Azure Resource Manager throttles apply at the subscription level - typically around 12,000 reads and 1,200 writes per hour. Get and List on guestDiagnosticSettings are read operations and unlikely to be throttled in normal use.

How do I create a baseline diagnostic profile through Jentic?

Run jentic.search('create azure guest diagnostic settings'), load the guestDiagnosticsSettings_CreateOrUpdate schema, and execute it with the subscription ID, resource group, settings name, and a body listing the eventLogs and performanceCounters to collect.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and you pick exactly which guestDiagnosticSettings operations it can call. You can leave the agent with only the list, get, and create-or-update operations and withhold the destructive delete of a settings resource unless you explicitly add it. Since the subscription, resource group, and settings name all live in the request path, a rule can also pin the agent to a single diagnostic settings resource in one resource group.