Currently there is really no way to get current Azure File share usage from Azure CLI or Azure PowerShell. The only way possible is to enable Azure Monitor or just go to UI (or Azure Storage Explorer) and check usage yourself.
Please add this to output of Get-AzStorageShare command as for now you could only get Quota information without any information about current usage. Thanks!

Encryption Scope depends on Key Vault
Key Vault has a collocation constraint which prevents that it work on multiple regions
Encryption Scope is incompatible with RA-GRS and does not support secondary failover region

You can turn on the Soft Delete option in Blob Storage, but not when it's got the ADLS Gen2 box checked. Please make this available in the ADLS Gen2 storage accounts. We just had an accidental deletion of a top-level folder in the container and it couldn't be restored by the MS engineers even with the geo-replication going.

We can't get last-modified property of files in File Shares using Get-AzureStorageFile. It is null, but we have this property in Azure Portal.
Can we improve this command?

We would like to access Azure Files file shares on macOS systems using AD DS authentication, as we do for our Windows clients.

We do not want to mount using access keys.

Do you plan to implement this or should I look in a different direction?

PLEASE Support Reserved Capacity for Premium Blobs

The ability to create an Azure Monitor alert rule when an Azure Storage Files share usage approaches quota, out-of-the-box without having to create a custom script automation.

Currently, the only metric on which an alert can be created on a storage account usage is usedCapacity(Avg) which is in bytes. A feature where an alert can be created for a certain percentage of storage account being full would be very helpful to monitor the usage of the storage account. For example, if a user wants to create an alert when 80% of the total capacity of a storage account is used, he should be able to do that very easily using portal, Azure CLI, and Azure PowerShell.

Enable JSON format support at blob storage API HTTP response.

Example, instead of:

HTTP/1.1 404 The specified resource does not exist.
Content-Length: 223
Content-Type: application/xml
Server: Blob Service Version 1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: dbe27af2-701e-0045-0939-c25bc5000000
Date: Tue, 24 Nov 2020 08:10:19 GMT

<?xml version="1.0" encoding="utf-8"?><Error><Code>ResourceNotFound</Code><Message>The specified resource does not exist.
RequestId:dbe27af2-701e-0045-0939-c25bc5000000
Time:2020-11-24T08:10:20.8064839Z</Message></Error>

Using a querystring option or using a "x-ms" specific header to obtain:

{

"Error":{

    "Code":"ResourceNotFound",

    "Message":"The specified resource does not exist. RequestId:dbe27af2-701e-0045-0939-c25bc5000000 Time:2020-11-24T08:10:20.8064839Z"

}

}

Immutability at the object level is really missing here. It's a huge drawback compared to the competition.

Bo.

Pls. enable authentication support for Azure File SMB access using Azure AD credentials from Windows 10 devices joined to Azure AD.

Azure Storage Explorer support variety of features such as Copy, Paste, Clone etc. However, we did not see any documentation which explains which roles and permissions should be set to view these feature.

Having such documentation should help us.

Storage is the largest part of the cost of my lab. I have 4 P10 disks that cost me $17 per month each. I would like more machines but this cost is prohibitive. Any ideas?

Why can Azure storage account name be only up to 24 characters and cannot contain anything besides numbers and lowercase characters? Most Azure services allow at least "-" character, but Storage and Kusto are notable exceptions.

I love to have an incident at 3 am and figure out if it is prodscr1weuncasrlt or prodscr1neuncasrlt, vs prod-scr1-weu-cas-rlt.

Allowed Access to Trusted services lumps general access to some resources in with allowing more tightly control access for resources such as Cognitive Services via assigning roles to the instance Managed Identity. Why not split these categories into two flags?

We were generating many millions of transactions per day in Data Lake. Through some trial and error we were able to identify the Databricks delta lake merge and optimize commands that were generating the transactions. It would be great if some fine grained details were available on the transactions [beyond the API read/write level] that could trace which Databricks job / notebook was generating the transactions; something like # transactions by type by notebook / job by date.