A resource group is the first thing you create in Microsoft Azure: it’s the container that your web apps, databases and bots live in. This guide shows you how to create a resource group in the Azure portal, step by step with real screenshots, and how to delete it safely when you’re done.
What is an Azure resource group?
A resource group (opens in a new tab) is a container that holds related resources for an Azure solution. Microsoft recommends putting resources that share the same lifecycle in the same group, so you can deploy, update and delete them together. A few facts are worth knowing before you create one:
- It’s free. A resource group costs nothing by itself. You pay only for the resources you put in it.
- Its region stores metadata. The region you pick is where Azure stores the group’s information about its resources. The resources themselves can live in other regions.
- Deleting it deletes everything inside. When you delete a resource group, every resource in it is deleted too, and you can’t undo it.
- Its name follows simple rules. 1 to 90 characters: letters, digits, underscores, hyphens, periods and parentheses. It can’t end with a period, and it must be unique within your subscription (naming rules (opens in a new tab)).
What you’ll have at the end
An empty resource group named rg-jdbots-demo in the Central India region, ready to hold resources. The next guide, How to Create an App Service Plan in Microsoft Azure, creates a free App Service plan inside it.
Prerequisites
- An Azure account with an active subscription. If you don’t have one, create a free Azure account (opens in a new tab).
- Permission to create resource groups in that subscription. The Owner or Contributor role is enough.
- Cost: nothing. An empty resource group is free.
Step 1: Open Resource groups in the Azure portal
Sign in to the Azure portal (opens in a new tab). In the search box at the top of the page, type Resource groups, then select Resource groups under Services.

Step 2: Select + Create
The Resource groups page lists every resource group you can access. Select + Create at the start of the toolbar.

Step 3: Fill in the Basics tab
The Create a resource group form opens on the Basics tab. It asks for three things:
| Field | What it means | Value used in this guide |
|---|---|---|
| Subscription | The subscription that owns the group and pays for its resources. | Your subscription (shown as My Subscription in the screenshots) |
| Resource group name | A name that’s unique in your subscription. Start it with rg-, the prefix Microsoft’s naming guidance (opens in a new tab) uses for resource groups, so it’s easy to recognise. | rg-jdbots-demo |
| Region | Where the group’s metadata is stored. Pick the region closest to you, where most of its resources will run. | (Asia Pacific) Central India |

The Tags tab is optional. Tags are name and value labels, such as environment: demo, that help you filter resources and track costs. You can add them at any time, so skip that tab for now and select Review + create at the bottom of the form.

Step 4: Review and create the resource group
The Review + create tab shows a summary of your choices. Check the subscription, the name and the region.

Select Create at the bottom of the page.

When the resource group is ready, a notification appears in the top-right corner of the portal.

Step 5: Open your new resource group
Select Go to resource group in the notification. The Overview page shows the group’s Essentials: its subscription, subscription ID, location and deployments. The Resources list is empty because you haven’t added anything yet.

Your resource group is ready. Every resource you create in it from now on appears in this list.
Do It with the Azure CLI
Prefer the command line? A single Azure CLI command, az group create, creates the same resource group. Dewiride DevBlogs walks through it step by step, including signing in and checking the result: How to Create a Resource Group in Microsoft Azure using Azure CLI (opens in a new tab).
Clean Up When You’re Done
A resource group costs nothing on its own, but the resources inside it might. When you no longer need the group and everything in it:
- Open the resource group and select Delete resource group in the toolbar.
- In the Delete a resource group pane, type the resource group name to confirm.
- Select Delete.

Warning: deleting a resource group permanently deletes every resource in it, and you can’t undo it (Microsoft Learn (opens in a new tab)). Check the Resources list first. If you’re continuing to the App Service plan guide, keep rg-jdbots-demo: that guide creates a plan inside it.
Common Mistakes
| Mistake | What happens | Do this instead |
|---|---|---|
| Picking a region far from you | Management requests are routed through the group’s region, and compliance rules may require data to stay in one country. | Pick the region closest to you, where most of the group’s resources will run. |
| Putting unrelated resources in one group | Deleting the group to remove one app also deletes everything else in it. | Group resources that share a lifecycle, such as one app in one environment. |
| Ending the name with a period | The portal rejects the name. | Use letters, digits, hyphens, underscores, periods and parentheses, and end with a letter or digit. |
| Deleting without checking the Resources list | Every resource in the group is deleted permanently. | Open the group, check its resources, then delete it. |
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| The Subscription list is empty | Your account has no subscription in the directory you’re signed in to. | Switch directory from the account menu at the top right, or create a free Azure account. |
| The name is rejected as already in use | Resource group names must be unique within a subscription. | Choose another name, for example add -01 to the end. |
| Creating fails with an authorization error | Your account isn’t allowed to create resource groups in this subscription. | Ask the subscription owner for the Contributor role. |
| Deleting the group fails | A lock (opens in a new tab) on the group or its resources, or a resource connected to one in another group. | Remove the lock under Settings > Locks, remove the cross-group dependency, then delete again. |
FAQ
Does a resource group cost anything?
No. A resource group is free. You pay for the resources you create inside it, at each resource’s own price.
Can resources in one group be in different regions?
Yes. The group’s region only decides where its metadata is stored. Microsoft recommends keeping resources in the same region as their group where you can, to reduce the impact of a regional outage (What is Azure Resource Manager? (opens in a new tab)).
Can I rename a resource group?
No. Azure doesn’t offer a rename for resource groups. Create a new group with the name you want and move the resources (opens in a new tab) into it.
Can I move a resource to another resource group?
Yes, for most resource types, and even to another subscription in the same Microsoft Entra tenant. A move changes the resource’s ID, so update any scripts or dashboards that use it.
How should I name resource groups?
Use one pattern everywhere. Microsoft’s Cloud Adoption Framework suggests rg-<workload>-<environment>, for example rg-webapp-prod (Define your naming convention (opens in a new tab)).
Conclusion
You created an empty resource group in the Azure portal, checked its overview, and saw how to delete it safely. Next, put something in it: How to Create an App Service Plan in Microsoft Azure creates a free plan inside rg-jdbots-demo.
Additional Resources
- Manage resource groups with the Azure portal (opens in a new tab) (Microsoft Learn)
- What is Azure Resource Manager? (opens in a new tab) (Microsoft Learn)
- Naming rules and restrictions for Azure resources (opens in a new tab) (Microsoft Learn)
- Resource group and resource deletion (opens in a new tab) (Microsoft Learn)
- Move resources to a new resource group or subscription (opens in a new tab) (Microsoft Learn)
- How to Create a Resource Group in Microsoft Azure using Azure CLI (opens in a new tab) (Dewiride DevBlogs)
0 comments