Study guide
Azure IoT and DevOps Services
Microsoft Azure Fundamentals AZ-900
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips
2 Domain 1: Cloud Concepts (25-30%)
1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model
3 Domain 2A: Azure Architecture Components
2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview
4 Domain 2B: Azure Compute Services
2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop
5 Domain 2C: Azure Networking Services
2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery
6 Domain 2D: Azure Storage Services
2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics
7 Domain 2E: Azure Identity, Access, and Security
2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services
8 Domain 3A: Azure Cost Management
3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization
9 Domain 3B: Azure Governance and Compliance
3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together
10 Domain 3C: Azure Monitoring and Management Tools
3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health
11 Additional Azure Services and Exam Review
Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice
12 Advanced Azure Topics and Service Deep Dives
Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans
Azure IoT and DevOps Services
Key Takeaways Explain This Topic AI
Azure IoT Hub is the PaaS message broker for secure two-way communication with millions of devices over MQTT, AMQP, or HTTPS.
Azure IoT Central is a fully managed SaaS app that delivers dashboards, device templates, and rules with no infrastructure to run.
Azure IoT Edge pushes cloud logic and AI onto devices so they keep working offline and process data locally.
Azure DevOps has five services: Repos (Git), Pipelines (CI/CD), Boards (Agile tracking), Artifacts (package feeds), and Test Plans.
GitHub Actions provides CI/CD inside GitHub; DevTest Labs gives cost-controlled dev/test environments with auto-shutdown.
Last updated: October 2026
Quick Answer: IoT Hub = PaaS device message broker (full control). IoT Central = SaaS IoT app (no code, no infrastructure). IoT Edge = run cloud logic on the device, even offline. Azure DevOps = Repos + Pipelines + Boards + Artifacts + Test Plans. GitHub Actions = CI/CD inside GitHub. DevTest Labs = managed dev/test sandboxes with cost caps.
The Azure IoT trio — and the one distinction that matters
IoT and DevOps services are not named in the July 20, 2026 AZ-900 skills outline, so treat this section as optional context. The key IoT distinction is IoT Hub (PaaS) vs. IoT Central (SaaS) . Read for the level of control and effort:
Service Cloud model Effort Choose when the scenario says...
IoT Hub PaaS High control, more setup "custom solution", "full control", "build my own dashboards/back end"
IoT Central SaaS Low/no code "fastest to deploy", "no infrastructure to manage", "built-in dashboards and rules"
IoT Edge Device runtime / extension Medium "process data on the device", "keep working offline", "reduce data sent to cloud"
Azure IoT Hub
Azure IoT Hub is the managed cloud gateway every device connects to. It supports device-to-cloud telemetry and cloud-to-device commands, per-device authentication (each device has its own identity and key), and millions of simultaneous connections. Supported protocols are MQTT , AMQP , and HTTPS . IoT Hub does not give you dashboards; you route its messages to Storage, Event Hubs, or Functions and build the rest yourself — which is exactly why it is the PaaS, full-control answer.
Azure IoT Central
Azure IoT Central is a finished SaaS application sitting on top of IoT Hub. You connect devices using device templates , get dashboards , rules and alerts , and user management without writing code or running servers. It is the answer whenever the priority is speed and simplicity over customization.
Azure IoT Edge
Azure IoT Edge deploys containerized modules — including trained AI models and Azure services — down onto the device. The device then filters, aggregates, or scores data locally and can keep operating while disconnected from the cloud. Pick it when the scenario stresses low latency , offline operation , or sending only summarized data upstream (saving bandwidth).
Worked example: A remote oil rig with intermittent connectivity must run anomaly detection on sensor data even when the satellite link drops. IoT Edge (running the model on-site) is correct; IoT Hub alone would stop scoring when offline.
Azure DevOps — the five services
Azure DevOps is Microsoft's suite for planning, building, testing, and shipping software. Memorize all five and what each does:
- Service Purpose
- Azure Repos Private, unlimited Git repositories for source control
- Azure Pipelines CI/CD to build, test, and deploy automatically
- Azure Boards Agile work tracking — Kanban boards, backlogs, sprints, work items
- Azure Artifacts Package feeds for NuGet, npm, Maven, and Python (pip)
- Azure Test Plans Planned and exploratory manual + automated testing
Trap: Pipelines is the CI/CD answer, not Repos. Repos only stores code; Pipelines does the automated build-test-deploy. Distractors often swap these.
GitHub and Azure
Microsoft owns GitHub, so Azure integrates tightly with it:
GitHub Actions — workflow-based CI/CD that can deploy straight to Azure; the GitHub-native counterpart to Azure Pipelines.
GitHub Advanced Security — code scanning, secret scanning, and dependency review.
GitHub Codespaces — cloud-hosted development environments in the browser.
A common scenario mixes them: teams keep code in GitHub and run releases through Azure Pipelines or GitHub Actions — both are valid CI/CD choices.
Why the PaaS-vs-SaaS framing keeps appearing
The IoT services are a clean illustration of the cloud service models you learned in Domain 1. IoT Hub is PaaS : Microsoft runs the broker, but you assemble the rest of the solution — storage, analytics, dashboards — yourself, trading effort for control. IoT Central is SaaS : Microsoft runs the entire application and you only configure it, trading control for speed. When a stem emphasizes least administrative effort or fastest time to value , the SaaS answer (IoT Central) wins; when it emphasizes full customization or integrating with my own back end , the PaaS answer (IoT Hub) wins.
Note too that IoT Central is built on top of IoT Hub, so they are complementary, not competitors.
The same effort-versus-control lens applies to the developer tooling. Azure DevOps and GitHub overlap heavily. Both can host code and run CI/CD; Azure DevOps adds project-management features through Boards and Test Plans. Many real teams combine them — code in GitHub, releases through Azure Pipelines or GitHub Actions.
Do not over-think it: if the choice is purely CI/CD automation , either Pipelines or GitHub Actions is correct, and Repos is never the CI/CD answer.
Azure DevTest Labs
Azure DevTest Labs spins up cost-controlled dev/test environments. Key features:
Auto-shutdown schedules to stop VMs after hours (cuts cost).
Cost limits and quotas per lab.
Claimable VMs pre-provisioned and ready for any developer to grab.
Custom images and formulas so every new VM starts with the right tools.
Study note: For IoT, the key decision is PaaS control ( IoT Hub ) vs. SaaS simplicity ( IoT Central ), with IoT Edge for offline/local processing. For DevOps, recall the five services and that Pipelines (or GitHub Actions) is CI/CD, while Repos is just source control.