Storage

How can we improve Azure Storage?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Fix NullReference exception when user signs out in Windows and emulator is running

    When Emulator is running on Windows 10 and then I sign out I see the exception (NullReferenceException) over signing out screen.

    1 vote
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
    • 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.

      11 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
      • Support latest rest version in Azure Storage Emulator

        Currently you cannot use the latest Azure Storage Emulator (5.2) with the latest Storage Client Library (8.3.0) because the SCL supports '2016-05-31 REST version' and ASE doesn't.

        You will receive the error 'Invalid storage account 'devstoreaccount1'. Please make sure your credentials are correct.' if you try and connect to it.

        It is suggested by others to downgrade to SCL 7.2.1, but that is a no go if you happen to be using .NET Standard 1.4 in your project.

        3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
        • 1 vote
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
          • Fix Azure Storage Emulator security issue by enabling a custom or random storage key

            We are not allowed to provide the storage emulator to our developers because of the security issues of its design!

            Possible to have a custom storage key for devstoreaccount1 (or a randomly created one) via e.g. "AzureStorageEmulator newKey"?

            Current implementation is a security issue because a) it is a default password, which against almost all compliance frameworks, b) you are storing it hardcoded in cleartext in the configuration file.

            The hashed form (preferably via SHA256 or SHA512) can then be stored on local file system instead of the cleartext one. (a good idea could be using SHA512CryptoServiceProvider for preventing errors…

            2 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Storage Emulator  ·  Flag idea as inappropriate…  ·  Admin →
            • Don't see your idea?

            Feedback and Knowledge Base