Developer Tools · Integration
Azure Virtual Machines
Add Azure Virtual Machines to your product for your customers, and give your AI agents governed access to it.
Embed an Azure Virtual Machines integration so your customers can inspect and manage compute from inside your product, with access scoped per tenant and every call audited. fastn handles each customer's credentials and API upkeep, so infrastructure operations do not need an integration per subscription.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read VM inventory, size, and power state into your product.
Start, stop, or restart machines from your product with permissions you control.
Read attached disks and network configuration for context.
Trigger your product when a machine changes power state.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads VM state and tags before recommending an action.
An agent stops an idle machine within governed permissions.
An agent reacts to a state change and updates the incident record.
Example prompt
List running virtual machines with no owner tag and low CPU over the last week.
Set up Azure Virtual Machines in 4 steps
- 01Open the Azure Virtual Machines connector from your fastn dashboard.
- 02Have each customer authenticate their Azure subscription with least-privilege scopes.
- 03Map the subscriptions and resource groups your product covers, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Azure Virtual Machines integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Azure Virtual Machines integration without building it. Your customers connect their own Azure Virtual Machines account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Azure Virtual Machines update is not your on-call problem.
- One integration serves your product and your agents. The same governed Azure Virtual Machines connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
Amazon EC2
AzureWorks well with
Azure MonitorOften used alongside
Tools the same teams tend to run next to Azure Virtual Machines, across other categories.
Slack
Snowflake
Airtable
PostgreSQLAzure Virtual Machines integration FAQ
How do I add an Azure Virtual Machines integration to my product?
Enable the Azure Virtual Machines connector in your fastn dashboard, then let each customer authenticate their own Azure Virtual Machines account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Azure Virtual Machines client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Azure Virtual Machines account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Azure Virtual Machines account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Azure Virtual Machines integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads VM state and tags before recommending an action.
Who maintains the Azure Virtual Machines integration?
fastn does. When Azure Virtual Machines changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Azure Virtual Machines events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Azure Virtual Machines?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Azure Virtual Machines integration?
A common starting point: read VM inventory, size, and power state into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Azure Virtual Machines integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Azure Virtual Machines does not change your per-connector cost. You can start free with 3 connected accounts.
Add Azure Virtual Machines to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.