Jon Gallant

My feedback

  1. 145 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Storage » Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. Providing this functionality is on our backlog but there is no ETA we can share at this time. We have logged this request in the GitHub repository for the new open source storage emulator, Azurite. Please continue the discussion there: https://github.com/Azure/Azurite/issues/38. We will provide updates when they become available on this ask as well as in the GitHub repository. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

    Jon Gallant commented  · 

    I realize this is an old thread, but just in case you happen upon this while trying to figure out how to use Azurite with HTTPS. I created a blog post to help you setup an HTTPS -> HTTP proxy https://blog.jongallant.com/2020/02/azurite-https-defaultazurecredential/ Please comment or vote for this item if you still need HTTPS.

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

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant shared this idea  · 
  3. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant commented  · 

    Thanks Elio.

    Jon Gallant shared this idea  · 
  4. 13 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 →
    Jon Gallant 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

    1 comment  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant shared this idea  · 
  6. 12 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 →
    Jon Gallant shared this idea  · 
  7. 4 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 →
    Jon Gallant 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

    0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant shared this idea  · 
  9. 22 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  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant shared this idea  · 
  10. 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).

    Jon Gallant commented  · 

    There is currently no way to compress IoT Hub message collections. Currently the SendEventBatchAsync method does not compress the payload. We'd like the DeviceClient.SendEventBatchAsync method to behave exactly as it does today, but just enable compression BEFORE sending to IoT Hub and decompression BEFORE sending to EventHubClient.SendBatchAsync.

    We know that we can create a receiver and decompress ourselves, but we don't want to do that because it breaks all downstream services that use IoT Hub as an input.

    Jon Gallant supported this idea  · 
  11. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure IoT  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Gallant shared this idea  · 
  12. 15 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 →
    Jon Gallant shared this idea  · 
  13. 23 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 →
    Jon Gallant shared this idea  · 

Feedback and Knowledge Base