Microsoft Azure VMwareCloudSimple

Name: VMwareCloudSimple API
Brand: VMwareCloudSimple
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth234 Endpoints

Install Jentic One Beta

Connect the VMwareCloudSimple to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VMwareCloudSimple, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 VMwareCloudSimple API.

Provision and tear down VMware private clouds in specific Azure regions under a subscription

Reserve and release dedicated cloud nodes for isolated VMware workloads

Create virtual machines from VM templates and attach them to virtual networks

GET STARTED

Start building with VMwareCloudSimple API

Explore with Jentic

View OpenAPI Document

For Agents

Provision VMware private clouds, dedicated nodes, and virtual machines on Azure CloudSimple, and inspect available SKUs and regions through the Azure Resource Manager control plane.

Use for: Provision a new VMware private cloud in an Azure region, List all dedicated cloud nodes in my subscription, Find which VM templates are available in a private cloud, Check SKU availability before reserving a CloudSimple node

Not supported: Does not handle guest OS configuration, application deployment, or in-guest patching - use for Azure CloudSimple control plane operations only.

Use Cases

Patterns agents use VMwareCloudSimple API for, with concrete tasks.

★ Lift-and-shift VMware workloads to Azure

Migrate existing on-premises VMware workloads to Azure by provisioning a CloudSimple private cloud, reserving dedicated nodes, and creating virtual machines from existing templates. The API exposes the full ARM lifecycle for private clouds and nodes so migration can be scripted end to end. Typical first-pass provisioning takes minutes once SKU and region availability have been confirmed.

Create a private cloud named prod-vmw-eastus in region eastus with one dedicated node SKU and verify the operation reaches succeeded state.

Capacity planning for VMware private clouds

Query availability of CloudSimple SKUs across regions before placing capacity, so finance and platform teams can plan reservations against dedicated cloud nodes. The availabilities and dedicatedCloudServices endpoints expose what can be provisioned where, allowing agents to pre-validate capacity before initiating long-running provisioning calls.

List all availabilities under regionId=eastus2 and report which dedicated cloud node SKUs have remaining capacity.

Automated VM provisioning from templates

Stand up VMware virtual machines from existing VM templates on a CloudSimple private cloud and attach them to specific virtual networks and resource pools. The virtualMachineTemplates, virtualNetworks, and resourcePools endpoints provide everything needed to drive a templated VM build from an automation runner.

Create a virtual machine named app-01 from template tpl-rhel8 on private cloud pc-prod, attached to network vnet-app, and confirm the deployment status.

Agent-driven infrastructure operations on CloudSimple

Let an AI agent drive routine CloudSimple operations such as listing private clouds, retrieving node status, and polling operation results, using Jentic to discover and call the right management plane endpoints without hand-coding ARM URIs. This lets ops teams expose VMware-on-Azure runbooks as agent tools.

Search Jentic for 'list azure vmware private clouds', load the operation schema, and execute it against subscription 00000000-0000-0000-0000-000000000000.

Key Endpoints

34 endpoints — jentic publishes the only available openapi specification for vmwarecloudsimple, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds

List private clouds in a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds/{pcName}

Get a private cloud by name

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/dedicatedCloudNodes

List dedicated cloud nodes

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/availabilities

List availability for SKUs in a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds/{pcName}/customizationPolicies

List customisation policies on a private cloud

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/operationResults/{operationId}

Track a long-running operation

GET

/providers/Microsoft.VMwareCloudSimple/operations

List all available operations under the provider

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds

List private clouds in a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds/{pcName}

Get a private cloud by name

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/dedicatedCloudNodes

List dedicated cloud nodes

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/availabilities

List availability for SKUs in a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.VMwareCloudSimple/locations/{regionId}/privateClouds/{pcName}/customizationPolicies

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD token 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 'list VMware private clouds in a region' or 'check CloudSimple node availability', and Jentic returns the matching VMwareCloudSimple operation with its input schema so the agent calls the right ARM endpoint without browsing Microsoft docs.

Time to first call

FAQs

Specific to using VMwareCloudSimple API through Jentic.

Why is there no official OpenAPI spec for VMwareCloudSimple?

Microsoft Azure does not publish a standalone OpenAPI specification for the VMwareCloudSimple management API. Jentic generates and maintains this spec from the published Azure REST API definitions so that AI agents and developers can call VMwareCloudSimple via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

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.