Using a Shared Access Signature (SAS) is usually the best way to control access rights to Azure storage resources (like a container for backups) without exposing the primary / secondary storage keys. It is based on a URI and this is what I want to look at today.
I always use the Azure Storage Explorer to build a SAS token. Let’s dig into what the different parts mean.
I only ever use the storage explorer when managing my blobs, files, queues within storage accounts. It is your single view access point for all your storage needs and I totally recommend downloading it and using it (https://azure.microsoft.com/en-gb/features/storage-explorer/).
Do you execute DBCC CHECKDB on your Azure SQL Database? From past experience I know some people do, I would suggest not to bother. Why?
Sometimes you may not want to flip over to the Azure portal to grab the database size, such as the used space below.
Microsoft and Oracle recently announced a joint cloud partnership (I have seen the word multi/cross-cloud to explain this) which I found very fascinating to read. It is currently in preview and the idea is to have an integrated cloud experience between Oracle Cloud and Microsoft Azure. A private dedicated connection is obviously needed and whilst knowing more about Azure, looking at the below diagram it makes sense (from an architecture POV) as the Oracle equivalent of ExpressRoute is FastConnect which is needed.
All About Tech 