Elio Damaggio

My feedback

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

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    Elio Damaggio shared this idea  · 
  2. 14 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 (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    Hi Simon,

    We recently delivered the device twin functionality that should work for your scenario.
    https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-c2d-guidance

    An error occurred while saving the comment
    Elio Damaggio commented  · 

    Hi Simon, Joby,

    We are always listening to feedback on our quotas, and open to change them (when possible) if this affects many customers and possible customers. The main issue is that any new limit we define, would still affect some solutions. What limit would work for your cases?

    We are also aware that there are some scenarios for which C2D messages are ill-suited (e.g. updating configurations on devices, and long-running workflows), and working on new capabilities to address those in a batter way.
    It would help to understand the specific scenarios you are using these messages for.

    Elio

    An error occurred while saving the comment
    Elio Damaggio commented  · 

    IoT Hub messaging was designed to provide reliable communications. As such, the TTL is designed to overcome connectivity issues and not to assist in workflows (such as an enterprise messaging system like Service Bus). IoT Hub has to avoid keeping messages indefinitely as it should not be the source of truth on the status of your long running workflows. The 48 hours limit is derived from a notion than any flow running for more than a day is considered "long running".

    In case you have a long running workflow, the recommended route is to store the status of this workflow in the cloud (in SB or DocDB for instance), and use IoT Hub just for communications. IoT Hub provides a feedback queue for C2D messages that provides information on whether messages are successfully received by the device or expired. This feedback help drive your long running workflow in the cloud and deciding if the message is worth to resend or not.

  3. 7 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 (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    Hi Maik,

    Message transformation is on our radar, but not planned yet.
    In the meantime, you can easily use Azure Functions directly to pick up messages transform them, and put them in another Event Hub.

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

    We’ll send you updates on this idea

    2 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    We currently propose two avenues (depending on the specifics of your scenario).
    One way it to use a token service as delineated in https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-security#custom-device-authentication).
    The other way is to perform the check after the data has been sent to IoT Hub.

    One has to consider that an external module (e.g. Function) called for each message that hits IoT Hub would still has to be scaled to the same performance targets as a protocol gateway.

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

    We’ll send you updates on this idea

    1 comment  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    IoT Hub shipped routes in Dec 2016. It should solve this request.

  6. 15 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 (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    Elio Damaggio supported this idea  · 
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    We are aware of this requirement, and considering this feature.

  7. 65 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  13 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    What is the scenario for this feature request?
    Does it require all operations (device-originated, service-originated, identity operations) to be disabled?
    Does all IoT Hub data need to be retained (device identities, twin data, messages)?

    An error occurred while saving the comment
    Elio Damaggio commented  · 

    Hi Vien,

    Could you detail your scenario?
    Is it disable of all operations? Only device ones?

  8. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    Thanks for this feedback, it is already planned.

  9. 51 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    IoTHub team is evaluating auto-scale.
    In the meantime, you can use the REST APIs to change the number of units provisioned: https://msdn.microsoft.com/en-us/library/mt589015.aspx.

  10. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure IoT (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    IoTHub team is looking at various ways to improve telemetry scenarios. Supports for specific data format is being actively investigated. We will update when we have more information.

  11. 39 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 (Hub, DPS, SDKs)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Elio Damaggio commented  · 

    We are currently evaluating HTTP/2 support. Which scenarios are you guys considering that are not currently supported by AMQP or MQTT?

Feedback and Knowledge Base