Companies starting design and development on new IoT products have often heard about how cloud providers such as Microsoft Azure and Amazon Web Services (AWS) can help deploy and rapidly scale their products. Because of this, one of the most frequently asked questions is: What cloud provider should I choose? Both Azure and AWS have been expanding their services over the past years, so let’s take a deeper look at Azure vs. AWS and which cloud provider might be right for you and your new IoT product.

Considerations: Azure vs. AWS

From a technical perspective, you want to choose a cloud provider that not only fits your immediate needs but also scales easily with your business years down the road. Both Azure and AWS can easily support most of your functional and nonfunctional requirements, let’s take a step back and look at it from a high-level perspective first.

• If you have an existing partnership with either vendor, continuing with the same vendor could minimize system-level integration issues.
• If your company relies on Microsoft Suite, working with Azure may position you to leverage internal features you’d like to use, such as Azure File Storage.
• If you’re planning an international expansion, it’s important to consider the region and availability zones of each provider per country.

Off the shelf, Azure and AWS both provide highly secure and scalable offerings. You’ll have access to certification-based security, be able to transmit data bi-directionally, and easily manage the number of devices you have going. Additionally, you’ll be able to update the underlying containerized software with their over-the-air (OTA) updates – just like a Tesla!

Azure

Azure’s unique IoT offerings lie within its integration with the Windows OS, hardware specialization, and additional special security features. Some of its offerings:

• Microsoft tries to make all of its products Windows OS compatible, including their IoT stacks. Although it’s not common, if your IoT device is running a Windows OS, Azure provides ease of compatibility to their IoT Hub.
• Azure’s IoT Sphere service is a specialized hardware chip and underlying firmware that provides users with a true end-to-end security experience. This may be useful for hardware devices that must be HIPAA compliant.
• Azure supports the Advanced Message Queueing Protocol (AMQP). AMQP provides additional security at connect, supports peer-to-peer connection, is more extensible, and has many other great benefits.

AWS

AWS provides customizability and a wider variety of tools than Azure as well as a selection of analytics services that are tailored and designed to work with IoT Core and Greengrass.

• AWS’s latest IoT service, IoT TwinMaker, takes the Digital Twin concept to a new level, where you can create a virtualization of your IoT world. Visually being able to see, navigate, and manage your solutions is now much easier.
• Working with IoT Analytics to analyze your device data with Device Defender allows you to mitigate issues that were found in audit findings, whereas Azure will only monitor without mitigating issues.
• AWS IoT Core and IoT Device Management services are HIPAA eligible services and can be HIPAA compliant.
• One unique thing about AWS’s IoT framework is the direct C++ device SDK. Although both Azure and AWS provide many common languages for SDK, and Azure works with .NET, AWS’s C++ support is more advanced.

Scoring Criteria Table

We’ve generated a list of criteria and respective scoring of how well we believe both AWS and Azure are doing based on these latest service offerings, which are outlined below. For any project, you should weigh the importance of each criterion, multiply by the score for the respective cloud provider, and sum up the score.

Use Case Examples

#1: Developing a New Medical Device

Company A is creating a new medical device to be launched across North America and in several countries across Asia. Company A has worked with both AWS and Azure on a case-by-case basis and must determine which provider to go with for the new product, which must be HIPAA compliant. Due to recent security concerns for international expansion, the product will have additional in-house developed security measures. As the business case is still in an early stage, the product’s communication protocol must scale to potentially diverse regulations.

As seen above, the recommended cloud provider should be Azure to potentially leverage their AMQP protocol and IoT Sphere service if necessary. The use of Azure IoT service here is a risk management strategy, and the tradeoff would be that the C++ device SDK is not official and a workaround will be needed.

#2: Monitoring and Diagnostics of Equipment

Company B is opening up a new manufacturing company with state-of-the art machinery to build electric vehicles. To monitor and track the condition of all of its major hardware components, the company directly partnered up with robotic suppliers to integrate IoT health telemetry reporting. Company B’s prime success metric is the number of hours of operation and the ability to predict when each equipment will fail and why. This will be translated into continuous real-time telemetry measurements, simulating scenarios with device telemetry, and being able to understand the cause of failures. The additional security will be handled via the network of the factory itself, and suppliers are flexible with both the device development languages and using the MQTT protocol for its lightweight feature.

Company B should go with an AWS-based framework as it provides audit mitigation and off-the-shelf analytics, IoT Sitewise, and IoT Analytics. The potential trade-off here is that they would lose on the hardware integrated security.

Azure vs. AWS: Necessary Questions

Here are some questions you can ask about your product’s development:

1. As you will most likely get to deployment fastest by continuing the relationship, do you have any partnerships or already use a product suite with Microsoft or AWS?
2. Does either cloud provider have a specific offering that is critical for your product solution?
3. Based on the evaluation matrix scoring breakdown and your technical requirements, do you foresee a feature from a particular provider that can heavily accelerate your development?
4. Do you feel that the default criteria in the weighted evaluation matrix accurately represent your product?

Selecting the right cloud provider for your new IoT product is complicated but can be made easier with the more transparency you have in your product roadmap. When you know what criteria are most important, you can understand Azure vs. AWS and match them with the technical requirements of your product solution.