Related forum post.
This is still a (serious) issue even with SQL Server 2016 SP2.
Please escalate - we have multi-terabyte database backups in Azure blob storage.
Upvotes: 1<=-=Apr 14 2017 2:38AM=-=>
Also refer MSDN forum thread:<=-=Sep 4 2017 4:53PM=-=>
No wonder customers are hating on SQL backups to Azure.
We are on SQL 2016 SP1 CU4 now, and no surprise it’s still not working.<=-=Nov 6 2017 5:34PM=-=>
Running SQL Server 2016 SP1 with CU5 and SQL Server Management Studio (SSMS) 17.3 now and this is still broken.
Really? Now at SQL Server 2016 SP2 CU2 and SSMS 17.8.1 and not as much as a peep.
The UI polish with the Managed Backup to Azure features is atrocious.
Please fix this junk.
Thank you for the feedback. We are working on prereqs to make this possible. Not in scope for CY2019.
Was bitten by this restriction today. We have a service that is growing and suddenly we needed to change public IP if we wanted to use Azure Load Balancer because our Public IP sku was BASIC.
Errata: First paragraph should read as:
Whilst there is are Peformance Counters for the *total* disk ("\\LogicalDisk(_Total)\\% Free Space") it is often meaningless if you cannot see what a specific drive is doing.
Apologies closed in error. Reopening
For the love of Azure - please address this pronto!