AZ-220 Microsoft Azure IoT Developer Exam Guide: Skills, Retirement, and Practical Next Steps
AZ-220 validated the ability to build and maintain the cloud and device sides of Azure IoT solutions, including connectivity, device management, edge workloads, data handling, monitoring, and security. It was intended for Azure IoT developers who could also program with an Azure IoT SDK-supported language. The exam retired on July 31, 2023, so the key decision today is whether to use its outline for structured IoT learning or pursue a currently available credential instead of trying to schedule AZ-220.
Can you still take AZ-220?
No. Microsoft states that Exam AZ-220: Microsoft Azure IoT Developer retired on July 31, 2023. Candidates cannot schedule or take a retired exam, and they cannot earn its associated certification after retirement. Treat any page advertising a current AZ-220 appointment, guaranteed result, or active exam delivery as requiring independent verification rather than as evidence of availability.
The retirement applies to the exam and the Microsoft Certified: Azure IoT Developer Specialty certification for which AZ-220 was part of the requirements. Microsoft’s retirement policy explains that retired exams and associated credentials cannot be earned after the retirement date, while certifications already earned remain on the learner’s Microsoft Learn transcript.
This changes the purpose of preparation. A candidate should not purchase material on the assumption that a booking is possible. The useful reason to study AZ-220 content now is to build an Azure IoT skills checklist, support work on an existing solution, or identify the technical area that a current certification or Applied Skills credential should cover.
What did AZ-220 validate?
AZ-220 assessed the practical responsibilities of an Azure IoT developer: creating and maintaining the cloud and device portions of an IoT solution, configuring and maintaining devices through cloud services, setting up physical devices, and troubleshooting configurations throughout the device lifecycle.
The role also covered implementing design specifications for device topology, connectivity, diagnostics, monitoring, and security. Developers were expected to create code for two-way device-to-cloud communication, develop and deploy modules, configure device networking for Azure IoT Edge, and help manage IoT data streams and transformation.
This was not a narrow device-programming test. The published audience profile described collaboration with architects, device developers, data engineers, and other stakeholders for business integration. Candidates were also expected to understand device types, Azure data storage, data analysis, data processing, AI, and other platform as a service options.
Programming was part of the expected background. Microsoft stated that candidates needed to program in at least one language supported by an Azure IoT SDK. That requirement makes passive reading a weak preparation method for the original objectives: a learner should be able to explain a design and implement a small working flow in a supported development language.
Which skills were measured?
The latest published outline, identified as skills measured as of January 30, 2023, divided AZ-220 into seven domains. Use that dated version when studying historical objectives; the study guide also contains an earlier version, so mixing the two lists can create an inaccurate checklist.
Set up the Azure IoT Hub solution infrastructure covered 15–20% of the exam. Provision and manage devices covered 15–20% of the exam. These domains establish the foundation: the learner must connect the service architecture to device identity, lifecycle management, and reliable communication decisions.
Implement IoT Edge covered 20–25% of the exam, making it the largest listed domain. Give this area deliberate attention when using the blueprint for learning, especially if your practical work involves deploying workloads away from the central cloud.
Implement business integration covered 5–10% of the exam. Process and manage data covered 10–15% of the exam. The two domains point to the boundary between device-originated information, downstream business systems, processing, and useful data outputs.
Monitor, troubleshoot, and optimize IoT solutions covered 10–15% of the exam. Implement security covered 10–15% of the exam. Do not treat those as optional finishing topics: operational diagnosis and protection were explicit parts of the role the exam was designed to assess.
How should the percentages affect study time?
Use the weights to set priority, not to predict a question count or a passing result. Start with the three largest areas—Implement IoT Edge at 20–25% of the exam, Set up the Azure IoT Hub solution infrastructure at 15–20% of the exam, and Provision and manage devices at 15–20% of the exam—then cover every remaining domain.
The blueprint is a coverage map rather than permission to ignore smaller domains. Business integration was weighted at 5–10% of the exam, but a weak understanding there can still expose gaps in the end-to-end design. A sensible sequence is foundation, devices, edge, data and integration, then operations and security, with a final review across all seven domains.
What background should an IoT learner build first?
Before working through the historical blueprint, establish enough Azure and programming knowledge to follow a device-to-cloud solution from hardware through services and data consumers. Microsoft’s audience profile assumes familiarity with device types, Azure platform services, data storage, data analysis, data processing, AI, and at least one Azure IoT SDK-supported programming language.
A practical starting exercise is to draw one complete flow on paper: a device produces telemetry, a cloud service receives it, another component processes or stores it, and an operator or business system consumes the result. Label identity, connectivity, data movement, monitoring, and security on the diagram. Then use the seven AZ-220 domains to locate what you do not yet understand.
Do not spend the first phase memorizing service names without building relationships between them. For each service or capability in your notes, record the problem it solves, what data or identity it handles, where it runs, and what failure or security concern it introduces. This creates decision-making practice rather than a disconnected glossary.
How can you turn the outline into hands-on practice?
Convert every domain into an observable task or explanation. The goal is not to reproduce old exam questions; it is to demonstrate that you understand how an IoT solution is assembled, operated, and protected. Keep a short lab record containing the design choice, the implementation step, the result, and the failure you investigated.
For Set up the Azure IoT Hub solution infrastructure, practice describing the role of the hub in an IoT architecture and the communication path between devices and cloud services. For Provision and manage devices, trace how a device is introduced, maintained, and removed over its lifecycle. Your notes should distinguish device identity and device configuration rather than treating registration as the whole management problem.
For Implement IoT Edge, compare cloud-only processing with processing closer to the device. Document what a module does, how it is deployed, how it communicates with other components, and what happens when connectivity is limited. The edge domain was the largest listed domain, so it deserves a complete design narrative rather than a brief terminology review.
For Process and manage data and Implement business integration, follow telemetry beyond ingestion. Identify where transformation occurs, where data is stored or analyzed, and how another system would use the output. For Monitor, troubleshoot, and optimize IoT solutions, write a fault path: what symptom appears, which signal you inspect, and how you separate device, network, service, and application causes.
For Implement security, review the complete trust boundary. Ask how identities are established, how communication is protected, how access is controlled, and how a compromised or decommissioned device is handled. Keep security decisions beside each lab rather than postponing them to a final reading session.
What study sequence is most efficient?
Study in dependency order: understand the solution architecture, establish IoT Hub foundations, work through device provisioning and management, build the edge portion, follow data into business integration, and then test monitoring, optimization, and security across the whole design. This order reduces the risk of learning isolated features without understanding where they belong.
Phase one is an orientation pass through the latest dated skills outline. Mark each objective as familiar, explainable, or untested. Do not use the older pre-January 30, 2023 list as your primary checklist when your purpose is to understand the later blueprint; Microsoft explicitly provides separate versions based on the exam date.
Phase two is implementation. Choose a small, coherent scenario and use it to connect the domains. A useful scenario can include device telemetry, cloud communication, an edge processing requirement, a downstream data consumer, operational signals, and a security boundary. The scenario is a study device, not a claim about what appeared on the retired exam.
Phase three is diagnosis. Revisit each design choice and ask what would change if the device were intermittently connected, if processing had to occur locally, if the data had different sensitivity, or if the device lifecycle ended. Explain the answer aloud or in writing without consulting notes, then verify terminology against the official outline.
Phase four is consolidation. Create one page per domain with its purpose, key relationships, implementation evidence, and unresolved questions. Review the heaviest domains more often, but require yourself to produce an answer for every domain before considering the historical syllabus covered.
What should a four-week roadmap look like?
A four-week plan works best when each week produces evidence of capability rather than only completed reading. Adjust the pace to your existing Azure and programming background, but preserve the order: map the objectives, build the core flow, extend it to edge and data, and finish with cross-domain troubleshooting and security review.
Week one: read the latest skills-measured section and create the seven-domain checklist. Study the intended role and sketch an end-to-end IoT solution. Confirm that you can explain device-to-cloud and cloud-to-device responsibilities at a conceptual level, and identify the Azure IoT SDK-supported language you will use for practice.
Week two: concentrate on Set up the Azure IoT Hub solution infrastructure and Provision and manage devices. Implement or document a small device lifecycle flow, then test your understanding by explaining how identity, communication, configuration, and retirement relate to one another. Record questions that require product documentation rather than guessing from memory.
Week three: give priority to Implement IoT Edge, then connect it to Process and manage data and Implement business integration. Produce a design that states what runs on the device, what runs at the edge, what runs in cloud services, and where processed information goes. The point is to make placement and data-flow decisions explicit.
Week four: cover Monitor, troubleshoot, and optimize IoT solutions and Implement security, then perform a complete review. Use failure scenarios and threat questions to test the earlier work. Finish by checking every line of the latest outline, not by relying on a practice score or a collection of remembered answers.
Which mistakes weaken preparation?
The largest mistake is preparing to schedule a retired exam. Verify status on Microsoft Learn before spending money or time on a booking. A current-looking third-party listing does not override Microsoft’s stated retirement date, and no collection of memorized questions can create a valid appointment or guarantee a result.
A second mistake is studying only the largest blueprint domain. Implement IoT Edge was weighted at 20–25% of the exam, but the exam also measured infrastructure, device management, integration, data, operations, and security. Use the percentages to prioritize effort while still completing a pass through every domain.
A third mistake is treating the device as a simple message sender. The published role included physical-device setup, configuration maintenance, lifecycle troubleshooting, topology, connectivity, diagnostics, monitoring, and security. Your preparation should therefore include operational and architectural reasoning, not only code that sends telemetry.
A fourth mistake is confusing product familiarity with implementation ability. Reading about an Azure service may help you recognize terminology, but it does not show that you can choose where a function belongs or diagnose a broken flow. Pair each study topic with a diagram, a lab, a written procedure, or a failure analysis.
Finally, avoid mixing dated objectives without labeling them. Microsoft’s study guide includes skills measured before January 30, 2023 and skills measured as of January 30, 2023. Keep the later list as the primary historical reference and note any older material separately so that outdated emphasis does not silently shape your plan.
What were the official exam logistics?
The published logistics are historical because AZ-220 is retired. Microsoft listed the exam languages as English, Japanese, Korean, French, Spanish, Portuguese (Brazil), Chinese (Simplified), Italian, German, and Chinese (Traditional). The study guide stated that a candidate could request an additional 30 minutes if the exam was not available in the preferred language.
The study guide listed a passing score of 700 or greater. That figure belongs to the retired exam’s published requirements; it should not be used as a current registration promise or as evidence that a particular practice result predicts certification.
Microsoft listed the price as based on the country or region where the exam was proctored. Because the exam is retired, there is no responsible current price to quote for AZ-220. Candidates researching a different, active credential should verify its fee and delivery conditions on that credential’s current official page.
The exam page recommended registering with a personal Microsoft account because records associated with an organizational work or school account could be lost and unrecoverable if the candidate left that organization. This is useful historical account guidance, but it does not make AZ-220 schedulable today.
The official study guide also referenced an exam sandbox, accommodations, practice testing, and a Microsoft Learn profile for scheduling and managing credentials. Those resources explain Microsoft’s former preparation and administration process; they should not be interpreted as confirmation that a retired AZ-220 appointment can be created.
What should you use instead of a retired AZ-220 booking?
Choose the next credential from your intended role, not from the retired exam code. The supplied official exam page lists no related exams for AZ-220, and the retirement policy says that a retired exam cannot be taken or used to earn its associated certification. Use current Microsoft Learn credential pages to verify any alternative before committing to it.
If your goal is IoT engineering, retain the AZ-220 outline as a technical study plan and pair it with current Azure IoT documentation and learning content. Microsoft Q&A material indicates that IoT-related learning modules remained available in some cases, while the course-retirement page warns that retired course pages can eventually be removed and recommends saving useful learning paths and modules to personal collections.
If your work is primarily data engineering, cloud operations, AI, device certification, or security, select a current credential whose published audience and skills match that role. Do not describe another certification as an official AZ-220 replacement unless Microsoft’s current credential page explicitly does so. The Q&A discussions supplied here do not establish a single replacement exam for every IoT developer.
A practical decision rule is simple: first identify the work you want to perform, then compare that work with the current credential’s official skills. If the target role spans device and cloud responsibilities, keep the historical AZ-220 domains as a learning map while validating the current assessment separately.
How should you use old AZ-220 resources safely?
Old courses, notes, and community explanations can help explain concepts, but they should be treated as dated study aids rather than proof of current Azure behavior or an active exam syllabus. Anchor your notes to Microsoft’s latest published AZ-220 outline and label material that predates January 30, 2023.
Save useful Microsoft Learn paths or modules to a personal collection when available. Microsoft’s course-retirement guidance says that learning paths and modules may remain available after associated course content changes, and saving them helps preserve access until they are finally retired. This protects your study plan from depending on a page that may later disappear.
Check product documentation separately when performing hands-on work. Azure services change, and a historical exam objective can describe a role without guaranteeing that every interface, command, feature name, or recommended architecture remains current. For current implementation decisions, prefer current official service documentation over an old exam-preparation summary.
Do not use dumps, leaked questions, or answer memorization as a substitute for skill. They cannot restore a retired exam, validate a present-day design, or establish that you understand device lifecycle, edge deployment, data movement, operations, and security. Build your own explanation and implementation evidence instead.
What should you do next?
Start by stopping any AZ-220 purchase or scheduling process and confirm the retirement notice on Microsoft Learn. Then decide whether your objective is historical exam study, practical Azure IoT capability, or a current credential. That decision determines whether you need a domain-by-domain learning plan, a current certification comparison, or both.
For a learning plan, download or save the latest skills outline, create the seven-domain checklist, and rank your gaps. Give special attention to Implement IoT Edge at 20–25% of the exam, while preserving coverage of every other labeled domain. Select one supported programming language and build a small end-to-end practice scenario.
For a credential decision, write down the role you want next and the work it involves: device setup, cloud configuration, edge development, data engineering, operations, AI, or security. Review current Microsoft credential pages against that list, and verify status, prerequisites, delivery, languages, and pricing there because those details can change.
For a final knowledge check, explain one complete IoT design without notes. Include device identity and communication, cloud and edge responsibilities, data flow, business integration, monitoring and troubleshooting, and security. Any part you cannot explain becomes the next study task—not a reason to rely on exam dumps or unsupported claims.
Conclusion
AZ-220 remains useful as a map of Azure IoT developer responsibilities, but it is not a current exam option. Its published blueprint covered infrastructure, devices, IoT Edge, integration, data, operations, and security, with IoT Edge as the largest domain. Use that structure for disciplined technical practice, then verify a current credential against your target role on Microsoft Learn before making a scheduling or purchasing decision.
Related exams
- AZ-104 exam — Microsoft Azure Administrator
- AZ-120 exam — Planning and Administering Microsoft Azure for SAP Workloads
- AZ-140 exam — Configuring and Operating Windows Virtual Desktop on Microsoft Azure
- AZ-305 exam — Designing Microsoft Azure Infrastructure Solutions
- AZ-400 exam — Microsoft Azure DevOps Solutions
- AZ-500 exam — Microsoft Azure Security Technologies
