Azure IoT Developer (AZ-220) study plan

Azure IoT Developer (AZ-220) · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Set up the Azure IoT Hub solution infrastructure & Provision and manage devices

Map every IoT Hub tier and scaling limit (device-to-cloud and cloud-to-device throughput, message size, retention) to a written sizing table
Create an IoT Hub with the CLI or portal and configure a shared access policy scoped to only the permissions a backend service needs
Register 10 simulated devices using individual connection strings and one group enrollment via DPS, then compare the two provisioning flows
Configure a custom allocation policy in DPS and explain when custom versus hashed allocation is appropriate

A one-page sizing and provisioning decision document plus a working hub with 10 devices registered through DPS

Week 2

Implement device twin tags and desired properties from a backend app and confirm reported properties flow back
Build direct method invocations from the service side with a timeout and handle the device-side response
Configure file upload from a device through a storage account and verify the notification arrives on the service endpoint
Set up message routing to a built-in endpoint with a query filter and prove non-matching messages are excluded

A demo repo where a simulated device reports telemetry, receives a direct method, and uploads a file, with routing filters verified by log output

Week 3

Install and initialize IoT Edge on a Linux VM and register the device identity through DPS
Deploy a custom module from a container registry and confirm module-to-module communication over the Edge hub
Configure a module twin's desired properties and force a configuration refresh to prove the reported state updates
Set the Edge hub store-and-forward time-to-live and explain the offline behavior it produces

A running Edge device with two custom modules exchanging messages and a documented offline store-and-forward test result

Week 4

Create a layered deployment with a base configuration and a deployment manifest targeted by device twin tag
Implement an Edge module that buffers telemetry locally and forwards it when connectivity returns
Debug an Edge module using the runtime logs and module logs to isolate a startup failure
Verify Edge hub routes and priorities by tracing a message through two competing routes

A layered deployment applied to two devices with different tags, plus a written root-cause note from a deliberately broken module

Week 5

Route telemetry to Blob Storage, Event Hubs, and a Service Bus queue and compare the message format at each endpoint
Enrich routed messages with a custom application property and filter on it in a route query
Build an Azure Function that reacts to the Event Grid device lifecycle events for device creation and deletion
Configure an Event Grid subscription on the hub and validate end-to-end delivery with a test device

A working pipeline from device telemetry to blob storage with enrichment, plus a Function triggered by a device-created event

Week 6

Implement a Stream Analytics job that aggregates telemetry over a tumbling window and writes results to a downstream sink
Integrate IoT Hub with Logic Apps to send an alert when a threshold is breached
Handle duplicate and out-of-order messages in a stream processing query and explain the tradeoffs
Compare built-in endpoints, routing, and Event Hubs-compatible endpoints for a given throughput scenario

An end-to-end analytics flow that aggregates telemetry in a window and fires a Logic App alert on a threshold breach

Week 7

Configure diagnostic settings to send IoT Hub logs and metrics to Log Analytics and write a query for connection errors
Create metric alerts for throttling and device disconnect spikes and test each alert threshold
Enable Microsoft Defender for IoT and review a security recommendation for a simulated device
Apply a device-level SAS token rotation policy and verify an expired token is rejected

A monitoring workbook or saved query set with two tested alerts and a documented SAS rotation procedure

Week 8

Enforce a private endpoint for IoT Hub and confirm public access is blocked for a test client
Trace a failed device connection using logs and metrics and document the diagnosis steps
Complete a timed practice set weighted by domain percentage and review every missed item
Build a one-page reference of limits, quotas, and security defaults for final review

A timed practice run score with a written remediation list and a final one-page limits and security cheat sheet

Week 2: Can provision a device through DPS and demonstrate twin, method, and file upload flows without notes

Week 4: Can deploy a layered Edge configuration and diagnose a module startup failure from logs

Week 6: Can route enriched telemetry to two endpoint types and aggregate it in a streaming job

Week 8: Scores at or above 80 percent on a timed mixed-domain practice set with security and monitoring items reviewed