:gh:

:azure:

Azure Tags will allow us to better manage our resources and ensure that minimal effort is expended managing cost and resource

Below are details on a RFC from Azure Practice in regards to how to best accomplish this

Business Level - Understand and Manage

Environment Level - Support and Maintain

Engineering Level - Automate, Facilitate IaC/Automation, Simplify BAU

Auto-Expiry Requirements

As an Azure User within Contino, I would like….

to have some stuff I deploy in my Azure subscription to not be incurring charges while Im not using it
to not have to think about “fire and forget” projects I spin up

As an Azure Billing Owner within Contino, I would like…

Development level subscriptions for engineering to have an accountable owner that is flagged if not periodically reviewed
Development level “hard stop” resource deletion/stop/review that exceeds an extended limit that, as warned by a budget warning and a budget excess, the user has not agreed or reviewed
Tag based granular “hands-off” automation tool set

define Tag Names with a sub-set of available pre-sets that we as an org scan for, and then act on - controlled by the user

caution around tagging and re-tagging outside any IaC delivered resources that may see the change as a “change!” and cause a re-deployment!

Paul K space : Org-Wide Resource Automated Actions (Tags)