Skip to main content
Resource groups and service limits in Azure — what they are, why they matter, and how to manage them. Resource groups are logical containers that help you organize and manage Azure resources such as virtual machines, storage accounts, databases, and networking. They provide a convenient scope for role-based access control (RBAC), Azure Policy assignment, cost reporting, and lifecycle operations. Service limits and quotas are the platform guardrails that control how many resources you can provision per subscription, per region, or per resource provider. What you’ll learn
  • How resource groups are used to organize and manage resources
  • Common organization strategies and their trade-offs
  • Key resource group behaviors and constraints
  • How to create a resource group in the portal and reference it when deploying resources
  • How quotas and limits work and how to view or request quota increases

​
What is a resource group?

A resource group is a logical container for Azure resources. It stores control-plane metadata in a specified Azure region, while the resources themselves can be deployed to any supported region. Key characteristics:
  • A resource can belong to only one resource group at a time.
  • Resource group metadata (control plane) is stored in the resource group’s region.
  • Resources inside a group can be deployed to different regions.
  • Resource group names cannot be changed after creation.
  • Resource groups cannot be nested; design your naming and structure accordingly.

​
Common organization strategies

Choose the organization strategy that fits your operational model and governance needs. Note: These are organizational patterns only — they do not alter network connectivity. Resources across resource groups can still communicate when networking (VNets, peering, NSGs) is configured appropriately.

​
Important resource group behaviors

  • You can move resources between resource groups or subscriptions using the Move operation (portal, PowerShell, CLI, REST).
  • Azure Resource Mover is a separate service for moving resources between regions; use it when moving resources across regions.
  • Use tags and consistent naming to improve discoverability and cost allocation.

​
Create a resource group in the Azure portal

Let’s create a resource group through the Azure portal — this demonstrates the portal experience.
A screenshot of the Microsoft Azure portal showing the "Create a resource group" page with fields for Subscription, Resource group (entered as "rg-admin-01"), and Region (set to (US) East US). A large white workspace and a visible mouse cursor are also shown.
To create a resource group from the portal:
  1. Click Create and search for “Resource groups” (or use the left-hand menu).
  2. Select the Subscription where you want to create the group.
  3. Enter the Resource group name (cannot be changed later).
  4. Select the Region for the resource group (this is where the group metadata is stored).
  5. Optionally add Tags for cost allocation and filtering.
  6. Click Review + Create and then Create to finalize.
After the resource group exists, you can select it during resource creation — for example, a storage account.
A screenshot of the Microsoft Azure portal showing the "Create a storage account" wizard. The Basics tab displays project and instance details (subscription, resource group, region, performance options) with form fields and navigation tabs.

​
Create and manage resource groups via CLI, PowerShell, or REST

Examples:
  • Azure CLI
  • Azure PowerShell
Tip: Use Tags and consistent naming conventions to make resource groups easier to search, filter, and report on for cost allocation and policy enforcement.

​
Service limits and quotas (why they matter)

Quotas and limits prevent accidental overprovisioning, protect platform stability, and ensure fair resource distribution across tenants. They are applied at different scopes (subscription, region, resource provider) and may be either adjustable (soft limits) or non-adjustable (hard limits). Practical implications
  • Quotas help you plan capacity (for example, vCPU quotas per region).
  • Soft limits can usually be increased by request; hard limits cannot.
  • If you cannot raise a hard limit, using additional subscriptions can increase capacity but adds management overhead.

​
Quota types and examples

Important: If you are using a free trial or sponsored subscription, quota increase approvals are less likely. Paid production subscriptions generally have a higher chance of approval.

​
Viewing and managing quotas in the portal

To inspect quotas and current usage:
  1. Open the Subscription in the Azure portal.
  2. Go to Usage + quotas (or Limits + quotas / Usage + quotas).
  3. Select the provider or service (for example, Compute or Storage).
  4. Optionally filter by region and review current usage versus quota.
  • The portal indicates which quotas are adjustable and which require a support request.
  • For adjustable quotas, you can often submit a request directly from the portal.
  • For non-adjustable limits, consider alternative strategies such as additional subscriptions.
Useful links and references

​
Quick reference and best practices

  • Resource group naming: plan names carefully — they cannot be changed later.
  • Governance: apply RBAC and Azure Policy at the resource group level for scoped control.
  • Tags: use for cost allocation and automated reporting.
  • Move vs. migrate: use Move for resource group/subscription reorganization and Azure Resource Mover for cross-region migrations.
  • Quotas: monitor usage, request increases early, and maintain a plan for hard limits (additional subscriptions or architecture changes).
Summary
  • Resource groups are logical containers for organizing and scoping management of Azure resources.
  • Choose an organization strategy (by application or by resource type) that fits your operations.
  • Resource group metadata is stored in the group’s region; resources can be deployed across regions.
  • Resource groups cannot be renamed or nested, but resources can be moved between groups or subscriptions.
  • Azure enforces quotas at subscription and regional levels; many quotas are adjustable while some are hard limits.
  • Use the portal, CLI, PowerShell, or REST APIs to manage resource groups and request quota changes when needed.
Now that you understand subscriptions, resource groups, and quotas, you’ll be ready to explore the next elements of the Azure resource hierarchy.

Watch Video