Unintended Resource Deletion Risk
usabilityActiveStableUsing tag-based deletion could inadvertently remove all resources associated with a VM, risking critical infrastructure.
Score Breakdown
Heuristic ranking from public discussion signals — not a validated prediction of commercial opportunity, demand, or willingness to pay.
Composite 68/100 (High, unvalidated). Top driver: Willingness to pay (30% weight, 22.5 pts).
Heuristic only — often urgency map or random scaffolding on ingest, not measured mention frequency. Maps to XPS relevance (with market size).
LLM/mock judgment of intensity from title/summary text — not ops or ticket data. Maps to XPS quality (with willingness to pay).
LLM/mock purchase-intent guess from text — not invoices, surveys, or paid seats. Maps to XPS quality.
Heuristic/scaffold (often random or fixed on insert) — not a verified mention trajectory. Maps to XPS novelty.
Heuristic/scaffold (often random or fixed) — not TAM research. Maps to XPS relevance (with frequency).
Catalog notes (not predictive analysis)
Unintended Resource Deletion Risk (usability). Catalog heuristic opportunity score: 68/100 — a chosen formula over discussion-signal facets, not evidence of demand, conversion, or willingness to pay. Treat as browsing rank, not a commercial prediction.
Using tag-based deletion could inadvertently remove all resources associated with a VM, risking critical infrastructure.
Source Examples
“Expose --tag command to delete all resources that have a tag. **Is your feature request related to a problem? Please describe.** A convenient way to delete all resources with a specific tag. **Describe the solution you'd like** `az resource delete --tag # deletes all resources that have a specific tag.` `az vm delete --tag # deletes all VMs that have a specific tag.` `az network vnet --tag # deletes all vnets that have a specific tag.` Follow up from #4897 `az vm create ... --tags` applies tags to every resource it creates. Using this in conjunction with `az resource delete --tag` will not only delete the VM but every resource that was created to deploy the VM. **Describe alternatives you've considered** **Additional context** - `az vm create's --tags` does not document that the tags are applied to every resource created via VM create. The parameter help should be updated. - @tjprescott suggests implementing a delete_command() type to support tag-based deletion for any command. - It might be good to restrict tag-based deletion to a resource group scope. So that resources with the same tag in another resource-group are not accidentally deleted.”
Competitive Landscape
- Existing solutions are either too expensive or too limited
- Most competitors target enterprise, leaving mid-market underserved
- Community scripts and manual processes are the primary alternative
Recommended Next Steps
- ✓Validate pain intensity with 5-10 target customer interviews
- ✓Build minimal viable solution addressing the core workflow
- ✓Test pricing with early adopters from community forums
Related Pain Points
Target Customers
- IT teams at mid-size organizations (100-2000 employees)
- MSPs and consultants managing multiple client environments
- Teams without dedicated specialist staff for this domain
Monetization Ideas
- 1SaaS subscription model ($99-$499/month depending on scale)
- 2Usage-based pricing aligned with value delivered
- 3Freemium tier to drive adoption and prove value