Storage Service Encryption provides encryption at Rest; it does handle encryption, key management and decryption part of the out-of-the-box feature. There is no additional requirement for payload management or enabling code to manage the feature.
Azure SSE encrypt data when it writes to Azure Storage, and it can be enabled on
Blob Storage and
File Storage (in preview at the time of the draft), only. The feature is available to
Premium storage. This feature is a relatively new (while drafting the post) thus it would be advisable to check the availability into your preferred region.
It is an amazing journey for me as a
Cloud Architect since last decade. On my first day with CxO boardroom, someone asked me “Would it be secure and compliant to trust the cloud with sensitive and PII data?” It was a valid question, and my precise reply was I’m sure it would be.
I begin the “Googling” – and shockingly no useful search result having
PII both present in a web page. I am going to rest the preface of the series here, and let’s get going with technology.
I wrote the following script last year, was very handy and proved useful for last few Azure projects. The script creates an Azure AD Application, an Azure AD Service Principal and then assign a given role.
Azure StorSimple is a unique service, not many organisation subscribe to it, nor many have an appropriate use case to implement hybrid on-demand storage solution bridging on-premise StorSimple Hardware and Azure Storage.
However, there are some certain scenarios where organisations are dealing with a significant amount of supplementary data (less frequently accessed). i.e. Insurances, Banking & Financial, Law. Some of mentioned institutions have very large dataset (not archived due to legal or compliance framework) while most of their teams and staff are working on a small set of the overall dataset. These are an excellent fit for Azure StorSimple implementation.
There are number of solutions available to transfer data from one location to another location, I was trying to narrow down to some good practices, and I find them between SQL Sever Integration Service and BACPAC File Export/Import.
The question has halted me for last month, so decided to go back to basic. Researching and then writing blog my brainstorming process, it has been successful in past for me, and I am hoping that it is going to be this time as well as. Unlikely my other posts, I am going to stay away from suggesting or even hinting the conclusion. Comparing Azure Service Bus and Azure Storage Queue is like comparing Apples and Oranges.
Interestingly, it came to my notice that implemented web resources are leveraging HTTP content compression as other through delivered Azure Edge traffic. It wasn’t passing
Accept-Ending HTTP header unless it finds selected resource type (i.e.