DEV Community: Ipadeola Taiwo

Implementing RBAC in Azure for Secure Resource Group Access

Ipadeola Taiwo — Fri, 08 May 2026 03:14:09 +0000

In modern cloud environments, not every team member should have full access to resources. Proper access control is important for security, accountability, and preventing accidental changes.

In this project, I implemented Role-Based Access Control (RBAC) in Microsoft Azure to manage access to a Resource Group. I created multiple users with different permission levels and ensured that only authorized users could create or modify resources, while others had view-only access.

This hands-on project helped me understand:

Azure IAM and RBAC
Role assignments
Least privilege principle
Resource Group level access control

Project Scenario
A company project is hosted in Azure, and multiple team members require access to the environment. However, not everyone should have full control over the resources.

Objectives

Create a Resource Group
Create users
Assign RBAC roles
Implement least privilege access

Implementation Steps
First create a resource group, this act as logical container for our resoucrces and help us manage our resources easily

To create a resource group click on the search bar in azure console and type resource groups

Click on the resource groups result shown

Nest step is to click on create as shown in the image below

on clicking on the create button it will take you to the next page where you will fill in the following information, information such as selecting subscription, by default azure create subscription1 for us and that is what we would be using in this mini project
next give it a resource group name and also select a region, for this project we would go with the South Africa North (as i am based in Nigeria and is the closed region to my company, choose a region closest to your company)
then click on next

Next you are to select a tag name and value for the resource group to make it easier to search, but this is optional for this project we would leave it blank
Next is to click on review and create after confirmation click on create

we have succesfully created our resource groups

next let us create a user
for this project we would create 3 users

dev-user -> role: Contributor -> Access Level: Create/Edit Resources
tester-user -> role: Reader -> Access Level: View Only
auditor-user -> role: Reader -> Access Level: View Only

To create a user click on the search bar and type microsoft entra ID

Click on microsoft entra ID from the results
Go to manage and click on results

Click on new user, create new user

fill all the information and click on next

Since we want to gie it role from the resource group level we wonrt give it role at this point we would click on review and create and this would create our dev-user

we would create a new user again to do the same thing we did ealier to create our tester-user and our auditor-user

at this state we have our three new users created

Now let us give each users role to what they can do so we dont just give them unnecessary power they do not need to have, for protections and securities reasons

for us to give them role we would go our resource group we created ealier, by typing resource group in the search bar and click on jake-projects-rg we created ealier

Thank click on access control (IAM)

We would click on add -> assign role

let us start assigning role to our dev-user first, since we want to give contributor access control to our dev-user we would role we wouls click on priviledge administrator and search for contributor

Click on the next button
click on User, group, or service principal at the select access to
on the members click on select member in order to add we we want to give this permision to which is our dev-user

now our dev-user have been selected

Next click on review and assign
we have succesfully given role based accessed control to our dev-user

now let us do same thing to our remaining 2 users we want to give read access to

we would do the same thing as above
we would click on add, add role assignment
since the access we want to give to both users are read access only we would click on the job function and select the reader access this restrict the user from creating resources or accidentally deleting the resources but can only view

We would click on the add member and select the member we want to assign this role to in our case is the tester-user, and the auditor-user

we would click on review and assign to complete this
we have succesfully created and assign reader role to both users

When we click on role assigment inside the access control (IAM) in our resource group we can see we have succesfully

now this users can now sign in to their created accounts and do only what they are gicen power to do

The Dev-user can create resources, modify resources work on resources but delete resources and delete the resource group, mind you if the dev user mistakenly delete the resource group it can not be undone

auditor user and tester user can only read but can not create resources can not modify resources and can not delete resources

Security Improvement

During testing, I observed that a user with the Contributor role could delete the entire Resource Group. To improve protection against accidental or unauthorized deletion, Azure Resource Locks can be implemented to restrict deletion operations even for users with elevated resource permissions.

Deploying an Azure Virtual Machine: Networking, SSH, and Apache Setup

Ipadeola Taiwo — Sat, 18 Apr 2026 16:36:19 +0000

Before deploying a virtual machine, we need to create a Resource Group. In Azure, a Resource Group acts as a container that holds all related resources such as virtual machines, networking components, and storage.
Step 1: Create a Resource Group: To create a resource group, type on search box to acces resource group, and create a resource group

After creating the Resource Group, the next step is to configure networking. In Azure, this is done using a Virtual Network (VNet), which provides a private network for your virtual machine.

Before deploying a virtual machine, we need to set up the required networking. In Azure, this is done by creating a Virtual Network (VNet), which allows our VM to communicate securely with other resources.

This leads us to the next step:

Step 2: Create a Virtual Network (VNet): In the Azure portal, search for Virtual Networks using the search bar. Select it, then click on Create to begin setting up a new virtual network.

Select your existing subscription, then choose the Resource Group you created earlier.

Click Next to proceed to the Security tab and leave the default settings unchanged. Continue by clicking Next to the IP Addresses section.

Here, keep the default address space of 10.0.0.0/16, which provides up to 65,536 IP addresses for your virtual network. Delete the default subnet and click next, you can leave the tag blank depends on your choice, review and create your vnet

Step 3: After creating the Virtual Network, open it from the Azure portal. In the left-hand menu, navigate to Settings and select Subnets.

Click on + Subnet to create a new subnet within the virtual network.

Click on +subnet

Give the subnet a name, then set the address range to 10.0.0.0/24.
This subnet mask provides 256 IP addresses.
Finally, click Add to create the subnet.

After setting up the Resource Group, Virtual Network, and Subnet, we are now ready to deploy the Virtual Machine.
These networking components ensure that the VM can communicate securely within the Azure environment

Step 4: Create a Virtual Machine: To deploy our vm we click on the search box in the azure console and click on the virtual machine in the resultof the search

click on create

click on virtual machine

select the created resource group, give it a name, select the region of your choice, (best region closer to the clients)

For Availability Zone, you can select Zone 1 for testing purposes.

Next, choose the operating system for your virtual machine. You can select either Windows or Linux, depending on your use case. For this tutorial, we will proceed with Ubuntu Server 24.04 LTS.

Select the VM size based on your requirements (for training purposes, a smaller size is recommended).

For authentication type, select SSH Public Key for secure access. Then, provide a username for the VM.

Under Inbound port rules, allow public inbound access and select the required ports:

Port 22 (SSH) – for connecting to your VM
Port 80 (HTTP) – for web traffic once Apache is installed, click on next to Disk

Os size should be by choice for training purpose choose 30 gig to incure little or no cost

For the Disk type, you can choose between SSD and HDD.
For cost efficiency during training, select HDD, then click Next.

Networking

Select the previously created Virtual Network (VNet) and Subnet.
Allow public inbound access for required ports, then proceed to the next step.

Management

For simplicity, leave all settings at their default values.

Monitoring

Also leave the monitoring settings as default.

Advanced

Leave all advanced options unchanged.

How to Create a Resource Group in Azure (Step-by-Step Guide)

Ipadeola Taiwo — Tue, 17 Mar 2026 13:26:41 +0000

What is resource group and why should you care

In Microsoft Azure, a Resource Group is a logical container used to organize and manage related resources. It is one of the first things you need to create before deploying any service in Azure.

Whether you're deploying a virtual machine, database, or web app, Resource Groups help you manage everything efficiently, control access, and reduce costs.

In this guide, you’ll learn how to create a Resource Group step-by-step using the Azure Portal.

Step 1: Log in to the Azure Portal by visiting portal.azure.com and signing in to your account.
Step 2: In the Azure Portal, use the search bar at the top and type “Resource groups,” then select it from the results.

Step 3: Click the “Create” button to start creating a new Resource Group.

Step 4: Configure your Resource Group settings. By default, your Azure subscription (e.g., “Subscription 1”) will be selected. If you have multiple subscriptions, choose the one you want to use. Next, enter a name for your Resource Group—usually the name of your project works best. Then, select a region close to where your project or users are located. Once done, click the Next button to continue.

Step 5: Add tags (optional) Tags help you organize resources so you can find them easily later. You can leave this section blank if you want. It won’t affect your Resource Group. In this tutorial, we’ll skip adding tags.

Step 6: Review and create your Resource Group After clicking Next in the previous step, you will be taken to the Review + Create page. Carefully check that all the information is correct, including your subscription, Resource Group name, and region. Once everything looks good, click Create. Congratulations—you have successfully created your Resource Group! 🎉

Step 7: Confirm your Resource Group creation After clicking Create, look at the bell icon at the top of the Azure Portal. You should see a notification saying “Resource Group created”. You can then choose to either Go to resource group to view it immediately or Pin to dashboard for quick access later.

Congratulations! You have successfully created your first Resource Group in Azure. By organizing your resources in a Resource Group, you can manage, monitor, and deploy your projects efficiently.

Next, you can start adding resources like Virtual Machines, Databases, or Storage accounts to your Resource Group and explore how Azure manages them.

Best practices

Use meaningful names for your Resource Groups to easily identify projects.
Choose regions close to your users to improve performance.
Use tags for better organization, especially if you manage many projects.

Now that you know how to create a Resource Group, you’re ready to start building and managing your cloud projects in Azure. Happy learning! 🚀

Did you find this guide helpful? 💡
I’d love to hear about your experience creating your first Resource Group in Azure!
Share your thoughts or questions in the comments below, and stay tuned for more tutorials on Azure, Cloud Computing, and DevOps.