IoTHub Unauthorised Response
We work with small handheld devices that send events and general info to our backend using Azure IoT Hub and MQTT with self-made SAS Tokens. On the 24th of September we received over 1 million Unauthorized responses when trying to connect to the hub, using our handsets that had not had any code/protocol changes. From there, the number of Unauthorized responses have dropped dramatically to be in the ten thousands, but we are still getting the Unauthorized response on handsets that have the correct provisioning info (keys, hub address). When discussing with Microsoft support team they have said it is due to an expired Sas token, but our Sas tokens have been regenerated and still the problem persists. They also said they didn't make any code/structural changes to the hub, but the sudden unexpected behavior persists. Has anyone had similar issues? We have regenerated Sas tokens, sent new keys and provisioning info, but any handsets we get back into our hands do not show the problem.Take back control over IoTHub messages in Azure Functions
Azure Functions are a blessing for IoT solutions. To be so flexible executing code whenever messages are arriving, every IoT project is fully depending on it. But one of the biggest frustrations is the casting of (EventHub) messages towards a string! Only the message body is left! Once a message is passed on to an Azure Function, I only have access to the body of the message. I can not access the (routing) properties anymore. And before we got Azure Functions, we had to work with Stream Analytics. And I still do! And it's so nice to have access to the IoT Hub values like the device name of the message. Because I am working with Azure Functions, I have to put it in the Message body first??? It would be great to have access to both the properties and the IoTHub values! Well, it's possible now with some clever casting... Read the full story here
