Hello WA,
Thank you for posting your query here!
Please note that Azure Storage provides service-side encryption (SSE) to automatically encrypt your data when it is persisted to the cloud. This encryption uses 256-bit AES encryption, one of the strongest block ciphers available, and is FIPS 140-2 compliant. The encryption and decryption process is transparent and does not require any changes to your applications.
For key management, data in a new storage account is encrypted with Microsoft-managed keys by default. However, you can also manage encryption with your own keys. If you choose to manage encryption with your own keys, you have two options: You can specify a customer-managed key to use for encrypting and decrypting data in Blob Storage and in Azure Files. Customer-managed keys must be stored in Azure Key Vault or Azure Key Vault Managed Hardware Security Model (HSM). Or you can specify a customer-provided key on Blob Storage operations. https://learn.microsoft.com/en-us/azure/storage/common/storage-service-encryption
This means that even if a file was to leave your network, without the encryption key, it would be rendered useless.
Also, for controlling access to the data, you can use Azure’s robust Identity and Access Management (IAM) solutions, along with the DLP capabilities provided by Microsoft Purview. This will ensure that only authorized applications and users can access the data. https://learn.microsoft.com/en-us/purview/dlp-learn-about-dlp
Do let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.