Azure is one of the most popular cloud platforms, and many learners are
eager to get started. However, beginners often feel overwhelmed due to the
wide range of services and concepts. If you have no prior experience in cloud
computing or Azure, the best place to start is with Azure Fundamentals
(AZ-900). In this blog series, we will cover both theoretical concepts and
practical hands-on exercises to help you build a strong foundation in
Microsoft Azure.
We will also provide a real-world,
enterprise-level roadmap to guide your learning journey step by
step.
For Phase 1 (Cloud Fundamentals) the topics I listed are sufficient to understand Azure basics, but if your
goal is to prepare properly for Microsoft Certified:
Azure Fundamentals (AZ-900) and to build a solid base for
later phases, you should expand Phase 1 slightly.
Think of
Phase 1 as “cloud literacy +
Azure platform orientation.
Below is a complete but still
beginner-level Phase 1 syllabus.
Phase 1 — Azure
Fundamentals
(Expanded) -
CLICK HERE
Phase 2 — Azure global infrastructure regions availability zones (Expanded) - CLICK HERE
Azure Core Services Overview
You do not need deep knowledge yet — just understand what these
services do.
Compute
- Example services:
- Azure Virtual Machines
- App Services
- Containers
Purpose: running applications and servers.
------------------------------------
Storage
- Learn basic storage services:
- Azure Blob Storage
- File storage
- Disk storage
- Archive storage
Purpose: storing data.
------------------------------------
Networking
- Basic networking concepts in Azure:
- Virtual Network (VNet)
- Subnet
- Public IP
- Load balancer
- VPN gateway
You don’t need deep configuration yet — just understand the
purpose.
An easy way to differentiate between
VMs and containers is - virtual machine
virtualize the hardware and container is
virtualize the operating system.
The operating system level virtualization of containers is one reason why
the container approach is more efficient than a full virtual machine.
It allows you to run multiple lightweight containers on a single host
without sacrificing the isolation that the virtual machine originally
offered.
Azure supports several container variations, the most popular being
Docker.
you can easily deploy and manage multiple containerized
applications without worrying about which server will host each container.
The decision of whether to use a VM or a container depends on how much
flexibility you need
If you need to completely control the environment, then you might
choose a VM.
If then the probability, performance characteristics and management
capabilities of containers might be the better choice.
In Microsoft azure, everything you build falls
into 3 main categories.
Compute -> Storage -> Networking
1. Compute (Run application)
A compute is the set of cloud services used to run applications, virtual
machines, and workloads.
Azure Virtual Machines (VMs)
Azure virtual machines are on-demand, scalable computing
resources that provide full control over the operating system and
applications.
Example - Run a windows/Linux Server
App Services
Azure app
services is a platform for building, deploying, and hosting web application
without managing the underlying infrastructure.
Example - Host a website or API
Containers
A containers are lightweight, portable units that package an application
and its dependencies to run consistently across environment.
Example
- Run apps using docker
2. Storage (Store data)
Storage services in azure are used to store, manage, and retrieve
data in a secure and scalable way.
Blob Storage
Azure blob storage is an object storage service used to store
large amounts of unstructured data such as an images, videos and documents.
File Storage
Azure file storage provides fully managed file shares in the
cloud that can be accessed via standard file protocol.
Disk Storage
Azure disk storage provides persistent block level storage
volumes for use with virtual machine.
Archive Storage
Azure Archive storage is a low-cost storage tier designed for
long-term retention of infrequently accessed data.
3. Networking
A networking services in azure enable communications between
resources, users, and on-premises environment.
Virtual Network (VNet)
A virtual network is a logically isolated network in azure that
allows resources to securely communicate with each other.
Subnet
A subnet is a segmented portion of a virtual network used to
organize and manage resource efficiently.
Public IP
A public IP address is an internet routable IP address that
allows azure resources to be accessed from outside the network.
Load Balancer
Azure load balancer distributes incoming network traffic across multiple
resources to ensure high availability and reliability.
VPN Gateway
A VPN gateway enables secure communication between azure virtual
networks and on-premises networks over the internet.
Describe Azure virtual networking
Virtual Network (VNet) = Your private network in Microsoft
Azure
Everything else is just features of that network.
Remember does 6 things :
VNet does 6 things:
1. Isolate (Separate network)
2. Connect (Azure
resources)
3. Internet Access
4. Connect to on-premises
5.
Control traffic (routing)
6. Secure traffic (filtering)
That's
it. That entire page = these 6 points.
1. Isolation
You can create multiple private networks. (like different
departments)
2. Communication
Resources
inside azure can talk to each other.
3. Internet Access
Add public IP ->
accessible from internet.
4. On-premises connection
Connect your office network to
azure.
5. Routing
Decide where traffic should go.
6. Security (Filtering)
Allow or block traffic using
rules.
Visual Memory
Azure Virtual Private Network (VPN)
VPN - Secure tunnel over the internet
A
VPN securely connects networks or devices over the public
internet using encryption.
Your Network <-- Encrypted Tunnel <-- Azure VNet
Even though data goes over the internet.
It is encrypted and
safe.
VPN Gateway
A VPN gateway is an azure service that enables secure
communication between networks using VPN.
Like
1. Site-to-Site (S2S) -> office <-> Azure
2.
Point-to-Point (P2P) -> Laptop <-> Azure
3. VNet-to-VNet ->
Azure <-> Azure
Types of VPN
1. Policy-Based
Uses fixed rules (IP-based)
Less
flexible
2. Route-Based
Uses routing
tables
More flexible & preferred
Always remember
Route-based VPN = Recommended in Azure
High Availability
Azure makes VPN reliable using:
1. Active / Standby (default)
Active VPN ->
Working
Standby VPN -> Backup
If active fails ->
standby takes over
2. Active / Active
Both
gateways work at the same time
High performance + redundancy
3. ExpressRoute Failover
If private connection fails -> VPN acts as backup
4. Zone-Redundant Gateway
Gateway spread across availability zones
protects from data
center failure
How to remember this easily
VPN = Secure Connection
Gateway does 3 things:
- Connect networks
- Encrypt data
- Provide high
availability
Final One-Line Summary
Azure VPN securely connects networks and users to
azure using encrypted tunnels, managed by VPN gateway with high availability
support.
Azure DNS is a hosting service that provides domain
name resolution using Azure infrastructure, allowing you to manage DNS records
with high availability, security and performance.
Azure DNS - Simple understanding
Azure DNS is a service that translates domain name (like google.com)
into IP addresses using Azure infrastructure.
Human use names:
www.google.com
Computers use IP:
142.250.x.x
DNS = translator
What is Azure DNS ?
Azure DNS lets you host and manage your domain's DNS record using
Azure.
means
You control domain records
Using
azure tools
Benefits
Instead of
remembering all text, remember this:
1. Fast (global network)
2.
Secure (RBAC + logs)
3. Easy (same Azure tools)
4. Private domains
(VNet support)
5. Smart mapping (alias records)
1. Reliability & performance
Uses global azure servers
closest server answers ->
faster
Keywords: Anycast (closest server responds)
2. Security
controlled using:
RBAC Role based access control (who
can access)
Logs (who did what)
Locks (prevent deletion)
3. Ease of Use
Same tools as Azure:
Portal
CLI
PowerShell
No
need to learn new system.
4. Private DNS (very important)
Use custom names inside your network
Example
Instead
of:
vm123.internal.cloud
You use:
myserver.local
5. Alias Records (Smart Features)
Point domain to Azure resources.
Example
Domain
-> Public IP
Domain -> CDN
If IP changes -> auto
update
Important Note
Azure DNS does NOT sell domain name
You must buy
from
Domain register
Then connect to Azure
Memory Trick
DNS = Name -> IP
Azure DNS = Manage DNS in Azure
Benefits:
Fast + Secure + Easy + Private + Smart
Please share and thank you for your support.






























