A week ago, one of our team member modified a script that clean (removes) Azure resources, based on a naming convention. Because the number of our Azure Subscription is limited, the Development Team is sharing the same subscription between them and for DEV and TEST environment. To be able to have a control on resources and trace the owner of them we have: Naming conventions: A prefix that specify the owner of the resource or the environment rvteststorage (rv - Radu Vunvulea) dv (Dev Environment) tt (Test Environment) ... Azure Resource Groups that give us the possibility to group resources together. As we can see in the above diagram, Azure Resource Groups can be used with success to group together different resources that have a logic for your application or from a business perspective. Coming back to the initial cleaning script, there was a small bug in the script, that didn't took into account the prefix of Azure Resource Groups and removed all the resou
DREAMER, CRAFTER, TECHNOLOGY ENTHUSIAST, SPEAKER, TRAINER, AZURE MVP, SOLVING HARD BUSINESS PROBLEMS WITH CUTTING-EDGE TECHNOLOGY