Azure Devtest Optimizer

Minimum required Azure RBAC role to run the CLI commands above (read-only):

{
  "role": "Cost Management Reader",
  "scope": "Subscription",
  "note": "Also assign 'Reader' role for VM and subscription inventory"
}

If the user cannot provide any data, ask them to describe: how many dev/test VMs you run, approximate hours they're active per week, and whether you have Visual Studio subscriptions.

Steps

1. Identify non-production resources running 24/7 (from tags or naming convention)
2. Analyze VM uptime metrics — flag resources with > 70% uptime in off-hours
3. Calculate savings from auto-shutdown (nights 7pm–7am + weekends)
4. Assess Dev/Test subscription eligibility
5. Generate Azure Automation runbooks for scheduled start/stop

Output Format

• Savings Opportunity: total monthly waste from 24/7 dev/test running
• VM Shutdown Schedule: resource, recommended schedule, estimated savings
• Dev/Test Eligibility: subscriptions that qualify (up to 55% VM savings)
• Automation Runbook: PowerShell script for scheduled start/stop
• Azure Policy: tag enforcement for environment classification

Rules

• Dev/Test pricing requires Visual Studio subscription — flag eligibility requirements
• Auto-shutdown saves ~60–70% of VM cost for standard business-hours usage
• Flag VMs that may need to stay on (build agents, monitoring, scheduled jobs)
• Include Logic App alternative for schedule management via portal
• Never ask for credentials, access keys, or secret keys — only exported data or CLI/console output
• If user pastes raw data, confirm no credentials are included before processing