DEV Community: Divine Uzor

Every Device Needs an Address: Understanding IP Addressing, IPv4, IPv6, NAT, and Subnetting

Divine Uzor — Sun, 12 Jul 2026 21:51:56 +0000

"How does data know where to go?"

In the previous article, we explored the OSI Model and saw how data travels through seven layers before reaching another device.

One layer stood out in particular.

Layer 3: The Network Layer.

This is the layer responsible for moving data between networks. But before data can travel anywhere, the network has to answer one very important question.

Where exactly should this data go?

Imagine ordering food online without entering your home address.

The restaurant prepares your meal.

The delivery rider picks it up.

Everything is ready.

But there's one problem.

Nobody knows where to deliver it.

That is exactly what would happen on the Internet if devices didn't have addresses.

Every phone, laptop, server, printer, router, virtual machine, and cloud resource needs an address so data knows where to go.

That address is called an IP address.

Whether you're troubleshooting a network, configuring Azure resources, deploying virtual machines, or simply browsing the web, IP addressing is working quietly in the background.

In this article, you'll learn:

What an IP address actually is
The difference between IPv4 and IPv6
Why IPv4 almost ran out of addresses
Public vs private IP addresses
How NAT lets multiple devices share one public IP
What subnetting and CIDR notation mean
Why these concepts matter in cloud computing

Let's begin.

What Exactly Is an IP Address?

An IP (Internet Protocol) address is a unique logical address assigned to a device connected to a network.

Its job is surprisingly simple.

It answers two questions.

Who are you?
Where are you?

Without an IP address, devices wouldn't know where to send information.

Think about sending a letter through the post.

The postal service doesn't know you personally.

It only knows the address written on the envelope.

The same thing happens on the Internet.

When you open YouTube or Google, your computer doesn't magically know where those servers are.

It sends packets that contain destination IP addresses, allowing routers across the Internet to deliver those packets to the correct server.

Every packet depends on an address.

No address.

No communication.

IP Address vs MAC Address

At this point, it's worth clearing up one of the biggest beginner questions.

What's the difference between an IP address and a MAC address?

Although both identify devices, they do very different jobs.

Think about yourself.

You have:

a home address
fingerprints

Your fingerprints identify who you are.

Your home address identifies where you live.

Networking works the same way.

A MAC address is like your fingerprint.

It is burned into the network interface card (NIC) by the manufacturer and identifies the physical device on the local network.

An IP address is like your home address.

It identifies where that device currently exists on a network.

If you move to another house, your fingerprint stays the same.

Only your address changes.

Likewise, if you connect your laptop to another network, your MAC address stays the same while your IP address usually changes.

This distinction is important because:

Layer 2 (Data Link) uses MAC addresses.
Layer 3 (Network) uses IP addresses.

Remember our OSI article?

This is where those layers begin working together.

IPv4: The Original Internet Addressing System

The version of IP addressing that built the Internet is called IPv4.

It has existed since the early 1980s and is still the most widely used version today.

An IPv4 address is made up of 32 bits.

Instead of writing 32 ones and zeros, we split them into four groups separated by periods.

For example:

192.168.10.25

Each group is called an octet because it contains 8 bits.

Each octet can contain values from:

0 – 255

That's because eight binary bits can represent 256 different values.

The same address in binary looks like this:

11000000.10101000.00001010.00011001

Fortunately, humans don't have to read binary very often.

That's why dotted decimal notation exists.

Every IPv4 Address Has Two Parts

An IPv4 address isn't just one long number.

It actually contains two separate sections.

Network portion
Host portion

The network portion identifies the network.

The host portion identifies the individual device inside that network.

Imagine a hotel.

The hotel's street address identifies the building.

The room number identifies one specific guest.

IP addressing works the same way.

The network tells routers which network to deliver traffic to.

The host tells the network which device should receive it.

We'll see exactly how the network decides where this dividing line is when we discuss subnet masks later in this article.

Why Did IPv4 Run Out?

When IPv4 was created, engineers believed its address space would last for decades.

After all...

32 bits gives us:

2³² = 4,294,967,296 addresses

More than 4.3 billion addresses.

Back then, that sounded impossible to exhaust.

But the Internet changed.

Today we don't just have computers.

We have:

smartphones
tablets
cloud servers
smart TVs
gaming consoles
IoT devices
security cameras
smart watches
sensors
virtual machines

Billions of devices now compete for IPv4 addresses.

Eventually, the available address pool began running out.

This problem became known as IPv4 address exhaustion.

Instead of replacing IPv4 immediately, engineers developed clever techniques to make those addresses last much longer.

The biggest one was Network Address Translation (NAT).

Before we explain NAT, we first need to understand the difference between public and private IP addresses.

Coming up in Part 4: We'll explore public vs. private IP addresses, how NAT allows your entire home to share a single public IP address, why this was one of the most important innovations in networking, and how IPv6 was designed to solve the address shortage permanently.

Ever Wondered How Data Travels Across the Internet? Meet the OSI Model

Divine Uzor — Fri, 03 Jul 2026 16:49:32 +0000

"The cloud isn't magic. It's networking happening at an incredible scale."

In the first article of this series, Why Every Cloud Engineer Needs to Understand Computer Networks, we explored why networking is one of the most important skills for anyone pursuing a career in cloud engineering.

Now it's time to answer another important question.

What actually happens when you press Enter after typing a website into your browser?

Let's use a simple example.

You open your browser and type:

https://www.google.com

You press Enter.

Within a fraction of a second, Google's homepage appears.

Simple, right?

Not quite.

Behind the scenes, your request travels through multiple processes before it ever reaches Google's servers. That request is prepared, secured, routed across networks, delivered to the correct server, and then the response makes the exact same journey back to your browser.

Understanding that journey is where the OSI Model comes in.

For cloud engineers, this isn't just networking theory. It's the foundation for understanding Azure Virtual Networks, AWS VPCs, DNS, Load Balancers, VPNs, Firewalls, Network Security Groups, and almost every networking service you'll work with in the cloud.

Why Do We Need the OSI Model?

Imagine you want to send a parcel to a friend in another country.

You carefully package it, write the address, and hand it to the courier.

From that point on, different people take over.

Someone sorts the package.

Someone loads it onto a truck.

Someone flies it across the ocean.

Someone else delivers it to your friend's doorstep.

Each person has one responsibility. Nobody tries to do everyone else's job.

Computer networks work exactly the same way.

Instead of handling communication as one giant process, networking breaks it into smaller tasks. Each task is assigned to a different layer, and together they move data from one device to another.

That's exactly what the OSI Model is.

It divides network communication into seven layers, each with a specific responsibility.

Meet the Seven Layers

The easiest way to understand the OSI Model isn't by memorizing all seven layers.

Instead, think of each layer as answering one important question.

Layer 7 – Application

Where does communication begin?

This is the layer closest to you.

Every time you browse a website, send an email, or connect to a server using SSH, you're interacting with the Application Layer.

This layer provides the protocols applications use to communicate across a network.

Some examples include HTTP, HTTPS, DNS, SMTP, and SSH.

When you typed https://www.google.com, your browser created an HTTPS request at this layer before passing it down to the next one.

Layer 6 – Presentation

Can the receiving computer understand the data?

Different systems don't always represent data in exactly the same way.

The Presentation Layer acts as the translator.

Its responsibilities include:

Translating data into a common format
Encrypting and decrypting information
Compressing data before transmission

Whenever you access an HTTPS website, this layer helps encrypt your data so your passwords and personal information remain protected while travelling across the internet.

Layer 5 – Session

How do two devices keep a conversation going?

Imagine making a phone call.

Someone dials.

Someone answers.

The conversation continues.

Eventually someone hangs up.

That's exactly what the Session Layer does.

It establishes communication, keeps it active while data is exchanged, and closes the connection cleanly when everything is complete.

Layer 4 – Transport

How does data reach the correct application?

This is one of the most important layers for cloud engineers.

The Transport Layer breaks large amounts of data into smaller pieces, ensures everything arrives in the correct order, and retransmits anything that gets lost along the way.

It's also where port numbers come into play.

Think of an IP address as the address of an apartment building.

A port number is the apartment number inside the building.

The IP address gets your data to the correct computer.

The port number delivers it to the correct application.

For example:

HTTPS uses Port 443
HTTP uses Port 80
SSH uses Port 22
DNS commonly uses Port 53

If you've ever configured an Azure Network Security Group or opened a firewall port, you've already worked with Layer 4.

Layer 3 – Network

How does data find another network?

This layer is responsible for logical addressing and routing.

Every device connected to a network has an IP address.

Routers examine these addresses and determine the best path to the destination.

Whether data travels across your home network or halfway around the world, Layer 3 is responsible for finding the route.

As cloud engineers, we encounter Layer 3 everywhere.

Azure Virtual Networks.

AWS VPCs.

Route Tables.

VPN Gateways.

ExpressRoute.

Everything begins with Layer 3 networking.

Layer 2 – Data Link

How do devices communicate on the same local network?

While Layer 3 uses IP addresses, Layer 2 relies on MAC addresses.

Switches use these hardware addresses to deliver data efficiently between devices connected to the same local network.

A common protocol here is ARP (Address Resolution Protocol).

Suppose your computer knows another device's IP address but doesn't know its MAC address.

It simply asks:

"Who has this IP address?"

The correct device replies with its MAC address, allowing communication to continue.

Layer 1 – Physical

How does data physically travel?

At the bottom of the OSI Model, data is nothing more than a stream of binary bits.

The Physical Layer converts those bits into signals that can travel across a medium.

Those signals might be:

Electrical signals through Ethernet cables
Pulses of light through fibre optic cables
Radio waves over Wi-Fi

Without this layer, nothing would ever leave your device.

The Journey Down... and Back Up

As your request travels down the seven layers, each layer adds its own information before passing it to the next.

This process is called encapsulation.

Once Google's server receives the request, the reverse happens.

Each layer removes the information that was added until the original request reaches the web application.

This reverse process is called decapsulation.

Think of it like shipping a gift.

You place the gift inside a box.

The courier adds labels.

Shipping companies attach tracking information.

When the recipient receives the package, they remove each layer until they finally reach the gift inside.

Networking works exactly the same way.

Why Cloud Engineers Should Care

One of the biggest misconceptions about the OSI Model is that it's only useful for passing certification exams.

Nothing could be further from the truth.

The OSI Model gives you a structured way to troubleshoot problems.

Imagine you've deployed a web application to Azure.

Users suddenly report they can't access it.

Instead of guessing, you can troubleshoot layer by layer.

Is the network connection working?
Does the server have the correct IP address?
Is Port 443 open?
Is HTTPS configured correctly?
Is the web application actually running?

Good engineers don't troubleshoot randomly.

They troubleshoot systematically.

That's exactly what the OSI Model helps you do.

Key Takeaway

If there's one thing I want you to remember from this article, it's this:

Every cloud service ultimately depends on networking.

When you configure a Virtual Network in Azure, you're working with Layer 3.

When you create firewall rules or Network Security Groups, you're working with Layers 3 and 4.

When users securely access your web application over HTTPS, Layers 4, 6, and 7 are all involved.

Cloud platforms don't replace networking.

They build on top of it.

The stronger your networking foundation becomes, the easier cloud engineering will be.

Final Thoughts

The OSI Model isn't something to memorize and forget after passing an exam.

It's a mental framework that helps you understand how computers communicate, why networks behave the way they do, and how to troubleshoot problems logically.

As you continue your cloud journey, you'll discover that almost every networking concept in Azure, AWS, and Google Cloud traces back to these seven layers.

Understanding them now will make everything you learn later feel much more connected.

In the subsequent articles, we'll explore IP Addressing, Subnetting, and CIDR Notation. These are the concepts that determine how cloud networks are designed, secured, and scaled.

If you found this article helpful, consider following the series. We're building the networking foundation every cloud engineer needs, one concept at a time.

Why Every Cloud Engineer Needs to Understand Computer Networks

Divine Uzor — Wed, 01 Jul 2026 16:57:21 +0000

When most people think about cloud computing, they think about Microsoft Azure, AWS, Kubernetes, containers, or Microsoft 365.

What many people don't realize is that none of these technologies work without computer networks.

Every Azure Virtual Machine communicates over a network.

Every Microsoft 365 sign in depends on a network connection.

Every website you visit, every email you send, every file you upload to the cloud, and every Microsoft Teams meeting all rely on networks to move data from one device to another.

This is why networking is one of the most important skills for anyone pursuing a career in cloud computing.

Cloud platforms are built on networking. If you understand how networks work, learning cloud technologies becomes much easier.

This article is the first in my Networking Fundamentals series: Building the Foundation for Cloud Engineering. In this series, I'll be breaking down the core networking concepts that every aspiring Cloud Engineer should understand. My goal is to explain each topic in a practical, beginner friendly way before we move into Azure networking and cloud infrastructure.
Let's start with the basics.

What Is a Computer Network?

A computer network is a group of devices connected together so they can communicate and share resources.

These devices include:

Computers
Smartphones
Servers
Printers
Routers
Switches
Smart TVs
Cloud resources

Instead of operating independently, these devices exchange information through the network.

Think about your home Wi Fi.

Your laptop, phone, smart TV, and gaming console all connect to the same router. They share internet access and can communicate with one another.

Now imagine that same idea expanded across office buildings, cities, countries, and eventually the entire internet.

That is networking.

Why Do Networks Matter?

Without networks, every computer would operate on its own.

You would not be able to:

Browse the internet
Send emails
Join Microsoft Teams meetings
Access cloud applications
Share files
Print to a network printer
Stream videos
Play online games

Networks make communication possible.

For businesses, they also provide important benefits such as:

Resource sharing
Centralized data storage
Better collaboration
Support for remote work
Secure communication
Scalable IT infrastructure

Almost every modern organization depends on reliable networking to keep its operations running.

The Four Main Types of Networks

Networks are classified according to their size and geographical coverage.

Personal Area Network (PAN)

A Personal Area Network connects devices around a single person.

Examples include:

Bluetooth earbuds
Smartwatches
Wireless keyboards
Fitness trackers

Its range is usually only a few meters.

Local Area Network (LAN)

A Local Area Network connects devices within a home, school, or office.

This is the network most people use every day.

If you are just beginning your networking journey, this is the most important type of network to understand.

Metropolitan Area Network (MAN)

A Metropolitan Area Network connects multiple Local Area Networks across a city.

Examples include universities, hospitals, and organizations with several offices in the same metropolitan area.

Wide Area Network (WAN)

A Wide Area Network connects networks across countries and continents.

The biggest example is the Internet.

The Devices That Make Networks Work

Every network depends on specialized devices that perform different functions.

Router

A router connects different networks together.

In most homes, it connects your local network to your Internet Service Provider.

Switch

A switch connects devices within the same network.

It forwards data only to the intended destination, making communication faster and more efficient.

Access Point

An access point allows wireless devices such as laptops, tablets, and smartphones to connect using Wi Fi.

Modem

A modem connects your home or office to your Internet Service Provider.

Many home networking devices combine the modem, router, switch, and wireless access point into one device.

Firewall

A firewall monitors network traffic and blocks unauthorized access.

It is one of the most important components for protecting a network.

Server

A server provides services to other devices.

Examples include web servers, file servers, database servers, and email servers.

Every time you visit a website, your device communicates with one or more servers.

Network Topologies

A network topology describes how devices are connected.

Bus Topology

All devices share one communication cable.

Star Topology

Every device connects to one central switch or router.

This is the most common topology used today because it is reliable, scalable, and easy to troubleshoot.

Ring Topology

Devices connect in a circular path.

Mesh Topology

Devices have multiple paths to one another, providing high availability and redundancy.

Hybrid Topology

A combination of two or more topologies.

Wired and Wireless Networking

Both wired and wireless networking have advantages.

Wired Networking

Best for:

Servers
Desktop computers
Data centers

Advantages:

Faster speeds
Lower latency
Greater reliability
Better security

Wireless Networking

Best for:

Smartphones
Tablets
Laptops

Advantages:

Mobility
Flexibility
Easy deployment

Most organizations use both.

Networking Terms Every Beginner Should Know

As you continue learning networking, these are some of the terms you will encounter regularly.

IP Address
MAC Address
DNS
DHCP
Packet
Bandwidth
Latency
Firewall

Don't worry if they seem unfamiliar right now.

Each of these concepts will be covered throughout this series.

How Does Data Travel Across a Network?

When you send a file across a network, it does not travel as one large piece of information.

Instead, it is divided into smaller pieces called packets.

Each packet contains addressing information and part of the original data.

These packets travel through different networking devices until they reach their destination, where they are reassembled into the original file.

This entire process happens in milliseconds every time you browse a website, send an email, or stream a video.

Why This Matters for Cloud Computing

Cloud computing does not replace networking.

It builds on it.

Whether you are deploying Azure Virtual Machines, configuring Microsoft Entra ID, designing virtual networks, or troubleshooting connectivity issues, networking fundamentals remain essential.

The stronger your understanding of networking, the easier it becomes to understand cloud infrastructure.

That is why I believe every aspiring Cloud Engineer should build a strong networking foundation before moving deeper into cloud technologies.

Final Thoughts

Networking quietly supports almost everything we do in modern IT.

Whether your goal is to become a Cloud Engineer, Systems Administrator, Network Engineer, Cybersecurity Professional, or DevOps Engineer, understanding how devices communicate will make every technology you learn afterward much easier to understand.

Strong foundations do more than help you pass certification exams.

They help you solve real world problems with confidence.

Every expert started by learning the fundamentals.

This series is my way of documenting that journey while hopefully making these concepts easier for anyone beginning theirs.

What's Next?

In the next article, we'll explore The OSI Model and learn how data moves across a network, one layer at a time.

Understanding the OSI Model makes concepts such as IP addressing, DNS, routing, and troubleshooting much easier to understand.

If you're following this series, I'd love to hear from you.

What networking concept did you find most challenging when you first started learning?

Moving to the Cloud: What Actually Happens to Your Data?

Divine Uzor — Fri, 26 Jun 2026 12:39:57 +0000

So you're thinking about moving to the cloud. Or maybe you've already started and you're realizing there's a lot more to it than just uploading files somewhere.

When I first started learning Azure, I kept asking the same basic questions. Where does my data actually live? How do I keep it safe? Who gets to look at it? Let me walk you through what I've learned.

You need a storage account first

Think of a storage account like a bank account. You can't just walk into a bank and hand them money without one. Same thing here. It's the container that holds everything together, and it determines what storage services and redundancy options you use. Everything flows through it.

One thing that tripped me up early on is that your storage account name has to be totally unique across every Azure user in the world. So you can't just use "mycompany" and call it done. You'll probably end up with something like "mycompanystorage123" after a few failed attempts.

Your data is never stored in just one place

Azure never keeps just one copy of your data because if that one server dies, you're out of luck. So they replicate it across different locations. There are four levels of protection, going from copies within a single datacenter (LRS, 11 nines of durability) all the way up to copies spread across both availability zones and entirely separate regions (GZRS, 16 nines). The more spread out the copies, the higher the durability rating.

Different data needs different storage

A video file is not the same as a virtual machine disk, and a chat message is not the same as a spreadsheet. Azure has five specialized services for this:

Use the right tool for the right job. You wouldn't store a video file in a queue system.

A clever way to save money

Not everything needs to be accessible all the time, and you shouldn't pay the same price for everything. Azure has four access tiers: Hot for daily use, Cool for data you keep for at least 30 days, Cold for at least 90 days, and Archive for things you rarely touch but need to hold for at least 180 days. The less you access it, the cheaper it is to store. It's like a storage unit. If those boxes are just collecting dust, why pay premium prices?

Getting your data into the cloud

Azure Migrate acts as a central hub that helps you assess your current setup, figure out what needs to move, and carry out the migration in an organized way. It brings together Microsoft and third party tools in one place.

But my favorite thing is the Azure Data Box. They literally ship you a physical device, you load up to 80 terabytes of data onto it, mail it back to Microsoft, and they upload it into the cloud for you. It sounds ridiculous, but think about remote locations with barely any internet, or situations where you need to move data out of Azure for legal reasons. Sometimes a physical box is genuinely the fastest option.

Who gets to see your data?

Azure handles identity through Microsoft Entra ID, its cloud based access management service. It handles employee logins, Single Sign On across multiple apps, application management, and Business to Business access. Think of it as the gatekeeper for everything in your environment.

Two things you need to understand here. Authentication is proving who you are, like showing your ID at the door. Authorization is what you're allowed to do once you're inside. One happens before you get access. The other defines what you do with it.

And please enable Multifactor Authentication. A password alone is no longer enough. The more I learn about cloud security, the more I realize it should never be the only thing protecting an account. MFA requires at least two of three things: something you know, something you have, and something you are. Even if someone steals your password, they still cannot get in without that second layer of verification.

Wrapping this up

Moving to the cloud feels intimidating at first. But once you understand the basics, the storage account, the redundancy, the storage types, the access tiers, how to get your data there, and how to control who sees it, it starts to make a lot more sense. The cloud is just someone else's computer. A really well managed one.

Are you just starting to explore cloud storage, or are you in the middle of a migration? Drop it in the comments.

Inside Azure: Compute Services, Networking, and Cloud Connectivity

Divine Uzor — Tue, 23 Jun 2026 15:07:05 +0000

In the previous article, we explored how Microsoft Azure organizes its global infrastructure through regions, availability zones, and resource organization. Those concepts provide the foundation for building reliable cloud solutions, but infrastructure alone does not run applications or connect services.

This is where Azure compute and networking services come in.

From Virtual Machines and containers to Virtual Networks and ExpressRoute, these services power modern cloud workloads and enable secure communication between resources. Understanding how they work together is essential for designing scalable, reliable, and efficient cloud solutions.

In this article, we'll take a closer look inside Azure to explore the compute and networking services that keep applications running and connected.

Azure Compute Services

One of the most important decisions in cloud architecture is choosing the right compute model.

Different workloads require different levels of control, automation, and scalability. A legacy application may need full control over the operating system, while a modern event-driven solution may benefit from serverless execution.

Azure provides multiple compute services to meet these varying requirements.

Azure Virtual Machines

Azure Virtual Machines (VMs) provide the highest level of control over your computing environment.

With a virtual machine, you manage the operating system, installed applications, security configurations, updates, and overall system maintenance. This makes VMs ideal for custom software environments, legacy applications, and lift-and-shift migrations where organizations want to move existing workloads to the cloud with minimal changes.

The flexibility of virtual machines is powerful, but it also comes with increased administrative responsibility.

Scaling with Virtual Machine Scale Sets

A single virtual machine may be sufficient for testing environments, but production workloads often require the ability to handle fluctuating demand.

Azure Virtual Machine Scale Sets allow organizations to automatically increase or decrease the number of virtual machine instances based on workload requirements.

This approach provides:

Improved performance during traffic spikes
Better resource utilization
Increased availability
Automated scalability

Instead of manually deploying additional servers, Azure can dynamically adjust resources based on predefined scaling rules.

Improving Availability with Availability Sets

Building reliable applications requires more than simply deploying multiple virtual machines.

Azure Availability Sets distribute virtual machines across separate fault domains and update domains. This helps minimize the impact of hardware failures and planned maintenance events.

By spreading workloads across different failure boundaries, organizations can improve uptime and maintain service availability even when part of the underlying infrastructure experiences disruption.

Azure Virtual Desktop

The rise of hybrid and remote work has increased the need for secure access to business resources from anywhere.

Azure Virtual Desktop allows organizations to deliver desktop environments and applications through the cloud while maintaining centralized administration and security controls.

Benefits include:

Secure remote access
Centralized management
Consistent user experiences
Reduced dependency on physical devices

This enables employees to remain productive while administrators retain control over the environment.

Containers and Azure Container Instances

Modern applications often require portability, consistency, and rapid deployment.

Containers package applications together with their dependencies, ensuring they behave consistently across development, testing, and production environments.

This approach offers several advantages:

Faster deployments
Efficient resource utilization
Application portability
Consistent execution environments

Containers have become a fundamental building block of cloud-native architectures and microservices-based applications.

Azure Functions and Serverless Computing

Not every workload needs continuously running infrastructure.

Azure Functions uses a serverless execution model where code runs only when triggered by an event.

Common use cases include:

Processing uploaded files
Automating workflows
Running scheduled tasks
Responding to application events

Because resources are consumed only during execution, organizations can reduce operational costs while maintaining scalability.

Azure App Service

Managing infrastructure is not always necessary.

Azure App Service simplifies web application deployment by abstracting the underlying infrastructure. Azure handles server maintenance, operating system updates, availability, and scaling.

This allows developers and administrators to focus on application functionality and performance rather than infrastructure management.

For many web-based applications, App Service provides a simpler alternative to managing virtual machines.

Azure Networking: Connecting Cloud Resources

While compute services run applications, networking services enable communication between them.

A well-designed network architecture provides secure connectivity, resource isolation, controlled access, and reliable communication between cloud and on-premises environments.

Networking serves as the foundation that connects every component within an Azure environment.

Azure Virtual Networks (VNets)

Azure Virtual Networks provide a private networking environment within Azure.

A VNet enables resources such as virtual machines, databases, and applications to communicate securely with one another while remaining isolated from external networks when required.

Within a VNet, administrators can:

Define IP address ranges
Create subnets
Apply security controls
Connect cloud and on-premises resources

Virtual Networks form the backbone of Azure networking architecture.

Azure VPN Gateway

Many organizations operate hybrid environments that combine on-premises infrastructure with cloud resources.

Azure VPN Gateway enables secure communication between these environments by creating encrypted tunnels over the internet.

This allows organizations to extend their existing networks into Azure while maintaining secure connectivity between locations.

VPN Gateway is often one of the first networking services adopted during a cloud migration journey.

Azure ExpressRoute

Some workloads require more reliability and predictable performance than internet-based connectivity can provide.

Azure ExpressRoute establishes a dedicated private connection between on-premises infrastructure and Azure services.

Compared to standard internet connectivity, ExpressRoute offers:

Lower latency
Higher reliability
Increased security
Consistent network performance

For mission-critical enterprise workloads, dedicated connectivity is often the preferred solution.

Azure DNS

Every application depends on name resolution.

Azure DNS translates human-friendly domain names into IP addresses, enabling users to access applications without needing to remember numerical addresses.

Benefits of Azure DNS include:

High availability
Global scalability
Simplified management
Integration with Azure services

Although often overlooked, DNS is a critical component of modern cloud networking.

Final Thoughts

Azure compute and networking services work together to deliver the performance, scalability, and connectivity that modern applications require.

Virtual Machines provide maximum control, containers support cloud-native applications, Azure Functions enable serverless execution, and App Service simplifies deployment. At the same time, networking services such as Virtual Networks, VPN Gateway, ExpressRoute, and Azure DNS ensure that resources communicate securely and efficiently.

Understanding these services is a crucial step toward designing cloud solutions that are reliable, scalable, and secure.

In the next article, we'll explore how Azure stores and protects data, supports workload migration to the cloud, and manages identities through Microsoft Entra ID. Together, these services form another critical layer of Azure architecture, helping organizations secure access, manage data effectively, and modernize their infrastructure in the cloud.

Understanding Azure Regions, Availability Zones, and Resource Organization

Divine Uzor — Fri, 19 Jun 2026 11:32:46 +0000

When people first start learning cloud computing, they often focus on virtual machines, storage accounts, and networking. While those services are important, understanding the structure behind the cloud is equally essential.

In Microsoft Azure, services are deployed within a carefully designed global infrastructure that provides reliability, scalability, security, and compliance. In this article, we'll explore Azure Regions, Availability Zones, Region Pairs, Sovereign Regions, and the organizational components that help manage cloud resources efficiently.

Azure Regions: The Foundation of Azure's Global Infrastructure

An Azure Region is a geographical area that contains one or more datacenters connected through a high-speed network.

Regions are designed to provide:

Low latency for users
High availability
Scalability
Data residency and compliance requirements

For example, if your users are located in West Africa, choosing a nearby Azure region can improve application performance and reduce network delays.

Think of a region as the physical location where your cloud resources live.

Availability Zones: Protecting Against Datacenter Failures

Even within a region, unexpected failures can occur.

To increase reliability, Azure provides Availability Zones.

Availability Zones are physically separate datacenters within the same Azure region. Each zone has independent power, cooling, and networking infrastructure.

This means that if one datacenter experiences an outage, workloads running in another zone can continue operating.

For mission-critical applications, deploying resources across multiple availability zones helps improve resilience and business continuity.

Azure Region Pairs: Built-In Disaster Recovery

What happens if an entire region becomes unavailable?

Azure addresses this challenge through Region Pairs.

A region pair consists of two Azure regions located within the same geography. These paired regions are designed to support disaster recovery scenarios.

Benefits include:

Improved business continuity
Data replication options
Reduced downtime during major outages
Prioritized recovery during large-scale incidents

Region pairs provide an additional layer of protection beyond availability zones.

Sovereign Regions: Meeting Specialized Compliance Requirements

Some organizations operate under strict regulatory requirements that prevent data from being stored in standard public cloud environments.

For these scenarios, Azure offers Sovereign Regions.

These are isolated cloud environments designed specifically for government agencies and organizations with strict security, privacy, and compliance requirements.

Sovereign regions provide greater control over data handling while still delivering cloud capabilities.

Azure China: A Specialized Sovereign Cloud

One example of a sovereign cloud environment is Azure China.

Azure China is designed to meet China's regulatory and data residency requirements. It operates separately from the global Azure cloud and helps organizations comply with local regulations while leveraging Azure services.

This demonstrates how cloud providers adapt their infrastructure to meet country-specific legal and compliance needs.

Azure Resources: The Building Blocks of Cloud Solutions

Every service you create in Azure is considered a resource.

Examples include:

Virtual Machines
Storage Accounts
Virtual Networks
Databases
Web Applications

Resources are the individual components used to build cloud solutions.

Managing these resources effectively becomes increasingly important as cloud environments grow.

Figure 1: Azure governance hierarchy showing how Management Groups, Subscriptions, Resource Groups, and Resources are organized.

Resource Groups: Organizing Azure Resources

Azure Resource Groups help organize related resources into a logical container.

For example, an application might include:

A virtual machine
A database
A storage account
A virtual network

These resources can be placed in the same resource group, making them easier to manage, monitor, and deploy.

Resource groups simplify administration and improve operational efficiency.

Azure Subscriptions: Boundaries for Billing and Access Control

An Azure Subscription acts as a boundary for:

Billing
Resource management
Access control

Organizations often create multiple subscriptions for different departments, projects, or environments.

For example:

Production Subscription
Development Subscription
Testing Subscription

This separation helps maintain governance while providing clear cost visibility.

Management Groups: Organizing at Scale

As organizations grow, managing numerous subscriptions can become challenging.

Azure Management Groups provide a higher level of organization.

Management groups allow administrators to:

Group subscriptions together
Apply governance policies consistently
Simplify access management
Standardize compliance requirements

The hierarchy typically looks like this:

Management Group
→ Subscription
→ Resource Group
→ Resources

This structure enables efficient governance across large Azure environments.

Final Thoughts

Azure's global infrastructure is more than just datacenters. Regions, Availability Zones, Region Pairs, and Sovereign Clouds work together to deliver reliability, compliance, and resilience.

At the same time, Resource Groups, Subscriptions, and Management Groups help organizations maintain order and governance as their cloud environments scale.

Understanding these foundational concepts is an important step for anyone beginning their cloud computing journey and preparing for Azure certifications.

What Azure concept did you find most interesting when you started learning cloud computing? Let me know in the comments.

Cloud Computing 101: What Every Beginner Should Know

Divine Uzor — Wed, 17 Jun 2026 15:22:30 +0000

When I first started learning cloud computing, I kept hearing terms like Azure, AWS, IaaS, PaaS, and SaaS. It felt like everyone already understood the language except me.

The good news is that cloud computing is much simpler than it initially sounds.

In this article, I'll break down the fundamentals of cloud computing, the different deployment models, the benefits of the cloud, and the major service types that power modern IT environments.

What Is Cloud Computing?

Cloud computing is the delivery of computing services over the internet. Instead of buying and maintaining physical servers, organizations can access resources such as:

Servers
Storage
Databases
Networking
Software
Analytics

on demand from a cloud provider.

This allows businesses to innovate faster, scale more easily, and pay only for the resources they use.

Cloud Deployment Models

Private Cloud

A private cloud is built and operated for a single organization.

Characteristics:

Hosted within the organization's environment
Managed by the organization
Not accessible to the general public
Greater control over resources and security

Private clouds are often used when organizations have strict security, compliance, or regulatory requirements.

Public Cloud

A public cloud is owned and operated by a cloud service provider.

Characteristics:

Shared infrastructure
Accessible over the internet
Pay-as-you-go pricing
Highly scalable

Examples include Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).

Hybrid Cloud

A hybrid cloud combines both public and private cloud environments.

This approach allows organizations to run workloads in the environment that best suits their needs while maintaining flexibility and control.

Other Cloud Models

Community Cloud

A cloud environment shared by multiple organizations with similar requirements.

Multi-Cloud

The use of services from more than one cloud provider.

Many organizations adopt a multi-cloud strategy to avoid vendor lock-in and take advantage of different providers' strengths.

Benefits of Cloud Computing

Cloud computing offers several advantages over traditional on-premises infrastructure.

High Availability

Cloud services are designed to remain accessible most of the time from virtually any location.

Elasticity

Resources can automatically expand or contract based on demand. This helps organizations handle unexpected traffic spikes without manual intervention.

Scalability

Businesses can quickly add or remove resources as requirements change.

Reliability

Cloud platforms are built with redundancy and fault tolerance, allowing systems to recover from failures with minimal disruption.

Predictability

Organizations can estimate resource usage and costs more accurately using cloud management tools and pricing models.

Security

Cloud providers invest heavily in both physical and digital security measures to help protect customer data and workloads.

Governance

Cloud environments provide tools and policies that help organizations maintain compliance and control over resources.

Manageability

Administrators can monitor, configure, and maintain cloud resources through centralized management tools.

Cloud Service Models

One of the most important concepts in cloud computing is understanding the different service models.

Infrastructure as a Service (IaaS)

IaaS provides the foundational infrastructure required to run applications.

With IaaS, you rent:

Virtual machines
Storage
Networking
Operating systems

The cloud provider manages the physical infrastructure while you manage the operating systems, applications, and data.

Platform as a Service (PaaS)

PaaS provides a complete environment for building, testing, and deploying applications.

With PaaS, developers can focus on writing code without worrying about managing the underlying infrastructure.

Software as a Service (SaaS)

SaaS delivers fully managed software applications over the internet.

Examples include:

Microsoft 365
Email platforms
Calendars
Collaboration tools

Users simply access the application while the provider manages everything behind the scenes.

Final Thoughts

Cloud computing has transformed the way organizations consume technology. By providing flexible, scalable, and cost-effective services over the internet, the cloud allows businesses to focus more on innovation and less on managing infrastructure.

For beginners, understanding deployment models, cloud benefits, and service models is the foundation for learning platforms such as Microsoft Azure, AWS, and Google Cloud.

This article is part of my ongoing journey into cloud computing, networking, and infrastructure technologies. As I continue learning, I'll be sharing more practical insights and lessons along the way.