Az 104 — Azure Resource Groups & Tags

· All resources must be in a resource group and a resource can only be a member of a single resource group.

· Resource groups can’t be nested.

· If you delete a resource group, all resources contained within are also deleted.

· Organizing resources by life cycle can be useful in non-production environments, where you might try an experiment, but then dispose of it when done.

· Resource groups make it easy to remove a set of resources at once.

· Note that you may also see a resource group called NetworkWatcherRG.

You can ignore this resource group, it’s created automatically to enable Network Watcher in Azure virtual networks.

· Tags are name/value pairs of text data that you can apply to resources and resource groups.

· Tags allow you to associate custom details about your resource, in addition to the standard Azure properties a resource has the following properties:

• department (like finance, marketing, and more)
• environment (prod, test, dev)
• cost center
• life cycle and automation (like shutdown and startup of virtual machines)

· A resource can have up to 50 tags.

· The name is limited to 512 characters for all types of resources except storage accounts, which have a limit of 128 characters.

· The tag value is limited to 256 characters for all types of resources.

· Tags aren’t inherited from parent resources.

· Not all resource types support tags, and tags can’t be applied to classic resources.