AWS S3 Encryption
Objects stay in S3 for scale. Decryption still requires a key share you hold outside AWS.
Service Encryption for Microsoft 365
Bring your own root keys to Microsoft 365 service encryption, generated and held under your control.
Microsoft Purview Customer Key encrypts Microsoft 365 data at rest with root keys you control. DuoKey generates and governs them under your authority.
Root keys created and governed by you, then made available to Microsoft 365 service encryption.
Search, eDiscovery and Copilot keep working, because Microsoft 365 services can still use the key.
Revoking access to your keys triggers cryptographic deletion of your data.
Customer Key encrypts data at rest for the Microsoft 365 services you authorise, with RSA root keys in Azure Key Vault or Managed HSM that you control.
One data encryption policy can cover several workloads, including Copilot interactions and Windows 365 data at rest.
Create, rotate and revoke keys from the Cockpit, with policies on who can do what and a record of every key operation.
Microsoft documents it plainly: revoking access to your keys triggers deletion of the availability key and cryptographic deletion of your data.
Customer Key covers service encryption for the core Microsoft 365 workloads. Use it broadly, and DKE for the small slice Microsoft must never read.
Generate and govern the keys behind Microsoft 365 service encryption.
Create, rotate and revoke from one console.
See who uses your keys and when.
Distributed trust, no single point of compromise.
The records regulators expect, from one place.
Built for large tenants and key volumes.
Customer Key for broad service encryption, DKE for what Microsoft must never read.
Proof in practice
Deep dives
Compliance
Trust
Customer programmes
See Customer Key with root keys under your authority and a real exit plan.
Products
Objects stay in S3 for scale. Decryption still requires a key share you hold outside AWS.