You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -340,6 +342,7 @@ Client-side encryption of Azure SQL Database data is supported through the [Alwa
340
342
| File Sync | Yes | Yes, RSA 2048-bit | - |
341
343
| Queue Storage | Yes | Yes | Yes |
342
344
| Avere vFXT | Yes | - | - |
345
+
| Azure Cache for Redis | Yes | N/A\*| - |
343
346
| Azure NetApp Files | Yes | Yes | - |
344
347
| Archive Storage | Yes | Yes, RSA 2048-bit | - |
345
348
| StorSimple | Yes | Yes, RSA 2048-bit | Yes |
@@ -349,6 +352,8 @@ Client-side encryption of Azure SQL Database data is supported through the [Alwa
349
352
350
353
\* This service doesn't persist data. Transient caches, if any, are encrypted with a Microsoft key.
351
354
355
+
\*\* This service supports storing data in your own Key Vault, Storage Account, or other data persisting service that already supports Server-Side Encryption with Customer-Managed Key.
356
+
352
357
## Conclusion
353
358
354
359
Protection of customer data stored within Azure Services is of paramount importance to Microsoft. All Azure hosted services are committed to providing Encryption at Rest options. Azure services support either service-managed keys, customer-managed keys, or client-side encryption. Azure services are broadly enhancing Encryption at Rest availability and new options are planned for preview and general availability in the upcoming months.
0 commit comments