Browse Certification Practice Tests by Exam Family

Microsoft AZ-220 Cheat Sheet: Azure IoT Route

May 1, 2026

Review the retired Microsoft Azure IoT Developer (AZ-220) route, IoT Hub, device provisioning, IoT Edge, telemetry, security, monitoring, and current Azure developer or AI alternatives.

On this page

AZ-220 is a retired Azure IoT Developer route. Use this cheat sheet to preserve useful IoT concepts while choosing a current Azure developer, AI, or administrator route before studying.

Use this as a route check. Review the older IoT scope, then compare current Azure developer, AI, and administrator routes.

Open AZ-220 exam page Compare AZ-204

Exam snapshot

FieldDetail
IssuerMicrosoft
Retired routeAzure IoT Developer Specialty
Exam codeAZ-220
Current statusRetired exam guidance
Closest current choicesAZ-204, AI-103, AI-200, and AZ-104 depending on your role
IT Mastery statusExam-selection sample question page

Transition map

Older AZ-220 areaWhat still mattersCurrent-route trap
Device connectivityDevice identity, IoT Hub, protocols, telemetry, and command patternsStudying retired exam details instead of current development paths
Provisioning and managementEnrollment, lifecycle, configuration, and device twinsTreating device identity as an afterthought
Edge and integrationIoT Edge, stream processing, service integration, and data routingIgnoring cloud-side app and data architecture
SecurityDevice credentials, network boundaries, least privilege, monitoring, and updatesFocusing only on connectivity without device trust
Monitoring and troubleshootingTelemetry flow, connection state, routing, metrics, and alertsTroubleshooting the app before checking device and hub signals

Must-know distinctions

DistinctionHow to decide
IoT device vs cloud appDevice code and identity behave differently from backend app services.
Telemetry vs commandTelemetry flows device-to-cloud; commands and control messages flow cloud-to-device.
Device identity vs user identityDevices authenticate as devices; users authenticate through identity systems.
Edge processing vs cloud processingEdge processing handles local or low-latency work; cloud processing centralizes scale and integration.
Retired route vs current examAZ-220 content can inform IoT concepts, but current exam planning should use active routes.

High-yield checklist

  • Confirm that AZ-220 is not the exam you plan to schedule.
  • Map IoT development work to AZ-204 when your role is application development.
  • Map AI-enabled device or data scenarios to AI-103 or AI-200 when appropriate.
  • Keep device identity, provisioning, and credential lifecycle distinct from user identity.
  • Track telemetry from device through hub, routing, processing, and storage.
  • Include monitoring and update strategy in device fleets.

Common traps

  • Studying an unavailable route because the code still appears in old search results.
  • Confusing device authentication with user authentication.
  • Ignoring device provisioning and lifecycle.
  • Treating telemetry routing as the same thing as storage.
  • Troubleshooting cloud code before checking device connection and hub metrics.

Practice strategy

Use the AZ-220 exam page to check whether old IoT content still matches your goal. If your goal is general Azure development, move to AZ-204 ; if your goal is AI app development, compare AI-103 and AI-200 .

Revised on Monday, May 25, 2026