Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

bdcoder

My feedback

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    bdcoder shared this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Cloud Shell  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    bdcoder commented  · 

    27-Oct-2018 -- same issue -- see: https://github.com/MicrosoftDocs/azure-docs/issues/17748

    Still looking for a solution

  3. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →
    bdcoder shared this idea  · 
  4. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    bdcoder commented  · 

    Background: While doing some testing it became apparent how easy it was to delete a container and all blobs within it -- Simply click the Delete icon for any container and then click "Yes" to confirm and all your production blobs may soon be magnetic dust -- and because most production code will automatically (re)create a container if it does not exist, you will NOT be able to recover your data (see point 2 below):

    This from Microsoft:

    If you delete a Blob Storage Container, we cannot guarantee that the data can be recovered. We can initiate a best effort option, though; if the data hasn’t been garbage collected yet, we would open a critical response incident ticket as soon as possible. For more information, feel free to visit the Azure Storage webpage. Also, it is always good practice to keep a backup of your data, but if this were to happen, the hypothetical procedure (behind the scenes) would be:

    1. Storage doesn’t provide in-place recovery, which means the data won’t be restored to the original storage account. Instead, it will be put in the secondary region.

    2. We would ask you NOT to recreate the containers. It is crucial that a container with the same name is not made because this will overwrite the path to the pre-existing container, losing all chance of recovery

    3. If the storage account in question is a LRS account, recovery is not possible. If it is GRS or RAGRS, we would ask you to execute the following steps:

    a. You would need to generate a read+list permissions SAS token for the container you want to recover, setting the expiry time to be at least 7 days in the future so the recovery has time to be recovered.

    b. You must make your account RAGRS via the portal. I would recommend doing this anyway, as the data is safer in this kind of storage.

    Bottom line -- if you have a production system and some intern or newbie decides to delete a container that holds production data, you are basically doomed.

    bdcoder supported this idea  · 
    bdcoder shared this idea  · 
  5. 5,138 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    172 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →
    bdcoder supported this idea  · 
    An error occurred while saving the comment
    bdcoder commented  · 

    Dear Microsoft:

    As seen by the multitude of posts below, can someone (anyone?) from inside Microsoft please post a reply with regard to the question about when SSL (https) will be supported with custom domains?

    As most of the comments below indicate, we WANT to use MS services, but unless SSL functionality comes before the end of this year (2016), many of us will simply be forced into to using a different service as we cannot make any type of argument to our superiors as to why our competitors are hosting their content via https, and we (who are using MS services) cannot.

    Tomorrow, I have to try to explain to a panel of execs why we cannot use https and our custom domain like our competitors are. I fear they may simply say, "Well then, lets switch services"!

    Again, an MS reply / announcement / specific date / any help would be in order.

Feedback and Knowledge Base