If you take the normal approach to create a linked server to SQL Azure Database, then you would end up in below error message.
Azure SQL Hyperscale: When the Database Outgrows One Server
Evaluate Hyperscale by separating compute and storage needs, testing read replicas, and checking migration, recovery, and current limits.
Azure SQL Elastic Pools: Sharing Resources Across Many Databases
Evaluate Azure SQL elastic pools using overlapping database demand, pool limits, per-database bounds, and measured workload performance.
SQL SERVER – Unable to Restore from URL – The Specified URL Points to a Block Blob. Backup and Restore Operations on Block Blobs are not Permitted
Restore from URL failed: operations on block blobs are not permitted. Checked against today’s documentation, the credential decides the blob type.
SQL SERVER – Previewing Old Azure Backup Blobs Before Removal with PowerShell
Backup Files From Azure Storage need a retention review before removal. I list the candidates before approving any cleanup.
SQL Azure Database – Msg 40197, Level 20 – The Service has Encountered an Error Processing Your Request. Please Try Again. Error Code 40549
A bulk insert from Azure Blob Storage failed hours in with Msg 40197, error processing your request, code 40549. Why long transactions get killed, and the fix.
Old SQL Backup Files in Azure Storage: PowerShell Inventory Before You Remove Anything
Old SQL backup files pile up in Azure Storage after a SQL Agent job runs for a while. An age cutoff finds candidates, but it cannot tell you what a restore still needs. This post gives a read-only PowerShell inventory and an msdb query that shows the backup chain.