What authentication does the VMwareCloudSimple API use?

The API uses Azure Active Directory OAuth 2.0 via the implicit flow scheme `azure_auth` defined in the spec, scoped to user_impersonation against https://management.azure.com. When called through Jentic, the OAuth token is held in your Jentic One instance and only short-lived scoped credentials are exposed to the agent.

Can I provision a VMware private cloud with this API?

Yes. The PUT operation on /subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds/{pcName} provisions a private cloud in the specified region, and the matching operationResults endpoint lets you poll until the long-running operation completes.

What are the rate limits for the VMwareCloudSimple API?

The spec does not declare explicit rate limits. Calls go through Azure Resource Manager, which enforces standard ARM throttling per subscription and per region. Inspect the x-ms-ratelimit-remaining-subscription-* response headers in production to see remaining quota.

How do I list dedicated cloud nodes through Jentic?

Search Jentic for 'list azure vmware dedicated cloud nodes', load the operation schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/dedicatedCloudNodes, then execute it with your subscriptionId. Install with `pip install jentic` and use the async search/load/execute pattern.

Does this API cover guest OS configuration inside the VM?

No. The API manages the placement and lifecycle of VMs and private clouds at the Azure control plane only. Guest OS configuration, application installation, and in-guest patching are not in scope and must be handled by VMware tooling or configuration management running inside the VM.

Can I limit what my agent is allowed to do with the Microsoft Azure VMwareCloudSimple API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the API carries the subscription, region, and private cloud name in the URL path, so you can pin the agent to a single private cloud or region and nothing else. You choose which operations it may call, so read-only calls like listing private clouds, dedicated cloud nodes, or SKU availability can be enabled while anything that deletes a dedicated cloud node or virtual machine stays out unless you add it. The stored Azure AD token is injected at execution time and never enters the agent's prompt or logs.