The Business Critical tier of Azure SQL Managed Instance offers the read-scale out feature enabling you to distribute read-only workloads such as reporting and analytics across built-in replicated secondary replicas within the same region. You can use this by specifying ApplicationIntent=ReadOnly in your connection string, your queries are then automatically routed to these replicas.
I do believe most people know about the ability to backup your SQL server databases to URL (from Azure VMs). If you recall you would use the storage key ( ideally not) or a SAS token, from there you would create a SQL credential that is bound to the SAS token (as a secret). Lots of moving parts especially when it comes to rotation time. So now, if you are on the newer versions of SQL server (SQL Server 2022 Cumulative Update 17 ) start thinking about backups via managed identities.
Ok, so Azure SQL doesn’t really have its own error log based somewhere on a machine within \\MSSQL\Log directory but the closest thing you will get is a system catalog view called sys.event_log which is very useful. It will get you information about all sort of event types such as:
This is by no means a complete list but more of a personal list of features I have seen not setup or just missed out when looking at Azure SQL DB. After reading, not only will I hope that you agree but it may provoke you to double check your setups.
Sometimes you may not want to flip over to the Azure portal to grab the database size, such as the used space below.
All About Tech 