Every Azure VM you manage. One command surface.
AzCmd schedules, starts, stops, and runs commands on Azure virtual machines across all of your tenants — from a single console, secured end-to-end by Microsoft Entra.
Built for teams that run VMs in more than one tenant
MSPs, consultancies, and IT teams shouldn't have to switch directories, juggle credentials, or write one-off runbooks just to manage compute.
Scheduling that cuts spend
Start and stop VMs on calendars, business hours, or tags. Dev and test machines stop burning money nights and weekends — automatically.
True multi-tenant control
Connect every customer or business-unit tenant once, then operate across all of them from a single console with per-tenant scoping.
Commands, on demand
Run operational commands against fleets of VMs — targeted by tenant, subscription, or tag — without RDP sessions or scattered scripts.
Everything on the record
Every action, schedule change, and command run is logged with who, what, where, and when. Answers are one search away.
Roles that match reality
Give engineers, help desk, and client contacts exactly the tenants and actions they need — and nothing more.
Fleet at a glance
Live power state and schedule coverage across every connected tenant, so you can see what's running and why.
Connected in minutes, not migrations
Connect a tenant
An admin grants consent through standard Microsoft Entra sign-in. No agents to install on VMs, no credentials to hand over.
Define schedules & policies
Target VMs by tenant, subscription, resource group, or tag. Set start/stop windows and the commands you want available.
Let it run
AzCmd executes on schedule and on demand, and keeps a complete audit trail of every action across every tenant.
Security is the architecture, not a feature
AzCmd was built by security practitioners for environments where access to customer tenants is a responsibility, not a convenience.
- ✓Microsoft Entra throughout. Sign-in and tenant consent use Entra — your identities, your conditional access policies.
- ✓Certificate-based service connections. Tenant connectors authenticate with certificates, not shared secrets or stored passwords.
- ✓Least-privilege by design. Permissions are scoped to the VM operations AzCmd performs — nothing broader.
- ✓Isolated per tenant. Each customer tenant is a separate, revocable connection. Pull consent and access ends immediately.
Frequently asked questions
?What is AzCmd?
AzCmd is a multi-tenant Azure VM automation platform. It schedules, starts, stops, and runs commands on Azure virtual machines across every Microsoft Entra tenant you manage — from a single console, without switching directories or juggling credentials.
?Does AzCmd require agents on my VMs?
No. AzCmd connects to each tenant through standard Microsoft Entra admin consent. There are no agents to install on VMs and no credentials to hand over.
?How does AzCmd authenticate to customer tenants?
Sign-in and tenant consent use Microsoft Entra, so your identities and conditional access policies apply. Tenant connectors authenticate with certificates rather than shared secrets or stored passwords, and permissions are scoped to the VM operations AzCmd performs.
?How much can scheduling Azure VMs save?
Azure bills VMs for every hour they run. A dev or test VM that is only needed during business hours spends most of the week idle, so stopping it automatically on nights and weekends can cut its compute cost by more than half.
?Who is AzCmd built for?
MSPs, consultancies, and IT teams that run Azure VMs in more than one tenant — anyone who manages compute across customer or business-unit directories and wants one place to schedule, operate, and audit it.
?Can I revoke AzCmd's access to a tenant?
Yes. Each tenant is a separate, revocable connection. Pull the Entra consent for a tenant and AzCmd's access to it ends immediately.
Take command of your Azure fleet
AzCmd is onboarding early access customers now. Tell us about your environment and we'll get you connected.