Static websites is planned for the coming year! This feature will include more detailed error messages as well as support for a default Storage Blob. As soon as we have updates to share on Static Websites we will do so. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

Thank you all for the feedback! This is something we are actively developing, and hope to rolling out in a preview in the first half of this year! Stay tuned for more information!

Thanks,

Will Gries
Program Manager, Azure Files

We are pleased to announce that we have made an Azure Logic Apps template available to expire old blobs. To set up this automated solution in your environment: Create a new Logic Apps instance, select the “Delete old Azure blobs” template, customize and run. We will release a blog post detailing instructions and providing more templates in the coming weeks.

Allowing users to define expiration policies on blobs natively from storage is still planned for the coming year. As soon as we have progress to share, we will do so. We will continue to provide updates at least once per quarter. 

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

Our apologies for not updating this ask earlier. We view this ask as a set of related features. Soft delete and automatic snapshots will help protect against accidental deletions and overwrites. Write Once Read Many (WORM) will disable modification (by anyone, including administrators and hackers) for a specified period of time.

This work is planned for the coming year, and we will be delivering it in multiple phases. As soon as we have progress to share, we will do so. We will continue to provide updates at least once per quarter. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

Thanks for your feedback. We are now planning to add support for /MIR and rsync-like functionality in AzCopy. Unlike them, the sync mechanism will only work on based on time stamp and file size. Deleting files in the destination will be based on an optional flag.

The first preview of this feature in AzCopy is expected to release around May, 2018.

Thank you for your feedback! We working to provide this functionality through the Azure Backup offering. They are currently testing this functionality in a private preview, and are going to be entering a public preview soon. I will update this feedback item as soon as this is released.

Thanks,

Will Gries
Program Manager, Azure Files

Thanks for your feedback! As you mentioned, we initiate a change detection job once every 24 hours to enumerate the Azure file share and scan for changes. This is required for the Azure file share because Azure Files currently lacks a change notification mechanism like Windows Server has (we watching the USN journal on Windows Server to automatically initiate sync sessions on the server after changes are made).

Long term, we would like to build a change notification mechanism directly into Azure Files. Shorter term, we could use your feedback to understand how painful the once every 24 hours change detection is for you. Please vote and/or leave comments on this item to let us know we should invest in work to make the change detection job run more frequently/faster.

Thanks,

Will Gries
Program Manager, Azure Files

Thank you for your feedback. We are currently working on features that will provide this functionality and will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

Thank you for the feedback! This is an issue we are aware of and are actively working to close this gap this year. Please feel free to continue to vote for this item to help us prioritize this effort.

Thanks,

Will Gries
Program Manager, Azure Files

Azure Storage is actively working on features that could improve the migration story from standard to premium disks.

Thanks for your feedback! We are planning to add support for Server Core installations. We’re not taking any dependencies in the Azure File Sync agent on Full-only features, so supporting Core should be relatively straight-forward, however we do have two small dependencies to unwind. First, we have a dependency on the AzureRM PowerShell module, which right now requires Internet Explorer to be installed (which obviously is not available on Core). Second, we are working to make sure our installer is completely configurable from in an unattended mode.

Please continue to vote for this item to help us prioritize (and to help the AzureRM team have the evidence to support Windows Server Core).

Thanks,

Will Gries
Program Manager, Azure Files

Azure Storage is currently working on features that would address this problem.

Thanks for this feedback. Long term, we would like the File REST API for Azure Files to be a superset of the functionality available in SMB. In the short term, we are looking to close some of the gaps in the API that are most painful, like the file attributes that you can set via SMB but not File REST.

We would appreciate further feedback on this item, in particular feedback on the things that you can do today over SMB but not REST to help us prioritize the order in which we close the gap!

Thanks,

Will Gries
Program Manager, Azure Files

Azure Storage is actively working on features that would address this concern.

Azure Storage is actively working on features that could address this request.

Thank you for you feedback. This work is planned for the coming year. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

Azure Storage is actively working on features that could address this problem.