Olivier Bloch (MSFT)

My feedback

  1. 22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  2. 86 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  11 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  3. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) commented  · 

    Hi Ian.
    Azure IoT Hub exposes an Event Hub endpoint for monitoring the Device 2 Cloud Messages using the AQMP protocol.
    The .Net SDK has an internal dependency to the Event Hub SDK which is available in various languages (C, Java, Node.js): https://github.com/Azure/azure-event-hubs.
    In addition to this endpoint IoT Hub allows to create new custom endpoint (service Bus Queue, Topic, Event Hub) along with defining routes using queries to direct messages to specific endpoints based on messages properties (and content as well soon).

  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  6. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  7. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  8. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  9. 38 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  10. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 
  11. 54 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →

    This is not in our plans for now but definitively an interesting scenario.
    As of today you can already do so in different ways such as compressing data in your device code before sending and using an Azure Function on the back end that will be triggered each time a compressed message arrives. Not totally integrated into IoT Hub but gives you the choice of the compression format and flexibility in routing messages before decompressing content (using message headers for routing).

    Olivier Bloch (MSFT) commented  · 

    Today's infrastructure for IoT Hub messaging is letting you put whatever you want in the payload of the messages. Nothing prevents from serializing your data with Protobuf on the device, sending up to IoT Hub and have your backend solution (using Stream Analytics, Functions, or your own worker role) deserialize the payload.
    What more would you expect from IoT Hub?

  12. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Olivier Bloch (MSFT) shared this idea  · 

Feedback and Knowledge Base