Resource groups are a fundamental element of the Azure platform.

A resource group is a
logical container for resources deployed on Azure.

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. Before any resource can be provisioned, you need a
resource group for it to be placed in.

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.

RBAC provides fine-grained access management for Azure resources, enabling you to
grant users the specific rights they need to perform their jobs. RBAC is considered a
core service and is included with all subscription levels at no cost.

Resource locks are a setting that can be applied to any resource to block modification or
deletion. Resource locks can set to either Delete or Read-only.

 Delete will allow all operations against the resource but block the ability to delete it.
 Read-only will only allow read activities to be performed against it, blocking any
modification or deletion of the resource.

Even if you are an owner of the resource, you must still remove the lock before you'll
be able to perform the blocked activity.

Predict costs and optimize spending for Azure

The key takeaway is that resources are always charged based on usage.

For example, if you de-allocate a VM then you will not be billed for

1. compute hours,
2. I/O reads or writes or
3. the private IP address since the VM is not running and has no allocated
compute resources.

However, you will incur storage costs for the disks. De-allocating a VM is not the same
as deleting a VM. De-allocation means the VM is not assigned to a CPU or network in
a datacentre. It's like turning off your physical computer. However, your persistent disks
remain, and the resource is present in your subscription.

Costs are resource-specific, so the usage that a meter tracks and the number of
meters associated with a resource depend on the resource type.

27 | P a g e