3 Simple Power Automate Workflows to Find and Shut Down Unused Cloud Resources
- Moke Jacobs

- 2 days ago
- 3 min read

Setting up virtual machines, databases, and storage in the cloud is quick and easy. But after projects end, many of these resources keep running. When unused resources build up, called cloud sprawl, your monthly bill can go up without you noticing.
HashiCorp research shows that cloud waste often happens due to skills gaps, idle or underused resources, and overprovisioning.
Why Should You Care About Unused Cloud Resources?
These costs are real and can add up fast. One major industry report found that cloud budgets often go over planned limits by about 17%. That’s why more people are focusing on automation and governance.
Here’s a real-world example: a company used a shutdown policy to automatically turn off non-production environments outside business hours, unless they were tagged as “Production.” This one change reportedly cut non-production costs by about 40%.
The key point isn’t the exact number, but the trend. Most waste goes unnoticed, and automation helps you spot it regularly.
3 Microsoft Power Automate Workflows to Find and Stop Cloud Waste
Manually searching for unused resources can be frustrating and take a lot of time. These workflows help you automate finding, checking, and cleaning up resources, especially if you use Microsoft Azure.
1) Auto-Stop Idle Development VMs
Development and test virtual machines are often a source of waste. Someone might use a VM for a short project, but after it ends, the VM keeps running.
A simple approach:
Run a scheduled flow daily
Pull a list of VMs with a tag like Environment: Dev
Check performance signals (for example, very low CPU usage across several days)
If it’s clearly idle, stop the VM (not delete it)
This saves money immediately, but developers can still restart the VM when they need it.
2) Find Unattached “Orphaned” Disks and Report Them
Even after you remove a VM, its storage disk might be left behind. These disks can keep adding to your monthly charges.
A useful workflow:
Run weekly
List all unattached managed disks
Compile a report with disk name, size, and estimated cost
Email it to the right owners (IT, finance, or cloud ops) for cleanup decisions
This is a good example of 'low risk, high reward' automation because it lets you review what needs attention before deleting anything.
3) Delete Temporary Resources After an Expiration Date
Short-term projects often create temporary resource likes databases, blob containers for transfers, or quick test environments. These are the easiest tomiss.k.
A clean method is to bake an expiration into the process:
Require a tag like Deletion Date (or Expires On) when the resource is created
Run a daily flow to find resources with that tag
If today’s date is past the deletion date, automatically remove the resource
This turns cleanup into a regular habit instead of a last-minute rush once a year.
How to Keep These Automations Safe
Automation is powerful, especially when it can delete resources. That’s why it’s important to have safety controls in place.
Here are smart guardrails:
Start in “report-only mode” (alerts first, no shutdowns/deletions) to validate logic
Add approvals for higher-impact actions (like deleting large disks or databases)
Use tags and exceptions (Production, Critical, Regulatory, etc.) so the flow avoids the wrong targets
Keep an audit trail of what was flagged, who approved it, and what changed
These simple checks help make sure that saving money doesn’t lead to outages.
Take Control of Your Cloud Spend
These three workflows are a great starting point for teams looking to control cloud sprawl. Instead of reacting to surprise bills, you can use a system that automatically finds, reviews, and cleans up unused resources. To learn more about Power Automate Workflows, Contact Ayvant IT today and schedule a free consultation.




Comments