# Azure Virtual Machines

Sedai continuously analyzes Azure VM utilization and autonomously right-sizes instances and purchasing — safety checks and audit trails included.

## Right-Size Every Azure VM, Autonomously

Most Azure VM fleets are provisioned for peak load and never revisited, leaving teams paying for capacity they rarely use. Sedai continuously analyzes utilization patterns and right-sizes VMs (in-family, cross-family, and burstable) while optimizing purchasing, so your fleet matches actual demand.

## VM Optimization Isn't a One-Time Sizing Decision.

Azure gives you dozens of VM families and sizes, but choosing right the first time isn't the same as staying right. Workloads drift, teams estimate for the worst case, and manual rightsizing can't keep pace across a growing fleet.

### Peak-load estimates become the safe default, and the safe default becomes permanent.

Downsizing without deep analysis risks throttling or availability issues, so teams round up instead, and the gap between allocated and actual usage compounds every month.

### Rightsizing doesn't scale with the fleet.

Tracking utilization and adjusting instance types across hundreds or thousands of VMs by hand can't keep up with how fast workload patterns shift.

### Azure's VM catalog adds another layer of difficulty.

Azure's VM catalog adds another layer of difficulty. With general-purpose, compute-optimized, memory-optimized, and burstable families all in play, matching the right family — not just the right size — to a workload's actual profile is its own analysis problem.

## How We Help

### Continuous VM Right-Sizing

Sedai analyzes utilization data to right-size VMs — in-family for consistency, cross-family for true mismatches, or burstable B-series where usage patterns fit.

### Safe, Autonomous Execution

Sedai applies changes with built-in safety checks, audit trails, and health monitoring — or via Copilot mode for teams who want to approve first.

### Purchasing Optimization

Get recommendations across on-demand, reserved instances, and savings plans, layered on top of rightsizing to minimize total compute spend.

## Stop Sizing for Peak.

Start Paying for Actual.

## Frequently Asked Questions

### Does Sedai support all Azure VM families, including B-series burstable instances?

Yes. Sedai works across Azure's VM families — general-purpose, compute-optimized, memory-optimized, and burstable B-series — and factors family-specific behavior, like CPU credit accumulation for B-series, into its recommendations.

### Will resizing a VM cause downtime?

Changing a VM's size in Azure requires a restart to take effect. Sedai schedules these changes to minimize disruption and monitors application health afterward, rolling back automatically if instability follows.

### What's the difference between in-family and cross-family recommendations?

In-family changes keep a workload on the same VM family (e.g., D4s\_v5 to D2s\_v5) for architectural consistency. Cross-family changes move a workload to a fundamentally better-suited family, such as when a CPU-bound workload is running on memory-optimized hardware.

### Can I review changes before Sedai applies them?

Yes. Copilot mode surfaces every recommendation for approval before execution, for teams that want oversight before autonomous action.

### Does Sedai only rightsize instances, or does it also help with purchasing?

Both. Sedai optimizes vertical scaling (instance size) and horizontal scaling (instance count), and separately recommends the most cost-effective purchasing option — on-demand, reserved instances, or savings plans — for your workload.