Azure · Cloud service
Azure Virtual Machines with OrchestrAI
Catalog exported 2026-09-02
Create, list, and delete Azure Virtual Machines from chat, with deletion held for your confirmation.
OrchestrAI exposes 3 Azure VMs operations: 1 is low-risk (read-only or low-impact), and 2 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Teams use OrchestrAI to spin up an Azure VM for a bastion host, a build agent, or a quick experiment, with the size, image, and resource group given in a single message. Listing VMs across resource groups is the fastest way to find machines nobody remembers creating. There is no start, stop, deallocate, or resize operation, so pausing a VM to save cost happens outside OrchestrAI for now.
Every Azure VMs operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List Azure VMs |
List Azure Virtual Machines | Low risk | No |
Create Azure VM |
Create an Azure Virtual Machine | Creates resources | No |
Delete Azure VM |
Delete an Azure Virtual Machine | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an Ubuntu 22.04 VM called bastion-01 in rg-network, size Standard_B2s, in eastus2
- List every virtual machine in the subscription with its resource group and size
- Delete the VM build-agent-3 in rg-ci
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Does OrchestrAI confirm before deleting an Azure Virtual Machine?
- Yes, VM deletion is a high-risk operation and stays pending until you approve the plan it shows.
- Can OrchestrAI stop or deallocate an Azure VM?
- Not in this release, since the three available VM operations are create, list, and delete.
- Which Azure VMs operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete Azure VM. None of them is classed destructive.
Other Azure services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.