Anonymous

My feedback

  1. 99 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Azure Kubernetes Service (AKS) » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    either allowing us to choose which nodes to delete when scaling down, or having the oldest nodes deleted during a scale down operation would both be better than the current behavior (newest nodes are deleted during scaledown)

    Anonymous supported this idea  · 
  2. 88 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for this feedback!

    We’re working on or have shipped several features that we think will satisfy this request.

    First, we have shipped the share snapshot feature, which enables you to protect a point-in-time for a file share. If a user were to delete a file, you can restore from the previous snapshot. To make this easier, Azure Backup will soon support scheduling share snapshot.

    Second, and more to the specific ask in the initial post, we are working on AAD authentication and authorization for Azure file shares. When we ship this feature, you will have the ability to set share ACLs that prevent deletes or modifications.

    Thanks,

    Will Gries
    Program Manager, Azure Files

    An error occurred while saving the comment
    Anonymous commented  · 

    Currently the reader role does not have permissions to view files on the azure portal, a message saying access denied will pop up if a reader attempts to view files. can the reader role be updated so it can view files on the azure portal?

    Anonymous supported this idea  · 

Feedback and Knowledge Base