Access Azure API with a bearer token for impersonation

In the past, I wrote an article on how to get Azure service tags. Back then, I was not able to access the Rest API provided.

A service tag represents a group of IP address prefixes from a given Azure service.

This week I revisited the API and dived a little deeper into this call.

In this blog, I show you how to read service tags using the Azure Rest API and we learn how to cope with the bearer token if we want to access the Access API. I show it both in Postman and using C# code.

Securing inbound and outbound ports for Azure IoT

The Azure IoT Hub is able to support a high number of IoT devices, all communicating with their own personal secure connection.

The Azure IoT Hub supports both MQTTs, AMQPs and HTTPs as transport protocols. It’s even possible to communication MQTTs and AMQPs over websockets for Azure IoT Edge.

No, it’s not possible to transfer IoT telemetry and commands without TLS supported communication.

But what if a hacker tries to spoof a device, or our IoT Hub?

How can we be sure that received telemetry is coming from genuine devices? And can we limit the device communication to our own Azure resources?

Do you know who you are talking against?

Let’s see how we can make Azure IoT yet a little bit more secure.