We’re back with this month’s edition of Device Certification Tips & Tricks to help you make the most out of your device certification project! This month, we’re talking about our Dependencies tab in the Device details section.
You may be wondering – what exactly is a dependency? A dependency exists when your IoT device does not connect directly to Azure. It may require additional hardware or software services, such as a gateway device, SaaS, or PaaS offering. Fortunately, your indirect device is still eligible for certification! Our program welcomes these indirect devices as crucial components of the IoT ecosystem. To certify your indirect device, all you need to do is highlight the dependencies in our portal (pictured below).
Some important things to note are:
- If you select a gateway dependency, the device must be an Azure Certified Device that has been published to the catalog.
- The customer-facing comments will appear on the catalog, so make sure the description of how the dependency works is clear and marketing ready!
Ready to get started? You can view more guidance on the dependencies feature on our Microsoft Docs page to learn more.
Remember to like this post or leave a comment down below if you have any questions! Our team is ready to help you get started with your IoT device certification journey.