| Module | Title | Hours |
|---|---|---|
| 1 | Deeper Dive into Core Services | 10–12 |
| 2 | Identity, Security & Compliance | 8–10 |
| 3 | Cost Management & Optimization | 6–8 |
| 4 | Management, Monitoring & Automation | 8–10 |
| 5 | Real-world Scenarios & Hands-on | 10–12 |
| Total | 42–52 hours |
Welcome back, cloud explorer! 🌟 In this module, we will go deeper into Azure's most important services. We already know the basics – now we will learn how to use them like a pro. Think of this as moving from riding a bicycle 🚲 to driving a car 🚗 – more power, more control!
Remember our workshop from the beginner course? Now it's time to upgrade it!
Imagine you have a workshop with many rooms. But now you have:
In this module, you will learn how to use these advanced tools to build amazing things!
Definition: VM sizing is about choosing the right amount of CPU, memory, and storage for your virtual machine.
Why important: If you choose a small VM, your app will be slow. If you choose a huge VM, you waste money.
Simple: Like buying shoes – you need the right size!
Real-life: A video editing company needs a large VM with lots of memory.
School: A small school website can use a tiny VM.
Home: A Minecraft server needs a medium VM.
Nigerian: A fintech in Lagos uses a large VM for transaction processing.
| VM Series | Use Case |
|---|---|
| B-series (burstable) | Websites with low traffic |
| D-series (general purpose) | Most applications |
| E-series (memory optimized) | Databases, analytics |
| N-series (GPU) | AI, video rendering |
✅ Summary: Choose the VM size that fits your needs – not too big, not too small.
Definition: Managed disks are Azure's storage for VM hard drives. They are easier to manage than unmanaged disks.
Why important: They handle backups, scaling, and security automatically.
Simple: Like having a housekeeper for your hard drives!
Real-life: A company uses managed disks so they don't worry about disk failures.
School: The school's VM uses a managed disk for safety.
Home: You use a managed disk for your personal VM.
Nigerian: A hospital uses managed disks for patient records.
Unmanaged Disk = You manage everything (hard work!)
Managed Disk = Azure manages it (easy!)
✅ Summary: Managed disks are easier and safer for your VMs.
Definition: VM extensions are small programs that run on your VM to add features, like installing software or configuring settings.
Why important: You can automate tasks without logging into the VM.
Simple: Like adding a new app to your phone with one tap.
Real-life: A company uses an extension to install antivirus software on all VMs.
School: The IT teacher uses an extension to install Python on all VMs.
Home: You use an extension to set up a web server.
Nigerian: A startup uses an extension to install Node.js on its VMs.
VM Extension = Small program that runs on the VM
Example: Install Chrome, update Windows, etc.
✅ Summary: Extensions let you automate tasks on your VMs.
Definition: App Service is a PaaS service that hosts web applications. You just upload your code, and Azure runs it.
Why important: No need to manage servers – just focus on your app.
Simple: Like uploading a video to YouTube – you don't need to build the video player!
Real-life: A company hosts its e-commerce website on App Service.
School: The school's website is on App Service.
Home: You can host a blog on App Service.
Nigerian: A restaurant in Abuja uses App Service for its online menu.
✅ Summary: App Service lets you host web apps without managing servers.
Definition: Deployment slots are separate environments in App Service where you can test your code before swapping it to the main (production) slot.
Why important: You can test changes without affecting real users.
Simple: Like trying on clothes in a dressing room before buying them.
Real-life: A company tests a new feature in a staging slot before going live.
School: The school tests a new homework portal in a staging slot.
Home: You test a new blog design in a staging slot.
Nigerian: A fintech tests payment updates in a staging slot.
Production slot = live website (real users)
Staging slot = test version (only you see it)
Swap = make staging the new production!
✅ Summary: Deployment slots let you test changes safely.
Definition: Custom domains let you use your own website name (like mywebsite.com) instead of the Azure default. SSL makes it secure (https://).
Why important: It looks professional and builds trust.
Simple: Like having a personalised number plate on your car.
Real-life: Every company uses a custom domain for its website.
School: The school uses myschool.edu.ng.
Home: You can buy a domain for your personal blog.
Nigerian: A business uses mybusiness.com.ng.
✅ Summary: Custom domains and SSL make your website look professional.
Definition: ACI lets you run containers (lightweight packages of code) in Azure without managing any servers.
Why important: It's fast and cheap for small applications.
Simple: Like a microwave meal – quick and easy!
Real-life: A company runs a small reporting tool in ACI.
School: A teacher runs a quiz app in ACI.
Home: You run a fun game in ACI.
Nigerian: A startup runs a prototype in ACI.
Container = small package of code + environment
ACI = run containers without managing servers
✅ Summary: ACI lets you run containers easily and cheaply.
Definition: AKS is a service that helps you manage a large group of containers – it's like a traffic controller for containers.
Why important: When you have many containers, you need a system to manage them.
Simple: Like a school principal who manages many classrooms.
Real-life: A big company runs hundreds of containers with AKS.
School: Not used in schools – it's for big companies.
Home: Not used at home.
Nigerian: A large bank uses AKS to manage its microservices.
✅ Summary: AKS helps you manage many containers.
Definition: Azure Functions is a serverless service – you write code that runs only when triggered.
Why important: You pay only when the code runs, not for idle time.
Simple: Like a vending machine – it only works when you press a button.
Real-life: A photo app uses a function to resize images when you upload them.
School: A function could send a notification when a teacher posts homework.
Home: A function could turn on your smart lights when you arrive home.
Nigerian: A delivery app uses a function to calculate shipping costs.
Trigger (e.g., upload photo) → Function runs → Done (resized photo)
✅ Summary: Functions run code only when needed, saving money.
Definition: A trigger is what starts a function (like a timer or a file upload). Bindings are connections to data (like reading from a database).
Why important: They make functions very flexible.
Simple: A trigger is like an alarm clock; bindings are like a phone line.
Real-life: A function triggers when an email arrives and saves it to storage.
School: A function triggers when a new student is added.
Home: A function triggers when a new photo is uploaded.
Nigerian: A function triggers when a transaction is made.
| Trigger Type | Example |
|---|---|
| Timer | Run every 5 minutes |
| HTTP | Call function via a URL |
| Blob | Run when a file is uploaded |
| Queue | Run when a message arrives |
✅ Summary: Triggers start functions; bindings connect to data.
Definition: VNet is a private network inside Azure, just like your home Wi-Fi.
Why important: It keeps your resources safe and connected.
Simple: A VNet is like a private road system for your cloud resources.
Real-life: A company uses VNet to connect its web server to its database securely.
School: The school network connects all computers – VNet does the same in Azure.
Home: Your home Wi-Fi connects your phone, laptop, and TV.
Nigerian: A healthcare provider uses VNet to connect patient records safely.
VNet = private cloud network
├── Subnet A (Web servers)
├── Subnet B (Database servers)
└── Subnet C (Application servers)
✅ Summary: VNet creates a private network for your Azure resources.
Definition: VNet peering lets you connect two VNets so they can communicate as if they were one network.
Why important: You can connect resources in different regions.
Simple: Like building a bridge between two islands.
Real-life: A company has VNets in Lagos and Europe and peers them.
School: Two school buildings connected by a walkway.
Home: Two routers connected to share internet.
Nigerian: A bank peers VNets in South Africa and Nigeria.
✅ Summary: VNet peering connects two VNets.
Definition: A load balancer distributes incoming traffic across multiple VMs so no single VM gets overloaded.
Why important: It makes your app reliable and fast.
Simple: Like a receptionist who sends visitors to different offices.
Real-life: A popular website uses a load balancer to handle millions of users.
School: The school office sends students to different classrooms.
Home: Not used at home.
Nigerian: An e-commerce site uses a load balancer during sales.
User requests → Load Balancer → VM1, VM2, VM3 (spread evenly)
✅ Summary: A load balancer distributes traffic to keep your app running smoothly.
Definition: Lifecycle management is a rule that automatically moves files to cheaper storage tiers when they become old.
Why important: It saves money.
Simple: Like moving winter clothes to the attic when summer comes.
Real-life: A company moves old project files to Archive after 2 years.
School: Old student records are archived.
Home: Old photos are moved to Archive.
Nigerian: A bank archives old transaction records.
New file → Hot tier (fast, expensive)
After 30 days → Cool tier (cheaper)
After 1 year → Archive tier (cheapest)
✅ Summary: Lifecycle management moves old data to cheaper storage.
Definition: A SAS is a secure link that gives temporary access to a storage file or container.
Why important: You can share files without giving away your storage keys.
Simple: Like a temporary key to your house for a friend.
Real-life: A company shares a large file with a client via a SAS link.
School: The teacher shares a PDF with students via a SAS link.
Home: You share a family video with a relative.
Nigerian: A lawyer shares a contract file with a client.
SAS URL = https://storage...?sp=r&se=2025-12-31...
(expires on 2025-12-31)
✅ Summary: SAS lets you share files securely and temporarily.
Small VM (B1s) → Web apps, low traffic
Medium (D2s) → General purpose
Large (E4s) → Databases, analytics
Users → Load Balancer
├── VM1
├── VM2
└── VM3
New file → Hot tier (0–30 days)
After 30 days → Cool tier
After 365 days → Archive tier
| Service | Type | Use case |
|---|---|---|
| Virtual Machines | IaaS | Full control, custom OS |
| App Service | PaaS | Web apps, APIs |
| Functions | Serverless | Event-driven, short tasks |
| ACI | Container | Simple container workloads |
| AKS | Container orchestration | Complex container management |
| Tier | Access frequency | Cost |
|---|---|---|
| Hot | Frequent | High |
| Cool | Infrequent | Medium |
| Archive | Rare | Low |
In this module, we took a deeper dive into Azure's core services. We learned:
You now have a solid understanding of Azure's core services at an intermediate level. In the next module, we will learn about Identity, Security, and Compliance.
Match the service with its description.
| Service | Description |
|---|---|
| App Service | Host web apps |
| Functions | Run code on demand |
| ACI | Run containers without servers |
| AKS | Manage many containers |
| VNet | Private network |
| Load Balancer | Distribute traffic |
| SAS | Temporary secure link |
Scenario 1: A company in Lagos wants to host a web app that gets 50,000 visitors per day. They want to test changes before going live. Which services should they use?
Scenario 2: A school wants to store old student records for 10 years. They don't need fast access. Which storage tier should they use?
Scenario 3: A fintech company needs to run a small piece of code when a transaction is made. Which service should they use?
In groups, design a simple architecture for a Nigerian e-commerce website. Include:
Draw a diagram of a VNet with two subnets: one for web servers and one for database servers. Label the components.
Cloud Architecture Design: Design a cloud architecture for a mobile app that lets users upload and share photos. Specify which Azure services you would use for compute, storage, and networking. Draw a diagram and explain your choices.
If you have an Azure free account, do the following:
Research how to create an Azure Function that triggers when a file is uploaded to storage. Write a simple guide on how to set it up.
In the next module, we will learn about Identity, Security, and Compliance. We'll cover:
Review the concepts of subscriptions and resource groups – they will be very important in Module 2.
🎉 Congratulations! You have completed Module 1 (Intermediate). Keep going! 🚀
Welcome to the world of security! 🌍 Now that we know how to build things in Azure, we need to learn how to protect them. In this module, we will learn about identities (who you are), security (keeping bad guys out), and compliance (following the rules). Think of it like a castle – you build walls, guard towers, and only let trusted people inside.
Imagine you are the king or queen of a big castle 🏰. Inside the castle, you have treasure, important documents, and many rooms.
You need to make sure that:
In this module, you will learn how to build your own secure castle in Azure!
Definition: Microsoft Entra ID (formerly Azure AD) is a cloud-based service that manages users and their access to resources.
Why important: It is the central place where you control who can access your Azure resources.
Simple: Like a school register – it has the names of all students and who can enter which classroom.
Real-life: A company uses Entra ID to manage employee logins to all their apps.
School: The school uses a system to manage student and teacher logins.
Home: Your Microsoft account is an Entra ID identity.
Nigerian: A Lagos bank uses Entra ID to manage employee access to banking apps.
Entra ID = Master list of users and their permissions
├── Users (people)
├── Groups (teams)
└── Applications (apps they can use)
✅ Summary: Entra ID is the service that manages identities in Azure.
Definition: A tenant is a dedicated instance of Entra ID for your organisation. It is like your own private copy of the service.
Why important: It keeps your users and data separate from other organisations.
Simple: Like having your own locker at school – only you have the key.
Real-life: Each company has its own tenant.
School: The school has its own tenant for all teachers and students.
Home: Not used at home.
Nigerian: A fintech has its own tenant for its employees.
Tenant = Your private directory in Entra ID
✅ Summary: A tenant is your organisation's private space in Entra ID.
Definition: A user is a person (or application) that needs access. A group is a collection of users.
Why important: Groups make it easy to give permissions to many people at once.
Simple: A user is like a student; a group is like a class.
Real-life: A company has users (employees) and groups (Marketing, Sales, IT).
School: Students are users; a class is a group.
Home: Family members are users; the "family" is a group.
Nigerian: A startup has users (employees) and groups (Developers, Managers).
User = Individual person
Group = Collection of users (e.g., "Finance Team")
✅ Summary: Users are individuals; groups are collections of users.
Definition: SSO lets you log in once with one set of credentials to access multiple apps.
Why important: You don't need to remember many passwords.
Simple: Like a master key that opens all doors in your house.
Real-life: Employees log in once to access email, HR system, and cloud apps.
School: Students use one login for the school portal and online library.
Home: You use your Google account to log in to YouTube, Gmail, and Drive.
Nigerian: A bank uses SSO for employees to access multiple internal apps.
Login once → Access all apps (no need to re-enter passwords)
✅ Summary: SSO means one login for many apps.
Definition: MFA requires two or more verification methods to log in. For example, a password + a code sent to your phone.
Why important: It makes it much harder for hackers to break in.
Simple: Like a bank vault that needs a key and a combination.
Real-life: Your online banking uses MFA.
School: Teachers use MFA to access student records.
Home: You can enable MFA on your Microsoft account.
Nigerian: Many Nigerian banks use MFA for online banking.
Step 1: Enter password
Step 2: Enter code from phone
✅ Access granted!
✅ Summary: MFA adds an extra layer of security to your login.
Definition: RBAC assigns permissions to users, groups, or applications based on their roles.
Why important: You give people only the permissions they need.
Simple: Like a school where teachers can grade, but students can only view.
Real-life: An admin can create VMs, a reader can only view them.
School: The principal can change settings, but the librarian can only view.
Home: Parents have full control, children have limited access.
Nigerian: A company gives developers "contributor" rights but not "owner".
| Role | Permissions |
|---|---|
| Owner | Can do everything |
| Contributor | Can create/manage resources but not give access |
| Reader | Can only view resources |
✅ Summary: RBAC gives permissions based on roles.
Definition: Azure Security Center is a tool that helps you monitor and improve your security posture.
Why important: It alerts you to threats and gives recommendations.
Simple: Like a security guard who watches cameras and tells you if something is wrong.
Real-life: A company uses Security Center to monitor its VMs for threats.
School: The school uses it to protect student data.
Home: Not used at home.
Nigerian: A hospital uses Security Center to protect patient records.
Security Center
├── Monitors for threats
├── Gives security recommendations
└── Shows Secure Score (how secure you are)
✅ Summary: Security Center monitors your Azure resources for security issues.
Definition: Azure Defender is a service that provides advanced threat protection for your resources, like VMs, databases, and storage.
Why important: It detects sophisticated attacks that basic tools might miss.
Simple: Like a detective who investigates suspicious activities.
Real-life: A bank uses Azure Defender to detect unusual transactions.
School: Not used in schools.
Home: Not used at home.
Nigerian: A fintech uses Azure Defender to protect against fraud.
Azure Defender = Advanced security for VMs, databases, storage, etc.
✅ Summary: Azure Defender provides advanced threat protection.
Definition: Key Vault is a service that securely stores secrets, keys, and certificates.
Why important: You don't want to hard-code passwords in your code.
Simple: Like a safe where you keep your most valuable items.
Real-life: A company stores database passwords in Key Vault.
School: The school stores API keys in Key Vault.
Home: Not used at home.
Nigerian: A startup stores payment gateway keys in Key Vault.
Key Vault = Secure storage for:
├── Secrets (passwords, keys)
├── Keys (encryption keys)
└── Certificates (SSL/TLS)
✅ Summary: Key Vault securely stores your secrets.
Definition: A managed identity is an identity that Azure creates for a service (like a VM or Function) so it can authenticate to other Azure services.
Why important: You don't need to store credentials – Azure handles it.
Simple: Like a security badge that is automatically given to a robot.
Real-life: A VM uses a managed identity to access Key Vault.
School: Not used in schools.
Home: Not used at home.
Nigerian: A function app uses a managed identity to access storage.
Managed Identity = Automatic identity for Azure services
No need to store passwords!
✅ Summary: Managed identities let Azure services authenticate automatically.
Definition: Azure Policy is a service that lets you create rules to enforce standards across your resources.
Why important: It prevents people from making mistakes, like creating VMs in the wrong region.
Simple: Like school rules – you can't run in the hallway.
Real-life: A company uses a policy to only allow VMs in a specific region.
School: A policy ensures all school resources use the same naming convention.
Home: Not used at home.
Nigerian: A bank uses policies to ensure all VMs are in South Africa.
Policy: Allowed locations = South Africa, Europe
If VM created in US → Policy denies it
✅ Summary: Azure Policy enforces rules to keep things consistent.
Definition: Azure Blueprints is a service that lets you define a set of resources, policies, and roles to create a repeatable environment.
Why important: You can deploy a whole set of resources with one click.
Simple: Like a recipe – follow it to bake the same cake every time.
Real-life: A company uses Blueprints to create new development environments.
School: The school uses Blueprints to set up new labs.
Home: Not used at home.
Nigerian: A startup uses Blueprints to deploy its app to multiple regions.
Blueprint = Pre-packaged environment (resources + policies + roles)
✅ Summary: Blueprints help you deploy compliant environments quickly.
Definition: A lock prevents a resource from being deleted or changed accidentally.
Why important: You don't want someone to delete your important VM.
Simple: Like putting a child-proof lock on a cabinet.
Real-life: A company locks its production database so no one can delete it.
School: The school locks the server that stores exam results.
Home: You lock your diary so no one reads it.
Nigerian: A hospital locks patient records to prevent accidental deletion.
Lock Types:
- CanNotDelete (prevents deletion)
- ReadOnly (prevents changes)
✅ Summary: Resource locks protect important resources from being deleted or changed.
Definition: Tags are key-value pairs (like "Project: Website" or "CostCenter: Marketing") that you add to resources.
Why important: They help you organise, track costs, and manage resources.
Simple: Like putting sticky notes on your belongings to know what they are for.
Real-life: A company tags resources by project, department, and environment (Dev/Prod).
School: Tags can show which class uses which resource.
Home: You might tag photos with names and dates.
Nigerian: A startup tags resources by region (Lagos, Abuja).
Tag: Environment = Production
Tag: Department = Finance
Tag: Project = PayrollApp
✅ Summary: Tags are labels that help you organise and track resources.
Definition: Defense in depth is a strategy that uses multiple layers of security to protect your resources. If one layer fails, another layer stops the attack.
Why important: It's like having multiple doors – if a thief breaks one, there is still another locked door.
Simple: Like a castle with walls, a moat, and guards.
Real-life: A company uses network firewalls, MFA, and encryption.
School: The school has locks on doors, security cameras, and passwords.
Home: Your home has a gate, a door lock, and an alarm.
Nigerian: A bank uses firewalls, encryption, and MFA.
Defense in Depth:
Layer 1: Network (firewall, NSG)
Layer 2: Identity (MFA, RBAC)
Layer 3: Data (encryption)
Layer 4: Applications (secure code)
✅ Summary: Defense in depth uses multiple security layers.
Layer 1: Network (firewalls, NSGs)
Layer 2: Identity (MFA, RBAC)
Layer 3: Data (encryption)
Layer 4: Applications (secure code)
Owner → Full control
Contributor → Can create/update resources
Reader → Can only view
Enter password → Enter code from phone → Access granted ✅
| Service | Purpose |
|---|---|
| Security Center | Monitoring and recommendations |
| Azure Defender | Advanced threat protection |
| Key Vault | Store secrets |
| Policy | Enforce rules |
| Blueprints | Deploy compliant environments |
| Role | Can create resources? | Can assign roles? |
|---|---|---|
| Owner | Yes | Yes |
| Contributor | Yes | No |
| Reader | No | No |
In this module, we learned about identity, security, and compliance in Azure. We covered:
You now have a strong understanding of how to secure and govern your Azure resources. In the next module, we will learn about Cost Management and Optimization.
Match the service with its purpose.
| Service | Purpose |
|---|---|
| Entra ID | Manage identities |
| MFA | Extra security |
| RBAC | Assign permissions |
| Key Vault | Store secrets |
| Azure Policy | Enforce rules |
| Resource Lock | Prevent deletion |
| Tags | Organise resources |
Scenario 1: A Nigerian bank wants to ensure that only IT staff can create VMs. Which Azure service should they use?
Scenario 2: A company wants to store database passwords securely. Which service should they use?
Scenario 3: A hospital wants to monitor its resources for threats. Which service should they use?
In groups, design a security plan for a Nigerian e-commerce company. Include:
Create a list of tags you would use for a cloud project. Include tags for project, department, environment, and cost centre.
Security Plan: Create a security plan for a fictional Nigerian company. Include identity management, access control, monitoring, governance, and defense in depth. Present your plan to the class.
If you have an Azure account, try the following:
Research how to create an Azure Policy that only allows VMs in a specific region. Write a simple guide on how to set it up.
In the next module, we will learn about Cost Management and Optimization. We'll cover:
Review your knowledge of subscriptions and resource groups – they will be important in Module 3.
🎉 Congratulations! You have completed Module 2 (Intermediate). Keep going! 🚀
Welcome to the money-saving module! 💵 In the cloud, you pay for what you use – but if you are not careful, your bill can be huge! In this module, we will learn how to plan, track, and reduce your Azure costs. Think of it like managing your pocket money – you need to know how much you have, where it goes, and how to save.
Imagine you have a lemonade stand 🍋. You need to buy lemons, sugar, and cups. You also need to pay for water and ice.
If you buy too many lemons, they go bad and you waste money. If you buy too few, you run out and lose customers.
You need to plan how much to buy, track what you spend, and optimize to make a profit.
In Azure, it's the same! You plan, track, and optimize your cloud spending to stay within budget.
Definition: Azure uses a pay-as-you-go model – you pay only for what you use, and you can stop anytime.
Why important: You don't need to buy expensive hardware upfront.
Simple: Like paying for water – you pay for what comes out of the tap.
Real-life: A company pays for VMs only when they are running.
School: The school pays for storage only for the term.
Home: You pay for extra iCloud storage only if you need it.
Nigerian: A small business uses cloud services and pays only for what they use each month.
Pay-as-you-go = pay per unit (like ₦ per GB or per hour)
✅ Summary: You pay only for what you consume, like a utility bill.
Definition: The Pricing Calculator is a free tool on the Azure website that helps you estimate how much a service will cost.
Why important: You can plan before you spend.
Simple: Like using a calculator to add up your shopping list.
Real-life: A company calculates the cost of running a VM for a year.
School: The IT teacher estimates the cost of hosting the school website.
Home: You can use it to see how much it would cost to store your family photos.
Nigerian: A fintech startup uses the calculator before launching a new service.
Pricing Calculator
├── Choose service (e.g., VM)
├── Set options (size, region, hours)
└── Get estimated cost
✅ Summary: The Pricing Calculator helps you estimate your Azure costs.
Definition: The TCO (Total Cost of Ownership) calculator compares the cost of running your own servers (on-premises) versus using the cloud.
Why important: It helps you decide if moving to the cloud saves money.
Simple: Like comparing the cost of buying a car vs. renting one.
Real-life: A company uses TCO to decide whether to move to Azure.
School: A school compares the cost of a physical server room vs. cloud.
Home: Not usually used by individuals.
Nigerian: A bank uses the TCO calculator to justify moving to the cloud.
| Aspect | On-premises | Cloud (Azure) |
|---|---|---|
| Hardware cost | High upfront | Pay as you go |
| Maintenance | You manage | Microsoft manages |
| Electricity | You pay | Included |
| Scalability | Hard | Easy |
✅ Summary: TCO calculator shows the total cost of on-premises vs. cloud.
Definition: A tool in the Azure portal that shows you exactly how much you're spending and on what.
Why important: You need to see where your money is going.
Simple: Like a bank statement for your cloud usage.
Real-life: A manager checks Cost Management to see if a project is over budget.
School: The school's finance officer tracks cloud spending monthly.
Home: You can see how much your free trial is using.
Nigerian: A company in Abuja reviews Cost Management every week.
Cost Management
├── View spending by resource
├── Set budgets & alerts
└── Recommendations to save money
✅ Summary: Cost Management + Billing helps you track and control spending.
Definition: A budget is a spending limit you set for a subscription or resource group. You get alerts when you reach a certain percentage.
Why important: It prevents surprise bills.
Simple: Like a weekly allowance – you can't spend more than you have.
Real-life: A company sets a monthly budget of $10,000 for Azure.
School: The school sets a budget for cloud storage.
Home: You set a budget for your mobile data.
Nigerian: A startup sets a budget of ₦500,000 per month.
Budget: ₦500,000/month
Alert at 80% (₦400,000) → Get email notification
✅ Summary: Budgets help you limit spending and avoid surprises.
Definition: Cost Analysis is a tool that lets you see your spending over time, by resource, by service, or by tag.
Why important: You can find out which services cost the most.
Simple: Like looking at a pie chart of your spending.
Real-life: A company sees that 60% of their cost is from VMs.
School: The school sees that storage costs the most.
Home: You see which apps use the most data.
Nigerian: A fintech sees that database costs are high.
Cost Analysis = Detailed view of your spending
├── By service (VMs, storage, etc.)
├── By resource (VM1, VM2, etc.)
└── By tag (Project, department)
✅ Summary: Cost Analysis helps you understand where your money goes.
Definition: Azure Advisor is a free service that gives you personalized recommendations to save money, improve performance, and increase security.
Why important: It tells you exactly what to do to save money.
Simple: Like a friend who gives you tips on saving money.
Real-life: Azure Advisor recommends shutting down idle VMs.
School: The school gets recommendations to resize VMs.
Home: Not used at home.
Nigerian: A startup gets recommendations to use reserved instances.
Azure Advisor
├── Cost recommendations (save money)
├── Performance recommendations (make things faster)
└── Security recommendations (make things safer)
✅ Summary: Azure Advisor gives you free recommendations to save money.
Definition: Reserved Instances let you pay for a VM or other service for 1 or 3 years in advance, at a discount of up to 72%.
Why important: It saves a lot of money for long-term workloads.
Simple: Like buying a yearly movie pass instead of paying per movie.
Real-life: A company reserves a VM for 3 years and saves 50%.
School: The school reserves a database server for 1 year.
Home: Not used at home.
Nigerian: A bank reserves VMs for 3 years to save costs.
| Payment option | Discount | Best for |
|---|---|---|
| Pay-as-you-go | 0% | Short-term, variable workloads |
| 1-year Reserved | Up to 40% | Predictable workloads |
| 3-year Reserved | Up to 72% | Long-term, stable workloads |
✅ Summary: Reserved Instances save money for long-term use.
Definition: Savings Plans are similar to Reserved Instances but more flexible – you commit to a certain amount of spend per hour, and you get a discount on many services.
Why important: It offers flexibility – you can change services and still get a discount.
Simple: Like a monthly subscription that gives you a discount on everything you buy.
Real-life: A company commits to spending $50/hour and gets a discount on VMs and databases.
School: Not used in schools.
Home: Not used at home.
Nigerian: A startup uses Savings Plans to save on multiple services.
Savings Plans = Commit to a hourly spend, get discounts
├── Compute Savings Plan (VMs, App Service, etc.)
└── EC2 Instance Savings Plan (similar)
✅ Summary: Savings Plans offer flexible discounts for committing to a spend.
Definition: Azure Hybrid Benefit lets you use your on-premises Windows Server and SQL Server licenses in Azure, saving up to 40%.
Why important: You already paid for the licenses, so you save money.
Simple: Like using a gift card you already have.
Real-life: A company with on-premises Windows licenses uses them in Azure.
School: Not used in schools.
Home: Not used at home.
Nigerian: A bank with existing SQL Server licenses saves 40% in Azure.
Azure Hybrid Benefit = Use your existing licenses in Azure
Saves up to 40% on Windows VMs and SQL Server
✅ Summary: Azure Hybrid Benefit saves money by using your existing licenses.
Definition: Right-sizing means choosing the right size for your VMs and other resources – not too big, not too small.
Why important: A VM that is too big wastes money. A VM that is too small is slow.
Simple: Like buying shoes – you need the right size!
Real-life: A company monitors VM usage and resizes VMs to save money.
School: The school resizes a VM from Standard D4s to D2s.
Home: Not used at home.
Nigerian: A startup uses Azure Advisor to right-size VMs.
Monitor CPU usage → If usage is low (below 30%) → Downsize VM
If usage is high (above 80%) → Upsize VM
✅ Summary: Right-sizing helps you avoid paying for resources you don't need.
Definition: Idle resources are resources that are running but not being used. For example, a VM that runs 24/7 but is only used during business hours.
Why important: You pay for idle resources, so you can save money by stopping them.
Simple: Like turning off the lights when you leave a room.
Real-life: A company automatically stops VMs at night and on weekends.
School: The school stops VMs during holidays.
Home: You turn off your computer when not in use.
Nigerian: A startup uses Azure Automation to stop VMs after business hours.
Schedule: Stop VM at 6 PM, start at 8 AM
Save 60% of VM cost!
✅ Summary: Stop idle resources to save money.
Definition: Storage tiers (Hot, Cool, Archive) let you pay less for data you don't access often.
Why important: It saves money on storage.
Simple: Like moving winter clothes to the attic – they are harder to reach but save space.
Real-life: A company moves old project files to Archive after 2 years.
School: Old student records are archived.
Home: Old photos are moved to Archive.
Nigerian: A bank archives old transaction records.
| Tier | Access frequency | Cost |
|---|---|---|
| Hot | Frequent | High |
| Cool | Infrequent | Medium |
| Archive | Rare | Low |
✅ Summary: Use storage tiers to save money on old data.
Definition: Tags are labels you add to resources to track costs by project, department, or environment.
Why important: You can see which department or project is spending the most.
Simple: Like putting a name tag on your lunch box.
Real-life: A company tags resources by department (Marketing, IT, Finance).
School: The school tags resources by class.
Home: You tag photos with names and dates.
Nigerian: A startup tags resources by region (Lagos, Abuja).
Tag: Department = Finance
Tag: Project = PayrollApp
Tag: Environment = Production
✅ Summary: Tags help you track costs by project or department.
Definition: Best practices are the recommended ways to manage costs effectively.
Why important: They help you save money and avoid surprises.
Simple: Like a checklist for saving money.
Real-life: A company uses all these practices to keep costs low.
School: The school follows these practices.
Home: You follow similar practices for your personal budget.
Nigerian: A startup uses these practices to stay within budget.
Best Practices:
1. Use Pricing Calculator
2. Set budgets and alerts
3. Use Reserved Instances
4. Right-size resources
5. Stop idle VMs
6. Use storage tiers
7. Tag resources
8. Use Azure Advisor
✅ Summary: Following best practices helps you save money in Azure.
Plan → Use → Track → Adjust
Hot (frequent access) → $$$
Cool (infrequent) → $$
Archive (rarely) → $
Pay-as-you-go → 100% cost
1-year RI → 60% cost (40% savings)
3-year RI → 28% cost (72% savings)
| Option | Commitment | Discount | Flexibility |
|---|---|---|---|
| Pay-as-you-go | None | 0% | High |
| Reserved Instance (1-year) | 1 year | Up to 40% | Low |
| Reserved Instance (3-year) | 3 years | Up to 72% | Low |
| Savings Plan | 1 or 3 years | Up to 65% | Medium |
| Tier | Access frequency | Cost | Retrieval time |
|---|---|---|---|
| Hot | Frequent | High | Milliseconds |
| Cool | Infrequent | Medium | Milliseconds |
| Archive | Rare | Low | Hours |
In this module, we learned how to manage and optimize costs in Azure. We covered:
You now have the tools to keep your Azure costs under control. In the next module, we will learn about Management, Monitoring, and Automation.
Match the tool/service with its purpose.
| Tool/Service | Purpose |
|---|---|
| Pricing Calculator | Estimate costs |
| TCO Calculator | Compare on-premises vs. cloud |
| Cost Management | Track spending |
| Budget | Set spending limit |
| Azure Advisor | Give recommendations |
| Reserved Instance | Prepay to save |
| Savings Plan | Flexible savings |
| Storage Tier | Save on old data |
| Tag | Cost allocation |
Scenario 1: A Nigerian company runs a VM 24/7 but only uses it for 8 hours a day. How can they save money?
Scenario 2: A school has 5 years of student records that they rarely access. Which storage tier should they use?
Scenario 3: A fintech startup has a steady workload on VMs and wants to save money. What should they do?
In groups, design a cost management plan for a Nigerian company using Azure. Include:
Use the Azure Pricing Calculator to estimate the cost of running a VM for 1 year in the South Africa region. Write down your estimate and the assumptions you made.
Cost Optimization Plan: Create a cost optimization plan for a fictional Nigerian e-commerce company. Include cost estimation, tracking, savings strategies, and optimization practices. Present your plan.
If you have an Azure account, try the following:
Research how to create an Azure Automation runbook to stop VMs automatically after business hours. Write a simple guide.
In the next module, we will learn about Management, Monitoring, and Automation. We'll cover:
Review your knowledge of resources and subscriptions – they will be important in Module 4.
🎉 Congratulations! You have completed Module 3 (Intermediate). Keep going! 🚀
Welcome to the control room! 🎮 In this module, we will learn how to manage Azure, monitor our resources, and automate tasks. Think of it like being the pilot of a big airplane – you need to know all the controls, watch the instruments, and sometimes let the autopilot take over.
Imagine you are the captain of a spaceship 🚀. You need to:
Azure is like that spaceship! You use tools to manage it, monitors to watch it, and automation to make your life easier.
Definition: The Azure Portal is a website where you can manage all your Azure resources visually.
Why important: It's the easiest way for beginners to interact with Azure.
Simple: Like a car dashboard – you can see everything and control everything.
Real-life: A company's IT team uses the portal to create VMs and storage.
School: The IT teacher uses the portal to manage the school's resources.
Home: You can use the portal to create your free account.
Nigerian: A startup uses the portal to deploy its app.
Azure Portal = Web-based management
├── Create resources
├── Monitor resources
└── Manage access
✅ Summary: The Azure Portal is the main graphical interface for Azure.
Definition: Azure CLI (Command Line Interface) is a tool that lets you manage Azure using commands in a terminal or script.
Why important: It's faster for repetitive tasks and can be used in scripts.
Simple: Like typing instructions instead of clicking buttons.
Real-life: A developer uses CLI to create 100 VMs in one command.
School: The IT teacher uses CLI to automate tasks.
Home: Not used at home.
Nigerian: A sysadmin in Lagos uses CLI to manage multiple subscriptions.
az vm create --name MyVM --resource-group MyRG --image UbuntuLTS
✅ Summary: Azure CLI lets you manage Azure via commands.
Definition: Azure PowerShell is a tool that uses PowerShell commands (like CLI) to manage Azure, especially on Windows.
Why important: It's powerful for Windows automation.
Simple: Like CLI but for PowerShell fans.
Real-life: A Windows admin uses PowerShell to manage Azure VMs.
School: The IT teacher uses PowerShell for Windows tasks.
Home: Not used at home.
Nigerian: A bank uses PowerShell for Windows-based automation.
New-AzVM -Name MyVM -ResourceGroupName MyRG -Image UbuntuLTS
✅ Summary: Azure PowerShell lets you manage Azure from Windows.
Definition: Cloud Shell is a browser-based terminal where you can run CLI or PowerShell commands without installing anything.
Why important: You don't need to install any software – just use your browser.
Simple: Like having a terminal in your browser.
Real-life: A developer uses Cloud Shell from any computer.
School: Students use Cloud Shell for labs.
Home: You can use Cloud Shell from your browser.
Nigerian: A startup uses Cloud Shell for quick management.
Cloud Shell = Terminal in the browser
├── Azure CLI
└── Azure PowerShell
✅ Summary: Cloud Shell lets you use CLI/PowerShell from your browser.
Definition: ARM (Azure Resource Manager) templates are JSON files that define your infrastructure in code.
Why important: You can deploy the same environment over and over consistently.
Simple: Like a recipe – follow it to bake the same cake every time.
Real-life: A company uses ARM templates to deploy its production and test environments.
School: The school uses a template to set up a lab for students.
Home: Not used at home.
Nigerian: A startup uses ARM templates to deploy their app in multiple regions.
ARM Template = JSON code
├── VM
├── Storage
├── VNet
└── Deploy → Creates all resources together
✅ Summary: ARM templates let you define your infrastructure as code.
Definition: Bicep is a new language for Infrastructure as Code that is simpler and more readable than ARM templates.
Why important: It's easier to write and understand.
Simple: Like writing a recipe in plain English instead of a complicated list.
Real-life: A company uses Bicep for faster deployments.
School: The school uses Bicep for lab environments.
Home: Not used at home.
Nigerian: A startup uses Bicep for faster infrastructure deployment.
resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
name: 'MyVM'
location: 'southafricanorth'
...
}
✅ Summary: Bicep is a simpler language for Infrastructure as Code.
Definition: Azure Monitor collects data from your resources (like performance, logs, and metrics) and helps you understand what's happening.
Why important: You need to know if your app is running well.
Simple: Like a doctor's check-up for your cloud resources.
Real-life: A developer uses Azure Monitor to see if a VM is running out of memory.
School: The IT team monitors the school's website to see if it's fast.
Home: Not used at home.
Nigerian: A fintech uses Monitor to track transaction processing times.
Azure Monitor
├── Metrics (CPU, memory, etc.)
├── Logs (detailed records)
└── Alerts (notify when something is wrong)
✅ Summary: Azure Monitor helps you see how your resources are performing.
Definition: Log Analytics is a tool within Azure Monitor that lets you query and analyze logs using KQL (Kusto Query Language).
Why important: You can find specific events or patterns in your logs.
Simple: Like searching through a giant diary to find a specific event.
Real-life: A developer uses Log Analytics to find errors in their app.
School: The IT team uses Log Analytics to see who accessed the system.
Home: Not used at home.
Nigerian: A bank uses Log Analytics to detect fraud.
Log Analytics
├── Query logs
├── Create dashboards
└── Set up alerts
✅ Summary: Log Analytics lets you search and analyze logs.
Definition: Application Insights is a tool that monitors your application's performance and user behaviour.
Why important: It tells you how your app is performing for users.
Simple: Like a fitness tracker for your app.
Real-life: A company uses Application Insights to see which pages are slow.
School: The school uses it to monitor the online learning portal.
Home: Not used at home.
Nigerian: A startup uses Application Insights to improve their app.
Application Insights
├── Performance metrics
├── User analytics
└── Exception tracking
✅ Summary: Application Insights monitors your application's performance.
Definition: Alerts are notifications that something is wrong (e.g., CPU too high). Action Groups are groups of actions to take (e.g., send an email).
Why important: You need to know when something goes wrong.
Simple: Like a smoke alarm – it tells you when there's a fire.
Real-life: A company sets an alert when VM CPU is over 80%.
School: The school gets an alert when the website goes down.
Home: Not used at home.
Nigerian: A fintech gets alerts for high transaction volumes.
Alert: CPU > 80% → Action Group → Send email to IT team
✅ Summary: Alerts notify you when something needs attention.
Definition: Azure Automation is a service that lets you automate tasks using runbooks (scripts) and DSC (Desired State Configuration).
Why important: You can save time and reduce errors.
Simple: Like a robot that does your chores.
Real-life: A company uses Automation to stop VMs at night.
School: The school uses Automation to back up data daily.
Home: Not used at home.
Nigerian: A startup uses Automation to deploy updates.
Automation
├── Runbooks (scripts)
├── Desired State Configuration (DSC)
└── Schedules (when to run)
✅ Summary: Azure Automation automates repetitive tasks.
Definition: Azure Logic Apps is a service that lets you create workflows using a visual designer – no coding required!
Why important: You can connect different systems and automate processes.
Simple: Like building a LEGO castle – you just connect the pieces.
Real-life: A company uses Logic Apps to send emails when a file is uploaded.
School: The school uses Logic Apps to send notifications.
Home: Not used at home.
Nigerian: A startup uses Logic Apps to integrate with payment systems.
Trigger (e.g., file upload) → Action (e.g., send email)
✅ Summary: Logic Apps let you create workflows visually.
Definition: Service Health shows the status of Azure services across regions and alerts you about outages or planned maintenance.
Why important: If Azure has a problem, you need to know.
Simple: Like a weather report for the cloud.
Real-life: A company checks Service Health before blaming their app for slowness.
School: The school checks if Azure is down before calling IT.
Home: You might check if Xbox Live is down.
Nigerian: A startup checks Service Health to know if Azure is having issues.
✅ Summary: Service Health tells you the status of Azure services.
Definition: Resource groups are containers for related resources. Management groups are containers for multiple subscriptions.
Why important: They help you organise and manage access and policies.
Simple: Like folders and filing cabinets.
Real-life: A company has resource groups for each project and management groups for each department.
School: The school has a resource group for each subject.
Home: Not used at home.
Nigerian: A bank has management groups for branches.
Management Group
├── Subscription 1
│ ├── Resource Group A
│ └── Resource Group B
└── Subscription 2
├── Resource Group C
└── Resource Group D
✅ Summary: Resource groups and management groups help you organise Azure.
Definition: Best practices are the recommended ways to manage, monitor, and automate Azure effectively.
Why important: They help you stay organised, save time, and avoid issues.
Simple: Like a checklist for a clean and efficient Azure environment.
Real-life: A company follows all these practices to keep their Azure environment healthy.
School: The school follows these practices.
Home: Not used at home.
Nigerian: A startup follows these practices to scale.
Best Practices:
1. Use resource groups and tags.
2. Use ARM or Bicep for IaC.
3. Set up alerts for critical resources.
4. Use Azure Automation for repetitive tasks.
5. Monitor performance regularly.
✅ Summary: Following best practices helps you manage Azure effectively.
Azure Portal → Graphical (click)
Azure CLI → Command line (type)
Azure PowerShell → PowerShell (type)
Cloud Shell → Browser terminal
Code (ARM/Bicep) → Deploy → Azure Resources
Resources → Metrics/Logs → Azure Monitor → Alerts → Action Group
| Tool | User interface | Best for |
|---|---|---|
| Portal | Graphical | Visual, beginners |
| Azure CLI | Command line | Scripts, automation |
| PowerShell | Command line | Windows automation |
| Cloud Shell | Browser terminal | Quick tasks, any device |
| Tool | Language | Complexity |
|---|---|---|
| ARM Templates | JSON | Higher |
| Bicep | Bicep | Lower |
In this module, we learned about management, monitoring, and automation in Azure. We covered:
You now have the skills to manage, monitor, and automate your Azure environment. This is the final module of the intermediate course – you are ready to take your Azure skills to the next level!
Match the tool/service with its purpose.
| Tool/Service | Purpose |
|---|---|
| Azure Portal | Graphical management |
| Azure CLI | Command-line management |
| Cloud Shell | Browser terminal |
| ARM Template | Infrastructure as Code |
| Bicep | Simpler IaC |
| Azure Monitor | Collect performance data |
| Log Analytics | Query logs |
| Alert | Notify of issues |
| Azure Automation | Automate tasks |
| Logic Apps | Visual workflows |
Scenario 1: A Nigerian company wants to deploy the same environment in three regions. Which tool should they use?
Scenario 2: A school wants to get an email when the website is down. Which service should they use?
Scenario 3: A fintech wants to automatically stop VMs at 6 PM every day. Which service should they use?
In groups, design a management and monitoring plan for a Nigerian company. Include:
Write a simple ARM template or Bicep script to deploy a VM. Share it with the class.
Automation Plan: Create a plan for automating the deployment and management of a web application in Azure. Include Infrastructure as Code, monitoring, alerts, and automation.
If you have an Azure account, try the following:
Research how to create an Azure Automation runbook that stops a VM at a specific time. Write a simple guide.
Congratulations! 🎉 You have completed all four modules of the Azure Fundamentals – Intermediate course.
You are now ready to take the next step in your Azure journey. Here are some suggestions:
Good luck, future Azure expert! ☁️🚀
🏆 You have completed the intermediate course! Keep learning and exploring the cloud. 🌟