Storage

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add support for HTTPS endpoints to Azure Storage Emulator

    The Azure storage emulator doesn't support HTTPS endpoints. That means that when we develop locally under SSL, we either have mixed content warnings or get broken links.

    "Note that the storage emulator supports connection via HTTP only. However, HTTPS is the recommended protocol for accessing resources in an Azure production storage account."
    https://azure.microsoft.com/en-us/documentation/articles/storage-configure-connection-string/

    141 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  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.

  2. Support multiple storage accounts in Azure Storage Emulator

    The Azure Storage Emulator only supports a single fixed account (devstoreaccount1).

    This makes integration testing and development on the same machine a pain, as we would like to be able to clear the integration testing account entirely before and after each test sequence, without removing development data.

    The connection string to the new account could use the extended syntax (see https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator#authenticating-requests-against-the-storage-emulator - not "UseDevelopmentStorage=true"), with the same account key but a different account name, and if need be, different ports for blob/table/queue endpoints.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  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/40. 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.

  3. Storage Emulator with storage transaction counting and billing simulation.

    This enhancement would help to estimate production runtime costs and catch issues like excessive queue polling during development.

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  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/39. 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.

  4. Changing the maximum URL length for the development storage emulator REST api

    I'm making a request to the local storage which is over 300 characters in length. (Pretend this request is over 300 characters)

    http://127.0.0.1:10002/devstoreaccount1/MyTableName(PartitionKey='MyReallyLongPartitionKey',RowKey='MyReallyLongRowKey')

    I receive the following error message:

    Bad Request - Invalid URL
    HTTP Error 400. The request URL is invalid.

    Now, if I shorten the keys for a total length of 300 for the URL, I receive the ResourceNotFound error, which is fine, of course, as there is no such entity.

    Obviously, it's allowable to have valid PartitionKeys and RowKeys queries exceeding the length of 300.

    Is there any way to change the maximum URL length that the…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base