Prevent surprises in Azure billing with automation!

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

In this video lesson, I go through the steps needed to identify resource groups that need to be removed. You'll use a GitHub Action that logs into Azure and then queries Resource Groups.


Resource Groups are groups of Azure services. If you follow a naming schema, you can then query Resource Groups that can be removed at the end of the day. In this video I use the word "demo" in a resource group, and then query all resource groups that have that word in it.


With that strategy, you can have flexibility by naming your resource groups while making sure they get deleted at the end of the day (or any other schedule you prefer).


Learning objectives:

  1. Create a GitHub Action workflow to query Resource Groups 
  2. Query Resource Groups that match locally
  3. Use scripting to extract Resource Group names
  4. Remove Resource Groups with the Azure CLI in GitHub Actions



Useful resources:



Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.