Anonymous

My feedback

  1. 22 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Automation » Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 747 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    Our apologies for not updating this ask earlier. Renaming Blobs is on our backlog, but is unlikely to be released in the coming year. Today, you can use the “Copy Blob” API as a workaround.

    Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol.  This enables usage of normal Windows API’s to rename files and directories.  You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files.

    For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

    Anonymous commented  · 

    azure restore did not let me chose the name of my restored VHD. Now I can't generalize the image because the Azure generalize command doesn't like the name that Azure chose while restoring my virtual machine. The fact that Azure thinks it is best to chose names for me is ridiculous. I am an administrator and shouldn't be forced to have UID's in the names of my Azure entities.

  3. 474 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    64 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    this is an awful thought process by microsoft.

Feedback and Knowledge Base