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. Meter SubCategory column had Geo Redundant storage and Locally Redundant storage. New Convention came out with blank for these. Please inclu

    Meter SubCategory column had Geo Redundant storage and Locally Redundant storage. New Convention came out with blank for these. Please include Geo Redundant storage and Locally Redundant storage categories.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bug in portal when creating a storage account attempts to copy the storage account's tags to the VNet with which it has an endpoint mapping

    When creating a storage account via the portal which has tags defined and utilizes a VNet endpoint, the portal attempts to copy the storage account's tags to the VNet. This behavior does not occur with PowerShell or CLI and should not be expected anyway, as tags are specific to each individual resource. This causes additional issues if the customer has Azure Policies in place requiring certain tags on certain resources, as well as VNet endpoints for Storage Accounts, preventing deployment. This can also cause issues if the individual deploying the storage accounts doesn't have rights to update the VNet's tags.…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Azure Function dll gets locked and cannot be deleted, read, written or executed even after restarting the Function

    I ran into an issue where after running an Azure function and there was an infinite recursion loop which caused the function host to die suddenly (entirely, no errors, nothing). The dll file open at the time got locked and could no longer be unlocked. This made fixing the problem very difficult.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base