
# Principles of resource groups

<Definition name="Resource Groups">
A logical container for resources deployed on Azure
</Definition>

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

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

Resource groups are a scope for applying RBAC to limit access to allow
only what is needed

# Using tagging to organise resources

<Definition name="Tags">
Name/value pairs of text data that you can apply to resources and resource groups
</Definition>

A resource can have up to 50 tags

Tags can be used to group billing data or to keep track of usage for
different projects

Not all resources support tags, so you need to check if your resource
supports them

# Resource locks

<Definition name="Resource Locks">
A setting that can be applied to any resource to block modification or deletion
</Definition>

Resource locks can be either:

-   Delete - Allow all operations against the resource but block the
    ability to delete it

-   Read-only - Only allow read activities to be performed against it,
    blocking any modification or deletion of the resource


Control and organize Azure resources with Azure Resource Manager

Architecture_and_Service.md

Compute.md

Core_Cloud_Services.md

Costs_and_Spending.md

Creating_an_account.md

Data_Storage.md

Managing_Services.md

Networking.md

Policy.md

Principles_of_cloud_computing.md

Resource_Manager.md

Security.md

AZ900

Certifications

Commands.md

GitKraken.md

Introduction.md

Fork_and_PR.md

GitHub

Boilerplate.md

Links_and_Images.md

Lists.md

Tables.md

Text_Formatting.md

HTML

Code.md

Markdown

Open_Source

Information_Theory

Cuckoo_Hashing.md

Probability.md

DADS

University_Illustrations

notes