This is currently not our our roadmap. Will mark this as unplanned and leave this open as we will revisit this in future planning cycles.
Thank you for your suggestion.
If you're using .NET standard client, you can already do this with Service Bus attachment plugin https://www.nuget.org/packages/servicebus.attachmentplugin
Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.
For any further questions, or to discuss your specific scenario, send us an email at DLMFeedback@microsoft.com.
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
Being the 2nd largest ask and 5 months since the last update, any updates to help people plan their work better?
@dan you're correct about Deferring rather than Abandoning. Though Deferring with a timespan feature request was close (https://feedback.azure.com/forums/216926-service-bus/suggestions/5471870-enable-setting-a-re-delivery-delay-when-abandoning) perhaps it shouldn't? 35 voices should go to that issue IMO.
Also testing scenarios, where between test runs queues need to be purged.
Without metadata support we're forced to use message to contain that info
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Azure Portal Team
How soon is "soon" Michael? :)
We are likely to support this in phases. Stay tuned for more details.
Please add support for this.
Great feature request. Let us go take a look at what this would take to build.
We already do something similar with Azure automation, having a schedule to shut VM down and bring it up. Having a Sleep feature would make it much simpler (and better).
Good feedback. No plans in this area, yet.