AZ-220 Microsoft Azure IoT Developer: Skills, Retirement Status, and Practical Study Guide
AZ-220 validated the ability to build and maintain the cloud and device sides of an Azure IoT solution, including provisioning, two-way communication, IoT Edge, data handling, monitoring, and security. It was designed for Azure IoT developers who could program with an Azure IoT SDK-supported language and work across physical devices, cloud services, and solution stakeholders. The first decision for a reader now is not which AZ-220 date to book: Microsoft states that the exam retired on July 31, 2023. This guide helps you decide whether to preserve its skills as a learning roadmap or redirect preparation to a current credential.
Can you still take AZ-220?
No. Microsoft states that Exam AZ-220: Microsoft Azure IoT Developer retired on July 31, 2023. Under Microsoft’s retirement policy, candidates cannot take a retired exam or earn its associated certification after retirement. Treat any page suggesting that you can schedule a new AZ-220 attempt as outdated until Microsoft’s own certification pages say otherwise.
The retirement changes the purpose of this guide. It is useful for understanding the former Azure IoT Developer Specialty skill set, planning hands-on IoT training, reviewing legacy project requirements, or deciding which adjacent Azure capability to study next. It is not a current registration guide and cannot provide a valid route to an AZ-220 result.
Microsoft also says that certifications already earned remain on a learner’s transcript after retirement. That distinction matters when reviewing a résumé or transcript: a previously earned credential is not the same as an exam that is still available to new candidates.
What role did AZ-220 measure?
AZ-220 was aimed at Azure IoT developers who created and maintained both the cloud and device portions of an IoT solution. The role extended beyond writing device code: it included configuring physical devices, maintaining them through their lifecycle, implementing connectivity and topology, diagnosing failures, monitoring solutions, and applying security controls.
The official profile expected candidates to work with architects, device developers, data engineers, and other stakeholders. That makes the historical exam broader than a service-name quiz. A serious study plan needs to connect device behavior to cloud ingestion, data processing, business integration, operational monitoring, and security decisions.
Microsoft also expected a general understanding of device types and Azure services for data storage, data analysis, data processing, AI, and other platform as a service options. Candidates were required to program in at least one language supported by an Azure IoT SDK. If those foundations are missing, begin with programming and Azure fundamentals before attempting the more integrated labs.
Who would have benefited most?
The exam best matched developers responsible for an IoT solution across its device and cloud boundary. It also provided a useful capability checklist for engineers moving from device development toward Azure operations, edge deployment, data pipelines, or solution integration.
It was less suitable as a narrow introduction to Azure or as a substitute for embedded-systems training. The published role included physical-device setup and lifecycle troubleshooting, while the measured skills also reached into cloud architecture and downstream data services.
Which skills were measured?
The later official outline, identified as skills measured as of January 30, 2023, divided AZ-220 into seven domains. Use that later outline when studying the historical skill set; the study guide also contains an earlier version, so mixing objectives from both lists can produce a confusing checklist.
The seven domains were Set up the Azure IoT Hub solution infrastructure; Provision and manage devices; Implement IoT Edge; Implement business integration; Process and manage data; Monitor, troubleshoot, and optimize IoT solutions; and Implement security. The exam page lists no related exams for AZ-220.
The domain weights describe the historical assessment emphasis, not a current exam allocation. Implementing IoT Edge was weighted at 20–25% of the exam, making it the largest listed domain. Set up the Azure IoT Hub solution infrastructure was weighted at 15–20% of the exam, and Provision and manage devices was weighted at 15–20% of the exam.
Implement business integration was weighted at 5–10% of the exam. Process and manage data was weighted at 10–15% of the exam, Monitor, troubleshoot, and optimize IoT solutions was weighted at 10–15% of the exam, and Implement security was weighted at 10–15% of the exam. Always keep each percentage attached to its domain when using the outline for study planning.
How should you interpret the weights?
Use the percentages to allocate attention, not to skip lower-weight domains. A business-integration topic may occupy less of the historical blueprint while still connecting the device workflow to the organization’s actual application. Likewise, security and monitoring are cross-cutting concerns that can affect nearly every implementation decision.
A practical approach is to study the domains in dependency order, then revisit them in weight order. Build the IoT Hub and device-management foundation first, add edge deployment, connect data and business services, and finish with deliberate monitoring, troubleshooting, optimization, and security reviews.
What belongs in the IoT Hub foundation?
Start by being able to explain how an IoT Hub solution is structured and how a device exchanges information with the cloud. The foundation domain covered infrastructure, device communication, topology, connectivity, diagnostics, and capabilities such as IoT Plug and Play.
Build one small reference solution rather than reading service descriptions in isolation. Register a device, establish device-to-cloud and cloud-to-device communication, inspect the device identity and twin, and document why a chosen protocol, gateway arrangement, or networking pattern fits the scenario.
Include file upload, message-size considerations, TLS server certificates, and IoT Hub scaling concepts in the review. The aim is not to memorize isolated configuration labels. It is to understand what each mechanism changes in communication, reliability, security, or operational cost, and what evidence would show that the configuration works.
A useful study note has four columns: requirement, Azure capability, configuration action, and verification method. For example, a requirement for two-way telemetry and commands should identify the relevant communication flow, the code or service configuration involved, and the observable result that confirms both directions function.
How should you study device provisioning and lifecycle management?
Separate initial provisioning from ongoing management. Device Provisioning Service addresses how devices are assigned and registered, while IoT Hub device identities, twins, modules, and management features support operation after enrollment. Keeping those stages distinct prevents a common mistake: treating registration as the whole device lifecycle.
Practice creating a provisioning workflow with Device Provisioning Service, configuring enrollments, linking provisioning to IoT hubs, and tracing the resulting device identity. Then review deprovisioning, automatic enrollment behavior, and device decommissioning. Write down what happens to identity, configuration, and operational ownership at each transition.
The domain also included IoT Hub device registry work, device-twin tags and properties, Automatic Device Management, module identities, and module twins. Test how desired and reported state differ, how a configuration change is represented, and how you would determine whether a device has applied that change.
Do not overlook Azure IoT Central. The historical objectives included device templates using DTDL, rules, actions, commands, device enrollment, application management, tenants, customization, visualizations, data integration, jobs, and APIs. Study IoT Central as an application-management surface with its own abstractions, not simply as another screen for IoT Hub.
A practical provisioning exercise
Use a disposable environment and record the complete path from enrollment to usable device. Confirm the hub association, identity creation, twin state, and first successful message. Repeat the exercise for a lifecycle change such as deprovisioning or replacement, then explain which records must be removed or updated.
If you cannot run the services, produce a sequence diagram and configuration checklist from the official objectives. Mark every step that you have only read about. That distinction keeps confidence aligned with demonstrated ability.
Why was IoT Edge the largest domain?
Implementing IoT Edge was weighted at 20–25% of the exam and covered the full path from device setup to module deployment, networking, certificates, offline operation, and gateway hierarchies. Give this domain the deepest hands-on treatment because it combines Azure configuration, containers, deployment manifests, and edge-specific operational constraints.
Practice creating an IoT Edge device identity, configuring the device, installing or understanding the container runtime, setting startup options, updating the runtime, and provisioning through Device Provisioning Service. Then deploy a standard or custom module and verify its status, logs, routing, and interaction with the edge runtime.
The objectives included creating deployment manifests, targeting one or multiple devices, and creating continuous deployments using Azure DevOps. Review how desired deployment configuration is expressed, how a target is selected, and how you would detect drift or a failed rollout. A deployment that exists in a registry but never reaches the target is not a successful implementation.
For custom modules, study development and customization, module configuration, routing, development-environment setup, and publishing images to Azure Container Registry. Connect each step to a verification check: image availability, pull authorization, module startup, route behavior, and cloud forwarding.
Finally, cover gateway patterns, IoT Edge gateway deployment, certificates, local storage for offline support, layered hierarchies, and interaction with the IoT Edge security manager. Edge architecture is not merely cloud deployment at a smaller scale; network interruption, trust, storage, and local processing change the design.
The edge mistakes that waste study time
A frequent preparation error is practicing only the happy path: deploy a module while connected, confirm one message, and stop. Add failure cases to the lab. Examine what happens when an image is unavailable, a route is wrong, a certificate is invalid, or the device cannot reach the cloud.
Another mistake is memorizing manifest syntax without understanding module roles and routes. For every manifest you create, explain which module produces data, which module consumes it, where messages are sent, and how the deployment behaves during an outage.
How do business integration and data skills fit together?
Treat business integration as the handoff between IoT telemetry and the systems that use it. Treat data processing as the movement, transformation, storage, and analysis of that information. Studying these domains together makes the architecture easier to reason about while preserving their distinct responsibilities.
The historical business-integration domain was weighted at 5–10% of the exam. Although it had the smallest listed range, it represented an important design question: how does an IoT solution connect to upstream and downstream business systems? Map the device event through ingestion, processing, storage or analysis, and the business action that follows.
For data preparation, draw separate paths for telemetry, device state, commands, and operational logs. Identify where transformation occurs, where data is retained, and which component consumes the result. This exercise helps prevent a common error—choosing a service because it can receive data without explaining how the data becomes useful or manageable.
The official profile referred to data storage, data analysis, data processing, AI, and other PaaS options. Review those categories at an architectural level, then connect them to the IoT services and integration patterns named in the objective list. Avoid claiming that one service is always the correct destination; the right design depends on the workload requirement stated in the scenario.
A useful architecture exercise
Take one fictional industrial telemetry flow and document it from sensor to business consumer. Record the message contract, ingestion point, transformation, storage or analysis destination, failure behavior, and security boundary. Then change one constraint—such as intermittent connectivity or a need for edge decisions—and revise the design.
This exercise is more valuable than copying a diagram because it forces you to justify service boundaries. It also exposes gaps in knowledge: if you cannot state where a message is transformed or how a downstream system receives it, return to that objective before moving on.
How should you prepare for monitoring and troubleshooting?
Study troubleshooting as a lifecycle discipline, not as a list of portal blades. The historical domain covered monitoring, troubleshooting, and optimization of IoT solutions, so your preparation should trace failures across device code, identity, network, hub communication, edge modules, routes, and downstream processing.
Create a fault-isolation matrix. For a missing telemetry message, list checks in order: is the device running, is it authenticated, is it connected, is the message accepted, is the route valid, is the receiving component healthy, and is the data visible in the intended destination? Record the evidence each check should produce.
Include operational signals for device connectivity, message flow, module health, deployment state, and resource behavior. Then practice deciding whether the remedy is a configuration change, a code change, a retry or buffering strategy, a capacity adjustment, or a security correction. Optimization without a measured bottleneck is guesswork.
Use the official objective bullets as a test of action. For each one, write a short incident scenario and a response procedure. The finished notes should tell you what to inspect first, what conclusion each observation supports, and what change you would validate afterward.
What security decisions should be explicit?
Security was a dedicated AZ-220 domain and also appeared throughout provisioning, certificates, networking, device management, and edge deployment. Prepare to explain identity, authentication, authorization, certificate handling, secure communication, and operational trust rather than treating security as a final checklist.
For each reference architecture, mark the identity of the device, the identity of the operator or deployment process, the identity used to pull module images, and the identities involved in downstream integration. Then document what each identity is allowed to do and how a compromise or expired credential would be detected and corrected.
Connect TLS server certificates and IoT Edge certificates to the communication path they protect. Connect Device Provisioning Service and device identities to onboarding and lifecycle control. Connect registry or deployment permissions to the ability to distribute modules. This mapping makes security choices concrete and helps distinguish device authentication from authorization to perform an action.
Avoid broad claims such as “the solution is secure” in study notes. Replace them with verifiable statements: which party authenticates, which resource authorizes the operation, where secrets or certificates are managed, and what happens when trust material is rotated or revoked.
What study order works best?
Use a build-and-break sequence: establish the hub foundation, provision a device, manage its state, deploy an edge module, connect data to an application path, introduce an operational fault, and then harden the solution. This order follows the dependencies between the historical domains and gives every reading task a practical anchor.
Do not begin with practice questions or memorized answers. The official skills outline is the controlling checklist, while hands-on implementation is the best way to test whether you can perform the underlying work. Practice material may help reveal weak areas, but it cannot replace understanding and should never be based on leaked or unauthorized exam content.
Keep a decision log for each lab. Note the requirement, the selected capability, the configuration, the expected result, the observed result, and the correction when the result differs. Review the log weekly and convert recurring errors into targeted exercises.
A four-phase roadmap
Phase one is foundation and communication. Review the later skills-measured list, learn the IoT Hub architecture, register a device, implement two-way communication, inspect twins, and document connectivity and topology choices. Finish only when you can explain the message path without relying on a diagram copied from a course.
Phase two is provisioning and management. Work through Device Provisioning Service, enrollments, hub linking, lifecycle changes, device registry operations, twins, modules, and Automatic Device Management. Add the IoT Central objectives separately so that its templates, DTDL, rules, jobs, APIs, and tenant concepts do not disappear inside an IoT Hub checklist.
Phase three is edge delivery. Configure an IoT Edge device, deploy modules, publish a custom image to Azure Container Registry, create routes, review continuous deployment, and test offline support, certificates, gateway patterns, and layered hierarchies. Keep deployment configuration under version control in your own practice project.
Phase four is integration and operations. Trace data into processing, storage, analysis, or business systems; add monitoring and troubleshooting scenarios; and perform a security review. Revisit every objective and classify it as demonstrated, explainable, or unverified. Spend the final study time on unverified items and on failures you have not yet diagnosed.
How can you turn the roadmap into weekly actions?
Assign each session one observable outcome rather than a vague topic. Examples include “trace a provisioned device into the correct hub,” “explain the difference between twin desired and reported state,” or “diagnose why an edge module is running but its route produces no cloud message.” Small outcomes make progress measurable without pretending that reading time predicts competence.
At the end of a study block, close the documentation and reconstruct the workflow from memory. Then perform it again in the lab or compare your design with the official objective bullets. This exposes recognition without recall—the situation in which a learner understands a page while reading it but cannot implement the capability independently.
Reserve a review block for cross-domain scenarios. A device may be provisioned correctly but unable to communicate because of identity or certificate problems; an edge deployment may succeed while its route or offline storage behavior fails; telemetry may arrive while downstream transformation is incorrect. These combinations are where isolated memorization breaks down.
What should you verify before treating yourself as ready?
Readiness for the historical AZ-220 skill set means you can explain and demonstrate the main workflows, not merely recognize Azure product names. Use the later official outline as a final audit, and require evidence for each domain: a working configuration, a clear design explanation, or a documented troubleshooting procedure.
A strong final review includes one end-to-end architecture, one provisioning and lifecycle walkthrough, one edge deployment, one data and business-integration flow, one incident investigation, and one security threat or failure analysis. Keep the examples small enough to rebuild, but varied enough to expose assumptions about connectivity, identity, deployment, and data flow.
Microsoft’s study guide recorded a passing score of 700 or greater for the exam when it was active. That historical fact does not create a current AZ-220 opportunity, and it should not be used as a target for unofficial score claims. Since the exam is retired, readiness is better judged by demonstrated capability and by the current credential or role requirement you select next.
Signs your plan needs correction
If your notes contain mostly definitions and no verification steps, add labs. If you can deploy a device but cannot explain its identity and lifecycle, return to provisioning. If you can send telemetry but cannot locate a broken route or module, practice troubleshooting. If you focus on IoT Edge while ignoring business integration, data, monitoring, or security, rebalance against the full outline.
Do not use exam dumps, leaked questions, or memorized answer keys as a substitute for implementation. They provide no reliable basis for current technology decisions, may contain unauthorized material, and cannot establish that you can build or operate an IoT solution.
What are the delivery details worth preserving?
The archived exam page listed English, Japanese, Korean, French, Spanish, Portuguese (Brazil), Chinese (Simplified), Italian, German, and Chinese (Traditional) as exam languages. It also stated that price depended on the country or region where the exam was proctored. These are historical page details, not current scheduling information.
The study guide described an exam sandbox, accommodation requests, a practice-test option, and profile functions for scheduling and managing certification records when the exam was available. It also advised connecting a certification profile to Microsoft Learn and recommended a personal Microsoft account because records tied to an organizational account could be lost if the candidate left that organization.
Those logistics should not be copied into a current booking plan for AZ-220. The retirement notice is the controlling fact. For any replacement or adjacent certification, check that credential’s own exam page for current languages, delivery options, account requirements, price, and accommodation procedures.
What about the historical passing score and renewal?
The study guide stated that a score of 700 or greater was required to pass and that Microsoft associate, expert, and specialty certifications expire annually, with renewal through a free online assessment on Microsoft Learn. Those statements describe the certification program information attached to the active exam and should not be interpreted as a way to earn or renew AZ-220 after retirement.
Microsoft’s retirement policy says that previously earned certifications remain on a learner’s transcript, while a retired certification cannot be earned after the retirement date. Confirm the status of any credential in the learner’s own Microsoft Learn profile rather than relying on a third-party listing.
What should you do instead of booking AZ-220?
First, define the outcome you actually need: IoT application development, device interoperability, edge operations, cloud data engineering, AI, or evidence of a specific device’s Azure compatibility. AZ-220 covered several of these areas, but its retirement means a single current exam should not be assumed to replace the whole role.
If your goal is skill development, preserve the official AZ-220 domains as a project curriculum. Microsoft Q&A guidance confirms that IoT-related Microsoft Learn modules may remain available even after associated training or certification changes, although course and module availability can change. Save useful learning paths or modules to a personal collection where Microsoft provides that option.
If your goal is a current certification, inspect Microsoft Learn’s active certification catalogue and choose the credential whose published role and skills match your target. A Q&A response suggested Azure data-engineering study as one possible direction for people interested in the cloud data side of IoT, but that is a directional recommendation, not an official AZ-220 replacement.
If your goal is device validation, investigate Microsoft’s current device-certification material separately. A Q&A response described Azure Certified Device as validating device connection with Azure IoT Hub and secure provisioning through Device Provisioning Service, but readers should verify the current program page and requirements before making a certification decision.
A decision checklist for your next step
Choose the IoT outcome you want to demonstrate. Confirm whether the requirement comes from an employer, a project, a partner program, or your own learning plan. Check the current Microsoft page for the selected credential or learning resource. Preserve the AZ-220 outline only where it fills a real skills gap, and do not present completion of that outline as earning a current Microsoft certification.
For a practical portfolio, build a small solution that shows device onboarding, bidirectional messaging, state management, an edge module, data integration, monitoring, and security reasoning. Document the architecture and the failure tests. This provides evidence of capability without implying that an obsolete exam result exists.
How should you use this guide on dumpsboss.co?
Use this page as a status-aware planning reference: confirm retirement first, use the official outline to organize IoT study, and follow current Microsoft pages for any credential you may pursue. The useful preparation asset is the skill map and the implementation discipline, not a promise that third-party question collections can recreate an unavailable exam.
Before spending time or money on any AZ-220 material, compare its claims with Microsoft’s retired exam page and study guide. Reject listings that advertise a current booking, guarantee a pass, provide supposed live questions, or present old delivery details as current. Then move your effort to verified learning content, controlled lab work, and an active certification or role requirement.
Final recommendation
Do not schedule AZ-220: it retired on July 31, 2023, and Microsoft’s policy prevents new candidates from taking it or earning its associated certification after retirement. Use the later skills outline as a structured Azure IoT learning roadmap, validate each capability through implementation and troubleshooting, and select a current Microsoft credential only after matching its official scope to your intended role.
The most productive next action is to open the official study guide, choose the skills measured as of January 30, 2023, and mark every objective as demonstrated, explainable, or unverified. Build the missing capabilities in a small lab, save relevant learning resources, and verify the current alternative through Microsoft Learn before registering for anything.
Conclusion
AZ-220 remains a useful description of an Azure IoT developer’s former skill set, but it is not an available exam. The responsible preparation decision is therefore to separate historical study from current certification planning. Learn the hub, provisioning, edge, integration, data, operations, and security workflows; test them with evidence; and confirm any replacement credential directly against Microsoft’s current requirements.
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
